EDI 215 Motor Carrier Pickup Manifest for High-Volume Shippers

The LTL carrier's driver backs onto door 14 at 17:30, loads for forty minutes and leaves with a stack of signed bills of lading. The warehouse system marks 42 shipments as shipped. A week later the carrier invoices 41 PROs, a customer files a shortage claim for nine cartons that never left the dock, and nobody can prove which count was right at 18:10 that evening.

The X12 215 Motor Carrier Pickup Manifest exists to settle that question before the truck leaves. Sent once per pickup, it lists every shipment and carton the shipper expects the carrier to take, so the dock, the carrier's status messages and the freight bill can all be checked against one agreed count. Used well, it turns a daily pickup from a stack of paper into a reconciled event.

• What this guide covers: what the 215 is for and what it is not, the header, shipment and carton loops, when to use a manifest instead of a per-load tender, pickup count reconciliation, and how the same pickup meets e-way bill rules in India.
• What it adds: an annotated 215 sample, a dock-door incident traced minute by minute, a worked day's pickup reconciled in dollars and rupees, and a carrier go-live checklist.

What a 215 tells the carrier that a load tender never does

A 215 is a list, not an offer. X12 describes it as a way to provide a motor carrier with a manifest of all shipments tendered to that carrier, and states that it should not be used for load tenders, legal bills of lading, pickup notifications or appointment scheduling.

That boundary separates it from the 204 Motor Carrier Load Tender. A 204 asks a carrier to accept a specific load and expects a 990 response, which is why our article on 204 load tender and 990 response architectures focuses on acceptance timeouts and rate locks. A 215 assumes the carrier is already coming, usually on a standing daily pickup, and tells it exactly what should be on the dock.

• Typical users: distribution centres with a scheduled LTL or parcel pickup that carries dozens or hundreds of shipments a day, each with its own bill of lading and PRO number.
• What it replaces: a printed pickup manifest or end-of-day summary that the driver signs, which cannot be matched automatically against the carrier's status events or invoices.
• What it does not replace: the bill of lading or receipt for each shipment. Under 49 CFR 373.101, a for-hire, non-exempt motor carrier must issue a receipt or bill of lading showing consignor and consignee, origin and destination, number of packages, freight description and, where it affects rating, weight.

Because the manifest has no legal standing as a receipt, its value is entirely in reconciliation. If the shipper sends it but nobody compares it with what the carrier reports, the 215 becomes one more file in the EDI archive.

Header segments: purpose code, carrier SCAC and manifest number

In version 004010, which many shippers and carriers still exchange, the 215 opens with B2A for the purpose, BLR for the carrier's SCAC and date, and a mandatory L11 carrying the manifest number. Later releases restructure the header around a B1 segment, so confirm the version in the trading partner agreement before mapping.

• B2A, set purpose: B2A-01 uses element 353, where 00 means Original, 01 Cancellation, 04 Change and 05 Replace. Decide with the carrier whether a late addition is sent as a change or as a full replacement manifest.
• BLR, carrier identification: BLR-01 is the Standard Carrier Alpha Code of the pickup carrier and BLR-02 the date in CCYYMMDD format. One manifest should name one carrier.
• L11, manifest reference: the header L11 is mandatory in 004010; qualifier MA, Ship Notice/Manifest Number, is the natural choice for the shipper's manifest ID.
• Ship-from loop 0100: N1 with entity code SF, Ship From, plus N3 and N4 address lines and an L11 that can carry the dock, using qualifier DK for Dock Number.

An X12 004010 215 Motor Carrier Pickup Manifest identifies one pickup through B2A-01 purpose code 00 for an original, BLR-01 carrier SCAC, and a header L11 with qualifier MA holding the shipper's manifest number, so every later status, receipt and invoice line can be reconciled to a single count.

Shipment and carton loops: SMD, ship-to parties and CD3 lines

Below the header, each shipment opens a 0200 loop with an SMD segment, and each carton or handling unit within it opens a 0240 loop with a CD3 segment. That nesting is what makes a 215 countable: shipments are the SMD loops, cartons are the CD3 loops.

