Delivery and the kitchen: two services at once

At half past seven on a Friday, the dining room is full and the kitchen is in the middle of its busiest hour. Then the delivery tablet starts chiming. Six orders in ten minutes, each with a driver on the way, each wanting its food packed and ready the moment the driver walks in. The grill was already at its limit. Now it has two services to feed, and both are getting slower.

Delivery and the kitchen can work together, but only if the kitchen treats delivery as the second service it is, with its own tickets, its own packing, its own pace and a clear rule for when to stop taking orders. This guide covers why the two services clash, how to run delivery tickets beside dining room tickets, how to set up the pass and the packing, how to pace both, and when to switch delivery off. Every figure in it is an example.

The dining room and delivery make different promises. Dining room guests are promised a meal at the table, course by course, at a relaxed pace. Delivery guests are promised a meal at their door, all at once, as soon as possible. The kitchen has to keep both promises with the same cooks, the same stations and the same pass.

They also tend to peak at the same time. The busiest delivery hours, early evening and weekends, are often the busiest dining room hours too. A kitchen that copes comfortably with either on its own can be overwhelmed by both together.

And the costs of failure differ. A dining room guest who waits a little longer for a main can be looked after by a server. A delivery guest whose food sits on the pass for ten minutes waiting for a driver receives a cold meal and writes a review, without anyone in the venue ever meeting them.

Dining room tickets and delivery tickets behave differently, and the kitchen needs to read them differently.

A dining room ticket is usually coursed. Starters go first, mains are held until the table is ready, desserts come later. The kitchen paces the ticket to the table. A delivery ticket is all at once. Every dish on it needs to be ready at the same moment, packed and on the pass when the driver arrives.

That means a delivery ticket arriving in the middle of a dining room rush is not just more work; it is a different kind of work, demanding everything at once from stations that are pacing dining room courses. Kitchens that handle it well make delivery tickets instantly recognisable, so every cook knows which promise they are keeping.

Kitchen capacity is what both services share. Each station can produce only so many plates an hour, and every delivery dish uses some of that capacity, just as every dining room dish does.

Know your limits. For each station, roughly how many plates can it produce in a busy hour, and how many of those does the dining room already use on a full night? The difference is the capacity left for delivery. On a quiet Tuesday, there may be plenty. On a Saturday at eight, there may be none.

That simple calculation is the basis for everything else: how many delivery orders to accept, which dishes to offer for delivery, and when to stop.

Delivery orders usually arrive on a separate device, a platform's tablet or printer, rather than through the venue's own point of sale. That creates a practical choice: keep delivery as a separate queue, or bring it into the same queue as the dining room.

A separate queue keeps the two services apart and makes delivery easy to see, but it means someone has to read two places and decide which order comes next. A combined queue, where delivery tickets appear alongside dining room tickets at the stations, makes the kitchen's workload visible in one place, but it depends on the systems being able to share orders.

Whichever you use, make one person responsible for delivery orders during each service: accepting them, checking them and making sure their tickets reach the right stations. An unattended tablet is how delivery orders get lost.

A delivery ticket needs information a dining room ticket does not. It should say clearly that it is a delivery order, which platform or channel it came from, when the driver is expected, and any packing notes, such as sauces on the side or cutlery included.

Make delivery tickets stand out. A different colour, a clear label or a separate position on the rail or the screen helps cooks see at a glance which tickets are all-at-once. Our guide to kitchen tickets that never need a shout covers what belongs on every ticket; delivery tickets need all of that, plus the time the order must be ready.

Allergen information matters even more on delivery tickets, because there is no server at the door to double-check. Any allergy or dietary note from the guest must be on the ticket, where the cook cannot miss it.

The pass is where the two services meet, and where delivery most often goes wrong. A dining room dish leaves the pass in seconds. A delivery order needs to be assembled, checked, packed, sealed and labelled before it goes, and then it waits for a driver.

In the classic brigade de cuisine, the person calling orders at the pass kept every ticket moving; with delivery, that job now covers two services at once. Give delivery its own space at or near the pass: a packing area with containers, bags, labels, cutlery and sauces to hand. Check each delivery order against its ticket before it is sealed, the same way the pass checks a dining room plate. Our guide to order management, from table to pass covers the pass's role in more detail.

