Ecommerce Warehouse Management Integration: How Stores Connect With WMS Platforms
How to integrate an ecommerce store or OMS with a warehouse management system: order release, waves, picking and packing events, short picks, stock movements, receiving, shipping and reconciliation.
Quick answer
A WMS integration releases orders from your store or OMS to the warehouse, receives events as orders move through picking, packing and shipping, and reports every stock movement (receipts, putaway, adjustments, counts, transfers, damages) back to the system that calculates availability. Design for events, not just final states: short picks need re-sourcing, cancellations must stop work in progress, and multi-package shipments need tracking per parcel. Reconcile stock with scheduled snapshots and alert when the store and warehouse disagree.
Where This Fits
When fulfilment is outsourced, the integration is with a 3PL, covered in fulfilment integration. System boundaries between order, inventory and warehouse systems are in OMS vs IMS, and choosing which warehouse fulfils each order is in distributed order management.
What a WMS Owns
A WMS knows things nobody else does: which bin holds which stock, which orders are in which wave, who picked what and what is on the dock waiting for the carrier. It should own these operational details. Your store or OMS should own the customer order, promises and communication. The integration exchanges just enough between them.
| Data | Usually owned by | Shared with |
|---|---|---|
| Customer order and promise | Platform or OMS | WMS (as fulfilment request) |
| Bin locations and pick paths | WMS | Nobody else |
| On-hand stock per warehouse | WMS | IMS, ERP or OMS |
| Available to sell | OMS, IMS or platform | Sales channels |
| Shipment and tracking | WMS (with carrier) | OMS, platform, customer |
| Inventory value | ERP | Finance |
Order Release and Waves
Orders leave the store or OMS as fulfilment requests. The WMS groups them into waves or batches by carrier cut-off, priority, zone or order profile. The integration should send priority information (express service, promised date) so the WMS can plan, and receive status events back: released, in wave, picking, packed, shipped. Customer service needs these statuses to answer 'can I still change my order?'.
Picking, Short Picks and Substitutions
A short pick means the stock record was wrong. The WMS should report it immediately with the line and quantity, adjust the location's stock, and let the OMS decide: re-source from another location, ship what is available and backorder the rest, or contact the customer. Substitutions should only happen under rules the customer agreed to, as in grocery. Repeated short picks on the same SKU or location should trigger a cycle count.
Packing and Shipping
Pack verification by scanning reduces mis-ships. At packing, the WMS or a shipping system selects carton size, prints labels and records package weights and dimensions. Ship confirmation must include each package's carrier, tracking number and contents, so partial and multi-parcel shipments are represented accurately in the store and in customer notifications. Carrier details are in shipping integration.
Connecting your storefront to a warehouse system?
ZSpace Labs can design the event contract between your platform, OMS and WMS so statuses, stock and tracking stay consistent.
Stock Movements and Receiving
Every movement that changes sellable stock should produce an event: receipts against purchase orders or ASNs, putaway completion, adjustments, damages, cycle count corrections, transfers between warehouses and returns restocked. Send events with movement type, SKU, quantity, location and reason, so the receiving system can update availability and finance can value the change. Stock received but not yet put away should not be sellable.
Reconciliation
Events get lost and systems drift. Schedule full stock snapshots from the WMS, compare them with the expected position in the OMS or IMS, and alert on differences above a threshold. Investigate patterns: a SKU that drifts every week usually has a process problem, such as bundles, unit-of-measure mismatches or returns booked in the wrong place.
Integration Patterns
- Events over queues for status and stock movements; see event-driven architecture
- Idempotent processing with event IDs and sequence handling for each SKU and order
- Periodic snapshots for correction
- Shared identifiers: SKUs, units of measure and order numbers agreed up front
- Dead-letter handling and alerts for failed messages
- Middleware or an integration platform when several systems are involved
Peak Season Considerations
During peaks, order volume, wave sizes and stock changes all spike. Load test the integration at expected peak volumes, check API rate limits on both sides, decide in advance which updates can be batched, and agree a manual fallback (for example, file-based order release) if the integration fails during a sale.
Advantages and Limitations of Direct WMS Integration
| Advantages | Limitations |
|---|---|
| Real-time view of picking, packing and shipping | More events to process and monitor |
| Accurate stock from the system that counts it | WMS data models vary; mapping takes effort |
| Faster handling of short picks and exceptions | Requires agreed identifiers and units across systems |
| Better customer status updates | Peak loads stress both sides of the integration |
| Less manual reconciliation | Changes in either system need coordinated releases |
How to Integrate a WMS Step by Step
- 1. Agree data ownership between platform, OMS, IMS or ERP and WMS
- 2. Align identifiers and units of measure for every SKU and bundle
- 3. Define the event list: order statuses, short picks, packages, stock movements, receipts
- 4. Choose integration patterns: queues for events, snapshots for reconciliation
- 5. Build order release with priority and promise data
- 6. Handle short picks with re-sourcing rules in the order management layer
- 7. Process shipments per package and send tracking to customers
- 8. Reconcile stock daily and alert on drift
- 9. Load test for peaks and agree a manual fallback
- 10. Connect returns processing, including refund triggers on inspection
Worked Example
An illustrative scenario, not a client case: a homeware retailer's WMS reports stock only at night, so daytime oversells happen whenever a fast-moving item runs low. The team adds movement events for picks, adjustments and receipts, keeps the nightly snapshot for reconciliation and applies safety stock on fast sellers. Oversells fall, and short picks now trigger automatic re-sourcing to the second warehouse.
Common Mistakes
- Stock updates only once a day
- Short picks handled manually by email
- One tracking number assumed per order
- Received stock sellable before putaway
- Unit-of-measure mismatches (each versus case)
- No load testing before peak
Want warehouse data your storefront can trust?
Talk to ZSpace Labs about WMS and OMS integration, reconciliation and exception automation and Shopify fulfilment workflows.
Conclusion
A good WMS integration exchanges events, not just end states, so every pick, short pick, package and stock movement reaches the systems that need it. Agree ownership and identifiers, handle exceptions explicitly and reconcile regularly. Related: 3PL integration, OMS vs IMS and distributed order management.
Common questions
A warehouse management system runs operations inside a warehouse: receiving, putaway, storage locations, picking, packing, shipping, counts and labour.