ISO/IEC 15434:2019

Information technology - Automatic identification and data capture techniques - Syntax for high-capacity ADC media

This document specifies a transfer structure, syntax, and coding of messages and data formats when using high-capacity ADC media between trading partners (specifically between suppliers and recipients) and, where applicable, in support of carrier applications, such as bills of lading, and carrier sortation and tracking. The data encoded according to this document include: - data which can be used in the shipping, receiving and inventory of transport units; - data which can be contained within supporting documentation, in paper or electronic form, related to unit loads or transport packages; - data which can be used in the sortation and tracking of transport units. This document describes the ISO/IEC 646 characters used for automatic data capture; it is not the controlling specification for data structures (e.g. CII) referenced in this International Standard. This document does not supersede or replace any applicable safety or other marking or labelling requirements. It is intended to be applied in addition to any other mandated labelling requirements.

Technologies de l'information — Techniques automatiques d'identification et de capture des données — Syntaxe pour supports de CAD à haute capacité

General Information

• Status: Published
• Publication Date: 26-Feb-2019
• ICS: 35.040.50 - Automatic identification and data capture techniques
• Technical Committee: ISO/IEC JTC 1/SC 31 - Automatic identification and data capture techniques
• Drafting Committee: ISO/IEC JTC 1/SC 31/WG 2 - Data and structure
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 09-Jan-2025
• Completion Date: 30-Oct-2025

Relations

• Revised: ISO/IEC 15434:2025 - Information technology - Automatic identification and data capture techniques - Syntax for high-capacity ADC media
• Effective Date: 06-Jun-2022
• Revises: ISO/IEC 15434:2006 - Information technology - Automatic identification and data capture techniques - Syntax for high-capacity ADC media
• Effective Date: 10-Dec-2016

Overview - ISO/IEC 15434:2019 (Syntax for high‑capacity ADC media)

ISO/IEC 15434:2019 defines the transfer structure, syntax and coding to carry multiple data fields on high‑capacity automatic identification and data capture (ADC) media. It standardizes how data is packaged and exchanged between trading partners (suppliers and recipients) and, where applicable, supports carrier functions such as bills of lading, sortation and tracking. The standard covers message and format envelopes, headers and trailers, and the character set (subset of ISO/IEC 646) used for ADC.

Key topics and technical requirements

• Message envelope structure: A two‑level enveloping model containing a message header, one or more format envelopes, and a message trailer.
• Format envelopes: Each format envelope includes a format header, formatted data, and a format trailer. Multiple formats per message are permitted with bilateral agreement.
• Conformance indicators and control characters: The standard prescribes the three‑character conformance indicator at message start and a non‑printable format trailer character to delineate formats (see Annex A for ISO/IEC 646 values).
• Supported data formats: Defines numerous format identifiers and rules for encoded payloads, including:
  • Transportation / carrier sortation and tracking
  • Complete EDI transactions
  • Structured data using ASC X12 and UN/EDIFACT
  • GS1 Application Identifiers (AIs)
  • ASC MH10 data identifiers
  • Free‑form text, CII syntax rules, binary data, and text element identifiers
• Character set: Specifies the ISO/IEC 646 characters used for automatic data capture (not a replacement for other data‑structure specifications).
• Scope limitations: Does not define internal media storage formats, nor does it supersede safety or mandated labelling requirements.

Practical applications and who uses it

• Logistics and supply‑chain organizations for encoding shipping, receiving and inventory data on RFID tags, 2D symbols, smart cards or contact memories.
• Carriers and freight forwarders implementing sortation, tracking and bills‑of‑lading workflows that read high‑capacity ADC media.
• AIDC hardware and software vendors building readers, middleware and mapping utilities that parse multi‑field ADC payloads.
• IT integrators and EDI implementers who need a standard syntax for exchanging structured and unstructured transport‑related data across systems.

Related standards and references

• ISO/IEC 646 (7‑bit character set used by this standard)
• ISO/IEC 19762 (AIDC vocabulary)
• GS1 General Specifications (GS1 AIs)
• ANS MH10.8.2 (ASC MH10 data identifiers)
• ANS X12, UN/EDIFACT and CII (EDI and structured data syntaxes)
• ATA Common Support Data Dictionary (CSDD)

