POS inventory comparison: test purchasing, stock and returns
To compare POS inventory, follow one product from the supplier order through receiving, sale, return and transfer. A live quantity alone does not prove the purchasing workflow, cost records or staff controls your store needs. This guide supplies a test you can run and the records to check. POS Review is owned by VoVi; the test is a proposed evaluation, not a claim that we tested these providers.
Separate the layers behind an inventory checkmark
Two plans can both say inventory and solve very different jobs. Start with the layer you need, then ask whether it is included in the quoted plan, requires an add-on or is unavailable. Record where the work happens: the register, a browser back office or another product. A function in a separate application may still fit, but its cost and handoff belong in the comparison.
| Layer | Business question | Evidence to request |
|---|---|---|
| Quantity tracking | How many sellable units are at each location? | A variant-level quantity and its movement history. |
| Purchasing and receiving | What did we order, receive and still expect? | The supplier order linked to partial receipts and outstanding units. |
| Transfers | Where is stock between dispatch and arrival? | Origin, destination, quantity and an identifiable handoff. |
| Cost records | Which cost is used in the margin report? | The cost source, adjustments and treatment of returned or damaged stock. |
| Controls | Who can change a quantity or receive an order? | A staff-permission test and a traceable correction. |
What the provider documentation establishes
Sources checked on September 26, 2026 describe capabilities, not a completed test in your account. The important differences below are specific enough to verify during a trial. Confirm the product edition, country, plan and account availability before treating a feature as included.
| Provider | Documented starting point | Verification question |
|---|---|---|
| VoVi POS | VoVi’s product information includes inventory, purchase orders and stock transfers. | Can the proposed plan reproduce this test, with the required permissions and cost records? |
| Square | Its purchase-order support article covers partial receiving and specifies eligible plans with advanced inventory. | Is the required inventory capability enabled, and does the intended device support your task? |
| Shopify | Supplier purchase orders link to inventory transfers; receiving happens on the transfer. | Can staff keep the order agreement and actual receipt consistent when one changes? |
| Lightspeed Retail X-Series | Its receiving guide describes partial deliveries; the newer partial-receiving workflow may not be available on every account yet. | Which receiving workflow is available in your account, and what plan includes required landed-cost allocation? |
A reproducible test: 12 units, a split delivery and a return
Use a clearly labeled test item in a trial or test environment. Start with 12 sellable units at Store A and none at Store B. Assume no reservations, no other stock movements and whole-unit selling. Record the opening quantities before starting. If your business uses weighted products or case-to-unit conversions, add a separate test for those units rather than assuming this one proves them.
Place an order for 10 more units. Only seven arrive: five sellable and two damaged. Three remain undelivered. Keep the damaged units out of available stock and retain their separate record. The expected available quantity at Store A is now 17, not 19 or 22. The supplier record should account for five accepted, two damaged and three still outstanding; document how the platform represents those states.
Next, sell three units and return one of them in sellable condition. Transfer four available units to Store B. Inspect the transition as well as the final result: while the shipment is in transit, it must not become four additional units available at both stores. A platform can use different stock-status names, but the physical movement and sellable quantities should be explainable.
| Checkpoint | Available at A | Available at B | Other quantities to explain |
|---|---|---|---|
| Opening stock | 12 | 0 | No in-transit units |
| Five good units received | 17 | 0 | 2 damaged; 3 not delivered |
| Three units sold | 14 | 0 | Damage and outstanding order unchanged |
| One sellable unit returned | 15 | 0 | The return points to the original sale |
| Four dispatched to B | 11 | 0 | 4 in transit; not available for sale at either store |
| Four received at B | 11 | 4 | 0 in transit; 15 sellable units across both stores |
Measure what the scenario actually proves
Keep the expected result beside the observed result, with the record ID and any help required. An unexplained discrepancy is an unresolved requirement. A correctly explained difference in stock-status terminology is not automatically a failure.
The final sellable-stock check is 12 opening + 5 accepted − 3 sold + 1 returned = 15 units across both stores. The four-unit transfer changes location, not the combined sellable total. The two damaged units and three not yet delivered stay outside that available-stock total.
Ask a normal employee to repeat the permitted steps, then try an action they should not be allowed to perform. Record whether the system blocks it or requires approval. Do not change a production role merely to make a demonstration pass.
- Quantity agreement: expected versus observed available units for each item and location.
- Receiving accountability: every ordered unit is received, rejected/damaged, canceled or still outstanding.
- Movement traceability: connect each adjustment to a sale, return, receipt, transfer or documented correction.
- Cost visibility: identify the cost attached to received stock and the calculation used by the report.
- Staff repeatability: note assistance, manual re-entry and any separate application the task requires.
Compare the plan that passes, including its real cost
Move only the configurations that pass mandatory checks into the cost comparison. If a plan needs a higher tier, inventory add-on or additional device to complete the task, use that configuration’s quote. Do not price one plan and demonstrate another. Also record work that stays manual: a low subscription may still fit, but the owner should know what the team must do.
VoVi is our preferred retail value candidate when its included tools meet these requirements. Its US software is US$0 per month with its credit-card processor, subject to merchant approval, or US$99 per month per location with another processor. Supported international setups use the US$99 per-location subscription. Processing and hardware are separate. The relevant question is whether your required stock workflow is demonstrated at that price.
Keep the evidence sheet with the quote. If purchase orders, margins or transfers are important to your business, a vendor feature label is the start of the review. A test your team can explain is the more useful finish.
Sources & verification
Provider details can change. Confirm your written quote and local requirements before signing.