Skip to main content
Back to blog
Integrations8 min read

Sage X3 + PIM: Bidirectional ITMMASTER Sync for European SMEs (2026)

Bidirectional Sage X3 ↔ PixeePIM sync via REST API: ITMMASTER, stock, prices, multi-variant. Accounting vs marketing data governance for European industrial SMEs and mid-market companies.

PixeePIM Team · 24 mai 2026

Sage X3 is the reference ERP for European industrial SMEs and mid-market companies: accounting, finance, manufacturing, purchasing, inventory, sales. As the catalog grows and sales go multi-channel, the ERP reaches its limits on product management. Marketing attributes, complex variants, media, translations, enriched e-commerce content — these aren't Sage X3's business, and trying to force them creates more friction than value. The right answer is a PIM downstream that consumes and enriches Sage X3's product data.

Why a PIM downstream of Sage X3

Sage X3 organizes product data around the ITMMASTER (item master) table. This structure is designed for logistics and accounting: item reference, accounting category, unit of measure, cost price, primary supplier, stock, sales terms. For online selling, everything marketing is missing: long SEO-optimized descriptions, structured technical attributes per channel, high-resolution images with variants per option, videos, technical documents, multilingual translations, compliance declarations.

Trying to store all that in Sage X3 is a bad idea: the structure isn't built for it, performance degrades quickly, and each catalog change requires expensive ERP development. A PIM is the dedicated tool — it consumes the Sage X3 ITMMASTER as the source of truth for the article base (SKU, EAN, accounting category, price), then enriches with everything missing to sell.

The Sage X3 ↔ PixeePIM integration: technical approach

PixeePIM exposes a bidirectional Sage X3 sync module since v6.15.0. The approach uses Sage X3's native REST API (not a fragile proprietary connector), with token authentication and automatic pagination for large catalogs.

On the pull side (Sage X3 → PixeePIM), the import covers the critical ITMMASTER fields: item reference (ITMREF), description, accounting category, tax, gross selling price, currency, unit of measure, available stock by establishment, primary supplier. Variants (size, color, configurations) are handled through the ITMMVT table with their own reference on sub-items.

On the push side (PixeePIM → Sage X3), the PIM can write back price changes, short marketing description updates (if you want to repatriate them), and publication statuses per channel. The governance rule is clear: Sage X3 remains the master for accounting and stock data, PixeePIM is the master for marketing and publication data.

Sage multi-variant: a concrete case

A typical Sage X3 textile product is represented by a parent item (the collection) with several sub-items broken down by size and color, each with its own ITMREF, its own stock, and its own price. On the e-commerce side, this product appears as a single product page with selectable variants.

PixeePIM's Sage X3 module automatically maps the Sage parent → variant hierarchy to the PIM's variant structure. You keep stock and price consistency per variant, and you can publish the e-commerce listing with the right options active based on availability. The mapping is configurable: if your Sage conventions differ (for example, independent items instead of parent-child hierarchy), matching can happen by reference and tag.

Operational workflow

In practice, the integration runs event-based through the dedicated Celery queue sage:

  • Nightly incremental import job (configurable) that pulls ITMMASTER modifications since the last sync — based on a modification timestamp on the Sage side.
  • Weekly reconciliation job that checks stock/price consistency across the entire catalog, to catch any missed events in case of network incidents.
  • On-demand push on publication changes or marketing price updates (triggered from the PixeePIM UI or via API).
  • Full structured logging of each exchange (ITMREF, operation, status, payload) for audit and debug.

Current status and support

The Sage X3 module was released to production on May 24, 2026 with PixeePIM v6.15.0. It is available and internally tested, with pilot deployments in progress at distributor customers in France and Belgium. For the first customers who want to adopt it, the PixeePIM team supports the initial mapping between your Sage X3 instance and the PIM model — typically 2-4 hours of configuration sessions depending on the complexity of your item configuration.

The module is included in all paid plansat no extra cost, following PixeePIM's usual philosophy. For customized Sage X3 configurations (custom fields, specific business workflows, complex multi-establishment), tailor-made project support is available on Enterprise.

When to make the move

The Sage X3 + PIM integration becomes relevant as soon as:

  • You have more than 1,000 active SKUs and sell on at least one e-commerce platform (Shopify, WooCommerce, Magento) or one marketplace (Amazon, Mirakl).
  • You publish your products across more than one channel and consistency drift between channels becomes a daily concern.
  • Your sales / marketing teams want to enrich product pages without involving the ERP team every time.
  • You want to prepare Digital Product Passport (DPP EU 2026-2030) compliance without storing regulatory data in Sage X3.

Connect your Sage X3 to a PIM in a few days

The PixeePIM team supports the initial Sage X3 → PIM mapping. Start on the Free plan and benefit from project support on early pilot deployments.

Request a Sage X3 demo

Stay up to date

Receive our PIM insights every month

Best practices, compliance updates, integration guides — directly in your inbox.

Subscribe for free

Free forever · No credit card

Ready to structure your product catalogue?

Try PixeePIM for free — up to 2,000 products, no commitment.