These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Catering Management
- Features
- Event orders
Event orders
Keep the customer commitment, venue and serving time on one controlled order.
OverviewServed Event Lines×
Catering Management · Event orders
New
Served Event Lines
Event order lines
| Parent | Line number | Menu item | Portions | Served portions | Prepared at | |
|---|---|---|---|---|---|---|
| EO-70313 | 540 | MI-821 | 330 | 410 | 26 Oct | |
| EO-46290 | 220 | MI-343 | 340 | 950 | 23 Oct | |
| EO-79303 | 310 | MI-281 | 900 | 510 | 14 Oct | |
| EO-93489 | 900 | MI-579 | 320 | 790 | 20 Oct | |
| EO-91060 | 920 | MI-237 | 450 | 250 | 14 Oct |
6 of 6 records
MI-821Event order lines · EOL-10280
ParentEO-70313
Line number540
Portions330
Served portions410
Prepared at26 Oct
What you can do
Event orders in daily work
A coordinator begins with the event subject, customer reference, serving time and venue. Each line carries its menu item, portions, unit price and allergen declaration. The owner is the team member responsible for the order. Those details let the kitchen assess an actual commitment rather than a loose event note. A venue’s contact, address and eligibility note make the destination intelligible to the service team. The organization gives the order its operating context and time zone.
How the work is organized
- Confirm the destination. The coordinator selects the venue and owner under the operating organization before accepting a serving time.
- Price the actual lines. Portions and unit prices explain the order amount; allergen declarations travel with the menu commitment.
- Keep the accepted revision. The receipt and accepted time identify the scope handed to the kitchen, even when later work changes.
Acceptance checks active products, portion quantities and allergen constraints and confirms capacity for the serving time. The guarded action calculates the net amount, records accepted time and leaves an operation receipt. A changed line or changed venue should be reviewed against the current order revision before another acceptance action. The coordinator can explain the amount from the lines and can point to the accepted version that the kitchen received.
What to agree during setup
Agree who may accept an order and how the team checks serving-time capacity. Decide how the coordinator verifies products and allergen declarations before promising a menu. Require an owner, venue and current revision at the acceptance handoff. Give the supervisor a route to review changes after acceptance, with the original accepted and performed work still visible.
Check the handoff on an actual case
Consider a lunch order for a named venue with a revised guest count. The coordinator updates portions while the order is still Draft, checks the menu against the declared allergens, and accepts the feasible revision. The kitchen sees that accepted scope. If the guest count changes after preparation has begun, the original prepared and served facts stay attached to the order. Only the remaining scope can be corrected through the review path.
Before a coordinator changes an accepted order, compare the current line quantities with any preparation and service already recorded. The correction path preserves those facts and asks the supervisor to decide what remains eligible. A fresh order amount should represent the accepted commitment, while a receipt explains whether the guarded acceptance actually completed.
What your team sees
- Open Event Orders — Accepted, preparing and ready commitments with serving time, venue and owner.
- Served Event Lines — The portions guests received, linked back to their order and preparation time.
Follow the work through
Follow the process and review roles and permissions before a live handoff.
What it keeps track of
Data model- Event orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Event order lines
- Individual menu item lines within a meal order.
- Event venues
- Dining rooms, outlets, venues and delivery destinations served by the operation.
- Team members
- Staff members linked to an organization and platform identity.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
Who uses it
Permissions- Event Coordinator
- Accepts the feasible order.
- Kitchen Lead
- Reads its accepted scope before production; Service Lead uses its venue and serving time for handoff.
Set up Catering Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.