Ask a POS supplier to process a return in a different branch and show its effect on inventory, the register session and reporting. That short exercise can reveal details missing from a demonstration that starts with a barcode scan and ends with a printed receipt. A branch system needs to connect operations, not just display an attractive sales screen.
Before the meeting, distinguish the sales and inventory application from a bank payment terminal. They may connect, but buying one does not mean the other is included. Request a list of required components, accounts and devices, then test journeys that recur in your business.
Prepare a fictional store reflecting the operation
Imagine a footwear business with two shops and a warehouse. Choose a product in two sizes and colors, with different fictional quantities in each location. Prepare cashier, branch-manager and inventory roles. Decide who can grant discounts, approve returns and adjust stock.
This is a test example, not a required design for every retailer. Change the records to fit your business. Sizes do not represent a cafe's needs, and batch tracking may introduce other cases. Avoid a demonstration in which every product has no variants and every user is an unrestricted administrator.
Start with a sale, then inspect its consequences
Have the cashier sell a specific size, trying name and barcode search when required. Review the price, variant, discount and payment method, then inspect stock at the correct location. A lower overall total is insufficient when you need availability by branch.
Ask which step reserves or deducts stock and how a cancelled, incomplete sale is handled. If payment depends on another provider, request an explanation of unresolved states instead of a confident success message when a notification is delayed.
Record results rather than impressions
| Scenario | Evidence to review |
|---|---|
| Sell a variant in branch one | A correct receipt and variant stock in the relevant location. |
| Attempt a discount outside cashier authority | Denial or an approval request with a decision record. |
| Return an item in another branch | Original transaction reference, money handling and stock destination. |
| Transfer from warehouse to shop | Separate sent, in-transit and actually received quantities. |
| Close a session with a fictional discrepancy | Expected and counted cash, the difference and review owner. |
| A limited user opens a report | Only the authorized data scope is visible. |
| Lose connectivity in a test environment | Clearly allowed and blocked functions with understandable recovery. |
Add the result, explanation and decision to each row: accepted, needs a change or excluded. A general “demo passed” must not erase a return updating the wrong stock location. You may accept a temporary manual step, but document its owner and limits.
Cross-branch returns start with an operational decision
Does the business accept returns at any branch? Does an item join that branch's stock or go to the warehouse after inspection? Who approves exchanges or refunds, and how are they linked to the original receipt? Write the business's approved policy and ask the system to represent it.
Test a partial return and an unsellable item if these are in scope. Inspect reporting, permissions and the change history. A return button does not establish every detail, and a payment provider completing a refund does not by itself prove inventory is correct.
Moving stock needs receiving evidence
Shopify POS documentation distinguishes inventory tracking and movement between locations, with some workflows requiring administration tools. This illustrates why a sales screen may not cover transfer management. Ask where a transfer is created and where staff confirm receipt in the actual product you are considering.
In the footwear example, send several fictional units and receive fewer than were dispatched. Does the difference remain visible for review, or does the system silently balance stock? Request a record showing locations, quantities, owners and state. Then try a stock count and authorized correction, preserving an explanation of the discrepancy.
Test register sessions and operational reports
Open a session with a fictional float, record cash and noncash sales, then an authorized cash movement and a return if included. At closing, inspect the expected amount, the employee's count and how the difference is recorded. Do not use real money to prove behavior that can be rehearsed with training records.
Shopify's register guide describes sessions and reports for comparing expected and counted cash. In your system, ask for definitions of each number and the effects of timing, location and returns. Clarify whether financial-system integration is included or a separate project. A sales report does not automatically establish an approved financial posting.
Offline operation is not a yes-or-no question
Ask what continues without connectivity and what requires it. Recording a sale, finding a customer, checking another shop's stock and accepting a specific payment method may have different answers. Request an agreed demonstration in a safe environment. An application opening offline does not prove that every function works without a network.
When connectivity returns, inspect synchronization, conflicts and duplicate prevention. Document device, operating-system, printer, scanner and connectivity requirements. General compatibility with a device type is not a substitute for testing the configuration your branch will use.
End with implementation deliverables
Request separate items for subscriptions, equipment, configuration, data entry, training, integration and support. Specify included locations, devices and roles, account ownership and the product's export and backup arrangements. Local invoice or receipt requirements should be checked against official sources and the business's actual situation, without assuming unverified accreditation.
The owner, branch manager and inventory lead can then decide using shared evidence. When discussing POS implementation, send the scenario and expected results. If inventory belongs to a wider platform, also review ERP services. You can choose more accurately when you see an operation's effect beyond the checkout screen.
Test references
Shopify's POS inventory documentation and cash register management guide were checked on 3 November 2026. They explain particular product functions, not availability across every system, plan or country. The footwear scenario and test sheet are original proposals, not a real customer's case. The content was prepared with AI assistance and review of its text and sources.
