Integrating a 3PL with Shopify for Real-Time Fulfilment and Stock

Ask a third-party logistics provider whether its Shopify connection is real-time and the answer is often yes, which settles very little. Orders, tracking numbers and stock counts move on separate clocks, and one connector can be instant on one flow and hourly on another. A Shopify 3PL integration tends to hold up when paid orders reach the warehouse promptly after any agreed hold, tracking returns as each parcel ships, and stock changes are pushed as they happen using one agreed definition of the figure Shopify receives. Settle those three and overselling, delivery queries and spreadsheet uploads usually recede; leave one vague and a manual workaround survives around it.

The choice between the 3PL’s own app, an integration platform and a custom build therefore matters less than it first appears. Each can meet that standard or miss it, depending on configuration and on what the business has written down beforehand. The design questions grow when an ERP also sits in the flow, because the warehouse link becomes one leg of a wider ERP connection for Shopify, and order status or stock may then have two possible sources.

Why Real-Time Means Three Different Things in a Shopify 3PL Integration

Each flow has a different consequence when it runs late, so each deserves its own target rather than a blanket promise from the vendor.

Orders: from paid order to fulfilment request

Shopify can request fulfilment without anyone pressing a button. Its Help Center explains that with automatic fulfilment, the request goes to the fulfilment service once the order is paid. The same guidance notes that after a fulfilment has been requested, the order can no longer be edited and items cannot be refunded, and that once the warehouse has accepted a request, cancelling it means sending a cancellation request and waiting for a reply.

A store that releases orders the instant they are paid therefore gives up its window for address corrections, fraud review and customers changing their minds. Some retailers prefer a short, deliberate hold, for example releasing orders in batches or holding those flagged for review. The right delay depends on how often customers ask for changes, the 3PL’s daily pick cut-off and how much a shipped mistake costs to reverse.

Tracking: from shipped parcel to customer notification

Tracking flows the other way. When the 3PL creates the fulfilment in Shopify with a carrier and tracking number, the order is marked as fulfilled and Shopify can send the customer a shipping confirmation. Delays here seldom cause stock errors, but they tend to surface in the support inbox. Shopify’s developer documentation describes an optional arrangement in which Shopify asks the fulfilment service for outstanding tracking numbers once each hour, so a connector relying on that alone can leave a parcel unconfirmed for up to an hour after it leaves the dock.

Stock: from warehouse count to sellable quantity

Stock carries the most commercial risk, since it decides what the storefront will sell. The same documentation describes a stock endpoint that Shopify calls for all inventory once every hour, treating the values it returns as on-hand quantities. For a slow-moving catalogue, an hourly stock sync may be perfectly adequate. For a product featured in an email campaign, sixty minutes may be enough for the store to take orders against units the warehouse has already allocated elsewhere or set aside as damaged.

Connectors built for a tighter stock sync push changes through Shopify’s GraphQL Admin API as they occur, using inventory mutations such as inventorySetQuantities. Shopify’s inventory documentation explains that these mutations can carry a compare-and-swap check, which fails when the current quantity differs from the one the sender expected, and an idempotency key that stops the same adjustment being applied twice. Both safeguards matter when warehouse events arrive in bursts.

How Shopify Hands Work to a 3PL Behind the Scenes

In most Shopify 3PL integration projects, the 3PL’s app connects as what Shopify calls a fulfillment service. Registering one creates a separate location in Shopify for that warehouse, and the products it manages are fulfilled from that location. Shopify represents the work as fulfilment orders, each tied to one location, so a single order can mix items shipped by the 3PL with items packed elsewhere.

The exchange then follows a defined sequence, set out in Shopify’s developer documentation for fulfillment services. Shopify notifies the service at a callback address when fulfilment or cancellation is requested. The service reads the fulfilment orders assigned to it, accepts or rejects each request and, once the parcel has shipped, creates the fulfilment with tracking details. Shopify also publishes webhooks for the surrounding events, including requests accepted or rejected, orders placed on hold or released, and a fulfilment service failing to complete an order.

