Integrations
One integration hub, two directions. Items, stock, sales and suppliers come in. Approved purchase orders and their statuses go out. Nothing is retyped.
Native connector in production with a Moroccan luxury cosmetics distributor. Items, stock by warehouse and transit warehouse « DI », invoiced sales, supplier purchase orders, order creation with IRIS reference and status return.
Connector through the integration hub for multi-company and multi-site groups. Same flows as Sage 100cloud, with site and legal-entity mapping.
Connector via Odoo's XML-RPC / JSON-RPC API, versions 15 and above. Products and variants, stock quants by location, sales orders and invoices, purchase orders and receipts.
Business Central and Finance & Operations through the standard OData and REST APIs. Items, locations, item ledger, sales and purchase documents.
Connector via the Service Layer API. Items, warehouses, batches, A/R invoices, purchase orders and goods receipts.
Connector via SuiteTalk REST. Items, locations, inventory balances, sales transactions, purchase orders.
For any ERP without an API or when IT prefers file exchange. Scheduled pulls from an SFTP folder, validated against a documented file layout, with rejection reports.
A documented REST API to push data to IRIS and read forecasts, proposals and order statuses. OpenAPI specification and sandbox environment available.
Daily or intraday sell-out from your point-of-sale system when sales are not invoiced in the ERP.
Quoted on request after a short integration study. Most systems are connected through the REST API or CSV / SFTP within the standard onboarding time.
Your ERP feeds IRIS several times a day: items, stock by warehouse and transit warehouse, invoiced sales, supplier purchase orders. Sage 100cloud, Sage X3, Odoo, Microsoft Dynamics 365, SAP Business One, Oracle NetSuite, or scheduled CSV / SFTP imports.
Four steps, handled by IRISYS with your IT team. Read access first, write access only after the parallel run.
You create an ERP account for IRIS with read rights on items, stock, sales and suppliers. Credentials are stored encrypted.
Warehouses, transit warehouses, stores, brands and categories are mapped to IRIS objects. Testers and GWP item codes are identified.
Twelve to twenty-four months of history are imported and checked: duplicates, negative stock, missing categories.
After the parallel run, write rights are granted for purchase orders and transfers only. Every transmission is logged.
The standard flows for every ERP connector. Field names below use Sage 100cloud vocabulary as an example; the mapping is adapted per ERP.
| Flow | Direction | Frequency | Content |
|---|---|---|---|
| Items | ERP → IRIS | Every 4 hours | Reference, description, brand, category, family, barcode, case pack, status, variants (shades, sizes). |
| Stock by warehouse | ERP → IRIS | Every 4 hours | Physical stock and reserved stock per warehouse and per store, batches and expiry dates when managed. |
| Transit warehouses (« DI ») | ERP → IRIS | Every 4 hours | Goods in transit between the central warehouse and stores, deducted from the need before proposing. |
| Invoiced sales | ERP → IRIS | Daily, intraday optional | Sales lines per SKU, store, date, quantity, net price, promotion flag. |
| Suppliers and lead times | ERP → IRIS | Daily | Supplier master, contractual lead time, minimum order quantity. Real lead time and service level are recomputed from receipts. |
| Purchase orders | IRIS → ERP | On validation | Approved order proposals created as purchase orders with the IRIS reference, supplier, store or warehouse, lines and quantities. |
| Order statuses | ERP → IRIS | Every hour | Created, prepared, shipped, received. Partial receipts update the in-transit quantity. |
| Inter-store transfers | IRIS → ERP | On validation | Transfer proposals validated by the planner, created as transfer orders. |
An integration is only as good as what happens when it fails.
Every failed call is retried with exponential back-off. Transient ERP unavailability never loses an order.
When an order cannot be created after the retries, the planner and the administrator receive an alert in IRIS and by email, with the ERP error message.
Any failed transmission can be resent from the order screen once the cause is fixed. Every attempt is written to the audit log.
CSV / SFTP files are validated line by line. Rejected lines are listed in a report with the reason, and accepted lines are loaded.
Send us an anonymised sales export. We show you your forecasts and order proposals within 10 days.
