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 219 Logistics Service Request

The X12 document a shipper sends a logistics provider with order detail relevant to upcoming transportation requirements.

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

What is an EDI 219?

The EDI 219 Logistics Service Request is the ANSI X12 transaction set a shipper uses to send a logistics-related organization the order detail relevant to upcoming transportation requirements. It describes what will need to move, from where and to where, and when, so the provider can plan capacity and services.

The logistics provider answers with a 220 logistics service response. Unlike a load tender (204), which offers a specific shipment to a carrier, the 219 shares upcoming demand for planning.

How the EDI 219 worksDiagram of the EDI 219 Logistics Service Request. Shipper sends it to logistics provider or carrier. It usually starts the exchange. It is usually followed by 220 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B9 (Beginning Segment for Logistics Services) and B9A (Service Request) and summary: L3 (Total Weight and Charges). 2 optional loops are listed by their first segment.How the EDI 219 worksLogistics Service Request: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 219SENDERShipperRECEIVERLogistics provider orcarrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY220Logistics ServiceResponse997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code ABGS … GETransaction set 219ST … SEHEADINGB9Beginning Segment forLogistics ServicesB9AService Request+ 1 optional loop, starting with:N7DETAIL+ 1 optional loop, starting with:S5SUMMARYL3Total Weight and ChargesBlue 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 219. Your trading partner's implementation guide adds its own requirements.
How the EDI 219 worksDiagram of the EDI 219 Logistics Service Request. Shipper sends it to logistics provider or carrier. It usually starts the exchange. It is usually followed by 220 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B9 (Beginning Segment for Logistics Services) and B9A (Service Request) and summary: L3 (Total Weight and Charges). 2 optional loops are listed by their first segment.How the EDI 219 worksLogistics Service Request: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 219SENDERShipperRECEIVERLogisticsprovider orcarrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY220Logistics Service Response997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code AB (GS … GE)Transaction set 219 (ST … SE)HEADINGB9Beginning Segment forLogistics ServicesB9AService Request+ 1 optional loop, starting with:N7DETAIL+ 1 optional loop, starting with:S5SUMMARYL3Total Weight and ChargesBlue 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 219. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 219, 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 219 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

  • Giving a logistics provider advance notice of shipping requirements
  • Sharing order detail for transport planning
  • Requesting logistics services for upcoming orders

Where it fits in the document flow

This document 219 Logistics Service Request
Usually followed by 220 Logistics Service Response997 Functional Acknowledgment

Structure

Mandatory segments in the 219 (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
  • B9A
  • N7
  • S5
  • N1
  • G61
  • LH1
  • LX
  • LAD
  • L3
  • SE

Practical example

The 219 in practice

A retailer's supplier expects a large promotional order to ship in three weeks. It sends its third-party logistics provider a 219 with the order details, ship-from location, destinations, expected weights and pallet counts and the target ship dates. The provider replies with a 220 confirming the service and planned capacity.

Implementation

Implementation considerations for the 219

  • Send requests early enough for the provider to plan capacity.
  • Use order references that later tenders and shipments will carry.
  • Agree how changes to the requirement are communicated.
  • Distinguish the 219 planning request from the 204 shipment tender.

How ECOM helps

Automate the 219 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

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 219?

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

Request a Demo Contact us