Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
TD5 — Carrier Details (Routing Sequence/Transit Time)
X12 TD5 segment reference: carrier identification (SCAC), transportation method, and routing details on ASNs and shipping documents.
TD5 segment facts
- TD5 carries the SCAC carrier code and transportation method retailers use to validate routing-guide compliance.
- An unenrolled or wrong SCAC in TD503 is a frequent ASN compliance failure on routed retail programs.
- SignalEDI checks TD5 carrier and method values against partner routing rules before outbound 856 send.
What the TD5 segment does
TD5 conveys routing and carrier details — the SCAC carrier code, transportation method, and routing sequence — so buyers know how a shipment moves. It is common on 856 ASNs and routing requests.
Loop: Shipment level on 856
Key elements
| Element | Name | Description |
|---|---|---|
| TD501 | Routing sequence code | B=origin/delivery carrier, O=origin carrier — partner-defined. |
| TD502 | Identification code qualifier | 2=SCAC; identifies the carrier code type in TD503. |
| TD503 | Carrier identification (SCAC) | Standard Carrier Alpha Code for the carrier. |
| TD504 | Transportation method/type | M=motor (truck), A=air, LT=less-than-truckload. |
Example TD5 segment
TD5*B*2*FXFE*M~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common TD5 errors
- Invalid or unenrolled SCAC in TD503
- Transportation method code not accepted by the partner program
- Routing sequence code mismatch vs the retailer routing guide
Related reference
FAQ
Frequently asked questions
TD503 carries the Standard Carrier Alpha Code (SCAC) identifying the carrier; retailers validate it against routing-guide carriers.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”