972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

Guides

Infor M3 EDI integration guide: M3 APIs, ION and Enterprise Collaborator

How manufacturers and distributors connect Infor M3 to EDI trading partners through M3 APIs, Infor ION and M3 Enterprise Collaborator.

2 min read · Updated October 19, 2026

The short answer

Infor M3 connects to EDI through an integration layer that translates partner documents. Data reaches M3 through M3 APIs, such as the customer order API, through Infor ION using Business Object Documents, or through M3 Enterprise Collaborator (MEC) mappings in many existing landscapes. Deliveries and customer invoices drive outbound ship notices and invoices.

How EDI flows through Infor M3Sequence diagram for Infor M3. The trading partner sends a 850 purchase order to the integration layer, which translates and validates it and create the customer order through M3 APIs such as OIS100MI, Infor ION BODs or M3 Enterprise Collaborator. In Infor M3, item aliases map customer and GTIN numbers; deliveries and customer invoices are created. Delivery and customer invoice, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through Infor M3The integration layer translates; Infor M3 keeps the business recordsTrading partnerIntegration layerInfor M3850 purchase orderTranslate and validateCross-references turn partner codes into your items and locationsCreate the customer orderThrough M3 APIs such as OIS100MI, InforION BODs or M3 Enterprise CollaboratorItem aliases map customer and GTIN numbers; deliveries andcustomer invoices are createdDelivery and customer invoice856 ship notice and 810 invoiceInterfaces and objects as described in this guide. Your version, licensing and partner requirements decide which ones apply.
How EDI flows through Infor M3Sequence diagram for Infor M3. The trading partner sends a 850 purchase order to the integration layer, which translates and validates it and create the customer order through M3 APIs such as OIS100MI, Infor ION BODs or M3 Enterprise Collaborator. In Infor M3, item aliases map customer and GTIN numbers; deliveries and customer invoices are created. Delivery and customer invoice, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through InforM3The integration layer translates; Infor M3 keepsthe business recordsTradingpartnerIntegrationlayerInfor M3850 purchase orderTranslate and validateCross-references turnpartner codes into youritems and locationsCreate the customer orderThrough M3 APIs such asOIS100MI, Infor ION BODsor M3 Enterprise CollaboratorItem aliases mapcustomer and GTINnumbers; deliveriesand customer invoicesare createdDelivery and customerinvoice856 ship notice and 810invoiceInterfaces and objects as described in this guide.Your version, licensing and partner requirementsdecide which ones apply.

Read the diagram from top to bottom. Infor M3 does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and Infor M3 creates and posts the business records. Outbound documents are built from what Infor M3 actually recorded.

Expand diagram Download SVG

How EDI connects to Infor M3

Infor M3 serves manufacturers and distributors in industries such as food and beverage, fashion, equipment and chemicals. Many trade EDI with large retailers and global suppliers. An integration layer handles partner connectivity and translation; M3 receives and provides data through M3 APIs, Infor ION or M3 Enterprise Collaborator (MEC).

Document mapping

EDI documentDirectionM3 object
850 purchase orderInboundCustomer order
860 order changeInboundCustomer order changes
855 acknowledgmentOutboundOrder confirmation
856 ship noticeOutboundDelivery
810 invoiceOutboundCustomer invoice

Integration options

  • M3 APIs: function-based programs such as the customer order API (OIS100MI) for creating order headers and lines, plus APIs for reading deliveries and invoices.
  • Infor ION: message-based integration using Business Object Documents (BODs), with workflows and monitoring in ION. Central in Infor’s multi-tenant cloud.
  • M3 Enterprise Collaborator (MEC): mapping and messaging used in many existing B2B landscapes. Review existing MEC mappings before a cloud move, because they often contain years of partner logic.

Partner data

  • Customer records hold partner identifiers and order defaults.
  • Item alias numbers map customer and GTIN item numbers to M3 items.
  • Delivery addresses store store, distribution center and plant codes.
  • Order types can separate EDI orders and apply partner-specific defaults.

Deliveries and ship notices

Ship notices are built from M3 deliveries and their packages. Retail partners need carton detail and GS1-128 labels, so align packing and labeling in the warehouse with the ship notice data.

Best practices

  • Inventory existing MEC mappings and partner rules before upgrades or cloud migration.
  • Validate customers, items and prices before creating customer orders.
  • Use order types and defaults instead of custom code where possible.
  • Monitor ION and API errors daily and route business errors to owners.
  • Plan EDI early in migrations. See the ERP migration checklist.
Infor M3 integration and implementationIntegration methods, document mappings and ECOM services for Infor M3.

Frequently asked questions

What is M3 Enterprise Collaborator?

M3 Enterprise Collaborator (MEC) is a mapping and messaging component that has long been used to exchange business documents with M3, including documents from EDI translators.

What are M3 APIs?

M3 APIs are function-based programs, usually named with an MI suffix, that read and update M3 data. For example, OIS100MI is used to create and maintain customer orders.

Should we use ION or M3 APIs for EDI?

ION suits message-based flows and is central in Infor's cloud architecture. M3 APIs give direct, fine-grained control. Many integrations combine both, and existing MEC mappings may be reused or migrated.

Keep learning

Related

ERP

Infor M3 integration

EDI integration for Infor M3 through M3 APIs, Infor ION and M3 Enterprise Collaborator.

 industries

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

 services

ERP Implementation

ERP implementation for SAP, Oracle, Microsoft, NetSuite, Infor, Epicor, QAD and Sage, with B2B integration built in.

 Guide

ERP migration and EDI: a checklist for keeping trading partners running

How to move EDI and trading partner integrations to a new ERP without disrupting orders, shipments and payments.

 Transaction guide

EDI 856 Advance Ship Notice

The X12 document a supplier sends before delivery to describe exactly what is in a shipment, down to cartons and items.

Have an EDI question we did not answer?

ECOM's integration specialists can review your partners, documents and systems and recommend next steps.

Request a Demo Contact us