Get a free Shopify store audit

Shopify 3PL Integration: How It Actually Works

A Shopify 3PL integration connects your store to a warehouse as a fulfillment service or an order-management app. Here is how it actually works.

Shopify 3PL Integration: How It Actually Works — ASSOSIATIX Journal

A Shopify 3PL integration connects your store to a third-party warehouse in one of two ways: as a registered fulfillment service, which gets its own dedicated location and receives fulfillment requests directly from Shopify, or as an order-management app that reads assigned fulfillment orders and posts fulfillments back through the API. Either way, the 3PL becomes responsible for one or more of your store's locations.

The two ways a 3PL actually plugs into Shopify

Shopify's own developer documentation describes two distinct ways a third-party logistics provider connects to a store, and the difference matters because it changes who owns the location and how fulfillment requests flow.

The first is a registered FulfillmentService. When an app creates one, Shopify automatically creates a dedicated Location tied to it — the 3PL gets its own location rather than sharing yours. A FulfillmentService can accept or reject each fulfillment request it receives, and once it has accepted one, the merchant can still submit a cancellation request before the order ships.

The second is an order-management app. Rather than registering as a fulfillment service and taking on a dedicated location, this kind of app works directly against FulfillmentOrder objects that Shopify has already assigned to a location — reading what's been assigned to the merchant or a third-party location, and posting fulfillments back through the API.

Which model fits depends on what you're actually building. A registered fulfillment service is the right shape when the 3PL itself is the fulfillment location — it needs its own place in your location list and has to host the callback endpoints covered below. An order-management app is the right shape when you're reading and writing against fulfillment orders that are already assigned to a location elsewhere in your setup. If you're scoping or vetting either model — especially alongside an ERP that's also writing inventory and order data into Shopify — that's exactly the kind of integration work our Shopify integrations service covers.

Shopify's documentation lists the common use cases a fulfillment service app is actually built for: approving or rejecting requests to fulfill orders, automating the order fulfillment process for merchants, enabling clear communication between fulfillment centers and merchants, and giving merchants transparent reporting on order status through the Shopify admin. Those four use cases are a useful test when you're deciding whether a 3PL's existing Shopify connection is doing its job, or whether it's just forwarding orders without doing much else.

How one order actually moves from checkout to your 3PL

Shopify represents a fulfillment-service integration through a small set of related objects. An Order contains one or more FulfillmentOrders — Shopify's own definition is "an item or a group of items in an order that are to be fulfilled from the same location." A single order can have more than one FulfillmentOrder if it needs to ship from more than one location. Each FulfillmentOrder carries FulfillmentOrderLineItems, and once work actually ships, it's recorded as a Fulfillment — a shipment of one or more items with its own tracking information and location.

As of API version 2023-07, Shopify expects every fulfillment-service app to work against the FulfillmentOrder object; apps still built against the older Order/Fulfillment-only workflow have been unsupported since API version 2022-07.

A registered fulfillment-service app finds out what's happening through webhooks. Shopify's documented fulfillment-order webhook topics, available from API version 2023-01 onward, are: order_routing_complete (a fulfillment order was created and routing finished), fulfillment_request_submitted, fulfillment_request_accepted, fulfillment_request_rejected, placed_on_hold, hold_released, scheduled_fulfillment_order_ready, rescheduled, cancellation_request_submitted, cancellation_request_accepted, cancellation_request_rejected, cancelled, and fulfillment_service_failed_to_complete. An app that subscribes to this set can track a fulfillment order's entire lifecycle — from the moment Shopify finishes routing it, through every accept, reject, hold, and cancellation — without polling.

Merchants running an ERP alongside a 3PL should also know that editing an order after it's already assigned to a fulfillment order has its own separate lifecycle. See our breakdown of Shopify's RequestedOrderEdit API for ERP-connected 3PLs for what changes once a fulfillment order is already in play.

Setting up the connection

