In the global multimodal transport system, a single consignment often passes through multiple carriers, transport modes and transit nodes before delivery. For a long time, consignment numbering rules have been defined independently by each logistics enterprise, requiring repeated document matching and manual data entry during cross-party handover. This not only drags down efficiency but also causes traceability chain breaks. As the core standard of the GS1 global identification system for consignment operations, the Global Identification Number for Consignment (GINC), carried by GS1 Application Identifier (AI) 401, provides a globally unified standardized identity for each consignment. It serves as the core technical foundation for enabling cross-party, cross-regional and end-to-end traceability of entire consignments.
Based on authoritative technical specifications from the official GS1 Standards Reference Library[1], this article provides a systematic technical analysis of GS1 AI 401 across six dimensions: standard definition, technical characteristics, industry practices, Digital Link implementation, technical details and development trends, serving as a standard reference and implementation guide for enterprises’ logistics digitization and supply chain traceability system construction.
1. Standard Definition and Encoding Technical Specifications
1.1 Official Definition
Per the official GS1 standard definition, AI 401 corresponds to the Global Identification Number for Consignment (GINC), an application identifier within the GS1 system dedicated to identifying individual consignments[1]. Its core function is to assign a globally unique standardized identity code to the entire batch of goods under a single shipment transaction. It covers all transport scenarios including road, rail, sea, air and multimodal transport, unifies the identity of consignments across different carriers and logistics nodes, and supports consignment-level logistics tracking and document collaboration.
1.2 Encoding Structure and Format
The complete encoding format of GS1 AI 401 is N3 + X..30, consisting of two parts: a 3-digit numeric application identifier prefix and a 1–30 character variable-length GINC body. The technical definitions of each field are shown in the table below.
Table 1 Breakdown of the GINC Encoding Structure
| Structure Segment | Length Rule | Character Type | Functional Description |
|---|---|---|---|
| Application Identifier (AI) Prefix | Fixed 3-digit numeric | Numeric only | Fixed value 401, the exclusive identification prefix assigned by GS1 to mark the following data segment as a Global Identification Number for Consignment |
| GINC Body Code | Variable length, 1–30 characters | Mixed character set | Core identity code of the consignment, assigned independently by enterprises |
Per official syntax specifications, the GINC body has no mandatory internal segmentation rules, and does not require the mandatory inclusion of a GS1 Company Prefix. Enterprises may retain their existing internal consignment numbering systems; a GINC is syntactically compliant as long as it meets the character set and length constraints. This design enables smooth compatibility with the waybill numbering conventions of different enterprises and industries, allowing standardization upgrades without rebuilding internal numbering systems.
From the best practice perspective of ensuring global uniqueness, the industry universally recommends that enterprises use their own GS1 Company Prefix as the prefix of the GINC, followed by internal consignment serial numbers. This two-tier structure of “company prefix + internal number” inherently avoids global coding conflicts.
Practical encoding example: An enterprise holds the 7-digit GS1 Company Prefix 6901234, followed by a 6-digit business type code and a 7-digit serial number. The complete GINC is 6901234YL2024060001, with a total length of 16 characters, which meets the standard requirement of no more than 30 characters.
1.3 Character Set and Encoding Constraints
Per official GS1 specifications, the valid character set for the GINC body strictly matches the regular expression ([!%-?A-Z_a-z\x22]{1,30})[1]. Allowed characters include:
- Uppercase and lowercase English letters (A-Z, a-z), Arabic numerals (0-9), underscore (
_), and double quotation mark (", i.e. ASCII \x22); - Printable standard symbols in the ASCII range from
!to?, covering common punctuation and business separators; - Chinese characters, full-width characters and other non-standard special characters are not supported, and the total length is strictly controlled between 1 and 30 characters.
Important note: This standard does not define a built-in check digit. Code validity is guaranteed through character set rules, length constraints and business system uniqueness verification mechanisms, and is not subject to the modulo 10 check algorithm.
1.4 Core Technical Attributes
Based on official specifications, the core technical attributes of GINC are summarized in the table below.
Table 2 Core Technical Attributes of GS1 AI 401
| Technical Item | Official Specification | Description |
|---|---|---|
| FNC1 separator requirement | Mandatory (Yes) | As a variable-length identifier, its data segment must be separated from subsequent identifiers by FNC1 when used in a GS1 element string |
| Mandatory associated identifiers | None | Can be used independently and does not require binding to other GS1 Application Identifiers |
| Invalid pairing rules | None | No explicitly mutually exclusive Application Identifiers; can be freely combined with most GS1 standard AIs |
| GS1 Digital Link primary key capability | Supported (Yes) | Can be used as an independent primary key to build URIs and create dedicated digital entries for consignments |
| GS1 Digital Link key qualifier | None | No dedicated associated key qualifier |
| GS1 Digital Link attribute capability | Supported (Yes) | Can be embedded as an additional data attribute in URIs built on other primary keys |
2. Core Technical Functions and System Positioning
2.1 Core Technical Positioning
The core positioning of GINC is the global identity anchor for consignment-level goods, forming a clear hierarchical complement with the SSCC (Serial Shipping Container Code):
- SSCC (AI 00) targets individual logistics units (pallets, totes, cartons), with granularity at the single load carrier level;
- GINC (AI 401) targets the entire consignment transaction, with granularity covering all goods under one transport contract. One consignment may contain one or more SSCC logistics units.
Together, they build a two-tier identification system of “logistics unit – consignment batch”, adapting to the different needs of fine-grained unit management and consignment-level business collaboration respectively.
2.2 Core Technical Characteristics
(1) Global Uniqueness Guarantee Mechanism
At the syntax level, GINC does not mandate a built-in company prefix, but at the implementation level, it is recommended to rely on the GS1 layered allocation system to achieve uniqueness: enterprises build the GINC prefix based on their own GS1 Company Prefix, and independently assign consignment serial numbers within the number range. This two-tier allocation mechanism ensures that each consignment corresponds to a unique code worldwide, avoiding cross-enterprise and cross-regional number conflicts, and fundamentally solving the problem of incompatible traditional waybill numbers.
(2) Multi-Carrier Data Format Specifications
GINC can be carried by multiple physical carriers to adapt to different logistics scenarios:
- Linear barcodes: Adopt GS1-128 format, suitable for traditional waybills, logistics labels and other scenarios, compatible with existing frontline scanning devices;
- 2D barcodes: Adopt GS1 DataMatrix or GS1 QR Code format, which can carry GINC and extended information such as shipper/consignee details and batch numbers at the same time, suitable for digital documents and mobile scanning scenarios;
- RFID tags: Can be encoded in EPC format, supporting contactless batch reading, suitable for fast batch cargo verification scenarios such as ports and terminals.
(3) Universal Automatic Identification Compatibility
GINC fully complies with the general GS1 element string syntax. All GS1-compliant industrial scanners, handheld terminals and fixed gantry scanning devices can natively recognize and parse it without customized decoding logic development. Enterprises can deploy directly based on existing logistics hardware infrastructure with low transformation cost and short implementation cycle.
(4) Flexible and Extensible Architecture Design
The variable-length design of 1–30 characters balances standardization and flexibility: large enterprises can use longer codes to carry more business dimensions, while small and medium-sized enterprises can retain existing short numbering rules without major transformation of internal business systems to adapt to the standard. Meanwhile, the design without mandatory segmentation enables it to adapt to consignment numbering conventions across different industries and transport modes.
2.3 Technical Integration with Other GS1 Identifiers
GINC can be freely combined with various identifiers in the GS1 system to form a complete logistics data network:
- With SSCC (AI 00): One-to-many containment relationship. One consignment (GINC) can contain multiple logistics units (SSCC), enabling two-way traceability between the whole consignment and individual units through combined encoding;
- With GTIN (AI 01): Cargo content association relationship, identifying the trade item categories corresponding to the consigned goods and supporting rapid verification of the entire consignment;
- With GLN (Global Location Number): Shipper/consignee location association, accurately identifying the origin and destination of the consignment.
3. Industry Application Practices and System Integration
3.1 Third-Party Logistics: End-to-End Traceability for Cross-Border Multimodal Transport
System integration architecture: With GINC as the core identifier, connect the TMS (Transportation Management System), multimodal transport collaboration platform and customs declaration system to realize unified identification of the entire consignment from dispatch, transit and customs clearance to delivery. Data collection workflow: Upon booking confirmation, the system automatically generates a unique GINC prefixed with the company prefix, and binds all SSCC lists, manifest information and transport plans for the consignment. At each transit node, scanning the GINC automatically updates the transport status and node timestamp. Upon arrival, customs and the consignee can retrieve full-chain documents and trajectory information directly via the GINC. Hardware configuration requirements: Industrial-grade explosion-proof handheld terminals and port fixed gantry scanning devices, supporting GS1-128 and GS1 DataMatrix parsing, adaptable to high and low temperature and dusty port operating environments. Software interface standards: Complies with GS1 EDI standards, enabling automatic cross-enterprise and cross-carrier GINC data synchronization via IFTMIN (transport instruction) and IFTMCS (transport status notification) messages.
3.2 Retail & FMCG: Centralized Warehouse and Distribution Consignment Receiving Collaboration
System integration architecture: The retail distribution center WMS and supplier TMS use GINC as the unified handover identifier to realize fast receiving and automatic matching of entire consignments. Data collection workflow: When shipping, the supplier assigns a unique GINC to each distribution order, and synchronizes the GINC corresponding item details, quantity and batch information to the retail DC in advance via ASN (Advance Shipping Notice). Upon arrival, warehouse staff scan the pallet SSCC to automatically associate the corresponding GINC. After the entire consignment is verified, inbound registration is completed in batches without case-by-case counting. Hardware configuration requirements: Desktop 2D scanners and high-speed logistics label printers, supporting high-precision GS1 QR Code printing and recognition. Software interface standards: Supports DESADV (despatch advice) EDI messages, enabling automatic alignment of GINC and ASN data; connects to WMS inbound interfaces, supporting batch inbound posting for entire consignments.
3.3 Automotive Manufacturing: Consignment Handover for Inbound Logistics Milk-Run Operations
System integration architecture: The OEM’s inbound logistics system and supplier collaboration platform use GINC as the core identifier for each milk-run trip, realizing consignment handover and rapid verification of goods from multiple suppliers. Data collection workflow: Each milk-run trip is assigned a unique GINC, bound to the tote SSCC list and material details from all suppliers on the trip. After loading at each supplier site, the vehicle scans the GINC to complete node confirmation. Upon arrival at the OEM’s inbound warehouse, scanning the GINC completes inbound registration for the entire consignment and deducts supplier inventory in one step. Hardware configuration requirements: Vehicle-mounted industrial scanning terminals and explosion-proof handheld terminals, adaptable to complex operating conditions in production plants. Software interface standards: Connects to MES and SRM systems, realizing data linkage between GINC and material requirements and production scheduling through standard APIs.
4. Technical Implementation of GS1 Digital Link (Key Section)
GS1 Digital Link is the core technical path for GINC to upgrade from offline barcode identification to a digital logistics entry point, and also the key support for realizing end-to-end traceability of entire consignments.
4.1 URI Construction Rules
GINC has a dual identity in the GS1 Digital Link system: it can be used as an independent primary key, or embedded as an additional attribute in URIs of other primary keys. The specific construction rules are as follows:
- As an independent primary key: The GINC code is placed directly after AI 401 as a path segment, following the format
https://[enterprise domain]/401/[complete GINC code]. It corresponds to the dedicated digital homepage of one consignment, displaying full information such as logistics trajectory, cargo details and document files. - As an additional attribute: Embedded in URIs of other primary keys such as SSCC, following the format
https://[enterprise domain]/00/[SSCC code]/401/[GINC code]. It is used to identify the consignment batch to which a single logistics unit belongs, enabling reverse traceability from individual units to the entire consignment.
Since the GINC body is a continuous string with no internal separator, it is carried as a single path segment in the URI without additional separation markers.
4.2 Complete Examples
- Primary key mode example (with GS1 Company Prefix):
https://id.logistics.com/401/6901234YL2024060001 - Attribute mode example:
https://id.logistics.com/00/123456789012345678/401/6901234YL2024060001
4.3 Parsing Mechanism and Data Interaction Workflow
- The scanning terminal (smartphone or professional device) recognizes the GINC Digital Link URI in the GS1 2D barcode.
- The terminal initiates an HTTPS request to the enterprise’s Digital Link server, which identifies the requester’s identity (consignee, carrier, regulator) based on request headers and context.
- The system returns corresponding content based on permissions: full trajectory and details for the cargo owner, estimated delivery time and receiving guidelines for the consignee, and compliance document data for regulators.
- Data output follows the JSON-LD structured standard, supporting automatic machine parsing and seamless integration with business systems without manual secondary entry.
4.4 Technical Advantages Over Traditional Consignment Barcodes
Table 3 Comparison of GINC Digital Link and Traditional Waybill Barcodes
| Comparison Dimension | Traditional Waybill Barcode | GINC Digital Link |
|---|---|---|
| Information capacity | Carries only the waybill number; details require access to a dedicated system | Directly maps to a digital homepage; trajectory, documents and details are available by scanning |
| Cross-platform interoperability | Only recognizable by internal systems; cross-party access requires API integration | Based on standard HTTP protocol, accessible by any terminal without a dedicated app |
| Data update capability | Information is fixed after barcode generation and cannot be dynamically updated | Server-side data is updated in real time; rules and status can be adjusted dynamically |
| Traceability granularity | Only supports consignment-level node query | Supports multi-level two-way traceability from consignment to logistics unit to individual item |
| Interaction capability | One-way information reading only | Supports two-way interactions such as scan-to-sign, exception reporting and document download |
4.5 End-to-End Traceability Application Solution
Based on GINC Digital Link, a “one-code-through” consignment traceability system can be built: a GS1 2D barcode with GINC URI is generated when the consignment departs, and is affixed to the waybill and each logistics unit label. All transit nodes can update trajectory data by scanning the code and obtain upstream and downstream node information at the same time. The final consignee can view all transport nodes, temperature and humidity records and corresponding documents by scanning the code, realizing full-chain transparency of the entire consignment.
5. Technical Details and Usage Specifications
5.1 Independent Encoding Rules
When used independently, GINC follows the general GS1 element string syntax: it starts with the AI prefix 401, followed by the 1–30 character GINC body. If there are subsequent identifiers in the element string, the FNC1 separator must be added at the end of the GINC data segment.
- Basic encoding example (with GS1 Company Prefix):
(401)6901234YL2024060001
5.2 Combined Encoding Rules
GINC can be freely combined with other GS1 Application Identifiers to carry multiple pieces of information. Taking the “SSCC + GINC” combination as an example:
- Encoding example:
(00)123456789012345678(401)6901234YL2024060001 - Parsing rule: First read the fixed-length SSCC code, then read the GINC code until FNC1 or the end of the barcode. Since SSCC is fixed-length, the variable-length GINC can follow directly without additional separation.
Chart suggestion: A combined encoding structure diagram may be drawn, showing from left to right the FNC1 start character, AI 00 + SSCC, and AI 401 + GINC + FNC1 in a layered structure, to visually illustrate the encoding composition and separation rules.
5.3 Usage Restrictions and Best Practices
- Length restriction: The GINC body must be strictly controlled between 1 and 30 characters. Exceeding the length will cause standard devices to fail to parse correctly.
- Character specification: Only characters within the regular expression definition shall be used. Chinese characters, full-width symbols and non-standard special characters are prohibited to ensure universal recognition by devices worldwide.
- Uniqueness constraint: One consignment corresponds to one unique GINC. The same code must not be reused for different consignment transactions to avoid traceability confusion.
- FNC1 specification: If other identifiers follow the variable-length GINC, an FNC1 separator must be added to avoid parsing ambiguity.
- Coding allocation best practice: Although not mandatory at the syntax level, scenarios such as cross-enterprise mutual recognition and cross-border logistics recommend constructing GINC using the “GS1 Company Prefix + internal serial number” structure to ensure global uniqueness and cross-party interoperability.
5.4 Code Verification Methods
- Regular expression verification: Verify character set and length compliance using the official regular expression
([!%-?A-Z_a-z\x22]{1,30}), which can be directly integrated into enterprise code generation systems. - Standard tool verification: Use official GS1 AI syntax verification tools to verify compliance of element string format and FNC1 separator usage.
- Business verification: Enterprise internal systems must perform uniqueness verification on GINC to ensure no duplicate or conflicting codes.
6. Technology Development Trends and Evolution Directions
6.1 Digital Identity Foundation for Cross-Border Logistics
With the advancement of global trade integration, demand for unified identification in cross-border logistics continues to grow. As a globally universal consignment identification standard, GINC will gradually connect with national single windows and customs declaration systems, becoming a standardized identity credential for cross-border consignments. In the future, a single GINC will support the entire declaration, transshipment and customs clearance process from the country of origin to the destination country, greatly improving cross-border logistics efficiency.
6.2 Integration with IoT Technology: Real-Time Consignment Status Sensing
Against the backdrop of widespread IoT technology adoption, GINC will evolve from a static identity identifier to a dynamic data entry point. By binding GINC with positioning, temperature/humidity and shock sensors installed on the consignment, users can obtain real-time status data of the entire consignment by scanning the code, realizing active monitoring and anomaly warning during transport and replacing the traditional node-based passive traceability model.
6.3 Core Index for Blockchain Trusted Traceability
In cross-border logistics and multimodal transport scenarios, data trust between different parties is the core pain point. GINC can serve as the core index of a blockchain depository system, with full-chain data of consignment dispatch, transit, receipt and customs clearance stored on-chain for evidence preservation, ensuring data immutability and traceability. Compared with enterprise-customized waybill numbers, the globally unified GINC enables cross-platform and cross-party on-chain data mutual recognition, building a trusted logistics traceability network.
6.4 AI-Driven Intelligent Logistics Scheduling
Based on full-chain logistics data accumulated via standardized GINC, more accurate AI models for time-of-arrival prediction, route optimization and risk warning can be trained. The unified coding standard eliminates data barriers between different carriers and systems, provides high-quality and full-coverage basic datasets for AI models, and drives logistics scheduling to upgrade from experience-driven to data-intelligent.
6.5 Standard Evolution Direction
Combined with the GS1 digital transformation roadmap, the GINC standard may continue to be optimized in two directions in the future: first, supplementing the qualifier system to support standardized carriage of extended attributes such as transport mode and consignment type; second, deepening integration with Digital Product Passports (DPP) to support consignment-level transmission and verification of cross-border cargo compliance data, further expanding the application boundary of the standard.
Closing
GS1 AI 401 (Global Identification Number for Consignment, GINC) is an important part of the GS1 logistics identification system, filling the gap of globally unified identification at the consignment batch level. At the syntax level, it does not mandate a built-in company prefix, has high flexibility, and is compatible with enterprises’ existing waybill systems. At the implementation level, it is recommended to build GINC with the GS1 Company Prefix as the prefix to ensure global uniqueness and cross-party interoperability.
For industries such as logistics, retail and manufacturing, implementing the GINC standard not only improves consignment handover efficiency and opens up cross-party traceability chains, but also lays a standardized foundation for future scenarios such as logistics digitization, intelligent scheduling and trusted depository. As the digitization level of global supply chains continues to improve, GINC will gradually become the universal “identity language” in the global consignment field, supporting the efficient, transparent and trusted operation of multimodal transport and cross-border trade.