When you build an EDI integration on Chain.io, you configure an adapter by its display name (for example, "Chain.io 310 EDI"), but the JSON you map against is defined by a Chain.io specification. This article is the lookup between the two: start from the X12 transaction set or EDIFACT message you exchange, find the adapter you configure for it, and open the specification to see the exact JSON shape that adapter uses, with the full field reference and a worked example.
A few transaction sets map to more than one adapter because there is more than one way to handle them. The 204, for instance, has both a load-tender adapter and a newer shipment adapter, and the 856 can be produced as either an ASN or a shipment. Pick the adapter that matches the flow you are configuring.
X12
| EDI Transaction Set | X12 Name | Adapter | Specification |
|---|---|---|---|
110 | Air Freight Details & Invoice | Chain.io 110 EDI | Freight Invoice EDI |
204 | Motor Carrier Load Tender | Chain.io 204 EDI (Legacy Load Tender) | Load Tender EDI |
204 | Motor Carrier Load Tender | Chain.io 204 EDI | Shipment |
210 | Motor Carrier Freight Details & Invoice | Chain.io 210 EDI | Freight Invoice EDI |
214 | Transportation Carrier Shipment Status | Chain.io 214 EDI | Shipment Status EDI |
214 | Transportation Carrier Shipment Status | Infor Nexus 214 | Shipment Status EDI |
300 | Reservation (Booking Request) (Ocean) | Chain.io 300 EDI | Shipment |
301 | Confirmation (Ocean) | Chain.io 301 EDI | Shipment |
304 | Shipping Instructions | Chain.io 304 EDI | Shipment |
309 | Customs Manifest | Chain.io 309 EDI | Shipment |
310 | Freight Receipt & Invoice (Ocean) | Chain.io 310 EDI | Freight Invoice EDI |
315 | Ocean Shipment Status Details | Chain.io 315 EDI | Shipment Status EDI |
315 | Ocean Shipment Status Details | Chain.io 315 EDI (Standard Shipment) | Shipment |
315 | Ocean Shipment Status Details | Infor Nexus 315 | Shipment Status EDI |
810 | Invoice | Chain.io 810 EDI | Freight Invoice EDI |
850 | Purchase Order | Chain.io 850 EDI | Purchase Order |
856 | Ship Notice / Manifest | Chain.io 856 EDI | ASN EDI |
856 | Ship Notice / Manifest | Chain.io 856 EDI (Standard Shipment) | Shipment |
860 | Purchase Order Change Request | Chain.io 860 EDI | Purchase Order |
888 | Item Maintenance | Chain.io 888 EDI | Product |
940 | Warehouse Shipping Order | Chain.io 940 EDI | Purchase Order |
940 | Warehouse Shipping Order | EDI JSON 940 Warehouse Order | Warehouse Order EDI |
943 | Warehouse Stock Transfer Shipment Advice | Chain.io 943 EDI | Purchase Order |
944 | Warehouse Stock Transfer Receipt Advice | Chain.io 944 EDI | Purchase Order |
945 | Warehouse Shipping Advice | Chain.io 945 EDI | Shipment |
945 | Warehouse Shipping Advice | Chain.io 945 EDI | Warehouse Shipping Advice EDI |
990 | Response to a Load Tender | Chain.io 990 EDI | Booking Response EDI |
EDIFACT
EDIFACT adapters are named by their message type. As with X12, the adapter converts between the EDIFACT message and the Chain.io specification listed below, so map against that spec for the adapter you are configuring.
| EDIFACT Message | Message Name | Adapter | Specification |
|---|---|---|---|
APERAK | Application Error & Acknowledgement | Chain.io EDIFACT EDI APERAK | Shipment Status EDI |
IFCSUM | Forwarding & Consolidation Summary | Chain.io EDIFACT EDI IFCSUM | Freight Invoice EDI |
IFTMAN | Arrival Notice | Chain.io EDIFACT EDI IFTMAN | Shipment EDI |
IFTMBC | Booking Confirmation | Chain.io EDIFACT EDI IFTMBC | Booking Response EDI |
IFTMIN | Forwarding & Transport Instruction | Chain.io EDIFACT EDI IFTMIN | Shipment EDI |
IFTSTA | Multimodal Status Report | Chain.io EDIFACT EDI IFTSTA | Shipment Status EDI |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article