Infor SX.e
Infor SX.e is the leading ERP for wholesale distributors, covering purchasing, inventory management, pricing, and customer financials for distributor customers across electrical, plumbing, HVAC, and industrial verticals. Infor SX.e routes all third-party API calls through the Infor ION API gateway.
What you can do
Read and write sales orders
Pull open, confirmed, and shipped sales orders by customer, branch, or date range. Create new orders and update existing line items including pricing and ship-to addresses.
Sync customer and contact records
Read customer master data including account type, credit limit, pricing class, and assigned sales rep. Write back updated contact details and credit status from your product.
Query inventory availability
Check on-hand quantities, available-to-promise stock, and bin locations across multiple warehouses. Askel handles SX.e's branch and warehouse hierarchy so your product sees accurate availability by location.
Read purchase orders and receipts
Pull open POs by vendor and expected receipt date. Read incoming receipts as they are posted to keep your product's inbound pipeline up to date.
Sync vendor and product master data
Read vendor records, product lines, and pricing matrices including customer-specific pricing contracts. Askel normalizes SX.e's pricing structure so your product can display correct prices without understanding SX.e's pricing tier logic.
Access AR invoices and payment data
Read open AR invoices, payment history, and customer aging data. Useful for credit-management or collections products that need to surface outstanding balance information.
Surfacing SX.e inventory data in a distributor's ecommerce storefront
Halloran Electrical Supply runs their wholesale distribution business on SX.e and has recently launched an ecommerce storefront using your B2B commerce platform. When a buyer searches for a product, they need to see real-time inventory levels from SX.e's warehouse network rather than stale cached quantities.
- 1
Export the .ionapi file from Infor OS Portal
Halloran's IT admin logs into the Infor OS Portal, navigates to the ION API settings, and creates a service account for the Askel integration. The portal generates a .ionapi JSON file containing the OAuth token endpoint, client credentials, and tenant routing parameters. The admin downloads and saves this file.
- 2
Upload the .ionapi file to Askel
Halloran's admin uploads the .ionapi file into the Askel setup screen inside your commerce platform. Askel parses the file, extracts the OAuth endpoints and credentials, and requests an access token from the ION gateway. A successful connection is confirmed by fetching a product availability sample.
- 3
Schema discovery
Askel reads the available SX.e endpoints through the ION gateway and identifies the Inventory, Product, Customer, and SalesOrder objects along with any custom fields Halloran has added. Your CS team sees a mapping draft within minutes.
- 4
Map and validate
Halloran uses a custom availability-code field to indicate supplier lead times. A CS rep maps this field to the storefront's 'estimated ship date' display and runs a dry-run against 200 SKUs to verify the quantities and availability codes match what Halloran's buyers expect to see.
- 5
Go live
Real-time inventory lookups are enabled. When a buyer searches the storefront, Askel queries Halloran's SX.e branch inventory and returns current on-hand and available-to-promise quantities. Out-of-stock and low-stock alerts appear automatically based on the SX.e data.
Service account
The customer's Infor OS Portal admin creates a service account and exports a .ionapi JSON file containing the ION OAuth token endpoint, client ID, client secret, and tenant routing data. Askel parses this file, requests a Bearer token from the ION gateway, and refreshes it automatically. No user passwords are stored.
How Askel sits between your product and the customer's system
FAQ for Infor SX.e
Is the .ionapi file the same format as for other Infor CloudSuite products?+
Does this work with both SX.e Cloud and on-premises SX.e deployments?+
What ION API authorizations does the service account need?+
What happens when a customer upgrades their SX.e version?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.