Exact Online and Orderful integration

What moves between them

Purchase orders and purchase order lines flow from Exact Online into Orderful as EDI 850 documents, tagged with the supplier ISA identifier and your company ISA ID so Orderful routes them correctly to the supplier. When goods are dispatched in Exact, goods deliveries flow into Orderful as EDI 856 ship notices. Exact accounts (filtered for IsSupplier=true) are mapped to Orderful ISA identifiers so each supplier receives documents destined for their ISA. The sync runs on a daily schedule or responds to Exact webhooks for purchase orders and goods deliveries, whichever is enabled.

How ml-connector handles it

ml-connector stores both Exact OAuth credentials and Orderful API key encrypted and refreshes the Exact access token when it expires (every 10 minutes). It polls or listens for Exact purchase orders and goods deliveries, then fetches full entity details via the REST API since Exact webhooks only provide entity keys. It maps Exact division IDs and supplier account numbers to Orderful ISA identifiers from a pre-configured routing table (one ISA per supplier). For each purchase order, it constructs an EDI 850 document with the supplier ISA as receiver, your company ISA as sender, line items from purchase order lines, and quoted delivery dates. For each goods delivery, it constructs an EDI 856 document with the same ISA routing and item quantities. It posts the EDI documents to Orderful's /v4/create endpoint, tagged test or live depending on the environment. It tracks Exact's 30-day refresh token expiry and surface renewal warnings so an outage does not occur when the token is revoked. Every record carries a full audit trail and can be replayed if an Orderful call fails.

A real-world example

A mid-sized food distribution company uses Exact Online to manage purchasing and order fulfillment across two warehouses in the Netherlands and Belgium. Before the integration, when a purchase order was created in Exact, the procurement team exported it and sent it as an EDI 850 file via email or manual FTP to each supplier. With Exact Online and Orderful connected, purchase orders created in Exact are automatically transformed into EDI 850 documents and routed through Orderful to the right supplier based on the supplier account setup, eliminating the manual export step. When goods arrive and are received in Exact, the goods delivery is automatically converted to an EDI 856 ship notice so suppliers confirm receipt. The procurement team saves hours per week on manual document handling and suppliers get EDI documents in a consistent, machine-readable format.

What you can do

• •Transform Exact Online purchase orders into EDI 850 documents and route them to suppliers through Orderful based on supplier ISA identifiers.
• •Post Exact goods deliveries as EDI 856 ship notices to Orderful so suppliers confirm goods receipt.
• •Map Exact Online supplier accounts to Orderful ISA identifiers so each supplier receives documents routed to their ISA.
• •Authenticate Exact Online with OAuth tokens (10-minute refresh cycle) and Orderful with API key, handling token expiry and renewal.
• •Sync purchase orders and goods deliveries on a daily schedule or via Exact webhooks, with retries and a full audit trail.

Questions

Which direction does data move between Exact Online and Orderful?

Data flows from Exact Online into Orderful. Purchase orders and purchase order lines are transformed into EDI 850 documents, and goods deliveries are transformed into EDI 856 ship notices. Both are routed to suppliers through Orderful using ISA identifiers. No data flows back from Orderful into Exact.

How does ml-connector map Exact suppliers to Orderful ISA identifiers?

A pre-configured routing table maps each Exact supplier account number to the supplier's Orderful ISA identifier (sender ISA). Your company's ISA identifier is configured once and used as the receiver on all outbound EDI documents. When a purchase order is created for a supplier in Exact, ml-connector looks up the supplier's ISA and constructs the EDI 850 with the correct sender and receiver.

Does the integration handle Exact's 10-minute token expiry and 30-day refresh token rotation?

Yes. ml-connector refreshes the Exact access token before each API call (automatic refresh when a call returns 401), and it tracks the 30-day refresh token expiry so you can renew your app registration before the token is revoked. If the refresh token expires, ml-connector surfaces an alert so the integration can be re-authorized without downtime.