Aquaculture CRM
In aquaculture the sale is agreed months before the harvest: the buyer wants a particular size in a particular week, and when the fish will reach that size is known on the production side. When the two sides are kept in separate places, sales promises a batch that is not ready and production ships a batch without knowing who it was set aside for.
The size range, quantity and delivery week promised to a buyer are a record linked to the account; the harvest batch stands separately, and the two are read side by side by delivery week.
- Write the size range, quantity and delivery week agreed with the buyer onto the account record and track approaching commitments from the list
- Link the harvest batch to a record with production unit, size class and harvest date fields, and see which batch is set aside for whom
- Collect dispatch documents as attachments on the record and keep their validity dates as fields, listing missing paperwork before loading
- Plan cold chain delivery as a task, record the vehicle and delivery time, and inform the buyer by SMS or WhatsApp
| Harvest Batch | A batch is a record; the production unit, the size class and the harvest date are its fields, and the quantities set aside accumulate under that record. |
|---|---|
| Buyer Commitment | The agreed size, quantity and delivery week are a record linked to the buyer's account; commitments whose week is approaching are filtered from the date field. |
| Document Set | The documents accompanying a dispatch sit as attachments on the record; the validity date is a field, and a dispatch with a missing document stays flagged on the list. |
| Cold Chain Delivery | A delivery is a task; the vehicle, the delivery time and the temperature note are its fields, and a closed task leaves a trace on the buyer's record. |
In fish farming time works in two directions: the fish in the pond or the cage grows every week, while the buyer wants a fixed size range and a fixed delivery week. The sales side gives that promise over the phone, the production side keeps the harvest order on its own schedule; when the two do not meet, either the promised size does not hold or a batch that is ready sits waiting. On the dispatch side a single missing document stops the whole load, and the hunt for who has that document starts on the morning of loading.
In Rapitek CRM the buyer is an account record; the agreed size range, quantity and delivery week sit on the record linked to that account, and as the week approaches the commitments drop into a list. The harvest batch is a separate record: the production unit, the size class and the harvest date are its fields, and how much has been set aside for which buyer is read from that record. Because the documents accompanying a dispatch are collected as attachments on the same record and their validity dates are kept as fields, a missing document is visible before the day of loading rather than on it.
The scope of the plans and the items priced separately are set out on the pricing page.
