Shopify WMS & 3PL integration
Sync fulfillment events, tracking, and stock updates so Shopify always reflects what’s happening in the warehouse.
Events to sync
- Fulfillment created, packed, shipped
- Tracking number updates
- Inventory adjustments by location
Operational pitfalls to avoid
- Split shipments
- Cut-off times and carrier rules
- Missing SKU mappings
WMS VS 3PL
A WMS and a 3PL are not the same integration
Both keep Shopify in sync with what is physically happening in the warehouse, but they sit on opposite sides of the operation, and the integration work is genuinely different. Getting this distinction wrong is the most common reason a warehouse project stalls halfway through.
Integrating a WMS
A warehouse management system is software you run over your own warehouse. You own the master data, the locations and the picking rules, so the integration is a two-way conversation: Shopify sends orders, the WMS sends back stock, fulfillments and tracking. You decide which system is the source of truth for inventory, and that single decision shapes everything else in the project.
- Your own warehouse, your own staff
- Full control of locations, bins and picking rules
- You own the inventory master data
- Usually an on-premise or private API
Integrating a 3PL
A third-party logistics provider holds your stock and ships on your behalf. You do not own their system, so you integrate against whatever they expose: a REST API, an EDI feed, or a nightly file drop. The work shifts from modelling your operation to reconciling theirs, which means their item codes, their cut-off times and their status names.
- Someone else's warehouse and staff
- You integrate against their API, EDI or files
- Stock is reported to you, not owned by you
- A second provider means a second integration
DATA FLOWS
What syncs between Shopify and your warehouse
Six flows cover almost every WMS and 3PL project. Which of them you need, and in which direction they run, depends on who owns the stock.
Inventory by location
Available stock is pushed to Shopify per location, not as a single global figure. Without it, a two-warehouse store oversells the moment one site runs dry.
Orders to the warehouse
Paid orders travel to the WMS or 3PL with the data a picker actually needs: SKU, quantity, shipping method, delivery notes and any B2B or gift requirement.
Fulfillments and tracking
When the box leaves, the fulfillment is created in Shopify with its carrier and tracking number, so the customer gets notified without anyone opening the admin.
Returns and RMAs
Returned goods come back into stock only once the warehouse has inspected them. Restocking on the refund instead of on the inspection is how phantom inventory appears.
Adjustments and cycle counts
Cycle counts, breakages and manual corrections made on the warehouse floor are reflected in Shopify, so the number on the storefront matches the number on the shelf.
SKU and barcode mapping
Shopify variants and warehouse item codes rarely match one to one. The mapping layer, barcodes, packs and kits included, is where most of the real integration work lives.
MULTI-WAREHOUSE
The multi-warehouse problem Shopify does not solve on its own
Shopify can hold stock in several locations and route orders between them, but its smart order routing decides with the only data it has: available quantity and a priority list. It does not know that one site cannot ship hazardous goods, that another closes at 14:00, or that splitting a two-line order costs more in carriage than the margin on the second line.
That is why multi-warehouse stores end up with split shipments nobody asked for, orders sent to whichever site happens to sit first in the list, and stock that looks available but is already committed elsewhere. Allocation logic has to live where the operational rules live: in the WMS, or in the integration layer between the two.
We wrote up the specific limits in detail in Shopify multi-warehouse limitations: why smart order routing falls short.
HOW IT WORKS
How a warehouse integration is built, step by step
1. Decide who owns the inventory
Before a single line of code: is Shopify or the warehouse the source of truth for stock? Conflict resolution, the direction of every sync and what happens to a manual adjustment all follow from this one answer.
2. Map the catalogue
Match Shopify variants to warehouse item codes, including barcodes, packs, kits and every SKU that exists in one system but not the other. Unmapped SKUs are the single biggest cause of failed fulfillments in the first month.
3. Agree the events and the cadence
Which events cross the boundary and how often: orders in near real time, stock every few minutes, a full reconciliation overnight. Not everything needs to be instant, and designing as though it does is expensive.
4. Handle the exceptions
Split shipments, partial fulfillments, cancellations after picking has started, backorders, carrier cut-offs. This is the part that decides whether the integration survives Black Friday, and the part most projects leave until last.
5. Reconcile and monitor
A nightly comparison of Shopify stock against warehouse stock, with alerts when the two drift apart. An integration you cannot audit is one your team will quietly stop trusting.
BEFORE YOU CHOOSE
Six questions to settle before you commit
- Does the provider expose a real API, or only EDI and scheduled files? The answer sets your minimum sync latency.
- Can it report stock per location, or only one global total?
- How are partial and split fulfillments represented on their side?
- Who wins when Shopify and the warehouse disagree about a quantity?
- What happens to orders placed after the carrier cut-off?
- If you add a second warehouse or 3PL next year, does the design survive it?
If the provider’s documentation does not answer these six, ask before signing. Every one of them is cheap to settle up front and expensive to discover in production.
FAQ
Frequently asked questions about WMS and 3PL integration
What is the difference between a WMS and a 3PL integration?
With a WMS you own the system and the warehouse, so you decide the data model and can make the sync two-way. With a 3PL you integrate against a system somebody else controls, which means adapting to their item codes, their statuses and whatever interface they publish.
Do I need an API to integrate my 3PL with Shopify?
Not necessarily. Plenty of providers still work over EDI or scheduled CSV and SFTP drops, and those integrate perfectly well. They simply set a floor on how fresh your stock figures can be: a file dropped every four hours means Shopify is, at worst, four hours behind the shelf.
Can Shopify handle stock across several warehouses?
It can hold inventory per location and route orders between them, but its routing only knows quantities and a priority order. Operational rules such as cut-off times, hazardous goods or the carriage cost of a split have to be applied by the WMS or by the integration layer.
How long does a WMS or 3PL integration take?
For a provider with documented endpoints and a clean catalogue, a first working sync usually takes a few weeks. What stretches a project is rarely the connection itself: it is catalogue mapping and the exception rules nobody wrote down.
Will it work with more than one warehouse or 3PL?
Yes, and it should be designed for it from the start even if you only have one today. Adding a second provider to a design that assumed a single one usually means rebuilding the allocation logic from scratch.
What happens if the warehouse system goes offline?
Messages queue and retry instead of being dropped, and the nightly reconciliation catches anything that still slipped through. The failure mode worth designing against is the silent one: an integration that loses an event and tells nobody.
Tell us your systems.