What to ask on an EPOS demo, and what to bring
3 min read
Short answer
Bring your real menu and two or three of your most awkward orders, and ask the supplier to put them through while you watch. Then ask what happens when the internet drops, when a printer stops, when an order changes after it has gone to the kitchen, and what you will pay in a year's time, not just this month.
A demo is a performance. That is not a criticism; it is what demos are for. The person showing you the system knows its best routes and will take them. Your job is to steer them onto the roads you actually drive.
Bring three things
Your menu. Not a description of it, the actual printed menu. Ask them to show how one of your more complicated items would look on the till.
Your awkward orders. Every café has them. The breakfast with a swapped item and an included drink. The table of six who want to pay separately. The takeaway that becomes eat in. Write down two or three and ask them to put each one through while you watch.
Someone who works the counter. Owners judge a system by its reports. Staff judge it by how many taps an order takes. Bring both points of view.
Questions about a normal service
- Show me a table from sitting down to paying. How many taps?
- How does an option like oat milk or an extra shot appear, and does it change the price?
- How does a set meal with an included drink print in the kitchen and at the bar?
- How do I split a bill evenly, by item, and by a fixed amount?
- How do eat in and takeaway stay apart?
Questions about a bad day
These are the ones that tell you most, because a demo will never show them unprompted.
- The internet goes down. What stops working? Ask them to unplug it and show you.
- The kitchen printer jams. How would I know an order did not print? How do I reprint?
- An order changes after it has gone. How does the kitchen find out?
- A new starter arrives on Saturday. How do they sign in, and what can they not do?
- Something breaks at eight in the morning. Who do I call, and when do they answer?
The answers do not need to be perfect. They need to be specific. “That doesn’t really happen” is not an answer.
Questions about money
- What is the monthly cost, per what? Per terminal, per site, per user?
- What does the first year cost in total, including hardware and installation?
- What is the price after any introductory period ends?
- Do I have to change my card provider? (See our post on card machines.)
- What happens if I want to leave: notice period, and can I take my data with me?
Ask for the total in writing. A monthly figure on its own is easy to make look small.
Things to watch rather than ask
How fast the screen responds. A half-second lag on every tap becomes a long day.
Whether the person demonstrating ever hesitates. If the supplier’s own staff have to think about where something is, so will yours.
What they show you first. If it is the reports, the system may be built for the office rather than the counter.
After the demo
Before you decide, ask for a second look on a device you choose: your own phone, or a tablet you already have. If the system is meant to run in a browser, it should work there too. And ask to speak to a café of a similar size that already uses it.
Where MasaKasa sits
We are happy to be asked every question above. A MasaKasa demo runs on an ordinary tablet and phone, and we would rather put your awkward orders through than ours. The demo request form on our homepage asks a little about your café so we can show you the parts that matter to you.
The short version
Bring your menu, your awkward orders and someone from the counter. Ask what happens on a bad day, ask for the full cost of a year in writing, and judge the system by how it handles your service rather than by how good the demo looks.