SMD-01 carries the service level code and SMD-02 the shipment method of payment, such as PP for Prepaid (by Seller), CC for Collect or TP for Third Party Pay. Shipment-level L11 segments should carry the bill of lading number with qualifier BM and the purchase order with PO, because those are the keys the carrier's 214 and 210 will echo back.

ST*215*0412~
B2A*00~
BLR*ABCD*20261112~
L11*M20261112DC07*MA~
N1*SF*NORTHGATE DC 07~
N3*4410 DISTRIBUTION PKWY~
N4*MEMPHIS*TN*38118~
L11*14*DK~
SMD*SG*PP~
L11*BOL7781203*BM~
L11*PO55219*PO~
N1*ST*RIVERSIDE HARDWARE 112~
N4*NASHVILLE*TN*37210~
CD3*G*412.5~
MAN*GM*00006141410000041237~
CD3*G*398~
MAN*GM*00006141410000041244~
SE*18*0412~

Notes (illustrative values; 004010 layout):
  SMD*SG*PP         service level SG Standard Ground, freight prepaid by seller
  L11*BOL7781203*BM  bill of lading number the driver signs and the 210 will cite
  CD3*G*412.5       one handling unit, gross weight 412.5 (unit agreed with the carrier)
  MAN*GM*0000614141 SSCC-18 with application identifier 00, as printed on the pallet label
  SE*18             segment count from ST to SE inclusive; mismatch rejects the set

The ship-to loop 0220 is mandatory in 004010 and can repeat up to 10 times per shipment, which covers consignee, bill-to and other parties. Marks on each carton belong in MAN; code GM sends an SSCC-18 with its application identifier, which lets the carrier's scan at the dock match the manifest line without a lookup table.

The international loop 0260, with AT6 and item-level detail, applies only to cross-border shipments. Most domestic manifests leave it out, and carriers that do not support it may reject a set that includes it, so agree its use in the implementation guide.

Manifest or per-load tender: choosing for each pickup

Use a 215 when the carrier comes on a schedule and carries many shipments; use a 204 when each load needs the carrier's acceptance, a rate and an appointment. Sending both for the same freight creates duplicate shipments in the carrier's system, so the choice should be a field on the carrier and lane master, not a planner's decision each day.

• Daily LTL or parcel pickup: one 215 per pickup, sent after the last carton is staged and before the driver arrives, with any late adds sent as a replacement set.
• Truckload or dedicated loads: a 204 per load, because acceptance, equipment and appointment must be agreed in advance and the 990 response matters.
• Multi-stop pool distribution: a 204 for the linehaul load and, where the pool carrier asks for it, a 215 listing the shipments inside that load for its breakbulk terminal.
• Ad hoc expedites: a 204 or a portal booking; a manifest adds nothing when there is one shipment and no standing pickup.

Pickup count reconciliation at the dock door

Reconcile three counts for every pickup: shipments and cartons on the 215, shipments and cartons the driver signs for, and shipments the carrier reports as picked up in its 214 status messages. All three should match before the warehouse system confirms the shipments as despatched.

On the carrier side, status code AF in a 214 means Carrier Departed Pick-up Location with Shipment, while CP means Completed Loading at Pick-up Location and X3 means Arrived at Pick-up Location. An AF per bill of lading gives a machine-readable pickup count; the signed bills give the paper count; and the 215 gives the expected count.

1. 17:05, manifest sent: warehouse system builds 215 control number 0412 for carrier ABCD with 42 shipments and 318 cartons; the carrier's 997 accepts it at 17:07.
2. 17:30, driver arrives: a 214 with X3 is received for the pickup; the driver starts loading from door 14.
3. 18:05, trailer full: the driver leaves shipment BOL7781241, nine cartons, on the dock and signs 41 bills. The dock clerk scans "load complete" and the warehouse system marks all 42 shipments shipped.
4. 18:10, departure: the carrier sends 41 AF statuses. No rule compares them with the manifest, and the advance ship notice for BOL7781241 goes to the customer at 18:15.
5. Controlled version: a rule that holds despatch confirmation until AF count equals manifest count would have flagged one missing shipment at 18:10, kept the ship notice back and moved BOL7781241 to the next morning's pickup.

The failure was not the driver's choice to leave freight behind; trailers fill up. It was the warehouse system confirming despatch from its own scan instead of from the carrier's evidence. A count rule tied to the manifest catches that within minutes rather than at invoice time.

