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.
- Food Distribution SCM
- Features
- Distribution orders
Distribution orders
Accept orders against the service time, destination, portions and menu constraints.
OverviewMy Distribution Orders×
Food Distribution SCM · Distribution orders
New
My Distribution Orders
Distribution orders
| Record number | Subject | Status | Serve at | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| DO-50450 | Draft do-679 | Draft | 27 Oct | DP-3554 | ||
| DO-60951 | Accepted do-101 | Accepted | 21 Oct | DP-1641 | ||
| DO-81348 | Preparing do-281 | Preparing | 20 Oct | DP-6578 | ||
| DO-69689 | Ready do-533 | Ready | 09 Oct | DP-2260 | ||
| DO-65667 | Served do-897 | Served | 26 Oct | DP-2847 |
6 of 6 records
Draft do-679Distribution orders · DO-50450
DraftServe at27 Oct
CounterpartyDP-3554
What you can do
Start with the service commitment
An order begins with a destination, a planned service time and the menu lines the team expects to prepare. Order Coordinator selects the delivery point and checks that it is active and belongs to the operating organization. The destination’s contact, address and eligibility note give the team context before it commits. The order owner stays visible from draft through service.
The service time matters as much as the requested quantity. Before acceptance, Order Coordinator reviews the available products, the requested portions and the ingredient allergen declarations carried into the menu scope. The acceptance workflow checks capacity for that time and calculates the net amount. The accepted timestamp and operation receipt identify the actual commitment; a draft alone is work to review.
How the work is organized
- Order header. Keep the number, subject, destination, owner, service time, revision and current status together.
- Menu lines. Keep each menu item, portions, price and allergen declaration under its parent order.
- Acceptance evidence. Retain the actual accepted time and the guarded operation result so a retry has an established answer.
What to agree during setup
Choose who can accept an order for each organization and when the kitchen considers a service time feasible. Review how a menu line maps to an active product and which approved recipe revision applies when preparation begins. Decide how the team handles a destination that becomes inactive while an order is still open. These are operating decisions for the Order Coordinator and Kitchen Lead to make before the first live cycle.
For example, a venue requests several portions for an evening service. The coordinator checks the venue and the allergen declarations before acceptance. If the number of guests changes, the team reads the current revision and lines before revising the commitment. The earlier acceptance remains visible through its receipt.
Check the handoff on an actual case
Trace one accepted order from its number to its lines and destination. Confirm that the planned service time and net amount match the accepted scope. Ask the kitchen to show which lines are being prepared and which have an actual preparation timestamp. A ready order should still distinguish preparation from the served portions recorded on its lines. If some portions are later served while the rest are cancelled, the served history remains on the line.
A correction to accepted or executed work is a reviewed compensating action. Exception Reviewer checks the current revision, prior decisions and operation receipts before it changes the remaining scope. A repeated correction request returns the prior outcome instead of creating another effect.
What your team sees
- Open Distribution Orders — Draft and active service commitments with owner, destination and service time.
- My Distribution Orders — The order owner’s worklist for the current operating cycle.
- Order Status Board — Orders grouped by their current stage without treating readiness as delivery.
Follow the work through
Use order acceptance for the intake decision and preparation and service for the later handoff.
What it keeps track of
Data model- Distribution orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Order lines
- Individual menu item lines within a meal order.
- Delivery points
- Dining rooms, outlets, venues and delivery destinations served by the operation.
- Products
- Sellable menu products and packaged goods.
- Product recipes
- Versioned recipe headers for products, with yield and approval state.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
Who uses it
Permissions- Order Coordinator
- Owns intake and acceptance.
- Kitchen Lead
- Prepares the accepted lines.
- Exception Reviewer
- Investigates changes to committed scope.
- Admin
- Maintains the operating setup.
Set up Food Distribution SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.