To sell a limited batch without overpromising, set a production cap for each pickup date, reserve units at a defined point in the order process, and stop accepting orders when that cap is reached. Then reconcile accepted orders against the kitchen’s production list before making the batch.
The important distinction is timing. An ordinary item can be marked sold out when today’s supply runs out. A preorder commits part of a future batch to a guest. Your ordering process needs to account for those commitments before the kitchen begins work.
Set the batch quantity and order window
Start with the smallest dependable limit, not the largest number you hope to sell. Ask the chef or production lead how many units the kitchen can make alongside normal service. Ask the person buying ingredients how much confirmed supply will arrive in time. Include packaging, refrigerator space, staff hours, and pickup capacity in the discussion.
For example, the kitchen may be able to bake 60 pies, but the pickup area may only handle 40 during the available window. Unless you add another pickup period or change the handoff process, 40 is the more useful starting cap. A pickup period is an operational limit as well as a promise to the guest.
Decide whether the cap applies to the whole batch, a particular pickup day, or each pickup window. If Friday and Saturday have separate production runs, track them separately. Otherwise, Friday orders could consume stock the team intended to make on Saturday. If the same batch serves several windows, use one shared batch limit as well as any window-specific limits.
Hypothetical example: A bakery plans 40 boxed pies for Saturday. The production lead sets aside four as a buffer for damage or production problems, leaving 36 available to preorder. Each order can contain up to four pies. The order window closes Thursday at noon, or earlier if all 36 sell. These quantities are assumptions for planning, not a guarantee that the bakery will produce all 40.
Write down who can change the cap and who must approve an increase. A manager should not raise availability just because requests keep coming in; the production and pickup limits still apply. Also decide what happens if ingredient delivery falls short after orders close. Name the person responsible for contacting affected guests and arranging an appropriate remedy.
Your restaurant website can explain the offer before guests begin an order. Put the pickup date, window, quantity limit, and closing time where a guest can see them before checkout. Include the time zone if guests may order from outside the area.
Reserve inventory at the right step
A guest viewing a pie is not the same as a guest buying one. The difficult moment comes between putting it in a cart and completing checkout. If several people reach that point together, an ordering system needs a clear rule for which units are still available.
Ask whether the system can place a temporary hold when checkout begins, how long that hold lasts, and whether it releases the units after abandonment or a failed payment. Also ask how it handles two checkout attempts competing for the final unit. A temporary hold reduces the chance of promising the same item twice, but a long hold can make stock appear unavailable while guests are still deciding.
Another approach is to allocate stock only when the order is accepted. That can keep units available longer, but the guest needs a clear message if the last unit is taken before their order is accepted. Ask the provider to explain precisely what “accepted” means in its workflow and what the guest sees when availability changes.
The worksheet below uses the bakery’s 36-unit sellable cap. Each row is a separate moment in the same hypothetical batch. It assumes temporary holds count against availability and that a canceled accepted order returns to sale only after staff release it.
| Moment | Accepted units | Held units | Available units |
|---|---|---|---|
| Preorder opens | 0 | 0 | 36 |
| Orders accepted; guests checking out | 27 | 3 | 6 |
| Two held units expire | 27 | 1 | 8 |
| Four more units accepted; last hold expires | 31 | 0 | 5 |
| Two accepted units canceled and released | 29 | 0 | 7 |
Accepted, held, and available units add up to 36 in each row. The four production-buffer pies are outside that sellable cap; they are not extra units to advertise. If a cancellation occurs after the order window closes, staff can keep the released units unavailable rather than reopen sales. Record that decision so the kitchen and front counter use the same count.
If the ordering setup cannot enforce the rule you need, use a conservative manual process: limit the channels taking preorders, assign one person to update the count, and close sales before the last units are committed. Manual tracking becomes risky when orders arrive simultaneously, so consider a smaller cap or a different ordering workflow rather than relying on someone to catch every collision.
Make pickup and cancellation terms clear
Guests need to know what they are buying and when they can collect it. Show the item description, unit size, pickup location, date, and time window before checkout and in the order confirmation. If substitutions are possible, explain the choices rather than assuming a guest will accept a different item.
State the order cutoff and the cancellation deadline separately. A guest may be able to place an order until Thursday noon, while a cancellation may require a different deadline because ingredients have already been committed. Explain how to request a cancellation, who will confirm it, and what happens to any payment. Have a qualified adviser review contract or legal questions where needed.
For the bakery example, a useful guest-facing message might say: “Saturday pickup, 10 a.m. to noon. Preorders close Thursday at noon or when sold out. Contact the bakery by the stated cancellation deadline to request a cancellation.” The bakery must supply its actual deadline and payment terms before using that message.
Plan for guests who miss the window. Tell staff where to hold an uncollected order, who can authorize a later pickup, and how to contact the guest if that is part of the restaurant’s process. Do not promise an item will remain available indefinitely if food quality or storage space limits how long it can be held.
Before launch, run a simulated check of the customer journey: select multiple units, reach the last available unit, abandon checkout, and review the pickup information and confirmation wording. Use a safe test environment or a vendor-supported simulation that does not create a real payment, guest message, or courier dispatch. A simulation checks the configured flow; it does not prove every condition will work during a busy live service.
Reconcile orders with production
At the cutoff, one person should compare the accepted-order list with the inventory count and the kitchen’s production sheet. Count units, not just orders: one order for four pies consumes four units. Separate pickup dates and windows, and include any approved changes made by phone or at the counter.
For the bakery, the final worksheet row shows 29 accepted pies after two canceled units are released. If sales remain closed, the kitchen’s committed quantity is 29, not 36. The production lead can decide separately how much of the planned buffer to prepare. That decision should not create additional guest promises unless the manager deliberately reopens availability and confirms capacity.
Use this launch checklist before taking the first preorder:
- Confirm capacity: Record the batch size, sellable cap, buffer, pickup windows, and the people who approved them.
- Set the rules: Record the opening and closing times, per-order limit, inventory hold or allocation point, and cancellation process.
- Check every channel: Decide where orders may be placed and how phone or counter orders affect the same cap. If channels do not share a count, assign a single owner to reconcile them.
- Prepare the handoff: Give the kitchen a unit count by item and pickup window. Give the pickup team a list that distinguishes accepted, canceled, and changed orders.
- Handle exceptions: Assign someone to resolve failed payments, duplicate requests, ingredient shortages, and guest changes. Keep a record of each adjustment and its effect on available units.
- Close the loop: After pickup, compare prepared units with collected and uncollected orders. Use the differences to adjust the next batch’s cap or pickup staffing.
A small live service pilot can reveal practical issues a simulation cannot, such as a crowded pickup counter. Run it with a deliberately conservative cap and staff ready to intervene; do not treat it as proof that future batches will run without problems. The online ordering buying guide can help you assess the wider ordering workflow, while the direct-order contribution guide helps frame channel costs separately from batch capacity.
Use the checklist to review your current setup, then ask Fleksa about restaurant online ordering, the specific preorder controls you need, and verified US availability.
Frequently asked questions
Should a preorder cap include the production buffer?
Keep the buffer outside the sellable cap. If you plan to make 40 units and reserve four for problems, offer no more than 36 unless the production lead approves a change.
When should canceled items go back on sale?
Release them only after the cancellation is confirmed and the responsible person decides there is still time and capacity to accept another order. After the cutoff, keeping sales closed may be simpler.
Can a restaurant take preorders through more than one channel?
Yes, but each accepted unit must count against the same relevant batch limit. Ask how channels share availability; if they do not, assign one person to reconcile orders and use a conservative cap.
