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 227 Trailer Usage Report

The X12 document a shipper or consignee uses to report its use of a carrier-supplied trailer for trailer inventory purposes.

Sent by
Shipper, consignee or third party
Received by
Motor carrier
Standard
ANSI ASC X12

What is an EDI 227?

The EDI 227 Trailer Usage Report is the ANSI X12 transaction set for sending information on a shipper's, consignee's or third party's planned use of a trailer supplied by a motor carrier, for trailer inventory reporting only. It tells the carrier when a trailer was loaded, rejected or where it is located.

Carriers drop empty trailers at busy shipping sites, and keeping track of them is costly. The 227 helps the carrier manage its trailer pool. It is not a shipment tender or a bill of lading.

How the EDI 227 worksDiagram of the EDI 227 Trailer Usage Report. Shipper, consignee or third party sends it to motor carrier. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BLR (Transportation Carrier Identification) and the required 0100 loop with N1 (Party Identification). 1 optional loops are listed by their first segment.How the EDI 227 worksTrailer Usage Report: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 227SENDERShipper, consignee orthird partyRECEIVERMotor carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TUGS … GETransaction set 227ST … SEHEADINGBLRTransportation Carrier IdentificationRequired loop 0100 · repeats many timesN1Party Identification+ 1 optional loop, starting with:N7Blue 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 227. Your trading partner's implementation guide adds its own requirements.
How the EDI 227 worksDiagram of the EDI 227 Trailer Usage Report. Shipper, consignee or third party sends it to motor carrier. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BLR (Transportation Carrier Identification) and the required 0100 loop with N1 (Party Identification). 1 optional loops are listed by their first segment.How the EDI 227 worksTrailer Usage Report: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 227SENDERShipper,consignee orthird partyRECEIVERMotor carrier997 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 TU (GS … GE)Transaction set 227 (ST … SE)HEADINGBLRTransportation CarrierIdentificationRequired loop 0100 · repeatsmany timesN1Party Identification+ 1 optional loop, starting with:N7Blue 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 227. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting that a dropped trailer has been loaded
  • Reporting a rejected or damaged trailer
  • Reporting trailer locations in a shipper's yard

Where it fits in the document flow

This document 227 Trailer Usage Report
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 227 (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
  • BLR
  • N1
  • N7
  • SE

Practical example

The 227 in practice

A paper mill keeps a pool of carrier trailers in its yard. When a trailer is loaded, the yard management system sends the carrier a 227 with the trailer number, the loaded status and the door location; when a trailer arrives with a damaged floor, it sends a rejection. The carrier uses the reports to plan pickups and replace unusable equipment.

Implementation

Implementation considerations for the 227

  • Use the 227 for trailer inventory only; tender shipments with the 204.
  • Report trailer numbers exactly as the carrier marks them.
  • Integrate with yard management so reports are timely.
  • Agree with each carrier which statuses to report.

How ECOM helps

Automate the 227 with ECOM

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.

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

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

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

Request a Demo Contact us