X-Cart ↔ Sage 200 Integration
X-CartE-commerceSelf-hosted X-Cart talking to Sage 200 — variant SKUs, order import and stock sync on a platform you can actually get at.
X-Cart is the self-hosted e-commerce platform — PHP, your server, your database. That changes the integration economics versus hosted platforms: instead of fighting a rate-limited API, we can read its database directly, use its REST API where sensible, or hook its module layer — whichever is most reliable on your version and hosting. The Sage 200 side is the usual loop: orders to SOP, stock/prices out, despatch back. Where X-Cart earns its own page is variants — its product variants (size/colour configurations) map to Sage stock items in ways that need an explicit decision, and its module ecosystem means no two stores have quite the same order flow.
Data Flows
- 1
Orders → SOP
X-Cart orders import to Sage 200 SOP via the REST API or direct DB read — variants resolved to real SKUs, customer matching, shipping/tax/payment-state handling identical in shape to our other e-commerce links.
- 2
Variants → stock items
Each orderable variant maps to one Sage stock item (the sane default) — or to a parent item with attributes where your Sage setup genuinely works that way. The mapping table is editable data, not code.
- 3
Stock & prices → store
Sellable quantity and web price band push to X-Cart — self-hosted means no rate limits, so near-real-time stock is actually achievable if it matters for your velocity.
- 4
Despatch → tracking
Sage despatch + tracking writes back to the X-Cart order status, firing its shipped emails — the store remains the customer's source of truth.
Where These Integrations Go Wrong
The failure modes we design around — most X-Cart ↔ Sage projects hit at least two of these.
Variant mapping is the whole game
A t-shirt with 4 sizes × 6 colours is 24 orderable SKUs. If X-Cart variants don't map 1:1 to Sage stock items — or if some variants are made-to-order — the import misbooks stock. Nail the mapping model before the first order flows.
Self-hosted means your problem
DB access is a gift until the hosting box hiccups or an X-Cart upgrade moves a table. The integration health-checks its own connection and alerts — silent sync failure on a self-hosted store goes unnoticed for days.
Module interference
X-Cart stores accumulate modules that rewrite checkout, discounts and order fields. A data audit finds which modules touch the order record — custom fields from a checkout module often carry data Sage needs.
Version spread is wide
X-Cart 4 and X-Cart 5 are different platforms sharing a name — different schemas, different APIs. Scoping starts by identifying which you run; the build differs materially.
What's Included
- Order import to Sage 200 SOP (API or direct DB read, version-dependent)
- Variant ↔ Sage stock-item mapping table, editable without code
- Stock and price sync to X-Cart (near-real-time where hosting allows)
- Despatch/tracking writeback to X-Cart order status
- Module/custom-field audit and mapping
- Sync health monitoring with failure alerts
Who It's For
Sage 200 businesses on X-Cart — often long-standing stores that chose self-hosted for control, where the 'integration' is currently a nightly CSV or a staff member with two screens. Also X-Cart 4 holdouts deciding between a proper sync and a platform move.
FAQ
X-Cart 4 or 5 — does it matter?
Completely — they share a brand and little else. X-Cart 5's REST API is the clean path; X-Cart 4 usually means direct database reads. We scope off your actual version and modules, not the marketing name.
Can you read the X-Cart database directly?
Yes — self-hosted means we can query the order/product tables directly where the API is thin (common on XC4 and modified XC5 stores). Direct reads plus the API for writes is often the most robust combination.
We have custom checkout fields — will they reach Sage?
Custom order fields (delivery instructions, PO references, gift notes from checkout modules) map to Sage SOP analysis codes or order notes — whatever makes them visible to your despatch and accounts teams.
Scope Your X-Cart Build
Fixed quote once we know your Sage version, the flows you need and the volumes.