WMS integrations with e-commerce platforms and carriers
An integration is more than a one-time order import. It must manage identity, state transitions, retries, partial fulfilment, cancellations, inventory publication and shipment data when one system is temporarily unavailable.
Core data flows
Sales channels typically send order lines, address, service and payment or hold state. WMS returns actual fulfilment, shipment ID and tracking. Inventory publication is often separate because sellable quantity is not the same as physical on-hand.
- Order events and periodic reconciliation should complement each other.
- SKU, order and shipment identifiers must remain stable.
- Failures need an observable queue with repair and retry actions.
Platform and carrier API boundaries
Shopify documents inventory states and webhooks, but not every state change emits one. WooCommerce distinguishes the authenticated WC REST API from its Store API. eBay separates fulfilment orders from inventory records and offers. “Integrating a platform” therefore means choosing exact objects, versions and state semantics.
Carrier APIs commonly create shipments, labels, pickup requests or tracking records. WMS should distinguish label creation from physical handover, and a carrier error must not silently mark an order shipped.
Illustrative example
This is a simplified workflow example, not a customer result or a guarantee of a specific Paktera capability.
A Shopify order is imported with a stable external ID. One line is short, so WMS waits for a partial-shipment decision rather than duplicating the order or reporting full fulfilment. Two shipments return separate tracking numbers and actual quantities; reconciliation later confirms the final state.
Common mistakes and safe rollout
Common mistakes are relying only on webhooks, matching by title, duplicating orders on retries, ignoring rate limits and skipping a test environment. Start with one channel and explicit acceptance criteria. The exact scope of any Paktera connector, fields and carrier services must be confirmed in a demo or technical discovery; this article does not guarantee them.
Integration acceptance checklist
Before launch, agree which system owns each field and who resolves errors. These are suggested acceptance tests, not a claim that every Paktera connector already implements them.
| Scenario | Action | Acceptance criterion |
|---|---|---|
| Duplicate event | Deliver the same test order twice. | Exactly one order is created. |
| Unknown SKU | Send an unmapped item code. | An explicit error; no item is guessed from its name. |
| Stock publication | Change reserved and available quantities. | The channel receives the agreed sellable quantity. |
| Partial shipment | Ship only part of an order. | Actual lines, quantities and tracking numbers are returned. |
| Recovery | Reconcile systems after a test outage. | No missing records, duplicates or stale state. |
Key terms
- Webhook
- An event notification sent by one system to another endpoint.
- Reconciliation
- Periodic comparison of objects and states across systems.
- Rate limit
- A limit on API request volume or frequency.
- External ID
- A stable identifier for an object in another system.