Food CRM
At a food producer the same product goes to the chain supermarket, the local wholesaler and the hotel kitchen on different terms; as the number of channels grows, who is getting which price is lost in the spreadsheet. The field team is visiting, the listing negotiation is running, samples are going out — but none of it sits in the same place.
The price for a chain supermarket, a wholesaler and a hotel kitchen sits in the account record's own field; the order takes it from there. A field visit is a task, closed on site from the app.
- Manage chain supermarket, wholesaler, HORECA and export customers as separate account types and apply each its own price and discount terms
- Plan field sales visits, see that the representative reached the point with GPS verification, and have shelf and stock notes written onto the visit record
- Track the listing negotiation and sample despatch as a staged opportunity and see which product is at which step with which chain
- Link a product complaint to a case record by batch number and gather complaints for the same batch into a single list
| Channel-Based Pricing | Chains, wholesalers and HORECA are separate account types; the agreed price and discount sit in the account's field and pass from there to the order. |
|---|---|
| Point of Sale Visit | A visit is a task; the date, the representative and the point of sale are its fields; the representative closes it at the supermarket from the mobile app, the location is verified by GPS, and shelf and stock notes are written to the same record. |
| Listing Process | Getting a product into a chain is an opportunity record; the negotiation, the sample and the paperwork are each a stage, and every stage has its own date. |
| Batch and Complaint | A complaint is a case record; the batch number is carried in its field, and cases belonging to the same batch appear in a single list. |
What makes food difficult is not the complexity of a single process but the fact that several processes running at once know nothing about each other. A listing negotiation with a chain supermarket takes months and has its own document calendar; the local wholesaler orders weekly; the hotel and restaurant kitchen asks for samples and negotiates the price separately; the export customer asks for product specifications and a shipping schedule. When these are kept in different files, the point the field team visits and the terms on the price list do not match; and when a complaint comes in, which batch went where can only be found by hand.
In Rapitek CRM every channel sits inside the same account structure but with its own terms: the price and discount are fields on the account, and the order takes them from there. A field visit is a task; the representative opens it from the mobile app on arriving at the point, the location is verified by GPS, and shelf and stock notes are written inside the visit. The listing negotiation and sample despatch each move along as an opportunity record with its own stages; a complaint is a case record, and because the batch number is carried in its field, complaints belonging to the same batch are gathered in a single list.
The scope of the plans and the items priced separately are set out on the pricing page.
