OrderPay
Guide 8 of 10

Treat packing and fulfilment as their own controlled stages.

Prepared does not mean packed, and packed does not mean handed over. Explicit progress helps authorised staff understand the current responsibility without changing financial state.

Prepare the packing view

Use the accepted order snapshot to confirm item, variant, modifier, quantity, menu, run, customer-visible instructions, and fulfilment context. Restrict unnecessary personal data.

Define ready

Agree what must be complete before an order is marked ready, who can set the state, and how the customer is notified. Keep shortages and substitutions in an explicit exception path.

Verify the handoff

For pickup, kerbside pickup, or configured local delivery, use the approved customer or order reference without announcing excess information. Record only the state needed for the workflow.

Keep money state separate

Fulfilment progress does not itself authorise a cancellation, refund, or payment adjustment. Those actions require the relevant role, reason, provider result, and audit evidence.