For most kitchens, “ASAP” orders are the easy case. The ticket lands, the kitchen makes it, the driver takes it. The pace is set by the orders themselves and the only real decision is how busy you can be before you need to slow things down.

Pre-orders break that rhythm. A customer ordering at 11am for a 7pm delivery has decoupled when the order arrives from when it has to be ready. Multiply that by a few hundred customers a week and your kitchen is now managing two streams: the one walking in the door right now, and the one that’s been queued for hours. Without rules, those streams collide.

This post is about the rules. How to think about scheduling pre-orders so that they actually help operations instead of breaking them.

What “pre-order” even means in practice

There are three distinct things people call pre-orders, and they want different rules.

Same-day pre-orders. A customer orders at 10am for collection at 1pm. The order goes into the queue for the 12:45 prep slot, gets made, and gets handed over. From the kitchen’s point of view it looks a lot like an ASAP order — it just lands earlier.

Next-day or future-date pre-orders. A customer orders on Wednesday for delivery on Friday at 8pm. The order sits in a queue for two days. The kitchen has to remember it exists, account for the ingredients, and make sure it doesn’t get lost.

Recurring or scheduled bulk orders. Catering. Sunday roasts ordered Thursday for collection. Bakery pre-orders for weekend. These often come with significant lead times and need their own scheduling rules entirely.

The trouble starts when you try to handle all three with the same settings. The rules that work for “order an hour ahead for collection” fall apart when applied to “order Friday for Sunday lunch”, and vice versa.

The four levers that actually matter

Most ordering platforms give you the same handful of scheduling controls. The names vary but the levers are the same.

Prep time

How long the kitchen needs from accepting an order to having it ready. This is the single most important number on your site and most operators set it once and never look at it again.

A 15-minute prep time during lunch service when the kitchen is full is fiction. So is a 40-minute prep time on a quiet Tuesday afternoon. If your prep time can’t change with service load, your delivery times can’t either, and you’re either over-promising or padding too much.

The right approach is to set a baseline prep time that reflects a normal load, and then have something — either you or the system — adjust it when the kitchen gets busy. Five-minute increments are usually enough. Ten minutes during a sustained rush.

Order throttling (capacity per slot)

The cap on how many orders can be made per time window. Five orders per 15 minutes, or eight orders per 30 minutes, or whatever your kitchen can actually produce.

This is where most kitchens leak service quality. If you accept 12 orders in a 15-minute window when you can comfortably make 6, you don’t get 12 happy customers — you get 6 happy ones and 6 late ones, and possibly some angry phone calls. The throughput is set by the kitchen, not the website.

Throttling pushes the overflow forwards. Order 7 in a busy window gets the next available slot, not the one they asked for. That’s not a problem for the customer if the slot they get is still acceptable. It’s a problem if your platform doesn’t show them they’ve been bumped, or if they’re refusing to accept anything past 15 minutes from now.

Lead time

The minimum gap between when an order is placed and when it can be ready. Distinct from prep time because it’s about your kitchen’s queue, not the act of cooking.

A 20-minute lead time for ASAP means a customer ordering at 6:00 will be told the earliest available slot is 6:20. A 24-hour lead time on a Sunday roast pre-order means the customer can’t order one for tomorrow if it’s already today.

Lead times protect the kitchen from being ambushed. They also protect the customer from a worse outcome than a longer wait: getting their food at the time they were promised, but cold or wrong because the kitchen was forced to rush it.

Cut-off times

The deadline for placing orders for a future slot. “Sunday roast orders must be placed by 8pm Saturday.” “Catering orders require 48 hours notice.”

Cut-offs do two jobs. They give you a chance to do the prep — counting portions, ordering ingredients, planning labour. And they give the customer a clear signal that an order isn’t being made just-in-time, so they don’t show up at the cut-off expecting flexibility.

The patterns that cause most of the pain

A few specific failure modes come up again and again.

Accepting more pre-orders than the slot can hold

You’ve throttled ASAP orders to 6 per 15 minutes. Good. But the 7pm Friday slot has been accepting pre-orders all week and now it has 18 pre-orders queued up for the same 15 minutes when the dinner walk-ins arrive.

Pre-orders and ASAP orders compete for the same kitchen capacity. If your throttling rule applies to ASAP only, you’ve left the back door open. The fix is to count both streams against the same slot capacity, so the system stops accepting pre-orders for a slot once the projected load — pre-orders plus expected ASAP throughput — hits the limit.