That structure helps with diagnosis. When an order appears stuck, the useful question is which step it reached: not yet requested, requested but not accepted, accepted but not shipped, or shipped without tracking. A connector that logs each transition answers that without anyone comparing two dashboards.

Not every 3PL works through an app. Warehouses that also serve retail and wholesale channels often exchange EDI documents built on the X12 standard: the Warehouse Shipping Order (940) instructs a shipment, the Warehouse Shipping Advice (945) confirms it and the Inventory Inquiry/Advice (846) reports stock. In that arrangement, a middleware layer translates between Shopify’s fulfilment orders and those documents, and the timing of each flow depends on how often files are exchanged.

Which Stock Figure Should Shopify Receive From the 3PL?

Two systems can both say “stock” and mean different things. Shopify’s inventory states define on hand as the total of committed, unavailable and available units at a location. Committed covers units set aside for unfulfilled orders, and available is what the store can still sell.

3PL platforms tend to expose several figures. ShipBob’s developer documentation is a clear example. Its inventory API returns an on-hand quantity, a committed quantity reserved for existing orders, a fulfillable quantity defined as on hand minus committed, and a sellable quantity that adds stock expected to arrive and removes quarantined and damaged units. Each is correct for its purpose, but only one matches what Shopify expects.

Figure sent to ShopifyWhat it usually containsRisk if Shopify treats it as on hand
Warehouse on handEvery unit in the building, including units picked for open ordersLow, provided Shopify’s committed count reflects the same open orders
Fulfillable or allocated stockOn hand minus units already reserved for ordersUnits for unfulfilled Shopify orders are deducted twice, so the store understates what it can sell
Sellable including inboundFulfillable stock plus goods expected to arriveThe store may sell units still in transit or awaiting receipt

None of these figures is wrong in itself. The trouble starts when the definition on one side differs from the assumption on the other, and the result looks like a stock sync failure even though every message arrived on time. Agreeing the figure in writing, then testing it with an order that is placed, picked and shipped while a sync runs, tends to expose a mismatch before customers do. The pattern closely resembles the double counting that makes stock drift between a store and an ERP, where competing definitions also masquerade as technical faults.

Signs the Current 3PL Connection Needs Rework

  • Stock in Shopify moves in steps, often on the hour. That pattern usually points to a scheduled stock sync rather than event-driven updates, which can leave fast sellers exposed between runs.
  • Customers ask about dispatch before tracking arrives. Tracking that trails the physical shipment generates avoidable contacts and can make the store look slower than its warehouse.
  • Staff upload CSV files of orders or tracking numbers. Manual steps tend to survive wherever the connector cannot handle an exception, such as split shipments or personalised items.
  • Returned units reappear in Shopify days after the warehouse received them. Returns are often the least automated flow, and saleable stock sits idle in the meantime.
  • Wholesale or marketplace orders reach the 3PL by email. A second, manual route into the same warehouse makes stock figures harder to reconcile.

Three Ways to Connect a 3PL to Shopify

The options for a Shopify 3PL integration differ less in what they can do than in who controls the rules and who fixes problems when they occur.

The 3PL’s own Shopify app

Most established 3PLs offer a Shopify connector, and it is often the quickest route because the vendor usually maintains it as Shopify’s APIs change. The limits lie in configuration. Release timing, the stock figure sent and the way exceptions are reported are set by the vendor, and a business with unusual rules may find no setting that matches. This route suits a store that sells mainly through Shopify, uses one warehouse and can accept the vendor’s defaults once it understands them.

An integration platform or middleware

An integration platform (iPaaS) or middleware service sits between Shopify, the 3PL and often an ERP. It suits businesses with several sales channels or warehouses, or a 3PL that only works through EDI, because one layer can translate formats, apply routing rules and keep a log of every message. The trade-off is another subscription, another system to monitor and, frequently, a single person who understands the mappings when something breaks.

