Talk to us
Shopify logo Ecommerce Shopify GXO logo WMS & 3PL GXO

Integration combo

Shopify to GXO integration

Shopify is the storefront. GXO is enterprise-grade contract logistics: warehouses at scale, integrated with their own WMS, with the operational rhythm a large brand expects. Connecting them properly means orders flow to GXO for despatch on the right service level, inventory and tracking writebacks keep Shopify honest, and exception handling is structured rather than ad-hoc. Built and supported as a Patchworks Partner Agency.

Talk to us about Shopify to GXO See all combos

Flow shape

Order sync: Shopify to GXO

Shopify orders flow to GXO on the agreed batch cadence with the right service-level mapping; tracking and fulfilment events write back to Shopify as despatch completes.

  1. Trigger Shopify Order paid orders/paid webhook
  2. Extract Patchworks Queue for batch configured cadence
  3. Transform Patchworks Map to GXO service level, address, items
  4. Action GXO Send batch via API or SFTP
  5. Trigger GXO Despatch event tracking + carrier
  6. Writeback Shopify Fulfil order tracking, carrier

Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.

What we sync

5 synchronisations between Shopify and GXO.

Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.

  1. 01

    Order sync

    Shopify GXO

    Orders raised in Shopify flow into GXO on creation, status change and edit. The flow normalises Shopify's order schema into the record shape GXO expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so GXO stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.

  2. 02

    Inventory sync

    GXO Shopify

    Stock levels in GXO push to Shopify on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where Shopify has its own location model we map GXO's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with GXO retaining authority.

  3. 03

    Fulfilment sync

    GXO Shopify

    Pick, pack and dispatch events from GXO push back into Shopify so the order record advances in step with the physical warehouse. Partial fulfilments, split shipments, backorders and substitutions are modelled rather than collapsed into a single 'shipped' state. Carrier, service level, tracking number and dispatched-at timestamp arrive on the same event so Shopify's customer comms can fire at the right moment. Where Shopify is a marketplace, the flow conforms to that marketplace's strict on-time-dispatch SLA rather than the storefront's looser conventions.

  4. 04

    Tracking sync

    GXO Shopify

    Carrier tracking numbers and delivery events from GXO sync into Shopify so the customer-facing surface (order page, dispatch email, helpdesk ticket) reflects real delivery state rather than the warehouse's last known status. Updates flow through as events: in-transit, out-for-delivery, delivered, attempted, returned-to-sender. Shopify's notification rules fire against these events rather than against GXO's internal status codes, which means the customer experience stays consistent even when the carrier mix changes underneath.

  5. 05

    Returns sync

    Shopify GXO

    Return authorisations created in Shopify flow into GXO with reason codes, inspection state, restocking decisions and refund eligibility carried through. Where GXO is the ERP or WMS, the return becomes an inbound record that affects available stock and accounts. Where GXO is the storefront, the order record updates so the customer-facing return state stays honest. Exchanges are handled as a paired return-plus-outbound rather than collapsed into a refund-plus-new-order, which keeps the accounting clean and the operational picture accurate.

Typical delivery

8 to 12 weeks for a standard delivery.

Up to 5× faster using PatchBuddy
  1. Week 1 to 2 Discovery: GXO spec, file formats, service-level mapping, exception model.
  2. Weeks 3 to 6 Build: orders, inventory, despatch, tracking, returns writeback.
  3. Weeks 7 to 9 Integration testing through GXO UAT cycles.
  4. Weeks 10 to 12 Cutover and hyper-care into retainer.

Patchworks delivery

How Patchworks shapes Shopify to GXO.

GXO integrations are project-grade: file specifications, structured EDI or API exchanges, formal UAT cycles. Patchworks gives the merchant a controlled boundary between Shopify's event stream and GXO's batch-oriented expectations. Flows live in Patchworks with full audit trail; runbooks cover what to do when a GXO batch lags or rejects, and the on-call engineer sees the picture before customer care does.

Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →

Our Patchworks practice

Questions

Common questions.

Get in touch

Tell us what you’re trying to connect.

And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.

Direct: contact@ecirql.com