Do we need to remove our existing WooCommerce plugins?

Not necessarily. We review which plugins touch orders, stock or accounting during scoping, and agree what stays. Where a plugin conflicts with the integration, we say so before build.

How often is stock published?

On a cadence agreed in scoping and stated in your scope document. We do not claim real-time stock on this page.

Can several stores feed one X3 company?

Yes, that is a common pattern. Each store is mapped separately so orders remain distinguishable in X3.

APIWORX works the exception queue and escalates to your named contacts when a business decision is required.

Storefront · Sage X3

Sage X3

WooCommerce

Connect Sage X3 + WooCommerce

Automate sales order, customer record, product / item data, stock availability, despatch and tracking between Sage X3 and WooCommerce — with monitoring and managed support from APIWORX.

See How It Works

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 WooCommerce.

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 WooCommerce, 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.

Order-to-cash automation Inventory synchronization

How it works

From requirements to a managed integration

Tell Us What You’re Connecting

Provide the systems, workflow and business requirements.

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 teams running Sage X3 with a WooCommerce store that has outgrown plugin-and-spreadsheet handling.

What needs to be in place

A WooCommerce store with REST API access and a stable plugin set.
Sage X3 with API access and a service user permitted to create the documents in scope.
Agreed rules for which items and warehouses the store may publish availability from.
A named owner on your side for pricing, tax and item-master decisions.

When you may not need this

If your store takes a few orders a day and one person keys them in comfortably, a plugin export may be enough. This is for teams where order volume, stock accuracy or item complexity has made manual handling a daily cost.

What is out of scope

APIWORX does not maintain your WooCommerce plugins, theme or hosting.
Stock publishing cadence is agreed in scoping; this page does not claim continuous real-time stock.
Payment gateway reconciliation is scoped separately where your gateway data supports it.

What actually moves, and who owns it

A representative WooCommerce and Sage X3 scope. Objects and direction are confirmed per customer before build.

Sage X3APIWORX (mapping, retries, exception queue)WooCommerce

Objects exchanged between Sage X3 and WooCommerce, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Sales order	WooCommerce	Sage X3	WooCommerce at capture	Order reaches an agreed status	Held in exception queue with the validation error	APIWORX
Customer record	WooCommerce	Sage X3	Agreed per customer type	New or changed customer on an order	Unmatched customer raises a named exception	APIWORX
Product / item data	Sage X3	WooCommerce	Sage X3	Item or attribute change	Retried, then queued with the rejected field	APIWORX
Stock availability	Sage X3	WooCommerce	Sage X3	Agreed publishing cadence	Last published figure retained; exception raised	APIWORX
Despatch and tracking	Sage X3 or warehouse	WooCommerce	Despatch record	Order despatched	Retried, then queued for review	APIWORX
Refund / credit	WooCommerce	Sage X3	Agreed in scoping	Refund approved	Held for finance review	APIWORX (delivery) / you (approval)

Three decisions that make or break this integration

Orders that arrive complete

Most WooCommerce-to-ERP pain is not the happy path, it is the order with a missing tax code, an unrecognised SKU or a discount nobody mapped. Validation happens before posting, so a bad order becomes a named exception instead of a wrong document in X3.

Required fields validated against X3 expectations before the document is created.
Discounts, shipping charges and tax mapped to agreed X3 treatment.
Unmapped SKUs stop the line rather than being posted to a catch-all item.
Orders held by fraud or payment review only move when they reach the agreed status.

Stock published on a rule you chose

Availability is calculated from the warehouses and stock statuses you nominate, then published on an agreed cadence. That makes overselling a rule you can change rather than a mystery to investigate.

Warehouse inclusion and buffer rules documented per item or group.
Backorder and pre-order behaviour handled explicitly.
Cadence stated in your scope; no real-time promise is made here.
A failed publish preserves the last figure and raises an exception.

Fulfilment and returns your customers can see

Despatch confirmations and tracking flow back to WooCommerce so customers and support see the same status your warehouse does. Refunds and credits post under the treatment finance agreed, not whatever a plugin defaults to.

Tracking references written back to the store order for customer notifications.
Partial shipments handled as separate confirmations where your process allows.
Refunds mapped to the agreed X3 credit treatment.
Return-related stock movements confirmed in scoping rather than assumed.

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 WooCommerce and Sage X3.

How an order is traced
WooCommerce order number	Sage X3 sales order number
Store customer email	Sage X3 customer account
Warehouse despatch record	Tracking reference on the store order
Store refund record	Sage X3 credit document reference

Scope and questions

Do we need to remove our existing WooCommerce plugins?: Not necessarily. We review which plugins touch orders, stock or accounting during scoping, and agree what stays. Where a plugin conflicts with the integration, we say so before build.
How often is stock published?: On a cadence agreed in scoping and stated in your scope document. We do not claim real-time stock on this page.
Can several stores feed one X3 company?: Yes, that is a common pattern. Each store is mapped separately so orders remain distinguishable in X3.
Who owns exceptions?: APIWORX works the exception queue and escalates to your named contacts when a business decision is required.