Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC 15418-18: Information Technology — Automatic Identification and Data Capture Techniques — Application Identifiers and Data Identifiers
Standardizing Data Representation for Global Supply Chain Interoperability
The CAN/CSA-ISO/IEC 15418-18 standard is the Canadian adoption of the international ISO/IEC 15418 standard, which governs the use of Application Identifiers (AIs) and Data Identifiers (DIs) in automatic identification and data capture (AIDC) systems. By providing a unified framework for encoding data elements in barcodes, RFID tags, and other AIDC media, this standard ensures seamless data exchange across global supply chains, manufacturing, logistics, and retail industries. This article explores the standard’s scope, technical requirements, implementation guidance, and compliance considerations.
Scope and Purpose
CAN/CSA-ISO/IEC 15418-18 specifies the conditions for the allocation, syntax, and structure of Application Identifiers (GS1 system) and Data Identifiers (ASC MH10 system). It defines how distinct data elements—such as product identifiers, lot numbers, expiration dates, and weights—are encoded in AIDC carriers like GS1-128 barcodes, GS1 DataMatrix, and RFID tags compliant with ISO/IEC 18000 series.
The standard is applicable to organizations that require unambiguous representation of data in machine-readable formats. It covers:
- The GS1 Application Identifier system (AI) used in retail, healthcare, and transportation.
- The ASC MH10 Data Identifier system (DI) popular in industrial and government applications.
- Maintenance procedures for adding or modifying identifiers through a registry process.
Key Benefit: By harmonizing AI and DI usage, organizations reduce data ambiguity, improve scanning reliability, and enable interoperability between partners using different standards families.
Technical Requirements and Structure
Identifier Syntax
The standard defines precise syntax rules for both AI and DI systems. Application Identifiers are variable-length numeric prefixes that precede data fields. For example, AI 01 indicates a Global Trade Item Number (GTIN), while AI 10 designates a batch or lot number. Each AI is followed by a data string of defined length and format (e.g., numeric, alphanumeric).
Data Identifiers follow a similar syntax but are expressed as combinations of letters, numbers, or both. For instance, DI 1P may represent a part number, and DI Q indicates a quantity. The syntax is documented in the ASC MH10 committee standards and maintained jointly by the Automatic Identification and Mobility (AIM) organization and GS1.
Encoding Rules
The standard mandates the use of functional separators (e.g., ASCII character 29 in GS1-128) between concatenated data fields. It also prescribes the order of data elements when multiple identifiers appear in a single carrier (e.g., AI for GTIN followed by AI for expiration date). Compliance with ISO/IEC 15416 (barcode quality) and ISO/IEC 15426 (verifier conformance) is recommended for optimal scanning performance.
| AI | Definition | Format | Example |
|---|---|---|---|
| 01 | Global Trade Item Number (GTIN) | N14 | 9501234567890 |
| 10 | Batch / Lot Number | AN20 | LOT2025A |
| 17 | Expiration Date (YYMMDD) | N6 | 270101 |
| 30 | Count of Items (variable weight/quantity) | N8 | 00000100 |
| 400 | Customer Purchase Order Number | AN30 | PO-2025-901 |
| 412 | Global Location Number (GLN) of Buyer | N13 | 0612345678900 |
| DI | Definition | Example Usage |
|---|---|---|
| 1P | Part Number | 1P12345 |
| 6K | Unit of Measure | 6KEA (each) |
| V | Version Number | V01 |
| Q | Quantity | Q50 |
| Y | Date (YYMMDD) | Y250701 |
Implementation Tip: When using both AI and DI systems in the same supply chain, ensure that your encoding software supports the appropriate syntax. Many scanners and decoders can interpret both if the carrier (e.g., GS1-128 or Data Matrix) is correctly configured.
Implementation Highlights
Successful implementation of CAN/CSA-ISO/IEC 15418-18 requires careful attention to data structures, carrier selection, and verification processes. Below are key implementation areas:
Data Syntax Compliance
Each identifier must be encoded according to the syntax defined in the standard. For GS1 AIs, the data immediately follows the AI without any delimiter except where the AI prefix ends. Fixed-length fields (e.g., 14-digit GTIN) must be zero-padded as needed. For variable-length AIs, the format string in the standard indicates maximum length, but the actual data may be terminated by a separator character.
Carrier Selection
The standard itself is carrier-agnostic, but practical implementations often use:
- GS1-128 (UCC/EAN-128) for AIs in linear barcodes
- GS1 DataMatrix for marking small items (healthcare, electronics)
- RFID tags adhering to ISO/IEC 18000-63 or 18000-6C for GS1 AIs in EPC memory banks
- Data Matrix for DIs (often used by the automotive and aerospace industries)
Important: Do not mix AI and DI identifiers in the same data string unless the carrier specification explicitly supports both. Some combinations can lead to decoding errors. Refer to GS1 General Specifications or the AIM DPM standard for guidance.
Verification and Data Quality
After encoding, each symbol should be verified using a barcode verifier graded according to ISO/IEC 15416 (linear) or ISO/IEC 15415 (2D). For RFID, conformance with ISO/IEC 18047-6 test methods is recommended. Implement automated verification at the point of printing and scanning to detect formatting errors early.
Non‑Compliance Risk: Using unofficial or outdated data identifiers (e.g., legacy AIs assigned by a single industry group) can cause misreading, data loss, and rejection by supply chain partners. Always consult the current CAN/CSA-ISO/IEC 15418-18 registry and GS1 or MH10 maintenance documents.
Compliance and Maintenance
CAN/CSA-ISO/IEC 15418-18 is a normative standard in Canada, adopted from ISO/IEC 15418. Compliance demonstrates an organization’s commitment to international data interoperability. Key compliance aspects include:
- Registry management: The standard incorporates maintenance procedures that allow new identifiers to be proposed, reviewed, and published. GS1 maintains the AI list; the MH10 Committee (via AIM) handles DIs. Both registries are updated periodically.
- Audit documentation: Organizations should document their data identifier mapping to show which AIs/DIs they use and how they are encoded.
- Training: Personnel involved in label design, software development, and quality control should be trained on the standard’s syntax and separator rules.
- Version control: Always reference the specific edition of the standard (e.g., CAN/CSA-ISO/IEC 15418-18). Note that this standard is identical to ISO/IEC 15418:2016, with Canadian deviations (if any) clearly marked.
Best Practice: Integrate identifier validation into your enterprise resource planning (ERP) or warehouse management system (WMS). Use check-digit algorithms for GTINs (AI 01) and implement full character-set verification for alphanumeric DIs.
For conformance testing, external laboratories accredited by the Standards Council of Canada (SCC) can evaluate products and labels against the requirements of the standard. Self-assessment checklists are also available from GS1 Canada and the AIM website.
Q: What is the difference between an Application Identifier (AI) and a Data Identifier (DI) in CAN/CSA-ISO/IEC 15418-18?
A: An AI is a numeric prefix used in the GS1 system (e.g., 01 for GTIN), while a DI is an alphanumeric prefix governed by the ASC MH10 standard (e.g., 1P for part number). Both serve to identify data elements, but they belong to different identifier families. The standard harmonizes their use so that a single carrier can be interpreted by systems supporting either family, provided encoding rules are followed.
A: An AI is a numeric prefix used in the GS1 system (e.g., 01 for GTIN), while a DI is an alphanumeric prefix governed by the ASC MH10 standard (e.g., 1P for part number). Both serve to identify data elements, but they belong to different identifier families. The standard harmonizes their use so that a single carrier can be interpreted by systems supporting either family, provided encoding rules are followed.
Q: Is CAN/CSA-ISO/IEC 15418-18 mandatory in Canada?
A: The standard itself is voluntary, but it may be referenced in customer contracts or regulatory requirements (e.g., healthcare labeling, military logistics). Many retailers and logistics providers require compliance with GS1 and ISO/IEC 15418 as a condition of doing business.
A: The standard itself is voluntary, but it may be referenced in customer contracts or regulatory requirements (e.g., healthcare labeling, military logistics). Many retailers and logistics providers require compliance with GS1 and ISO/IEC 15418 as a condition of doing business.
Q: How often is the identifier registry updated?
A: GS1 publishes updates to its Application Identifier list annually, while ASC MH10 Data Identifiers are revised as needed. Users should regularly check the GS1 General Specifications and the AIM Data Identifier registry to ensure they are using current codes.
A: GS1 publishes updates to its Application Identifier list annually, while ASC MH10 Data Identifiers are revised as needed. Users should regularly check the GS1 General Specifications and the AIM Data Identifier registry to ensure they are using current codes.
Q: Can I use the same carrier for both AI and DI strings?
A: It depends on the carrier. GS1-128 and GS1 Data Matrix support only AIs. For DIs, carriers such as Code 128, Data Matrix (without GS1 FNC1), or UID marking (MIL-STD-130) are typical. Some carriers (e.g., RFID EPC memory) can store AI‑formatted data. Mixing both in one symbol is generally not allowed unless the symbol format explicitly accommodates both, which is rare. For cross‑industry shipments, it is recommended to use separate labels or a single carrier chosen based on the dominant data standard required by the trading partner.
A: It depends on the carrier. GS1-128 and GS1 Data Matrix support only AIs. For DIs, carriers such as Code 128, Data Matrix (without GS1 FNC1), or UID marking (MIL-STD-130) are typical. Some carriers (e.g., RFID EPC memory) can store AI‑formatted data. Mixing both in one symbol is generally not allowed unless the symbol format explicitly accommodates both, which is rare. For cross‑industry shipments, it is recommended to use separate labels or a single carrier chosen based on the dominant data standard required by the trading partner.
This article reflects the status of the CAN/CSA-ISO/IEC 15418-18 standard as of 2026. Always consult the latest official version from GS1 Canada, the Standards Council of Canada, or ISO for the most current requirements and identifiers.