Sage Integration

Sage isn't one product

Like Microsoft Dynamics, Sage's branding covers multiple distinct ERPs with different histories, different data models, and different integration approaches. For Horizon, the relevant Sage products are:

• Sage X3 — Sage's mid-market manufacturing ERP, formerly Sage ERP X3. Used by manufacturers in the $50M-$500M range across discrete and process manufacturing.
• Sage 300cloud (formerly Sage 300 ERP / Accpac) — smaller manufacturer ERP, particularly common in North America for distribution and light manufacturing.
• Sage 200 (UK and international) — UK-focused mid-market product, similar capability tier to Sage 300cloud.
• Sage Intacct — financial-focused cloud ERP. Less common for manufacturing as the primary system but used by some service-oriented businesses with manufacturing components.

Sage X3 integration

Sage X3 is the most common Sage product among Horizon prospects, given its manufacturing focus. Integration uses three mechanisms:

• Sage X3 REST API — modern API layer covering most entities. Documented endpoints for items, inventory, sales orders, purchase orders.
• Sage X3 Web Services — older SOAP-based interface, still functional and used for some entities where REST coverage is limited.
• Direct database access — Sage X3 uses Oracle or SQL Server depending on customer deployment. For bulk historical data and analytics queries, direct view access through the customer's DBA team is often the fastest path.

Sage X3-specific data objects Horizon reads

• Product master (ITMMASTER) with planning attributes — planning policy, lead time, ABC class, safety stock
• Product site records (ITMFACILIT) for site-specific overrides
• Stock by site, location, lot, and serial
• Sales order history with customer and shipment dimensions
• Purchase order and receipt data
• BOMs (BOM and BOMD tables) with multiple BOM types (production, sales, subcontract)
• Routings with operations, work centers, and standard times
• Work center capacity and shift calendars

Sage 300cloud and Sage 200 integration

For Sage 300cloud (and the closely-related Sage 200), integration is typically through:

• Sage's REST API where available
• The Sage 300 SDK for older customizations
• Direct database access for bulk data — Sage 300's Pervasive PSQL or SQL Server databases have well-documented schemas

The planning scope for Sage 300cloud customers is typically narrower than Sage X3 — many Sage 300 customers don't run the full manufacturing module, so demand planning, inventory optimization, and replenishment cover most needs without production planning depth.

Sage Intacct integration

For the rare manufacturing customer running Sage Intacct as the primary system, integration uses Intacct's Web Services API (older SOAP interface) and the newer REST API. Intacct's data model is more financial than operational, so the planning scope is often limited unless the customer has a separate operational system.

Alternative integration path

Sage environments — particularly older Sage 300 and Sage 200 deployments without modern API surface — commonly use scheduled SFTP delivery of CSV extracts produced by Sage's reporting tools. Well-tested pattern across the Sage portfolio.

Authentication patterns

• Sage X3 (cloud or on-premise): OAuth 2.0 or token-based authentication through Sage X3's web services configuration.
• Sage 300cloud: API key or service account, depending on deployment configuration.
• Sage Intacct: Web Services API key with session-based authentication.
• Direct database access (any Sage product): Customer-provisioned read-only database user.

Write-back patterns

• Planned purchase orders for Sage X3 through PO creation APIs
• Planned production orders (Sage X3 only — other Sage products typically don't have production order entities)
• Item planning parameter updates
• Forecast records for Sage X3's MRP processes

Common Sage X3-specific considerations

• Folder structure — Sage X3's folder concept (similar to SAP's company code) defines the data segmentation. Multi-folder customers need explicit mapping during integration.
• Multi-version BOMs — Sage X3 supports multiple BOM types (production, sales, subcontract) for the same item. Integration captures the appropriate BOM for planning context.
• Standard vs special operations — Sage X3's routing structure includes both standard and special operations. The integration handles both for accurate capacity planning.
• Multi-currency and multi-legal-entity — Sage X3 is often deployed in multi-country, multi-currency configurations. Integration respects the legal entity boundaries while supporting cross-entity planning where the business model allows it.