The QTY segment carries a quantity value. The qualifier identifies what is being counted. In ORDERS: 21=ordered quantity. In DESADV: 12=despatched quantity, 52=quantity in trade units, 131=number of packages. In INVOIC: 47=invoiced quantity, 46=delivered quantity. The unit of measure appears in the third sub-element.
QTYHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
QTY+21:100:PCE'Ordered quantity: 100 pieces.
| 1.1 | Quantity: Qualifier | 21Ordered quantity |
| 1.2 | Quantity: Value | 100 |
| 1.3 | Quantity: Unit | PCEpieces |
{
"orderedQuantity": {
"value": 100,
"unit": "PCE"
}
}Example shape. In production the field names and structure follow your own API contract.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Quantity | 1.1 Qualifier, 1.2 Value, 1.3 Unit |
| Code | Meaning |
|---|---|
1 | Discrete quantity |
12 | Despatched quantity |
21 | Ordered quantity |
46 | Delivered quantity |
47 | Invoiced quantity |
48 | Received quantity |
59 | Consumer units per traded unit |
113 | Quantity to be delivered |
145 | Actual stock |
192 | Free goods quantity |
194 | Received and accepted |
195 | Received, not accepted |
| Code | Meaning |
|---|---|
PCE | pieces |
EA | each |
KGM | kg |
GRM | g |
LTR | litres |
MTR | metres |
CT | cartons |
CS | cases |
PK | packs |
NAR | articles |
C62 | units |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with QTY in it? The explainer breaks down every segment and runs in your browser.
Explain my message