How ecosio EDI for Infor M3 connects to Infor M3
API connection with real-time message status
ecosio exchanges documents with M3 over an API link rather than file drops, and exposes the processing status of each message so the sender can see whether an order was received, translated and delivered. Partner-facing formats (EDIFACT, XML and others) stay on the ecosio side; M3 sees a normalised payload.
M3 customer-order and delivery processing
Inbound orders land as M3 customer orders and outbound dispatch advices and invoices are generated from M3 delivery and invoicing data. Exactly which M3 programs and APIs are used depends on the project; ecosio's own write-up names BE-terna as the M3 customiser partner, so treat the M3 side as a per-customer implementation, not a packaged adapter.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Trading partner via ecosio | Infor M3 | Purchase order or order change | Partner sends the document; ecosio validates and forwards |
| Infor M3 | Trading partner via ecosio | Order confirmation | Customer order accepted or changed in M3 |
| Infor M3 | Trading partner via ecosio | Dispatch advice (ASN) | Delivery confirmed or shipment released |
| Infor M3 | Trading partner via ecosio | Invoice | Invoice batch run in M3 |
| ecosio | Infor M3 users | Message status and errors | Each message changes state or fails validation |
Setting it up
- 1List trading partners and documentsInventory which customers and suppliers need orders, order responses, dispatch advices and invoices, and which format and version each partner demands.
- 2Agree the M3 data contractDecide which M3 fields carry partner item numbers, ship-to identifiers, delivery terms and tax data, and where they are stored on the customer, item and address records.
- 3Build the API linkHave your M3 partner and ecosio configure the connection and the mapping between the normalised payload and M3 order and delivery structures.
- 4Map partner codesCreate cross-references for partner item numbers, units of measure, GLN or ship-to codes and payment terms before testing any documents.
- 5Test per partner in a non-production tenantRun sample orders through to dispatch advice and invoice. Each partner usually has its own certification or test sequence.
- 6Define error ownershipDecide who watches the ecosio message status screen, who fixes mapping errors, and who contacts the trading partner.
- 7Go live in wavesCut over partners one at a time, keeping the old channel available until the first invoices have been accepted.
What usually breaks
- !Partner item numbers and units of measure not cross-referenced in M3, so orders arrive but fail to create lines.
- !Dispatch advices sent before the delivery is actually confirmed, or with pack and lot data M3 has not yet captured.
- !Invoices rejected by the partner because VAT or tax codes in M3 do not match what the partner's format requires.
- !Order changes treated as new orders, creating duplicates when the partner resends a document.
- !Status shown in ecosio looks fine while the message failed to post inside M3, because nobody owns the reconciliation between the two.
- !Custom M3 fields added by the customiser partner are not documented, so a later M3 upgrade breaks the mapping.
A private AI layer across both systems
Failed-message triage
A private assistant reading ecosio message status and the M3 order tables can explain in plain language why a given order was rejected and propose the cross-reference or code that is missing, for a person to approve.
Reconciliation across both systems
Ask which partner orders in ecosio have no matching M3 customer order, or which M3 deliveries have no dispatch advice sent. The answer is a read-only comparison, shown with the query used.
Partner mapping drafts
When a new partner spec arrives, the assistant can compare it with existing mappings and draft the new cross-reference list, which a consultant reviews before it goes in.
Plain-language EDI questions
Planners and customer service ask 'where is order 4711 from this customer' and get the answer from both systems without opening two screens, with answers limited to the asker's M3 roles.
Try it here, free
Infor M3 Customer Order Status Tracking Worksheet
Document what each customer order status means in your M3 setup, stage by stage, and share it with the order desk.
When something else fits better
- Infor's own EDI managed service over ION, if you want a first-party route and already run ION.
- A different managed EDI provider with an M3 connector, which is worth comparing if your partners are mainly North American rather than European.
- For one or two low-volume partners, a portal or flat-file exchange may be enough and avoids a managed-service contract.
Frequently asked questions
Is ecosio an Infor product?
No. ecosio is an independent European EDI managed-service provider that publishes an integration approach for Infor M3. It is separate from Infor's own EDI managed service, which connects through ION. Which one fits depends on your trading partners, region and existing Infor integration footprint.
Does ecosio run on-premises?
ecosio is a managed service, so the EDI translation and partner connectivity run on the provider's side. Your M3 can still be on-premises; the API link is the boundary. If your policy forbids documents leaving your network, confirm the data handling terms before choosing a managed service.
What does real-time status give me?
It shows where each message is in its life: received, translated, delivered or failed. That cuts the guesswork when a partner says they never got an invoice. You still need an owner to reconcile the status against what actually posted in M3.
Who customises the M3 side?
ecosio's integration write-up names BE-terna as an M3 customiser partner. In practice any M3 partner or your internal team can do it, as the mapping and any extra fields are specific to your configuration.
Pairing documented at ecosio.com/en/blog/edi-integration-with-infor-m3/ . ecosio EDI for Infor M3 is a product of ecosio; Netray is independent and not affiliated with either vendor.