How to Connect POS, Inventory and Sales Reporting Across Locations
Agree which system owns each record, then prove the connection with one store and a cross-location transfer.

Connect multi-location POS, inventory and reporting by assigning a system of record for each event, mapping item and location IDs, and reconciling one location before rollout. Test refunds, delayed receipts and cross-location transfers before relying on the consolidated report.
Key takeaways
- Use consistent item, pack and location mappings.
- Make a replay leave totals and stock unchanged.
- Track stock in transit separately until the receiving location posts it.
Where should each record come from?
POS sales and refunds → Validated sales events → Inventory movements and reporting
Inventory receipts, transfers and adjustments → Reporting
| Record | Suggested source | Fields needed to reconcile |
|---|---|---|
| Sale or refund | POS | Location, receipt and line IDs, event time, original sale ID for refunds, item, quantity and amount |
| Stock movement | Inventory system | Movement reference, location, item, signed quantity, unit and movement type |
| Product and pack mapping | Assigned catalogue owner | Canonical item ID, source item IDs, pack-to-unit conversion and effective dates |
| Reporting totals | Reporting model | Business date, currency, location, sales definitions and refresh status |
A scanner can identify a unit of sale while a supplier identifies an outer case. Keep separate identifiers and document the conversion between them. GS1 Canada GTIN packaging guide
How should the integration handle exceptions?
- Repeated sale event. Store a unique key built from the source, location and transaction-line event identifier. Replaying an import should leave quantities and totals unchanged.
- Late event. Keep the transaction time and the import time. Flag the affected business day for recalculation and show when the report refreshed.
- Unmapped item. Hold the event in a review queue until the catalogue owner confirms the mapping. Replay the held event after the correction.
- Transfer in progress. Track the send and receipt against the same transfer reference. An in-transit unit belongs in neither store's available quantity until the receiving event posts.
- Refund. Record the financial event and verify whether a separate restock event should change available stock.
What would you test before adding a location?
In a fictional trial, Store 1 sends 12 units to Store 2. Store 2 receives 11 and flags one short. The inventory report should show 11 received and one unresolved against the same transfer, with no additional sale. Next, replay one completed sale and run a refund without a restock. Check each source, the event queue and the resulting daily totals.
Run both locations through a business-day close. Record material sales and stock differences, the person responsible for investigating them, and the point at which the owner can declare a report final. Compare the cost of an integration with other options using the software selection matrix. If you have sample files or API details, bring them to an integration discussion with Wizy.
Frequently asked questions
Which system should own sales and stock in a multi-location integration?
The POS normally owns sales and financial refunds, while the inventory system owns stock movements. Define which system maintains item mappings and agree how reporting derives shared totals.
How can you avoid counting a POS import twice?
Identify each event with a stable source, location and transaction-line key. Check that replaying a completed import leaves both reporting and inventory unchanged.
Which location counts inventory during a transfer?
Track units as in transit after they leave the sending store. Add them to the receiving store’s available stock once its receipt posts, and flag any quantity that remains unresolved.
