Key takeaways
- Throttling means pacing online orders to what the line can cook on time, not switching ordering off at the first sign of a rush.
- Use the gentlest tool first: longer prep times, then slot caps, then pausing slow items, and only then pausing a whole channel.
- Write the triggers down in advance so any manager can act in under a minute and every channel changes at once.
- Off-premises orders now make up most restaurant traffic, so one bad night of blown quote times reaches many guests[1].
The problem throttling solves
Picture a Friday at 7:15. The dining room is full, a 30-top just ordered, and the printer is still feeding pickup tickets from your website and three delivery tablets. The online system keeps quoting 20 minutes because nobody told it otherwise. By 7:45 the shelf is empty, drivers are waiting, and guests are calling to ask where their food is.
That is what throttling prevents. It is the set of rules that tells your ordering channels how much the kitchen can take, so the quote a guest sees stays true. The stakes are larger than they used to be. Nearly 75% of all US restaurant traffic now happens off-premises[1], and the off-premises share of traffic at full-service restaurants rose from 19% in 2019 to 30% in 2024[2].
- 2019
- 2024
Source: National Restaurant Association, 2025[2]
Show the data
| Item | 2019 | 2024 |
|---|---|---|
| Full-service | 19% | 30% |
| Limited-service | 76% | 83% |
Guests are not forgiving about time. 94% of consumers say speed is critical when they order off-premises[3]. An honest 45-minute quote keeps more goodwill than a 20-minute promise that turns into an hour.
Four throttling tools, gentlest first
Most online ordering platforms and marketplace tablets offer some version of these controls. Use them in this order, because each step down removes more sales than the one before.
| Tool | What it does | Best used when | Downside |
|---|---|---|---|
| Extend prep or ready time | Pushes the quoted time out for new orders | Line is 10 to 15 minutes behind but stations are working | Some guests choose a faster competitor |
| Order or item caps per slot | Limits how many orders, or how many items, can be due in each 15-minute slot | Predictable peaks such as Friday 6 to 8 pm | Needs good setup and a realistic cap |
| Pause specific items | Hides slow or heavy items such as large platters or fried sides | One station, like the fryer or grill, is the bottleneck | Guests may abandon carts |
| Pause a channel or the whole store | Stops new orders on one app or everywhere for a set time | Equipment failure, staff shortage or the line cannot recover | Lost sales and possible ranking effects on apps |
Slot caps are the most underused tool. A cap of, for example, eight entrees per 15-minute window on your own site spreads orders across the evening instead of letting twenty land at once. Guests who wanted 7:00 see 7:15 or 7:30 and most simply take it.
Set your triggers before the rush
Throttling fails when it depends on someone noticing the problem and deciding what to do while they are cooking. Agree on triggers and actions on a calm afternoon and post them by the expo station.
Pick one measure the whole team can see
Use ticket time on the kitchen display, or the age of the oldest ticket on the rail. Everyone should be able to read it in two seconds.
Set a yellow line
For example, when the oldest ticket is more than 10 minutes past its quoted time, extend prep time on all online channels by 15 minutes.
Set a red line
For example, when the oldest ticket is more than 20 minutes late, or a station is down, pause heavy items, and pause delivery apps for 20 minutes if the line still cannot catch up.
Name who acts
Give one person per shift, usually the expo or the manager on duty, the authority and the logins to change every channel.
Set the recovery rule
Decide when to step back. For example, once the oldest ticket is back within five minutes of quote for two checks in a row, return prep times to normal.
Write these on one card. A good trigger card fits on half a page and uses the same words your team already uses on the line.
Change every channel at once
The most common throttling mistake is changing only one channel. Your website shows 45 minutes while two marketplace tablets still promise 20, and the host is quoting 25 on the phone. Guests on the fast channels arrive early and wait at the counter, and the overload continues.
- Keep a written list of every place orders come in: your site, each marketplace tablet, your app if you have one, the phone and any catering portal.
- Note where the prep-time and pause settings live in each one, and test them on a slow day so nobody hunts for menus during a rush.
- If you run several tablets, consider whether an order aggregator or POS integration lets you change prep time in one place. The guide to taming tablet chaos from multiple delivery apps covers the options.
- Tell the host the current quote every time it changes, so phone and walk-in guests hear the same time as online guests.
Mobile ordering is now ordinary for most guests: 57% of adults have recently used it, including 74% of millennials[4]. That makes the online quote the first promise many guests hear, so it has to move first.
What to say on the phone and at the counter
Throttling changes what guests hear, and staff need words for it. Keep the script short and honest.
- Phone order or status call: “Thanks for calling. The kitchen is very busy tonight, so pickup orders are running about 45 minutes. I can put that in now and text you when it is ready, or you can order online and pick a later time.”
- Guest at the counter waiting: “Your order is about ten minutes out. We slowed new online orders so we can get yours out right. Can I get you a water while you wait?”
- Driver asking about an order: “It is in the window now, about six minutes. If you have another pickup nearby, we will hold it on the shelf.”
Never quote a time you have not checked with the line in the last few minutes. If a guest wants to cancel because of the longer time, let them cancel cleanly and thank them for calling.
Example: one restaurant's throttle plan
Example: a fictional neighborhood Thai restaurant does most of its takeout between 6 and 8 pm on Fridays and Saturdays. The wok station is the bottleneck. On a busy night it can turn out about 30 wok dishes in 15 minutes before quality drops.
The owner sets a cap of 20 wok dishes per 15-minute slot on the restaurant's own ordering site, leaving room for dine-in tickets. On each delivery app, the default prep time is raised from 15 to 25 minutes on Friday and Saturday evenings only. The trigger card says that when the oldest ticket is 10 minutes late, the expo extends all channels by 15 minutes; at 20 minutes late, the large family platters are paused online.
After a month, the owner checks the reports. Late orders fell, refunds for cold food dropped, and Friday online sales were close to the month before because guests took later slots rather than leaving. Younger guests are the heaviest takeout users, with nearly 6 in 10 Gen Z and millennial adults using takeout or drive-thru at least weekly[5], so keeping them coming back mattered more than squeezing every order into 7 pm.
Common throttling mistakes
- Pausing everything at the first sign of a rush, when a longer prep time would have kept orders flowing at a pace the line could handle.
- Forgetting to un-pause. Set a timer or use the platform's timed pause so a 20-minute break does not become a lost evening.
- Capping orders but not items. Ten small orders and ten family platters are very different loads on the line.
- Ignoring scheduled orders. Orders placed earlier for 7 pm still land at 7 pm, so count them inside your slot caps.
- Letting the throttle hide a staffing gap. If you throttle every weekend, schedule another cook or simplify the menu at peak.
Review and adjust every month
- Compare quoted versus actual ready times by channel and by hour.
- Count how often the yellow and red triggers were hit, and on which nights.
- Check whether slot caps filled up, and how early.
- Look at complaints and refunds that mention lateness or temperature.
- Raise caps where the line kept up comfortably, and lower them where it did not.
If triggers fire every Friday at the same time, the problem is not a surprise rush. It is a staffing or prep plan that needs to change, or a cap that should be lower from the start. Pair this review with your expo bag-check routine so speed gains do not come at the cost of missing items.
Frequently asked questions
What does it mean to throttle online orders?
It means limiting how many online orders can land in a given window, or stretching the quoted ready time, so the kitchen is not handed more tickets than it can cook on time. Most ordering platforms offer prep-time, slot-limit and pause settings for this.
Is it better to pause online ordering or extend prep times?
Extend prep times first. Guests can still order and they see an honest time. Pause only when the line cannot recover within the extended time or when a whole station is down.
How do I throttle orders on delivery apps?
Most marketplace tablets have a busy mode or a prep-time setting, and some let you pause the store for a set period. Check each one, because names and limits differ, and change them at the same time as your own ordering site.
Will throttling hurt my sales?
It can reduce orders for a short window, but late and wrong orders cost refunds, remakes and repeat guests. A paced order you can deliver on time is usually worth more than two that arrive late.
References
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). Report: Takeout, drive-thru, delivery are more popular than ever (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