Keep finished delivery orders in a clear holding area, away from the dining room pass, so drivers can collect them without walking into the line of plates going out to tables.

Delivery timing has three parts: the time the kitchen needs to cook and pack the order, the time the driver takes to arrive, and the time the food can wait before it suffers. The aim is for food to be packed just as the driver arrives.

Most platforms let the venue set a preparation time, and some let it change that time during service. Set it honestly. A preparation time that is too short means drivers wait, or food is rushed. One that is too long means food sits on the pass, cooling, until the driver arrives, or guests choose another venue because the wait looks long.

On busy nights, increase the preparation time rather than letting orders run late. A guest told forty minutes who receives their food in thirty-five is happy; one told twenty-five who waits forty-five is not.

Ticket times, the time from an order reaching the kitchen to the food leaving the pass, are the clearest measure of whether the kitchen is coping. Measure them for both services, separately where you can.

Watch what happens to dining room ticket times when delivery orders arrive. If they rise sharply every time the delivery tablet gets busy, delivery is taking capacity the dining room needs. Watch delivery ticket times too: if delivery orders are consistently late leaving the pass, the kitchen is over its limit.

Our guide to ticket times, the only kitchen metric that moves covers how to measure them and what to look for.

The delivery menu decides which stations delivery orders load. If most delivery dishes come from the grill, delivery competes directly with the dining room's busiest station. If delivery dishes come from stations with spare capacity at the peak, the two services can run side by side.

Design the delivery menu with station load in mind. Dishes that can be prepared largely in advance, such as braises, curries and baked dishes, use little station time at the peak. Dishes that need the grill or the fryer at the last minute use a lot. Our guide to a delivery menu that is not your dining room menu covers how to choose dishes that travel and suit the kitchen.

Look at which stations are busiest when delivery orders peak, and keep delivery dishes away from them where you can.

Pacing is the habit of spreading the kitchen's work so it is never overwhelmed. In the dining room, it means not seating too many tables at once. For delivery, it means not accepting more orders than the kitchen can produce on time.

Many platforms offer ways to pace delivery: a busy setting that lengthens preparation times, a limit on orders in a period, or a pause that stops new orders for a while. Use them. A pause of fifteen minutes during the dining room peak can save both services from a backlog that would take an hour to clear.

Agree the rules in advance. For example: if dining room ticket times pass a set limit, delivery preparation time goes up; if they pass a higher limit, delivery pauses. Our guide to pacing covers so the kitchen never drowns covers the dining room side.

Sometimes the right decision is to stop taking delivery orders altogether, for the rest of a service or for certain nights. That is not failure; it is protecting the guests already in the building.

Switch delivery off when the kitchen cannot produce delivery orders on time without hurting the dining room. The signs are clear: dining room ticket times rising sharply, delivery orders leaving the pass late, drivers waiting in a queue, cooks visibly over their limit. A short pause is often enough; on some nights, a full stop is better.

Look at the numbers over a few weeks too. If delivery orders on Saturday nights consistently slow the dining room and earn little after commission, it may be better not to offer delivery on Saturday nights at all, and focus delivery on quieter nights when the kitchen has capacity to spare.

The decision to slow or stop delivery needs to belong to one person on each service, usually the head chef or whoever runs the pass. They can see the kitchen's load, the dining room's tickets and the delivery queue, and they can make the call quickly.

Give them the authority to make it without asking. A head chef who has to find a manager before pausing delivery will pause it too late. Make sure the front of house knows too, so that if a guest asks why the venue is not on the app tonight, the answer is ready.

Review the decisions afterwards. If delivery was paused often, look at whether the delivery menu, the staffing or the preparation times need to change.

Delivery adds work in the kitchen and at the pass, and that work needs people. On busy nights, the work of accepting orders, packing them and handing them to drivers can easily take one person's full attention.

Many venues give that job to a single person during the delivery peak: someone who manages the delivery device, checks and packs orders and deals with drivers. That keeps cooks cooking and the pass focused on the dining room.

Count delivery into staffing decisions. A night with a heavy delivery forecast needs more hands in the kitchen or at the pass than a night with none, even if the dining room bookings are the same.

Treat packing as a station of its own, with its own set-up and its own checklist. The packing station should have everything an order needs, containers, lids, bags, labels, sauces, cutlery and napkins, laid out before service, so packing an order takes a minute rather than five.

