System Selection
Part of POS implementation and training
Testing common sales scenarios before staff use the system
Build a short POS test sheet for routine sales, payment uncertainty, corrections and the records staff need to inspect.
Before staff serve customers on a new POS, run a short set of sales on the installed devices and record the results. Check more than the checkout screen: inspect the order, payment record, receipt and any stock or preparation handoff relevant to the sale.
Define the expected result
Choose cases from the business's actual counter work. For each, record the item or service, intended amount, payment method, staff role and expected records before running it.
Scenario / Result to inspect
- Cash sale
- Cart, cash entry, change, receipt and order.
- Card sale
- Terminal or processor result and matching order.
- Wrong item before payment
- Corrected cart and no unintended completed sale.
- Declined or unclear card attempt
- Original processor status checked before any retry.
- Return after payment
- Original order, supported refund path and stock decision where relevant.
- Business-specific handoff
- Correct kitchen ticket, booking balance or other required output.
Add discounts, split payments or online pickup only if staff will use them at opening. The list is a proposed test sheet until someone records each result.
Use the installed setup and staff roles
Run cases on the intended till, network, payment device and printer. Sign in as a cashier for cashier work and use a manager account only for approvals.
Note the location, app mode and subscription. Shopify custom POS roles apply at Pro locations, so a Pro rehearsal does not establish the same controls at Lite locations.
Separate practice orders from live charges. Shopify's test-transaction guidance recommends using cash for test purposes and says its card reader cannot process card transactions while Shopify Payments is in test mode. Choose a method supported by the actual account, label the order and account for any refund, fee or stock movement.
Follow each transaction through
After a completed case, find the order again and compare it with the customer document. For card payments, check the system that processed the charge.
With an external terminal, confirm payment in the processor or terminal before treating the POS order as paid. A manual mark alone does not confirm an external charge.
If a result is unclear, stop and locate the original transaction in the actual processor before retrying. Follow that processor's status instructions for another setup.
Record the decision
Mark each case pass, fix and rerun, or launch block. A pass requires the expected records to agree.
A fix needs an owner and a repeat check of the affected path. An essential sale or payment that cannot be confirmed blocks that path from staff use until resolved.
Record the device, staff role, time, order and payment references where available, what differed and who owns the next check. Keep the final result sheet with the opening instructions.
POS testing outcomes and actions
- Pass
- Expected records match — system ready for staff use
- Fix and rerun
- Issue identified; owner assigned; repeat test required
- Launch block
- Critical failure — cannot confirm sale/payment; must resolve before opening
