Skip to content

Drive-thru done properly: lanes, car order, speed-of-service timers and the kitchen behind the window

In a drive-thru, the car is the unit of work and seconds are the product. Track each car through the order point, the kitchen and the window; time every stage against a target; and fix the slowest stage first.

By Wameed field teamOnboarding and support

5 min read

In short: a drive-thru runs onspeed of service. Track eachcar through its stages (at the order point → ordered → preparing → at the window → delivered, orabandoned), give eachlane its own stations and time targets, link the car to itssale and itskitchen ticket, and reviewaverage, median and 90th-percentile times per stage and per hour. In Wameed the drive-thru module (Professional plan and above) provides lanes, a live board in queue order, server-clock timers with over-target highlighting, reporting, a link to the kitchen display and an order-ready feed for a screen. It does not detect cars physically and is not an offline feature.

The customer in the car will not wait 10 minutes. Every stage you can measure, you can shorten.

The lane as a queue

A lane has an ordered set ofstations: for exampleorder point (speaker) → payment window → pickup window. A busy site may have two lanes, or two order points merging into one window.

Eachcar is a unit of work that moves through the stations:

StageMeaning
At order pointThe car has arrived and is ordering
OrderedThe sale is rung and linked to the car
PreparingThe kitchen is cooking the ticket
At windowThe car is at the pickup window
DeliveredHanded over
AbandonedLeft without completing

“A car arrives when a human says so”: the system relies on staff to mark the stage, not on sensors, so make marking part of the routine.

Speed of service (SOS)

What to time

  • Order time: arrival to order complete.
  • Kitchen time: order complete to ready.
  • Window time: at window to hand-over.
  • Total time: arrival to delivery.

Set atarget per stage per lane. Many operators aim at a total of a few minutes at peak; set yours from your own baseline and improve.

Averages lie

The average hides the worst experiences. Look at:

  • Median (p50): the typical car.
  • 90th percentile (p90): the slow tail, where complaints live.
  • Abandon rate: cars that left.

Wameed reportsaverage, p50 and p90 per stage, per lane and per hour of the day.

Live timers

The board shows each car’selapsed time per stage and highlights those over target. Timers run on theserver’s clock, so a tablet with the wrong time cannot distort them.

How the system connects

  1. The cashier rings the sale on the normal till.
  2. Attach the sale to the car; this ties the money to the car and moves it from the order point.
  3. The kitchen sees the ticket on the kitchen display with thelane and car position. Seekitchen display system guide.
  4. The window crew see the cars in queue order and the linked order numbers.
  5. An order-ready feed drives a customer or signage screen that shows ready order numbers.

Setting up a lane

  1. Create the lane and name its stations in order.
  2. Set targets for each stage.
  3. Train the crew on marking the stage changes.
  4. Place a tablet or screen at each station.
  5. Link the KDS and station printers. Seekitchen printing.
  6. Test with a rush, not a quiet hour.

Improving the slowest stage

Slow stageTypical causesFixes
OrderLong menu, indecision, poor speakerSimplify the board, a combo-first menu, a better speaker, order suggestions
KitchenBatching, poor layout, a bottleneck stationRe-route stations, pre-stage items, add a runner
WindowPayment delays, checking bags, one windowTake payment at the order point, a bag check routine, a second window
QueueToo many cars at peakTwo order points, staff a pre-order lane

Always fixthe slowest stage first; improving another does not shorten the total.

Staffing the lane

  • Order taker with a headset.
  • Cashier/window who hands over.
  • Expeditor assembling orders.
  • A runner at peak.
  • A lane lead watching the timers.

Review hourly staffing against the p90 times.

What the system does not do

  • It doesnot detect cars with sensors; staff mark stages.
  • It doesnot wire signage hardware; it offers an order-ready feed for a screen.
  • It doesnot run offline, because the lane queue is a shared resource. Keep a manual fallback. SeePOS downtime procedures.

Payments and invoices

Take card at the window or order point, with an integrated reader. Every order still needs a compliant ZATCA invoice. SeeZATCA for restaurants.

Mistakes to avoid

  • Measuring only the average.
  • Not marking stage changes.
  • Optimising the fast stage.
  • A long menu on the board.
  • No manual fallback.

Frequently asked questions

Which plan has drive-thru?

Professional and above.

Does it detect cars automatically?

No; staff mark each stage.

Does it work offline?

No; the lane queue is shared and needs a connection.

What should I measure first?

Total time per car and the p90 per stage.

  • #درايف ثرو
  • #نظام درايف ثرو
  • #مسارات السيارات
  • #سرعة الخدمة
  • #drive-thru POS
  • #drive-thru speed of service
  • #lane management

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading