Work from immutable order snapshots
Each accepted line keeps the relevant item, variant, modifier, menu, run, and fulfilment context. A later catalogue change does not silently alter that accepted requirement.
Plan production from the orders that were actually accepted.
Production views should answer what must be prepared for a run without making the team reconstruct demand from emails, provider receipts, or an edited product list.
Separate production from payment exceptions
Paid, cancelled, refunded, disputed, and unresolved orders have different operational meaning. OrderPay preserves those states so a team can review exceptions instead of treating every checkout attempt as production demand.
Carry work into packing and handoff
Preparation is not the final state. Packing and fulfilment progress remain explicit so the team can distinguish an item that is made from an order that is ready for pickup or delivery.