Pickup vs delivery vs dine-in: choosing your first online order channel

Owners ask me which online ordering channel they should turn on first. The honest answer is "the one that matches what your kitchen and your dining room already do well." Turning on delivery before you have the bandwidth or the right kitchen flow will make every Saturday miserable. Turning on dine-in QR ordering in a fine-dining concept will offend the regulars.

Here's a tighter version of the conversation than I usually have over coffee.

The three channels

• Pickup. Customer orders through your site, drives to the restaurant, picks up at a counter or curbside. You don't touch delivery logistics at all.
• Delivery. Customer orders through your site, you deliver. Either you drive (in-house delivery) or you hand off to a marketplace driver (DoorDash Drive, UberEats Direct).
• Dine-in QR ordering. Diner sits at a table, scans a QR code, orders from their phone. Saves a server trip per table.

Pickup is the right answer for most independents on day one

It has the lowest operational overhead. You already make food. You already have a counter. The only new thing is a packaging station and a system for handing off bags without holding up the line. Margins are full menu margin (no commission, no driver fee). The ramp is gradual — you don't go from 0 to 50 orders overnight, you go from 0 to 5 to 10 to 20 over a couple months as locals figure out it's an option.

Pickup also tells you whether your kitchen can handle off-premise volume at all before you commit to the harder channels. If 10 pickup orders on a Saturday makes you miss tickets in the dining room, delivery will break you.

When to add delivery

Three signals it's time:

1. You have a stable pickup volume — say, 25+ orders a week — and you're seeing customers ask specifically about delivery.
2. Your menu travels well. Pizza, burritos, sandwiches, rice bowls — yes. Soufflé, fried fish, anything plated with sauce on top — be careful. The food has to arrive looking like food.
3. You have a 20-minute window in your kitchen flow where you can fire a delivery ticket without disrupting on-premise service. Most kitchens can. Some can't — especially open kitchens with one expediter.

First-party delivery (you driving, RestoWebMaker handles the addresses, geofencing, fees) keeps full margin. Marketplace handoff (DoorDash Drive) costs ~$8/order but expands your radius and gets you a driver instantly. Most independents start with first-party delivery in a 3-mile radius and add marketplace handoff for orders outside that.

When NOT to add delivery

If your dining room is consistently full and you're turning away walk-ins, delivery isn't a growth lever — it's a way to let your kitchen melt down trying to do two services at once. The right move is to invest in the dining room: faster table turns, better reservation discipline, maybe a second seating.

If your concept is built on the experience (omakase, tasting menu, hands-on counter service), delivery is the wrong channel and you should never have it on the menu. Your brand is what people pay for; soggy delivery undermines it.

Dine-in QR ordering — only when the math works

QR ordering has gotten a bad reputation from the post-COVID era when it was forced onto every concept regardless of fit. The truth is more nuanced: it works great for fast-casual, brewpubs, beer gardens, large-format dining where guests want to order rounds without flagging a server. It works terribly for fine dining, date-night concepts, anywhere the server is the experience.

The labor math: in a 100-seat brewpub, QR ordering can let you run 2 servers instead of 4 on a Saturday night and the guest experience improves (drinks come faster, no waiting to order another round). At 100 seats × 4 servers × $25/hr loaded × 5 hrs × 4 Saturdays a month, that's ~$10K a month in labor savings. The same math in a 40-seat fine-dining concept turns negative.

The recommended sequence

1. Launch with pickup only. Get to 25+ orders/week.
2. If your menu travels and your kitchen has bandwidth, add first-party delivery in a 3-mile radius.
3. If demand exceeds your delivery radius, add a marketplace driver handoff for outside-the-radius orders.
4. QR ordering only if your concept matches and the labor math works.

RestoWebMaker supports all three on the Essential and Pro tiers (QR and delivery on Pro). The choice of which to enable first is yours; the platform doesn't pressure you to turn them all on. You ship one, learn from it, then layer the next when the operation is ready.