ISO/IEC 15434:2019 is essential when you need interoperable, standards‑based encoding of multi‑field data on high‑capacity ADC media for supply‑chain, carrier and inventory applications.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15434
Fourth edition
2019-02
Information technology — Automatic
identification and data capture
techniques — Syntax for high-capacity
ADC media
Technologies de l'information — Techniques automatiques
d'identification et de capture des données — Syntaxe pour supports
de CAD à haute capacité
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Fax: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Documentation notation conventions . 2
5 Message format . 2
5.1 General . 2
5.2 Message envelope . 3
5.2.1 General. 3
5.2.2 Message header . 3
5.2.3 Message trailer . 4
5.3 Format envelope . 4
5.3.1 General. 4
5.3.2 Format header . 4
5.3.3 Format header “00” - Reserved format. 6
5.3.4 Format Header “01” — Transportation . 6
5.3.5 Format Header “02” — Complete EDI message / transaction . . 6
5.3.6 Format header “03” — Structured data using ASC X12 segments . 6
5.3.7 Format header “04” — Structured data using UN/EDIFACT segments . 7
5.3.8 Format header “05” — Data using GS1 application identifiers . 7
5.3.9 Format header “06” — Data using ASC MH 10 data identifiers . 7
5.3.10 Format header “07” — Free form text data . 7
5.3.11 Format header “08” — Structured data using CII syntax rules . 7
5.3.12 Format Header “09” — Binary data . 7
5.3.13 Format header (“10”- “11”) — Reserved formats . 8
5.3.14 Format header “12” — Data using text element identifiers . 8
5.3.15 Format header (“13”-“99”) — Reserved formats . 8
5.3.16 Format trailer . 8
5.4 Data format . 8
5.4.1 General. 8
5.4.2 Format “00” (Reserved) . 9
5.4.3 Format “01” carrier sortation and tracking (transportation) . 9
5.4.4 Format “02” (Complete EDI message / transaction) .11
5.4.5 Format “03” (Structured data using ASC X12 segments) .12
5.4.6 Format “04” (Structured data using UN/EDIFACT segments) .12
5.4.7 Format “05” (Using GS1 application identifiers).12
5.4.8 Format “06” (Using ASC MH 10 data identifiers) .12
5.4.9 Format “07” (Free form text format) .12
5.4.10 Format “08” (Structured data using CII syntax rules) .12
5.4.11 Format “09” (Binary data) .13
5.4.12 Format “10”-“11” (Reserved) .13
5.4.13 Format “12” (Using text element identifiers) .13
5.4.14 Format “13” (Blocked) .13
5.4.15 Format “14”-“99” (Reserved) .13
6 Human readable representation .14
Annex A (normative) Subset of ISO/IEC 646 (table of hexadecimal and decimal values) .15
Bibliography .17
© ISO/IEC 2019 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www. iso. org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www. iso. org/patents) or the IEC
list of patent declarations received (see http:/ /patents.i ec. ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www. iso
.org/iso/foreword. html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
This fourth edition cancels and replaces the third edition (ISO/IEC 15434:2006), which has been
technically revised.
The main changes compared to the previous edition are as follows:
— "Document notation conventions" have been moved to a new Clause 4;
— "Human readable representation" has been inserted (Clause 6).
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www. iso. org/members. html.
iv © ISO/IEC 2019 – All rights reserved

Introduction
This document defines the manner in which data is transferred to high-capacity automatic data capture
(ADC) media from a supplier’s information system and the manner in which data is transferred to the
recipient’s information system. It does not define the internal data storage format for specific high-
capacity ADC media. This document does not specify the application of data structures provided by a
specific data syntax format. The application of the data structure is specified by industry conventions.
Users of ADC technologies benefit by being able to receive data in a standard form and by being able to
provide data in a standard form. Static ADC technologies such as bar code symbologies, magnetic stripe,
optical character recognition, surface acoustical wave (SAW) and Weigand effect typically encode a
single field of data. Most applications of these technologies involve the encoding of a single field of data
by the supplier of the medium and the subsequent decoding of the data field by the recipient. Encoding
single fields of data permits the supplier to perform the encodation from a single field within the
supplier’s information system. Decoding single fields of data permits the recipient to input this data
into a single field in the recipient’s information system, in lieu of key entry.
High-capacity ADC technologies, such as two-dimensional symbols, RFID transponders, contact
memories and smart cards, encode multiple fields of data. These multiple fields are usually parsed by the
recipient’s information system and then mapped to specific fields of data in the recipient’s information
system. This document defines the syntax for high-capacity ADC media, so as to enable ADC users to
utilize a single mapping utility, regardless of which high-capacity ADC medium is employed.
© ISO/IEC 2019 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 15434:2019(E)
Information technology — Automatic identification and data
capture techniques — Syntax for high-capacity ADC media
1 Scope
This document specifies a transfer structure, syntax, and coding of messages and data formats
when using high-capacity ADC media between trading partners (specifically between suppliers and
recipients) and, where applicable, in support of carrier applications, such as bills of lading, and carrier
sortation and tracking.
The data encoded according to this document include:
— data which can be used in the shipping, receiving and inventory of transport units;
— data which can be contained within supporting documentation, in paper or electronic form, related
to unit loads or transport packages;
— data which can be used in the sortation and tracking of transport units.
This document describes the ISO/IEC 646 characters used for automatic data capture; it is not the
controlling specification for data structures (e.g. CII) referenced in this International Standard.
This document does not supersede or replace any applicable safety or other marking or labelling
requirements. It is intended to be applied in addition to any other mandated labelling requirements.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 646, Information technology — ISO 7-bit coded character set for information interchange
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabulary
ANS MH10.8.2, ASC MH 10 Data Identifiers and Application Identifiers
ANS X12, Electronic Data Interchange
Syntax Rule CII (Vers 3.00), CII Syntax Rule Specifications (3.00) (Electronic Data Interchange — Japan)
GS1 General Specification. GS1
ATA Common Support Data Dictionary (CSDD), Air Transport Association
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19762 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
© ISO/IEC 2019 – All rights reserved 1

4 Documentation notation conventions
This document uses the following typographical conventions in message examples.
a) BOLD, ALL CAPITALS Text that shall be entered exactly as it appears. (In this document,
F G U R E
, , , , o are used to represent non-printable special char-
S S S S T
acters. The ISO/IEC 646 representation of special characters that
shall be used and is used in this document can be found in Annex A.)
b) italic, lower case Variable parameters. The user shall supply an appropriate value. In
some cases, default values are recommended in this document.
5 Message format
5.1 General
This clause defines how data shall be transferred from a high capacity ADC media reading device to the
user's application software.
To allow multiple data formats to be contained within a data stream, a two-level structure of enveloping
is employed. The outermost layer of the message is a message envelope that defines the beginning and
end of the message. Within the message envelope, there is one or more format envelopes that contain
the data (see Figure 1). Multiple formats in a single message should only be employed with bilateral
agreements of the trading partners.
The message envelope shall consist of
— a message header,
— one or more format envelope(s), and
— a message trailer (when required).
Each format envelope within the message envelope shall consist of
— a format header,
— data, formatted according to the rules defined for that format, and
— a format trailer (when required).
2 © ISO/IEC 2019 – All rights reserved