Registering a fulfillment service means creating a FulfillmentService resource and telling Shopify where to send requests. The resource requires the fulfillments access scope, and registering a new fulfillment service specifically requires write_fulfillments.

The resource's callback_url is the foundation for three endpoints Shopify can call:

  • callback_url/fulfillment_order_notification — a POST endpoint, and the only one that's mandatory. Shopify sends fulfillment and cancellation request notifications here.
  • callback_url/fetch_tracking_numbers — a GET endpoint, required only if tracking_support is set to true, used to retrieve tracking numbers.
  • callback_url/fetch_stock — a GET endpoint, required only if inventory_management is set to true, used to retrieve on-hand inventory levels for the fulfillment service's location.

One detail worth planning around: Shopify's developer documentation states that a request for all inventory data from fetch_stock happens once every hour to keep Shopify in sync with the remote fulfillment service — that's the only inventory-sync cadence Shopify documents for this endpoint, not a real-time push. A single callback_url can also be shared across multiple fulfillment services, which matters if a 3PL operates more than one of your warehouse locations and you'd rather not stand up a separate endpoint set for each.

Shopify's own documentation points out that you can test these callback_url-prefixed endpoints against a development store before going live, which is worth doing deliberately rather than treating the first real order as the test case — the fulfillment_order_notification endpoint in particular is mandatory, and a misconfigured one means fulfillment and cancellation requests simply never arrive.

How Shopify decides which location fulfills an order

Order routing is the layer that decides which location — your own warehouse, a storefront, or your 3PL's — actually receives each fulfillment order. Shopify's default order routing strategy applies three rules, in this order:

  1. Minimize split fulfillments — locations with every ordered item in stock are prioritized over ones that don't; when no single location has everything, Shopify prioritizes whichever locations result in the fewest packages. With no other rules in play, this defaults to the location with the highest available inventory for that order.
  2. Stay within the destination market — locations in the same market as the shipping address are prioritized.
  3. Ship from the closest location — measured as straight-line distance, not driving distance, so the result can occasionally differ from what you'd expect. Shopify recommends applying this rule last, specifically to break ties. If two locations share the same address, the older one is prioritized.

Shopify's own worked example shows how this plays out: a customer orders to a New Jersey address, and the store has four candidate locations — New York, Vancouver, Miami, and Texas. Minimize split fulfillments eliminates Texas, which doesn't have every item in stock. Stay within the destination market eliminates Vancouver, which is outside the US. Ship from the closest location picks New York over Miami. The order is routed to New York.

If your 3PL's warehouse should take priority over your other locations rather than compete purely on inventory and distance, Shopify has a separate rule for that: Use ranked locations. You group your locations — warehouse locations in the top-ranked group, everything else below — and Shopify fulfills from the top group first. With more than one warehouse location in that top group, pairing it with Ship from the closest location at the end breaks ties between them.

This same split-fulfillment logic is also at the center of Shopify's deprecation of order-level split shipping — see our breakdown of that deprecation for 3PL integrations if your integration still assumes the old behavior.

Why Shopify's automatic-fulfillment setting can quietly break a hybrid setup

Shopify ships with manual fulfillment turned on by default. Shopify's own guidance is to choose automatic fulfillment specifically when you exclusively sell digital downloads or gift cards, or when you use a fulfillment service for all of your products — not when some portion of your catalog still ships from your own hands.

That caveat is stated directly in Shopify's help documentation: "If you package and ship products yourself, then don't turn on automatic fulfillment. All new orders are marked as fulfilled, which prevents you from sorting them to find the orders that still need to be shipped." For a merchant running a hybrid setup — part of the catalog fulfilled by a 3PL, part fulfilled in-house — turning this setting on for convenience on the 3PL side will also mark your own self-shipped orders as fulfilled the instant they're placed, with no built-in way to tell which ones Shopify marked automatically versus which ones your team actually packed and shipped.

System fulfillment holds that can freeze a 3PL order before it reaches the warehouse

