ANSI X12 transaction set 215
Connect ANSI X12 215 shipping manifests with UPS and your ERP, WMS or 3PL.
Tirnav helps logistics and finance teams automate EDI 215 workflows with partner-specific mapping, testing and exception handling. Map shipment records from your shipping system, WMS or 3PL into the carrier shipping manifest format and send the validated message.
Message overview
EDI 215 is the ANSI X12 Motor Carrier Pick-up Manifest Transaction Set. It communicates a manifest of shipments to a motor carrier to support pickup and shipping operations.
Typical message flow
Implementation workflow
Review the carrier implementation guide, X12 version and business requirements for EDI 215.
Agree connectivity, sender and receiver identifiers, and test data with the trading partner.
Map shipment records from your shipping system, WMS or 3PL into the carrier shipping manifest format and send the validated message.
Validate required fields, qualifiers, references and business rules against the agreed implementation guide.
Test accepted and rejected messages, duplicate handling and acknowledgement requirements.
Launch with transaction monitoring, actionable alerts and controlled reprocessing.
X12 reference
Segment requirements vary by trading partner and implementation guide. These are common examples, not a universal requirement list.
| Segment | Business meaning | Implementation notes |
|---|---|---|
| ISA / GS | Control headers | Identify the interchange sender, receiver and functional group using the agreed partner identifiers. |
| ST / SE | Transaction envelope | Identify the 215 transaction set and validate its control number and segment count. |
| B4 | Beginning segment | Identifies the pickup manifest, shipment status, carrier information and key shipment references. |
| N1 / N2 / N3 / N4 | Party and location | Identifies shipment parties and locations such as shipper, consignee, carrier and pickup location. |
| G62 | Date and time | Communicates pickup, shipment, delivery and other transportation-related dates and times. |
| L11 | Reference information | Carries shipment, order, bill of lading, booking and other reference numbers. |
| MS3 | Interline information | Identifies participating carriers and transportation responsibilities when interline movement is involved. |
| S5 | Stop-off details | Identifies stops, stop sequence and related pickup or delivery information within the manifest. |
| L5 | Commodity information | Identifies the commodities included in the pickup manifest and provides shipment descriptions. |
| L0 | Line-item quantities | Communicates quantities, packaging, weights and units of measure for manifested shipments. |
| L1 | Freight charges | Provides freight rates, charges, allowances and other transportation pricing information when required. |
| L3 | Shipment totals | Provides shipment-level totals such as weight, quantity, volume and freight charges. |
| GE / IEA | Control trailers | Close the functional group and interchange with control counts and matching references. |
Mapping and operations
Tirnav transforms the partner message into the format required by your ERP, WMS, OMS, 3PL or custom application while applying partner-specific business rules.
Exception handling
Detect rejected, malformed or incomplete messages.
Diagnose source data, mapping or business-rule failures.
Resolve the issue with the right owner and correction.
Reprocess safely while preserving transaction history.
Trading partners
Related transaction sets
EDI 215 is the ANSI X12 Motor Carrier Pick-Up Manifest Transaction Set. It is used to communicate a manifest of shipments to a motor carrier for pickup, transportation and shipping operations.
An EDI 215 can include shipment references, pickup locations, delivery information, carrier details, stop information, commodities, quantities, weights and other transportation details required by the carrier.
EDI 215 can be used for motor carrier pickup manifest workflows where supported by the carrier. Tirnav can map carrier-specific EDI 215 requirements and integrate the manifest data with your ERP, WMS, TMS or 3PL system.
Tirnav can collect shipment and pickup information from your ERP, WMS, TMS or 3PL, transform it into the required EDI 215 structure, validate the transaction and transmit it to the carrier.
EDI 215 is a Motor Carrier Pick-Up Manifest used to communicate shipment information to a carrier. EDI 856 is an Advance Ship Notice commonly used to communicate shipment contents to a receiving trading partner. The appropriate transaction depends on the business workflow and implementation guide.
EDI 215 communicates a pickup manifest to a motor carrier, while EDI 240 communicates motor carrier package status information. They support different stages of the transportation workflow.
Implementation typically requires the carrier's implementation guide, applicable X12 version, sample EDI files, connectivity requirements, shipment and package mapping rules, and destination-system field mappings.
Tirnav validates EDI 215 messages before transmission and identifies issues such as missing shipment references, invalid data or mapping errors. Failed transactions can be reviewed, corrected and reprocessed.
Explore our latest thoughts on technology and business.
Learn how automotive EDI helps Indian OEMs and suppliers automate forecasts, purchase orders, ASN, invoices, ERP integration and supplier collaboration.
A practical plan to convert UB-04 claim data into HIPAA-compliant X12 837I, submit to a clearinghouse or payer, and track 999/277CA acknowledgments - with realistic timeline and cost.
Confused about how to start with EDI? We break down the three paths: SaaS Fulfilment Portals (like SPS Commerce Web), Integrated EDI (ERP Automation), and building your own In-House system.
Skip the backlog. Connect directly with our architects to discuss your business goals, technical challenges, and digital transformation roadmap.