Figure 1 — Enveloping structure
NOTE Annex A shows the decimal and hexadecimal values of ASCII characters used in this document.
5.2 Message envelope
5.2.1 General
The message envelope defines the start and end of the data contained within the data stream and
provides the following functions:
— indicates that the message contained within this media is formatted in conformance with the rules
of this document;
— indicates the character which has been defined to separate formats within this message;
— provides a unique character to indicate the end of the message.
The structure within a data stream is as follows:
a Message, containing one or more formats;
a Format, containing one or more segments;
a Segment, containing one or more data elements;
a Data element (field), potentially containing one or more sub-elements (sub-fields).
5.2.2 Message header
5.2.2.1 General
The message header consists of two parts:
— the three-character conformance indicator, and
— the format trailer character.
© ISO/IEC 2019 – All rights reserved 3

R
The complete message header is: [)>
S
5.2.2.2 Conformance indicator
The conformance indicator shall be the first three characters in the message header. It shall be [)> (left
bracket, right parenthesis and greater than). See Annex A for a table of ASCII decimal and hexadecimal
values used in this document.
5.2.2.3 Format trailer character
The format trailer character shall be the fourth character in the message header. It shall be the non-
R
printable ASCII character “ ” (see Annex A). The format trailer character is used throughout the
S
message to indicate the end of a data format envelope (see 5.3.16).
5.2.3 Message trailer
The message trailer identifies the end of the message within the data stream. It shall be the end of
E
transaction character, “ o ” (see Annex A). The message trailer character shall not be used elsewhere in
T
E
the message except in format “09” (binary data) where the “ o ” character may appear.
T
The message trailer shall not be used with formats “02” (complete EDI message / transaction) and “08”
(structured data using CII syntax rules).
5.3 Format envelope
5.3.1 General
The format envelope defines the start and end of data in a given format and provides the following
functions:
— identifies the data format used within the envelope;
— defines the character(s) used to separate the segments, data elements (fields) and sub-elements
(sub-fields) within this data format;
— indicates any applicable date, release or control information.
5.3.2 Format header
5.3.2.1 General
A format header shall consist of two parts:
— a format indicator (a two-digit numeric identifier which identifies the rules governing the format);
— variable data (if any) which defines the separators used and version and release, date or control
information of the applicable standards.
Table 1 lists the format indicators and variable data associated with the format header.
4 © ISO/IEC 2019 – All rights reserved

