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
CLD — Load Detail
X12 CLD segment on EDI 856 ASN: carton counts, load detail, and package quantities tied to SSCC hierarchy for retail receiving.
CLD segment facts
- CLD quantity drift vs WMS pick confirm is a leading indicator of ASN chargebacks before finance sees deductions.
- Retail DCs scan SSCC first — CLD/MAN hierarchy must match label placement on each carton.
- SignalEDI ASN validation cross-checks CLD totals against line-level shipped quantities in the partner profile.
What the CLD segment does
CLD describes cartons or handling units within an HL shipment loop — quantity per carton, packaging code, and weight. CLD pairs with REF and MAN (SSCC) segments for scan-based receiving.
Loop: Under HL pack/shipment loops
Common transaction sets: 856
Key elements
| Element | Name | Description |
|---|---|---|
| CLD01 | Number of loads | Carton or handling unit count at this hierarchy level. |
| CLD02 | Quantity shipped | Units in the carton or pallet. |
| CLD03 | Packaging code | CTN=carton, PLT=pallet — partner-specific. |
Example CLD segment
CLD*1*24*CTN~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common CLD errors
- CLD02 qty mismatch vs physical pick
- Missing CLD when SSCC present
- Hierarchy level wrong for CLD placement
Related reference
FAQ
Frequently asked questions
CLD counts cartons; MAN*GM* carries the SSCC barcode ID scanned at the DC — both must agree with physical labels.
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, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling 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.”