Even after an order is routed to the right location, it isn't automatically eligible for fulfillment. Shopify documents five system fulfillment hold types that a third-party app or service can place automatically:

  • Marketplace authorization pending — a sales channel such as Facebook or Google can hold the order for fraud analysis and payment authorization, lasting 5 minutes to 24 hours.
  • Managed Markets authorization pending — the same kind of fraud and compliance check, also 5 minutes to 24 hours, confirming details like the customer's email and phone number and that accurate duties and import taxes were collected.
  • Awaiting return items — placed on exchange items created as part of a return, released manually once the returned items are received and inspected.
  • Pending upsell offer — if a post-purchase upsell app presents an offer at checkout, the order's fulfillment status moves to On hold for up to one hour, or until the customer accepts or declines the offer, whichever comes first.
  • Unknown delivery date — applied to orders on a selling plan with an unscheduled future fulfillment date, typically pre-orders.

A single fulfillment can carry more than one hold at a time — Shopify's own example pairs a manual hold for low inventory with a system hold from a third-party app. If a 3PL integration assumes an order is ready to fulfill the instant it's routed, these holds are exactly where that assumption breaks: an order can sit routed to the correct location and still be untouchable until every hold on it clears.

A pre-go-live test checklist

Before flipping fulfillment over to a 3PL, it's worth testing the specific mechanics above rather than trusting that the integration will just work:

  • Confirm the fulfillment service's location actually appears under Settings > Locations in your Shopify admin, with Fulfill online orders from this location turned on.
  • Map every shipping-rate name your store uses to the carrier the 3PL will actually ship with, so tracking and customer notifications line up correctly.
  • Place a test order that triggers a post-purchase upsell hold, and confirm the hold releases — within the one-hour window, or immediately if the customer responds — before the order reaches the 3PL.
  • Place a multi-item test order that forces a split fulfillment across locations, and confirm each resulting fulfillment reaches the right place with correct tracking.
  • Confirm that fetch_stock's once-per-hour inventory sync is enough buffer for your actual sales velocity — a fast-moving SKU can oversell in the window between two hourly syncs if nothing else is pushing updates in between.

If you want this set up for your store, talk to our team.

Frequently asked questions

What's the difference between a Shopify fulfillment service app and an order-management app for a 3PL?

A fulfillment service app registers with Shopify and gets a dedicated location created automatically, along with formal accept/reject workflow for each fulfillment request. An order-management app doesn't register a fulfillment service or get its own location — it works directly against FulfillmentOrder objects that are already assigned elsewhere, reading what's assigned and posting fulfillments back through the API.

How does Shopify decide which location — my warehouse or my 3PL's — fulfills an order?

By default, Shopify applies three rules in order: minimize split fulfillments, stay within the destination market, and ship from the closest location. If you want your 3PL's warehouse prioritized regardless of those factors, you add the Use ranked locations rule and put the warehouse in the top-ranked group.

How often does inventory actually sync between Shopify and a 3PL's fetch_stock endpoint?

Shopify's documentation states that a full inventory request to fetch_stock happens once every hour. That's the only cadence Shopify documents for this endpoint — it isn't a real-time push, so a high-velocity SKU can still oversell within that hourly window unless something else is updating stock in between.

Can turning on automatic fulfillment break things if I still ship some orders myself?

Yes. Shopify's own documentation warns against enabling automatic fulfillment if you package and ship products yourself, because every new order gets marked as fulfilled immediately — including the ones you still need to pack and ship — which makes it hard to find the orders that actually still need your attention.

What should I test before I go live with a 3PL integration?

At minimum: confirm the 3PL's location is visible and enabled under Settings > Locations, map shipping-rate names to the right carrier, trigger a post-purchase hold and confirm it releases, force a split fulfillment across locations to confirm both legs route and track correctly, and check whether the hourly fetch_stock cadence gives you enough buffer for your sales velocity.

Sources

Tell us what you're building.

Share a few details and we'll reply within 1–2 business days with questions, a scope and a quote.