Table 1 — Format header table showing associated separators
Format Format
Variable header data Format description
indicator trailer
00 Reserved for future use
G R
01 vv Transportation
S S
02 Complete EDI message / transaction
F G U R
03 vvvrrr Structured data using ANSI ASC X12 segments
S S S S
F G U R
04 vvvrrr Structured data using UN/EDIFACT segments
S S S S
G R
05 Data using GS1 application identifiers
S S
G R a
06 Data using ASC MH10 data identifiers
S S
R
07 Free form text
S
08 vvvvrrnn Structured data using CII syntax rules
Binary data (file type) (compression technique)
G G G G R
09 ttt.t ccc.c nnn.n
S S S S S
(number of bytes)
10-11 Reserved for future use
Structured data following text element identifier
G R
S S
rules
Blocked for use to avoid conflict with ISO/
IEC 15961-2
14-99 Reserved for future use
a
Previously known as FACT data identifiers.

NOTE 1 vv represents the two-digit version of format “01” being used
R
NOTE 2 represents the format trailer character (see 5.3.16).
S
F
NOTE 3 represents the segment terminator (see 5.3.2.2.2).
S
G
NOTE 4 represents the data element separator (see 5.3.2.2.3).
S
U
NOTE 5 represents the sub-element separator (see 5.3.2.2.4).
S
NOTE 6 vvvrrr represents the three-digit version (vvv) followed by the three-digit release
(rrr) (see 5.3.6).
NOTE 7 vvvvrrnn represents the four-digit version (vvvv) followed by the two-digit release (rr)
followed by the two-digit edition indicator (nn) (see 5.3.11).
NOTE 8 ttt.t represents the file type name (see 5.3.12).
NOTE 9 ccc.c represents the compression technique name (see 5.3.12).
NOTE 10 nnn.n represents the number of bytes (see 5.3.12).
5.3.2.2 Separators and terminators
5.3.2.2.1 General
The separators and terminators are an integral part of the data stream. The separator and terminator
characters shall not be used in non-binary data elsewhere in the message. For binary data strings
(format “09”), special considerations apply (see 5.3.12).
© ISO/IEC 2019 – All rights reserved 5

5.3.2.2.2 Segment terminator
Each segment in format “03” shall be terminated by the segment terminator character, the non-printable
F
character “ ” (see Annex A).
S
5.3.2.2.3 Data element separator
Data elements in formats “01,” “03,” “05,” and “06” shall be separated by the data element separator, the
G
non-printable character “ ” (see Annex A).
S
5.3.2.2.4 Sub-element separator
Sub-elements in format “03” shall be terminated by the sub-element separator character, the non-
U
printable character “ ” (see Annex A).
S
5.3.3 Format header “00” - Reserved format
Format header “00” is reserved for future use.
5.3.4 Format Header “01” — Transportation
The format header shall be represented as
G
01 vv
S
where
G
is the data element separator to be used between data elements;
S
vv represents the two-digit version as given in 5.4.3.1.
5.3.5 Format Header “02” — Complete EDI message / transaction
The format header shall be represented as
There is no variable header data for this data format (see 5.4.4).
5.3.6 Format header “03” — Structured data using ASC X12 segments
The format header shall be represented as
F G U
03vvvrrr
S S S
where
vvv
...