A packing checklist stops the small omissions that lead to bad reviews: the missing sauce, the forgotten side, the drink left behind, the cutlery not included. Check each order against its ticket and the checklist before sealing it.

Label every bag clearly with the order reference, so drivers pick up the right one, and label containers within a bag when an order contains similar-looking dishes, especially where one is for a guest with an allergy.

When delivery and the kitchen clash, both sets of guests suffer, and both leave reviews. Dining room guests notice when their mains are slow because the kitchen is packing delivery orders. Delivery guests notice when their food arrives cold because it waited on the pass.

The commonest mistakes are predictable: accepting more delivery orders than the kitchen can handle, preparation times set too short, delivery dishes that load the busiest station, no one in charge of the delivery device, and packing done by cooks between dining room tickets.

Each of these can be fixed with a decision made before service rather than during it. The aim is a kitchen where both services run at their own pace, rather than one where each slows the other.

Look back at each week's services with the numbers in front of you. On which nights did delivery orders peak? What happened to dining room ticket times at the same moments? How often were delivery orders late leaving the pass? How often was delivery paused?

Compare delivery's contribution with its cost to the dining room. If delivery orders on certain nights earn little after commission and slow the dining room, adjust: change the delivery menu, change the preparation times, pause during the peak or stop offering delivery on those nights.

Small adjustments made every week, based on what actually happened, settle the kitchen into a rhythm where both services work.

An invented bistro takes delivery orders through a platform tablet that sits at the pass. On Friday and Saturday nights, delivery orders arrive at the same time as the dining room peak, and both slow down: dining room mains take ten minutes longer than usual, and delivery orders often wait on the pass for drivers.

The bistro makes five changes. It removes its two grill-heavy dishes from the delivery menu. It sets longer preparation times on Friday and Saturday evenings. It gives one person the job of managing delivery from six until nine, at a packing station beside the pass. It agrees that if dining room tickets pass fifteen minutes, delivery pauses for a quarter of an hour. And it stops offering delivery after half past eight on Saturdays.

Within a month, dining room ticket times on weekend nights return to normal, delivery orders leave the pass on time, and complaints about cold food stop. Delivery orders fall slightly on Saturdays but rise on quieter weeknights, when the kitchen has room for them.

servearound does not take delivery or takeaway orders and does not connect to delivery platforms today, so delivery orders arrive on the platform's own device; orders on servearound's point of sale and from the menu guests open at the table are for seated tables. On the kitchen screen, those dining room orders reach each station's board oldest first, each ticket showing its age as it counts, with held courses fired when the table is ready.

Kitchen analytics then show what both services did to the kitchen: ticket times by station, ticket time by day and hour, the queue depth against ticket time and which dishes took the most kitchen minutes, so the nights and hours when delivery and the dining room collide stand out. The stations page shows how many tickets each station has live. See Order Fulfillment and Analytics.

Both services share the same stations and often peak at the same time, and delivery tickets demand every dish at once, which strains stations pacing dining room courses.

Yes. Mark them clearly as delivery, with the channel, the time the driver is expected, packing notes and any allergy information.

Either can work, but one person should be responsible for delivery orders each service, so they are accepted, checked and sent to the right stations.

Honestly, for the kitchen's real pace on that night, and longer on busy nights. Food should be packed as the driver arrives.

When dining room ticket times rise past an agreed limit, delivery orders leave the pass late or drivers queue. A short pause is often enough.

One person per service, usually the head chef or whoever runs the pass, with the authority to decide without asking.

On busy nights, often one person to manage the delivery device, pack orders and deal with drivers, so cooks keep cooking.

Set up packing as its own station, with everything to hand, and check every order against its ticket and a checklist before sealing it.

If delivery on those nights slows the dining room and earns little after commission, it may be better to focus delivery on quieter nights.

Delivery and the kitchen work together only when delivery is treated as a second service: tickets that are all at once rather than coursed, with their own marking, packing, timing and person in charge. Know how much kitchen capacity is left for delivery on each night, keep delivery dishes off the busiest stations, and set honest preparation times that grow on busy nights.

Pack at a station of its own with a checklist, hold finished orders away from the dining room pass, and agree in advance when delivery slows, pauses or stops, with one person empowered to decide. Measure ticket times for both services, review each week, and be willing to switch delivery off on the nights when it costs the dining room more than it earns.