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
TD1 — Carrier Details (Quantity and Weight)
X12 TD1 segment reference: packaging code, lading quantity, and shipment weight used on 856 ASNs and shipping-related documents.
TD1 segment facts
- TD1 summarizes packaging code, lading quantity, and weight that receiving DCs reconcile against physical handling units.
- Packaging codes in TD101 are partner-defined — an unrecognized code is a common ASN rejection cause.
- SignalEDI validates TD1 quantity and weight consistency against carton hierarchy before outbound 856 send.
What the TD1 segment does
TD1 reports packaging code, lading quantity, and gross weight for a shipment or handling unit. It supports carrier handoff and receiving reconciliation, most often on 856 ASNs.
Loop: Shipment/order level on 856
Key elements
| Element | Name | Description |
|---|---|---|
| TD101 | Packaging code | CTN25=carton, PLT94=pallet, and similar partner-defined codes. |
| TD102 | Lading quantity | Number of packages/handling units described. |
| TD106 | Weight qualifier | G=gross weight; partner guides specify. |
| TD107 | Weight | Numeric weight value for the shipment unit. |
Example TD1 segment
TD1*CTN25*4****G*120*LB~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common TD1 errors
- Packaging code not on the partner's allowed list
- Lading quantity inconsistent with carton/pallet counts elsewhere in the ASN
- Weight qualifier/units mismatch vs partner spec
Related reference
FAQ
Frequently asked questions
TD1 typically sits at the shipment or order level of an 856 to summarize packaging quantity and weight for the carrier and receiving DC.
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.”