A product can appear available on your website at 10:01, sell through a marketplace at 10:02, and be discovered out of stock in the warehouse at 10:03. That is the commercial risk behind disconnected stock data. Knowing how to sync ERP inventory is not simply a technical exercise. It is about making sure customers, warehouse teams, finance and sales teams act on the same version of the truth.
For growing distributors, wholesalers and retailers, inventory often moves through more systems than anyone first expects: an ERP, an e-commerce platform, marketplaces, warehouse processes, courier tools and sometimes multiple legal entities. A reliable integration removes the need to reconcile those systems by hand while protecting the rules that make stock control accurate.
Start with the inventory truth you need to share
The ERP is often the natural inventory master because it holds purchasing, goods receipts, adjustments, transfers, sales orders and financial records. That does not mean every stock figure in the ERP should be published directly to every sales channel.
First, define the figure each channel needs. Physical stock is what is counted or received into a location. Available stock is physical stock less allocations, reservations, quality holds and any safety stock. A website normally needs available-to-sell stock, not the quantity sitting on a shelf before committed orders are considered.
This distinction prevents a common failure: an integration accurately transfers the wrong number. If the ERP says 100 units are on hand but 35 are allocated to trade customers and 10 are held for inspection, publishing 100 online creates a promise the business cannot keep.
You also need to decide where ownership changes. In a straightforward model, the ERP owns stock and sends availability to selling channels. The e-commerce platform and marketplaces send paid or confirmed orders back to the ERP, where stock is allocated and fulfilment begins. For more complex operations, a warehouse management system may be the source for location-level availability, while the ERP remains the financial and order-management record.
How to sync ERP inventory across every channel
A dependable inventory integration is designed around business events, not just a scheduled data export. The process should reflect what happens when stock changes and how quickly each connected system needs to know.
Map products before mapping quantities
Stock sync depends on product identity. Every sellable product, variant, bundle and pack size needs a consistent identifier across systems, usually an SKU. Do not assume product names are enough. Small variations in descriptions, capitalisation or supplier codes can cause orders and stock updates to attach to the wrong item or fail altogether.
The product mapping should also account for units of measure. A case of 12, an individual unit and a supplier pack cannot be treated as the same quantity without conversion logic. Bundles require particular care: an online bundle may reduce the component stock held in the ERP, while a pre-assembled kit may be a separate stocked item. The right approach depends on how the warehouse picks it and how finance values it.
Define the stock calculation and channel rules
Before building the connection, document the calculation that becomes the published stock value. This may include on-hand quantity, allocated orders, inbound stock, quarantined stock, stock held at third-party locations and a channel-specific buffer.
A safety buffer is useful where channels cannot reserve inventory instantly or where stock counts are subject to delay. For example, a business may choose to publish five fewer units than are currently available for fast-moving lines. That can reduce overselling, but too large a buffer suppresses legitimate sales. The figure should be based on order volume, pick accuracy and update frequency, not guesswork.
Channel rules matter too. A trade portal may be allowed to show back-order availability, while a marketplace should only receive immediately available stock. Some product ranges may be excluded by channel, such as restricted goods, made-to-order items or stock held for contract customers.
Select an update method that matches demand
There are three common approaches. Scheduled synchronisation updates stock at set intervals, such as every 15 minutes or hourly. It is often suitable for lower-volume businesses with stable demand, but it leaves a window in which two channels can sell the same final unit.
Event-driven synchronisation sends an update when a relevant transaction occurs, such as an order allocation, goods receipt, stock adjustment or warehouse transfer. This offers faster visibility and better protection for high-volume or fast-selling products, provided the ERP and connected platforms support reliable event handling.
A hybrid design is often the most practical option. Event-driven updates handle urgent changes, while scheduled checks reconcile inventory at regular intervals. This gives the business both speed and a controlled way to identify missed messages or temporary platform outages.
Send orders back quickly and consistently
Inventory sync is incomplete if sales orders only travel one way. When an order is placed online, the integration should create or update the appropriate order in the ERP, including the customer, delivery details, tax treatment, payment status, sales channel, delivery service and line items.
The ERP can then allocate stock and return fulfilment updates, including dispatch status, tracking information and cancellations where required. Without this closed loop, stock may look correct at the point of sale but drift as orders wait to be entered manually.
Duplicate protection is essential. APIs can retry requests after a timeout, and users can occasionally submit an order twice. Each transaction needs a unique external reference and logic that recognises an order already processed, rather than creating a second allocation.
Build for exceptions, not just the happy path
The best integrations expect imperfect data and operational change. A discontinued SKU, an unknown warehouse location or a temporary marketplace API failure should not silently corrupt inventory or stop all order processing.
Set up clear exception handling. Failed updates should be logged with enough detail for a team member to identify the product, source system, time, error and recommended action. Where appropriate, the integration should retry automatically. Where a commercial decision is needed, such as a missing product mapping, it should alert the right owner rather than repeatedly sending an invalid message.
It is equally important to retain an audit trail. Operations and finance teams should be able to answer practical questions: which system changed this quantity, when did it change, and did the sales channel receive the update? This is especially valuable during month-end checks, customer disputes and system migrations.
Test the rules with real operational scenarios
Testing only a standard product with plenty of stock gives false confidence. Use a controlled test environment and cover the transactions that cause stock discrepancies in real life.
Test a sale of the final available unit, two near-simultaneous orders from different channels, a partial shipment, a cancellation before dispatch, a return, a stock adjustment and a goods receipt. Test a bundle or pack conversion if you sell them. Confirm that each action creates the intended result in both the ERP and the selling channel, including timestamps and status changes.
Reconciliation should continue after launch. Compare a selected set of SKUs and channel quantities daily during the early period, then move to a frequency that reflects transaction volume and risk. A small number of exceptions may be normal; recurring mismatches are a sign that a rule, mapping or process needs correction.
Avoid the shortcuts that create stock drift
Manual spreadsheet uploads can appear cheaper than integration until order volumes rise or a key employee is unavailable. They introduce timing gaps, inconsistent product references and no reliable audit trail. They are particularly risky during promotions, seasonal peaks and new-channel launches.
Another shortcut is treating all warehouses as one location. If stock is held across multiple sites, a third-party fulfilment provider or intercompany entities, the integration must reflect which location can fulfil which order. Consolidated visibility may be useful for management reporting, but fulfilment logic needs more precision.
Finally, do not make the integration responsible for solving every underlying data issue. If stock adjustments are not authorised, goods receipts are delayed or product records are poorly maintained, automation will expose those weaknesses quickly. The solution should include clear ownership of master data and stock-control processes.
Make inventory sync part of a scalable architecture
A tailored integration can connect ERP inventory to e-commerce, marketplace, CRM and courier processes without forcing the business to replace systems that already work well. Harmonise Solutions designs these connections around the order-to-cash process, the inventory rules and the reporting needs of the organisation, rather than applying a generic connector and hoping it fits.
As the business grows, revisit the design when you add sales channels, warehouses, product ranges or entities. What worked for one webstore and one warehouse may need different reservation rules, location logic and monitoring when orders are flowing through several channels.
The objective is not merely to make stock figures move faster. It is to give every team the confidence to sell, buy, fulfil and report from data they can trust – even on the busiest day of the year.