Infor Distribution SX.e is a wholesale distribution ERP that runs sales and order management, materials and inventory, purchasing, financials, and customer operations on the Infor OS platform. An unofficial API lets you programmatically pull customers, sales orders, products, inventory, purchase orders, pricing, and invoices—and push updates like new orders, customer records, and purchase orders back into SX.e, even where the native ION API surface is gated or version-specific.

Infor Distribution SX.e is a wholesale distribution ERP built specifically for the needs of the evolving wholesale distribution industry. Distributors use SX.e to run enterprise-wide processes—from sales, omnichannel engagement, inventory, and warehouse management to financials—on the Infor OS platform, with integrations, analytics, mobility, and extensibility layered on top. SX.e also powers the Infor CloudSuite Distribution (CSD) offering for distributors running in the cloud.
Core functional areas include:
Common data entities:
Distributors run mission-critical order, inventory, and purchasing workloads on SX.e every day, but turning those workflows into reliable API-driven automation is non-trivial:
Supergood reverse-engineers authenticated browser flows and the Infor OS / ION API gateway to deliver a resilient, normalized API layer for your SX.e environment—whether you run on-premises or on Infor CloudSuite Distribution.
Use Infor Distribution SX.e with AI agents: Infor Distribution SX.e MCP Server →
Book a 30-minute session to confirm your modules, deployment model, and ION API authentication setup.
We deliver a production-ready SX.e adapter tailored to your distributor configuration and entitlements.
Go live with continuous monitoring and automatic adaptation as Infor Distribution SX.e evolves.
Authentication
/authenticateAuthenticate to an Infor Distribution SX.e environment via the ION API gateway using OAuth 2.0 credentials and obtain a session token for downstream calls.
Sales
/customersList customers, ship-tos, and contacts with filters for account, warehouse, status, and pricing agreement.
Sales
/ordersRetrieve sales orders, order lines, quotes, and backorders with status, customer, and date-range filters.
Sales
/create_orderCreate a new sales order against a customer using the distributor's configured product lines and pricing matrices.
Inventory
/productsPull products/parts, product lines, and warehouse inventory levels including lot and serial records.
Purchasing
/purchase_ordersList purchase orders, vendors, receipts, and replenishment recommendations across warehouses.
- Pull sales orders, order lines, and backorders from SX.e into a single warehouse or analytics layer - Stream warehouse inventory and product-line data to e-commerce and OMS platforms - Reconcile customer and ship-to records across systems for a unified order 360
- Push new sales orders and quotes into SX.e from e-commerce, EDI, or CPQ tools - Apply distributor-specific pricing matrices and customer agreements at order creation - Route returns, backorders, and credit holds to fulfillment without portal clicks
- Sync purchase orders, vendors, and receipts into procurement and AP systems - Pull replenishment recommendations to drive automated buying workflows - Match receipts against purchase orders and surface exceptions for review
- Sync invoices, payments, and AR/AP transactions into general-ledger and finance systems - Pull price sheets, cost records, and rebates for downstream pricing and margin analysis - Surface delinquent accounts and credit events to collections workflows
Authentication
ION API OAuth 2.0 credentials with password grant against the Infor OS Authorization Service, handled in a managed session
Connectivity
Infor OS / ION API gateway endpoints plus authenticated browser flows where SX.e operations aren't exposed via published APIs
Response format
Normalized JSON across Sales, Materials, Purchasing, Warehouse, and Financials objects
Rate limits
Adaptive throttling tuned to your SX.e environment to avoid ION gateway and server-side limits
Session management
Automatic OAuth token refresh, credential rotation, and re-authentication on expiry
Data freshness
Near real-time pulls for orders, inventory, and purchasing with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order status, inventory changes, purchase-order receipts, and invoice events
Latency
Sub-second reads on cached entities; multi-second writes when posting orders and purchase orders through SX.e workflows
Throughput
Horizontally scaled workers sized to distribution-grade order, pricing, and inventory volume
Reliability
Retry, backoff, and idempotency keys for order creation, purchasing, and financial transactions
Adaptation
Continuous monitoring of SX.e releases, ION API changes, and distributor-specific configuration drift
Yes. Supergood adapts to either deployment model. For on-premises SX.e we use the ION API password grant against the Infor OS Authorization Service; for CloudSuite Distribution we work against your cloud tenant's gateway, with configuration tuned to your environment.
Programmatic access flows through the Infor OS / ION API gateway, so provisioned credentials and authorization-service configuration are required. Supergood works with your existing credentials and entitlements and handles the OAuth 2.0 setup and token lifecycle for you.
Not every screen or operation has a published ION endpoint. Where coverage is partial, Supergood supplements the gateway with authenticated browser flows so you get a consistent API surface across both.
Each environment is profiled against its configured product lines, pricing matrices, warehouse setup, and customer agreements. Supergood preserves these distributor-specific fields and rules rather than forcing a generic schema.
Yes. The API supports both reads and writes—pulling customers, orders, inventory, and invoices, and pushing new sales orders, customer records, and purchase orders back into SX.e with idempotency safeguards.