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 215 Motor Carrier Pickup Manifest

The X12 document shippers use to give a motor carrier a manifest of all the shipments tendered to it, typically for one pickup.

Sent by
Shipper or party contracting the carrier
Received by
Motor carrier
Standard
ANSI ASC X12

What is an EDI 215?

The EDI 215 Motor Carrier Pickup Manifest is the ANSI X12 transaction set that lets shippers or other parties give a motor carrier a manifest of all the shipments tendered to that carrier. It summarizes the shipments on a pickup, such as their references, pieces and weights.

The standard distinguishes the 215 from the load tender, the legal bill of lading, the pickup notification and appointment scheduling. Carriers use the manifest to confirm what was handed over at pickup and to plan linehaul capacity.

How the EDI 215 worksDiagram of the EDI 215 Motor Carrier Pickup Manifest. Shipper or party contracting the carrier sends it to motor carrier. It usually starts the exchange. It is usually followed by 997 and 214. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B1 (Beginning Segment for Booking or Pickup/Delivery) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with SMD (Consolidated Shipment Manifest Data) and the required 0240 loop with CD3 (Carton (Package) Detail). 3 optional loops are listed by their first segment.How the EDI 215 worksMotor Carrier Pickup Manifest: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 215SENDERShipper or partycontracting the carrierRECEIVERMotor carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment214Transportation CarrierShipment Status Message2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code UPGS … GETransaction set 215ST … SEHEADINGB1Beginning Segment for Booking or Pickup/DeliveryRequired loop 0100 · repeats up to 1N1Party IdentificationDETAILRequired loop 0200 · repeats up to 999,999SMDConsolidated Shipment Manifest DataRequired loop 0240 · repeats up to 999,999CD3Carton (Package) Detail+ 3 optional loops, starting with:N1AT6Blue 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 215. Your trading partner's implementation guide adds its own requirements.
How the EDI 215 worksDiagram of the EDI 215 Motor Carrier Pickup Manifest. Shipper or party contracting the carrier sends it to motor carrier. It usually starts the exchange. It is usually followed by 997 and 214. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B1 (Beginning Segment for Booking or Pickup/Delivery) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with SMD (Consolidated Shipment Manifest Data) and the required 0240 loop with CD3 (Carton (Package) Detail). 3 optional loops are listed by their first segment.How the EDI 215 worksMotor Carrier Pickup Manifest: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 215SENDERShipper or partycontracting thecarrierRECEIVERMotor carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment214Transportation Carrier Shipment StatusMessage2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code UP (GS … GE)Transaction set 215 (ST … SE)HEADINGB1Beginning Segment for Bookingor Pickup/DeliveryRequired loop 0100 · repeats upto 1N1Party IdentificationDETAILRequired loop 0200 · repeats upto 999,999SMDConsolidated ShipmentManifest DataRequired loop 0240 · repeatsup to 999,999CD3Carton (Package)Detail+ 3 optional loops, starting with:N1AT6Blue 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 215. Your trading partner'simplementation guide adds its own requirements.

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

  • Listing all shipments handed to a carrier at a pickup
  • Daily manifests for parcel or LTL carriers
  • Reconciling shipments tendered against those picked up

Where it fits in the document flow

This document 215 Motor Carrier Pickup Manifest
Usually followed by 997 Functional Acknowledgment214 Transportation Carrier Shipment Status Message

Structure

Mandatory segments in the 215 (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
  • B1
  • N1
  • SMD
  • CD3
  • AT6
  • SLN
  • SE

Practical example

The 215 in practice

A distribution center hands 45 LTL shipments to one carrier at its daily pickup. Its shipping system sends the carrier a 215 listing each shipment's bill of lading, pieces and weight. The carrier checks the manifest against what was loaded and resolves any missing shipment before the trailer leaves the yard.

Implementation

Implementation considerations for the 215

  • Close the manifest only after loading, so it reflects what the carrier actually took.
  • Use the same shipment references as bills of lading and status messages.
  • Confirm which carriers want manifests and in which format.

How ECOM helps

Automate the 215 with ECOM

Industry

Trucking and Transportation

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

Industry

3PL and Warehousing

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

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

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

Request a Demo Contact us