Restaurant purchase order workflow: keep human control from request to close

A restaurant purchase order is a promise about an intended purchase, while a receipt records what actually arrived. The value of the workflow is the controlled bridge between them. National Restaurant Association inventory guidance notes that technology can automate purchase orders, coordinate suppliers, manage permissions, and update prices. Those capabilities do not remove the need to define who may request, approve, issue, receive, amend, and close an order. Traceability guidance also recognizes POs, advance shipping notices, invoices, and receipts as linked reference documents. Build the links first; choose automation only after the human control path is clear.

Start with a request that another person can evaluate

A request should state why the purchase is needed without pretending that a forecast or par level is a fact. Record the site, requesting role, product identity, specification, quantity, unit, required-by point, and the stock, prep, service, or maintenance record supporting it. If a request combines several products, preserve separate lines. A named substitute or preferred supplier can be a proposal, but it should not bypass the review of product identity, pack, unit cost, usable quantity, and operational impact. This gives the approver enough context to approve, reduce, defer, ask a question, or reject without relying on a private conversation.

• Name the requester and site so a central buyer can distinguish local need from a duplicate request.
• Record product description, specification, quantity, and unit as the requester understands them, then verify the source record before issue.
• Keep required-by date or service point separate from a supplier promise; the former is an operational need, not delivery proof.
• Show the proposed supplier, alternative, or substitute as a decision field rather than hiding it in a free-text note.
• Record the approver, decision, date, and question or condition attached to an approval.

Issue, receive, and handle exceptions as separate states

Once approved, issue a PO with a stable number and revision history. Send the intended lines to the supplier through the channel your operation controls, and link an advance shipping notice or equivalent when one is used. At receipt, compare the issued lines with physical quantity, condition, timing, and site-defined checks. Do not overwrite the PO to make a partial or substituted delivery appear expected. Create a discrepancy or exception record, link evidence, and preserve the original order. The invoice should be matched to accepted receipt data, not treated as proof that the order was fulfilled. A closure status should show whether all lines are accepted, corrected, credited, replaced, or still open.

Clearly labeled illustrative example: one PO through closure

A repeatable restaurant PO process

1. 1Capture the request. Record site, requester, product identity and specification, quantity, unit, required-by point, supporting record, and any proposed supplier or substitute.
2. 2Review and approve. Check need, permissions, price source, alternatives, and operational impact. Record approve, amend, defer, reject, or question with the responsible person and date.
3. 3Issue the PO. Assign a stable PO number and revision, preserve the approved lines, send the order through the controlled supplier channel, and link any advance notice.
4. 4Receive and record. Compare order and delivery line by line, record accepted and held quantities, condition and site-defined checks, and link the receiving evidence.
5. 5Resolve exceptions. Create a discrepancy for missing, damaged, wrong, substituted, or otherwise unresolved lines. Link supplier communication, replacement, credit, or internal disposition without rewriting the original PO.
6. 6Match and close. Link the invoice to accepted receipt data, keep open exceptions visible, record final ownership, and close only when the documented follow-up is complete.