Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Food Distribution SCM
- Payment provider
- Delivery event source
SCM for Food Distribution follows an order from a named delivery point and service time through acceptance, kitchen preparation, dispatch review, distribution events and reconciliation. An order owner checks active products, requested portions, allergen declarations and capacity before accepting.
Distribution orders in one list
Dispatch Supervisor approves the submitted ticket revision before release.
Every feature works on the same records. Pick one to see the screen your team works in.
Accept orders against the service time, destination, portions and menu constraints.
Distribution orders
| Record number | Subject | Status | Serve at | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| DO-50450 | Breakfast trays for Cedar Hall | Draft | 04 Nov | Jun Seo | Harbor conference center | |
| DO-60951 | Lunch service for Bayview clinic | Accepted | 29 Oct | Miriam Haddad | Eastbank office pantry | |
| DO-81348 | Soup and rolls for North Pier cafe | Preparing | 28 Oct | Rosa Delgado | Maple residence dining room | |
| DO-69689 | Evening meals for Maple residence | Ready | 17 Oct | Lucia Chen | Maple residence dining room | |
| DO-65667 | Salad boxes for Harbor conference | Served | 03 Nov | Lucia Chen | North Pier cafe |
Keep each venue or destination tied to its operating organization.
Delivery points
| Name | Code | Contact name | Address | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| Cedar Hall dining room | CEDAR-HALL | Elena Ruiz | 24 Cedar Street, Oakland, CA | Breakfast drop before 7:30 a.m. | Willow Pantry Collective | |
| Bayview clinic kitchen | BAY-CLINIC | Nabil Farouk | 81 Bayview Road, San Mateo, CA | Use clinic service entrance | Willow Pantry Collective | |
| North Pier cafe | NPIER-CAFE | Tina Park | 5 Pier Lane, Alameda, CA | Cold items require signed receipt | Harvest Lane Kitchen | |
| Maple residence dining room | MAPLE-RES | Grace Okoro | 42 Maple Avenue, Berkeley, CA | Pureed meals accepted weekdays | Maple Hearth Distribution | |
| Harbor conference center | HARBOR-CONF | Luis Moreno | 16 Harbor Drive, Richmond, CA | Loading dock booking required | Maple Hearth Distribution |
Prepare accepted menu lines against approved recipes and record actual preparation.
Order lines
| Parent | Line number | Menu item | Portions | Prepared at | Served portions | |
|---|---|---|---|---|---|---|
| Lunch service for Bayview clinic | 790 | Roasted vegetable breakfast tray | 370 | 29 Oct | 510 | |
| Breakfast trays for Cedar Hall | 680 | Lemon chicken lunch bowl | 450 | 01 Nov | 440 | |
| Evening meals for Maple residence | 830 | Tomato basil soup, 16 oz | 880 | 16 Oct | 920 | |
| Snack packs for Willow after-school | 540 | Grain and greens salad box | 130 | 18 Oct | 920 | |
| Sandwich platters for Eastbank office | 180 | Apple oat snack pack | 570 | 18 Oct | 930 |
Review each submitted dispatch ticket revision before release.
Approval conditions
| Status | Revision | Table code | Sent at | Guest count | Delivery reference | |
|---|---|---|---|---|---|---|
| Submitted | 400 | CEDAR-A12 | 22 Oct | 12 | DEL-2026-08142 | |
| Submitted | 900 | BAYVIEW-B04 | 20 Oct | 37 | DEL-2026-08158 | |
| Submitted | 700 | PIER-C07 | 09 Oct | 39 | DEL-2026-08177 | |
| Submitted | 960 | MAPLE-D18 | 12 Oct | 8 | DEL-2026-08203 | |
| Submitted | 960 | HARBOR-E02 | 14 Oct | 30 | DEL-2026-08216 |
Record allocation, picking, shipping, delivery and return against an order.
Distribution events
| Parent | Product | Event type | Quantity | Occurred at | External event ID | |
|---|---|---|---|---|---|---|
| Salad boxes for Harbor conference | Turkey and cucumber sandwich platter | Delivered | 90 | 20 Oct | dispatch_evt_8812 | |
| Salad boxes for Harbor conference | Roasted vegetable breakfast tray | Returned | 420 | 16 Oct | load_evt_8830 | |
| Snack packs for Willow after-school | Tomato basil soup, 16 oz | Delivered | 550 | 18 Oct | arrival_evt_8846 | |
| Breakfast trays for Cedar Hall | Turkey and cucumber sandwich platter | Returned | 340 | 13 Oct | serve_evt_8861 | |
| Breakfast trays for Cedar Hall | Apple oat snack pack | Delivered | 240 | 20 Oct | return_evt_8879 |
Check guarded operations against persisted effects and retain the review trail.
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| Evening meals for Maple residence | ACCEPT-2026-8801 | Accept meal order | 580 | Failed | Allergen declaration is incomplete | |
| Sandwich platters for Eastbank office | PREP-2026-8802 | Release kitchen batch | 440 | Needs review | Hot hold fell below target | |
| Snack packs for Willow after-school | DISPATCH-2026-8803 | Dispatch delivery van | 410 | Failed | Delivery point was closed | |
| Fresh pasta for Ridgeview dining | DELIVER-2026-8804 | Confirm venue receipt | 490 | Needs review | Prepared count differs from order | |
| Lunch service for Bayview clinic | REVIEW-2026-8805 | Review allergen exception | 610 | Failed | Menu substitution lacks approval |
Accept to verified delivery ships ready to use. One step needs a named approval before the work moves on: Review dispatch (Dispatch Supervisor).
Review the destination, menu and planned service time.
Commit feasible portions and retain the acceptance result.
Use the approved recipe and record actual preparation.
Dispatch Supervisor decides the submitted ticket revision.
Track shipped, delivered and returned quantities.
Match operation receipts to actual records and references.
Open any distribution order to see its dispatch tickets, the roles that work on it, its process stages and its approvals on one page.
Serve at, Owner, Counterparty and Revision.
Each line is linked to this distribution order.
Order Coordinator, Kitchen Lead and Dispatch Supervisor, each with their own permissions.
Every status change, in order.
Review dispatch, with who decides.
North Pier cafe · Draft
| Status | Revision | Table code |
|---|---|---|
| Submitted | 400 | CEDAR-A12 |
| Submitted | 900 | BAYVIEW-B04 |
| Submitted | 700 | PIER-C07 |
Signed in as Dispatch Supervisor
| Decision | Approver | |
|---|---|---|
| Review dispatchDispatch Supervisor decides the submitted ticket revision. | Dispatch Supervisor | |
| Approve dispatch tickets | Dispatch Supervisor | |
| Approve distribution orders | Exception Reviewer |
Everyone opens Food Distribution SCM to the work that is theirs. Pick a role to see what it starts with.
Owns order intake, destination selection and accepted service scope.
This is the first screen this role sees.
Distribution orders · Order Coordinator
Prepares the accepted portions and records actual ingredient use.
This is the first screen this role sees.
Distribution orders · Kitchen Lead
Independently decides whether a submitted dispatch ticket can be released.
This is the first screen this role sees.
Dispatch tickets · Dispatch Supervisor
| Status | Revision | Table code | Sent at | Guest count | Delivery reference | |
|---|---|---|---|---|---|---|
| Submitted | 400 | CEDAR-A12 | 22 Oct | 12 | DEL-2026-08142 | |
| Submitted | 900 | BAYVIEW-B04 | 20 Oct | 37 | DEL-2026-08158 | |
| Submitted | 700 | PIER-C07 | 09 Oct | 39 | DEL-2026-08177 | |
| Submitted | 960 | MAPLE-D18 | 12 Oct | 8 | DEL-2026-08203 | |
| Submitted | 960 | HARBOR-E02 | 14 Oct | 30 | DEL-2026-08216 |
Records distribution movements and delivery evidence against the order.
This is the first screen this role sees.
Dispatch tickets · Delivery Operator
Checks failed operations, corrections and payment evidence before closure.
This is the first screen this role sees.
Dispatch tickets · Exception Reviewer
| Status | Revision | Table code | Sent at | Guest count | Delivery reference | |
|---|---|---|---|---|---|---|
| Submitted | 400 | CEDAR-A12 | 22 Oct | 12 | DEL-2026-08142 | |
| Submitted | 900 | BAYVIEW-B04 | 20 Oct | 37 | DEL-2026-08158 | |
| Submitted | 700 | PIER-C07 | 09 Oct | 39 | DEL-2026-08177 | |
| Submitted | 960 | MAPLE-D18 | 12 Oct | 8 | DEL-2026-08203 | |
| Submitted | 960 | HARBOR-E02 | 14 Oct | 30 | DEL-2026-08216 |
Maintains organization, staff, catalogue and access setup.
Read service status, movement, recipes and exceptions from the operating records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 26 | ||
| Accepted | 17 | 65% | |
| Preparing | 12 | 71% | |
| Ready | 8 | 67% |
Sample totals per stage
Which commitments are still draft, being prepared or ready for service?
What part of each accepted menu line was actually served?
Where do shipped quantities differ from delivered and returned quantities?
Which ingredient declarations belong to each approved recipe?
Review ingredient movements by Ingredient, signed quantity and occurred at.
Read dispatch tickets and review decisions by parent order, source revision and operation key; confirm the ticket context before attributing a decision.
Which guarded actions still need evidence review?
Which provider receipts still await verification?
See how Food Distribution SCM fits your kind of team.
Coordinate accepted meal orders and dispatch decisions across service venues.
Track packaged products from an accepted order through delivery to an outlet.
Keep organizations, staff, destinations and review decisions clear across an operating group.
Each stage of accept to verified delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to inspect orders, prepare decisions and trace exceptions with your team.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 18 tablesStart with one team and one process, then add the rest once the basics are running.
Set up organizations, active team members, delivery points and access for the people who will own orders and review dispatch.
Load products, ingredients, approved recipe revisions and allergen declarations. Check units and portion yields with Kitchen Lead.
Rehearse a draft order through feasibility, acceptance, preparation and service, preserving each actual timestamp and quantity.
Submit a ticket revision for independent review, release its approved scope and record shipped, delivered or returned product quantities.
Reconcile a failed receipt, a partial service cancellation and payment evidence before staff use the cycle for live work.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure SCM for Food Distribution for your business. Start with one organization, active delivery points, menu products and an order that your team can follow through service.
Yes. Keep each dining room, outlet or venue as a delivery point with its own contact, address and organization.
The kitchen reads the current order and its menu lines, then uses the approved recipe revision selected for preparation.
Ingredient records carry allergen declarations. Order lines also retain the declaration for their menu scope so the coordinator and kitchen can check it before acceptance and preparation.
No. Preparation, served portions and distribution events are recorded separately. Follow the actual event and portion evidence.
Dispatch Supervisor reviews the submitted revision and records an independent approve, reject or return decision with a reason.
The changed revision goes through review again. The earlier decision remains with the earlier scope.
Record the actual delivered and returned quantities as their own distribution events, retaining the earlier shipped event.
Exception Reviewer reads the operation receipt and linked effects first, then attaches evidence and resolves the outcome against what persisted.
The team reviews provider-issued payment evidence and its verified state before closing a refund-related correction. A repeated request should return its prior result.
Start free, then use Proto to change fields, steps and approvals before your team goes live.