Pickup, Delivery, or Dine-In: Configuring Order Types That Fit Your Restaurant

How to configure pickup, delivery, and dine-in order types for your restaurant — with practical guidance on delivery fees, minimum orders, cutoff times, and when to skip a channel entirely.

·8 min read

Not every restaurant should offer delivery. There, I said it.

I've watched operators burn through kitchen bandwidth, bleed margin on driver costs, and tank their dine-in experience trying to be everything to everyone. The restaurant across the street does pickup and dine-in only, runs 70 covers a night with a four-person line, and clears more profit than the place offering all three channels with double the headcount.

The question isn't "should I offer pickup, delivery, and dine-in?" It's "which order types make sense for my operation, and how do I configure each one so it doesn't create chaos?"

That's what this guide covers. A practical framework for deciding which channels to turn on, how to set them up, and what levers to pull so your kitchen doesn't end up in the weeds every Friday night.

Pickup: the order type every restaurant should nail first

Pickup is the foundation. It's the simplest order type to operate, the highest-margin digital channel, and the one where you have the most control. If you're just getting started with online ordering, start here. Get it right before adding complexity.

Here's what makes pickup deceptively tricky: timing. A customer orders at 6:14 PM. Your system says "Ready in 20 minutes." They show up at 6:32 and the food's been sitting at the pass getting cold. Or worse — the kitchen got slammed and food won't be ready until 6:45. Now you've got an annoyed customer at the counter checking their phone every thirty seconds.

The fix is dynamic prep time estimates, not a static "15-20 minutes" that never changes. But beyond timing, there are settings most operators skip during setup and regret later.

Minimum order amounts. For pickup, I usually recommend keeping this low or turning it off entirely. The whole point of pickup is that it's frictionless. A $5 minimum on a pickup order just irritates the person who wants a single sandwich on their lunch break. That person becomes a regular. Don't gate them.

Order cutoff times. The one most people miss. If your kitchen closes at 10 PM, you don't want orders at 9:58. A "last call" window — 20 or 30 minutes before close — gives your kitchen a clean shutdown instead of firing one more ticket while everyone else breaks down stations.

Special instructions. Turn them on. Customers want to say "extra sauce on the side" or "I have a shellfish allergy." Low-friction information that makes food better and reduces re-makes.

Tipping. Offer it, but don't be aggressive. A simple "add a tip" option with preset percentages works. Pickup customers tip less than dine-in, but regulars who feel a connection to your team do tip — around 10-15% when the option is presented well, which adds up across hundreds of orders a month.

The delivery question: honest math before you flip the switch

Delivery is where most restaurants get into trouble. Not because delivery is inherently bad — but because the economics are brutal if you don't configure it deliberately.

A 30-seat sushi restaurant in Seattle turned off delivery and saw their kitchen efficiency improve overnight. Their average delivery order was $38. After driver costs, packaging, and insurance, they netted about $4 on that order. Meanwhile, every delivery ticket occupied a station and slowed dine-in covers averaging $65 with a 22% net margin. They were losing money every time a delivery order displaced a dine-in cover during peak.

That doesn't mean delivery is always wrong. It means you need to do the math. Delivery makes sense when you have excess kitchen capacity during off-peak hours, your average order value absorbs delivery costs, and you can handle the volume without impacting dine-in. If you do offer it, the settings matter more than any other order type.

Delivery fees. Flat fee or percentage-based. Flat fees ($3-$7 depending on your market) are simpler and more transparent. Percentage-based fees work better for restaurants with high ticket variance — a 5% delivery fee feels fair on a $120 catering order but barely covers gas on a $20 order. "Free delivery" is almost always the wrong answer unless you've baked the cost into your menu prices.

Minimum order amounts. Unlike pickup, minimums on delivery are essential. A $15-$25 minimum prevents the orders that cost you money to fulfill. Nobody wins when you send a driver across town for a single appetizer.

Delivery radius and zones. A 2-mile radius in a dense urban neighborhood is very different from a 2-mile radius in the suburbs. Think about your delivery time, not your delivery distance. If a delivery can't reach the customer in 30-40 minutes, the food quality suffers and you've wasted everyone's time.

Separate delivery hours. Your delivery hours don't have to match your dine-in hours — and probably shouldn't. Consider running delivery only during off-peak windows, or cutting it off 45 minutes before close so drivers aren't racing the clock.

Dine-in digital ordering: the QR code question

Dine-in ordering went through a weird arc. Pre-2020, almost nobody did it digitally. During the pandemic, QR codes were everywhere because they replaced physical menus for hygiene reasons. By 2023, a lot of restaurants ripped them out because "people want the human experience back."

