X12 transaction guide · Transportation
EDI 225 Response to a Cartage Work Assignment
The X12 document a cartage carrier uses to accept or decline a cartage work assignment and return its references.
- Sent by
- Cartage (drayage) carrier
- Received by
- The party that issued the work assignment
- Standard
- ANSI ASC X12
What is an EDI 225?
The EDI 225 Response to a Cartage Work Assignment is the ANSI X12 transaction set a cartage carrier uses to respond to a cartage work assignment (222). It states whether the carrier accepts or declines the assignment and returns any related reference numbers.
The response is small, but timing matters: a declined or unanswered assignment leaves a container at a ramp or port, where storage and demurrage charges accrue. Issuers use 225s to see quickly which moves still need a carrier.
How to read this diagram: the top row shows who sends the 225, 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 225 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.
When it is used
- Accepting a drayage move
- Declining an assignment the carrier cannot cover
- Returning the carrier's own reference for the move
Where it fits in the document flow
Structure
Mandatory segments in the 225 (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
- SCP
- SE
Practical example
The 225 in practice
A drayage company receives 30 work assignments for the next day. It accepts 27 with 225 responses carrying its dispatch numbers and declines three for which it has no chassis. The issuer reassigns the three declined moves to another drayage partner within the hour.
Implementation
Implementation considerations for the 225
- Respond to every assignment, including declines, within the agreed time.
- Return the assignment reference exactly as received.
- Feed declines to the people who can reassign the move.
- Use the carrier's reference in later status and billing messages.
How ECOM helps
Automate the 225 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
3PL and Warehousing
Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related transportation documents
- 222Cartage Work Assignment
- 215Motor Carrier Pickup Manifest
- 219Logistics Service Request
- 220Logistics Service Response
- 300Reservation (Booking Request) (Ocean)
- 301Confirmation (Ocean)
- 303Booking Cancellation (Ocean)
- 304Shipping Instructions
- 313Shipment Status Inquiry (Ocean)
- 317Delivery/Pickup Order
- 319Terminal Information
- 322Terminal Operations and Intermodal Ramp Activity
Need help with the EDI 225?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.