Practical guide for multi-site operators.
In this guide
- Start from the rush, not from the feature list
- Questions to ask about order taking
- Delivery platforms and online orders
- Kitchen display and preparation
- Stock, recipes and food cost
- Fiscal receipts and reports
- When you have more than one location
Start from the rush, not from the feature list
Most POS demos happen in a quiet room. Your POS will be judged at lunch, with a queue at the counter, a courier waiting at the door and a new team member on the till. Before you compare features, write down what a busy hour looks like at your site: how many people take orders, where orders come from, who prepares what and who hands it over.
Then test every candidate against that picture. Ask to ring up your real menu, with your modifiers and combos, and time nothing but your own patience: if a cashier needs to search through screens for a common order, it will be slow every day.
Questions to ask about order taking
Order taking is the core of the POS. Check these points on a real device, with someone from your team, not only with the seller.
- Can a new team member take a typical order without help after a short walkthrough?
- Are modifiers, extras and combos quick to add and clearly printed for the kitchen?
- Does it handle dine-in, pickup and delivery in the same flow?
- What happens when the internet drops? Can you keep taking orders and printing fiscal receipts?
- Are discounts and staff meals controlled by role, with a record of who applied them?
Delivery platforms and online orders
In quick-service, a large part of the work often arrives from Glovo and Bolt and from your own online ordering. If those orders live on separate tablets, someone has to retype them or read them out to the kitchen, and that is where mistakes start.
Ask whether Glovo and Bolt orders and online orders land directly in the same order queue and the same sales reports as counter orders. Ask how menu changes and items that run out are kept in sync, and how cancelled or changed delivery orders show up.
Kitchen display and preparation
A kitchen display replaces paper tickets with a screen at each station. The useful questions are practical: can each station see only what it prepares, are new and late orders easy to spot, and can the screen show the steps of a recipe for people who are still learning it?
Check also how an order is marked as ready and how that status reaches the counter, the courier and the customer waiting for an online order.
Stock, recipes and food cost
A POS that only records sales tells you what you sold, not what it cost you. Look for POS and inventory management together: recipes linked to menu items, stock that goes down with every sale, goods receipt against supplier invoices and alerts for products close to expiry.
Ask to see a simple report: theoretical consumption from recipes next to what was actually received and counted. That comparison is where waste and errors become visible.
Fiscal receipts and reports
Make sure every channel ends with a correct fiscal receipt, including online and delivery orders, and that the daily sales report can be matched to the fiscal Z report of each register. If the numbers never meet, you will spend time every week explaining differences instead of fixing them.
When you have more than one location
With several sites, ask whether menus and prices can be managed centrally with local exceptions, whether you see sales and stock per location on one screen, and whether users and roles are set once for the whole network.
Finally, ask what the POS connects to: accounting, delivery platforms, payments and your other tools. A POS that exports clean data through an API keeps your options open.