Catering CRM template: confirm every order, and win back the regulars who go quiet

A caterer has two kinds of customer: the party that orders once, and the office that orders every month until it quietly stops. This board handles both, with one card per customer and one deal per order.

Palby CRM counts Closed and Completed as won. A customer who orders again stays on the same card, with the new order added as a deal.

Fields sit on the customer, not on each order. So for a customer who orders more than once, log every order as its own deal:

• Name it with the date and the headcount, like "12 Mar lunch, 40 pax, Level 5 pantry". A deal name holds up to 120 characters.
• Set Expected close to the event date.
• Add the menu as lines from your products list: "Buffet A (per pax)", quantity 40, at S$18. The deal's value adds itself up.

The card's own fields then hold the next order's details. When a regular orders again, move their card back to Quote sent, update the fields, and let the deals keep the history.

1. Reply within the day. Catering enquiries go to whoever quotes first, and Enquiry goes stale after one quiet day.
2. Chase the quote in three days. Event dates are close, so Quote sent goes stale after three.
3. Confirm dietary needs before an order is Closed. The stage asks for them, so a card can't move there with the field empty.
4. Ask how it went the next day. When a card moves to Completed, set its follow-up to Tomorrow.
5. Catch the regular who goes quiet. Add a note each time an order comes in. Every board has an Inactive over 30 days view, and an office with no note, chat or stage move in 30 days lands on it.
6. Plan for the festive rush. Office parties pile into December and the weeks before Chinese New Year. Message last year's festive customers by early November.

1. Pick Home services, cleaning and repairs when you set up your business.
2. Delete Job done and Paid. Rename Job booked to Closed, then add Completed after it.
3. Add the ten fields.
4. In each stage's settings, pick its Needed to enter fields and type its Stale after days.
5. Add your menus under Manage products, in any stage column's menu, priced per pax.

Orion ordered every month until September. It's been on the 30-day list since last week, and today's call asks why before another caterer finds out.

Copy these columns into Google Sheets or Excel, one row per order:

Customer | Company | Phone | Event type | Event date and time | Pax | Menu | Price per pax (S$) | Total (S$) | Dietary needs | Service | Delivery address | Postal code | Status | Paid

Sort by Event date and time every day, and once a month look for regulars with no order in the last 30 days.