By Raied Muheisen · Reviewed October 16, 2026. This is a buyer-run acceptance script, not a report of RitePicks hands-on product testing.
A useful POS demo proves that the quoted setup handles your business, including ordinary exceptions. Give each shortlisted supplier the same small sample catalog without private customer information. Keep the software plan, devices, app versions and unresolved questions with the proposal.
Prepare a realistic test pack
- Five to ten products: simple, variant, barcode, discount and relevant tax examples.
- Receiving: ten ordered, eight saleable on arrival and two requiring documented resolution.
- Checkout: sale, authorized discount, required tender types and a return.
- Reporting: sales, refunds, applicable taxes and tips, and settlement reconciliation.
- Disruption: internet loss, a failed peripheral and restricted staff permissions.
Identify pass-or-fail requirements before the meeting. Send the script in advance so the correct specialist and equipment are available. A known limitation can be acceptable when it fits the business; discovering it after installation is the avoidable problem.
Record the evidence consistently
| Task | Pass condition | Evidence |
|---|---|---|
| Sale | Correct item, payment and receipt | Redacted receipt and setup notes |
| Return | Stock and tender records reflect the event | Transaction record and report |
| Receiving | Saleable stock and unresolved order are explainable | Order and movement history |
| Permissions | Protected actions need authorization | Role and approval settings |
| Export | Required records open outside the product | Readable sample file |
| Outage | Behavior matches documented limits | Procedure and outstanding questions |
Use pass, conditional and not demonstrated. An untested claim is not a pass. For a conditional result, record the workaround, cost, responsible business and whether it is acceptable during the busiest shift. Keep written answers instead of relying on memory.
Checkout: prove the exception as well as the ordinary sale
Scan a product, find another by search, change quantity and apply a permitted discount. Complete the sale, then return only one line. Inspect payment, stock and reporting effects. Ask how a missing receipt is handled and what authority is needed.
Demonstrate required split tender, deposits, gift cards or store credit. Note what is unavailable offline or needs another plan. Use a cashier role rather than an administrator account: unrestricted access can conceal an awkward everyday process. If a manager is needed, show how that approval is recorded.
Inventory: require the movements to reconcile
Start with a known quantity and perform a receipt, sale, return, transfer and count correction. Inspect each event in history. Show how damaged goods remain unavailable and how partial deliveries leave a clear purchase-order record. The inventory guide includes a reproducible quantity example.
For ecommerce, test orders against limited stock using a sandbox or an approved supervised process. Inspect reservation rules, identifiers, updates and error alerts. Do not create live customer orders just to test synchronization. Confirm who handles failures spanning the store and online platform.
Hardware: name the supported configuration
Record model numbers for register, payment device, printers, scanner and cash drawer. Check connections, operating system and required adapters. Physical connectivity does not prove application support. Ask who diagnoses a fault involving several suppliers.
Print a long receipt, scan a difficult label and review the counter layout. For mobile equipment, inspect charging and backup power. A demonstration network does not establish that your store Wi-Fi or kitchen routing is reliable. Test the environment as part of implementation, with responsibility assigned.
Offline operation involves four separate claims
- Local access: can staff view products and create an order?
- Persistence: does the order survive an application or device restart?
- Coordination: can other registers or kitchen devices see it without internet?
- Card acceptance: what is stored, when is it submitted and who bears a later decline?
Request documented limits, eligible payment types and reconnection deadlines. Square’s offline-payment documentation, checked October 16, 2026, includes conditions and time limits. That is a reason to read the specific procedure, not an assertion that other POS systems behave the same way.
Do not disconnect an operating merchant system or use real cards without an authorized supervised test. Many catalog, order and inventory tasks can use sample data. Follow the provider’s instructions for live payment testing.
Restaurant add-on: route one complicated order
Create a meal with a required choice, paid modifier and preparation note. Route components, change one item and cancel another. Test an unavailable ingredient and a delayed online order. Review the kitchen, cashier and manager views.
If tables, tabs, courses or delivery are essential, make them requirements. Toast vs. Clover and Clover vs. Square help frame a shortlist; neither replaces your restaurant’s own acceptance test. Confirm which features are native, which use an app and who supports each.
Reconcile, export and make the decision reviewable
Identify reports for sales, tax, refunds and settlement, including reasons totals may differ. Export a sample catalog and transaction record, then open both outside the POS. Put any missing critical records in the decision log before signing.
Finish with passed requirements, accepted limitations and unresolved blockers. Add the total-cost worksheet and the agreement. A polished presentation is helpful, but evidence of the required workflow is what makes a purchase reviewable. Choose from the retail shortlist only after those tradeoffs are understood.