Tastings
Scheduling a tasting against a catering order, and recording what the client thought.
KitchenSync → Tastings lists tasting appointments. Each one belongs to a catering order.
What an appointment holds
| Field | Notes |
|---|---|
| Client name and email | Who is coming |
| Scheduled at | Date and time |
| Items to taste | What you are putting in front of them |
| Status | Where it has got to |
| Tasting notes | Yours, before or during |
| Feedback | Theirs, after |
Booking one
From the tastings page, or from a catering order's own tasting section — the second is usually easier, because the order already knows the client and the menu.
There is no tasting TYPE. No seated versus walk-around versus chef presentation; that distinction does not exist in the software. If it matters to you, put it in the notes.
After the tasting
Record what they said in Feedback and move the status on. That feedback stays attached to the order, so whoever builds the final menu can see what was liked.
There is no star rating, no structured per-dish scoring, and no automatic update to the order's menu from a tasting outcome. Changing the menu after a tasting is something you do yourself on the order.
Why it is attached to an order
Because a tasting is only useful next to the event it is for. The link means:
- The tasting shows on the catering order it belongs to
- The order's client details fill themselves in
- The kitchen dashboard can list upcoming tastings alongside upcoming events
An appointment with no order is not something the system supports — if a prospective client wants a tasting before anything is booked, create the catering order first, even a bare one.
What is not here
No reminder emails to the client, no calendar invitation, no conversion tracking from tasting to booking, and no comparison across tastings. It is a schedule and a place to write down what happened.
Keep reading
Still stuck? A person reads every email.
If a guide and the app disagree, the app is right. Tell us and the guide gets fixed.