Greenhouse and Nursery CRM
When a seedling order comes in the plant is still in the soil, and the decision was made months earlier. Get the season's demand wrong and you are either left with seedlings you cannot sell or unable to find the species the landscaping firm wants.
A supermarket chain, a landscaping firm and a dealer are each an account record; species preference and order history accumulate there, and next season's production plan comes out of those records.
- Keep the order history and species preferences of supermarket chains, landscaping firms and dealers per customer
- Follow the balance between orders and stock on the same screen and update your production plan accordingly
- Keep plant species, price and stock information up to date and share it with your customers
- Send campaigns and offers to the target customer group during planting and sowing seasons
- Send new product announcements and order confirmations over WhatsApp
| B2B Customer Management | A supermarket chain, a landscaping firm and a dealer are each an account record; species preference is in a field, and order history accumulates under the card. |
|---|---|
| Order and Production Planning | Orders and stock are tied to the same product record; open orders and the quantity on hand appear side by side in a single list. |
| Product Catalogue Management | Species, price and stock are fields on the product record; the list shared with the customer is produced from that card, and no separate catalogue is kept. |
| Seasonal Campaigns | A campaign is a record; the target group is filtered on customer fields, and because orders coming back are tied to the campaign, the result is measured. |
| Plant Passport Tracking | For every batch that goes out for dispatch, the plant passport number and its date of issue are fields on the batch record; a batch whose paperwork is not complete does not close the dispatch task, and which batch went to which customer is read backwards from the same record. |
In a nursery there are months between sale and production: the decision about a seedling to be delivered in spring is taken in autumn. That is why the real question for the business is not how many orders came in this month, but which customer wanted which species and in what quantity last season. As long as that information sits scattered across order slips, the production plan is made from memory.
Because Rapitek CRM keeps the data of past seasons broken down by customer and by species, next season's demand forecast rests on that record. The wholesale and retail sides are run with separate price lists and payment terms; order picking, packing and dispatch stages are followed on the same record too.