Here's my take: digital dine-in ordering isn't about replacing servers. It's about eliminating bottlenecks.

Think about the dead time in a typical dine-in experience. Customer sits down. Waits for a menu. Waits for a server. Orders. Wants another drink but can't flag anyone down. Wants dessert but the server's in the weeds. Wants to pay and it takes ten minutes.

A customer who can't flag down a server for a second drink doesn't order that drink. The table waiting twelve minutes for a check is a table you can't turn. A well-configured dine-in digital ordering option supplements the server — customers can browse the menu, reorder drinks, or add dessert without waiting. The server still runs food, makes recommendations, and provides hospitality. They just spend less time as a human order-entry terminal.

Table number requirements. You need a way to route food to the right table. The simplest approach: each table gets a QR code that embeds the table number. Customer scans, browses, orders, and the ticket prints with "Table 14" on it. No typing required. If your tables aren't numbered (communal seating, counter service), you can use location descriptors or order names instead.

Tipping for dine-in. Default tip suggestions should be at full-service levels (18%, 20%, 22%) — the server is still providing table service and creating the experience. Some operators worry digital ordering reduces tips. In my experience, it actually increases average tip percentage because the checkout screen presents it cleanly and removes the awkwardness of the check-presenter dance.

The cross-cutting settings most operators miss

A few settings span all order types. These are the ones I see misconfigured most often.

Business hours validation. Your ordering system needs to know when you're open — and enforce it. I've talked to restaurant owners who discovered their system was accepting orders at 3 AM because nobody configured the hours. Beyond basic open/close, different order types should have different hours. Maybe pickup and dine-in run 11 AM to 10 PM, but delivery cuts off at 8:30 PM. Per-type scheduling prevents kitchen overload in the final stretch.

Tipping per order type. Customize your default tip percentages per channel. Dine-in gets 18/20/22%. Pickup gets 10/15/20%. Delivery gets 15/18/20%. When defaults match customer expectations, people tip more consistently. When they feel pushy (30% suggested on a pickup order), customers hit "no tip" out of spite.

When to add or remove an order type

Your order type configuration isn't a set-it-and-forget-it decision. It should evolve as your operation changes.

Add a channel when you have consistent excess capacity during the hours it would serve. If your kitchen can handle 20% more volume between 2-5 PM, that's a natural window for delivery.

Remove a channel when it's cannibalizing a more profitable one. Turning off delivery takes courage — it feels like leaving revenue on the table. But if delivery orders slow your dine-in service during peak hours, and dine-in margins are double delivery margins, you're protecting revenue, not abandoning it.

Adjust seasonally. Summer patios mean extended dine-in hours and tighter delivery windows. A restaurant near a university might run delivery hard during the school year and dial it back over summer. The best operators treat order type configuration like a living thing. Your operations playbook should include a quarterly review of per-channel performance — volume, margin, ticket size, and kitchen throughput impact.

Frequently asked questions

Should I offer all three order types from day one?

No. Start with pickup. It's the simplest to operate, has the best margins, and lets you work out your digital ordering workflow before adding complexity. Once pickup runs smoothly, add dine-in if you have table service. Add delivery last, and only if the math works.

How do I set delivery fees without scaring off customers?

Be transparent. A flat fee between $3 and $6 is standard in most markets. Customers understand delivery costs money — what annoys them is hidden fees at checkout. Show the fee upfront, set a reasonable minimum, and make sure the total value proposition holds up. If you need to charge $8+ to make it work, raise menu prices slightly and lower the visible fee instead.

Do QR code dine-in orders actually increase revenue?

In my experience, yes — by 12-18% per table on average. The biggest driver isn't initial order size, it's add-on ordering. When a customer can scan a code and add a second drink or a dessert without flagging down a server, they do it more often. The friction of waiting for a server was silently killing incremental revenue. For a deeper look at how real-time order tracking fits into this workflow, that guide covers the operational side.

What's a good "last call" cutoff time before close?

20-30 minutes for pickup, 45-60 minutes for delivery. The delivery window is longer because you need time for prep, packaging, and transit. For dine-in, I'd stop accepting new digital orders 30 minutes before the kitchen closes — anyone already seated can still order through their server. These windows protect your closing routine without losing significant revenue.

Get your order types working for you, not against you

The restaurants I admire most aren't the ones offering every possible channel. They're the ones who picked the right channels for their operation and configured each one thoughtfully.

If you're ready to set up ordering that actually fits how your restaurant works — with per-type settings for delivery fees, minimums, tipping, cutoff times, and business hours — Deally gives you all of this out of the box. Three order types, fully configurable, with the flexibility to turn channels on and off as your operation evolves.

Start with pickup. Get it tight. Then expand from there.