All integrations
ERP integration

Factory Labs + Infor SX.e Integration: A Real Gateway for a Tough ERP

How Factory Labs integrates with Infor SX.e (formerly NxTrend). A first-party SX.e gateway service that translates SX.e's idiosyncratic interfaces into a normalized JSON shape the CRM reads live. No middleware. No nightly extract jobs.

Updated 2026-05-17 Β· Official Infor SX.e site

Infor SX.e (formerly NxTrend) is the ERP behind a large share of US industrial and electrical distribution. It is also one of the harder ERPs to integrate well: the API surface is older, the documentation is sparse in places, and most CRMs treat SX.e as a sync target via custom integration projects that cost hundreds of thousands of dollars and break on every SX.e patch cycle.

Factory Labs takes a different approach: a first-party SX.e gateway service maintained by our team, treated as a real product rather than a per-customer integration project.

What we support

The Factory Labs SX.e gateway works with:

  • Infor SX.e CloudSuite Distribution. The Infor-hosted modern deployment.
  • Infor SX.e on-premise. Self-hosted SX.e on Linux or Windows with the IDO Runtime accessible from the gateway.
  • SX.e 10.x and later. Includes the patches Infor has issued through 2025.

The gateway handles both modern and legacy interface surfaces (IDOs, REST APIs where exposed, the older middleware patterns) so customers do not need to do API modernization work as a prerequisite.

What the integration does

Factory's account view live-queries SX.e for:

  • Customer master. Customer, ship-to, bill-to, contact roles, payment terms, credit hold status.
  • Order history. Open orders, recent invoices, line items with quantities, prices, costs, ship-from warehouse.
  • Pricing. Customer-specific contract pricing, list pricing, quantity break tiers, special agreements.
  • Inventory. On-hand by warehouse, available-to-promise, lead times, substitute item logic.
  • Open A/R. Aging buckets, recent payments, credit hold status.
  • Item master. Item attributes, vendor data, item-warehouse rules.

Write-back: order entry from quote, customer master updates, sales rep assignment changes, case-to-RMA linking.

How it works

The SX.e gateway is a separate Factory Labs service (not part of the main CRM Lambda) because:

  1. SX.e's interface latency varies more than modern ERPs. The gateway handles retries, timeouts, and connection pooling.
  2. The IDO Runtime and legacy interfaces have specific patterns (e.g. session management, stateful filters) that benefit from a dedicated process.
  3. Per-tenant adapters are sometimes needed for customer-specific SX.e modifications. The gateway architecture cleanly contains that complexity.

The gateway:

  • Maintains a session pool against SX.e to avoid the per-request handshake overhead.
  • Translates SX.e's IDO + legacy interfaces into a normalized JSON Account / Order / Item shape.
  • Caches per-resource with TTLs tuned to SX.e's typical refresh patterns (60s for inventory, longer for pricing and master data).
  • Maps SX.e custom fields and UD (user-defined) attributes into Factory's JSONB custom-field surface automatically.
  • Surfaces SX.e errors in a structured way so reps can see "credit hold from SX.e" or "pricing exception" rather than opaque error messages.

The gateway runs in Factory's cloud per default; for high-security on-premise SX.e deployments, a customer-managed gateway container is also supported (it runs inside your network and tunnels to Factory's CRM tenant).

How to set it up

  1. Identify the SX.e endpoint. IDO Runtime URL for modern deployments, or the appropriate Infor-published API endpoint for CloudSuite.
  2. Provision a service user in SX.e. Read access to customers, orders, items, A/R. Write access to orders and customer if you want full functionality.
  3. Connect Factory. Settings β†’ Integrations β†’ ERP β†’ Infor SX.e. Paste endpoint, credentials, company code.
  4. Configure customer-specific modifications. If your SX.e has bespoke modifications (most do), the Factory team helps map custom UD fields and special workflow patterns. This is part of standard onboarding.

End to end: 1-2 weeks for a typical SX.e customer including the modifications mapping. Faster for vanilla CloudSuite deployments.

What this means for your team

  • Reps see live SX.e data without flipping to the SX.e green screen or the SX.e web portal.
  • Sales ops stops the weekly Factory-vs-SX.e reconciliation routine; there is one record.
  • IT runs no middleware tenant for the CRM-SX.e bridge.
  • Distribution operations gets a unified surface that does not require SX.e training for every new CRM user.

Pricing notes

The SX.e gateway is part of Factory Labs Growth ($45/user/month) and up. The first-party nature of the gateway means there is no per-customer integration project to pay for upfront and no maintenance retainer to keep it working through SX.e patch cycles. We handle that.

For comparison: most SX.e + Salesforce or SX.e + Dynamics 365 integration projects we have seen quoted by partners run $200,000-400,000 for the initial build, with a 20-30% annual maintenance retainer to keep it working as SX.e is patched.

Frequently asked questions

Our SX.e deployment is heavily customized. Will the integration still work? Yes, with some adapter work as part of onboarding. The gateway architecture is designed for customer-specific modifications; we have customers with substantial UD field libraries and bespoke workflow modifications running cleanly.

Does the gateway support on-premise SX.e? Yes. Two deployment patterns: gateway-in-Factory-cloud with VPN to your network, or customer-managed gateway container inside your network. The latter is the right choice for high-security deployments.

What happens at SX.e patch / upgrade time? The gateway is versioned against SX.e versions. We track Infor's release cadence and validate the gateway against new SX.e versions before customers upgrade. If a patch breaks an interface, the gateway adapts on our side; customers do not have to redo the integration.

Can we run Factory Labs alongside our existing SX.e GUI? Yes, and most customers do. Reps use Factory for customer-facing work and SX.e for accounting / warehouse-specific tasks. The two are reading the same data.

Does the gateway handle order entry into SX.e? Yes, including line-level pricing overrides, special charges, ship-from selection, and the SX.e-specific quirks around drop-ship and direct-ship orders.