Open one week at a time
Publish individual meals on a scheduled menu, set the order cutoff before preparation, and offer only the pickup dates or configured local-delivery windows you can fulfil.
Close meal orders before prep starts.
A small weekly menu works best when customers know which meals are available, when orders close, and when they can collect. OrderPay connects that dated offer to paid preparation and packing work without requiring a fixed-price meal bundle.
Limit the preparation run
Set product limits and, when several meals use the same preparation capacity, a shared pool. The server checks current availability before accepting an order.
Pack from paid orders
Confirmed orders retain the chosen meals, variants, menu date, and fulfilment details. Review production quantities and packing progress for the run rather than counting unconfirmed checkout attempts.
Example: Sunday Table
A synthetic seller offers chicken bowls and vegetarian dinners for Sunday pickup. Orders close Thursday evening; both meals use a merchant-configured 60-unit preparation pool with separate product limits.
Start with a simple menu
A customer can place a one-off order for a dated menu. This workflow does not provide automatic nutrition labels, choose-any-five bundle pricing, imported subscriptions, or delivery-route planning.
Frequently asked questions
Can customers order just this week?
Yes. A dated menu supports individual orders for an available week. A recurring customer agreement is a separate product choice with its own terms.
Does OrderPay calculate nutrition labels or delivery routes?
No. Merchants remain responsible for required food information and their delivery operation; the current workflow does not generate nutrition labels or plan routes.