A customer places an order for a product marked “in stock.” Payment is accepted, confirmation arrives and the customer expects delivery within the advertised timeframe.
Then the warehouse discovers that the item is unavailable.
Someone needs to investigate the discrepancy, contact the customer and arrange a replacement, backorder or refund. What appeared to be a straightforward online sale becomes an exception involving several teams.
For eCommerce merchants, inventory accuracy affects customer confidence, operational efficiency and the ability to make reliable delivery promises.
Connecting the online store, warehouse and ERP can help, but the integration needs to reflect how stock moves through the business. Accurate availability depends on agreed definitions, consistent processes and systems that exchange the right information at the right time.
Understand what “in stock” actually means
Different systems can hold different inventory figures without any of them being technically incorrect.
The warehouse may record the number of units physically present. The ERP may also account for reservations, incoming purchases and stock allocated to other orders. The online store needs to know how much customers can buy.
Consider a business with 100 units in its warehouse. Thirty are reserved for existing orders, five are damaged and ten are being held as a buffer.
The quantity available to sell is 55 units, assuming those categories are separate and the business deducts all three.
Publishing the physical quantity of 100 would overstate availability. Publishing 55 gives customers a figure that reflects those commitments.
Before implementing an integration, agree on the meaning of each inventory field and which figure the storefront should use.
Assign responsibility for inventory information
An integration works more reliably when each system has a defined role.
The ERP may manage purchasing, financial inventory records and sales-order commitments. A warehouse management system may handle receiving, storage locations, picking and dispatch. The commerce platform presents availability and captures customer orders.
The exact arrangement will vary, particularly when a third-party logistics provider manages fulfilment.
Document which system owns each inventory event. Establish where reservations are created, where damaged stock is recorded and which system calculates the quantity available to sell.
Avoid allowing several systems to independently overwrite the same figure without clear rules. Otherwise, a recent warehouse update could be replaced by an older number from another source.
Ownership should extend to people as well as systems. Staff need to know who investigates discrepancies and who can approve adjustments.
Map the full inventory journey
Stock availability changes throughout a product’s lifecycle.
A purchase order is raised. Goods arrive at the warehouse. Staff check the delivery, record accepted quantities and put products into storage. Customers place orders, units are reserved, items are picked and shipments leave.
Returns, cancellations and stock transfers introduce further changes.
Each event needs an agreed effect on inventory. Receiving a supplier shipment, for example, does not necessarily mean every unit should immediately become available online. Some products may require inspection, assembly or labelling first.
Similarly, cancelling an order should release stock only when the reservation still exists and the goods have not already progressed into a fulfilment process that needs reversing.
Mapping these events exposes gaps that a simple scheduled stock upload can miss.
Connect order reservations with online availability
The point at which stock becomes reserved is a critical design decision.
If an online order is accepted but the ERP does not receive it for several minutes, another channel may continue selling the same units.
Merchants need to decide when inventory is committed and how that commitment reaches other systems. Possible triggers include order placement, payment authorisation or approval of an account order.
The appropriate approach depends on the business. Reserving stock too late can allow overselling. Holding it indefinitely for unpaid or abandoned orders can make available products appear unavailable.
Define expiry and release rules for temporary reservations. Also ensure that the same order is not deducted twice when it moves from the commerce platform into the ERP.
The systems should recognise one commercial commitment throughout its lifecycle.
Choose an update frequency that suits the business
Inventory updates can run on a schedule, respond to events or combine both approaches.
A scheduled transfer may suit a business with relatively stable stock and modest order volume. Faster updates become more important when several channels compete for limited inventory.
The decision should reflect sales velocity, stock levels and the consequence of selling an unavailable item.
A product with thousands of units and occasional sales has different requirements from a popular item with three units remaining.
Avoid describing a connection as “real time” without defining its actual behaviour. Ask how quickly changes normally appear, what happens during busy periods and how delayed messages are handled.
Even a fast integration needs a plan for interruptions. Update speed and reliability should be considered together.
Coordinate inventory across sales channels
An online store may share inventory with retail locations, marketplaces, sales representatives and wholesale accounts.
Each channel creates demand against the same stock unless the business deliberately separates allocations.
A merchant might reserve a quantity for a major customer, hold stock for physical stores or assign a portion to a marketplace. Those decisions need to appear in the availability calculation.
Otherwise, each channel can behave as though it has access to the full warehouse quantity.
Clear allocation rules are particularly important during promotions and product launches. A sales campaign can expose weaknesses that remain unnoticed during normal trading.
Test how the systems behave when several orders arrive close together and stock approaches zero. The aim is to manage the combined commitment across channels.
Account for multiple warehouses and collection locations
Total stock across the business does not always represent what can be delivered to a particular customer.
A product may be available in one warehouse but unsuitable for shipment from that location. A store may have stock on display that is excluded from online fulfilment. Transferring an item between locations may add several days.
The storefront’s availability and delivery information should reflect these constraints.
For click and collect, customers need to know whether an item is ready at their selected location or must be transferred there first.
For delivery, allocation rules should consider which locations can fulfil the order and whether splitting the shipment is acceptable.
A single “in stock” message may be too broad when the fulfilment options differ materially.
When expanding across the Tasman, these location rules also inform whether your New Zealand operation should share the Australian storefront or use a separate site.
Handle bundles, packs and units of measure carefully
Inventory errors can arise when systems represent the same product differently.
The warehouse may store individual units while the website sells cartons of twelve. A bundle may contain several components that are also sold separately. A product might be purchased by the metre but stored on rolls.
These relationships need explicit conversion rules.
If a carton contains twelve units, selling one carton should create the correct commitment in the warehouse and ERP. The integration also needs to handle partial availability and any restrictions on breaking packs.
For bundles assembled from shared components, availability depends on the required quantities of every component, alongside existing reservations.
Accurate product identifiers and units of measure are fundamental. Matching product names alone is not a reliable basis for inventory integration.
Separate incoming stock from stock ready to sell
An expected supplier delivery can support a future availability promise, but it should remain distinguishable from stock already received.
Purchase orders can be delayed, partially fulfilled or delivered with discrepancies.
If the business accepts preorders or backorders, define which incoming quantities can be offered and what timing customers should see. Explain whether a date is an estimate or a confirmed commitment.
The order process also needs to account for mixed baskets containing available and backordered products. Customers should understand whether the order will ship together or in separate deliveries.
Internally, teams need a process for revising expectations when supplier dates change.
Accurate inventory communication includes uncertainty where it exists.
Make returns part of the inventory process
A returned item should become available again only when it is suitable for resale.
The business may need to inspect its condition, confirm that components are present and decide whether it requires repackaging or repair.
Recording a refund and returning stock to saleable inventory are separate actions. Automatically treating them as equivalent can introduce inaccurate availability.
Use clear statuses for goods awaiting inspection, approved for resale, damaged or being returned to a supplier.
Apply the same discipline to failed deliveries and cancelled shipments. The system should reflect where the product is and whether it is ready to fulfil another order.
Monitor integrations and reconcile the results
An inventory connection needs more than a successful initial launch.
Messages can fail, product mappings can become outdated and systems can receive updates in the wrong order. Repeated delivery of the same event can also create errors if the receiving system applies it more than once.
Build monitoring around missing updates, rejected records and unusual inventory movements. Give staff enough information to investigate the product, location and transaction involved.
Periodic reconciliation provides another useful check. Compare system balances using the same definitions and investigate differences.
Physical stock checks remain necessary because integrations cannot independently detect an unrecorded breakage or a picking mistake.
Connected systems improve the flow of information; warehouse discipline keeps that information grounded in reality.
If discrepancies persist despite a running connector, follow our ERP integration failure and recovery guide to distinguish stale updates from mapping errors and verify the recovery.
Measure accuracy through customer and operational outcomes
Assess inventory improvements using measures that reflect the business problem.
Track orders cancelled because of unavailable stock, manual inventory corrections, fulfilment delays and customer enquiries caused by inaccurate availability.
Also review discrepancies by product and location. Repeated problems may point to packaging conversions, receiving practices or a specific integration rule.
Measure update delays and the time required to resolve failed transactions. A problem detected quickly is easier to contain than one discovered after several additional orders.
Reliable inventory gives customers a promise the business can fulfil. By connecting systems around clear ownership, consistent stock definitions and disciplined physical processes, merchants can reduce exceptions and make online availability more dependable.