A custom integration

A purpose-built service using Shopify’s GraphQL Admin API and the 3PL’s API gives full control over timing, figures and failure handling. It tends to make sense when stock rules are unusual, such as kits assembled in the warehouse or stock shared with retail shops, when order volumes make hourly corrections costly, or when an existing connector has been patched until it is fragile. The build budget is higher, and someone has to own the code as both APIs evolve.

Wholesale flows deserve particular attention in that decision. Pallet orders, customer-specific packing instructions and account terms rarely fit a consumer-oriented connector, so stores adding a trade channel often plan the 3PL rules alongside their wholesale ordering and B2B fulfilment workflows rather than bolting them on later.

Criterion3PL’s own appIntegration platformCustom integration
Best suited forOne store, one warehouse, standard workflowsSeveral channels or warehouses, EDI-only 3PLsUnusual stock rules, high volumes, fragile existing set-ups
Stock sync timingSet by the vendor; confirm whether it pushes or pollsConfigurable within the platform’s scheduling limitsEvent-driven, designed around the business’s targets
Control over release rules and figuresLimited to the settings offeredModerate, through mappings and rulesFull
Ongoing ownershipVendorPlatform vendor plus an internal or agency ownerInternal team or agency
Main riskDefaults that do not match how the business operatesMapping knowledge held by one personHigher build cost and a maintenance commitment

For a single-warehouse store with a tidy catalogue, the vendor’s app may cover every requirement, provided someone confirms how it treats each of the three clocks. The reverse also holds: a connector that needs a spreadsheet every morning is already costing staff time that rarely appears in its subscription price.

Key takeaway: Treat orders, tracking and stock as three separate agreements with the 3PL, each with its own timing target, owner and failure alert. The stock agreement deserves the most care, because a mismatched definition of on hand can cause overselling even when every sync runs on schedule.

How to Set Up a Shopify 3PL Integration in Six Steps

  1. Map both sides’ order states. Shopify’s fulfilment orders move between states such as open, in progress, on hold and closed, while the 3PL will have its own, often including exceptions and backorders. Writing the mapping down shows which warehouse states have no Shopify equivalent and therefore need an alert rather than a silent wait.
  2. Agree the stock figure and the stock sync method. Decide which figure the 3PL sends, whether changes are pushed as they happen or pulled on a schedule, and how often a full comparison runs to catch anything missed. A nightly check of every SKU is a common safety net.
  3. Set the release rule for orders. Choose between immediate release and a short hold, weighing the edit and cancellation limits described earlier against the warehouse’s cut-off times. Document how changes made after release are handled.
  4. Clean up SKUs and kits. Shopify’s documentation notes that SKUs returned by a fulfilment service’s stock endpoint are matched case-sensitively, so “TEE-blue” and “TEE-BLUE” are different products to the integration. Bundles need a rule too: either the warehouse holds a kit SKU, or the connector translates one Shopify item into its components.
  5. Design for missed, duplicated and late messages. Shopify’s webhook guidance warns that deliveries can be missed and that events within a topic may arrive out of order, and it advises apps to run reconciliation jobs. ShipBob’s documentation similarly warns that its webhooks may be delayed or lost and may arrive more than once. The integration should therefore discard duplicates, order events by timestamp, retry safely and alert a named person when a request is rejected or a fulfilment fails.
  6. Test with awkward orders, then run in parallel. Split shipments, partial stock, address edits, cancellations after acceptance, returns and a promotion-day burst all belong in the test plan. A parallel run with daily comparisons then gives the team evidence before manual checks are switched off.

Internal expert input required: confirm WD Market’s standard reconciliation frequency and alerting set-up for 3PL integrations, and add a verified, publishable example of a Shopify 3PL project if one exists.

