.jpg)
A useful POS demo runs your own menu, your busiest service and your payment setup, not a generic tour. Prepare a sample menu with modifiers, your EFTPOS terminal model and your ordering channels, then ask each vendor to run eight scenarios live. Score every demo on the same 1 to 5 criteria so you can compare them fairly.
You've got a shortlist and you're booking demos. This is the stage where many owners hand control of the process to the vendor, and a vendor-led POS system demo is usually a tour of the features that look best: a clean menu, a simple order and perfect connectivity.
Your service doesn't look like that. It has a table of six splitting the bill three ways, a flat white with four modifiers, and a kiosk order arriving while the printer is busy. Those are the scenarios that show whether a system will cope, and they're the ones that get skipped unless you ask.
With wage costs averaging about 40 per cent of revenue across NZ hospitality, according to the Restaurant Association, choosing the wrong system is expensive to unwind. This guide gives you a POS demo checklist, eight scenarios to ask for live, and a scorecard so you can evaluate demos side by side.
A POS demo should cover your menu and modifiers, how orders from every channel reach the kitchen, how a card payment works end to end through your EFTPOS terminal, and how the day's reporting and GST come out. If it doesn't, it's a presentation, not an evaluation.
Start with what to ask in a POS demo before you arrive: can we run this on our own menu, our busiest-hour scenario and our EFTPOS terminal? A vendor confident in the product will say yes without hesitation.
The demo should also show how your channels connect. Ask to see self-service kiosk orders and an online ordering system feeding the same kitchen queue as the counter, and ask what happens after you sign: setup, training and support. If you're assessing point of sale software, ask to see it handle your messiest order, not the tidiest.
Preparing means arriving with your own menu, your busiest-hour scenario and your payment details, so the vendor demonstrates your operation instead of theirs. An hour of preparation makes the demo far more useful. Copy this POS demo checklist and tick it off before you go.
☐ Sample menu with modifiers: your most complicated items, such as a flat white with oat milk, extra shot and extra hot, or a burger with three swaps.
☐ Peak-hour scenario: your busiest 15 minutes, including orders, staff on shift and which channels are active.
☐ Current EFTPOS terminal model: make, model and who you rent it from.
☐ Number of devices: tills, handhelds, kitchen screens, printers and kiosks.
☐ Ordering channels: counter, kiosk, QR, online and delivery apps.
☐ Current pain points: your top three problems with the system you have now.
☐ Your scorecard: print the scorecard below, one per provider.
These are the POS demo questions that matter most, framed as things to watch rather than things to hear about. Ask the vendor to run each scenario live on your menu, and compare what you see with what good looks like in the table.
Note anything the vendor skips or calls 'on the roadmap'. For the commercial terms behind what you see, read the POS contract checklist.
After the scenarios, move to the commercial questions a demo can't answer: the full cost, what's included, support hours, contract term and what happens to your data. Ask every provider the same questions and get the answers in writing.
• What is the full first-year cost, broken into software, hardware, EFTPOS, setup and training?
• Which features are in the base plan, and which are paid add-ons?
• What are the support hours and channels for a system problem during evening and weekend service?
• What is the minimum term, and what is the notice period for leaving?
• Who migrates my menu and customer data from my current system, and is there a cost?
• Can I speak to a current NZ customer with a venue like mine?
For the contract questions in full, see the POS contract checklist. For what good support looks like, see what support to expect from a POS provider.
To compare POS demos from different providers, score each one from 1 to 5 on the same criteria straight after the demo, while it's fresh. That's how to evaluate a POS system fairly: by one yardstick, not by whichever presentation felt slickest.
If you haven't settled on a shortlist yet, start by learning how to compare POS systems in NZ. Then use this scorecard for each demo. Score 1 for poor, 5 for excellent.
A demo is the time to put this guide to work. Ask Tabin to run the eight scenarios on your own menu, and ask every other provider on your shortlist for the same ones.
• Your sample menu, including your most modifier-heavy items.
• Your EFTPOS terminal make and model.
• Your list of devices and ordering channels.
• The eight scenarios and the scorecard from this guide.
When you're ready, book a demo with Tabin.
A POS system demo that doesn't use your menu, your scenarios and your payment setup is just a tour. The goal is to see how the system behaves under the conditions it will meet in your busiest service, and to compare providers on the same yardstick.
Use the checklist before every demo, run the eight scenarios live, and score each provider straight afterwards. When you're ready to put your own scenarios to the test, book a demo with Tabin.