Updated 2026-11-18 · Research-based guide · Includes a practical decision worksheet
Retail technology has to work when a customer is waiting. A polished checkout demo is only one part of the evaluation. Test the complete movement from a product record to a sale, payment, stock change, return, and accounting record before committing to a system.
Start with a clean item catalog
Define SKU, variation, description, price source, tax configuration owner, and stock location. Distinguish similar items in a way employees can understand. GS1 US explains how product variations affect barcode identification. Check your requirements with suppliers and sales channels before printing labels; an internal SKU and a globally recognized product identifier are not automatically the same thing.
Write a transaction test pack
Include a normal sale, a discount, a partial return, a damaged item, a receipt lookup, and an item with no readable label. Use a test environment or the vendor’s approved demonstration process. Decide the expected stock and payment results in advance. Staff should be able to explain each movement rather than accept whatever totals appear on a screen.
Review payment handling with the right parties
Ask the payment provider and acquiring bank which responsibilities remain with your store and which are handled by their service. The PCI Security Standards Council publishes merchant resources on protecting payment data. Do not assume a device, software subscription, or outsourced checkout eliminates all merchant obligations. Avoid putting live payment credentials into casual demonstrations or staff training files.
Test a realistic return
Imagine a customer buying two differently sized shirts and returning one through another register. Check the original transaction reference, item variation, refund destination, stock condition, and permission required. Then inspect the exported accounting data. This is a proposed evaluation scenario, not a claim about any particular point-of-sale product.
Plan for a connection or device failure
Ask what “offline mode” actually supports and what it does not. Confirm the payment provider’s conditions and the risk your business would accept. Staff need clear instructions for a failed terminal, duplicate-looking payment, or interrupted return. A recovery process should tell them whom to contact and what record to preserve without improvising unsafe payment handling.
Compare staff effort and ongoing costs
Include hardware, payment processing, subscriptions, support, training, label supplies, and integration work. Measure time to complete and correct the test pack, not just the speed of a normal sale. See business systems planning for a roadmap and operations and supply-chain technology for inventory handoffs beyond the counter.
Questions readers ask
Can I compare systems using one ordinary sale?
That misses important failure and exception cases. Include returns, corrections, permission limits, and exports in a repeatable test pack.
Who should join the evaluation?
Include a cashier, a stock owner, the person responsible for finance, and the party responsible for payment configuration and support.
Put this guide into practice
Test a checkout sale, declined payment, return and stock correction using the store’s approved test environment. Record what staff see and which records change. Include the shift handoff when a transaction needs a supervisor.
| Check | Evidence to record |
|---|---|
| Staff action | Observation, source or test result; responsible person; follow-up date. |
| Record updated | Observation, source or test result; responsible person; follow-up date. |
| Recovery path | Observation, source or test result; responsible person; follow-up date. |
This is a proposed exercise using illustrative circumstances, not a report of a test or visit performed by our publication.
Sources and further reading
- GS1 US: identifying product variations with barcodes
- PCI Security Standards Council: merchant resources
Source pages checked November 16, 2026. The planning examples and checklists are editorial suggestions, not reported product tests or guaranteed outcomes.
Published by Sadddam Hussain. Research-led guidance for US readers. Read our editorial standards.
