How to choose a POS for your restaurant & counter.
Last reviewed 2026-05-26 · by the RetailPOS team
Restaurant POS is the most crowded category in the SaaS market and the one with the most snake oil. Toast quotes you $69/month plus a hardware lease plus locked processing; Square for Restaurants is cheaper but doesn't count the bacon; TouchBistro is built around full-service tables you don't have. The counter-service independent — burgers, sandwiches, pizza-by-the-slice, build-your-own bowls, ghost kitchens — gets squeezed in between, paying for table-service features they don't need.
This guide is for owner-operators of counter-service restaurants. It covers the workflows that decide service quality (kitchen ticket flow, 86 in one tap, modifier speed) and the ones that decide margin (recipe-driven ingredient depletion, food-cost %, tip-by-server routing). Full table service with course timing is a different category; this guide is not for that.
What this industry actually needs from a POS
Kitchen ticket flow is the daily make-or-break
Order rung at the till → ticket prints (or appears) on the line. Cook bumps when ready → cashier sees ready, calls customer name. Sounds simple; cheap POS gets the timing wrong, the ordering wrong, the bump-status wrong. Test this in the demo with 5 simultaneous orders.
86 in one tap
You ran out of bacon at 8pm. One tap on any tablet marks bacon out-of-stock; every till greys out every bacon-containing item within seconds. The alternative is yelling across the kitchen all night. This is table stakes; some POS systems still don't do it cleanly.
Recipe depletion is real margin protection
Every burger = 1 bun + 1 patty + 2 lettuce + 2 tomato + 1 box. Selling decrements all six. Without recipes, your food cost is the supplier invoice minus what's on the shelf, and the gap is unexplained margin you can't chase.
Modifier groups need real depth
A build-your-own bowl has 10+ choices across 4-5 modifier groups (base × protein × toppings × sauce × add-ons). The cashier flow has to handle this fluidly. Demo a real menu, not the salesperson's scripted demo.
Tips by server matter for payroll
Pooled vs per-server is a real policy decision. Whichever you pick, the POS has to track it correctly. The end-of-day report shows tips by server + by tender (cash vs card) so payroll declares the right amount.
Time-of-day menus are a daily reality
Breakfast 7-11, lunch 11-4, dinner 5-close. Items appear and disappear automatically. Some POS systems require manual menu swap; the good ones flip on a schedule.
Food cost % is the manager's morning number
What every plate cost in ingredients today, compared to what it sold for. Manager checks it at open; an unusual spike points to portion creep, supplier price change, or theft. The POS that surfaces this live (not on a weekly report) is the one worth paying for.
Delivery + pickup channels add complexity
UberEats, DoorDash, in-house delivery, customer pickup. Each is a channel with its own commission + flow. The POS should keep them in one revenue ledger without forcing the cashier to remember which till to ring on.
Must-have features
- ✓Kitchen ticket printer / KDS support
Tickets print to a kitchen printer (Star SP742, Epson TM-U220) or appear on a kitchen display tablet. Cook bumps when ready. The cashier sees status without walking back to the kitchen.
- ✓One-tap 86 across all tills
Out-of-stock items grey out everywhere within seconds. Comes back when you mark it back in. No menu re-edit.
- ✓Recipe BOM at item level
Every burger / sandwich / bowl carries its real recipe. Selling decrements the ingredients. Refunds restock proportionally.
- ✓Deep modifier flow
Multi-group, multi-select, with price deltas and recipe overrides. The cashier UI surfaces every level of the build within taps.
- ✓Tip pool + per-server tip routing
Configurable per shop. Server attaches to the ticket at open; tips track to them by tender type at close.
- ✓Time-of-day menu scheduling
Breakfast / lunch / dinner menus visible by hour. Tills follow automatically; no manual swap.
- ✓Food cost % live on manager dashboard
Today's sold items × their recipe cost vs revenue. Manager checks at open; flags spikes within hours, not weeks.
- ✓Multi-channel support (in-store + delivery + pickup)
Channels as first-class on the order. Reports break revenue + food cost down per channel.
- ✓Bring-your-own payment processor
Stripe (or alt) account stays yours; processing rate is yours to negotiate. Avoid POS systems with mandatory in-house processing.
Nice-to-haves
- +Customer-facing display
A second screen at the counter showing the order, the total, and the tip prompt. Lifts tip-take noticeably; some staff find it pushy. Tenant configurable.
- +Order-ahead via QR / phone
Customer scans a code at the table or street; sends order to the kitchen. Reduces counter-line pressure. Useful at high-throughput sites; overkill at slower ones.
- +Loyalty per customer
Repeat-customer tracking + earn-on-sale points. Niche-dependent — coffee + lunch counter benefit; dinner-only place doesn't.
- +Reservation calendar (if part-table)
Some counter shops have a few sit-down tables for groups. A light reservation calendar is enough. Full table service is a different category.
- +Inventory countdown by menu item
“Only 4 burgers left” on the cashier UI based on real-time stock. Drives staff to push other items + avoids overselling.
Buying traps to avoid
- ⚠Built for table service, sold for counter service
Toast, TouchBistro, Squirrel — all built for full table-service with course timing, table maps, server stations. The counter-shop flow works but you pay full price for features your order line never uses. Pick a POS designed for counter / quick-service from day one.
- ⚠Processing locked at high rates
Toast Payments at 2.49% + 15¢. Square at 2.6% + 10¢. On $30K monthly card volume, the rate difference between Toast and your own Stripe at 2.2% is ~$87/month — a chunk of net. Bring your own processor.
- ⚠Hardware lease at $80-120/month per terminal
Toast offers terminals at $0 down with a multi-year contract. Math out the total over 3-5 years; it's usually 2-3× the buy-it-outright price. Avoid.
- ⚠KDS as a paid add-on
Kitchen display systems are often priced as a $35-50/month/screen add-on. For a counter shop with one kitchen display, this is the cost of an entire employee shift per year. Look for a POS that includes the KDS in the base plan.
- ⚠Food-cost reporting that lags 24 hours
Some POS systems batch-compute food cost overnight, so today's morning manager sees yesterday's number. Live food cost is the only useful kind; if it's a day late, by the time you spot a spike the damage is done.
How to choose your restaurant & counter POS
- 1Decide counter vs full table service
If your menu is mostly “order at counter, food brought out or picked up,” counter-service POS is for you. If your servers take orders at tables with course timing and split-checks per table, table-service POS is different. Buying the wrong category costs more than features missed.
- 2List your menu honestly with modifier depth
A 15-item menu with 4 modifier groups per item is more like 200+ unique line variants. Demo each POS on your actual menu, not the salesperson scripted one. The cashier-side speed on YOUR menu is what matters.
- 3Time 5 simultaneous orders in the demo
Rush-hour stress test: 5 customers in a row, each ordering a build-your-own with modifiers. Time end-to-end. If it lags, your Friday rush hates you.
- 4Walk the kitchen ticket flow
In the demo: ring an order. Watch the ticket print or appear on the KDS. Have the cook bump it. Watch the status flow back to the cashier. Time the round-trip. If it takes more than 2 seconds, every ticket bleeds time at peak.
- 5Test the 86 workflow
On the demo: mark bacon 86. Try to ring a bacon-containing item. Confirm the bacon item is greyed out AND every burger that contains bacon is greyed out. Restore bacon. Confirm everything comes back. This catches half-baked 86 implementations.
- 6Set up one real recipe and check the math
In the demo: set up a burger with its recipe (bun, patty, lettuce, etc.). Sell one. Check the stock ledger: did each ingredient decrement correctly? Refund the burger; did each ingredient restock? If not, recipes don't actually work.
- 7Check the food-cost dashboard
Demo: ask to see the live food-cost % dashboard. Confirm it updates within minutes of a sale, not at end-of-day. A 24-hour-lagged food cost is a 24-hour blind spot on your margin.
- 8Calculate the real monthly cost over 3 years
Add: monthly plan + per-transaction fee × your volume + processing rate × your volume + KDS add-on + hardware lease. Compare to the bring-your-own-Stripe + flat plan alternative. Decide on the 3-year cost, not the marketed monthly.
Glossary
- KDS
- Kitchen Display System. A tablet (or printer) at the line where orders appear. Cook bumps each ticket when ready; the bumped status flows back to the cashier.
- 86
- Restaurant jargon: out-of-stock. “86 the bacon” means stop selling bacon. A POS should make this a one-tap action that propagates to every till.
- Modifier group
- A set of choices attached to an item. Build-your-own bowls typically have 5+ groups (base, protein, veg, sauce, extras).
- Recipe BOM
- The ingredient breakdown at the item level. Selling 1 burger decrements 1 bun + 1 patty + 2 lettuce + 1 box from stock.
- Tip pool
- An end-of-shift redistribution where tips collected across all tickets are split among all servers (and sometimes back-of-house) by hours worked or a formula.
- Per-server tip
- The alternative to pooling: tips track to the specific server attached to each ticket and pay out to them.
- Food cost %
- The cost of ingredients consumed divided by revenue, expressed as a percentage. Healthy counter-service is typically 28-35%; tracking it daily catches creep.
- Channel
- The path the order came from — in-store, online, delivery (UberEats / DoorDash), pickup. Each has its own commission and reporting line.
- Bump (a ticket)
- Marking a kitchen ticket as “ready.” The cashier (or KDS screen) shows the next ready order; cook moves to the next pending.
- Z-report
- The end-of-shift cash-and-card reconciliation: opening float, sales by tender, tips by server, expected vs counted, variance.
Frequently asked
- Does it print to a kitchen printer like Toast does?
- Yes — Star SP742ME impact printer on the line, Star TSP143 thermal up front. Tickets print on send-to-kitchen; the cook bumps when ready. No KDS subscription, no per-screen fee — included.
- How does the 86 workflow work?
- One tap on any tablet marks the item out-of-stock; every till greys it out within a second. No menu re-edit, no restart. Comes back at the next intake.
- Can we run a breakfast + lunch menu off the same till?
- Set hours per category — breakfast menu visible 7-11am, lunch 11-4pm. Tills follow automatically. Same configuration for daily soup, weekly chef's special, etc.
- Tips by server — how does that land on payroll?
- Attach a server to each ticket at open. End-of-day report shows tips by server, hours worked, gross sales rung. Export to your payroll provider as CSV; no built-in payroll today.
- What does it cost compared to Toast?
- $29/store/month Starter, $69/store/month Pro — flat. Bring your own Stripe account (lower processing) and your own hardware. A typical single-location counter shop saves $80-150/mo vs Toast plus a few percentage points on processing.
Ready to look at the product side of this? See the restaurant & counter pack →
Open your restaurant & counter in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.