Most retail businesses do not set out to run separate inventory systems for their website and their stores. It happens gradually - the online store gets bolted on, the POS stays where it is, and someone ends up manually adjusting stock counts at the end of each day. That works until it does not, and the moment it breaks is usually in front of a customer: an item sells in-store that was already showing as the last unit online, or an order gets placed for something that has been sitting at zero in the warehouse for a week. A single shared view of stock is not a luxury feature. It is the foundation that everything else depends on.
The single source of truth
The idea behind unified stock is straightforward: every channel - your website, your POS, your wholesale portal, your app - reads from and writes to the same inventory record. A sale anywhere decrements the same number. A receive-in anywhere increments it. There is no reconciliation step because there is nothing to reconcile.
In practice, this means choosing where that source of truth lives. For most retailers it is either the POS platform (if it has a capable inventory module) or a dedicated inventory management system that the POS and ecommerce platform both connect to. The wrong answer is treating the ecommerce platform as the source and syncing outward, because ecommerce platforms were not designed for the transactional precision that physical stores require. Getting this architecture decision right early saves a significant amount of pain later. See our notes on keeping stock accurate across multiple locations for more on how the data model needs to be set up.
Real-time sync versus nightly batch
Nightly stock syncs were the standard approach for a long time, and they are still common. They are also increasingly inadequate. A product that sells out at 9am will keep accepting online orders until the batch runs at midnight. For slow-moving, high-margin categories this might be acceptable. For anything with genuine velocity - seasonal lines, promotional items, anything with limited depth - it is a real problem.
Real-time or near-real-time sync changes the picture. When a transaction at the POS fires a stock update to the central inventory record within seconds, the website reflects the current position almost immediately. The technical requirements are not extreme - a reliable webhook or event-driven integration between your POS and your inventory layer is enough for most retailers. The harder part is usually the POS integration itself: not every POS exposes the hooks you need, and some require middleware to translate events into a format your inventory system understands.
How unified stock enables click and collect
Click and collect is one of the clearest illustrations of why unified stock matters. When a customer selects "pick up at Fitzroy" at checkout, the system needs to know not just that you have the item somewhere, but that you have it at that specific location. That requires store-level stock visibility - not just a total across all locations. If your inventory system only tracks aggregate quantities, you cannot make that promise with confidence.
A properly unified system reserves the item at the chosen store the moment the order is placed, preventing it from being sold to a walk-in customer or allocated to another online order before the pick is done. That reservation logic is a small piece of the build, but it is the piece that determines whether click and collect is a feature or a liability. There is more detail on the workflow in our article on click and collect that actually works.
The operational work behind it
Unified inventory is a technical problem, but solving it technically only works if the operational side keeps up. Stock records drift when receiving is done inconsistently, when damaged goods are not written off, when transfers between locations are not logged in the system. The software can only reflect what it is told. Retailers who get the most from a unified system are the ones who treat the stock record as a live asset - cycle counting regularly, investigating variances promptly, and training staff to process every movement through the system rather than around it.
If you are building toward a unified stock setup - whether that means integrating an existing POS with a new ecommerce platform, adding locations to an existing system, or starting from scratch - the architecture and integration choices you make early have a long tail. We work through those decisions with retailers at every stage of the build. If you are thinking through your own setup, tell us about your project and we can talk through what is likely to work for your situation.
Frequently asked questions
- What does omnichannel inventory mean for a small retailer?
- It means having one stock record that every sales channel reads from and writes to, rather than separate counts for your website and your stores. When a sale happens anywhere, the same number updates. For small retailers, this is often achieved by connecting an ecommerce platform directly to the POS or to a simple inventory management tool that sits between them.
- How often should stock sync between my online store and POS?
- Real-time or near-real-time is the right target for any product with meaningful sales velocity. Nightly syncs leave a window where you can oversell items that have already sold in-store. Most modern POS and ecommerce platforms support webhook-based integrations that can sync stock within seconds of a transaction.
- Can I use my ecommerce platform as the source of truth for inventory?
- In most cases, no. Ecommerce platforms are designed for web transactions and typically lack the transactional precision and store-level tracking that physical retail requires. A dedicated inventory system, or the inventory module within a capable POS platform, is usually a better source of truth, with the ecommerce platform reading from it.