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 service
Event service
Track delivered products and actual served portions at the event.
OverviewDelivered Fulfillment Events×
Catering Management · Event service
New
Delivered Fulfillment Events
Fulfillment events
| Parent | Product | Quantity | Occurred at | External event ID | |
|---|---|---|---|---|---|
| EO-13788 | PRD-3707 | 610 | 22 Oct | EEI-853 | |
| EO-73619 | PRD-4299 | 800 | 10 Oct | EEI-934 | |
| EO-19392 | PRD-9739 | 920 | 20 Oct | EEI-419 | |
| EO-87388 | PRD-6883 | 350 | 17 Oct | EEI-606 | |
| EO-77449 | PRD-3305 | 460 | 15 Oct | EEI-547 |
6 of 6 records
EEI-853Fulfillment events · FE-67766
ParentEO-13788
ProductPRD-3707
Quantity610
Occurred at22 Oct
What you can do
Event service in daily work
The accepted order names a venue and serving time. Its lines retain ordered portions, prepared time and served portions. Fulfillment events add dated allocation, pick, ship, deliver or return facts for a product and order. The Service Lead uses those records to distinguish work sent toward a venue from portions actually served to guests. A delivery event alone does not settle the served quantity on an order line.
How the work is organized
- Match the destination. Service Lead checks the order venue and serving time before recording physical handoff.
- Track movement by product. Fulfillment events retain their external identity and dated allocation, delivery or return result.
- Record guest service separately. The line’s served portions describe what guests received; unresolved scope remains visible.
At handoff, the Service Lead checks the destination and product against the accepted order. External fulfillment identifiers help match incoming events to the right local order and avoid treating a repeated event as a second delivery. The service team records actual served portions for each line. An order reaches Served after its performed scope is accounted for. A partially served order retains both the performed quantity and any remaining scope requiring a decision.
What to agree during setup
Agree who records physical events and who confirms the portions served to guests. Match each external fulfillment identity to its order and product before importing it. Decide how the team reports a short delivery, return or partially served event to Operations Supervisor. Keep venue contacts current so a delivery reaches the intended service location.
Check the handoff on an actual case
Imagine a reception where a tray is delivered but several portions remain unused. The fulfillment event records delivery of the product, while the line records only the portions actually served. If remaining food is returned or wasted, its event or ingredient movement is separate. The coordinator can answer how much was ordered, prepared, delivered and served without merging these meanings. If the event needs a correction, the supervisor reviews only the eligible unserved scope.
At shift change, the incoming Service Lead can compare a delivered product with the line’s served portions and the original order. A returned item remains a physical return, even if guests received some portions earlier. When the numbers differ, keep the event identity and time with the record so the team can reconcile the remaining work without counting a repeated delivery twice.
What your team sees
- Delivered Fulfillment Events — Product deliveries with source identity, occurrence time and parent order.
- Served Event Lines — Actual served portions beside the planned portions on each order line.
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.
- Fulfillment events
- Allocation, picking, shipping, delivery and return events.
- Event venues
- Dining rooms, outlets, venues and delivery destinations served by the operation.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
Who uses it
Permissions- Service Lead
- Records fulfillment and guest service.
- Event Coordinator
- Checks remaining commitment; Operations Supervisor reviews a correction when performed and unserved scope diverge.
Set up Catering Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.