What a restaurant POS actually does in 2026
A point-of-sale system started life as a cash register with a screen. In 2026, the term covers everything from a $9 tablet app to a $40,000 hardware-software-services bundle with a 36-month contract. The phrase has stretched so far it's almost useless without context.
For our purposes: a restaurant POS is the software your team uses to take an order, route it to the kitchen, and collect payment. Everything else — menu management, inventory, loyalty, online ordering, gift cards, kitchen display, payroll — is something a POS vendor might bundle or sell separately, depending on their pricing strategy.
The first thing to understand about POS selection is that vendors compete on bundling, not on the core POS feature set. The actual order-taking and payment flow has been a solved problem for a decade. Where vendors differentiate is what they bundle around it, and whether you're locked in.
The five real decisions in POS selection
Forget feature checklists. There are five decisions that determine whether you'll be happy with your POS three years from now.
- Hardware lock-in. Some vendors (Clover, Toast) only run on their hardware. Others (Vertex, Square, Lightspeed) run on any tablet or browser. Lock-in feels fine on day one and miserable on day 700 when you want to switch.
- Payment processor. Some vendors bundle processing into their POS pricing (Toast, Clover via merchant services partners). Others let you bring your own (Vertex via Stripe, Lightspeed). Bundled rates can be higher than market — calculate effective rate before signing.
- Contract length. Toast typically wants 2-3 years. Most others are month-to-month. A long contract is a vendor preventing you from leaving, not a discount.
- Add-on pricing. Loyalty, online ordering, gift cards, marketing, payroll, scheduling — each is usually a separate monthly add-on. The $69/mo plan turns into $300/mo fast if you need everything.
- Migration cost. If you've already got menu data, customer history, and gift card balances somewhere, ask what migration looks like. Some vendors charge $1,500-5,000 for migration. Some let you DIY via CSV in two hours.
POS hardware in 2026: less than you think
Five years ago, a restaurant POS rollout meant buying $1,500-2,500 terminals with proprietary firmware. In 2026, the smart move is almost always to use general-purpose tablets and Stripe-compatible peripherals.
For a typical full-service restaurant, your hardware kit is: one or two iPads (or Android tablets) per service area at $400-600 each, a receipt printer at $200-400, a cash drawer at $80-150, and a card reader at $59-449 depending on capability. Total: $1,200-3,500 for a complete two-station setup. That's a third of what proprietary terminals cost.
Stripe Terminal (the Stripe Reader S700, BBPOS WisePOS E, and Tap-to-Pay on iPhone) covers card-present payments cleanly and doesn't require you to be on Stripe's pricing tier or commit to specific software. Square Reader hardware is locked to Square Payments. Toast hardware is locked to Toast Payments. Clover is locked to Clover. Buy hardware your software can switch on, not hardware your software is forced through.
- iPads (2 stations): $800-1,200
- Receipt printer (Star TSP143IIIBI): $250
- Cash drawer: $100
- Stripe Reader S700 or BBPOS WisePOS E: $349-449
- Total for a 2-station setup: $1,500-2,000 hardware out the door
What POS software should cost
Restaurant POS software pricing has stratified into three tiers, and which tier you should be on depends on your operational complexity, not your size.
Entry tier ($0-30/month per location): Square for Restaurants, Vertex Ordering. Best for single-location restaurants under $1M annual revenue with straightforward menus. You'll lose some specialized features (advanced reporting, deep KDS integration) but gain transparent pricing and short contracts.
Mid tier ($69-150/month per location): Toast (Essentials), Lightspeed Restaurant, TouchBistro. Best for multi-location operators or restaurants with kitchen complexity (line-station routing, prep-time logic, expediter screens). Trade-off is longer contracts and bundled processing.
Enterprise tier ($300+/month per location, custom quotes): Aloha, Micros Simphony, Toast Premium. Best for chains over 20 locations or operators with heavy back-office integration needs (centralized purchasing, multi-state tax, hospitality property management). Trade-off is everything: cost, contract length, vendor lock-in, implementation timelines.
If you're at the entry tier today and you're considering upgrading, the question isn't 'do I need more features?' but 'are my current operational pain points actually solved by feature X?' Most upgrades happen because vendors push them, not because the missing feature would change the business.
The integrations that matter (and the ones that don't)
POS integration marketing is heavy on logos and light on substance. Most restaurants need fewer integrations than they think. The ones that actually move the needle:
- Accounting (QuickBooks Online, Xero, Wave). One-way nightly sync of revenue, taxes, and tips. Saves real bookkeeper time.
- Online ordering (your own storefront or a third-party app). If your POS doesn't natively handle online orders, you'll be reconciling two order streams manually. That's the single most common reason small restaurants quit a POS.
- Inventory (built-in or Restaurant365). Recipe-level deduction is rarely worth the setup time for restaurants under $2M. Category-level usage tracking is usually plenty.
- Gift cards. If you sell gift cards, make sure your POS supports them natively. Bolt-on solutions (Square Gift Cards on a non-Square POS) create reconciliation pain.
- Payroll (Gusto, ADP, Toast Payroll). Time-tracking integration with payroll matters most for operators with hourly staff and tipped wages.
Mobile POS vs counter POS: when each wins
The phrase 'mobile POS' is overused. There are actually three different mobile patterns, and they solve different problems.
Handheld order entry (server walks to table, takes order on iPhone or small tablet): wins for full-service restaurants where servers can run more tables, fewer trips between table and station, and faster ticket-to-kitchen latency. Real impact on cover counts during peak.
Tableside payment (server runs card at the table on a handheld reader): wins for fast-casual to mid-tier full-service. Reduces checkout time per table by 2-4 minutes and unlocks pay-and-go behavior. Mandatory in countries where chip-and-PIN dipping at the table is the cultural default; nice-to-have in the US.
Counter-mode POS (single station, customer-facing, no servers): wins for QSR, coffee shops, delis. The whole thing is built around throughput. You want one station that can ring up 60-100 orders an hour without slowing down.
Most restaurants don't need all three. Pick the pattern that matches your service model. A coffee shop trying to deploy handheld order entry is paying for hardware and training they don't need.
Online ordering: build-vs-buy on your POS
If your POS has native online ordering, use it. If it doesn't, you'll integrate with a third-party app like ChowNow, Toast Now, or your own website's order form — and either pay per-order commission, deal with reconciliation across two systems, or both.
The math on third-party platforms (DoorDash, UberEats, Grubhub) is a separate question. They drive incremental orders but take 15-30% commission, which destroys margin on low-ticket items. Most restaurants use them tactically (lunch hours, low-margin items only) rather than as a primary channel.
For first-party online ordering — orders directly from your own storefront — the goal is to capture customers who already know you exist and want to order without phone calls. These orders don't need to subsidize a marketplace's customer acquisition cost. If your POS includes first-party online ordering natively, that's a meaningful cost saving: $0/month vs $99-300/month for ChowNow or Olo, and a clean reconciliation flow.
Migration: what it actually takes
POS migration sounds terrifying. In practice, for a single-location restaurant, it's a half-day project if you plan it well.
What you migrate: menu items, modifiers, categories, customer list (if you have one), gift card balances (if any), staff accounts. What you don't migrate (usually): historical orders, individual receipts, raw transaction data. Those stay in your old system as a legal archive but don't carry forward operationally.
Timing: most migrations happen on a Monday or Tuesday morning during your slowest window. You run shadow operations (old POS for the morning, new POS by lunch) for one day, then commit. Don't migrate during a holiday rush or right before a busy weekend.
Cost: if your new vendor charges $1,500+ for migration, push back hard or do it yourself. Most modern POS platforms accept CSV import for menus, customers, and gift cards. A motivated owner can do their own migration in 2-4 hours.
Red flags during the sales process
Vendor sales processes are designed to surface their advantages and bury their tradeoffs. A few signals that suggest you should keep shopping:
- Refusal to share month-to-month pricing or full feature matrix in writing.
- Required hardware purchase before software pricing is finalized.
- Bundled payment processing with no quote of the effective rate at your typical ticket size.
- Demo restricted to a curated environment — won't let you bring your actual menu data.
- Reference customers all over 5 years tenure (means they can't escape; not necessarily that they love it).
- Contract language that auto-renews for 12+ months unless you cancel 90 days before the term ends.
Pulling it together: how to actually choose
POS selection isn't about picking the 'best' system. It's about picking the system that fits your operational reality and doesn't lock you into the wrong long-term path.
Start by writing down: how many locations now and projected in two years, monthly revenue, average ticket size, do you do online ordering, do you need a KDS, do you have legacy hardware you want to keep using. Take that document to three vendors. Insist on flat written pricing, not 'starts at' tiers. Compare effective payment processing rates at your actual ticket distribution, not just the published headline rate.
Then take the top two and ask them how a tenant typically leaves their platform. If they can answer cleanly — 'CSV exports for menu and customer data, your Stripe account stays on your account, hardware can be repurposed' — that's a good sign. If they hedge or change the subject, you've already learned the most important thing about that vendor.
Vertex Ordering is built for the entry-to-mid tier of this market. Flat monthly pricing, no hardware lock-in, Stripe Connect for transparent processing, month-to-month contracts. If that fits your operation, the next step is the free trial. If it doesn't, the rest of this cluster has supporting articles on specific decisions: iPad vs Android POS, cloud vs legacy systems, hardware specifics, and real pricing breakdowns by operator type.