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

X12 transaction guide · Transportation

EDI 220 Logistics Service Response

The X12 document a logistics provider sends to answer a shipper's logistics service request.

Sent by
Logistics provider or carrier
Received by
Shipper
Standard
ANSI ASC X12

What is an EDI 220?

The EDI 220 Logistics Service Response is the ANSI X12 transaction set a logistics-related organization uses to send data to a shipper in response to a logistics service request (219). It confirms, modifies or declines the requested services and can return the provider's planned dates, equipment and references.

The 220 gives the shipper confidence that upcoming requirements are covered before shipments are tendered. Exceptions in the response, such as capacity shortfalls, should reach the shipper's planners while there is still time to act.

How the EDI 220 worksDiagram of the EDI 220 Logistics Service Response. Logistics provider or carrier sends it to shipper. It usually follows 219. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B9 (Beginning Segment for Logistics Services). 3 optional loops are listed by their first segment.How the EDI 220 worksLogistics Service Response: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS219Logistics Service RequestEDI 220SENDERLogistics provider orcarrierRECEIVERShipper997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AHGS … GETransaction set 220ST … SEHEADINGB9Beginning Segment for Logistics Services+ 2 optional loops, starting with:LCDN7DETAIL+ 1 optional loop, starting with:S5Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 220. Your trading partner's implementation guide adds its own requirements.
How the EDI 220 worksDiagram of the EDI 220 Logistics Service Response. Logistics provider or carrier sends it to shipper. It usually follows 219. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B9 (Beginning Segment for Logistics Services). 3 optional loops are listed by their first segment.How the EDI 220 worksLogistics Service Response: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS219Logistics Service RequestEDI 220SENDERLogisticsprovider orcarrierRECEIVERShipper997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code AH (GS … GE)Transaction set 220 (ST … SE)HEADINGB9Beginning Segment forLogistics Services+ 2 optional loops, starting with:LCDN7DETAIL+ 1 optional loop, starting with:S5Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 220. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 220, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 220 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Confirming logistics services for upcoming orders
  • Reporting changes to requested dates or capacity
  • Declining requests the provider cannot fulfill

Where it fits in the document flow

Usually follows 219 Logistics Service Request
This document 220 Logistics Service Response
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 220 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • B9
  • LCD
  • N7
  • S5
  • N1
  • LX
  • LAD
  • SE

Practical example

The 220 in practice

A logistics provider receives a 219 for a promotional shipment. It confirms the pickup dates for most orders but can only supply refrigerated trailers for part of the volume on the requested day. Its 220 confirms the accepted orders, proposes the next day for the rest and returns its reference numbers, and the shipper's planner adjusts the schedule.

Implementation

Implementation considerations for the 220

  • Reference the request and order identifiers from the 219.
  • Code exceptions clearly so they can be routed to planners.
  • Keep the confirmed plan consistent with later tenders and responses (204 and 990).
  • Monitor unanswered requests as well as declined ones.

How ECOM helps

Automate the 220 with ECOM

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 220?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us