The Mistake That Keeps Manual Work Alive: Leaving Returns Out of Scope

Projects often concentrate on outbound orders and treat returns and purchase-order receipts as later work, yet these are the events that increase stock. ShipBob, for instance, publishes separate webhook events for returns and for warehouse receiving orders, down to boxes arriving, being scanned and being stowed. If those events do not reach Shopify, restocked units stay unsellable until someone notices.

Fulfilment Automation in Practice: The GloveTray Shopify Project

WD Market’s work with GloveTray, a Shopify store selling primarily into the USA, shows where fulfilment automation can sit among competing priorities. GloveTray ships its own orders rather than using a 3PL, so the connection in question was with a carrier. Among the project objectives was to “automate manual fulfillment processes”, and the delivered work included Latvijas Pasts shipping-label automation alongside a product-page redesign and a Microsoft Clarity set-up. The case study describes the operational value as “reducing manual work associated with shipping-label creation”.

The transferable lesson concerns sequencing. During an important sales season, GloveTray put the changes closest to revenue first, alongside the fulfilment step that generated repeated manual effort, instead of waiting for a complete redesign. The GloveTray product-page redesign and shipping-label automation sets out that order of work in detail.

Agreeing the Clocks Before Choosing the Connector

A Shopify 3PL integration is judged on three flows rather than one: orders reaching the warehouse at the right moment, tracking returning as parcels ship, and stock arriving as a figure both systems define the same way. Shopify’s native fulfilment service model polls stock and tracking hourly unless the connector pushes changes, so the first question for any vendor app, platform or custom build is how it handles each flow. After that, the work is mostly documentation and testing: the order-state map, the stock definition, the release rule and a named owner for failures, checked against the current connection before anything new is bought or built.

From Hourly Syncs to Event-Driven Fulfilment

If that review reveals gaps the current connector cannot close, WD Market designs and builds integrations between Shopify, 3PLs and ERPs, starting from the order, tracking and stock agreements outlined in this guide. To see how those projects are scoped and priced, explore WD Market’s ecommerce ERP integration services.

When you are ready to talk through your warehouse set-up, order volumes and the flows still causing manual work, schedule a discovery call with WD Market. For shorter notes on integration and ecommerce operations between projects, follow WD Market on LinkedIn.

Questions About Shopify 3PL Integration

Can a 3PL connect to Shopify without an app?

In practice, a 3PL normally appears in Shopify as a fulfilment service registered by an app, whether the 3PL’s own connector, an integration platform or a custom build. Some smaller warehouses work from CSV order exports and tracking imports instead. That can be workable at low volumes, but stock is then updated by hand, and the delay and keying errors tend to make an API connection worthwhile as order numbers grow.

How often should stock sync between a 3PL and Shopify?

Ideally, each stock change is sent when it happens, with a scheduled full comparison as a backstop. The hourly pull Shopify makes from a fulfilment service’s stock endpoint may suit slow-moving products, but fast sellers and promoted items can oversell within that window. Event-driven updates combined with a daily reconciliation of every SKU give many stores a sensible balance; very high-volume catalogues may justify more frequent checks.

Can one Shopify store use more than one 3PL?

Yes. Each fulfilment service has its own location in Shopify, and the fulfilment method is chosen per product, so a store can send some products to one warehouse and others to a second. Complications tend to appear when the same SKU is stocked in both, because routing, stock totals and split shipments then need explicit rules. That situation is often where an integration platform or custom logic becomes worth considering.

What does a custom 3PL integration with Shopify involve?

Usually a mapping phase covering order states, stock definitions and release rules, then a service that listens to Shopify and 3PL events, then testing with real edge cases and a parallel run. Effort depends on the number of warehouses, sales channels and exceptions such as kits or B2B orders. WD Market scopes this as part of its custom integration work connecting stores, ERPs and warehouses, starting with the flows that create the most manual effort.