A POS inventory integration online store setup works when one system is the single source of truth for stock, changes flow between systems quickly through events plus a periodic safety check, and conflicts are handled by clear rules instead of luck. Get that design right and you stop overselling the last item to two customers at once.
The overselling problem
A retailer with a physical shop and an online store has one pile of stock and two places that sell from it. Say you have one blue jacket in size medium. A shopper in the shop buys it at the till while another orders it on a phone. If each system keeps its own count and they only compare notes later, both sales succeed and you are left apologising to one customer and refunding them.
The more you sell, the more often this happens, and the more it costs in refunds, wasted shipping labels and goodwill. It also pushes owners toward a hidden workaround: hold back stock for the website, so that items sit unsold online while sold out in the shop or the reverse. A well-designed integration removes the need for padding the numbers.
If you are just starting to sell online and are still choosing tools, read our beginner article on ecommerce for a small New York business first. This guide assumes you already have a point-of-sale system and an online store, and want them to agree.
POS inventory integration online store: pick a source of truth
A source of truth is the one system whose stock numbers are treated as correct when systems disagree. Every other system reads from it, or sends it changes, but never quietly maintains a competing count.
Common choices:
- The POS or inventory system is the master. This suits shops where most stock movements, such as deliveries, counts and transfers, are recorded there. The online store pulls quantities and sends orders to it. This is the most common and usually the safest choice for a retailer with a physical shop.
- The online store is the master. This fits businesses that are mostly online with a small shop attached. The POS reads stock from the store.
- A separate inventory or order-management system is the master. This fits several channels, warehouses or marketplaces. Both the shop and the website connect to it.
Choose by asking where stock is physically received and adjusted by staff, and where mistakes are most likely to be noticed. Then write the rule down: which system owns quantity, which owns price, which owns product descriptions and images. They do not have to be the same system for every field.
Sync frequency and webhooks
How often should inventory sync? As often as the cost of a stale number justifies. For a single hand-made item or a limited run, delay is costly and you want changes pushed within seconds. For a deep stock of common items, a delay of several minutes may be acceptable. There are three common patterns:
- Scheduled polling. Each system is asked for changes at an interval. It is simple and robust but always somewhat behind.
- Webhooks and events. The system that changes stock sends a notification right away. It is fast, but notifications can arrive late, twice, or out of order, so the receiver must cope.
- Both together. Use events for speed and a scheduled reconciliation as a safety net that catches anything missed. This is the pattern we recommend for most retailers.
Whatever you choose, make updates idempotent: applying the same message twice should not subtract stock twice. Send quantity changes with an identifier and timestamp, or send the full current quantity instead of a plus-or-minus delta where the platform allows it. Deltas are precise but unforgiving of lost messages; absolute counts self-heal.
Handling conflicts
Even with a source of truth, near-simultaneous events collide. Decide the rules before they happen.
- Reserve on order, not on payment. Reduce available stock when an online order is placed or a cart checkout starts, and release it if payment fails or times out.
- Keep a small safety buffer for items that sell fast in both channels, such as holding back one unit online for in-shop sales, as a deliberate setting rather than a hidden habit.
- Define what happens when stock goes negative. Either block the sale, or accept it and raise an alert for staff to resolve, such as by sourcing from another shop or backordering.
- Last-writer-wins is risky. Prefer rules based on the source of truth, plus an audit log of every stock change and which system made it.
Customers should see honest messages: in stock, low stock, backorder or unavailable, not a number that might be wrong by the time they check out.
Product data mapping
Integrations fail most often at the seam between product catalogues. Before building anything, agree how a product is identified. A stable stock-keeping code per variant, used identically in both systems, is the safest key. Do not match on product names, which change and collide.
Map these items carefully:
- Variants such as size and colour, and whether each system models them the same way.
- Bundles, kits and products sold by weight or length, which POS and web systems often handle differently.
- Prices, including sale prices and whether shop and web prices should differ.
- Tax categories, which need to be set according to guidance from your accountant or the official tax authority.
- Barcodes, units of measure, images and categories.
Run a dry import and reconcile mismatches by hand before switching anything on.
Returns across channels
A returned item must be put back into the right stock pool at the right moment. Decide whether online purchases can be returned in the shop, and the reverse, and make sure the return updates stock and financial records in one place, with the original sale linked. Not every return is sellable again: damaged items should go to a separate status, not back into available stock. Gift receipts, partial refunds and exchanges need clear rules. These cases are the ones that quietly break stock counts, so list them explicitly with your staff.
Monitoring and reconciliation
Treat the integration as something that will occasionally fail, and make failure visible.
- Log every sync message, with outcome and error details.
- Alert a named person on repeated failures, a growing queue or a long gap since the last successful sync.
- Run a scheduled reconciliation that compares quantities across systems and reports differences, ideally fixing small drifts automatically while flagging large ones.
- Do physical counts on fast-moving items regularly and feed the results back to the source of truth.
- Keep a manual override for staff to pause online sales of an item quickly.
It is worth building the reconciliation report before the sync itself, because it shows you the size of the problem from day one. If you have a vendor handling part of this, our vendor due diligence checklist includes questions on support and failure handling.
Putting it together
Write a one-page design: the source of truth for each data type, the sync pattern, the conflict rules, the identifier you match on, and who gets alerted. Build that, test with real stock movements, then expand to more products. If you want help scoping it, see our page on software development for New York businesses or get in touch.
Frequently asked questions
How often should inventory sync?
As often as a stale number would cost you. For one-off or limited items, push changes within seconds using webhooks. For deep stock of common items, minutes may be fine. Most retailers do best combining event-driven updates with a scheduled reconciliation that catches missed messages.
What is a source of truth?
It is the one system whose stock figures win when systems disagree. Others read from it or send changes to it, but never keep a competing count. For a retailer with a shop, that is often the POS or a separate inventory system. Write down which system owns quantity, price and product content.
How do I avoid overselling?
Choose a single source of truth, reserve stock when an order is placed, update systems quickly through events, and keep a deliberate safety buffer for fast sellers. Define what happens if stock goes negative, log every change, and run regular reconciliations and physical counts to correct drift.