Pickup reconciliation for an X12 215 manifest should hold warehouse despatch confirmation until the count of carrier 214 AF statuses equals the manifest's SMD shipment count, with a 15-minute window after departure, because 49 CFR 373.101 receipts alone cannot be matched automatically.

Who owns the manifest, the receipt and the freight bill

Each count in the reconciliation belongs to a different party, and a mismatch is only resolved when the right owner corrects their own record. The shipper owns the manifest and the despatch confirmation; the carrier owns the receipt, the status events and the invoice.

Our guide to 214 status and 210 invoice reconciliation covers duplicate events and invoice idempotency in depth. For the 215, the narrower point is that the manifest number and the BOL numbers must survive into every carrier message, or there is nothing to reconcile against.

India: per-invoice e-way bills and the transporter's EWB-02

X12 215 has no statutory role in India, and Indian carriers rarely receive it; manifests usually travel as files or API calls. The legal counterpart is the e-way bill trail: one EWB-01 per consignment above the threshold, and a consolidated EWB-02 that the transporter may generate for all consignments in one vehicle.

Rule 138(1) of the CGST Rules 2017 requires a registered person causing movement of goods with a consignment value exceeding fifty thousand rupees to furnish Part A of FORM GST EWB-01 before movement. Under Rule 138(6), once those bills exist, the transporter may list their serial numbers on the common portal and generate a consolidated e-way bill in FORM GST EWB-02 before the goods move.

• Manifest-to-EWB match: every invoice on the pickup manifest above the threshold should carry an EWB number before the vehicle is loaded, and the EWB-02 should list exactly those numbers.
• Transshipment at a hub: Rule 138(5) requires Part B conveyance details to be updated before goods move from one conveyance to another, which a partial-truckload network does at every breakbulk.
• Assigning the bill: Rule 138(5A) lets the consignor, recipient or transporter assign an EWB number to another registered or enrolled transporter so that transporter can update Part B.

Consolidated e-way bill control under CGST Rule 138(6) lets a transporter generate FORM GST EWB-02 listing every EWB-01 in one vehicle before movement, and a pickup manifest check should block gate-out whenever an inter-state invoice above ₹50,000 under Rule 138(1) is missing from that consolidated bill.

The API mechanics of generating and updating these bills are covered in our article on e-way bill API integration. For the manifest, the operational rule is simpler: no consignment above the threshold leaves the dock unless its EWB number appears both on the internal manifest and on the transporter's EWB-02.

A day's pickup reconciled in dollars and rupees

The same count discipline protects money in both markets: in the US it keeps freight accruals and customer deductions honest; in India it also keeps every invoice above the threshold covered by a valid e-way bill reference in the vehicle.

The US gap is a timing problem: the missing shipment will move tomorrow, so the cost is a wrong accrual and a wrong ship notice, both reversible if caught that evening. The India gap is a compliance problem: the invoice is in the vehicle without its e-way bill reference in the consolidated bill, which the transporter must fix before the truck leaves the compound.

Manifest checks a translator enforces and where software assists

Structural and count checks belong in the EDI translator and the warehouse system, where they run on every pickup without judgement. Explaining a count gap, or reading a smudged signed bill, is where software can help a clerk without deciding for them.

Acknowledgement monitoring deserves its own alert because a rejected 215 looks, on the shipper's side, exactly like an accepted one. Our article on the 997 functional acknowledgment explains how to read AK5 and AK9 results and set overdue windows by document type.

Rolling out the 215 with a carrier: tests and go-live checklist

Treat the 215 as a carrier-specific integration with its own test plan. Carriers differ on version, on how they handle change and replace codes, and on whether their dock scans can match SSCC marks, so a mapping that works for one will not automatically work for the next.

Run two weeks in parallel with the paper manifest, comparing counts every evening, before switching off paper. The first week usually exposes late adds sent as new manifests instead of replacements; the second exposes bills of lading that carriers key with a different number format. Fix both in the mapping, not in daily workarounds.

More EDI and carrier integration guides are listed on the Logistics & Supply Chain hub. If you are scoping software that sends 215 manifests, matches carrier statuses and holds despatch until the counts agree, tell us about your carriers and volumes and we will reply with a proposal.