1 Scope
This document specifies the requirements for the labelling and direct product marking of 1D and 2D barcode labels for packaging.
This document applies to production, inventory, distribution, field service, sales, maintenance and repair processes, as well as to the automotive, aerospace, chemical, consumer goods, electronics, medical, marine, railway and telecommunications industries.
2 Normative references
The content of the following documents constitutes the essential provisions of this document through the normative references in the text. Among them, note the date of the reference documents, only the date of the corresponding version applicable to this document; do not note the date of the reference documents, the latest version (including all the revision of the list) applicable to this document.
GB/T 4122 (All Parts) Packaging Terms
GB/T 8170 Rules for Rounding off Values and Expression and Judgment of Limit Values
GB 12904 Barcode for Commodity Retail Commodity Code and Barcode Representation (GB 12904-2008, ISO/IEC 15420:2000, NEQ)
GB/T 12905 Barcode Terminology
GB/T 12908 Information Technology - Automatic Identification and Data Acquisition Technology - Bar Code Symbol Specification - 39 Bar Code (GB/T 12908-2002, ISO/IEC 16388:1999, MOD)
GB/T 14258 Information Technology - Automatic Identification of Pathogens and Data Acquisition Technology - Bar Code Symbol Printing Quality Inspection (GB/T 14258-2003,1sO/IEC 15416:2000, MOD)
GB/T 15425 Commodity Bar Code 128 Bar Code
GB/T 16986 Commodity Bar Code, Application Identifier (GB/T16986-2018,1SO/IEC15418:2016, NEQ)
GB/T 17172 417 Bar Code
GB/T18284 Fast Response Matrix Code (GB/T 18284-2000, neq ISO/IEC 18004:2000)
GB/T 18347128 Barcode (GB/T18347-2001, idt ISO/IEC 15417:2000)
GB/T 21049 Hanxin Code
GB/T 23704 Inspection of Printing Quality of Two dimensional Bar Code Symbols (GB/T 23704-2017, ISO/IEC 15415:2011, MOD)
GB/T 37056 Item Coding Terminology
ISO/IEC 15418 Information technology - Automatic identification and data capture technologies - GS1Application identifiers and ASC MH10 Data identifiers and maintenance
Note: GB/T 16,986-2018 Commodity Bar Code Application Identifier (ISO/IEC 154,182,016, NEQ)
ISO/IEC 15424 Information technology Automatic identification and data capture technologies Data carrier identifiers (including symbolic ldentifiers)
ISO/IEC 15434 Information technology - Automatic identification and data capture technologies - Syntax for high capacity ADC media
ISO/IEC 15459-2 Information Technology - Automatic Identification and Data Acquisition Technology - Unique Identification - Part 2: Registration procedures
ISO/IEC 16022 Information technology - Automatic identification and data capture technologies - Data Matrix bar code symbol specification3 Terms, definitions and abbreviations
3.1 Terminology and definitions
The terms defined in GB/T 12905, GB/T 37056 and GB/T 4122 (all parts) and the following terms and definitions apply to this document.
4 Requirements
4.1 Marking
4.1.1 General rules
Companies may assign unique identification to individual products, batches or product types. Serialisation or single production is the unique identification of a single product, see 4.1.22 and 4.2.3.3. batch identification is the unique identification of a batch of European products, see 4.1.3 and 4.2.3.3. product code is an example of product uniqueness, see 4.2.3.4.
4.1.2 Product identification
A unique identifier such as a serial number can be assigned to each product. The serial number should be unique, either within the company ID or within the company ID plus part code. When a unique identifier is used, the code symbol shall contain only an enterprise identifier, the serial number and/or the original part number.
4.1.3 Batch identification
Companies may use batch unique identification on their products. Some products may be assigned a batch identifier such as a batch number.
4.2 General requirements for data formats
4.2.1 General rules
It is appropriate to use this document in accordance with relevant industry guidelines, some of which can be found in the references.
4.2.2 General format
4.2.2.1 Overview
Tags may contain mandatory and optional data fields. Unless otherwise specified, each data field should not exceed 25 data characters in length and the character count does not include overhead characters. See Appendix A for information on partial serialisation of electronic products.
Machine readable data elements should be preceded by a DI as defined in ISO/1EC 15418 or comply with AI as defined in GB/T 16986. The user may use DI or AI in accordance with industry practice.
4.2.2.2 Data Identifiers
The DI list is only a general description for industrial and international applications. Specific guidelines for use are defined in detail by the trading partners. DI can be used with any alphanumeric data carrier, ensuring cross-industry universality of DI in automatic identification technology.
ISO/IEC 15418 provides a complete list and specifications for the use of DI, which can be in a single alphabetic character format or a single alphabetic character preceded by 1 to 3 numeric characters.
4.2.2.3 Application identifiers
AI is designed for international trade and cross-industry applications. AI is used to identify generic and simple data fields in cross-industry and international supply chain applications. This document contains two main elements: the data content and the data carrier.
GB/T 16986 specifies the rules for the definition, format and structure of data fields, with each AI containing 2-4 characters.
4.2.2.4 Code organisation
The data structure used for product identification or product tracing should include the code provided by the code organisation and the specific code structure, which is the GTIN vendor identification code specified in GB/T 16986.
The CLEI code is normally 10 characters long and is structured as follows: a basic code representing the type of technology or equipment (four alphanumeric characters), a series code (two alphanumeric characters), a sub-series code (two alphanumeric characters), a feature code representing the attributes of the equipment (three alphanumeric characters), and a code for the product. attribute (three alphanumeric characters), a reference code representing the manufacturer of the equipment within the base code (one alphanumeric character) and a supplementary code representing the time of manufacture or version of the equipment (two alphanumeric characters). When using DI, this coding structure uses the IAC and IAC-assigned CINs that comply with ISO/IEC 15459-2.
The ISO/IEC 15459 IACs are registered in Appendix E. 4.2.3 Mandatory data fields
4.2.3.1 General rules
The product identification types and mandatory data fields are shown in Table 1.
4.2.3.2 Corporate identification codes
The DI and AI used for the Enterprise Identification Code shall use the format of Tables 2 and 3. Multiple DIi's starting with 2V are allowed for one product. The trading partners jointly select the corporate identification code. When separate data fields are used to identify supply lizards and products, the appropriate DI should be placed before the enterprise identifier.
4.2.5 Syntax
4.2.5.1 Syntax of 1D barcode symbology data fields
Data encoded using the EAN/UPC code system do not contain an identifier. The DI should be placed before the data of the three-nine barcode symbology as specified in GB/T 12908. The AI should be placed before the GS1-128 barcode data that complies with the provisions of GB/T 15425. DI should be placed before the 128 barcode data as specified by GB/T 18347. Data encoded using the UPC-A code system should comply with GB 12904.
4.2.5.2 Linking of multiple data fields in 1D barcode symbologies
The total length of linked data in a 1D barcode symbology is preferably limited to 32 characters, including DI, AI and linking characters, but excluding code system overhead characters. If the length exceeds 32 characters, it is advisable to use 2D barcodes.
a) When linking data in a 1D barcode message, it is appropriate to use the appropriate data cell separator according to specific industry standards. The maximum length of the linked data field is limited by the barcode system used, the reading technology and the space available for barcode printing.
b) Fixed length data fields need to be allocated specific data and AI when linked.
c) When variable length data fields need to be linked using the three nines barcode system, it is advisable to use "+" plus the symbol (ASCII decimal value of 43 to separate the data fields according to the provisions of GB/T 12908.
d) When it is necessary to use the 128 barcode system to link multiple variable length data fields with DI, it is appropriate to use the "+" character (the decimal value of ASCII code is 43) to separate the data fields according to GB/T 18347.
e) When it is necessary to use GS1-128 barcode system to link multiple variable length data fields, the "FNC1" character (transmitted as "6s", the decimal value of ASCII code is 29) is used to separate the data fields between the data fields.
4.2.5.3 2D barcode data field syntax
4.3 Layout and Positioning
4.3.1 Layout
Layout refers to the position of the field on the label. The layout of a 1D or 2D barcode depends on the space available for the product and other factors such as business rules of the industry sector, trading partner agreements or customer labelling requirements.
4.3.2 Positioning
Positioning refers to the location of the label on the product. Each label should be positioned so that it can be easily scanned and does not compromise product safety or product performance. Attention should be paid to the installed product-readable barcode symbol.
4.3.3 Headings for 1D barcodes
It is desirable to use headings for the fields of 1D barcodes. When using DI, the DI is enclosed in net brackets, e.g. (1P)PART #SPLR, and when using AI, the AI is part of the human readable characters and not part of the heading, which should be in accordance with ISO/IEC 15418. The header may be located above or below the barcode symbol in accordance with industry guidelines and application standards.
The heading may be abbreviated to a DI with parentheses if the physical space available to the mark is insufficient to permit its use, and may be eliminated where space is extremely limited.
4.3.4 Human-readable characters
1D barcodes should be printed with human readable characters, which should be clearly printed. The height of the uppercase characters should be 2 mm, with a minimum height of 1.25 mm, and the DI or AI in parentheses, with the human readable characters containing all data of the barcode.
The 1D barcode symbology with DI is shown in Figure 1 and the barcode symbology with AI is shown in Figure 2.
4.4 Symbology requirements
4.4.1 Recommendations for the use of the code system
Appendix A (informative) Part serialisation of electronic products
Appendix B (informative) Part Commonly used identifiers
Appendix C (informative) GB/T 1988 character set (hexadecimal and decimal)
Appendix D (Informative) ISO/IEC 15434 Data Syntax Implementation Guide
Appendix E (informative) ISO/IEC 15459 Registration of IACs
Appendix F (Informative) Application of the Triple 9 and 128 barcode code systems
Appendix G (Informative) Application of DUNS codes and DI to 1D and 2D barcodes
Appendix H (Informative) Label Adhesion Characteristics and Mark Durability
Appendix I (Informative) Mode 36 Internal Service Code Check Character Algorithm
Bibliography
1 Scope
2 Normative references
3 Terms, definitions and abbreviations
4 Requirements
Appendix A (informative) Part serialisation of electronic products
Appendix B (informative) Part Commonly used identifiers
Appendix C (informative) GB/T 1988 character set (hexadecimal and decimal)
Appendix D (Informative) ISO/IEC 15434 Data Syntax Implementation Guide
Appendix E (informative) ISO/IEC 15459 Registration of IACs
Appendix F (Informative) Application of the Triple 9 and 128 barcode code systems
Appendix G (Informative) Application of DUNS codes and DI to 1D and 2D barcodes
Appendix H (Informative) Label Adhesion Characteristics and Mark Durability
Appendix I (Informative) Mode 36 Internal Service Code Check Character Algorithm
Bibliography
1 Scope
This document specifies the requirements for the labelling and direct product marking of 1D and 2D barcode labels for packaging.
This document applies to production, inventory, distribution, field service, sales, maintenance and repair processes, as well as to the automotive, aerospace, chemical, consumer goods, electronics, medical, marine, railway and telecommunications industries.
2 Normative references
The content of the following documents constitutes the essential provisions of this document through the normative references in the text. Among them, note the date of the reference documents, only the date of the corresponding version applicable to this document; do not note the date of the reference documents, the latest version (including all the revision of the list) applicable to this document.
GB/T 4122 (All Parts) Packaging Terms
GB/T 8170 Rules for Rounding off Values and Expression and Judgment of Limit Values
GB 12904 Barcode for Commodity Retail Commodity Code and Barcode Representation (GB 12904-2008, ISO/IEC 15420:2000, NEQ)
GB/T 12905 Barcode Terminology
GB/T 12908 Information Technology - Automatic Identification and Data Acquisition Technology - Bar Code Symbol Specification - 39 Bar Code (GB/T 12908-2002, ISO/IEC 16388:1999, MOD)
GB/T 14258 Information Technology - Automatic Identification of Pathogens and Data Acquisition Technology - Bar Code Symbol Printing Quality Inspection (GB/T 14258-2003,1sO/IEC 15416:2000, MOD)
GB/T 15425 Commodity Bar Code 128 Bar Code
GB/T 16986 Commodity Bar Code, Application Identifier (GB/T16986-2018,1SO/IEC15418:2016, NEQ)
GB/T 17172 417 Bar Code
GB/T18284 Fast Response Matrix Code (GB/T 18284-2000, neq ISO/IEC 18004:2000)
GB/T 18347128 Barcode (GB/T18347-2001, idt ISO/IEC 15417:2000)
GB/T 21049 Hanxin Code
GB/T 23704 Inspection of Printing Quality of Two dimensional Bar Code Symbols (GB/T 23704-2017, ISO/IEC 15415:2011, MOD)
GB/T 37056 Item Coding Terminology
ISO/IEC 15418 Information technology - Automatic identification and data capture technologies - GS1Application identifiers and ASC MH10 Data identifiers and maintenance
Note: GB/T 16,986-2018 Commodity Bar Code Application Identifier (ISO/IEC 154,182,016, NEQ)
ISO/IEC 15424 Information technology Automatic identification and data capture technologies Data carrier identifiers (including symbolic ldentifiers)
ISO/IEC 15434 Information technology - Automatic identification and data capture technologies - Syntax for high capacity ADC media
ISO/IEC 15459-2 Information Technology - Automatic Identification and Data Acquisition Technology - Unique Identification - Part 2: Registration procedures
ISO/IEC 16022 Information technology - Automatic identification and data capture technologies - Data Matrix bar code symbol specification3 Terms, definitions and abbreviations
3.1 Terminology and definitions
The terms defined in GB/T 12905, GB/T 37056 and GB/T 4122 (all parts) and the following terms and definitions apply to this document.
4 Requirements
4.1 Marking
4.1.1 General rules
Companies may assign unique identification to individual products, batches or product types. Serialisation or single production is the unique identification of a single product, see 4.1.22 and 4.2.3.3. batch identification is the unique identification of a batch of European products, see 4.1.3 and 4.2.3.3. product code is an example of product uniqueness, see 4.2.3.4.
4.1.2 Product identification
A unique identifier such as a serial number can be assigned to each product. The serial number should be unique, either within the company ID or within the company ID plus part code. When a unique identifier is used, the code symbol shall contain only an enterprise identifier, the serial number and/or the original part number.
4.1.3 Batch identification
Companies may use batch unique identification on their products. Some products may be assigned a batch identifier such as a batch number.
4.2 General requirements for data formats
4.2.1 General rules
It is appropriate to use this document in accordance with relevant industry guidelines, some of which can be found in the references.
4.2.2 General format
4.2.2.1 Overview
Tags may contain mandatory and optional data fields. Unless otherwise specified, each data field should not exceed 25 data characters in length and the character count does not include overhead characters. See Appendix A for information on partial serialisation of electronic products.
Machine readable data elements should be preceded by a DI as defined in ISO/1EC 15418 or comply with AI as defined in GB/T 16986. The user may use DI or AI in accordance with industry practice.
4.2.2.2 Data Identifiers
The DI list is only a general description for industrial and international applications. Specific guidelines for use are defined in detail by the trading partners. DI can be used with any alphanumeric data carrier, ensuring cross-industry universality of DI in automatic identification technology.
ISO/IEC 15418 provides a complete list and specifications for the use of DI, which can be in a single alphabetic character format or a single alphabetic character preceded by 1 to 3 numeric characters.
4.2.2.3 Application identifiers
AI is designed for international trade and cross-industry applications. AI is used to identify generic and simple data fields in cross-industry and international supply chain applications. This document contains two main elements: the data content and the data carrier.
GB/T 16986 specifies the rules for the definition, format and structure of data fields, with each AI containing 2-4 characters.
4.2.2.4 Code organisation
The data structure used for product identification or product tracing should include the code provided by the code organisation and the specific code structure, which is the GTIN vendor identification code specified in GB/T 16986.
The CLEI code is normally 10 characters long and is structured as follows: a basic code representing the type of technology or equipment (four alphanumeric characters), a series code (two alphanumeric characters), a sub-series code (two alphanumeric characters), a feature code representing the attributes of the equipment (three alphanumeric characters), and a code for the product. attribute (three alphanumeric characters), a reference code representing the manufacturer of the equipment within the base code (one alphanumeric character) and a supplementary code representing the time of manufacture or version of the equipment (two alphanumeric characters). When using DI, this coding structure uses the IAC and IAC-assigned CINs that comply with ISO/IEC 15459-2.
The ISO/IEC 15459 IACs are registered in Appendix E. 4.2.3 Mandatory data fields
4.2.3.1 General rules
The product identification types and mandatory data fields are shown in Table 1.
4.2.3.2 Corporate identification codes
The DI and AI used for the Enterprise Identification Code shall use the format of Tables 2 and 3. Multiple DIi's starting with 2V are allowed for one product. The trading partners jointly select the corporate identification code. When separate data fields are used to identify supply lizards and products, the appropriate DI should be placed before the enterprise identifier.
4.2.5 Syntax
4.2.5.1 Syntax of 1D barcode symbology data fields
Data encoded using the EAN/UPC code system do not contain an identifier. The DI should be placed before the data of the three-nine barcode symbology as specified in GB/T 12908. The AI should be placed before the GS1-128 barcode data that complies with the provisions of GB/T 15425. DI should be placed before the 128 barcode data as specified by GB/T 18347. Data encoded using the UPC-A code system should comply with GB 12904.
4.2.5.2 Linking of multiple data fields in 1D barcode symbologies
The total length of linked data in a 1D barcode symbology is preferably limited to 32 characters, including DI, AI and linking characters, but excluding code system overhead characters. If the length exceeds 32 characters, it is advisable to use 2D barcodes.
a) When linking data in a 1D barcode message, it is appropriate to use the appropriate data cell separator according to specific industry standards. The maximum length of the linked data field is limited by the barcode system used, the reading technology and the space available for barcode printing.
b) Fixed length data fields need to be allocated specific data and AI when linked.
c) When variable length data fields need to be linked using the three nines barcode system, it is advisable to use "+" plus the symbol (ASCII decimal value of 43 to separate the data fields according to the provisions of GB/T 12908.
d) When it is necessary to use the 128 barcode system to link multiple variable length data fields with DI, it is appropriate to use the "+" character (the decimal value of ASCII code is 43) to separate the data fields according to GB/T 18347.
e) When it is necessary to use GS1-128 barcode system to link multiple variable length data fields, the "FNC1" character (transmitted as "6s", the decimal value of ASCII code is 29) is used to separate the data fields between the data fields.
4.2.5.3 2D barcode data field syntax
4.3 Layout and Positioning
4.3.1 Layout
Layout refers to the position of the field on the label. The layout of a 1D or 2D barcode depends on the space available for the product and other factors such as business rules of the industry sector, trading partner agreements or customer labelling requirements.
4.3.2 Positioning
Positioning refers to the location of the label on the product. Each label should be positioned so that it can be easily scanned and does not compromise product safety or product performance. Attention should be paid to the installed product-readable barcode symbol.
4.3.3 Headings for 1D barcodes
It is desirable to use headings for the fields of 1D barcodes. When using DI, the DI is enclosed in net brackets, e.g. (1P)PART #SPLR, and when using AI, the AI is part of the human readable characters and not part of the heading, which should be in accordance with ISO/IEC 15418. The header may be located above or below the barcode symbol in accordance with industry guidelines and application standards.
The heading may be abbreviated to a DI with parentheses if the physical space available to the mark is insufficient to permit its use, and may be eliminated where space is extremely limited.
4.3.4 Human-readable characters
1D barcodes should be printed with human readable characters, which should be clearly printed. The height of the uppercase characters should be 2 mm, with a minimum height of 1.25 mm, and the DI or AI in parentheses, with the human readable characters containing all data of the barcode.
The 1D barcode symbology with DI is shown in Figure 1 and the barcode symbology with AI is shown in Figure 2.
4.4 Symbology requirements
4.4.1 Recommendations for the use of the code system
Appendix A (informative) Part serialisation of electronic products
Appendix B (informative) Part Commonly used identifiers
Appendix C (informative) GB/T 1988 character set (hexadecimal and decimal)
Appendix D (Informative) ISO/IEC 15434 Data Syntax Implementation Guide
Appendix E (informative) ISO/IEC 15459 Registration of IACs
Appendix F (Informative) Application of the Triple 9 and 128 barcode code systems
Appendix G (Informative) Application of DUNS codes and DI to 1D and 2D barcodes
Appendix H (Informative) Label Adhesion Characteristics and Mark Durability
Appendix I (Informative) Mode 36 Internal Service Code Check Character Algorithm
Bibliography
Contents of GB/T 41977-2022
1 Scope
2 Normative references
3 Terms, definitions and abbreviations
4 Requirements
Appendix A (informative) Part serialisation of electronic products
Appendix B (informative) Part Commonly used identifiers
Appendix C (informative) GB/T 1988 character set (hexadecimal and decimal)
Appendix D (Informative) ISO/IEC 15434 Data Syntax Implementation Guide
Appendix E (informative) ISO/IEC 15459 Registration of IACs
Appendix F (Informative) Application of the Triple 9 and 128 barcode code systems
Appendix G (Informative) Application of DUNS codes and DI to 1D and 2D barcodes
Appendix H (Informative) Label Adhesion Characteristics and Mark Durability
Appendix I (Informative) Mode 36 Internal Service Code Check Character Algorithm
Bibliography
