Choosing software · 6-minute read
The POS demo checklist: test a working day before you buy
Bring sample products, test returns and closing totals, and score the evidence. A practical checklist for comparing billing software demos.
The practical answer
What should you test in a POS demo?
A useful POS demo follows one sale through payment, receipt, stock and the closing report. Then it repeats the journey with a return, an incorrect entry and an interruption. Ask your cashier to operate the software and record what actually works in the edition being quoted.
1. Bring a small, awkward basket.
A polished demonstration usually follows the easiest path. Your preparation should include the exceptions that slow your staff down. Create a sample basket with a normal item, a discounted item, a returned item and a product that needs a size, weight or serial number. Use made-up customer details.
Write down who should be allowed to change a price, approve a refund and see the closing report. Bring the exact model numbers of any printer, scanner or scale you want to reuse. A demo on the supplier’s equipment does not prove that your equipment is compatible.
2. Follow the evidence beyond the receipt.
Ask the demonstrator to show the result of each action in stock and reports. Record the software edition and device used, so the evidence can be matched to the quotation.
| Try this | Look for this evidence |
|---|---|
| Scan a basket | The right product, unit, price and quantity reach the bill. |
| Correct an entry | Staff can fix the mistake; restricted changes require the intended approval. |
| Take your usual payments | The receipt and report agree. Distinguish recording a payment from integrating with a payment provider. |
| Return part of a sale | Refund method, returned stock and the original sale remain understandable. |
| Change cashier | Permissions and shift ownership behave as agreed. |
| Count stock | The starting quantity, sales, returns and remaining quantity reconcile. |
| Close the day | Cash, non-cash payments, refunds and discounts can be explained separately. |
| Recover from a problem | The supplier demonstrates the relevant outage or restore process in a safe test environment. |
3. Score proof, not confidence.
Use four labels for every requirement: demonstrated, needs configuration, not available or not tested. A verbal “yes” belongs in the last category until there is evidence. For configuration work, ask who will do it, what it costs and how you will accept the result.
The second-cashier test
After the walkthrough, let a staff member repeat a sale, correction and return without the presenter taking over. Note where they hesitate. This is a practical way to identify training needs before a busy opening day.
If AI-assisted reports or forecasts are offered, ask which source records produced an answer, how corrections are reflected and what happens when data is incomplete. A plausible explanation is not enough to approve a purchase or stock order. Treat these as evaluation questions, not assumed Oasis POS features.
4. Match the demo to your actual setup.
For a business in India, ask the supplier to demonstrate the invoice and payment workflows relevant to your business and confirm the scope in writing. Confirm the exact edition, counter count, devices, integrations, training and service arrangements. A product name or a generic demo is not evidence of your business’s compliance.
Compare quotations against the same requirement list. A lower starting price may cover a different number of counters or a smaller setup scope. Use the first-year and renewal cost guide to ask about both initial and recurring costs.
Questions to answer before choosing
How long should a POS demo take?
Long enough to complete your agreed test cases and review the results. Set the agenda by workflow rather than a fixed number of minutes. If a critical task is skipped, arrange a follow-up before deciding.
Can you compare suppliers with the same checklist?
Yes. Give each provider the same sample basket, equipment list and must-have tasks. Record evidence for the quoted edition and keep any unresolved requirement visible.