Choosing a fast casual POS system

What a fast casual POS system has to do

A fast casual POS system has to take a heavily customized order quickly, whether it comes from the counter, a kiosk, a phone or a table, and put every one of those orders into one kitchen queue the line can read at a glance. Everything else, from reports to loyalty, matters less than whether a cashier can ring a build-your-own bowl during the lunch rush and the cook can make it without walking to the front to ask a question.

Fast casual has a particular shape. Guests order and pay up front, food is made to order with a lot of choice, and it reaches the guest by name, by number or by someone walking it to a table. That shape tells you what to weigh. Order entry speed, clean modifiers, a pay-first flow and kitchen routing carry the day. Coursing, long-running tabs and elaborate table management mostly do not apply, so do not let a demo spend its time there.

• ✓Fast entry: the items you sell most within one or two taps, with search for the rest.
• ✓Modifiers the kitchen can read: required choices, limits on how many, and defaults.
• ✓Combos priced the way your menu board prices them.
• ✓Pay-first ordering, so nothing reaches the kitchen until it is paid for.
• ✓One queue for counter, kiosk, online pickup and table orders.
• ✓A quick way to mark an item as sold out everywhere at once.
• ✓Clear answers on hardware, internet needs and how card processing is quoted.

Map your order flow before you look at any screens

Most owners shop for a POS by watching demos. A better first step is an hour with a notepad during your busiest service. You are not judging staff; you are recording how an order actually moves through your building, because that path is what the system has to support.

• ✓List every way an order arrives today: the counter, the phone, a pickup page, a kiosk, a QR code at the table, delivery.
• ✓For each one, note who keys it in, where it waits, and how the kitchen learns about it.
• ✓Note how the food finds its owner: a called name, a number on the receipt, a table marker or a pickup shelf.
• ✓Mark every point where someone retypes an order or shouts it across the room. Those are the handoffs a new system should remove.
• ✓Write down what happens when you run out of something mid-rush and how long it takes for every channel to stop selling it.

When you finish, you will have a short list of real requirements. A shop that does most of its business at the counter with a queue out the door needs different things from one where a third of the tickets come from a pickup page. Take that list to every conversation and ask each vendor to show you your flow, not their favorite screen.

Build the menu for speed, not for the printed board

Your printed menu is laid out for guests reading it. Your register menu should be laid out for a cashier under pressure. Put the items you sell most on the first screen, grouped the way people order them, and move the rarely ordered items one level down where search finds them.

Modifiers are where fast casual lives or dies. Treat sizes as a required option with a price difference rather than separate items. Give each group clear limits: choose one base, up to three toppings, any number of sauces. Set sensible defaults so the common order takes the fewest taps. Then read the result as a cook would. If a ticket says a protein, a base and five toppings in a consistent order, the line can work. If it reads like a paragraph, it slows everyone down.

Resist relying on typed notes for common requests. If guests ask for extra sauce or no onions every day, make those modifier options. Options are consistent, they show the same way on every ticket and every channel, and they can carry a price when they should. Free text ends up spelled six different ways.

Finally, agree as a team on how you 86 an item. Decide who is allowed to do it, where they do it, and who un-86s it when the delivery arrives. The goal is that the kiosk and the pickup page stop offering an item at roughly the same moment the cashier does.

One kitchen queue for every channel

The real test of a fast casual system is the kitchen during a rush, when counter orders, kiosk orders and pickup orders all land together. If those arrive on different screens or different printers, the line ends up merging them by hand, and the pickup guest who ordered first waits behind three counter guests who ordered later.

Decide how your stations split the work. A common setup sends hot line items to one screen, cold builds and salads to another, and drinks to the front. Each item should route to the station that makes it, and someone at the pass should see the whole order so it leaves complete. Choose per station whether the cook works from a screen, from paper or from both; many kitchens keep paper at one station where cooks are used to rails and run screens elsewhere.

Pickup orders need their own discipline. Set a realistic prep time for your kitchen rather than an optimistic one, and agree on a simple human rule for when to pause online ordering: for example, when the expo calls it because the oldest tickets on the board are running late. Name the person who pauses and the person who resumes, so it does not depend on whoever happens to notice.

Payments, tips and hardware: the questions to ask

Pay-first ordering suits fast casual because the kitchen only cooks what has been paid for. Ask how each channel handles that. At a kiosk, for instance, no order should exist until the card clears. At the register, ask what happens when a card is declined after the round was rung, and who clears it.

• ✓Tender: if your kiosks take cards only, keep at least one staffed register for cash, and make sure your signage says so.
• ✓Tips: ask where the guest chooses a tip at the counter, at the kiosk and online, and how tips are attributed to staff.
• ✓Internet: ask plainly what happens when the connection drops. If the answer is that the system needs internet, plan for it with a backup connection and a written fallback procedure your managers have practiced.
• ✓Hardware: ask exactly which tablets, card readers and printers are supported, and who you call when one fails.
• ✓Fees: ask how card processing is quoted for your business and what you will see on your statement, then compare offers line by line.

Where Opero fits a fast casual counter

Opero is a restaurant operating system that runs on Android tablets only. The register covers counter order entry with tiles, search, modifiers, combos, a guest name on the order, and dine-in, takeout or delivery as the order type. Charge holds the round, and the kitchen fires when payment books. The self-order kiosk is pay-first and takes cards only, with an English and Spanish menu. The pickup ordering page offers ASAP or a pickup time later the same day, with per-location prep time and cutoff, and can be paused for 15, 30 or 60 minutes or until you resume it. QR table orders are paid from the guest's phone and tagged with the table.

Every channel lands on the kitchen display, which routes items to stations, shows ticket age in colour, and lets cooks 86 an item from the header. Printing uses one supported receipt and kitchen printer, plugged by USB into the tablet or kiosk running the Opero app. Card payments need one card reader for each register or kiosk that takes cards, bought from Opero. Opero needs a working internet connection on every screen.

The Opero plan is $149 per location and Opero Full-Service is $249 per location. Inventory with recipe costing and labor scheduling with a PIN time clock are on Full-Service. Opero takes no marketplace commission; card processing is quoted per business.

A one-week test plan

Whatever system you choose, do not switch on a Friday. Use a week to prove it with your own menu and your own people.

• ✓Day one: build your ten best-selling items with their real modifiers and combos. Ring each one and read the kitchen ticket aloud.
• ✓Day two: have every cashier ring the same twenty orders from your notepad list. Watch where they hesitate and fix the layout, not the cashier.
• ✓Day three: set up stations and send test orders from the counter, a kiosk and a phone at the same time. Check that each item lands where it is made.
• ✓Day four: practice an 86 and an un-86, and confirm every channel follows.
• ✓Day five: run a declined card, a refund and a paused pickup page so managers know the steps.
• ✓Day six: unplug the internet for a minute during a quiet period and walk through your written fallback.
• ✓Day seven: run a slow shift live, collect complaints from the line and the counter, and fix them before the weekend.