No buffer between pre-order acceptance and the slot

The customer can pre-order until 6:50pm for a 7:00pm slot. From the kitchen’s point of view, that’s not a pre-order — it’s an ASAP order in a costume. The kitchen has 10 minutes to react and the queue management value of accepting it early is zero.

A meaningful lead time on pre-orders — even 30 minutes — turns this into actual planning. The customer who pre-ordered at 4pm for 7pm gives the kitchen real notice. The customer who pre-orders at 6:50 for 7pm is just an ASAP order and should be treated as one.

Forgetting that pre-orders exist

The classic. The Friday 8pm pre-orders were taken on Wednesday and nobody pulled them onto the screen for Friday’s service. The kitchen is making ASAP orders at full pace and the pre-orders are sitting in the queue unmade until someone notices.

This is partly a system problem and partly a discipline one. A good order management screen surfaces upcoming pre-orders as the slot approaches — 30 minutes out, then 15, then now. If yours doesn’t, you need a print-off or a glance-at-the-queue habit. Either way, somebody on every shift needs to be the person who watches the upcoming queue.

Inconsistent cut-offs across products

You set a 24-hour cut-off on Sunday roasts. You forgot to set one on the side of slow-cooked pork that takes 12 hours to prep. A customer orders a roast and a pork side together on Saturday at 11pm. The roast is fine. The pork can’t physically be made in time.

Cut-offs need to be per-product or per-category when they matter, not just per-site. The slowest item on a pre-order menu sets the cut-off for the whole order unless your platform handles them separately.

How to set the rules for different operations

The right scheduling setup depends on what kind of business you’re running. A few common patterns.

High-volume takeaway, ASAP-dominant

Most orders are “want it now”. Pre-orders are a small slice — a customer ordering at 5pm for 7pm collection, that sort of thing.

Short lead time (15–20 mins) on ASAP.
Aggressive throttling on peak slots (Friday 7–9pm).
Pre-order cut-off: same as lead time. No special treatment.
Throttling counts pre-orders and ASAP against the same slot capacity.

Bakery or café with daily prep

A lot of the day’s volume is decided the day before. People pre-order pastries for morning collection. Walk-ins fill the rest.

24-hour cut-off on pre-orders to allow morning prep.
Daily limit on pre-orders per product (you’ve only made 30 pain au chocolat, sell 30).
Pre-order slots in 15-minute windows so collection doesn’t bunch up at opening.

Catering or large-format orders

Hours of prep, special ingredients, sometimes a separate kitchen entirely.

48-hour minimum lead time, sometimes 72 for larger orders.
Daily or weekly capacity limit on catering separate from regular orders.
Cut-off times that align with your supplier ordering, not arbitrary round numbers.
A separate menu so the catering rules don’t bleed into regular ordering.

The kitchen needs to know on Saturday how many roasts to prep for Sunday.

Pre-order required for the speciality, no ASAP option.
Cut-off on Saturday evening (give yourself the morning to react to demand).
Slots in 15-minute windows from your service start to keep the kitchen flow even.
A maximum per slot that’s based on the kitchen’s plating speed, not the dining room.

What to check on Monday morning

If your scheduling is working, you’ll see it in a few numbers. None of them require fancy reporting — they come straight off your order list.

How many orders were late last week? Track the gap between promised time and actual handover. A few minutes occasionally is fine. A pattern of 10+ minute lateness on Friday nights means your throttling is too loose.
How many slots filled up and rejected orders? Some lost orders are healthy — they mean you’re protecting service quality. A lot of lost orders across many slots means your capacity settings are too tight, or you need more kitchen capacity, or both.
How many pre-orders did you have for the busiest slot, and did the kitchen know about them on time? If the answer to the second part is “we noticed when the timer hit zero”, that’s your problem.

The point of scheduling rules isn’t to make customers wait. It’s to make sure the orders you accept are the ones you can actually deliver well. Every “we’re too busy right now” is a customer you’ve lost in the short term, but every undercooked, late, or wrong order is a customer you’ve lost forever. The maths is unflattering for any operator who’s still treating order acceptance as a yes-no decision instead of a capacity-management problem.

Good scheduling is invisible to the customer. The slots they want are mostly available, the food arrives when it was promised, and the kitchen never looks like it’s drowning. That’s not luck. It’s a small set of rules, applied consistently, and reviewed often enough that they stay calibrated to how the business actually runs.

Why pre-orders break kitchens (and how scheduling rules fix it)