WMS Integration

WMS integration connects your Warehouse Management System with all systems that matter before and after the warehouse: online shop, marketplaces, ERP, order management and shipping carriers. Without a clean connection, double bookings, outdated stock in the shop and delayed tracking information occur – regardless of how efficiently the WMS operates inside the warehouse itself.

This guide explains which systems need to be connected, which interfaces are suitable, what typical data flows look like and how to structure an integration project – from requirements analysis to productive go-live.

Why WMS Integration Is the Critical Success Factor

A WMS alone only controls what happens physically in the warehouse. However, the customer order comes from the shop, purchasing from the ERP, shipping labels from the carrier API. Each of these sources delivers data that must be processed in the WMS and reported back.

Integration creates a closed loop:

1. Order arrives in the shop → WMS receives pick order
2. WMS picks and packs → stock is reduced
3. WMS reports shipment → shop receives tracking number
4. Return arrives → WMS books in → shop updates availability

If one link in this chain is missing, warehouse and sales work with different truths. This leads to overselling, customer complaints and manual rework – often more expensive than the integration itself.

WMS Integration Ecosystem

The WMS sits at the center and exchanges data bidirectionally with all connected systems:

Which Systems Need to Be Connected?

Shop System and Marketplaces

The online shop or marketplace is the primary source of customer orders. The following data must flow through the integration:

• Inbound: New orders, cancellations, address changes
• Outbound: Available stock, shipping confirmations, tracking numbers, return status

For multi-channel setups with several sales channels, an OMS is recommended as a central hub between shops and WMS. Learn more about shop integration in the Multi-Channel Fulfillment chapter.

ERP and Financial Accounting

The ERP manages purchasing, suppliers, cost centers and accounting. Typical integration points:

1. Goods receipt – WMS reports stored quantities to ERP
2. Goods issue – shipping posting triggers warehouse deduction in ERP
3. Inventory – stock discrepancies are passed to financial accounting
4. Master data – item numbers, EANs and descriptions are kept in sync

Shipping Carriers and Label Systems

The WMS or connected shipping software generates shipping labels via carrier APIs. Tracking numbers, shipping costs and delivery status are reported back. Without this connection, labels would have to be created manually and tracking numbers copied into the shop.

Fulfillment Service Providers (3PL)

With external fulfillment, the WMS runs at the service provider. Your shop system must then be connected via their API or middleware. The technical integration should already be checked during provider selection – subsequent integrations are costly and error-prone.

Integration Methods Compared

The Four Critical Data Flows

001. Order Intake (Order Import)

New orders are transferred from the shop or OMS to the WMS. Required fields:

• Order number (unique, not reusable)
• SKU, quantity, batch or serial number requirements if applicable
• Delivery address complete and validated
• Shipping method and priority (standard, express)
• Payment status or release flag

The WMS reserves stock and creates pick orders. Missing or incorrect addresses should be validated before handover – not only in the warehouse.

002. Inventory Sync (Inventory Sync)

Inventory management in the WMS is the leading source for physical stock. The shop only displays what the WMS reports as available.

003. Shipment Confirmation (Shipment Confirmation)

After packing, the WMS reports to shop and customer:

1. Shipping date and time
2. Carrier and product (e.g. DHL Parcel)
3. Tracking number
4. Actually shipped line items (partial shipment possible)

The customer automatically receives a shipping notification – provided the shop processes the feedback promptly.

004. Return Feedback (Return Processing)

Returned goods are booked in and inspected in the WMS. Depending on the result:

• Restocking → stock increases, shop is updated
• B-grade / scrap → separate stock pool or write-off
• Trigger refund → feedback to shop/ERP

Returns Integration Loop

Integration Project in Six Phases

Phase 1: Requirements Analysis

Before configuring interfaces, document all involved systems, data objects and processes. Clarify:

• Which shop systems and marketplaces are in use?
• Is there an OMS as middleware?
• Which WMS – own warehouse or 3PL system?
• Which carrier APIs are used?
• Which SLAs apply for stock updates and shipping notifications?

Phase 2: Interface Specification

Create a mapping document for each data object: Which field in the shop corresponds to which field in the WMS? Examples:

• order_id ↔ order number
• sku ↔ item number
• qty ↔ quantity
• tracking_number ↔ tracking number

Phase 3: Development and Configuration

Depending on method: API development, middleware configuration or EDI setup. Use test environments (sandbox) of all involved systems – never develop directly in production.

Phase 4: Testing with Realistic Scenarios

Test at least these cases:

1. Standard order with one item
2. Multi-line order with partial shipment
3. Cancellation before and after pick start
4. Inventory sync after goods receipt and shipping
5. Return with restocking
6. Peak scenario with 50+ orders in a short time

Phase 5: Parallel Operation and Cutover

Run the new setup in parallel with the old process initially. Compare postings and stock daily. Only when deviations are below the agreed tolerance, switch off the old process.

Phase 6: Monitoring and Maintenance

After go-live, monitor interface health, error rates and latency. Alerts on failed API calls prevent orders from remaining unprocessed for hours.

Typical WMS Integration Timeline

Common Mistakes and How to Avoid Them

Typical pitfalls:

• SKU mismatch – shop uses variant SKU, WMS only main item number
• Duplicate order imports – missing idempotency on API retries
• Delayed stock – batch sync every 4 hours with express shipping
• Missing error handling – API timeout leads to lost order instead of retry
• No audit log – traceability missing when discrepancies occur

Checklist: WMS Integration Before Go-Live

12 mandatory items before productive start:

• SKU mapping between all systems complete and verified
• Order intake tested (single and multi-line)
• Cancellation workflow validated in both directions
• Stock sync after goods receipt, shipping and returns correct
• Shipping confirmation with tracking number visible in shop
• Partial shipment scenario successfully completed
• Error handling on API failure (retry, alert) active
• Sandbox tests with realistic data volumes completed
• Parallel operation at least one week without critical deviations
• Documentation for warehouse team and IT available
• Escalation path for interface failure defined
• Rollback plan in case of failed cutover

WMS Integration for Small Warehouses vs. Enterprise

For WMS in small and medium warehouses, pre-built shop connectors from WMS providers (Shopify, WooCommerce, Shopware) are often sufficient. WMS selection should therefore always include the question: Which standard integrations are available without custom development?

In enterprise environments with ERP (SAP, Microsoft Dynamics) and EDI connections to suppliers, integration projects are significantly more complex – a planning period of 3–6 months is realistic.

Integration Effort by Company Size

KPIs for Measuring Integration Success

After go-live, these metrics show whether the integration runs reliably:

1. Sync latency – time between warehouse movement and shop stock update (target: under 5 minutes)
2. API error rate – share of failed interface calls (target: under 0.1%)
3. Order-to-pick time – time from order receipt to pick start (target: under 30 minutes)
4. Tracking availability – share of shipments with tracking within 2 hours after shipping (target: over 98%)
5. Stock discrepancy – difference WMS vs. shop (target: 0 with correct integration)

The underlying WMS functions must be fully configured before integration – otherwise faulty data is only distributed faster between systems.

Related Topics

• WMS Warehouse Management System
• WMS Functions
• WMS Selection
• Technical Integration in 3PL Selection
• Shop Integration in Multi-Channel

Last updated: July 7, 2026