3 GS1 Application Identifier definitions
3.1 Introduction
This section describes the meaning, structure and function of the GS1 system element strings so they can be correctly processed in users’ application programmes. An element string is the combination of a GS1 Application Identifier and a GS1 Application Identifier data field. The allowable character set to be used for GS1 Application Identifier element strings is defined in section 7.11.
There are AIs that have additional syntax restrictions, e.g., numerical only; see below definition for each AI. Automatic processing of element strings in business applications requires information about the type of transaction to which the transferred data refers. See section 7 for an explanation of this process.
Element strings can be carried by GS1-128, GS1 DataBar symbology, GS1 Composite, GS1 DataMatrix and GS1 QR Code symbols. The rules for use and interrelationships between the GS1 Application Identifiers are contained in section 2 and 4.
When a predefined length GS1 key and attributes are encoded together, the GS1 key SHOULD appear before the attributes. In most cases predefined length element strings SHOULD be followed by non-predefined element strings. The sequence of predefined and non-predefined element strings should be at the discretion of the creator of the element strings.
3.2 GS1 Application Identifiers in numerical order
Table 3-1 GS1 Application Identifiers
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 00 | Identification of a logistic unit (SSCC): AI (00) | N2+N18 | SSCC | |
| 01 | Identification of a trade item (GTIN): AI (01) | N2+N14 | GTIN | |
| 02 | Identification of trade items contained in a logistic unit: AI (02) | N2+N14 | CONTENT | |
| 03 | Identification of a Made-to-Order (MtO) trade item (GTIN): AI (03) | N2+N14 | MTO GTIN | |
| 10 | Batch or lot number: AI (10) | N2+X..20 | (FNC1) | BATCH/LOT |
| 11 (2) | Production date: AI (11) | N2+N6 | PROD DATE | |
| 12 (2) | Due date for amount on payment slip: AI (12) | N2+N6 | DUE DATE | |
| 13 (2) | Packaging date: AI (13) | N2+N6 | PACK DATE | |
| 15 (2) | Best before date: AI (15) | N2+N6 | BEST BEFORE or BEST BY | |
| 16 (2) | Sell by date: AI (16) | N2+N6 | SELL BY | |
| 17 (2) | Expiration date: AI (17) | N2+N6 | USE BY or EXPIRY | |
| 20 | Internal product variant: AI (20) | N2+N2 | VARIANT | |
| 21 | Serial number: AI (21) | N2+X..20 | (FNC1) | SERIAL |
| 22 | Consumer product variant: AI (22) | N2+X..20 | (FNC1) | CPV |
| 235 | Third Party Controlled, Serialised Extension of Global Trade Item Number (GTIN) (TPX): AI (235) | N3+X..28 | (FNC1) | TPX |
| 240 | Additional product identification assigned by the manufacturer: AI (240) | N3+X..30 | (FNC1) | ADDITIONAL ID |
| 241 | Customer part number: AI (241) | N3+X..30 | (FNC1) | CUST. PART No. |
| 242 | Made-to-Order variation number: AI (242) | N3+N..6 | (FNC1) | MTO VARIANT |
| 243 | Packaging component number: AI (243) | N3+X..20 | (FNC1) | PCN |
| 250 | Secondary serial number: AI (250) | N3+X..30 | (FNC1) | SECONDARY SERIAL |
| 251 | Reference to source entity: AI (251) | N3+X..30 | (FNC1) | REF. TO SOURCE |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 253 | Global Document Type Identifier (GDTI): AI (253) | N3+N13+[X..17] | (FNC1) | GDTI |
| 254 | Global Location Number (GLN) extension component: AI (254) | N3+X..20 | (FNC1) | GLN EXTENSION COMPONENT |
| 255 | Global Coupon Number (GCN): AI (255) | N3+N13+[N..12] | (FNC1) | GCN |
| 30 | Variable count of items: AI (30) | N2+N..8 | (FNC1) | VAR. COUNT |
| 310n (3) | Net weight, kilograms (variable measure trade item) | N4+N6 | NET WEIGHT (kg) | |
| 311n (3) | Length or first dimension, metres (variable measure trade item) | N4+N6 | LENGTH (m) | |
| 312n (3) | Width, diameter, or second dimension, metres (variable measure trade item) | N4+N6 | WIDTH (m) | |
| 313n (3) | Depth, thickness, height, or third dimension, metres (variable measure trade item) | N4+N6 | HEIGHT (m) | |
| 314n (3) | Area, square metres (variable measure trade item) | N4+N6 | AREA (m2) | |
| 315n (3) | Net volume, litres (variable measure trade item) | N4+N6 | NET VOLUME (l) | |
| 316n (3) | Net volume, cubic metres (variable measure trade item) | N4+N6 | NET VOLUME (m3) | |
| 320n (3) | Net weight, pounds (variable measure trade item) | N4+N6 | NET WEIGHT (lb) | |
| 321n (3) | Length or first dimension, inches (variable measure trade item) | N4+N6 | LENGTH (in) | |
| 322n (3) | Length or first dimension, feet (variable measure trade item) | N4+N6 | LENGTH (ft) | |
| 323n (3) | Length or first dimension, yards (variable measure trade item) | N4+N6 | LENGTH (yd) | |
| 324n (3) | Width, diameter, or second dimension, inches (variable measure trade item) | N4+N6 | WIDTH (in) | |
| 325n (3) | Width, diameter, or second dimension, feet (variable measure trade item) | N4+N6 | WIDTH (ft) | |
| 326n (3) | Width, diameter, or second dimension, yards (variable measure trade item) | N4+N6 | WIDTH (yd) | |
| 327n (3) | Depth, thickness, height, or third dimension, inches (variable measure trade item) | N4+N6 | HEIGHT (in) | |
| 328n (3) | Depth, thickness, height, or third dimension, feet (variable measure trade item) | N4+N6 | HEIGHT (ft) | |
| 329n (3) | Depth, thickness, height, or third dimension, yards (variable measure trade item) | N4+N6 | HEIGHT (yd) | |
| 330n (3) | Logistic weight, kilograms | N4+N6 | GROSS WEIGHT (kg) | |
| 331n (3) | Length or first dimension, metres | N4+N6 | LENGTH (m), log | |
| 332n (3) | Width, diameter, or second dimension, metres | N4+N6 | WIDTH (m), log | |
| 333n (3) | Depth, thickness, height, or third dimension, metres | N4+N6 | HEIGHT (m), log | |
| 334n (3) | Area, square metres | N4+N6 | AREA (m2), log | |
| 335n (3) | Logistic volume, litres | N4+N6 | VOLUME (l), log | |
| 336n (3) | Logistic volume, cubic metres | N4+N6 | VOLUME (m3), log | |
| 337n (3) | Kilograms per square metre | N4+N6 | KG PER m² | |
| 340n (3) | Logistic weight, pounds | N4+N6 | GROSS WEIGHT (lb) | |
| 341n (3) | Length or first dimension, inches | N4+N6 | LENGTH (in), log | |
| 342n (3) | Length or first dimension, feet | N4+N6 | LENGTH (ft), log | |
| 343n (3) | Length or first dimension, yards | N4+N6 | LENGTH (yd), log |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 344n (3) | Width, diameter, or second dimension, inches | N4+N6 | WIDTH (in), log | |
| 345n (3) | Width, diameter, or second dimension, feet | N4+N6 | WIDTH (ft), log | |
| 346n (3) | Width, diameter, or second dimension, yard | N4+N6 | WIDTH (yd), log | |
| 347n (3) | Depth, thickness, height, or third dimension, inches | N4+N6 | HEIGHT (in), log | |
| 348n (3) | Depth, thickness, height, or third dimension, feet | N4+N6 | HEIGHT (ft), log | |
| 349n (3) | Depth, thickness, height, or third dimension, yards | N4+N6 | HEIGHT (yd), log | |
| 350n (3) | Area, square inches (variable measure trade item) | N4+N6 | AREA (in2) | |
| 351n (3) | Area, square feet (variable measure trade item) | N4+N6 | AREA (ft2) | |
| 352n (3) | Area, square yards (variable measure trade item) | N4+N6 | AREA (yd2) | |
| 353n (3) | Area, square inches | N4+N6 | AREA (in2), log | |
| 354n (3) | Area, square feet | N4+N6 | AREA (ft2), log | |
| 355n (3) | Area, square yards | N4+N6 | AREA (yd2), log | |
| 356n (3) | Net weight, troy ounces (variable measure trade item) | N4+N6 | NET WEIGHT (tr oz) | |
| 357n (3) | Net weight (or volume), ounces (variable measure trade item) | N4+N6 | NET VOLUME (oz) | |
| 360n (3) | Net volume, quarts (variable measure trade item) | N4+N6 | NET VOLUME (qt (US)) | |
| 361n (3) | Net volume, gallons U.S. (variable measure trade item) | N4+N6 | NET VOLUME (gal (US)) | |
| 362n (3) | Logistic volume, quarts | N4+N6 | VOLUME (qt (US)), log | |
| 363n (3) | Logistic volume, gallons U.S. | N4+N6 | VOLUME (gal (US)), log | |
| 364n (3) | Net volume, cubic inches (variable measure trade item) | N4+N6 | NET VOLUME (in3) | |
| 365n (3) | Net volume, cubic feet (variable measure trade item) | N4+N6 | NET VOLUME (ft3) | |
| 366n (3) | Net volume, cubic yards (variable measure trade item) | N4+N6 | NET VOLUME (yd3) | |
| 367n (3) | Logistic volume, cubic inches | N4+N6 | VOLUME (in3), log | |
| 368n (3) | Logistic volume, cubic feet | N4+N6 | VOLUME (ft3), log | |
| 369n (3) | Logistic volume, cubic yards | N4+N6 | VOLUME (yd3), log | |
| 37 | Count of trade items or trade item pieces contained in a logistic unit: AI (37) | N2+N..8 | (FNC1) | COUNT |
| 390n (3) | Amount payable or coupon value - Single monetary area: AI (390n) | N4+N..15 | (FNC1) | AMOUNT |
| 391n (3) | Amount payable and ISO currency code: AI (391n) | N4+N3+N..15 | (FNC1) | AMOUNT |
| 392n (3) | Amount payable for a variable measure trade item – Single monetary area: AI (392n) | N4+N..15 | (FNC1) | PRICE |
| 393n (3) | Amount payable for a variable measure trade item and ISO currency code: AI (393n) | N4+N3+N..15 | (FNC1) | PRICE |
| 394n (3) | Percentage discount of a coupon: AI (394n) | N4+N4 | (FNC1) | PRCNT OFF |
| 395n (3) | Amount payable per unit of measure single monetary area (variable measure trade item): AI (395n) | N4+N6 | (FNC1) | PRICE/UoM |
| 400 | Customer’s purchase order number: AI (400) | N3+X..30 | (FNC1) | ORDER NUMBER |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 401 | Global Identification Number for Consignment (GINC): AI (401) | N3+X..30 | (FNC1) | GINC |
| 402 | Global Shipment Identification Number (GSIN): AI (402) | N3+N17 | (FNC1) | GSIN |
| 403 | Routing code: AI (403) | N3+X..30 | (FNC1) | ROUTE |
| 410 | Ship to - Deliver to Global Location Number (GLN): AI (410) | N3+N13 | SHIP TO LOC | |
| 411 | Bill to - Invoice to Global Location Number (GLN): AI (411) | N3+N13 | BILL TO | |
| 412 | Purchased from Global Location Number (GLN): AI (412) | N3+N13 | PURCHASE FROM | |
| 413 | Ship for - Deliver for - Forward to Global Location Number (GLN): AI (413) | N3+N13 | SHIP FOR LOC | |
| 414 | Identification of a physical location - Global Location Number (GLN): AI (414) | N3+N13 | LOC No. | |
| 415 | Global Location Number (GLN) of the invoicing party: AI (415) | N3+N13 | PAY TO | |
| 416 | Global Location Number (GLN) of the production or service location: AI (416) | N3+N13 | PROD/SERV LOC | |
| 417 | Party Global Location Number (GLN): AI (417) | N3+N13 | PARTY | |
| 420 | Ship-to / Deliver-to postal code within a single postal authority: AI (420) | N3+X..20 | (FNC1) | SHIP TO POST |
| 421 | Ship-to / Deliver-to postal code with three-digit ISO country code: AI (421) | N3+N3+X..9 | (FNC1) | SHIP TO POST |
| 422 | Country of origin of a trade item: AI (422) | N3+N3 | (FNC1) | ORIGIN |
| 423 | Country of initial processing: AI (423) | N3+N3+N..12 | (FNC1) | COUNTRY - INITIAL PROCESS |
| 424 | Country of processing: AI (424) | N3+N3 | (FNC1) | COUNTRY - PROCESS |
| 425 | Country of disassembly: AI (425) | N3+N3+N..12 | (FNC1) | COUNTRY - DISASSEMBLY |
| 426 | Country covering full process chain: AI (426) | N3+N3 | (FNC1) | COUNTRY – FULL PROCESS |
| 427 | Country subdivision of origin code for a trade item: AI (427) | N3+X..3 | (FNC1) | ORIGIN SUBDIVISION |
| 4300 | Ship-to / Deliver-to Company name: AI (4300) | N4+X..35 | (FNC1) | SHIP TO COMP |
| 4301 | Ship-to / Deliver-to contact name: AI (4301) | N4+X..35 | (FNC1) | SHIP TO NAME |
| 4302 | Ship-to / Deliver-to address line 1: AI (4302) | N4+X..70 | (FNC1) | SHIP TO ADD1 |
| 4303 | Ship-to / Deliver-to address line 2: AI (4303) | N4+X..70 | (FNC1) | SHIP TO ADD2 |
| 4304 | Ship-to / Deliver-to suburb: AI (4304) | N4+X..70 | (FNC1) | SHIP TO SUB |
| 4305 | Ship-to / Deliver-to locality: AI (4305) | N4+X..70 | (FNC1) | SHIP TO LOC |
| 4306 | Ship-to / Deliver-to region: AI (4306) | N4+X..70 | (FNC1) | SHIP TO REG |
| 4307 | Ship-to / Deliver-to country code: AI (4307) | N4+X2 | (FNC1) | SHIP TO COUNTRY |
| 4308 | Ship-to / Deliver-to telephone number: AI (4308) | N4+X..30 | (FNC1) | SHIP TO PHONE |
| 4309 | Ship-to / Deliver-to GEO location: AI (4309) | N4+N20 | (FNC1) | SHIP TO GEO |
| 4310 | Return-to company name: AI (4310) | N4+X..35 | (FNC1) | RTN TO COMP |
| 4311 | Return-to contact name: AI (4311) | N4+X..35 | (FNC1) | RTN TO NAME |
| 4312 | Return-to address line 1: AI (4312) | N4+X..70 | (FNC1) | RTN TO ADD1 |
| 4313 | Return-to address line 2: AI (4313) | N4+X..70 | (FNC1) | RTN TO ADD2 |
| 4314 | Return-to suburb: AI (4314) | N4+X..70 | (FNC1) | RTN TO SUB |
| 4315 | Return-to locality: AI (4315) | N4+X..70 | (FNC1) | RTN TO LOC |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 4316 | Return-to region: AI (4316) | N4+X..70 | (FNC1) | RTN TO REG |
| 4317 | Return-to country code: AI (4317) | N4+X2 | (FNC1) | RTN TO COUNTRY |
| 4318 | Return-to postal code: AI (4318) | N4+X..20 | (FNC1) | RTN TO POST |
| 4319 | Return-to telephone number: AI (4319) | N4+X..30 | (FNC1) | RTN TO PHONE |
| 4320 | Service code description: AI (4320) | N4+X..35 | (FNC1) | SRV DESCRIPTION |
| 4321 | Dangerous goods flag: AI (4321) | N4+N1 | (FNC1) | DANGEROUS GOODS |
| 4322 | Authority to leave flag: AI (4322) | N4+N1 | (FNC1) | AUTH LEAVE |
| 4323 | Signature required flag: AI (4323) | N4+N1 | (FNC1) | SIG REQUIRED |
| 4324 | Not before delivery date/time: AI (4324) | N4+N10 | (FNC1) | NBEF DEL DT |
| 4325 | Not after delivery date/time: AI (4325) | N4+N10 | (FNC1) | NAFT DEL DT |
| 4326 | Release date: AI (4326) | N4+N6 | (FNC1) | REL DATE |
| 4330(7) | Maximum temperature in Fahrenheit: AI (4330) | N4+N6+[-] | (FNC1) | MAX TEMP F |
| 4331(7) | Maximum temperature in Celsius: AI (4331) | N4+N6+[-] | (FNC1) | MAX TEMP C |
| 4332(7) | Minimum temperature in Fahrenheit: AI (4332) | N4+N6+[-] | (FNC1) | MIN TEMP F |
| 4333(7) | Minimum temperature in Celsius: AI (4333) | N4+N6+[-] | (FNC1) | MIN TEMP C |
| 7001 | NATO Stock Number (NSN): AI (7001) | N4+N13 | (FNC1) | NSN |
| 7002 | UNECE meat carcasses and cuts classification: AI (7002) | N4+X..30 | (FNC1) | MEAT CUT |
| 7003 | Expiration date and time: AI (7003) | N4+N10 | (FNC1) | EXPIRY TIME |
| 7004 | Active potency: AI (7004) | N4+N..4 | (FNC1) | ACTIVE POTENCY |
| 7005 | Catch area: AI (7005) | N4+X..12 | (FNC1) | CATCH AREA |
| 7006 | First freeze date: AI (7006) | N4+N6 | (FNC1) | FIRST FREEZE DATE |
| 7007 | Harvest date: AI (7007) | N4+N6+[N6] | (FNC1) | HARVEST DATE |
| 7008 | Species for fishery purposes: AI (7008) | N4+X..3 | (FNC1) | AQUATIC SPECIES |
| 7009 | Fishing gear type: AI (7009) | N4+X..10 | (FNC1) | FISHING GEAR TYPE |
| 7010 | Production method: AI (7010) | N4+X..2 | (FNC1) | PROD METHOD |
| 7011 | Test by date: AI (7011) | N4+N6+[N4] | (FNC1) | TEST BY DATE |
| 7020 | Refurbishment lot ID: AI (7020) | N4+X..20 | (FNC1) | REFURB LOT |
| 7021 | Functional status: AI (7021) | N4+X..20 | (FNC1) | FUNC STAT |
| 7022 | Revision status: AI (7022) | N4+X..20 | (FNC1) | REV STAT |
| 7023 | Global Individual Asset Identifier of an assembly: AI (7023) | N4+X..30 | (FNC1) | GIAI – ASSEMBLY |
| 703s (6) | Number of processor with three-digit ISO country code: AI (703s) | N4+N3+X..27 | (FNC1) | PROCESSOR # s |
| 7040 | GS1 UIC with Extension 1 and Importer index: AI (7040) | N4+N1+X3 | (FNC1) | UIC+EXT |
| 7041 | UN/CEFACT freight unit type: AI (7041) | N4+X..4 | (FNC1) | UFRGT UNIT TYPE |
| 710 | National Healthcare Reimbursement Number (NHRN) – Germany PZN: AI (710) | N3+X..20 | (FNC1) | NHRN PZN |
| 711 | National Healthcare Reimbursement Number (NHRN) – France CIP: AI 711) | N3+X..20 | (FNC1) | NHRN CIP |
| 712 | National Healthcare Reimbursement Number (NHRN) – Spain CN: AI (712) | N3+X..20 | (FNC1) | NHRN CN |
| 713 | National Healthcare Reimbursement Number (NHRN) – Brasil DRN: AI (713) | N3+X..20 | (FNC1) | NHRN DRN |
| 714 | National Healthcare Reimbursement Number (NHRN) – Portugal AIM: AI (714) | N3+X..20 | (FNC1) | NHRN AIM |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 715 | National Healthcare Reimbursement Number (NHRN) – United States of America NDC: AI (715) | N3+X..20 | (FNC1) | NHRN NDC |
| 716 | National Healthcare Reimbursement Number (NHRN) – Italy AIC: AI (716) | N3+X..20 | (FNC1) | NHRN AIC |
| 717 | National Healthcare Reimbursement Number (NHRN) – Costa Rica Sanitary Register Number: AI (717) | N3+X..20 | (FNC1) | NHRN SRN |
| ... (5) | National Healthcare Reimbursement Number (NHRN) – Country “A” NHRN | N3+X..20 | (FNC1) | NHRN xxx |
| 723s (6) | Certification reference: AI (723s) | N4+X2+X..28 | (FNC1) | CERT # s |
| 7240 | Protocol ID: AI (7240) | N4+X..20 | (FNC1) | PROTOCOL |
| 7241 | AIDC media type: AI (7241) | N4+N2 | (FNC1) | AIDC MEDIA TYPE |
| 7242 | Version Control Number (VCN): AI (7242) | N4+X…25 | (FNC1) | VCN |
| 7250 | Date of birth: AI (7250) | N4+N8 | (FNC1) | DOB |
| 7251 | Date and time of birth: AI (7251) | N4+N12 | (FNC1) | DOB TIME |
| 7252 | Biological sex: AI (7252) | N4+N1 | (FNC1) | BIO SEX |
| 7253 | Family name of person: AI (7253) | N4+X..40 | (FNC1) | FAMILY NAME |
| 7254 | Given name of person: AI (7254) | N4+X..40 | (FNC1) | GIVEN NAME |
| 7255 | Name suffix of person: AI (7255) | N4+X..10 | (FNC1) | SUFFIX |
| 7256 | Full name of person: AI (7256) | N4+X..90 | (FNC1) | FULL NAME |
| 7257 | Address of person: AI (7257) | N4+X..70 | (FNC1) | PERSON ADDR |
| 7258 | Baby birth sequence indicator: AI (7258) | N4+N1+X1+N1 | (FNC1) | BIRTH SEQUENCE |
| 7259 | Baby of family name: AI (7259) | N4+X..40 | (FNC1) | BABY |
| 8001 | Roll products - width, length, core diameter, direction, splices: AI (8001) | N4+N14 | (FNC1) | DIMENSIONS |
| 8002 | Cellular mobile telephone identifier: AI (8002) | N4+X..20 | (FNC1) | CMT No. |
| 8003 | Global Returnable Asset Identifier (GRAI): AI (8003) | N4+N14+[X..16] | (FNC1) | GRAI |
| 8004 | Global Individual Asset Identifier (GIAI): AI (8004) | N4+X..30 | (FNC1) | GIAI |
| 8005 | Price per unit of measure: AI (8005) | N4+N6 | (FNC1) | PRICE PER UNIT |
| 8006 | Identification of an individual trade item piece (ITIP): AI (8006) | N4+N14+N2+N2 | (FNC1) | ITIP |
| 8007 | International Bank Account Number (IBAN): AI (8007) | N4+X..34 | (FNC1) | IBAN |
| 8008 | Date and time of production: AI (8008) | N4+N8+[N..4] | (FNC1) | PROD TIME |
| 8009 | Optically readable sensor indicator: AI (8009) | N4+X..50 | (FNC1) | OPTSEN |
| 8010 | Component/Part Identifier (CPID): AI (8010) | N4+Y..30 | (FNC1) | CPID |
| 8011 | Component/Part Identifier serial number: AI (8011) | N4+N..12 | (FNC1) | CPID SERIAL |
| 8012 | Software version: AI (8012) | N4+X..20 | (FNC1) | VERSION |
| 8013 | Global Model Number (GMN): AI (8013) | N4+X..25 | (FNC1) | GMN |
| 8014 | Highly Individualised Device Registration Identifier (HIDRI): AI (8014) | N4+X..25 | (FNC1) | MUDI |
| 8017 | Global Service Relation Number (GSRN) to identify the relationship between an organisation offering services and the provider of services: AI (8017) | N4+N18 | (FNC1) | GSRN - PROVIDER |
| AI | Data Content | Format (1) | FNC1 | Data title |
|---|---|---|---|---|
| required (4) | ||||
| 8018 | Global Service Relation Number (GSRN) to identify the relationship between an organisation offering services and the recipient of services: AI (8018) | N4+N18 | (FNC1) | GSRN - RECIPIENT |
| 8019 | Service Relation Instance Number (SRIN): AI (8019) | N4+N..10 | (FNC1) | SRIN |
| 8020 | Payment slip reference number: AI (8020) | N4+X..25 | (FNC1) | REF No. |
| 8026 | Identification of pieces of a trade item (ITIP) contained in a logistic unit: AI (8026) | N4+N14+N2+N2 | (FNC1) | ITIP CONTENT |
| 8030 | Digital Signature (DigSig): AI (8030) | N4+Z..90 | (FNC1) | DIGSIG |
| 8040 | International Mobile Equipment Identity (IMEI): AI (8040) | N4+N15 | (FNC1) | IMEI |
| 8041 | International Mobile Equipment Identity 2 (IMEI2): AI (8041) | N4+N15 | (FNC1) | IMEI2 |
| 8042 | Embedded SIM: AI (8042) | N4+N32 | (FNC1) | ESIM |
| 8043 | Physical SIM: AI (8043) | N4+N18+[N..2] | (FNC1) | PSIM |
| 8110 | Coupon code identification for use in North America AI (8110) | N4+X..70 | (FNC1) | - |
| 8111 | Loyalty points of a coupon: AI (8111) | N4+N4 | (FNC1) | POINTS |
| 8112 | Positive offer file coupon code identification for use in North America: (AI 8112) | N4+X..70 | (FNC1) | - |
| 8200 | Extended packaging URL: AI (8200) | N4+X..70 | (FNC1) | PRODUCT URL |
| 90 | Information mutually agreed between trading partners: AI (90) | N2+X..30 | (FNC1) | INTERNAL |
| 91 to 99 | Company internal information: AIs (91 - 99) | N2+X..90 | (FNC1) | INTERNAL |
NOTES: (1): The first position indicates the length (number of digits) of the GS1 Application Identifier. The following value refers to the format of the data content. The following convention is applied:
n implied decimal point position N numeric digit X any character in Table 7-20 for GS1 AI encodable character set 82 Y any character in Table 7-21 for GS1 AI encodable character set 39 Z any character in Table 7-22 for (file-safe / URI-safe base64) N2 2 numeric digits, fixed length N3 3 numeric digits, fixed length N4 4 numeric digits, fixed length X3 3 characters, fixed length N..3 up to 3 numeric digits X..3 up to 3 characters in Table 7-20 for GS1 AI encodable character set 82 Y..3 up to 3 characters in Table 7-21 for GS1 AI encodable character set 39 Z..3 up to 3 characters in Table 7-22 for GS1 AI encodable character set 64 (file-safe / URI-safe base64) [ ] enclosed value is an optional component (2): If only year and month are available, DD must be filled with two zeroes, except where noted.
(3): The fourth digit of this GS1 Application Identifier indicates the number of decimal places (and in that way the implied decimal point position). Example: 3100 Net weight in kg without a decimal point 3102 Net weight in kg with two decimal places see section 7.8.7 for further information.
(4): All GS1 element strings that begin with GS1 Application Identifiers not contained in the predefined table shown in Table 7-6 SHALL be separated by a separator character unless this element string is the last one to be encoded in the symbol. For details on the separator character see section 7.8.4. (5) An example to illustrate future additional National Healthcare Reimbursement Numbers (NHRNs). If additional NHRN AIs are required, a request for a new NHRN AI SHALL be made through GSMP.
(6) The fourth digit of this GS1 Application Identifier indicates the sequence number, allowing for multiple occurrences of the AI. (7) The temperatures in these GS1 Application Identifiers are expressed in hundredths of degrees.
3.3 GS1 Application Identifiers starting with digit 0
3.3.1 Identification of a logistic unit (SSCC): AI (00)
The GS1 Application Identifier (00) indicates that the GS1 Application Identifier data field contains an SSCC (Serial Shipping Container Code). The SSCC is used to identify logistic units (see section 2.2).
The extension digit is used to increase the capacity of the serial reference within the SSCC. It is assigned by the company that constructs the SSCC. The extension digit ranges from 0-9.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the SSCC – here the physical builder or the brand owner of the logistic unit (see section 1.2.3.3). It makes the SSCC unique worldwide but does not identify the origin of the unit.
The structure and content of the serial reference is at the discretion of owner of the GS1 Company Prefix to uniquely identify each logistic unit. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 | SSCC (Serial Shipping Container Code) | |||
|---|---|---|---|---|
| Application Identifier | Extension digit | GS1 Company Prefix | Serial reference | Check |
| ──────────────› | ‹──────────────────── | digit | ||
| 0 0 | N1 | N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 | N18 |
The data transmitted from the barcode reader means that the element string denoting the SSCC of a logistic unit has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SSCC
3.3.2 Identification of a trade item (GTIN): AI (01)
The GS1 Application Identifier (01) indicates that the GS1 Application Identifier data field contains a GTIN. The GTIN is used to identify trade items (see section 2.1). The GTIN for trade items may be a GTIN-8, GTIN-12, GTIN-13 or a GTIN-14. See section 2.1 for the rules for GTIN formats and mandatory or optional attributes in the various trade item applications.
The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 | Global Trade Item Number (GTIN) | ||
|---|---|---|---|
| Application Identifier | GS1-8 Prefix or GS1 Company Prefix ───────────────────────────› | Item reference | Check |
| ‹─────────────── | digit | ||
| 0 1 | 0 0 0 0 0 0 N1 N2 N3 N4 N5 N6 N7 | N8 | |
| 0 1 | 0 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 | N12 | |
| 0 1 | 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | |
| 0 1 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 | N14 |
(GTIN-8) (GTIN-12) (GTIN-13) (GTIN-14) The data transmitted from the barcode reader means that the element string denoting the GTIN of a trade item has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GTIN
3.3.3 Identification of trade items contained in a logistic unit: AI (02)
The GS1 Application Identifier (02) indicates that the GS1 Application Identifier data field includes the GTIN of the contained trade items. The GTIN is used to identify trade items (see section 4).
The GTIN for trade items may be a GTIN-8, GTIN-12, GTIN-13 or a GTIN-14. See section 2 for the rules for GTIN formats and mandatory or optional attributes in the various trade item applications.
The GTIN of the trade items contained is the GTIN of the highest level of trade item contained in the logistic unit. Note: This element string SHALL be used only on a logistic unit if:
the logistic unit is not itself a trade item; and
-
all trade items that are contained at the highest level have the same GTIN.
-
The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 | Global Trade Item Number (GTIN) | ||
|---|---|---|---|
| Application Identifier | GS1-8 Prefix or GS1 Company Prefix ───────────────────────────› | Item reference | Check |
| ‹─────────────── | digit | ||
| 0 2 | 0 0 0 0 0 0 N1 N2 N3 N4 N5 N6 N7 | N8 | |
| 0 2 | 0 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 | N12 | |
| 0 2 | 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | |
| 0 2 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 | N14 |
(GTIN-8) (GTIN-12) (GTIN-13) (GTIN-14) The data transmitted from the barcode reader means that the element string denoting the GTIN of trade items contained in a logistic unit has been captured.
This element string must be processed together with the count of trade items, AI (37), which must appear on the same unit (see section 3.6.5). Restrictions apply to the use of AI (02) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CONTENT
3.3.4 Identification of a Made-to-Order (MtO) trade item (GTIN): AI (03)
The GS1 Application Identifier (03) indicates that the GS1 Application Identifier data field contains an Identification of a Made-to-Order (MtO) trade item (GTIN). The Identification of a Made-to-Order (MtO) trade item (GTIN) is used to identify trade items (see section 2.1). This GTIN may be a GTIN- 12, GTIN-13 or a GTIN-14, see section 2.1 for the rules for GTIN formats and mandatory or optional attributes in the various trade item applications.
The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 | Identification of a Made-to-Order (MtO) trade item (GTIN) | ||
|---|---|---|---|
| Application Identifier | GS1 Company Prefix ───────────────────────────› | Item reference | Check |
| ‹─────────────── | digit | ||
| 0 3 | 0 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 | N12 | |
| 0 3 | 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | |
| 0 3 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 | N14 |
(GTIN-12) (GTIN-13) (GTIN-14) NOTE: GTIN-8 (see section 4.2.7) is not an option for Made-to-Order GTIN. The data transmitted from the barcode reader means that the element string denoting the GTIN of a Made-to-Order trade item has been captured.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MTO GTIN
3.4 GS1 Application Identifiers starting with digit 1
3.4.1 Batch or lot number: AI (10)
The GS1 Application Identifier (10) indicates that the GS1 Application Identifier data field contains a batch or lot number. The batch or lot number associates an item with information the manufacturer considers relevant for traceability of the trade item to which the element string is applied. The data may refer to the trade item itself or to items contained. The number may be, for example, a production lot number, a shift number, a machine number, a time, or an internal production code. In cases where the same product is manufactured in different locations the brand owner and the manufacturer are responsible for ensuring the non-duplication of batch/lot numbers for a GTIN. For the re-use of batch/lot numbers with a GTIN, sector-specific constraints need to be considered.
The data is alphanumeric and may include all characters contained in Table 7-20. Note: The batch or lot number is not part of the unique identification of a trade item.
| GS1 Application Identifier | Batch or lot number |
|---|---|
| 1 0 | X1───────────› variable length ───────────›X20 |
The data transmitted by the barcode reader means that the element string denoting a batch or lot number has been captured. As this element string is an attribute of a particular item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13.2). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BATCH/LOT
3.4.2 Production date: AI (11)
The GS1 Application Identifier (11) indicates that the GS1 Application Identifier data field contains a production date. The production date is the production or assembly date determined by the manufacturer. The date may refer to the trade item itself or to items contained. The structure is:
Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: How the day of the month is expressed for regulated healthcare products will change starting 1 January 2025. As of that date the day of the month SHALL NOT be expressed as two zeroes. A valid day of the month (e.g., last day of July = 31) SHALL be included.
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Production date | |||
|---|---|---|---|---|
| Application | Year | Month | Day | Day |
| Identifier | ||||
| 1 1 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a production date has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROD DATE
3.4.3 Due date for amount on payment slip: AI (12)
The GS1 Application Identifier (12) indicates that the GS1 Application Identifier data field contains the date by which an invoice should be paid. This data element represents an attribute of a payment slip reference number, AI (8020), and a Global Location Number (GLN) of the invoicing party. The structure is:
Year: the tens and units of the year (e.g., 1998 = 98), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Due date | ||
|---|---|---|---|
| Application Identifier | Year | Day | |
| 1 2 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a due date has been captured. Restrictions apply to the use of this AI in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: DUE DATE
3.4.4 Packaging date: AI (13)
The GS1 Application Identifier (13) indicates that the GS1 Application Identifier data fields contain a packaging date. The packaging date is the date when the goods were packed as determined by the packager. The date may refer to the trade item itself or to items contained. The structure is:
Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Packaging date | |||
|---|---|---|---|---|
| Application Identifier | Year | Month | Day | Day |
| 1 3 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a packaging date has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PACK DATE
3.4.5 Best before date: AI (15)
The GS1 Application Identifier (15) indicates that the GS1 Application Identifier data fields contain a best before date. Best before date on the label or package signifies the end of the period under which the product will retain specific quality attributes or claims even though the product may continue to retain positive quality attributes after this date. Best before date is primarily used for consumer information and may be a regulatory requirement.
Note: A retailer may use this to determine a date after which they will no longer merchandise the product. Currently, there are implementations of best before date which are interpreted in their processes as the date to sell by.
The structure is: Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the Day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Best before date | |||
|---|---|---|---|---|
| Application Identifier | Year | Month | Day | Day |
| 1 5 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a best before date has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BEST BEFORE or BEST BY
3.4.6 Sell by date: AI (16)
The GS1 Application Identifier (16) indicates the date specified by the manufacturer as the last date the retailer is to offer the product for sale to the consumer. The product should not be merchandised after this date.
Note: This AI is to be used in sectors where the manufacturer has agreed to apply the SELL BY date for the customer’s use. The structure is: Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the Day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Sell by date | |||
|---|---|---|---|---|
| Application Identifier | Year | Month | Day | Day |
| 1 6 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a sell by date has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SELL BY
3.4.7 Expiration date: AI (17)
The GS1 Application Identifier (17) indicates that the GS1 Application Identifier data fields contain an expiration date. The expiration date is the date that determines the limit of consumption or use of a product/coupon. Its meaning is determined based on the trade item context (e.g., for food, the date will indicate the possibility of a direct health risk resulting from use of the product after the date, for pharmaceutical products, it will indicate the possibility of an indirect health risk resulting from the ineffectiveness of the product after the date). It is often referred to as "use by date" or "maximum durability date.” The structure is:
Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); if it is not necessary
-
to specify the day, the field must be filled with two zeroes.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: How the day of the month is expressed for regulated healthcare products will change starting 1 January 2025. As of that date the day of the month SHALL NOT be expressed as two zeroes. A valid day of the month (e.g., last day of July = 31) SHALL be included.
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 | Expiration date | |||
|---|---|---|---|---|
| Application Identifier | Year | Month | Day | Day |
| 1 7 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting an expiration date has been captured. As this element string is an attribute of a trade item or a coupon, it must be processed together with the GTIN or the GCN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: USE BY or EXPIRY
3.5 GS1 Application Identifiers starting with digit 2
3.5.1 Internal product variant: AI (20)
This element string may be used to distinguish an internal product variant from the usual item if the variation is not sufficiently significant to require a separate Global Trade Item Number (GTIN) and the variation is relevant only to the brand owner and any third party acting on its behalf.
The internal product variant is only for use by the brand owner and any third party acting on its behalf and not for dealings with any other trading partners. The product variant SHALL NOT be used where the variation would trigger the allocation of a different GTIN per the GTIN Management Standard.
Although the element string will not have meaning to all trading partners, the element string may remain on the item throughout distribution.
| GS1 Application Identifier | Internal product variant |
|---|---|
| 2 0 | N1 N2 |
The GS1 Application Identifier (20) indicates that the data field contains an internal product variant number. The internal product variant number must only be assigned by the brand owner. It forms a subsidiary numbering facility that can be used in addition to the item’s GTIN and allows the creation of 100 variants of a particular item.
The data transmitted from the barcode reader means that the element string denoting an internal product variant has been captured. The internal product variant must be processed together with the GTIN of the trade item (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: VARIANT
3.5.2 Serial number: AI (21)
The GS1 Application Identifier (21) indicates that the GS1 Application Identifier data field contains a serial number. A serial number is assigned to an entity for its lifetime. When combined with a GTIN, a serial number uniquely identifies an individual item. The serial number field is alphanumeric and may include all characters contained in Table 7-20. The brand owner and the manufacturer are responsible for ensuring the non-duplication of serial numbers for a GTIN. For the re-use of serial numbers with a GTIN, sector-specific constraints need to be considered.
| GS1 Application Identifier | Serial number |
|---|---|
| 2 1 | X1 ───────────── variable length─────────────› X20 |
The data transmitted from the barcode reader means that the element string denoting a serial number has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SERIAL
3.5.3 Consumer product variant: AI (22)
This element string may be used to distinguish one variant of a retail consumer trade item from another if the change does not require the allocation of a different Global Trade Item Number (per the GTIN Management Standard), but communication between trading partners is required to support consumers. The brand owner is responsible for assigning the consumer product variant. The data is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Consumer product variant |
|---|---|
| 2 2 | X1 ───────────── variable length─────────────› X20 |
The GS1 Application Identifier (22) indicates that the data field contains a consumer product variant. Note: The consumer product variant, AI (22), differs from the internal product variant, element string AI (20), which is relevant only to the brand owner and any third party acting on its behalf.
The data transmitted from the barcode reader means that the element string denoting a consumer product variant has been captured. The consumer product variant must be processed together with the GTIN of the trade item (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CPV
3.5.4 Third Party Controlled, Serialised Extension of Global Trade Item Number (GTIN)
(TPX): AI (235) The GS1 Application Identifier (235) indicates that the GS1 Application Identifier data field contains a Third Party Controlled, Serialised Extension of GTIN (TPX). This identifier is assigned to an entity for its lifetime. When combined with a GTIN, a TPX uniquely identifies an individual item and forms a unit pack Unique Identifier (upUI) for tobacco traceability per EU 2018/574. The serial number field is alphanumeric and may include all characters contained in Table 7-20. The Third Party determines the TPX, but the TPX shall begin with the ID Issuer Unique Identification Code (UIC), followed by GS1 UIC Extension 1 and GS1 UIC Extension 2.
The UIC begins with one numeric digit followed by one alphanumeric character from Table 7-20,
- GS1 AI encodable character set 82.
The GS1 UIC Extension 1 is one alphanumeric character from Table 7-20, GS1 AI encodable
- character set 82.
The GS1 UIC Extension 2 is one alphanumeric character from Table 7-20, GS1 AI encodable
- character set 82 For users of the GS1 algorithm, the characters 0-9, A-Z and a-e SHALL be used for GS1 UIC Extension 2. For users of a non-GS1 algorithm, characters f-z and special characters SHALL be used. When encoded in a GS1 barcode the TPX SHALL be encoded before the GTIN.
Note: Use of a Manufacturer’s Serial Number, AI (21), SHALL be the default choice in all trade item application standards, unless otherwise specified within an application standard.
Third Party Controlled, Serialised Extension of GTIN (required by regulation) SHALL NOT be used in conjunction with a Manufacturer’s Serial Number.
| GS1 Application | Third Party Controlled, Serialised Extension of GTIN |
|---|---|
| Identifier | |
| 2 3 5 | X ───────────── variable length─────────────› X 1 28 |
The data transmitted from the barcode reader means that the element string denoting a Third Party Controlled, Serialised Extension of GTIN has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: TPX
3.5.5 Additional product identification assigned by the manufacturer: AI (240)
The GS1 Application Identifier (240) indicates that the GS1 Application Identifier data field contains additional item identification. The purpose of this element string is to enable identification data other than the Global Trade Item Number (GTIN) to be represented in a GS1 system data carrier. It is a cross-reference to previously used catalogue numbers. The additional item identification is considered an attribute of the GTIN (e.g., it facilitates migration to the GS1 system during a transitional period). However, it must not be used to replace the GTIN.
The additional item identification field is alphanumeric and may include all characters contained in Table 7-20. Its content and structure are at the discretion of the company applying the element string.
| GS1 Application Identifier | Additional item identification |
|---|---|
| 2 4 0 | X1─────────────variable length─────────────› X30 |
The data transmitted from the barcode reader means that the element string denoting an additional item identification has been captured. This element string must be processed together with the GTIN of the trade item (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ADDITIONAL ID
3.5.6 Customer part number: AI (241)
The GS1 Application Identifier (241) indicates that the GS1 Application Identifier data field contains a customer part number. The purpose of this element string is to enable identification data other than the Global Trade Item Number (GTIN) to be represented in a GS1 system data carrier. The element string SHOULD only be used between trading partners that are currently using the customer part number for ordering and who have agreed on a timetable to convert to the GTIN for their business purposes. Therefore, the use of the GTIN and the AI (241) on trade items is for transitional use during the conversion. The customer part number must not be used in place of the GTIN. The customer part number field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Customer part number |
|---|---|
| 2 4 1 | X1 ─────────────variable length ─────────────›X30 |
The data transmitted from the barcode reader means that the element string denoting a customer part number has been captured. This element string must be processed together with the GTIN of the trade item (see section 4.13 Data relationships). When indicating this element string in the non- HRI text section of a barcode label, the following data title SHOULD be used: CUST. PART No.
3.5.7 Made-to-Order variation number: AI (242)
The GS1 Application Identifier (242) indicates that the data field contains a Made-to-Order variation number. The data is variable length numeric up to and including six digits. The Made-to-Order variation number provides the additional data needed to uniquely identify a custom trade item (see section 2.6.8).
There is a mandatory association of AI (242) with a GTIN-14, indicator digit 9. This association indicates that the GTIN-14, indicator digit 9 represents a custom trade item when paired with AI (242).
A Made-to-Order variation number may not be used with the following GTINs: GTIN-8, GTIN-12, GTIN-13 and GTIN-14 indicator digit 1 through 8. The use of a GTIN-14, indicator digit 9 and a Made-to-Order variation number is only approved for the manufacturing and maintenance, repair & overhaul (MRO) environment.
| GS1 Application Identifier | Made-to-Order variation number |
|---|---|
| 2 4 2 | N1─────── variable length──────› N6 |
The data transmitted by the barcode reader means that the element string denoting a Made-to- Order variation number has been captured. This element string must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD also be used: MTO VARIANT
3.5.8 Packaging component number: AI (243)
The GS1 Application Identifier (243) indicates the GS1 Application Identifier data field contains a Packaging Component Number (PCN). A PCN is assigned to the packaging component for its lifetime. When associated with a GTIN, a PCN uniquely identifies the relationship between a finished consumer trade item and one of its packaging components.
The current use case for PCN is for internal use only however the PCN may be considered in future use cases for open supply chain applications. The Packaging Component Number field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Packaging Component Number | |
|---|---|---|
| 2 4 3 | X1───────────› variable length─────────────› X20 |
The data transmitted from the barcode reader means that the element string denoting a Packaging Component Number has been captured. As this element string is an attribute of a particular item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13.2).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PCN
3.5.9 Secondary serial number: AI (250)
The GS1 Application Identifier (250) indicates that the GS1 Application Identifier data field contains a secondary serial number. While the element string using AI (21) (see section 3.5.2) contains the serial number of the trade item, the element string denoting a secondary serial number represents the serial number of a component of that item. The company applying the element string determines which component the element string refers to for a given trade item. The recognition of the meaning of the secondary serial number is accomplished via the GTIN and information provided by the issuer regarding the component to which the secondary serial number refers.
If this element string is being used, the trade item must be symbol marked with the following element strings: AI (01): representing the GTIN of the trade item.
-
AI (21): representing the serial number of the trade item.
-
AI (250): representing the serial number of a component of the trade item.
-
Only one element string with AI (250) may be associated with a particular GTIN.
The secondary serial number field is alphanumeric and may include all characters contained in Table 7-20. The number and to what component it relates is determined by the issuer.
| GS1 Application Identifier | Secondary serial number |
|---|---|
| 2 5 0 | X1───────────── variable length─────────────›X30 |
The data transmitted from the barcode reader means that the element string denoting a secondary serial number has been captured. This element string must be processed together with the GTIN and the serial number of the trade item (see section 4.13.2). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SECONDARY SERIAL
3.5.10 Reference to source entity: AI (251)
The GS1 Application Identifier (251) indicates that the GS1 Application Identifier data field consists of a reference to the original item. Reference to source entity is an attribute of a trade item used to refer to the original item from which the trade item was derived. The issuer of the trade item must indicate through other means the source entity to which the data refers.
For example, the original item could be an animal from which a carcass of beef is derived. This element string would enable reference to the original animal, so that, if the animal was found to be contaminated, all derived products could be isolated. In addition, this element string could also be used for regulatory compliance when recycling parts from various white goods, such as refrigerators, where it is necessary to refer to the original appliance. The reference to the source entity field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Reference to source entity |
|---|---|
| 2 5 1 | X1─────────────variable length ─────────────›X30 |
The data transmitted by the barcode reader means that the element string denoting a reference to source entity has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: REF. TO SOURCE
3.5.11 Global Document Type Identifier (GDTI): AI (253)
The GS1 Application Identifier (253) indicates that the GS1 Application Identifier data field contains the Global Document Type Identifier (GDTI). The GDTI is used to identify a document type with an optional serial number.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GDTI – here the document issuer (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the Document Type is at the discretion of the document issuer, in order to uniquely identify each type of document. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
The optional serial component is assigned to a single document for its lifetime. When the serial component is included, the GDTI uniquely identifies an individual document. The serial component field is alpha-numeric and may contain up to 17 characters. It may contain all characters contained in Table 7-20. The issuer of the document determines the serial component.
| GS1 Application Identifier | Global Document Type Identifier (GDTI) | ||
|---|---|---|---|
| GS1 Company Prefix | Document type | Check | Serial component |
| ──────────────› | ‹───────────── | digit | (optional) |
| 2 5 3 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | X1 ──variable ──› X17 |
The data transmitted from the barcode reader means that the element string denoting a GDTI has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GDTI
3.5.12 Global Location Number (GLN) extension component: AI (254)
The GS1 Application Identifier (254) indicates that the data field contains an extension component of a Global Location Number (GLN). The use of AI (254) is optional, but when used it must appear in conjunction with AI (414), identification of a physical location.
The party who defined the location determines the extension component. Once determined, it is unchanged for the life of the associated GLN. The GLN extension component field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | GLN extension component |
|---|---|
| 2 5 4 | X1 ────── variable length ──────› X20 |
The data transmitted from the reader means that the element string denoting an extension component of a GLN has been captured. As this element string is an attribute of a physical location, it must be processed together with the GLN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GLN EXTENSION COMPONENT
3.5.13 Global Coupon Number (GCN): AI (255)
The GS1 Application Identifier (255) indicates that the GS1 Application Identifier data field contains the Global Coupon Number (GCN). The GCN provides a globally unique identification for a coupon, with an optional serial number.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GCN. It makes the number unique worldwide. The structure and content of the coupon reference is at the discretion of the coupon issuer, in order to uniquely identify each type of coupon.
The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed. The optional serial component is assigned to an individual instance of a coupon. The combination of GS1 Company Prefix, coupon reference and serial component uniquely identifies an individual coupon. The serial component field is numeric and may contain up to 12 digits. The issuer of the Global Coupon Number determines the serial component.
| GS1 Application Identifier | Global Coupon Number (GCN) | ||
|---|---|---|---|
| GS1 Company Prefix ─────────────› | Coupon reference | Check | Serial component |
| ‹───────────── | digit | (optional) | |
| 2 5 5 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | N1 ─variable ─› N12 |
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GCN
3.6 GS1 Application Identifiers starting with digit 3
3.6.1 Variable count of items: AI (30)
The GS1 Application Identifier (30) indicates that the GS1 Application Identifier data field contains the number of items contained in a variable measure trade item. This element string is used to complete the identification of a variable measure trade item and, therefore, should never be applied in isolation.
The variable count of items field represents the quantity contained in the respective trade item. It is of variable length and may have up to eight digits. Note: This element string must not be used to indicate the contained quantity of a fixed measure trade item. However, if this element string appears on a fixed measure trade item (in error) it should not invalidate the item identification but should be treated as redundant data.
| GS1 Application Identifier | Variable count of items |
|---|---|
| 3 0 | N1 ──── variable length ────›N8 |
The data transmitted from the barcode reader means that the element string denoting a quantity (variable count of items), which can be considered part of the identification of a variable measure trade item, has been captured. This element string must be processed with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: VAR. COUNT
3.6.2 Trade measures: AIs (31nn, 32nn, 35nn, 36nn)
The GS1 Application Identifiers (digits A1 to A4 – see figure below) indicate that the GS1 Application Identifier data field contains the quantity or dimension of a variable measure trade item. It also denotes the unit of measure. These element strings are used to complete the identification of a variable measure trade item. They contain information such as the weight, size, volume, or dimension of a variable measure trade item and, therefore, should never be applied alone. Several element strings are possible if the variables required are dimensions or weights expressed in kilograms and pounds.
The GS1 Application Identifier digit A4 indicates the implied decimal point position, where, for example, the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is between N5 and N6. The “applicable value” field contains the variable measure that applies to the respective trade item.
| GS1 Application Identifier | Applicable value |
|---|---|
| A1 A2 A3 A4 | N1 N2 N3 N4 N5 N6 |
The GS1 Application Identifiers used with this element string are shown in Table 3-2. Note: Other values of AI (3nnn) specify gross measures and logistic measures.
Table 3-2 GS1 Application Identifiers for trade measures
| A1 | A2 | A3 | A4 | Trade measure | Unit of measure |
|---|---|---|---|---|---|
| 3 | 1 | 0 | n | Net weight | Kilograms |
| A1 | A2 | A3 | A4 | Trade measure | Unit of measure |
|---|---|---|---|---|---|
| 3 | 1 | 1 | n | Length or first dimension | Metres |
| 3 | 1 | 2 | n | Width, diameter, or second dimension | Metres |
| 3 | 1 | 3 | n | Depth, thickness, height, or third dimension | Metres |
| 3 | 1 | 4 | n | Area | Square metres |
| 3 | 1 | 5 | n | Net volume | Litres |
| 3 | 1 | 6 | n | Net volume | Cubic metres |
| 3 | 2 | 0 | n | Net weight | Pounds |
| 3 | 2 | 1 | n | Length or first dimension | Inches |
| 3 | 2 | 2 | n | Length or first dimension | Feet |
| 3 | 2 | 3 | n | Length or first dimension | Yards |
| 3 | 2 | 4 | n | Width, diameter, or second dimension | Inches |
| 3 | 2 | 5 | n | Width, diameter, or second dimension | Feet |
| 3 | 2 | 6 | n | Width, diameter, or second dimension | Yards |
| 3 | 2 | 7 | n | Depth, thickness, height, or third dimension | Inches |
| 3 | 2 | 8 | n | Depth, thickness, height, or third dimension | Feet |
| 3 | 2 | 9 | n | Depth, thickness, height, or third dimension | Yards |
| 3 | 5 | 0 | n | Area | Square inches |
| 3 | 5 | 1 | n | Area | Square feet |
| 3 | 5 | 2 | n | Area | Square yards |
| 3 | 5 | 6 | n | Net weight | Troy ounces |
| 3 | 5 | 7 | n | Net weight (or volume) | Ounces |
| 3 | 6 | 0 | n | Net volume | Quarts (US) |
| 3 | 6 | 1 | n | Net volume | Gallons (US) |
| 3 | 6 | 4 | n | Net volume | Cubic inches |
| 3 | 6 | 5 | n | Net volume | Cubic feet |
| 3 | 6 | 6 | n | Net volume | Cubic yards |
The data transmitted from the barcode reader means that the element string denoting a quantity, which can be considered part of the identification of a variable measure trade item, has been captured. This element string must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the data title listed in section 3.2 SHOULD be used.
3.6.3 Logistic measures: AIs (33nn, 34nn, 35nn, 36nn)
Note: For AI (337) refer to section 3.6.4 The GS1 Application Identifiers (A1 to A4 see figure below) indicate that the GS1 Application Identifier data field contains the logistic quantity or dimension of a logistic unit or a variable measure trade item. They also denote the unit of measure.
Note: The GS1 system provides standards for logistic weights and measures in metric and other units of measure. In principle, a particular logistic measure SHOULD be applied in only one unit of measure on a given logistic unit. However, application of the same attribute in several units of measure does not impede the correct processing of the transmitted data.
The GS1 Application Identifier digit in field A4 indicates the implied decimal point position, where, for example, the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is between N5 and N6. The Applicable Value field represents the measures of the respective unit.
| GS1 Application Identifier | Applicable value |
|---|---|
| A1 A2 A3 A4 | N1 N2 N3 N4 N5 N6 |
The GS1 Application Identifiers used with this element string are shown in Table 3-3.
Table 3-3 GS1 Application Identifiers for logistic measures
| A1 | A2 | A3 | A4 | Definition of logistic measures | Unit of measure |
|---|---|---|---|---|---|
| 3 | 3 | 0 | n | Logistic weight | Kilograms |
| 3 | 3 | 1 | n | Length or first dimension | Metres |
| 3 | 3 | 2 | n | Width, diameter, or second dimension | Metres |
| 3 | 3 | 3 | n | Depth, thickness, height, or third dimension | Metres |
| 3 | 3 | 4 | n | Area | Square metres |
| 3 | 3 | 5 | n | Logistic volume | Litres |
| 3 | 3 | 6 | n | Logistic volume | Cubic metres |
| 3 | 4 | 0 | n | Logistic weight | Pounds |
| 3 | 4 | 1 | n | Length or first dimension | Inches |
| 3 | 4 | 2 | n | Length or first dimension | Feet |
| 3 | 4 | 3 | n | Length or first dimension | Yards |
| 3 | 4 | 4 | n | Width, diameter, or second dimension | Inches |
| 3 | 4 | 5 | n | Width, diameter, or second dimension | Feet |
| 3 | 4 | 6 | n | Width, diameter, or second dimension | Yards |
| 3 | 4 | 7 | n | Depth, thickness, height, or third dimension | Inches |
| 3 | 4 | 8 | n | Depth, thickness, height, or third dimension | Feet |
| 3 | 4 | 9 | n | Depth, thickness, height, or third dimension | Yards |
| 3 | 5 | 3 | n | Area | Square inches |
| 3 | 5 | 4 | n | Area | Square feet |
| 3 | 5 | 5 | n | Area | Square yards |
| 3 | 6 | 2 | n | Logistic volume | Quarts (US) |
| 3 | 6 | 3 | n | Logistic volume | Gallons (US) |
| 3 | 6 | 7 | n | Logistic volume | Cubic inches |
| 3 | 6 | 8 | n | Logistic volume | Cubic feet |
| 3 | 6 | 9 | n | Logistic volume | Cubic yards |
The data transmitted from the barcode reader means that the element string denoting a logistic measure has been captured. This element string must be processed with the SSCC of the logistic unit or the GTIN of the variable measure trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the data title listed in section 3.2 SHOULD be used.
3.6.4 Kilograms per square metre: AI (337n)
The GS1 Application Identifier (337n) indicates that the GS1 Application Identifier data field contains the kilograms per square metre of a particular trade item. The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position, where, for example, the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is between N5 and N6.
The kilograms per square metre field contains the weight per area of the respective trade item. The unit of measure is kilograms.
| GS1 Application Identifier | Kilograms per square metre |
|---|
| 3 3 7 n | N1 N2 N3 N4 N5 N6 |
|---|
The data transmitted from the barcode reader means that the element string denoting kilograms per square metre has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: KG PER m²
3.6.5 Count of trade items or trade item pieces contained in a logistic unit: AI (37)
The GS1 Application Identifier (37) indicates that the GS1 Application Identifier data field contains the number of trade items contained in a logistic unit. This element string is a mandatory completion of AI (02) or AI (8026) described in sections 3.3.3 and 3.9.18.
The count of items field contains the number of trade items or number of trade item pieces contained in the respective logistic unit. This information refers to the identification number of the contained items.
| GS1 Application Identifier | Count of items |
|---|---|
| 3 7 | N1 ───variable length ───› N8 |
The data transmitted from the barcode reader means that the element string denoting a number of trade items contained in a logistic unit has been captured. Restrictions apply to the use of AI (37) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: COUNT
3.6.6 Amount payable or coupon value - Single monetary area: AI (390n)
The GS1 Application Identifier (390n) indicates that the GS1 Application Identifier data field contains the amount payable of a payment slip or the coupon value. The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position, where the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is before the last position of the amount payable. See examples in table below.
The applicable amount payable contains the sum to be paid with the respective payment slip (see section 2.6.6) or the coupon value (see section 2.6.2).
| GS1 Application Identifier | Applicable amount payable or coupon value |
|---|---|
| 3 9 0 n | N1 ───────variable length ───────› N15 |
Note: To aid unambiguous processing of payment slips, AI (391n), described in section 3.6.7, SHOULD be used to indicate the currency in which the amount is expressed.
Table 3-4 shows examples of the decimal point indication.
Table 3-4 Decimal point indication examples
| GS1 Application | Encoded value | |
|---|---|---|
| Identifier | ||
| 3 9 0 2 3 9 0 1 3 9 0 0 | 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 | 1 2 3 4 5 . 6 7 1 2 3 4 5 6 . 7 0 1 2 3 4 5 . 0 0 |
The data string transmitted from the barcode reader means that the element string denoting the amount payable of a payment slip or the coupon value has been captured. Restrictions apply to the use of AI (390n) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: AMOUNT
3.6.7 Amount payable and ISO currency code: AI (391n)
The GS1 Application Identifier (391n) indicates that the GS1 Application Identifier data fields consist of an ISO currency code and an applicable amount payable. The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position in the applicable amount payable field, where the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is before the last position of the amount payable. See examples in the figure below.
The ISO currency code field contains the three-digit currency number of the numerical international standard ISO 4217 and indicates the currency in which the amount payable is expressed. The applicable amount payable contains the sum to be paid with the respective payment slip (see section 2.6.6).
| GS1 Application Identifier | ISO currency code | Applicable amount payable |
|---|---|---|
| 3 9 1 n | N1 N2 N3 | N4─────variable length ─────›N18 |
Table 3-5 shows examples of the decimal point indication.
Table 3-5 Decimal point indication examples
| GS1 Application | ISO currency | Encoded value | Actual value |
|---|---|---|---|
| Identifier | code | ||
| 3 9 1 2 3 9 1 1 3 9 1 0 | 7 1 0* 7 1 0* 9 7 8** | 1 2 3 0 1 2 3 0 1 2 3 | 1 2 . 3 0 1 2 3 . 0 0 1 2 3 . 0 0 |
| * South African Rand ** Euro |
The data string transmitted from the barcode reader means that the element string denoting the amount payable has been captured. Restrictions apply to the use of AI (391n) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: AMOUNT
3.6.8 Amount payable for a variable measure trade item – Single monetary area:
AI (392n) The GS1 Application Identifier (392n) indicates that the GS1 Application Identifier data field contains the amount payable for a variable measure trade item. The amount payable refers to an item identified by the Global Trade Item Number (GTIN) of a variable measure trade item and is expressed in local currency. This AI is an attribute of the GTIN and is always used in conjunction with it.
The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position, where the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is before the last position of the amount payable. See examples in the figure below.
The applicable amount payable field contains the total to be paid for the variable measure trade item.
| GS1 Application Identifier | Applicable amount payable |
|---|---|
| 3 9 2 n | N1────variable length────›N15 |
Table 3-6 Decimal point indication examples
| GS1 Application | Encoded value | Actual value |
|---|---|---|
| Identifier | ||
| 3 9 2 2 3 9 2 1 3 9 2 0 | 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 | 1 2 3 4 5 . 6 7 1 2 3 4 5 6 . 7 0 1 2 3 4 5 . 0 0 |
The data transmitted by the barcode reader means that the element string denoting the amount payable of a variable measure trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRICE
3.6.9 Amount payable for a variable measure trade item and ISO currency code:
AI (393n) The GS1 Application Identifier (393n) indicates that the GS1 Application Identifier data field consists of an ISO currency code and an applicable amount payable. The amount payable refers to an item identified with the Global Trade Item Number (GTIN) of a variable measure trade item and is expressed in the indicated currency. This AI is an attribute of the GTIN and is always expressed in conjunction with it.
The GS1 Application Identifier digit shown as “n” indicates the implied decimal point in the applicable amount payable Field, where the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is before the last position of the amount payable. See examples in the figure below.
The ISO currency code field contains the three-digit currency number of the numerical international standard ISO/IEC 4217 and indicates the currency in which the amount payable is expressed. The applicable amount payable field contains the sum to be paid for the variable measure trade item.
| GS1 Application Identifier | ISO currency code | Applicable amount payable |
|---|---|---|
| 3 9 3 n | N1 N2 N3 | N4 ───variable length───›N18 |
Table 3-7 Decimal point indication examples
| GS1 Application | ISO currency code | Encoded value | Actual value |
|---|---|---|---|
| Identifier | |||
| 3 9 3 2 3 9 3 1 3 9 3 0 | 7 1 0* 7 1 0* 9 7 8** | 1 2 3 0 1 2 3 0 1 2 3 | 1 2 . 3 0 1 2 3 . 0 0 1 2 3 . 0 0 |
| * South African Rand ** Euro |
The data transmitted by the barcode reader means that the element string denoting the amount payable of a variable measure trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRICE
3.6.10 Percentage discount of a coupon: AI (394n)
The GS1 Application Identifier (394n) indicates that the GS1 Application Identifier data field contains the percentage discount of a coupon. The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position, where the digit 0 means that there is no decimal point, and the digit 1 means that the decimal point is before the last position of the amount payable. See examples in figure below.
| GS1 Application Identifier | Percentage discount of a coupon |
|---|---|
| 3 9 4 n | N1 N2 N3 N4 |
The data string transmitted from the barcode reader means that the element string denoting the percentage to be taken off the purchase amount has been captured. The purchase amount on which the percentage discount would be granted depends on the conditions of the promotion (can be the purchase value of one item, can be the purchase value of a bundle of items or can even be on the total purchase value).
Table 3-8 shows examples of the decimal point indication.
Table 3-8 Decimal point indication examples
| GS1 Application | Encoded value | Encoded value | Actual value |
|---|---|---|---|
| Identifier | |||
| 3 9 4 0 3 9 4 1 | 0 0 1 0 0 0 5 5 | 10 % 5.5 % |
This element string must be processed together with the Global Coupon Number of the coupon to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRCNT OFF
3.6.11 Amount payable per unit of measure single monetary area (variable measure
trade item): AI (395n) The GS1 Application Identifier (395n) indicates that the GS1 Application Identifier field contains the amount payable per unit of measure single monetary area (variable measure trade item).
The amount payable per unit of measure refers to an item identified by the Global Trade Item Number (GTIN) of a variable measure trade item and is expressed in local currency. This AI is an attribute of the GTIN and is always used in conjunction with it.
The GS1 Application Identifier digit shown as “n” indicates the implied decimal point position, where the digit 0 means that there is no decimal point and the digit 1 means that the decimal point is before the last position of the amount payable per unit of measure (single monetary area). See examples in figure below.
The Amount payable per unit of measure single monetary area field contains the price per unit of measure to be paid for the variable measure trade item.
| GS1 Application Identifier | Amount payable per unit of measure single monetary area (variable measure trade item) |
|---|---|
| 3 9 5 n | N1 N2 N3 N4 N5 N6 |
Table 3-9 shows examples of the decimal point indication.
Table 3-9 Decimal point indication examples
| GS1 Application | Encoded value | Actual value |
|---|---|---|
| Identifier | ||
| 3953 3952 3951 3950 | 123456 123456 123456 123456 | 123.456 1234.56 12345.60 123456 |
The data transmitted from the barcode reader means that the element string denoting the amount payable per unit of measure (single monetary area) has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (395n) in combination with other AIs, (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRICE/UoM
3.7 GS1 Application Identifiers starting with digit 4
3.7.1 Customer’s purchase order number: AI (400)
The GS1 Application Identifier (400) indicates that the GS1 Application Identifier data field contains the customer's purchase order number, restricted for use between two trading partners.
The customer's purchase order number field is alphanumeric and may include all characters contained in Table 7-20. It contains the number of the purchase order assigned by the company that issued the order. The composition and content of the order number is left to the discretion of the customer. For example, the purchase order number may include release and line numbers.
| GS1 Application Identifier | Customer's purchase order number |
|---|---|
| 4 0 0 | X1 ──────variable length──────›X30 |
The data transmitted by the barcode reader means that the element string denoting a customer's purchase order number has been captured. This element string may be processed as stand-alone information or in combination with the GS1 identification key to which it relates.
Important: This element string must be removed from the unit before the unit leaves the premises of the customer. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ORDER NUMBER
3.7.2 Global Identification Number for Consignment (GINC): AI (401)
The GS1 Application Identifier (401) indicates that the GS1 Application Identifier data field contains a Global Identification Number for Consignment (GINC). This number identifies a logical grouping of goods (one or more physical entities) that has been consigned to a freight forwarder and is intended to be transported as a whole. The consignment number must be allocated by a freight forwarder (or a carrier acting as a freight forwarder) or a consignor, but only if prior agreement of the freight forwarder is given. Typically AI (401) encodes a house waybill number.
According to the GS1 Logistics Interoperability Model (LIM) 2 a freight forwarder is a party that arranges the carriage of goods, including connected services and/or associated formalities, on behalf of a shipper or consignee. A carrier is a party that undertakes the transportation of goods from one point to another. A consignor is the party that sends the goods. A consignee is the party that receives the goods.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GINC – here the carrier (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the consignment reference is at the discretion of the carrier, in order to uniquely identify each consignment. It may contain all characters contained in Table 7-20.
| GS1 | Global Identification Number for Consignment (GINC) | |
|---|---|---|
| Application | GS1 Company Prefix ───────────────› | Consignment reference |
| Identifier | ──────────────────────────────› | |
| 4 0 1 | N1 ... Ni Xi+1 ... variable length Xj (j<=30) |
The data transmitted by the barcode reader means the element string denoting a GINC has been captured. This element string may be processed as stand-alone information or in combination with the SSCC.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GINC 2 https://www.gs1.org/lim
3.7.3 Global Shipment Identification Number (GSIN): AI (402)
The GS1 Application Identifier (402) indicates that the data field contains a Global Shipment Identification Number (GSIN). The Global Shipment Identification Number (GSIN) is a number assigned by a consignor (seller) of goods. It provides a globally unique number that identifies a logical grouping of logistic units for the purpose of a transport shipment from that consignor (seller) to the consignee (buyer). It identifies the logical grouping of one or several logistic units each identified with a separate SSCC and containing trade items as being part of a specific seller/buyer relationship and that travels under one despatch advice and/or Bill of Lading. It may be used by all parties in the transport chain as a communication reference, for example, in Electronic Data Interchange (EDI) messages where it can be used as a shipment reference and/or a consignor’s loading list. The GSIN fulfils the requirements of the UCR (Unique Consignment Reference) of the World Customs Organisation (WCO).
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GSIN – here the shipper (sender) (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the shipper reference is at the discretion of the shipper, in order to uniquely identify each shipment. It SHOULD be sequentially allocated. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | Global Shipment Identification Number (GSIN) | |
|---|---|---|
| GS1 Company Prefix ─────────────────› | Shipper reference | Check |
| ‹───────────────────── | digit | |
| 4 0 2 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 | N17 |
The data transmitted by the barcode reader means that the element string denoting a GSIN has been captured. This element string may be processed as stand-alone information or in combination with the SSCC. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GSIN
3.7.4 Routing code: AI (403)
The GS1 Application Identifier (403) indicates that the GS1 Application Identifier data field contains a routing code. The routing code is assigned by the parcel carrier and is an attribute of the SSCC (Serial Shipping Container Code). It is intended to provide a migration path to the adoption of a yet- to-be-defined international, multi-modal solution. The routing code must not be used to encode information for which other element strings have been created (such as a ship to postal code).
The routing code field is alphanumeric and may include all characters contained in Table 7-20. Its content and structure are at the discretion of the parcel carrier issuing the code. If parcel carriers wish to enter co-operative agreements with other parcel carriers, then a mutually agreed indicator is required to designate the structure of the routing code.
| GS1 Application Identifier | Routing code |
|---|---|
| 4 0 3 | X1 ────────variable length───────›X30 |
The data transmitted from the barcode reader means that the element string denoting a routing code has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ROUTE Note: This field may be used to encode the UPU S10 freight unit identifier within a GS1 symbol.
3.7.5 Ship to - Deliver to Global Location Number (GLN): AI (410)
The GS1 Application Identifier (410) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the consignee. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the addressee (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 0 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of the consignee of a physical item has been captured. This element string may be processed as stand- alone information or in combination with the GS1 identification key to which it relates. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO LOC
3.7.6 Bill to - Invoice to Global Location Number (GLN): AI (411)
The GS1 Application Identifier (411) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the addressee of an invoice. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the addressee (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 1 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of the addressee of an invoice has been captured. This element string may be processed as stand- alone information or in combination with the GS1 identification key to which it relates. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BILL TO
3.7.7 Purchased from Global Location Number (GLN): AI (412)
The GS1 Application Identifier (412) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the company from which the respective trade item has been purchased.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the supplier (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 2 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of the company that supplied the trade item has been captured. This element string may be processed as stand-alone information or in combination with the GS1 identification key to which it relates.
When indicating this element string in the non-HRI text section of a barcode label the following data title SHOULD be used: PURCHASE FROM
3.7.8 Ship for - Deliver for - Forward to Global Location Number (GLN): AI (413)
The GS1 Application Identifier (413) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the internal or subsequent final destination.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the final recipient (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
Note: This element string is for the internal use of the consignee and is not to be used by the carrier.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 3 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of the final recipient of a physical item has been captured. This element string may be processed as stand-alone information or in combination with the GS1 identification key to which it relates. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP FOR LOC
3.7.9 Identification of a physical location - Global Location Number (GLN): AI (414)
The GS1 Application Identifier (414) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of a physical location (see section 2.4). The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the holder of the physical location (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 4 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of a physical location has been captured from the location itself. This element string may be processed as stand-alone information or in combination with the GS1 identification key to which it relates.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: LOC No.
3.7.10 Global Location Number (GLN) of the invoicing party: AI (415)
The GS1 Application Identifier (415) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the invoicing party. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN – here the invoicing party (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the location reference is at the discretion of the party who defined the location, in order to uniquely identify each location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
Note: This element string is mandatory on a payment slip. Together with the payment slip reference number, AI (8020), it uniquely identifies a payment slip.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 5 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of the invoicing party has been captured. This element string must be processed together with the payment slip reference number to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PAY TO
3.7.11 Global Location Number (GLN) of the production or service location: AI (416)
The Application Identifier (416) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of the production or service location. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GLN (see section 1.2.3.3).
The structure and content of the location reference is at the discretion of the party that defined the location. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Location reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 6 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting the GLN of production or service location has been captured. This element string may be processed as stand- alone information or in combination with the GS1 identification key to which it relates. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROD/SERV LOC
3.7.12 Party Global Location Number (GLN): AI (417)
The GS1 Application Identifier (417) indicates that the GS1 Application Identifier data field contains the Global Location Number (GLN) of a party. The GS1 Company Prefix (GCP) is allocated by GS1 Member Organisations to the company that allocates the GLN. The GCP makes the number unique worldwide. The structure and content of the party reference is at the discretion of the party in order to uniquely identify themselves.
The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
| GS1 Application Identifier | GS1 Company Prefix ───────────────› | Party reference | Check |
|---|---|---|---|
| ‹─────────────── | digit | ||
| 4 1 7 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 |
The data transmitted from the barcode reader means that the element string denoting a Party GLN has been captured. When indicating this element string in the non-HRI text section of a barcode label, this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PARTY
3.7.13 Ship-to / Deliver-to postal code within a single postal authority: AI (420)
The GS1 Application Identifier (420) indicates that the GS1 Application Identifier data field contains the postal code of the addressee (national format). The postal code field contains the postal code of the addressee as defined by the appropriate postal authority. It is left justified and must not contain any fill characters.
| GS1 Application Identifier | Postal code |
|---|---|
| 4 2 0 | X1─────variable length─────›X20 |
The data transmitted from the barcode reader means that the element string denoting the national version of a postal code of the addressee of the transport unit has been captured. This element may be processed as stand-alone information or in combination with the GS1 identification key to which it relates. Restrictions apply to the use of AI (420) in combination with other AIs, see section 4.13 Data relationships. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO POST
3.7.14 Ship-to / Deliver-to postal code with three-digit ISO country code: AI (421)
The GS1 Application Identifier (421) indicates that the GS1 Application Identifier data field contains the postal code of the addressee (international format). The ISO country code field contains the three-digit country number of the numerical international standard ISO 3166.
The national postal code field, which follows the three-digit ISO country code, contains the postal code of the addressee as defined by the appropriate postal authority. It is left justified and must not contain any fill characters.
| GS1 Application Identifier | ISO country code | Postal code |
|---|---|---|
| 4 2 1 | N1 N2 N3 | X4──variable length──›X12 |
The data transmitted from the barcode reader means that the element string denoting the international version of a postal code of the addressee of the transport unit has been captured. This element string may be processed as stand-alone information or in combination with the GS1 identification key to which it relates. Restrictions apply to the use of AI (421) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO POST
3.7.15 Country of origin of a trade item: AI (422)
The GS1 Application Identifier (422) indicates that the GS1 Application Identifier data field contains the ISO country code of the country of origin of the trade item. The ISO country code field contains the three-digit country number of the numerical international standard ISO 3166 that is the country of origin.
Note: The country of origin is normally the country in which the trade item has been produced or manufactured. In meat supply chain applications AI (422) is used to indicate the country of birth of the animal. Due to a wide range of definitions for country of origin, which were created for different purposes, it is the manufacturer's responsibility to assign the correct country of origin.
| GS1 Application Identifier | ISO country code |
|---|---|
| 4 2 2 | N1 N2 N3 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code of the country of origin of the respective trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (422) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ORIGIN
3.7.16 Country of initial processing: AI (423)
The GS1 Application Identifier (423) indicates that the GS1 Application Identifier data field contains the ISO country code(s) of the country or countries of initial processing of the trade item.
The ISO country code field contains the three-digit country code(s) from the numerical international standard ISO 3166 that indicates the country or countries of initial processing.
Note: The country of initial processing is normally the country in which the trade item has been produced or manufactured. In meat supply chain applications AI (423) is used to indicate the country/countries of rearing and fattening of the animal. In certain applications, such as livestock fattening, the country of initial processing may include up to five different countries, all of which should be indicated. It is the responsibility of the supplier to allocate the correct country code(s).
| GS1 Application Identifier | |
|---|---|
| ISO country code(s) | |
| 4 2 3 | N1 N2 N3 .... N15 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code(s) of the country or countries of initial processing of the respective trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (423) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: COUNTRY – INITIAL PROCESS
3.7.17 Country of processing: AI (424)
The GS1 Application Identifier (424) indicates that the GS1 Application Identifier data field contains the ISO country code of the country of processing of the trade item. The ISO country code field contains the three-digit country code of the numerical international standard ISO 3166 that is the country of processing.
Note: It is the responsibility of the processor of the trade item to allocate the correct country code. In meat or fish supply chain applications AI (424) is used to indicate the country of slaughtering or processing.
| GS1 Application Identifier | ISO country code |
|---|---|
| 4 2 4 | N1 N2 N3 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code of the country of processing of the respective trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (424) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: COUNTRY – PROCESS
3.7.18 Country of disassembly: AI (425)
The GS1 Application Identifier (425) indicates that the GS1 Application Identifier data field contains the ISO country code of the country or countries of disassembly of the trade item. The ISO country code field contains the three-digit country code(s) from the numerical international standard ISO 3166 that indicates the country or countries of disassembly.
Note: In meat supply chain applications AI (425) is used to indicate the country of deboning. In certain applications, such as meat or fish process chains, the process of disassembly is a multi-stage process and the country of disassembly may include several different countries, all of which should be indicated. It is the responsibility of the party doing the disassembly of the trade item to allocate the correct country code(s).
| GS1 Application Identifier | ISO country code |
|---|---|
| 4 2 5 | N1 N2 N3 ...N15 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code(s) of the country or countries of disassembly of the respective trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (425) in combination with other AIs, see section 4.13 Data relationships. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: COUNTRY – DISASSEMBLY
3.7.19 Country covering full process chain: AI (426)
The GS1 Application Identifier (426) indicates that the GS1 Application Identifier data field contains the ISO country code of the country where all the processing of the trade item took place. The ISO country code field contains the three-digit country code of the numerical international standard ISO 3166 that is the country of full processing.
Note: If this AI is used, the full processing of a trade item must have taken place in a single country. This is particularly important in certain applications (e.g., covering a livestock animal’s birth, fattening and slaughter) where processing could take place in different countries. In situations like this, AI (426) may not be used. It is the responsibility of the supplier to allocate the correct country code.
| GS1 Application Identifier | ISO country code |
|---|---|
| 4 2 6 | N1 N2 N3 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code of the country of full processing of the trade item has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates. Restrictions apply to the use of AI (426) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: COUNTRY – FULL PROCESS
3.7.20 Country subdivision of origin code for a trade item: AI (427)
The GS1 Application Identifier (427) indicates that the GS1 Application Identifier data field contains the ISO based country subdivision code (e.g., provinces, states, cantons, etc.) of a country’s local region origin of the trade item. The ISO country subdivision code field contains up to three alphanumeric characters after separator of ISO 3166-2 that is the principal subdivision of origin.
Note: This GS1 AI is applicable to trade item groupings where the contents originate from only one region. Note: The local region of origin is the principal subdivision in which the trade item has been produced or manufactured. Determination of the principle subdivision is the brand owner’s responsibility.
| GS1 Application Identifier | ISO subdivision code |
|---|---|
| 4 2 7 | X1────variable length───› X3 |
The data transmitted from the barcode reader means that the element string denoting the ISO based country subdivision code of the trade item has been captured. This element string must be processed together with the GTIN of the trade item and the country of origin to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ORIGIN SUBDIVISION
3.7.21 Ship-to / Deliver-to Company name: AI (4300)
The GS1 Application Identifier (4300) indicates that the GS1 Application Identifier data field contains the name of a company. The company name is the name of the organisation intended to receive the logistic unit.
| GS1 Application Identifier | Ship-to / Deliver-to Company |
|---|---|
| 4 3 0 0 | X1───────────› variable length ───────────›X35 |
The data transmitted from the barcode reader means that the element string denoting the ship-to / deliver-to company name has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO COMP
3.7.22 Ship-to / Deliver-to contact name: AI (4301)
The GS1 Application Identifier (4301) indicates that the GS1 Application Identifier data field contains contact name for the ship-to address. This contact name is the name of the individual intended to receive the logistic unit.
| GS1 Application Identifier | Ship-to / Deliver-to Contact |
|---|---|
| 4 3 0 1 | X1───────────› variable length ───────────›X35 |
The data transmitted from the barcode reader means that the element string denoting the ship-to / deliver-to contact of a logistic unit has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO NAME
3.7.23 Ship-to / Deliver-to address line 1: AI (4302)
The GS1 Application Identifier (4302) indicates that the GS1 Application Identifier data field contains line one of the ship-to / deliver-to street address line 1 (e.g., street).
| GS1 Application Identifier | Ship-to / Deliver-to address line 1 |
|---|---|
| 4 3 0 2 | X1───────────›variable length───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting ship-to / deliver-to address line 1 has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships). As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO ADD1
3.7.24 Ship-to / Deliver-to address line 2: AI (4303)
The GS1 Application Identifier (4303) indicates that the GS1 Application Identifier data field contains line two of the ship-to / deliver-to street address.
| GS1 Application Identifier | Ship-to / Deliver-to address line 2 |
|---|---|
| 4 3 0 3 | X1───────────›variable length───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting line two of the ship-to / deliver-to address has been captured. This element string must be processed to together with the Ship-to / Deliver-to address line 1, (see section 4.13 Data relationships).
Restrictions apply to the use of AI (4303) in combination with other AIs, see section 4.13 Data relationships. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO ADD2
3.7.25 Ship-to / Deliver-to suburb: AI (4304)
The GS1 Application Identifier (4304) indicates that the GS1 Application Identifier data field contains suburb information for the ship-to / deliver-to address.
| GS1 Application Identifier | Ship-to / Deliver-to suburb |
|---|---|
| 4 3 0 4 | X1───────────›variable length ───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting the suburb for the ship to address has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO SUB
3.7.26 Ship-to / Deliver-to locality: AI (4305)
The GS1 Application Identifier (4305) indicates that the GS1 Application Identifier data field contains locality information for the ship-to / deliver-to address. Locality typically means a town or city.
| GS1 Application Identifier | Ship-to / Deliver-to locality |
|---|---|
| 4 3 0 5 | X1───────────›variable length───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting the locality for the ship to / deliver-to address has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO LOC
3.7.27 Ship-to / Deliver-to region: AI (4306)
The GS1 Application Identifier (4306) indicates that the GS1 Application Identifier data field contains the region information for the ship-to / deliver-to address. Region typically means a first-tier federal state within a country, such as a state in the USA or Australia or a county within the UK.
| GS1 Application Identifier | Ship-to / Deliver-to region |
|---|---|
| 4 3 0 6 | X1───────────›variable length───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting region or the ship to / deliver-to address has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO REG
3.7.28 Ship-to / Deliver-to country code: AI (4307)
The GS1 Application Identifier (4307) indicates that the GS1 Application Identifier data field contains the country code for the ship-to / deliver-to address. Alpha-2 codes from ISO 3166 Country Codes SHALL be used, e.g., FR for France, DE for Germany.
| GS1 Application Identifier | Ship-to / Deliver-to country code |
|---|---|
| 4 3 0 7 | X1 X2 |
The data transmitted from the barcode reader means that the element string denoting the country code for ship-to / deliver-to country code has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO COUNTRY
3.7.29 Ship-to / Deliver-to telephone number: AI (4308)
The GS1 Application Identifier (4308) indicates that the GS1 Application Identifier data field contains the phone number associated with the ship-to / deliver-to address.
| GS1 Application Identifier | Ship-to / Deliver-to telephone number |
|---|---|
| 4 3 0 8 | X1───────────›variable length───────────›X30 |
The data transmitted from the barcode reader means that the element string denoting the ship-to / deliver-to telephone number has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
This AI permits up to 30 alphanumeric characters from the GS1 AI encodable character set 82,
Table 7-20. It is recommended to specify a full International Direct Dial (IDD) phone number including country code, area code and subscriber number (and any extension if required). Note that a space character is not included in Table 7-20, so hyphen character may be used in place of space.
ITU standard E.164 format is an all-numeric format for IDD and assumes that the country code are the first digits; it contains no International Dialling Prefix. For example, the IDD format of GS1 Global Office telephone number is +32-2-788-78-00. The E.164 format for the same example is 3227887800. Either format (IDD or E.164) (e.g., +32-2-788-78-00 or 3227887800) is acceptable for the value of this Application Identifier.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO PHONE
3.7.30 Ship-to / Deliver-to GEO location: AI (4309)
The Application Identifier (4309) indicates that the GS1 Application Identifier data field contains a numeric string that can be converted to geocoordinates for the ship-to/deliver-to location.
The geocoordinate conversion algorithms are explained in section 7.13 and 7.14. The conversions, which must be carried out in the application software, can provide a latitude and longitude from a twenty-digit string associated with the ship-to/deliver-to location, see section 7.14. The process for converting a latitude and longitude into a twenty-digit string is shown in section 7.13.
| GS1 Application | Ship-to / Deliver-to GEO location | |
|---|---|---|
| Identifier | <- digits for latitude conversion-> | < -- digits for longitude conversion--> |
| 4 3 0 9 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 N18 N19 N20 |
The data transmitted from the barcode reader means that the element string associated with the ship-to/deliver-to GEO location has been captured. As this element string is an attribute of a logistic unit, it must be processed together with the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SHIP TO GEO
3.7.31 Return-to company name: AI (4310)
The GS1 Application Identifier (4310) indicates that the GS1 Application Identifier data field contains the return-to name of the company associated with the return-to address.
| GS1 Application Identifier | Return-to company name |
|---|---|
| 4 3 1 0 | X1───────────› variable length ───────────›X35 |
The data transmitted from the barcode reader means that the element string denoting the return-to company name has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO COMP
3.7.32 Return-to contact name: AI (4311)
The GS1 Application Identifier (4311) indicates that the GS1 Application Identifier data field contains the contact name for the return-to address. This contact name is the individual intended to receive the logistic unit for returned units.
| GS1 Application Identifier | Return-to contact |
|---|---|
| 4 3 1 1 | X1───────────› variable length ───────────›X35 |
The data transmitted from the barcode reader means that the element string denoting the Return to contact of a logistic unit has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO NAME
3.7.33 Return-to address line 1: AI (4312)
The GS1 Application Identifier (4312) indicates that the GS1 Application Identifier data field contains street address line 1 information for line one of a return to street address for the return-to address (e.g., street).
| GS1 Application Identifier | Return-to address line 1 |
|---|---|
| 4 3 1 2 | X1───────────›variable length ───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting return to address line 1 has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO ADD1
3.7.34 Return-to address line 2: AI (4313)
The GS1 Application Identifier (4313) indicates that the GS1 Application Identifier data field contains street address information for line two of a return-to street address.
| GS1 Application Identifier | Return-to address line 2 |
|---|---|
| 4 3 1 3 | X1───────────›variable length───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting return-to address line two has been captured. Restrictions apply to the use of AI (4313) in combination with other AIs. (see section 4.13 Data relationships). As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO ADD2
3.7.35 Return-to suburb: AI (4314)
The GS1 Application Identifier (4314) indicates that the GS1 Application Identifier data field contains suburb information for the return-to address.
| GS1 Application Identifier | Return-to suburb |
|---|---|
| 4 3 1 4 | X1 ──────────› variable length──────────› X70 |
The data transmitted from the barcode reader means that the element string denoting the suburb for the return-to address has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO SUB
3.7.36 Return-to locality: AI (4315)
The GS1 Application Identifier (4315) indicates that the GS1 Application Identifier data field contains locality information for the return-to address. A locality is typically a town or city.
| GS1 Application Identifier | Return to locality |
|---|---|
| 4 3 1 5 | X1 ──────────› variable length ──────────› X70 |
The data transmitted from the barcode reader means that the element string denoting the locality for the return to address has been captured. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO LOC
3.7.37 Return-to region: AI (4316)
The GS1 Application Identifier (4316) indicates that the GS1 Application Identifier data field contains the region information for the return-to address. Region typically means a first-tier federal state within a country, such as a state in the USA or Australia or a county within the UK.
| GS1 Application Identifier | Return to region |
|---|---|
| 4 3 1 6 | X1──────────› variable length ──────────›X70 |
The data transmitted from the barcode reader means that the element string denoting the region for the return-to address has been captured. As a free text field for transport process information, non- Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO REG
3.7.38 Return-to country code: AI (4317)
The GS1 Application Identifier (4317) indicates that the GS1 Application Identifier data field contains the country code for the return-to address. Alpha-2 codes from ISO 3166 Country Codes SHALL be used, e.g., AT for Austria, AU for Australia.
| GS1 Application Identifier | Return-to country code |
|---|---|
| 4 3 1 7 | X1 X2 |
The data transmitted from the barcode reader means that the element string denoting the country code for the return-to address has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO COUNTRY
3.7.39 Return-to postal code: AI (4318)
The GS1 Application Identifier (4318) indicates that the GS1 Application Identifier data field contains the postal code associated with the return-to address.
| GS1 Application Identifier | Return-to postal code |
|---|---|
| 4 3 1 8 | X1──────────› variable length ──────────›X20 |
The data transmitted from the barcode reader means that the element string denoting the postal code for the return-to address has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO POST
3.7.40 Return-to telephone number: AI (4319)
The GS1 Application Identifier (4319) indicates that the GS1 Application Identifier data field contains the phone number associated with the return-to address.
| GS1 Application Identifier | Return-to phone number |
|---|---|
| 4 3 1 9 | X1───────────› variable length ───────────›X30 |
The data transmitted from the barcode reader means that the element string denoting the phone number for the return-to address has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships).
This AI permits up to 30 alphanumeric characters from the GS1 AI encodable character set 82,
Table 7-20. It is recommended to specify a full International Direct Dial (IDD) phone number including country code, area code and subscriber number (and any extension if required). Note that a space character is not included in Table 7-20, so hyphen character may be used in place of space.
ITU standard E.164 format is an all-numeric format for IDD and assumes that the country code are the first digits; it contains no International Dialling Prefix. For example, the IDD format of GS1 Global Office telephone number is +32-2-788-78-00. The E.164 format for the same example is 3227887800. Either format (IDD or E.164) (e.g., +32-2-788-78-00 or 3227887800) is acceptable for the value of this Application Identifier.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: RTN TO PHONE
3.7.41 Service code description: AI (4320)
The GS1 Application Identifier (4320) indicates that the GS1 Application Identifier data field contains a description of the type of service or handling appropriate for the logistic unit.
| GS1 Application Identifier | Service code description |
|---|---|
| 4 3 2 0 | X1───────────› variable length ───────────›X35 |
The data transmitted from the barcode reader means that the element string denoting the type of service or handling appropriate for the logistic unit has been captured. The description may be a text field determined by the shipping company using this AI. As a free text field for transport process information, non-Latin characters and a space character may be encoded, see section 2.6.15. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SRV DESCRIPTION
3.7.42 Dangerous goods flag: AI (4321)
The GS1 Application Identifier (4321) indicates that the GS1 Application Identifier data field contains an indication that the logistic unit does or does not include dangerous goods.
| GS1 Application Identifier | Dangerous goods flag | Defined values |
|---|---|---|
| 4 3 2 1 | N1 | 0 (indicates not a dangerous good) 1 (indicates a dangerous good) |
The data transmitted from the barcode reader means that the element string denoting dangerous goods flag has been captured. To indicate the item is not a dangerous good a zero will be encoded in the data, to indicate the item contains a dangerous good a one will be encoded in the data. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used:
DANGEROUS GOODS
3.7.43 Authority to leave flag: AI (4322)
The GS1 Application Identifier (4322) indicates that the GS1 Application Identifier data field indicates whether an item can be left with the recipient without requiring a signature or other confirmation.
| GS1 Application Identifier | Authority to leave flag | Defined values |
|---|---|---|
| 4 3 2 2 | N1 | 0 (meaning no) 1 (meaning yes) |
The data transmitted from the barcode reader means that the element string denoting authority to leave flag has been captured. To indicate no (not authorised to leave) a zero will be encoded in the data, when indicating yes (authorised to leave) a one will be encoded in the data. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: AUTH LEAVE
3.7.44 Signature required flag: AI (4323)
The GS1 Application Identifier (4323) indicates that the GS1 Application Identifier data field indicates whether a signature is required when delivering a logistic unit.
| GS1 Application Identifier | Signature required flag | Defined values |
|---|---|---|
| 4 3 2 3 | N1 | 0 (meaning no) 1 (meaning yes) |
The data transmitted from the barcode reader means that the element string denoting signature required has been captured. To indicate no (no signature required) a zero will be encoded in the data, when indicating yes (signature is required) a one will be encoded in the data. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SIG REQUIRED
3.7.45 Not before delivery date/time: AI (4324)
The GS1 Application Identifier (4324) indicates that the data fields contain not before delivery date and time. This date indicates that the logistic unit cannot be delivered before the indicated date and local time to the receiver.
| GS1 Application Identifier | Not before delivery date/time | |||||
|---|---|---|---|---|---|---|
| YY | MM | DD | HH | HH | MM | |
| 4 3 2 4 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 |
The structure is: Year: the tens and units of the year (e.g., 2007 = 07), which is mandatory
-
Month: the number of the month (e.g., January = 01), which is mandatory
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory
-
Hour and Minutes: the number of the hour and minutes based on a local 24-hour time (e.g.,
-
2:30 p.m. = 1430). If it is not necessary to specify a time, these fields must be filled with nines.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12. The data transmitted from the barcode reader means that the element string denoting a not before delivery data/time has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: NBEF DEL DT
3.7.46 Not after delivery date/time: AI (4325)
The GS1 Application Identifier (4325) indicates that the data fields contain not after delivery date and time. This date indicates that the logistic unit cannot be delivered after the indicated date and local time to the receiver.
| GS1 Application Identifier | Not after delivery date/time | |||||
|---|---|---|---|---|---|---|
| YY | MM | DD | HH | MM | MM | |
| 4 3 2 5 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 |
The structure is: Year: the tens and units of the year (e.g., 2007 = 07), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory
-
Hour and Minutes: the number of the hour and minutes based on a local 24-hour time (e.g.,
-
6:30 p.m. = 1830). If it is not necessary to specify a time, these fields must be filled with nines.
Note: When it is not necessary to specify the day (the day field is filled with two zeroes), the resultant data string SHALL be interpreted as the last day of the noted month including any adjustment for leap years (e.g., “130200” is “2013 February 28”, “160200” is “2016 February 29”, etc.).
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12. The data transmitted from the barcode reader means that the element string denoting a not after delivery data/time has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: NAFT DEL DT
3.7.47 Release date: AI (4326)
The GS1 Application Identifier (4326) indicates that the data fields contain the release for the logistic unit. This date indicates that the logistic unit can be released for delivery after the indicated date.
| GS1 Application Identifier | Release date | ||
|---|---|---|---|
| YY | MM | DD | |
| 4 3 2 6 | N1 N2 | N3 N4 | N5 N6 |
The structure is: Year: the tens and units of the year (e.g., 2007 = 07), which is mandatory
-
Month: the number of the month (e.g., January = 01), which is mandatory
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory
-
The data transmitted from the barcode reader means that the element string denoting a release date has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: REL DATE
3.7.48 Maximum temperature in Fahrenheit: AI (4330)
The GS1 Application Identifier (4330) indicates that the data field contains the maximum temperature, measured in hundredths of degrees Fahrenheit, allowed for the transport and storage of the logistic unit.
The GS1 system provides standards for temperatures in Fahrenheit and Celsius units of measure. A maximum temperature SHALL NOT be applied in more than one unit of measure.
| GS1 Application Identifier | Temperature | |
|---|---|---|
| Absolute value of temperature (Measured in Fahrenheit with two decimal precision) | Negative Temperature | |
| Indicator | ||
| (when required) | ||
| 4 3 3 0 | N1 N2 N3 N4 N5 N6 | - |
The structure is: Absolute value of the temperature in Fahrenheit with two decimal precision: Last two digits will
- be after a decimal point (e.g., 023020 = 230.20° F)
Negative temperature indicator: If a negative temperature is intended, a “-“ is encoded as the
- last character in this AI field (e.g., 000250- = -2.50° F). If a “-“ is not encoded as the last character, the digits indicate a positive temperature. The data transmitted from the barcode reader means that the element string denoting a maximum temperature in hundredths of degrees Fahrenheit has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MAX TEMP F
3.7.49 Maximum temperature in Celsius: AI (4331)
The GS1 Application Identifier (4331) indicates that the data field contains the maximum temperature, measured in hundredths of degrees Celsius, allowed for the transport and storage of the logistic unit.
The GS1 system provides standards for temperatures in Fahrenheit and Celsius units of measure. A maximum temperature SHALL NOT be applied in more than one unit of measure.
| GS1 Application Identifier | Temperature | |
|---|---|---|
| Absolute value of temperature (Measured in Celsius with two decimal precision) | Negative Temperature | |
| Indicator | ||
| (when required) | ||
| 4 3 3 1 | N1 N2 N3 N4 N5 N6 | - |
The structure is: Absolute value of the temperature in Celsius with two decimal precision: Last two digits will be
- after a decimal point (e.g., 000090 = 0.90° C)
Negative temperature indicator: If a negative temperature is intended, a “-“ is encoded as the
- last character in this AI field (e.g., 001000- = -10.00° C). If a “-“ is not encoded as the last character, the digits indicate a positive temperature. The data transmitted from the barcode reader means that the element string denoting a maximum temperature in hundredths of degrees Celsius has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MAX TEMP C
3.7.50 Minimum temperature in Fahrenheit: AI (4332)
The GS1 Application Identifier (4332) indicates that the data field contains the minimum temperature, measured in hundredths of degrees Fahrenheit, allowed for the transport and storage of the logistic unit.
The GS1 system provides standards for temperatures in Fahrenheit and Celsius units of measure. A minimum temperature SHALL NOT be applied in more than one unit of measure.
| GS1 Application Identifier | Temperature | |
|---|---|---|
| Absolute value of temperature (Measured in Fahrenheit with two decimal precision) | Negative Temperature | |
| Indicator | ||
| (when required) | ||
| 4 3 3 2 | N1 N2 N3 N4 N5 N6 | - |
The structure is: Absolute value of the temperature in Fahrenheit with two decimal precision: Last two digits will
- be after a decimal point (e.g., 023020 = 230.20° F)
Negative temperature indicator: If a negative temperature is intended, a “-“ is encoded as the
- last character in this AI field (e.g., 000250- = -2.50° F). If a “-“ is not encoded as the last character, the digits indicate a positive temperature. The data transmitted from the barcode reader means that the element string denoting a minimum temperature in hundredths of degrees Fahrenheit has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MIN TEMP F
3.7.51 Minimum temperature in Celsius: AI (4333)
The GS1 Application Identifier (4333) indicates that the data field contains the minimum temperature, measured in hundredths of degrees Celsius, allowed for the transport and storage of the logistic unit.
The GS1 system provides standards for temperatures in Fahrenheit and Celsius units of measure. A minimum temperature SHALL NOT be applied in more than one unit of measure.
| GS1 Application Identifier | Temperature | |
|---|---|---|
| Absolute value of temperature (Measured in Celsius with two decimal precision) | Negative Temperature | |
| Indicator | ||
| (when required) | ||
| 4 3 3 3 | N1 N2 N3 N4 N5 N6 | - |
The structure is: Absolute value of the temperature in Celsius with two decimal precision: Last two digits will be
- after a decimal point (e.g., 000090 = 0.90° C)
Negative temperature indicator: If a negative temperature is intended, a “-“ is encoded as the
- last character in this AI field (e.g., 001000- = -10.00° C). If a “-“ is not encoded as the last character, the digits indicate a positive temperature. The data transmitted from the barcode reader means that the element string denoting a minimum temperature in hundredths of degrees Celsius has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MIN TEMP C
3.8 GS1 Application Identifiers starting with digit 7
3.8.1 Seven series AIs - Cautionary note
GS1 Application Identifiers issued in the 7 series represent a special case because they are restricted to: one or a small number of sectors (i.e. are not multi-sectoral) or
- a country or a region (i.e. are not global).
3.8.2 NATO Stock Number (NSN): AI (7001)
The GS1 Application Identifier (7001) indicates that the GS1 Application Identifier data field contains a NATO stock number. The NATO stock number is the number allocated to any item of supply in the NATO Alliance. It is the responsibility of the country that manufactures or controls the design of the item to allocate the number.
Note: This element string is only for use within the context of the supply within the NATO Alliance. Use of it is subject to the rules and regulations of the Allied Committee 135 (AC/135), the NATO Group of National Directors on Codification.
| GS1 Application Identifier | NATO supply classification ────────› | Assigning | Sequential |
|---|---|---|---|
| country | number | ||
| ────────› | ────────────› | ||
| 7 0 0 1 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 |
The data transmitted from the barcode reader means that the element string denoting a NATO stock number has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: NSN
3.8.3 UNECE meat carcasses and cuts classification: AI (7002)
The GS1 Application Identifier (7002) indicates that the GS1 Application Identifier data field contains a United Nations Economic Commission for Europe (UNECE, formerly known as UN/ECE) meat carcasses and cuts classification code. The UNECE meat carcasses and cuts code is an attribute of a Global Trade Item Number (GTIN) that denotes the trade description of the product. It is an alphanumeric, variable length code up to 30 characters.
Note: This element string is only for use within the context of UNECE standards for the quality of meat carcasses and cuts (bovine, porcine, ovine, and caprine).
| GS1 Application Identifier | UNECE product classification |
|---|---|
| 7 0 0 2 | X1────────variable length────────›X30 |
The data transmitted from the barcode reader means that the element string denoting a UNECE meat carcasses and cuts code has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: MEAT CUT
3.8.4 Expiration date and time: AI (7003)
The GS1 Application Identifier (7003) indicates that the data fields contain expiration date and time. The manufacturer determines the expiration date and time, which is relevant only for short duration and for items that will not be sent on long distances and not outside of the time zone.
A typical application of AI (7003) is in hospitals or public pharmacies for special, customised, products which may have a "life duration" shorter than one single day. The life duration varies according the pharmaceutical substances used in the treatment. The precise expiration date and time is defined at the end of the manufacturing process, and can be barcoded on the product label as an attribute to the item’s GTIN. Where there is no business requirement to express the expiration date to the nearest hour (or less), AI (17) Expiration date should be used.
The structure is: Year: the tens and units of the year (e.g., 2007 = 07), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory.
-
Hour: the number of the hour based on local 24-hour time (e.g., 2 p.m. = 14), which is mandatory.
-
Minutes: the number of the minutes based on local time (e.g., 15 minutes. = 15); if it is not
-
necessary to specify the minutes, the field must be filled with two zeroes. Time will then be interpreted as ending on the hour (e.g., 14:00 = expiry time at 14:00). Note: element string can only specify dates in the range from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 Application | Expiration date and time | ||||
|---|---|---|---|---|---|
| Identifier | YY | MM | DD | HH | MM |
| 7 0 0 3 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 |
The data transmitted from the barcode reader means that the element string denoting an expiration date and time has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: EXPIRY TIME
3.8.5 Active potency: AI (7004)
The GS1 Application Identifier (7004) indicates that the GS1 Application Identifier data field contains an active potency. The active potency of certain healthcare products (e.g., certain biologics, such as haemophilia products) varies by batch, and this will vary, within agreed tolerances, from the nominal potency of the trade item. Both the nominal and active potency of the item are measured in International Units (IUs).
| GS1 Application Identifier | Active potency |
|---|---|
| 7 0 0 4 | N1──variable length──› N4 |
The data transmitted from the barcode reader means that the Active potency of a Trade Item has been captured. The active potency must be processed with the GTIN and batch or lot number of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ACTIVE POTENCY
3.8.6 Catch area: AI (7005)
The GS1 Application Identifier (7005) indicates that the GS1 Application Identifier data field contains the Catch Area. The Catch Area identifies where the fisheries product was caught using the international fishing areas and subareas as defined by the United Nations Fisheries and Aquaculture Department of the Food and Agricultural Organization (FAO) A complete FAO Catch Area list can be accessed via: https://www.fao.org/fishery/en/area/search. It is assigned by the fishing vessel that has caught the fisheries product. These major fishing areas comprise:
Major inland fishing areas covering the inland waters of the continents,
-
Major marine fishing areas covering the waters of the Atlantic, Indian, Pacific and Southern
-
Oceans, with their adjacent seas.
Note: The major fishing areas, inland and marine, as well as the subareas can be identified when using this GS1 Application Identifier; FAO example: 27.8.e.2 West of Bay of Biscay Non- NEAFC Regulatory Area
| GS1 Application Identifier | Catch area |
|---|---|
| 7 0 0 5 | X1 ────›variable length ────›X12 |
The data transmitted from the barcode reader means that the element string denoting the Catch Area that has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CATCH AREA
3.8.7 First freeze date: AI (7006)
The GS1 Application Identifier (7006) indicates that the GS1 Application Identifier data field contains a first freeze date. The first freeze date is applicable to products that are frozen directly after slaughtering, harvesting, catching or after initial processing of the product. Examples include fresh meat, meat products or fishery products. The first freeze date is determined by the organisation conducting the freezing.
The structure is: Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); this field must always
-
be filled.
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 Application | First freeze date | ||
|---|---|---|---|
| Identifier | Year | Month | Day |
| 7 0 0 6 | N1 N2 | N3 N4 | N5 N6 |
The data transmitted from the barcode reader means that the element string denoting a first freeze date has been captured. As this element string is an attribute of a trade item, it must be processed together with the trade item GTIN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: FIRST FREEZE DATE
3.8.8 Harvest date: AI (7007)
The GS1 Application Identifier (7007) indicates that the GS1 Application Identifier data field contains a harvest date or date range. For example, the harvest date can be the date or date range when an animal was slaughtered or killed, a fish has been harvested, or a crop was harvested. This date or date range is determined by the organisation conducting the harvesting. Different organisations may use more specific terminology when referring to their specific needs and use terms such as: Date of catch or slaughter date. When referring to animals the date range refers to the whole animal and all meat or fish cuts derived from this animal.
The structure includes two distinct segments: Start date: This specifies the start of the time period being identified:
-
Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02); for a harvest
-
date. This field must always be filled.
End date: This specifies the end of the time period being identified:
-
Year: the tens and units of the year (e.g., 2003 = 03).
-
Month: the number of the month (e.g., January = 01).
-
Day: the number of the day of the relevant month (e.g., second day = 02); for a harvest
-
date.
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12. Note: In case the catch period spans one calendar day, the end date SHALL NOT be specified.
In case the catch period spans multiple calendar days, both the start and end date must be specified, with the end date being greater than the start date.
| GS1 Application | Harvest start date | Harvest end date | ||||
|---|---|---|---|---|---|---|
| Identifier | Year | Month | Day | Year | Month | Day |
| 7 0 0 7 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 | N11 N12 |
The data transmitted from the barcode reader means that the element string denoting a harvest date range has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: HARVEST DATE
3.8.9 Species for fishery purposes: AI (7008)
The GS1 Application Identifier (7008) indicates that the GS1 Application Identifier data field contains the fish species according to the 3-alpha Aquatic Sciences and Fisheries Information System (ASFIS) list of species.
The United Nations Fisheries and Aquaculture Department of the Food and Agricultural Organization (FAO) Fisheries and Aquaculture Statistics and Information Service (FIPS) collates world capture and aquaculture production statistics at the species, genus, family or higher taxonomic levels in 2,119 statistical categories (2011 data) referred to as species items. ASFIS list of species includes 12,421 species items selected according to their interest or relation to fisheries and aquaculture. For each species item stored in a record, codes (International Standard Statistical Classification of Aquatic Animals and Plants group, taxonomic and 3-alpha) and taxonomic information (scientific name, author(s), family and higher taxonomic classification) are provided. An English name is available for most of the records, and about one third of them have also a French and Spanish name. Information is also provided about the availability of fishery production statistics on the species item in the FAO databases; example: IZX. This list can be accessed via:
http://www.fao.org/fishery/collection/asfis/en
| GS1 Application Identifier | Species for fishery purposes code |
|---|---|
| 7 0 0 8 | X1 ──variable length──› X3 |
The data transmitted from the barcode reader means that the element string denoting the species for fishery purposes that has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: AQUATIC SPECIES
3.8.10 Fishing gear type: AI (7009)
The GS1 Application Identifier (7009) indicates that the GS1 Application Identifier data field contains the information on the fishing gear type. It is assigned by the fishing vessel that has caught the fisheries product. The fishing gear type, as defined by the United Nations Fisheries and Aquaculture Department of the Food and Agricultural Organization (FAO), is used to identify the type of fishing gear used for catching the fisheries product. The fishing gear type list provides definitions of fishing gear of all kinds, grouped by categories. These definitions and classifications are valid on a world-wide basis for both inland waters and sea fisheries, as well as, for small-, medium- and large-scale fisheries; example: 01.1.1 (one boat operated purse seines). This list can be accessed via:
http://www.fao.org/fishery/cwp/handbook/M/en.
| GS1 Application Identifier | Fishing gear type |
|---|---|
| 7 0 0 9 | X1──── variable length ────›X10 |
The data transmitted from the barcode reader means that the element string denoting the fishing gear type that has been captured. This element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: FISHING GEAR TYPE
3.8.11 Production method: AI (7010)
The GS1 Application Identifier (7010) indicates that the GS1 Application Identifier data field describes the production method. It is assigned by the fishing vessel that has caught the fisheries product. The production method provides the production method for fish and seafood as specified by the Fisheries and Aquaculture Department of the Food and Agricultural Organization (FAO) of the United Nations; example: 01.
The allowed values, as defined by the Fisheries and Aquaculture Department of the Food and Agricultural Organization (FAO) of the United Nations are: 01 ‘Caught at Sea’.
-
02 ‘Caught in Fresh Water’.
-
03 ‘Farmed’.
-
04 ‘Cultivated’.
| GS1 Application Identifier | Production method |
|---|---|
| 7 0 1 0 | X1── variable length ──›X2 |
The data transmitted from the barcode reader means that the element string denoting the production method has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROD METHOD
3.8.12 Test by date: AI (7011)
The GS1 Application Identifier (7011) indicates that the GS1 Application Identifier data field contains a test by date and optional time. The test by date and optional time is specified by the manufacturer as the last date and time the product is acceptable for use without testing. For instance, the manufacturer may use the test by date to indicate when an ingredient used in the manufacture of a pharmaceutical product is to be tested.
The structure is: Year: the tens and units of the year (e.g., 2003 = 03), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory.
-
Hour and minutes: the hour and minutes based on local 24-hour time (e.g., 2:30 p.m. =1430),
-
which is optional
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12. Note: The day of the month SHALL NOT be expressed as two zeroes. A valid day of the month (e.g., last day of July = 31) SHALL be included.
| GS1 Application Identifier | Test by date | ||||
|---|---|---|---|---|---|
| Test by date | Test by time | ||||
| (optional) | |||||
| Year | Month | Day | Hour | Minutes | |
| 7 0 1 1 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 |
The data transmitted from the barcode reader means that the element string denoting a test by date and optional time has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN to which it relates (see section 4.13 Data relationships).
After the test by date if the product is determined to be fit for use, the result should be communicated by the responsible party and, if necessary, a new test by date established. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: TEST BY DATE
3.8.13 Refurbishment lot ID: AI (7020)
GS1 Application Identifier (7020) indicates that the GS1 Application Identifier data field contains a refurbishment lot ID. Together with the GTIN of the trade item and the GLN of the production or service location, the refurbishment lot ID identifies a batch of items that were remanufactured to the original specifications using a combination of reused, repaired and new parts. It is an alphanumeric, variable length string of up to 20 characters.
| GS1 Application Identifier | Refurbishment lot ID |
|---|---|
| 7 0 2 0 | X1──────── variable length ────────›X20 |
The data transmitted from the barcode reader means that the element string denoting a refurbishment lot ID has been captured. It must be processed together with the GLN of the production/service location and the GTIN of the item to which it is related (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: REFURB LOT
3.8.14 Functional status: AI (7021)
GS1 Application Identifier (7021) indicates that the GS1 Application Identifier data field contains the functional status. The functional status of the trade item may need to be included by the manufacturer to meet regulatory or commercial requirements. For example requirements related to the type approval, allowing the trade item to be sold in a particular country.
| GS1 Application Identifier | Functional status |
|---|---|
| 7 0 2 1 | X1──────── variable length ────────›X20 |
The data transmitted from the barcode reader means that the element string denoting a functional status has been captured. As this element string is an attribute of a trade item, it must be processed in combination with the GTIN of the item to which it is related (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: FUNC STAT
3.8.15 Revision status: AI (7022)
GS1 Application Identifier (7022) indicates that the GS1 Application Identifier data field contains the revision status. The revision status of the trade item may need to be included by the manufacturer to meet regulatory or commercial requirements. For example, requirements related to the type approval, allowing the trade item to be sold in a particular country.
| GS1 Application Identifier | Revision status |
|---|---|
| 7 0 2 2 | X1──────── variable length ────────›X20 |
The data transmitted from the barcode reader means that the element string denoting a revision status has been captured. As this element string is subordinate to the functional status, it must be processed in combination with the functional status and the GTIN of the item to which it is related (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: REV STAT
3.8.16 Global Individual Asset Identifier of an assembly: AI (7023)
GS1 Application Identifier (7023) indicates that the GS1 Application Identifier data field contains the GIAI (Global Individual Asset Identifier) of an assembly. An additional barcode containing the GIAI of an assembly may need to be marked on a sub- component of the assembly (the so called leading part) in case the assembly does not have a surface that uniquely belongs to the assembly (and not to any of its sub-components). In order to distinguish between the identifier of the sub-component and the identifier of the assembly a separate GS1 application identifier is used for the latter.
The GS1 Company Prefix (see section 1.2.3.3) is allocated by GS1 Member Organisations to the company that allocates the GIAI – the asset owner or manager of the individual asset. The structure and content of the individual asset reference is at the discretion of the asset owner or manager. It may contain all characters listed in Table 7-20.
| GS1 | Global Individual Asset Identifier (GIAI) of an assembly | |
|---|---|---|
| Application Identifier | GS1 Company Prefix ───────────────› | Individual asset reference |
| ──────────────────────────────› | ||
| 7 0 2 3 | N1 ... Ni Xi+1 ... variable length Xj (j<=30) |
The data transmitted from the barcode reader means that the element string denoting a parent GIAI has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GIAI - ASSEMBLY
3.8.17 Number of processor with three-digit ISO country code: AI (703s)
The GS1 Application Identifier (703s) indicates that the GS1 Application Identifier data fields contain the ISO country code and approval number or GLN of the processor of a trade item. The number of processor is an attribute to a Global Trade Item Number (GTIN). It designates the number of the company who did the processing.
As many processors may be involved, each with an individual approval number, the fourth digit of the AI (s in the figure below) indicates the sequence of the processors. For a typical meat supply chain, the following sequence would be used:
7030: slaughterhouse
-
7031: first deboning/cutting hall
-
7032 to 7037: second through seventh processing location (cutting hall)
-
7038: slaughterhouse
-
7039: slaughterhouse
-
For a typical seafood supply chain, the following sequence would be used:
7030 vessel/aquaculture site
-
7031 primary processor
-
7032 secondary processor
-
The ISO country code contains the three-digit country number of the numerical international standard ISO 3166 that relates to the following approval number of processor. If ‘999’ is entered as the ISO country code it signifies that the subsequent data is a Global Location Number (GLN), and not an ‘approval number’.
Note: The approval number is usually assigned by a national or pluri-national authority to processors in the food supply chain. These authorities may choose to use the Global Location Number (GLN) (see section 2.4) for this purpose. The approval number (or GLN) remains with the item regardless of whether or not it changes ownership or function.
| GS1 Application Identifier | ISO country code | Number of processor |
|---|---|---|
| 7 0 3 s | N1 N2 N3 | X4 ─── variable length ────› X30 |
The data transmitted from the barcode reader means that the element string denoting the ISO country code and number of processor has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROCESSOR # s
3.8.18 GS1 UIC with Extension 1 and Importer index: AI (7040)
The GS1 Application Identifier (7040) indicates that the GS1 Application Identifier data field contains the Unique Identification Code of an EU 2018/574 ID Issuer, the National Authority that appointed it (via the GS1 UIC Extension 1), and, if applicable, the Importer (via an Importer Index). The UIC begins with one numeric digit followed by one alphanumeric character from the ISO/IEC 646 invariant character set per Table 7-20. The GS1 UIC Extension 1 is one alphanumeric character from the ISO/IEC 646 invariant character set per Table 7-20. The Importer Index is one character and include A-Z, a-z, 0-9, - (hyphen) and _ (underscore). Underscore is used to indicate the importer index does not apply (null). The other characters identify up to 63 importers of a product per country of placement. This identifier is authorised for use by the ID Issuer as long as it meets minimum requirements established by GS1. The use of UIC is limited to application standard 2.1.14 European Regulation 2018/574, traceability of tobacco products. The UIC shall be used solely exclusively to facilitate identification of country level authorisation for GS1 identification keys within illicit trade surveillance systems. The UIC shall not be used with GS1 identification keys for open, supply chain systems.
| GS1 Application Identifier | GS1 UIC with Extension 1 and Importer index | ||
|---|---|---|---|
| GS1 UIC | Extension 1 | Importer index | |
| 7 0 4 0 | N1 X2 | X3 | X4 |
The data transmitted from the barcode reader means that the element string denoting a Unique Identification Code has been captured. When indicating this element string in the non-HRI text section of a barcode label, this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: UIC+EXT
3.8.19 UN/CEFACT freight unit type: AI (7041)
The GS1 Application Identifier (7041) indicates that the data field contains the type of freight of the logistic unit. The codes used for freight unit type are the UN/CEFACT alphanumeric codes. GS1 maintains a list based on the UN/ECE Recommendation 21 codes on GS1 Navigator which includes some additional GS1 code values. All codes in the UN/ECE Recommendation 21 and GS1 code list are valid codes to be used with AI (7041). A list of code values maintained by GS1 can be viewed at: https://navigator.gs1.org/edi/codelist-details?name=PackageTypeCode.
| GS1 Application | UN/CEFACT freight unit type code |
|---|---|
| Identifier | |
| 7 0 4 1 | X1──── variable length ────›X4 |
The data transmitted from the barcode reader means that the element string denoting the freight unit type has been captured. As this element string is an attribute to a logistic unit it must be processed together with the SSCC of the unit to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: UFRGT UNIT TYPE
3.8.20 National Healthcare Reimbursement Number (NHRN): AIs (710), (711), (712),
(713), (714), (715), (716) and (717) The GS1 Application Identifiers (710), (711), (712), (713), (714), (715), (716) and (717) indicate that the GS1 Application Identifier data field contains a National Healthcare Reimbursement Number, from the NHRN GS1 Application Identifier series, associated to the Global Trade Item Number (GTIN) of the trade item. The GS1 Application Identifiers (710), (711), (712), (713), (714), (715), (716) and (717) indicate a specific NHRN from within the assigned series.
Use of the NHRN GS1 Application Identifier, associated to the GTIN of the trade item, is needed for compliance with a national/regional regulatory or industry requirement where the GTIN will not meet the need.
GTIN is the GS1 identifier for pharmaceutical and medical device trade items. The GS1 Application Identifier for National Healthcare Reimbursement Number is provided to meet regulatory or industry requirements until they are amended to accept the GTIN as a compliant identifier.
Within this application are the rules and recommendations for the association of NHRNs to the Global Trade Item Number (GTIN) where regulatory requirements require an NHRN for product identification, registration or reimbursement purposes.
There are a number of known NHRNs but at this time not all are required to be encoded within the data carrier found on the trade item. Flexibility for additional assigned NHRN AIs has been provided if required.
The National Healthcare Reimbursement Number GS1 Application Identifier is an initial step in a migration path to the most efficient method to identify trade items. GS1 recommends that Healthcare stakeholders faced with national numbers:
a. Use GTIN for all supply chain and reimbursement purposes (GTIN used in the data carrier and as the NHRN) as this is the most efficient and effective way for all stakeholders to identify trade items.
b. Use GTIN, cross-referenced to an NHRN in an existing database, in the case of an existing system of NHRNs (i.e. GTIN used in the data carrier with the NHRN found via cross- reference).
c. Use GTIN with an associated NHRN (GTIN and NHRN both used in the data carrier via the NHRN AI) as an intermediate solution for those who cannot use “a” or “b”. GS1 only recommends this as a migration path to noted options “a” or “b”.
Important: - There is a mandatory association of the National Healthcare Reimbursement Number Application Identifier with the GTIN. - The NHRN is usually assigned by a national authority to healthcare brand owners for specific trade items and SHALL only be used for compliance to regulatory requirements where the GTIN alone will not meet the requirements.
-
Additional individual NHRN AIs can only be assigned by GS1 and only in response to a work request being submitted through GSMP. - The GTIN and all associated NHRNs SHOULD be concatenated into a single data carrier (i.e. single GS1-128, GS1 DataMatrix). - Use of NHRN on the item is controlled by and subject to the rules and regulations of national/regional agencies. Those rules and/or regulations may supersede these recommendations.
-
More than one NHRN may need to be associated with a given GTIN.
The general format of an NHRN GS1 Application Identifier is:
| GS1 Application Identifier | National Healthcare Reimbursement |
|---|---|
| Number | |
| n n n | X1──── variable length ────›X20 |
When an NHRN AI is approved, the overall variable length (i.e. allowable number of characters) is specified by the national authority, with a twenty (20) character maximum as noted in the general format above if applicable.
The GS1 Application Identifiers used with this element string, their specific format and associated regulatory body or assigning organisation, are shown in Table 3-9:
Table 3-10 Overview of NHRN Application Identifiers
| GS1 Application | National Healthcare Reimbursement | Organisation |
|---|---|---|
| Identifier | Number | |
| 710 | X1 variable length X20 | Germany IFA |
| GS1 Application | National Healthcare Reimbursement | Organisation |
|---|---|---|
| Identifier | Number | |
| 711 | X1 variable length X20 | France CIP |
| 712 | X1 variable length X20 | Spain National Code |
| 713 | X1 variable length X20 | Brazil ANVISA |
| 714 | X1 variable length X20 | Portugal INFARMED |
| 715 | X1 variable length X20 | United States of America FDA |
| 716 | X1 variable length X20 | Italy AIFA |
| 717 | X1 variable length X20 | Costa Rica Ministry of Health |
| nnn (*) | X1 variable length X20 | Country “A” NHRN Authority |
| (*) An example to illustrate future additional NHRNs. If additional NHRN AIs are required, a request for | ||
| a new NHRN AI SHALL be made through GSMP. |
Companies wishing to apply one of the listed NHRN AIs will need to associate that NHRN AI to the trade item’s GTIN according to the NHRN AI rules and should contact their GS1 Member Organisation for further considerations of use.
The data transmitted from the barcode reader means that the element string denoting a National Healthcare Reimbursement Number has been captured. This element string is an attribute of a trade item and must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the data title listed in Table 3-1 SHOULD be used.
3.8.21 Certification reference: AI (723s)
The GS1 Application Identifier (723s) indicates that the GS1 Application Identifier data field contains a reference to a product certification. The certification reference is an attribute of a trade item or an individual asset.
As multiple certificates may be present, each with an individual certification reference, the fourth digit of the AI (s in the figure below) indicates the sequence of the certification references.
The general structure of AI (723s) is: Certification scheme (2 characters) defined by GS1. The following code values are currently
- allowed:
“EM” (European Marine Equipment Directive). See http://eur-lex.europa.eu/legal-
- content/EN/AUTO/?uri=CELEX:32018R0608 for more information.
Certification reference (28 characters)
| GS1 Application Identifier | Certification scheme | Certification reference |
|---|---|---|
| 7 2 3 s | X1 X2 X3 ───variable length────› X30 |
The data transmitted from the barcode reader means that the element string denoting the certification reference has been captured. As this element string is an attribute of a trade item or an asset, it must be processed together with the GTIN of the trade item or the GIAI of the asset to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CERT # s
3.8.22 Protocol ID: AI (7240)
The GS1 Application Identifier (7240) indicates that the GS1 Application Identifier data field contains the identifier of a clinical trial protocol. The data is alphanumeric and may include all characters listed in Table 7-20.
| GS1 | Protocol ID |
|---|---|
| Application | |
| Identifier | |
| 7 2 4 0 | X1 ───variable length────› X20 |
The data transmitted from the barcode reader means that the element string denoting the protocol ID has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROTOCOL
3.8.23 AIDC media type: AI (7241)
The GS1 Application Identifier (7241) indicates that the GS1 Application Identifier data field contains an AIDC media type. The AIDC media type allows the differentiation of what type of object or entity the GS1 AIDC data carrier is displayed or carried on. For example, a GS1 AIDC data carrier encoded with a Global Service Relation Number (GSRN) may be displayed on an identity card or an order form.
The structure and content of the AIDC media type are defined below to ensure the correct AIDC media type value is referenced. An overview of the AIDC media type value ranges is provided in Table 3-10.
| GS1 Application Identifier | AIDC media type - value |
|---|---|
| 7 2 4 1 | N1 N2 |
The data transmitted from the barcode reader means that the element string denoting an AIDC media type has been captured. Since the AIDC media type is an attribute of a service relation, it must be processed together with the GSRN of the service relation to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: AIDC MEDIA TYPE
Table 3-11 Overview of the AIDC media type table values
| AIDC media type - value | AIDC media type – value range assignments |
|---|---|
| 00 | Not used |
| 01 to 10 | Current ICCBBA assignment |
| 11 to 29 | Reserved for ICCBBA future assignment |
| 30 to 59 | Reserved for GS1 assignment |
| 60 to 79 | Reserved for future capacity needs of ICCBBA or GS1 if the initial capacity of values for either organisation is exhausted |
| 80 to 99 | Reserved for local or national use |
Table 3-12 AIDC media type table values
| AIDC media | AIDC media type | Defined by |
|---|---|---|
| type value | ||
| 00 | Not used | ICCBBA |
| 01 | Wristband | ICCBBA |
| 02 | Order form | ICCBBA |
| 03 | Sample Tube | ICCBBA |
| 04 | Working list / Lab list / form | ICCBBA |
| AIDC media | AIDC media type | Defined by |
|---|---|---|
| type value | ||
| 05 | Test report | ICCBBA |
| 06 | Delivery note / issue documentation | ICCBBA |
| 07 | Intended recipient label (attached to container) | ICCBBA |
| 08 | Label affixed to product | ICCBBA |
| 09 | Identity card | ICCBBA |
| 10 | Clinical or progress notes | ICCBBA |
| 11-29 | Reserved for ICCBBA future assignment | ICCBBA |
| 30-59 | Reserved for GS1 future assignment | GS1 |
| 60-79 | Reserved for future capacity needs of ICCBBA or GS1 if the initial capacity of values for either organisation is exhausted | ICCBBA or GS1 |
| 80-99 | Reserved for local or national use | ICCBBA |
Note: The values above are technical standards. Normative GS1 use of these values is established within application standards (e.g., management of biological samples could potentially use this AI on several AIDC media types, for example, a patient wristband, the sample tube itself, or a staff ID card).
Note: GS1 and ICCBBA independently, but collaboratively, administer AIDC media type value definitions and their normative use. For example, GS1 may or may not normatively use a media type defined by ICCBBA and vice versa. This independence could result in a duplicate value if both organisations were considering it at the same time. To avoid this, both organisations have agreed to notify the other when new values are being considered.
ICCBBA - www.isbt128.org - is an international non-profit organisation, based in the US, that manages, develops, and licenses ISBT 128, the international information standard for the terminology, coding and labelling of medical products of human origin. The acronym ICCBBA is derived from the International Council for Commonality in Blood Banking Automation.
ICCBBA - ISBT 128 - Table RT018 detailing their AIDC media type – definitions: www.isbt128.org/RT018
3.8.24 Version Control Number (VCN): AI (7242)
The GS1 Application Identifier (7242) indicates that the GS1 Application Identifier data field contains a Version Control Number (VCN). VCN is used when there is a need to differentiate or distinguish between identification that may be present multiple times on the same AIDC media type. For example, when AIDC media such as an ID badge carrying the GSRN of a service provider (8017), or a patient wristband displaying the GSRN of a service recipient (8018) needs to be replaced due to being lost or discarded, the VCN enables distinction between the re-issued AIDC media and any previous versions.
The structure and content of the VCN is at the discretion of the organisation managing issuance and validation of the physical identification entity.
| GS1 Application Identifier | Version control number (VCN) |
|---|---|
| 7 2 4 2 | X1 ─── variable length ────› X25 |
The data transmitted from the barcode reader means that the element string denoting Version Control Number has been captured. Since the VCN is an attribute of a service relation, it must be processed together with the GSRN of the service relation to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: VCN Important: Prior to the development of the Version Control Number (VCN), the SRIN could also be optionally used with a GSRN as a sequence indicator for version control purposes. Use of the SRIN in this manner presents challenges when further requirements to qualify a service encounter are necessary, in addition to version control. For new version control requirements, the VCN SHALL be used instead of the SRIN.
3.8.25 Date of birth: AI (7250)
The GS1 Application Identifier (7250) indicates that the GS1 Application Identifier data field contains the date of birth, the date of birth structure is: Year: the thousands, the hundreds, the tens and units of the year (e.g., 2003 = 2003), which is
-
mandatory. The use of thousands and hundreds for persons is based on life expectancy potentially exceeding 100 years. Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory.
| GS1 | Date of birth | |||
|---|---|---|---|---|
| Application | Year | Month | Day | Day |
| Identifier | ||||
| 7 2 5 0 | N1 N2 N3 N4 | N5 N6 | N7 N8 |
The data transmitted from the barcode reader means that the element string denoting a date of birth has been captured. As this element string is an attribute of a GSRN - RECIPIENT, it must be processed together with the GSRN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: DOB
3.8.26 Date and time of birth: AI (7251)
The GS1 Application Identifier (7251) indicates that the GS1 Application Identifier data field contains a date and time of birth, the date and time of birth structure is: Year: the thousands, the hundreds, the tens and units of the year (e.g., 2003 = 2003), which is
-
mandatory. The use of thousands and hundreds for persons is based on life expectancy potentially exceeding 100 years. Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory.
-
Hour: the number of the hour based on local 24-hour time (e.g., 2 p.m. = 14), which is mandatory.
-
Minutes: the number of the minutes based on local time (e.g., 15 minutes = 15), which is
-
mandatory.
| GS1 Application | Date and time of birth | ||||
|---|---|---|---|---|---|
| Identifier | YYYY | MM | DD | HH | MM |
| 7 2 5 1 | N1 N2 N3 N4 | N5 N6 | N7 N8 | N9 N10 | N11 N12 |
The data transmitted from the barcode reader means that the element string denoting a date and time of birth has been captured. As this element string is an attribute of a GSRN – RECIPIENT, it must be processed together with the GSRN – RECIPIENT to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: DOB TIME Note: The use of the GS1 Application Identifier (7251) is used for the purposes of recording the date and time of birth of a baby within a maternity environment. When there is no business requirement to express the time of birth then the use of GS1 Application Identifier (7250) should be used.
3.8.27 Biological sex: AI (7252)
The GS1 Application Identifier (7252) indicates that the GS1 Application Identifier data field indicates the biological sex of the subject of care as defined and detailed in “ISO/IEC 5218:2022 Information technology — Codes for the representation of human sexes”.
| GS1 Application Identifier | Biological sex |
|---|---|
| 7 2 5 2 | N1 |
The defined values currently in ISO 5218:2022 for biological sex are:
-
0 = Not known
-
1 = Male
-
2 = Female
-
9 = Not applicable
The data transmitted from the barcode reader means that the element string denoting the biological sex has been captured. As this element string is an attribute to a GSRN – RECIPIENT it must be processed together with GSRN - RECIPIENT (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BIO SEX
3.8.28 Family name of person: AI (7253)
The GS1 Application Identifier (7253) indicates that the GS1 Application Identifier data field contains family name of person information for the purpose of aiding positive patient identification.
The family name of person field is alphanumeric and may include all characters contained in Table 7-20 Note: A family name may also be known as a “Surname” or “Last Name”.
| GS1 Application Identifier | Family name of person |
|---|---|
| 7 2 5 3 | X1───────────›variable length ───────────›X40 |
The data transmitted from the barcode reader means that the element string denoting family name of person has been captured. As this element string is an attribute to the GSRN, it must be processed together with the identification key to which it relates (see section 4.13 Data relationships). As a free text field for positive patient information, non-Latin characters and a space character may be encoded.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: FAMILY NAME Note: To encode non-Latin characters within the alphanumeric value, use percent-encoding as defined within RFC 3986. A space character should be encoded as a single plus symbol, +.
3.8.29 Given name of person: AI (7254)
The GS1 Application Identifier (7254) indicates that the GS1 Application Identifier data field contains given name information for the purpose of aiding positive patient identification.
The given name of person field is alphanumeric and may include all characters contained in Table 7-20. Note: A given name may also be known as a first name, middle name, forename, second name, other given name or other given name/s.
| GS1 Application Identifier | Given name of person |
|---|---|
| 7 2 5 4 | X1───────────›variable length ───────────›X40 |
The data transmitted from the barcode reader means that the element string denoting given name of person has been captured. As this element string is an attribute to the GSRN, it must be processed together with the GSRN to which it relates (see section 4.13 Data relationships). As a free text field for positive patient information, non-Latin characters and a space character may be encoded.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GIVEN NAME Note: To encode non-Latin characters within the alphanumeric value, use percent-encoding as defined within RFC 3986. A space character should be encoded as a single plus symbol, +.
3.8.30 Name suffix of person: AI (7255)
The GS1 Application Identifier (7255) indicates that the GS1 Application Identifier data field contains name suffix of person information for the purpose of aiding identification. The name suffix of person field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Name suffix of person |
|---|---|
| 7 2 5 5 | X1───────────›variable length ───────────›X10 |
The data transmitted from the barcode reader means that the element string denoting name suffix of person has been captured. As this element string is an attribute to the GSRN, it must be processed together with the GSRN to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SUFFIX The following is a list of commonly used abbreviation examples. This list is not exhaustive, the decision as to whether to use the full name suffix or abbreviation is determined based on the maximum allowed field length:
-
Junior or Jr
-
Senior or Sr
-
First or I
-
Second or II
-
Third or III
-
Fourth or IV
Fifth or V
- Note: Name suffix is an additional term used following a person’s name to identify a subject of care or provider of care.
3.8.31 Full name of person: AI (7256)
The GS1 Application Identifier (7256) indicates that the GS1 Application Identifier data field contains full name of person information for the purpose of aiding positive patient identification. This field is a composite data element that is captured through the combination of GS1 Application Identifiers (7253) Family name of person, (7254) Given name of person and (7255) Name suffix of person.
The Full name of person field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Full name of person |
|---|---|
| 7 2 5 6 | X1───────────›variable length ───────────›X90 |
The data transmitted from the barcode reader means that the element string denoting full name of person has been captured. As a free text field for name identification information, non-Latin characters and a space character may be encoded. As this element string is an attribute to the GSRN, it must be processed together with the GSRN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: FULL NAME Note: To encode non-Latin characters within the alphanumeric value, use percent-encoding as defined within RFC 3986. A space character should be encoded as a single plus symbol, +.
Note: When shown as non-HRI text, it is advised to capitalise the Family name of person field to ensure no confusion with other name fields. Note: The order in which these identifiers are used, including their presence and use of a field delimiter, may be determined by regulatory or local user requirements. If a delimiter is required to separate different data fields within the “Full name of person” field then the comma character “,” is recommended for use.
3.8.32 Address of person: AI (7257)
The GS1 Application Identifier (7257) indicates that the GS1 Application Identifier data field contains information about the address of a person for the purpose of aiding positive patient identification (e.g., House number / flat number, street details an example being “Av. Louise 326”).
The address of person field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Address of person |
|---|---|
| 7 2 5 7 | X1───────────›variable length ───────────›X70 |
The data transmitted from the barcode reader means that the element string denoting address of person has been captured. As a free text field for name identification information, non-Latin characters and a space character may be encoded. As this element string is an attribute to the GSRN, it must be processed together with the GSRN to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PERSON ADDR Note: To encode non-Latin characters within the alphanumeric value, use percent-encoding as defined within RFC 3986. A space character should be encoded as a single plus symbol, +.
3.8.33 Baby birth sequence indicator: AI (7258)
The GS1 Application Identifier (7258) indicates that the GS1 Application Identifier data field indicates the baby birth sequence indicator and is used to identify the sequence in which a baby was born and the total number of babies in the series.
| Baby birth sequence indicator | |||
|---|---|---|---|
| GS1 Application Identifier | Sequence of birth of the baby | Sequence separator using solidus character | Total number of |
| babies in the | |||
| series | |||
| 7 2 5 8 | N1 | X1 | N1 |
The first number is the sequence of birth of the baby within the series followed by a "solidus" followed by the second number which is the total number of babies in the series. For example:
-
1/1 – One baby
-
1/2 – First of two babies (twin 1)
-
2/2 – Second of two babies (twin 2)
-
1/3 – First of three babies (triplet 1)
-
2/3 – Second of three babies (triplet 2)
-
3/3 – Third of three babies (triplet 3)
Note: The second character used in this element string as detailed by X1 shall be the “solidus” character as represented as the “/” graphic symbol and detailed in Table 7-20. The data transmitted from the barcode reader means that the element string denoting the baby birth sequence indicator has been captured. As this element string is an attribute to a GSRN – RECIPIENT it must be processed together with GSRN – RECIPIENT (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BIRTH SEQUENCE
3.8.34 Baby of family name: AI (7259)
The GS1 Application Identifier (7259) indicates that the GS1 Application Identifier data field contains Baby of family name information for the purpose of aiding positive patient identification. This field is a composite data element that is captured through the combination of the Application Identifier (7253) Family Name and free text indicating the identification of the specific “baby” being identified.
The Baby of Family Name field is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Baby of family name |
|---|---|
| 7 2 5 9 | X1───────────›variable length ───────────›X40 |
The data transmitted from the barcode reader means that the element string denoting baby of family name has been captured. As a free text field for positive patient information, non-Latin characters and a space character may be encoded. As this element string is an attribute to the GSRN - RECIPIENT, it must be processed together with the GSRN – RECIPIENT to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: BABY Note: To encode non-Latin characters within the alphanumeric value, use percent-encoding as defined within RFC 3986. A space character should be encoded as a single plus symbol, +.
Note: Baby of family name – In many countries it is common for a child to be born and initially not provided a “given name” by the mother, parents etc. Depending on the jurisdiction it then becomes a legal requirement to decide the “given name” within a defined period of time, for example in the UK it is 42 days and Norway it is 90 days.
Note: A family name may also be known as a “surname” or “last name”.
3.9 GS1 Application Identifiers starting with digit 8
3.9.1 Roll products - width, length, core diameter, direction, splices: AI (8001)
The GS1 Application Identifier (8001) indicates that the GS1 Application Identifier data fields contain the variable attributes of a roll product. Depending on the method of production, some roll products cannot be numbered according to standard criteria that have been determined in advance. They are, therefore, classified as variable items. For those products where the standard trade measures are not sufficient, the following guidelines should be used.
The identification of a roll product consists of the Global Trade Item Number (GTIN) and the variable attributes. The basic product (e.g., a certain type of paper) is included as data in the GTIN-14 ID number (see section 2.1.10), and the variables contain information about the special features of the particular item that has been produced. The variable values of a roll product, N1 to N14, consist of the following data:
N1 to N4: slit width in millimetres (width of the roll)
-
N5 to N9: actual length in metres
-
N10 to N12: internal core diameter in millimetres
-
N13: winding direction (face out 0, face in 1, undefined 9)
-
N14: number of splices (0 to 8 = actual number, 9 = number unknown)
| GS1 Application Identifier | Variable values of a roll product | ||||
|---|---|---|---|---|---|
| 8 0 0 1 | N1 N2 N3 N4 | N5 N6 N7 N8 N9 | N10 N11 N12 | N13 | N14 |
The data transmitted from the barcode reader means that the element string denoting the variable attributes of the identification of a roll product trade item have been captured. This element string must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: DIMENSIONS
3.9.2 Cellular mobile telephone identifier: AI (8002)
The GS1 Application Identifier (8002) indicates that the GS1 Application Identifier data field contains the serial number of a cellular mobile telephone. The serial number field is alphanumeric and may contain all characters contained in Table 7-20. A national or pluri-national authority usually assigns the number. It uniquely identifies each mobile telephone within a given authority for special control purposes. It is not considered as an attribute of the identification of the telephone as a trade item.
| GS1 Application Identifier | Serial number |
|---|---|
| 8 0 0 2 | X1 ────variable length ────› X20 |
The data transmitted from the barcode reader means that the element string denoting an electronic serial identifier of a cellular mobile telephone has been captured. This element string is normally processed as stand-alone information.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CMT No. Important: With the addition of the application standard for identification for activation of mobile devices/equipment in August 2025, see section 2.1.16, this GS1 AI is considered a legacy practice and SHALL NOT be used for future applications.
3.9.3 Global Returnable Asset Identifier (GRAI): AI (8003)
The GS1 Application Identifier (8003) indicates that the GS1 Application Identifier data field contains the GRAI (Global Returnable Asset Identifier). The GRAI is used to identify returnable assets.
The GS1 Company Prefix (see section 1.2.3.3) is allocated by GS1 Member Organisations to the company that allocates the GRAI – the asset owner or manager of the returnable asset. It makes the number unique worldwide.
When using AI (8003), a leading zero SHALL be required before the GRAI. This zero was originally added to support efficient use in GS1-128. The zero is mandatory for all GS1 barcodes that can encode AI (8003).
The structure and content of the asset type is at the discretion of the asset owner or manager. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
The optional serial component is assigned by the asset owner or manager. It identifies an individual asset within a given asset type. The field is alphanumeric and may contain all characters listed in Table 7-20.
| GS1 | Lead | Global Returnable Asset Identifier (GRAI) | ||
|---|---|---|---|---|
| Application Identifier | GS1 Company Prefix | Asset type | Check | Serial component |
| ─────────────› | ‹───────────── | digit | (optional) | |
| 8 0 0 3 | 0 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | N13 | X1 variable X16 |
The data transmitted from the barcode reader means that the element string denoting the GRAI has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GRAI
3.9.4 Global Individual Asset Identifier (GIAI): AI (8004)
The GS1 Application Identifier (8004) indicates that the GS1 Application Identifier data field contains a GIAI (Global Individual Asset Identifier). The GIAI is used for the unique identification of individual assets.
Note: Note: This element string must never be used to identify the entity as a trade item or logistic unit. If an asset is transferred between parties, the GIAI cannot be used for ordering the asset. However, asset identification may be exchanged between parties for the purpose of traceability.
The GS1 Company Prefix (see section 1.2.3.3) is allocated by GS1 Member Organisations to the company that allocates the GIAI – here the asset owner or manager. It makes the number unique worldwide.
The structure and content of the individual asset reference is at the discretion of the asset owner or manager. It may contain all characters listed in Table 7-20.
| GS1 | Global Individual Asset Identifier (GIAI) | |
|---|---|---|
| Application | GS1 Company Prefix ───────────────› | Individual asset reference |
| Identifier | ──────────────────────────────› | |
| 8 0 0 4 | N1 ... Ni Xi+1 ... variable length Xj (j<=30) |
The data transmitted from the barcode reader means that the element string denoting a GIAI has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GIAI
3.9.5 Price per unit of measure: AI (8005)
The GS1 Application Identifier (8005) indicates that the GS1 Application Identifier data field contains a price per unit of measure. This element string is used to indicate the price per unit of measure of price marked goods on a variable measure trade item to discriminate price variants of the same item. It is considered as an attribute of the respective trade item and not as part of its identification.
Content and structure of the price per unit of measure field are left to the discretion of the trading partners.
| GS1 Application Identifier | Price per unit of measure |
|---|---|
| 8 0 0 5 | N1 N2 N3 N4 N5 N6 |
The data transmitted from the barcode reader means that the element string denoting the price per unit of measure has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRICE PER UNIT Note: This element string is not recommended for open and global applications. The use of the element string denoting “Amount payable per unit of measure single monetary area (variable measure trade item)” AI (395n) is recommended instead.
3.9.6 Identification of an individual trade item piece (ITIP): AI (8006)
The GS1 Application Identifier (8006) indicates that the GS1 Application Identifier data field contains the identification of an individual piece of a trade item. The piece is not traded independently and therefore cannot be assigned its own GTIN.
The GTIN that is included in this element string is the GTIN for the complete trade item. The piece number identifies an individual piece of the trade item. The total count provides the total number of individual pieces of the trade item.
| GS1 Application Identifier | Global Trade Item Number (GTIN) | Piece number | Total count |
|---|---|---|---|
| 8 0 0 6 | N1 N2 N3 ................. N12 N13 N14 | N15 N16 | N17 N18 |
The data transmitted from the barcode reader means that the element string denoting the identification of an individual piece of a trade item has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ITIP Note: ITIP is the preferred data title for AI (8006) and GCTIN was deprecated from use as of January 2020.
3.9.7 International Bank Account Number (IBAN): AI (8007)
The GS1 Application Identifier (8007) indicates that the GS1 Application Identifier data field contains the international bank account identifier. The International Bank Account Number (IBAN), AI (8007), defined as ISO 13616, indicates to which account the amount of the respective payment slip is to be transferred (see section 2.6.6).
The invoicing party determines the applicable bank account number. The data field is alphanumeric and may contain all characters contained in Table 7-20.
| GS1 Application Identifier | International Bank Account Number |
|---|---|
| 8 0 0 7 | X────────variable length────────›X34 |
The data string transmitted by the barcode reader means that the element string denoting an IBAN has been captured. Restrictions apply to the use of AI (8007) in combination with other AIs, see section 4.13 Data relationships. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: IBAN
3.9.8 Date and time of production: AI (8008)
The GS1 Application Identifier (8008) indicates that the GS1 Application Identifier data fields contain a date and time of production (or assembly). The date and time of production is determined by the manufacturer. The date and time may refer to the trade item itself or to the items contained. The structure is:
Year: the tens and units of the year (e.g., 2000 = 00), which is mandatory.
-
Month: the number of the month (e.g., January = 01), which is mandatory.
-
Day: the number of the day of the relevant month (e.g., second day = 02), which is mandatory.
-
Hour: the number of the hour based on local time (e.g., 2 p.m. = 14), which is mandatory.
-
Minutes: may be dropped if not required.
-
Seconds: may be dropped if not required.
-
Note: This element string can only specify dates ranging from 49 years in the past to 50 years in the future. Determination of the correct century is explained in section 7.12.
| GS1 Application Identifier | Date and time of production | |||||
|---|---|---|---|---|---|---|
| YY | MM | DD | HH | MM | SS | |
| 8 0 0 8 | N1 N2 | N3 N4 | N5 N6 | N7 N8 | N9 N10 | N11 N12 |
The data transmitted from the barcode reader means that the element string denoting a date and time of production has been captured. As this element string is an attribute of a trade item, it must be processed together with the GTIN of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PROD TIME
3.9.9 Optically readable sensor indicator: AI (8009)
The GS1 Application Identifier (8009) indicates that the GS1 Application Identifier data field contains the optically readable sensor instruction parameters defined by AIM (Association for Automatic Identification and Mobility). The parameter field is alphanumeric and may contain all characters contained in Table 7-20. Refer to AIM, Inc. www.aimglobal.org for the sensor instruction parameters to be encoded.
| GS1 Application Identifier | AIM defined sensor instruction parameters |
|---|---|
| 8 0 0 9 | X────────variable length────────›X50 |
Note: This data element is intended to be carrier agnostic, however the user is cautioned regarding payload limitations of GS1 data carriers e.g., GS1-128 (48 total characters) The data transmitted by the barcode reader means that the element string denoting the parameters of a sensor/monitor has been captured. As this element string is an attribute of a trade item or a logistic unit, it must be processed together with the GTIN of the trade item or the SSCC of the logistic unit to which it relates (see section 4.13 Data relationships).
Note: This element string may appear in a separate barcode (from the one used to encode the GTIN or SSCC). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: OPTSEN
3.9.10 Component/Part Identifier (CPID): AI (8010)
The GS1 Application Identifier (8010) indicates that the GS1 Application Identifier data field contains the C/P Identifier. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the C/P Identifier, making the number unique worldwide.
The structure and content of the C/P reference is at the discretion of the company that has been assigned the GS1 Company Prefix to uniquely identify each C/P. The C/P reference format is variable length. The Component & Part reference SHALL only consist of numeric, alphabetic upper-case or special characters “#”, “-“, or “/”, see Table 7-21.
| GS1 | Component/Part Identifier | |
|---|---|---|
| Application Identifier | GS1 Company Prefix ─────────────────› | C/P reference number |
| ─────────────────────────› | ||
| 8 0 1 0 | N1 ... Nj Xj+1 ...variable length Xk (k<=30) |
The data transmitted from the barcode reader means that the element string denoting a C/P Identifier has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CPID
3.9.11 Component/Part Identifier serial number: AI (8011)
The GS1 Application Identifier (8011) indicates that the GS1 Application Identifier data field contains a C/P serial number. A C/P serial number is assigned to an entity for its lifetime. When combined with a C/P Identifier, a serial number uniquely identifies an individual item. The C/P serial number field is numeric only. The C/P Identifier issuer (e.g., C/P buyer or OEM) determines the C/P serial number.
The C/P serial number SHALL NOT begin with a "0" digit, unless the entire serial number consists of the single digit "0".
| GS1 Application Identifier | Component/Part Identifier serial number |
|---|---|
| 8 0 1 1 | N1 ───variable length────› N12 |
The data transmitted from the barcode reader means that the element string denoting a C/P serial number has been captured. As this element string is an attribute of a component/part, it must be processed together with the C/P Identifier of the component/part to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: CPID SERIAL
3.9.12 Software version: AI (8012)
The GS1 Application Identifier (8012) indicates that the GS1 Application Identifier data field contains a software version number. Software versioning is the process of assigning unique version numbers to unique states of computer software.
Examples include: Software versions for regulated healthcare device software.
-
Commercially available office productivity software (Microsoft® Word 2013 version
-
15.0.4701.1001, Adobe® Reader® XI version 11.0.10).
This AI may be combined with AI 10 (lot/batch) when the manufacturer decides that both lot and version control are required to meet regulatory or commercial requirements. The data is alphanumeric and may include all characters contained in Table 7-20.
| GS1 Application Identifier | Software version |
|---|---|
| 8 0 1 2 | X1 ───variable length────› X20 |
The data transmitted by the barcode reader means that the element string denoting a software version has been captured. As this element string is an attribute of a software trade item, it must be processed with the GTIN of the software to which it is related (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a label, the following data title SHOULD be used: VERSION
3.9.13 Global Model Number (GMN): AI (8013)
The GS1 Application Identifier (8013) indicates that the GS1 Application Identifier data field contains a GMN (Global Model Number). The GMN is used for the unique identification of a product model.
Note: This element string SHALL NOT be used to identify the entity as a trade item. The GS1 Company Prefix (see section 1.2.3.3) is allocated by GS1 Member Organisations to the brand owner that allocates the GMN. It makes the number unique worldwide.
The structure and content of the model reference is at the discretion of the brand owner. It may contain all characters listed in Table 7-20. The check character pair is explained in section 7.9.5. Its verification, which must be carried out in the application software, ensures that the identifier is correctly composed.
The total length of the GMN including the check characters SHALL NOT exceed 25 characters.
| GS1 | Global Model Number (GMN) | ||
|---|---|---|---|
| Application Identifier | GS1 Company Prefix ───────────────› | Model reference | Check |
| ───────────────────────────› | characters | ||
| 8 0 1 3 | N1 ... Ni Xi+1 ... variable length Xj (j<=23) | Xj+1 Xj+2 |
When indicating this element string in the non-HRI text section, the following data title SHOULD be used: GMN Regulated healthcare medical devices For regulated healthcare medical devices, the GMN SHALL NOT be used in any labelling, physical marking, or GS1 AIDC data carrier on associated trade items.
When indicating the Basic UDI-DI (GMN) on documents or certificates, the following data title SHOULD be used: GMN The Application Identifier (AI) 8013 SHALL be excluded in such documents and certificates.
For medical devices that fall under the EU regulations (see section 2.6.13).
3.9.14 Highly Individualised Device Registration Identifier (HIDRI): AI (8014)
The GS1 Application Identifier (8014) indicates that the GS1 Application Identifier data field contains the Highly Individualised Device Registration Identifier (HIDRI) but are currently identified with a made-to-stock GTIN for other business purposes. It is used for the unique identification of a family of standard contact lenses that will be registered in EUDAMED (European database on medical devices).
The structure and content of the grouping reference are at the discretion of the brand owner. It may contain all characters listed in Table 7-20. The check character pair is explained in section 7.9.5. Its verification, which must be carried out in the application software, ensures that the identifier is correctly composed.
As the Highly Individualised Device Registration Identifier (HIDRI) is stored within the UDI-DI field within EUDAMED, this element string SHALL contain at least one non-numeric character within the “grouping reference” data structure to ensure against any potential conflict with existing GTINs.
| GS1 | Highly Individualised Device Registration Identifier (HIDRI) | ||
|---|---|---|---|
| Application Identifier | GS1 Company Prefix ───────────────› | Grouping reference | Check |
| ───────────────────────────› | characters | ||
| 8 0 1 4 | N1 ... Ni Xi+1 ... variable length Xj (j<=23) | Xj+1 Xj+2 |
When indicating this element string in the non-HRI text section, the following data title SHOULD be used: MUDI Note: This element string SHALL never be used to identify the entity as a trade item. The GS1 Company Prefix (see section 1.2.3.3) is allocated by GS1 Member Organisations to the brand owner that allocates the MUDI-DI. It makes the number unique worldwide. The MUDI- DI can be used in any labelling, physical marking, or GS1 AIDC data carrier on associated trade items. For the purpose of EUDAMED access, HIDRI is sufficient as a standalone key.
When used in a barcode with production identifiers (e.g., lot number, serial number), HIDRI shall be associated with GTIN as the Application Identifiers for production identifiers have a mandatory association with GTIN Note: This element string can be up to 25 characters in length and can go as low as 8 to 15 characters and shall include the GS1 Company Prefix, at least one non-numeric character as the grouping reference, and the check character pair.
3.9.15 Global Service Relation Number (GSRN): AIs (8017, 8018)
The GS1 Application Identifiers (8017, 8018) indicate that the GS1 Application Identifier data field contains a GSRN (Global Service Relation Number). The GSRN is used to identify either the recipient or individual provider of services in the context of a service relationship. In order to provide identification for both roles in a service relationship, recipient and provider, two GSRN AIs are available. The resultant element string provides a means for the service provider to store data relevant to services provided to the recipient and by the individual provider.
The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GSRN – here the organisation offering the service (see section 1.2.3.3). It makes the number unique worldwide.
The structure and content of the service reference is at the discretion of the organisation offering the service in order to uniquely identify each service relation. The check digit is explained in section 7.9. Its verification, which must be carried out in the application software, ensures that the number is correctly composed.
The Global Service Relation Number – Provider (see figure below) identifies the relationship between an organisation offering services and the provider of services.
| GS1 | Global Service Relation Number (GSRN) - PROVIDER | ||
|---|---|---|---|
| Application Identifier | GS1 Company Prefix | Service reference | Check |
| ──────────────────› | ‹─────────────────────────── | digit | |
| 8 0 1 7 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 | N18 |
The data transmitted from the barcode reader means that the element string denoting the Global Service Relation Number for the Provider has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GSRN – PROVIDER The Global Service Relation Number – Recipient identifies the relationship between an organisation offering services and the recipient of services.
| GS1 | Global Service Relation Number (GSRN) - RECIPIENT | ||
|---|---|---|---|
| Application Identifier | GS1 Company Prefix | Service reference | Check |
| ──────────────────› | ‹─────────────────────────── | digit | |
| 8 0 1 8 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 | N18 |
The data transmitted from the barcode reader means that the element string denoting Global Service Relation Number for the Recipient has been captured. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: GSRN - RECIPIENT Note: AI (8017) and AI (8018) must not be used in combination, see section 4.13 Data relationships.
3.9.16 Service Relation Instance Number (SRIN): AI (8019)
The GS1 Application Identifier (8019) indicates that the GS1 Application Identifier data field contains a Service Relation Instance Number (SRIN). The SRIN is used when the Global Service Relation Number (GSRN) of a service provider (8017) or service recipient (8018) needs to be further qualified with a sequence indicator corresponding to an encounter or an instance of a service.
The structure and content of the Service Relation Instance Number is at the discretion of the organisation offering the service, in order to uniquely identify each service relation instance.
| GS1 Application Identifier | Service Relation Instance Number |
|---|---|
| 8 0 1 9 | N1 ───variable length───› N10 |
The data transmitted from the barcode reader means that the element string denoting a Service Relation Instance Number has been captured. Since the SRIN is an attribute of a service relation, it must be processed with the GSRN of the service relation to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: SRIN
3.9.17 Payment slip reference number: AI (8020)
The GS1 Application Identifier (8020) indicates that the GS1 Application Identifier data field contains a payment slip reference number. The payment slip reference number, assigned by the invoicing party, identifies a payment slip within a given Global Location Number (GLN) of an invoicing party (see section 2.6.6). Together with the GLN of the invoicing party, the payment slip reference number uniquely identifies a payment slip.
The data field is alphanumeric and may contain all characters contained in Table 7-20
| GS1 Application Identifier | Payment slip reference number |
|---|---|
| 8 0 2 0 | X1────variable length─────› X25 |
The data string transmitted from the barcode reader means that the element string denoting a payment slip reference number has been captured. Restrictions apply to the use of AI (8020) in combination with other AIs, see section 4.13 Data relationships.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: REF No.
3.9.18 Identification of pieces of a trade item (ITIP) contained in a logistic unit: AI
(8026) The GS1 Application Identifier (8026) indicates that the GS1 Application Identifier data field includes the ITIP of the contained pieces of a trade item. The ITIP is used to identify a piece of a trade item.
The GTIN that is included in this element string is the GTIN for the complete trade item. The piece number identifies a piece of the trade item. The total count provides the total number of pieces of the trade item.
| GS1 Application Identifier | Global Trade Item Number (GTIN) | Piece number | Total count |
|---|---|---|---|
| 8 0 2 6 | N1 N2 N3 ................. N12 N13 N14 | N15 N16 | N17 N18 |
Note: This element string SHALL be used only on a logistic unit if: the logistic unit is not itself a trade item; and
-
all the pieces of the trade item that are contained have the same ITIP.
-
The data transmitted from the barcode reader means that the element string denoting the ITIP of the trade item piece contained in a logistic unit has been captured. This element string must be processed together with the count of items which must appear on the same unit (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ITIP CONTENT
3.9.19 Digital Signature (DigSig): AI (8030)
The GS1 Application Identifier (8030) indicates that the GS1 Application Identifier data field is a Digital Signature (DigSig) that is in conformance with ISO/IEC 20248 Information technology — Automatic identification and data capture techniques — Digital signature data structure schema - https://www.iso.org/standard/81314.html. The DigSig data field SHALL only consist of alphanumeric characters from the file-safe/URI-safe base64 character set (a 64-character subset of ISO/IEC 646
Table 1) as defined in section 5 of RFC 4648, see Table 7-22.
| GS1 | Digital Signature (DigSig) |
|---|---|
| Application | |
| Identifier | |
| 8 0 3 0 | Z1 ───────────── variable length─────────────› Z90 |
The data transmitted from the barcode reader means that the element string denoting a Digital Signature (DigSig) has been captured. As this element string is an attribute of a trade item, asset, coupon, document, component, service relationship or logistic unit, it must be processed together with the identifier of the physical object to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: DIGSIG
3.9.20 International Mobile Equipment Identity (IMEI): AI (8040)
The Global System for Mobile Communications Association (GSMA) allocates IMEI numbers for device identification. The IMEI (International Mobile Equipment Identity) uniquely identifies the physical mobile device for connecting to and communicating with networks around the world. The numbers are placed in a database regulated by the GSM (Global System for Mobile Communications); this is how the devices are identified by networks to connect to and use them.
See GSMA for detailed information on this numbering scheme and how to get a code.
| GS1 Application Identifier | IMEI Number |
|---|---|
| 8 0 4 0 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 |
The data transmitted from the barcode reader means that the element string denoting an IMEI number has been captured. As this element string is an attribute of a specific trade item, it must be processed together with the GTIN and the serial number of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: IMEI
3.9.21 International Mobile Equipment Identity 2 (IMEI2): AI (8041)
The GSMA allocates IMEI numbers for device identification. See GSMA for detailed information on this numbering scheme and how to get a code. In cases when a device requires a second IMEI number, this GS1 Application Identifier is used in addition to AI (8040).
| GS1 Application Identifier | IMEI2 Number |
|---|---|
| 8 0 4 1 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 |
The data transmitted from the barcode reader means that the element string denoting a second IMEI number has been captured. As this element string is an attribute of a specific trade item, it must be processed together with the GTIN, the serial number and the IMEI of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: IMEI2
3.9.22 Embedded SIM number: AI (8042)
An embedded subscriber identity module (eSIM) number is a 32-digit number that identifies a digital SIM of a device. The GSMA assigns the first 5 digits, and a manufacturer allocates the remaining 27 digits of the number to identify the eSIM within a device. For more information on the structure of an eSIM number see ISO/IEC 7812-1 Identification cards – Identification of issuers.
| GS1 Application Identifier | Digital SIM Number |
|---|---|
| 8 0 4 2 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 N18 N19 N20 N21 N22 N23 N24 N25 N26 N27 N28 N29 N30 N31 N32 |
The data transmitted from the barcode reader means that the element string denoting a digital SIM number has been captured. As this element string is an attribute of a specific trade item, it must be processed together with the GTIN, the serial number and the IMEI of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: ESIM
3.9.23 Physical SIM Number: AI (8043)
A physical subscriber identity module (SIM) number identifies a physical SIM of a device. It is an 18 to 20 digit number allocated by the manufacturer to identify the physical SIM inserted/added into a device. For more information on the structure of an physical SIM number see ISO/IEC 7812-1 Identification cards – Identification of issuers and the ITU-T E.164 International Shared Country Codes.
| GS1 Application | Physical SIM Number | |
|---|---|---|
| Identifier | Required digits | Optional |
| Digits | ||
| 8 0 4 3 | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 N18 | N1..N2 |
The data transmitted from the barcode reader means that the element string denoting a physical SIM number has been captured. As this element string is an attribute of a specific trade item, it must be processed together with the GTIN, the serial number and the IMEI of the trade item to which it relates (see section 4.13 Data relationships). When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PSIM
3.9.24 Coupon code identification for use in North America: AI (8110)
See GS1 US for the North American Coupon Application Guideline using GS1 DataBar Expanded Symbols for detailed information on GS1 US coupon code data content. The coupon barcode is constructed by starting with a coupon GS1 Application Identifier (8110), followed by the required and optional data elements, until all desired data is encoded (or the limit of 70 digits is reached).
| GS1 Application Identifier | Formatted according to rules of North American Coupon Application Guideline using GS1 DataBar Expanded Symbols |
|---|---|
| 8 1 1 0 | X1 ────variable length──────›X70 |
The data string transmitted from the barcode reader means that the element string denoting a Coupon code for use in North America has been captured.
3.9.25 Loyalty points of a coupon: AI (8111)
The GS1 Application Identifier (8111) indicates that the GS1 Application Identifier data field contains the loyalty points of a coupon.
| GS1 Application Identifier | Loyalty points of a coupon |
|---|---|
| 8 1 1 1 | N1 N2 N3 N4 |
The data string transmitted from the barcode reader means that the element string denoting the loyalty points of a coupon has been captured. This element string must be processed together with the Global Coupon Number, AI (255) of the coupon to which it relates (see section 4.13 Data relationships).
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: POINTS
3.9.26 Positive offer file coupon code identification for use in North America: AI (8112)
See GS1 US for the North American coupon application guidelines for detailed information on GS1 US coupon code data content. The positive offer file coupon data string is constructed by starting with a coupon GS1 Application Identifier (8112), followed by the required and optional data elements, until all desired data is encoded (or the limit of 70 characters is reached).
| GS1 Application Identifier | Formatted according to rules of North American coupon application guidelines |
|---|---|
| 8 1 1 2 | X1 ────variable length──────›X70 |
The data string transmitted means that the element string denoting a positive offer file coupon code for use in North America has been captured.
3.9.27 Extended packaging URL: AI (8200)
The GS1 Application Identifier (8200) indicates that the GS1 Application Identifier data fields contain the identification of a brand owner authorised URL to be used in mandatory association with GTIN AI (01) encoded in one symbol.
| GS1 Application | Brand owner authorised URL |
|---|---|
| Identifier | |
| 8 2 0 0 | X1──────variable length───────›X70 |
The data transmitted from the barcode reader means that the element string denoting the Extended Packaging URL for a trade item has been captured. This element string SHALL be processed as specified in section 2.1.13 to obtain one URL address associated with the trade item identified by the GTIN.
When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: PRODUCT URL
3.10 GS1 Application Identifiers starting with digit 9
3.10.1 Information mutually agreed between trading partners: AI (90)
The GS1 Application Identifier (90) indicates that the GS1 Application Identifier data field contains any information mutually agreed between trading partners. The data field shows the information agreed between the two trading partners. The field is alphanumeric and may contain all characters contained in Table 7-20. It may also be used to incorporate data preceded by ASC MH10 Data Identifiers.
| GS1 Application | Data field |
|---|---|
| Identifier | |
| 9 0 | X1────variable length────›X30 |
The data transmitted from the barcode reader means that the element string denoting mutually agreed information has been captured. As this element string may contain any information, processing is subject to prior agreement between trading partners.
Important: The barcode carrying this element string SHOULD be removed from any item that leaves the jurisdiction of the trading partners. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: INTERNAL
3.10.2 Company internal information: AIs (91 - 99)
The GS1 Application Identifier (A1 A2) assigned to company internal information is AI (91 to 99). The GS1 Application Identifier data field may contain any company internal information. The field is alphanumeric and may show all characters contained in Table 7-20.
| GS1 Application Identifier | Data field |
|---|---|
| A1 A2 | X1 ────variable length────› X90 |
Note: Use of this Application Identifier for field lengths greater than 41 data characters will require the appropriate data carrier selection, see section 2.6.10. The data transmitted from the barcode reader means that the element string denoting company internal information has been captured. Processing of this element string is to be organised by the using company.
Important: This element string SHOULD be removed from any item that leaves the jurisdiction of the company. When indicating this element string in the non-HRI text section of a barcode label, the following data title SHOULD be used: INTERNAL
3.11 Compatibility of EPC Tag Data Standard and GS1 General Specifications
The GS1 Application Identifiers, defined in this section of the GS1 General Specifications, may be used in GS1 barcodes in line with the application standards outlined in section 2. GS1 Application Identifiers may also be used in EPC/RFID tags as defined in the latest version of the GS1 EPC Tag Data Standard (TDS).
Note: Some EPC Binary Coding Schemes are unable to encode the full serial number values defined in section 3. See Table 12-2 of the GS1 EPC Tag Data Standard (TDS) for limitations imposed on serial numbers within the EPC Binary Coding Schemes.