Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Shopify · Sage X3
Connect Sage X3 + Shopify / Shopify Plus
Automate order, customer, product and price, inventory by location, fulfilment and tracking between Sage X3 and Shopify / Shopify Plus — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Sage X3 and Shopify / Shopify Plus.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Sage X3 and Shopify / Shopify Plus, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for operations and IT teams running Sage X3 behind one or more Shopify or Shopify Plus stores.
What needs to be in place
- A Shopify or Shopify Plus store with a custom app or API credentials available.
- Sage X3 with API access and a service user permitted to create the documents in scope.
- Agreed rules for which X3 sites and stock statuses feed Shopify availability.
- A fulfilment process — internal or 3PL — that can return despatch detail.
When you may not need this
A single-location store with simple products may be served by lighter tooling. This is for teams with multiple sites, complex items or fulfilment steps that generate daily exceptions.
What is out of scope
- Multi-site stock rules are confirmed in scoping because they depend on your X3 configuration and warehouse policy.
- Shopify theme, checkout and app development are out of scope.
- APIWORX does not change your X3 pricing configuration; we apply the rules X3 holds.
What actually moves, and who owns it
A representative Shopify and Sage X3 scope, confirmed per customer before build.
Sage X3APIWORX (mapping, retries, exception queue)Shopify / Shopify Plus
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Order | Shopify | Sage X3 | Shopify at capture | Order reaches an agreed status | Held in exception queue with the validation error | APIWORX |
| Customer | Shopify | Sage X3 | Agreed per customer type | New or changed customer | Unmatched customer raises a named exception | APIWORX |
| Product and price | Sage X3 | Shopify | Sage X3 | Item or price change | Retried, then queued with the rejected field | APIWORX |
| Inventory by location | Sage X3 | Shopify | Sage X3 | Agreed publishing cadence | Last published figure retained; exception raised | APIWORX |
| Fulfilment and tracking | Sage X3 or 3PL | Shopify | Despatch record | Order despatched | Retried, then queued for review | APIWORX |
| Refund / credit | Shopify | Sage X3 | Agreed in scoping | Refund approved | Held for finance review | APIWORX (delivery) / you (approval) |
Three decisions that make or break this integration
Multi-location stock without guesswork
Shopify supports locations; X3 holds sites and stock statuses. The mapping between them is agreed explicitly so availability published to Shopify reflects a documented rule rather than a best guess.
- X3 site to Shopify location mapping agreed before build.
- Which stock statuses count as sellable defined per site.
- Buffers applied per item or group where you want protection.
- Publishing cadence stated in your scope; no real-time claim is made here.
Orders that respect payment and fraud holds
An order only becomes an X3 document when it reaches the status your team agreed. That keeps unpaid or flagged orders out of fulfilment while still capturing everything for reporting.
- Trigger status agreed with finance and operations.
- Discounts, gift cards and shipping mapped to agreed X3 treatment.
- Tax handling mapped rather than inherited by accident.
- Unmapped SKUs raise a named exception instead of posting to a catch-all.
Fulfilment visible to customers and support
Despatch confirmations and tracking flow back to Shopify so notifications fire from the store and support sees the same picture as the warehouse. Partial and split shipments are handled as agreed rather than collapsed into one update.
- Tracking written back so Shopify notifications work normally.
- Split and partial shipments handled per your fulfilment model.
- 3PL handoffs included where the 3PL can return the required detail.
- Failed writebacks retried, then queued with the reason attached.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every run is logged with the source record reference so an order, shipment or stock update can be traced end to end.
- Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier (order number, shipment ID, SKU).
- Exceptions are worked by the APIWORX team and escalated to your named operations contacts when a business decision is needed.
- Mapping changes — new SKUs, new locations, new warehouses, new channels — are part of the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How an order is traced
Illustrative — not customer data
An illustrative reference trace between Shopify and Sage X3.
| Shopify order name | Sage X3 sales order number |
|---|---|
| Shopify customer | Sage X3 customer account |
| Despatch record | Shopify fulfilment with tracking |
| Shopify refund | Sage X3 credit document reference |
Scope and questions
- Do you support several Shopify stores into one X3 company?
- Yes, that pattern is common for multi-brand or multi-region selling. Each store is mapped separately so orders stay distinguishable.
- Is inventory updated in real time?
- No. Availability is published on an agreed cadence with an agreed calculation, stated in your scope.
- Does this work with Shopify Plus features?
- Which Plus capabilities are relevant — scripts, B2B, multiple stores — is confirmed in scoping against your setup rather than assumed here.
- Who maintains mappings after launch?
- APIWORX, as part of the ongoing engagement, with your approval on anything that changes accounting or pricing behaviour.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your Shopify + Sage X3 integration
Tell us your systems and documents. A specialist confirms scope by email.