4 Application rules and management practices

4.1 Introduction

The main purpose of Automatic Data Capture (ADC) is to replace manual entry of information. This implies that an ADC message must provide all information required for a transaction without human intervention. GS1 system data may be used, for example, to record entities in computer files, to sort goods on conveyor belts, to check completeness of a consignment, to verify dates and to record physical stock taking.

Element strings may be applied directly on physical goods or printed in catalogues or documents. The scanning source and the type of transaction determine the required information in a given business application. Since all ADC data is being used in data sharing applications, strict validation of data to be processed is an absolute prerequisite.

For correct processing of scanned data, certain business applications may require the association of element strings representing a particular combination of identification data. The GS1 system enables users to achieve the needed level of data accuracy through the use of adequate element strings.

The logical set up of the data standard of the GS1 system enables system users to validate scanned data messages (see section 7). Validation is affected on two levels. The first is validation of the data for conformity with system rules (e.g., to provide a message that contains all information to be processed logically without human intervention). The second level is validation of the data for conformity with the requirements of a particular business application.

Sections 4.13 shows the rules for the first verification level (e.g., validate data to conform with the system logic). Section 4.13.1 defines the pairs of element strings that cannot appear on the same physical entity. Section 4.13.2 defines the element strings that mandate the appearance of another element string on the same physical entity. All other combinations of element strings are possible at the first level of verification, although they may not make sense at the second, the application level.

4.2 GTIN rules

4.2.1 Management of uniqueness

Global Trade Item Numbers (GTINs) must be allocated uniquely. GTINs SHOULD NOT contain any intelligence or parsable strings. The embedding of internal codes is discouraged because it is often found that the rules for changing them differ from the rules for changing a GTIN.

For some product types (e.g., healthcare items) it is common for national regulators to require the submission of a product filing from a party based within the jurisdiction of the regulator. Such arrangements have no direct impact on GTIN Management but need to be covered by the normal contractual arrangements (e.g., licenced distributor, subsidiary, reseller).

4.2.2 Allocating the numbers

A Global Trade Item Number (GTIN) is used to identify any trade item (product or service) upon which there is a need to retrieve predefined information and that may be priced or ordered or invoiced at any point in any supply chain. A separate, unique GTIN is required whenever any of the trade item declarations are different in any way that is relevant to the trading process.

The details on when to change a GTIN are included in the Global Trade Item Number (GTIN) Management Standard. This standard is designed to help industry make consistent decisions about the unique identification of trade items in open supply chains. The GTIN Management Standard defines when GTIN changes are needed at the retail consumer trade item level (base unit) as well as on higher level trade items (e.g., case, pallet) that currently exist and are used in distribution processes.

The GTIN Management Standard as well as specific standard rules that apply to upstream, fresh foods, healthcare and other specific sectors can be found at https://www.gs1.org/1/gtinrules/en.

Local, national or regional regulations may require more frequent GTIN changes. Such regulations have precedence over the rules provided within the GTIN Management Standard.

4.2.2.1 GTIN Management definitions

The following terms may be useful when reviewing the GTIN Management Standard that is published on https://www.gs1.org/1/gtinrules/en: Logistic unit – An item of any composition established for transport and/or storage that needs

• to be managed through the supply chain. It is identified with an SSCC (Serial Shipping Container

Code). Retail consumer trade item – The trade item intended to be sold to the end consumer at

• retail point-of-sale. They are identified with a unique GTIN-13, GTIN-12, or GTIN-8. (See section 2). Retail consumer trade item variant – A change to a retail consumer trade item (which may

• itself be a homogeneous or a physical trade item assortment/bundle of other retail consumer trade items) that does not require a new GTIN, but where identification of the variation may be required. Trade item – Any item (product or service) upon which there is a need to retrieve predefined

• information and that may be priced, ordered, or invoiced at any point in any supply chain.

Trade item grouping – A grouping of retail consumer trade items that is not intended for

• point-of-sale scanning. It is identified with a unique GTIN-14, GTIN-13, or GTIN-12.

Note: The GTIN Management Standard is intended for global use. Exceptions may occur only when local regulatory or legal requirements mandate otherwise. Note: The exchange of product data across global supply chains requires compliance with rules for product identity and data attribution. It is recommended that all retail consumer trade items are registered with GS1. For more information see your GS1 Member Organisation.

4.2.2.2 Trade item declarations

Trade item declarations are the set of all information about a trade item (e.g., manufacturer warranty, ingredients, instructions for use, specifications, contents, certifications). For a trade item, this is all of the information that is on the label and in the original packaging. It also includes relevant aspects of the extended packaging.

Although this list is not exhaustive, the basic trade items declarations are: The primary brand or, as may be defined by regulation, the product name and/or product

• description.

The trade item type and variety.

• The net content of trade item and/or net weight, volume, or other dimension impacting trade.

• If the trade item presents a grouping, the number of elementary items contained and their

• subdivision in sub-packaging units.

For a predefined trade item assortment/bundle, the composition of the trade item

• assortment/bundle.

A modification to any of the basic elements that characterise a trade item will usually lead to a change in the Global Trade Item Number (GTIN). Note: These rules are intended for global use. Exceptions may occur only when local regulatory or legal requirements mandate otherwise. For example, in some industries, such as healthcare, regulations or other requirements may dictate that any trade item changes require a new GTIN.

Note: If a party adapts, refurbishes, or modifies trade items see section 2.1.15 for information on identifying non-new trade items. Note: For complex products, such as some medical devices, key consideration for GTIN allocation is the commercialisation of the product (e.g., different for pricing or ordering or invoicing). If the product is ‘different’ a ‘different GTIN’ is required. Figure 4-1 is a scenario to represent the difficulties in determining when a GTIN change is necessary for complex medical devices, depending upon how the device is viewed (i.e., from a commercial and/or form, fit, function perspective). Nominally the commercial aspects of an item determine a GTIN change, the objective is to recognise that other important factors reside which may not necessarily signify a commercialisation shift, but would impact the GTIN assignment – particularly in the healthcare industry. It is the brand owner’s responsibility to manage appropriately the configuration of any complex device and its appropriate GTIN(s) assignment. The example shows major hardware components managed by GTIN and serial number combinations, recognising that within this complex medical device there are other potential parameters where configuration change must be managed; GTIN change may be dictated based on the manufacturers change management process. It is the brand owner that decides upon the identification requirement.

Figure 4-1 Example of the complexity of a medical device product with regard to GTIN allocation

4.2.2.3 Trade item variants

4.2.2.3.1 Consumer product variants

Per brand owner discretion, a consumer product variant (CPV) if used, SHALL be used with GTIN on retail consumer trade items in the following conditions: 1. A CPV may be assigned by the brand owner to a variation of a retail consumer trade item, which SHALL NOT require a new GTIN per the GTIN Management Standard, but where communication regarding the variation may be required.

2. Each retail consumer trade item variation SHALL NOT have more than one CPV value. 3. CPV may be assigned to retail consumer trade items that contain a homogeneous quantity or predefined assortment of retail consumer trade items.

3. When a retail consumer trade item is offered in different quantities (e.g., unit, six pack, 12 pack) the various packages for these quantities are each identified with a unique GTIN. Those packages may also each include a unique CPV and the actual data value for the CPV may or may not be the same between the various packages.

4. The CPV of a retail consumer trade item that contains a homogeneous quantity or predefined assortment of retail consumer trade items may change independently from the CPV of the contained retail consumer trade items, but shall change if the CPV of any of the contained retail consumer trade item changes.

4.2.2.3.2 Minor trade item variants for trade item groupings

For trade item groupings containing units that are themselves minor trade item variants of trade items whose GTINs remain unchanged, the rule is the following: If the identification of minor trade item variants is only relevant to the manufacturer, they

• SHOULD distinguish these variants by using the element string internal product variant, AI (20).

Examples include an identical product made in two separate locations or the same product with a minor package design change.

4.2.3 Responsibility for allocating the Global Trade Item Number

The established terminology of the GS1 system may not be familiar to all industries that use the GS1 system. As of release 23 of the GS1 General Specifications, a broader terminology framework is used to enable industry to consistently and accurately identify the party that has the responsibility to allocate/assign the GTIN.

Note: The term GTIN allocator is used to broadly and consistently refer to the party responsible for allocation of GTINs to trade items (defined in 4.2.3.1). This term is harmonised with the historical use of the term brand owner below.

There are foundational rules for the assignment of GTINs to trade items that apply in all scenarios: A trade item SHALL be assigned a GTIN before there is an offer made for sale of the trade item.

• GTIN is to be assigned at the earliest point in any trade item’s lifecycle after which a GTIN

• allocator has been established.

No downstream party (e.g., distributor, wholesaler, importer, merchant) may assign a different

• GTIN to a trade item that already has a GTIN, provided that the trade item is not changed in a way that would require a new GTIN as per GS1 standards (see GTIN Management Standard). When a GTIN is assigned to a trade item by a downstream party, the same GTIN may not be

• assigned to any trade item by any other party.

4.2.3.1 Responsibility for branded items

Allocation of a GTIN to a trade item is the responsibility of the party that warrants the trade item declarations, known as the GTIN allocator (see 4.2.2.2 for more on trade item declarations).

Prior to release 23 of the GS1 General Specifications, the party responsible for allocation of a GTIN to a trade item was referred to as the “brand owner”. In industries where the term “brand owner” is relevant and familiar, this term SHALL be considered as equivalent to the term GTIN allocator.

For branded items, the brand owner is the GTIN allocator, since the brand owner is the party that owns the specifications of the trade item, and, therefore is the party that warrants the trade item declarations.

There are situations when the GTIN allocator is: The manufacturer or supplier: The party that manufactures the trade item or has it

• manufactured, in any country.

The importer or wholesaler: The party that sells the trade item under its own brand name or the

• importer or wholesaler that changes the trade item (for example by modifying the packaging of the trade item). The retailer: The retailer that sells the trade item under its own brand name.

• Any party that chooses to take responsibility for the trade item declarations of a trade item that

• has not yet been assigned a GTIN and, in doing so, sells it under their own brand name.

In all cases, the party who warrants the trade item declarations is the party who SHALL assign the GTIN to a trade item. With that action, the party becomes the GTIN allocator. Note: A GTIN allocator is licenced a GS1 Company Prefix and/or individual GS1 identification keys by a GS1 Member Organisation. GS1 Company Prefixes and individual GS1 identification keys are allocated by the company to which they are assigned.

4.2.3.2 Unique scenarios

There are some unique scenarios to the rules regarding responsibility for GTIN allocation described section 4.2.3.1: Non-branded items: The GTIN allocator for trade items without a brand name and generic

• items (not private labels) SHOULD be the manufacturer of the non-branded item. Different manufacturers and/or suppliers may supply non-branded items that are similar or identical to a buyer (who could be a customer, a merchant or a manufacturer). Companies that trade in these items need to organise their computer applications (e.g., replenishment programs) to cope with this eventuality. If a brand is applied to a non-branded item, the GTIN Management Standard SHOULD be consulted for GTIN management rules.

Customer specific items: If a trade item is made specifically for one trade customer and is

• orderable only by this customer, then the customer SHOULD be the GTIN allocator. The GTIN

SHOULD be created from the customer’s GS1 Company Prefix or SHOULD be an individual GTIN identification key from the customer (see section 1.2.3.3). If the supplier (merchant) sells a trade item to more than one customer, then the merchant SHALL be the GTIN allocator.

Contracted parties: If a party is contracted to act on behalf of, or to represent, a GTIN

• allocator, a trade item created by the contracted party for the GTIN allocator SHALL be assigned a GTIN from the GTIN allocator’s licenced GS1 Company Prefix or individual GS1 keys. In such situations, it is critical to ensure that such contracts include language that ensures all allocated GTINs are properly registered and managed by the GTIN allocator.

Other exceptions: If a trade item does not have a GTIN, a downstream party may choose to

• take responsibility for the trade item declarations and become the GTIN allocator for the trade item subject to compliance with any relevant laws. Alternatively, a downstream party can assign an internal number (e.g., RCN) to a trade item that does not have a GTIN assigned to it, but only if the trade item is restricted for use within its own stores/platform.

4.2.4 Sector-specific rules

4.2.4.1 GTIN allocation rules for healthcare

Specific rules that apply to healthcare trade items can be found in the GS1 Healthcare GTIN Allocation Rules Standard.

4.2.4.2 GTIN allocation rules for upstream suppliers

Specific rules that apply to packaging and raw material trade items supplied to manufacturing companies can be found on https://www.gs1.org/1/gtinrules/en/tree/29/upstream. Upstream suppliers are those companies that typically supply or manufacture trade items that are supplied to other companies for further processing. Examples of these trade items include raw ingredient and packaging materials.

A Global Trade Item Number (GTIN) must be assigned to each predefined trade item and any unit of measure used in the price, order, or invoice process. Note: These rules are intended for global use. Exceptions may occur only when local regulatory or legal requirements mandate otherwise.

4.2.4.3 GTIN allocation considerations for apparel and home fashion

The GSMP General Merchandise Work Team validated the original Global Trade Item Number (GTIN) allocation rules and concluded that they are applicable to the apparel and home fashions product category. The content of this section extends the content in section 4.2 to cover scenarios specific to apparel and home fashions and may be different in other sectors. This section is the result of the review of the Trade Item Identification and Communication Guidelines (VICS EDI) TIIC, May 2001, by the GSMP Work Team.

4.2.4.3.1 Pre-pack/multi-pack/set-pack

For a pre-pack or assortment of trade items, each different item within the pre-pack will be assigned a GTIN maintaining the one-to-one relationship between trade item/colour ID/size ID and GTIN.

Each GTIN must be marked so as to enable scanning at the point-of-sale. A separate, unique GTIN is assigned to each orderable pre-pack. This GTIN is not intended to be scanned at the retail point- of-sale. Different pre-packs of trade items are assigned different GTINs when either the component item or quantity contents of the pre-packs are different.

A multi-pack is a group of trade items (the same or different) that are intended to be sold as a single consumer unit at the point-of-sale (e.g., a three-pack of men's white T-shirts or a 12-piece set of glassware). A multi-pack is not intended to be broken apart and sold as individual trade items. A multi-pack is assigned a GTIN that is different from the GTIN that may be assigned to the individual trade items. Generally, components of a multi-pack are not marked with individual GTINs.

Each different multi-pack of the same trade items (e.g., three-pack socks versus six-pack socks) must have a different GTIN assigned. Each different multi-pack GTIN must also have its own trade item/colour ID/size ID.

For a set-pack, each different trade item within the set-pack will be assigned a GTIN, maintaining the one-to-one relationship between trade item/colour ID/size ID and the GTIN. The individual trade item GTIN must be marked to enable retail point-of-sale scanning and may or may not be orderable separately outside the set-pack(s). A separate, unique GTIN is assigned to each set-pack. Different set-packs are assigned different GTINs when either the trade item or quantity contents are different.

Table 4-1 provides a summary of the requirements.

Table 4-1 Requirements by pack type

Pack	Individual items of the pack
Orderable by retailer	Sellable to consumer	GTIN marked	GTIN marked	Orderable by retailer	Orderable	Sellable	GTIN marked	GTIN marked
by retailer	to
consumer
Pre-pack	Yes	No	Yes	Maybe	Yes	Yes
Multi-pack	Yes	Yes	Yes	No	No	No
Set-pack	Yes	Yes	Yes	Maybe	Yes	Yes

Note: GTINs on individual trade items in a multi-pack are optional. Note: GTINs on individual trade items in a set-pack are required because the individual pieces are available for sale to the consumer.

Note: Individual components of pre-packs and set-packs may be ordered separately based on individual partnership agreement.

4.2.4.3.2 Gift with purchase/purchase with purchase/collateral item

A gift with purchase is a trade item given to a consumer as part of a promotional event, contingent on the consumer making a purchase of another item or items. A gift with purchase is considered inventory and has no retail value.

A purchase with purchase is a trade item sold to a consumer at a special price as part of a promotional event, contingent on the consumer purchasing another item or items. A purchase with purchase is considered inventory and has a retail value. When assigning and tracking Global Trade Item Numbers (GTINs) for gift with purchase and purchase with purchase trade items, GTINs SHOULD be assigned to all gift with purchase and purchase with purchase items and be marked with a GTIN to enable point-of-sale scanning.

A collateral item is a trade item delivered from a manufacturer to the retail selling floor that is not considered inventory and has no retail value (e.g., a display case that needs to be identified but has no retail value). GTINs SHOULD be assigned to all collateral items.

4.2.4.4 GTIN allocation considerations for direct marking

The master data linked to the GTIN marked on the item (see section 2.6.14) will generally apply for the item at time of production and first purchase. The master data will no longer apply when changes are made to the trade item (refurbishment, upgrade, memory extension, etc.). When such changes are made the GTIN as marked on the item MAY remain the same, and companies will need to ensure that it is clear to all parties which master data may change over time.

4.2.5 GTIN non-reuse

An allocated GTIN SHALL NOT be reallocated to another trade item. The only exceptions are: The GTIN may be deleted from all catalogues without first being marked as withdrawn or

• discontinued and may be reused 12 months after it is deleted or after it is last shared with a trading partner (whichever is later) if both: the GTIN is published in an externally accessible manner (e.g., to a catalogue or directly to

• a trading partner) with a status that indicates that it is draft, preliminary, investigational, or some equivalent status other than final, withdrawn, discontinued, or deleted; and the trading partners with whom the GTIN is shared agree that it may be reused, either as a

• condition of receiving the data (e.g., the GTIN is sent to the trading partners as part of an investigational product development phase) or after deletion (e.g., all trading partners confirm that the draft, preliminary, or investigational GTIN has not been propagated to a system that would be adversely affected by reuse of the GTIN).

If the GTIN is never published in an externally accessible manner (e.g., to a catalogue or

• directly to a trading partner), it may be reused immediately.

Trade items that have been withdrawn from the market and are reintroduced may use the

• original GTIN if they are reintroduced without any modifications or changes that require a new

GTIN as specified by the GTIN Management Standard. Note: The GTIN non-reuse rule went into effect on 1 January 2019 in response to digital business demand. GTINs discontinued and withdrawn from the market prior to 1 January 2019 may be considered for reuse one final time (*). However, companies are strongly advised to follow the non-reuse rule for all GTINs to avoid risks of conflicting data.

(*) If a GTIN was withdrawn prior to 1 January 2019, the previously applicable rules must be adhered to (see section 4.16.1 Deprecated GTIN reuse rules).

4.2.6 Data alignment

When a new Global Trade Item Number (GTIN) is assigned to a trade item, it is essential that the brand owner provide the detailed information to trading partners about the item's characteristics.

This information should be provided at as soon as possible before the trade item is actually traded. Expediting GTIN information to buyers reduces order exception handling and reduces the lead time in getting goods to the selling floor.

4.2.6.1 Data alignment best practice

A number of actions are vital to ensure that Global Trade Item Numbers (GTINs) are accurately communicated within the supply chain. These ensure that the data associated with any scanned barcode can be associated with accurate, up-to-date data. This is particularly essential for items scanned at the point-of-sale where the absence of accurate data may have legal implications.

The GTIN provides a supply chain solution for the identification of any item that is traded (priced, invoiced, or ordered). Overall supply chain costs are minimised by all partners in the supply chain adhering to identical GTIN Management Standards (see section 4.2.2).

The following best practices are proposed for all items. It has been developed by manufacturers, distributors and retailers to help eliminate any confusion between product identification and product listing in the retailer’s database in the supply chain.

1. GTIN Management and the barcoding of the GTIN are technical processes with rules detailed in these GS1 General Specifications. Product listing is the act of adopting a new product in an assortment by a commercial organisation. Product listing is the result of commercial negotiations between purchaser and seller. For example, GTIN Management should be independent from product listing.

2. For management reasons, or to ensure that correct information is communicated to the final consumer, changes to an item may require a new GTIN. A new GTIN does not automatically imply a new listing. For example, if a change requiring a new GTIN is made to a listed product, this should not automatically imply a new product listing is needed.

GTIN Management and database listing are to be considered as two entirely autonomous decisions: GTIN Management is not an object of negotiation. The brand owner makes available to its client all information regarding the listed items, ideally with an EDI message or in an e-product catalogue, no later than at the time of item listing. In case of time limited promotions or a product evolution, this information will be communicated largely beforehand, thus allowing the retailer to validate this information and to circulate it internally.

4.2.7 GTIN-8 guidelines and packaging size constraints

Before deciding to use a GTIN-8 as opposed to a GTIN-13 or GTIN-12, companies, working jointly with their printer, should consider options such as: Whether the barcode can be reduced in size; e.g., printed at a lower X-dimension, taking into

• account the minimum barcode print quality requirements (see section 5.12).

Whether the label or artwork can reasonably be changed to enable the inclusion of an EAN-13 or

• a UPC-A barcode or a symbol from the GS1 DataBar Retail POS family.

For example, redesigning the label and increasing the label size may be an option, especially

• when the existing label is small in comparison with the pack area.

Whether a truncated barcode can be used.

• Note: A truncated barcode (normal length, but reduced in height) may only be used if there is absolutely no possibility of printing a full size barcode. Truncation removes the omnidirectional scanning capability. A barcode with excessive truncation will not be of any practical use. Users considering this option should consult their customers to see if an acceptable compromise can be reached.

Packaging size constraints The use of a GTIN-8 is authorised when: The total printable area of the product packaging is less than 80 cm², or

• The area of the largest label for the item is less than 40 cm², or

• The product is cylindrical with a diameter less than 30 mm.

• Figure 4-2 GTIN-8 packaging size constraints

4.3 SSCC rules

4.3.1 Allocating Serial Shipping Container Codes

4.3.1.1 General rule

An individual Serial Shipping Container Code (SSCC) is a unique number, which remains the same for the life of the logistic unit to which it is assigned. When assigning an SSCC, the rule is that an individual SSCC number must not be reallocated within one year of the shipment date from the SSCC assignor to a trading partner. However, prevailing regulatory or industry organisation specific requirements may extend this period.

4.3.1.2 Responsibility

The Serial Shipping Container Code (SSCC) provides functionality to support the management (tracking, tracing, storage, etc.) of logistic units through the supply chain. To ensure global uniqueness and traceability, the physical builder of the logistic unit or the brand owner of the logistic unit is responsible for the allocation of the SSCC.

4.3.2 Aggregated/nested logistic units

Logistic units may be aggregated or nested into other logistic units for part of the journey to the final destination. For example, parcels may be combined onto pallets. In that case the SSCC of the higher logistic unit may be used to track and trace the contained logistic units. GS1 EDI and EPCIS support the electronic communication of such aggregations or nestings by enabling to specify links between the child SSCCs and parent SSCC.

When dealing with aggregated/nested logistic units in AIDC applications, the following rules apply to ensure correct identification of the higher logistic unit: Only the barcode of the higher logistic unit SHOULD be readable. The barcodes of the lower

• level logistic units should be obscured or otherwise prevented from being read (e.g., by instructing those scanning through a standard operating procedure). When using EPC/RFID tags, the filter value used for the higher logistic unit SHALL be different

• from the filter value used for the lower logistic units.

Note (informative): See the GS1 Logistics Label Guideline 3 for examples of the way to deal with nested/aggregated logistic units. 3 https://ref.gs1.org/guidelines/logistic-label/

4.4 Rules for GS1 asset identifiers

4.4.1 General rule

4.4.1.1 GS1 asset identifiers

GS1 asset identifiers can be used to identify any fixed assets of a company. It is left to the discretion of the issuer to determine whether the Global Returnable Asset Identifier (GRAI), AI (8003), or Global Individual Asset Identifier (GIAI), AI (8004), is more suitable for the application concerned.

4.4.1.2 Lead time in reusing GS1 asset identifiers

Asset identifiers must not be used for any other purpose and must remain unique for a period well beyond the lifetime of the relevant records. If a company assigns asset identifiers to trade items supplied to its customers, the company must ensure that the asset identifiers are never reused.

All issuers of asset identifiers must ensure that asset identifiers (GRAIs, GIAIs) allocated for medical devices/equipment used for treatment of a patient SHALL NOT be reused. Also, GIAIs that are marked directly on safety critical components and parts, such as used in rail, SHALL NOT be reused.

4.4.1.3 Responsibility

The asset owner or manager is responsible for the issuance and allocation of GS1 asset identifiers. Note: The term ‘asset manager’ includes manufacturers that issue and allocate asset identifiers to be used during the full lifetime of the asset. Furthermore, best practices may dictate that the trade item manufacturer applies the asset identifiers issued by the asset owner or manager during the manufacturing process (see section 2.3).

4.4.2 Allocating Global Returnable Asset Identifiers (GRAIs): AI (8003)

The structure of the element string for a Global Returnable Asset Identifier (GRAI) can include two parts: the mandatory identification of an asset type and an optional serial component, to distinguish individual assets within the same asset type (see section 2.3.1)

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 exact method used to allocate the GRAI is left to the discretion of the issuing organisation. However, a unique number, the asset type, must be assigned for each type of asset being identified, and for ease of administration, the GS1 system recommends that numbers be allocated sequentially and not contain classifying elements.

When it is not possible to assign an asset type (e.g., for museum exhibits), or when the type of asset is not required by the application (e.g., when the item is only used for a single type of asset), then the Global Individual Asset Identifier (GIAI), AI (8004), SHOULD be used.

When using AI (8003), a leading zero SHALL be required before the GRAI.

4.4.2.1 Identical assets identification

A single Global Returnable Asset Identifier (GRAI) SHOULD be assigned to a series of identical assets.

Table 4-2 Examples of GRAI excluding serial component

Asset type	GRAI1
50 litre aluminium beer keg	1234567890005
10 litre aluminium beer keg	1234567890012
10 litre wooden beer keg	1234567890029
Note: (1) The leading zero required before the GRAI when used with AI (8003) is not required when displayed as non-HRI text.

4.4.2.2 Serial component (optional)

The asset owner or manager assigns the optional serial component. It denotes an individual asset within a given asset type. The field is alphanumeric and is used to distinguish individual assets with the same asset types.

Table 4-3 Examples of GRAI including serial component

Asset Type	GRAI (incl. the serial component)1
50 litre aluminium beer keg	12345678900051234AX01
50 litre aluminium beer keg	12345678900051234AX02
50 litre aluminium beer keg	12345678900051234AX03
Note: (1) The leading zero required before the GRAI when used with AI (8003) is not required when displayed as non-HRI text.

4.4.3 Allocating Global Individual Asset Identifiers (GIAIs): AI (8004)

The Global Individual Asset Identifier (GIAI) is structured according to the figure below.

GS1	Global Individual Asset Identifier (GIAI)
Application Identifier	GS1 Company Prefix ───────────────›	Individual asset reference
──────────────────────────────›
8 0 0 4	N1 ... Ni Xi+1 ... variable length Xj (j<=30)

The exact method used to allocate the GIAI is left to the discretion of the issuing organisation. However, each GIAI must be unique for each individual asset being identified and, for ease of administration, the GS1 system recommends that GIAIs be allocated sequentially and not contain classifying elements.

4.4.4 Change of asset ownership

Asset identification numbers are used in a diverse range of business applications ranging from tracking the movements of reusable packaging trays to recording the life cycle history of aircraft parts. If a company sells an asset to another company then the asset identifier SHOULD ideally be replaced by another Global Individual Asset Identifier (GIAI) or Global Returnable Asset Identifier (GRAI) or be removed. It is permissible for the asset identifier to remain on the item when the ownership changes if the new owner takes responsibility for the GS1 Company Prefix associated with the asset identifier, or when the asset identifier was assigned by the manufacturer. For further information regarding changes of ownership, please refer to section 1.5.

4.4.5 Information associated with asset identifiers

The data related to the asset should be recorded and shared digitally using the asset identifier as the key to the information. Examples of the type of information held include the GLN of the party who owns or manages the asset, the value of the asset, the location of the asset and the life cycle history of the asset.

4.5 GLN rules

4.5.1 Allocating Global Location Numbers

4.5.1.1 Allocation general rule

A separate, unique GLN is required to be allocated whenever there is a need to distinguish one party and/or location from another. (e.g., each store location is required to have a separate GLN to identify the physical locations).

GLNs SHALL be allocated by the party that defined the party/location in support of their business operations. The below defines which party is responsible for allocating the GLN to a legal entity, function, physical location, or digital location. If a GLN is used to identify a combination of legal entity, function, physical location and/or digital location, all applicable rules SHALL apply.

Legal entity: Allocating a GLN to a legal entity is the responsibility of the legal entity itself or

• another legal entity that is part of the same organisation. If multiple legal entities within an organisation have licensed GS1 Company Prefixes or individual GLNs, the parties SHOULD coordinate GLN allocation. Function: The organisation identifying their own, internal functions to support their business

• operation is responsible for allocating GLN.

When representing itself as a legal entity or function in transactions, an organisation SHALL only use GLNs for which it has appropriate licences. This means that an organisation SHALL NOT use a GLN from another organisation’s licence to represent itself as a party.

Physical location: The owner or primary user(s) of the physical location is responsible for

• allocating the GLN.

When a party allocates a GLN to a location they do not own, that party SHOULD inform the

• owner and/or primary users of the location.

Parties SHALL use a GLN allocated by their own organisation, the owner of the location, or a

• primary user that is a business partner directly involved in a specified transaction. A party

SHALL NOT use a GLN allocated by an organisation that does not directly relate to their business relationships. Digital location: The owner or primary user(s) of the digital location is responsible for

• allocating the GLN.

Note: The owner is the organisation that has the legal or rightful title to the physical or digital location. A primary user is an organisation that directly transacts with a physical or digital location. There may be multiple primary users associated to a single location.

Example: an owner would be the organisation that has legal ownership of a mall. A primary user would be the organisation that is leasing a space within the mall for their retail store.

When allocating a GLN, an organisation SHOULD: 1. Verify that the party and/or location is not already identified by a GLN. 2. Associate master data for the identified party/location to the GLN (see section 4.5.3).

3. Communicate the GLN and associated data to trading partners in a timely manner. The GLN allocated to a party/location SHOULD be communicated to partners by the organisation that allocated the GLN in advance of a transaction/delivery so that all systems can be prepared for the interaction. See section 4.5.2 for additional details.

Individual companies need to determine how they allocate GLNs. An organisation may use a single GLN for order, delivery and invoice because each process is undertaken at the organisation (legal entity) level. However, an organisation may also allocate distinct GLNs to locations and functions within its organisation.

See the GS1 GLN Allocation Rules Standard for management rules and scenarios defining when a GLN SHOULD be allocated to a new party/location or as the result of a change. Note: These rules are intended for global use. National, federal or local regulations may take precedence. Examples include regulations affecting a company’s registration, taxation, or fiscal obligations, as well as its industry requirements.

4.5.1.2 Party/location without Global Location Number

When a party/location needs to be identified by a GLN, the organisation defining the party/location in support of their business operations SHALL allocate the GLN. See section 4.5.1.1 for details.

If the organisation does not have a GS1 Company Prefix, it must either request a GS1 Company Prefix or an individual GLN from a GS1 Member Organisation. A GLN SHALL NOT be sold, leased, or loaned to a separate party.

Note: GS1 Member Organisations offer various alternatives by which a company can obtain its own GLN.

4.5.1.3 Assigning GLN values

GLNs SHOULD be allocated without any classifying elements. There is no need to coordinate GS1 identification key values across different GS1 identification keys. This is true even when the keys have an identical format. For example, there is no risk of conflict when a GTIN-13 and a GLN have the same value: GS1 Application Identifiers, data qualifiers and XML tags (EDI) prevent misinterpretation.

While companies may place GLNs in logical groupings for internal purposes, there are no supply chain standards to do so. GLNs are assigned at the discretion of GS1 user companies to support their business applications. Any additions or deletions from the group do not impact individual GLN allocation.

4.5.2 GLN non-reuse

An allocated GLN SHALL NOT be reallocated to another party and/or location. The only exceptions are: If the GLN was never published in an externally accessible manner (e.g., to a registry or directly

• to a trading partner), it may be reused immediately

Parties and/or locations that have been withdrawn and are reintroduced may use the original

• GLN if they are reintroduced without any modifications or changes that require a new GLN as specified by the GS1 GLN Allocation Rules Standard The GLN non-reuse rule went into effect on 1 July 2022. GLNs discontinued and withdrawn from systems prior to 1 July 2022 may be considered for reuse one final time (*). However, companies are strongly advised to follow the non-reuse rule for all GLNs to avoid risks of conflicting data.

(*) If a GLN was withdrawn prior to 1 July 2022, the previously applicable rules must be adhered to (see section 4.16.2 Deprecated GLN reuse rules). Note: These rules are intended for global use. Exceptions may occur only when local regulatory or legal requirements mandate otherwise.

4.5.3 Information associated with a Global Location Number

GLNs are assigned to parties and locations to provide a key to access master data in a business process (e.g., order, invoice, deliver). For each GLN, master data will be assigned to support business processes.

Master data associated to a GLN SHOULD be established in a database, then the GLN may then be used to facilitate efficient communication of this information. The information held for legal entities, functions, physical locations and digital locations may include but is not limited to name, address, bank details, certifications and contact details.

Information associated with each GLN is held internally by trading partners or on central databases. If the party or location changes and the details are not updated, communications or deliveries will go to the outdated information held on file. Therefore, it is essential for organisations to inform trading partners as soon as possible about new GLN assignments or changes to information associated with a GLN.

The GLN Management Rules that define what changes to a party or location require a new GLN are included in the GS1 GLN Allocation Rules Standard. The GLN Management Rules are designed to help industry make consistent decisions about the unique identification of parties and locations and SHOULD be referenced when changes to parties, locations and the information associated to them occur.

Local, national or regional regulations may require more frequent GLN changes. Such regulations have precedence over the rules provided within the GS1 GLN Allocation Rules Standard.

Important: Identical postal addresses, geocoordinates, geoshapes or other representations of where something is, operates or can otherwise be reached can be associated to multiple GLNs.

4.6 GSRN rules

4.6.1 Allocating Global Service Relation Numbers

4.6.1.1 General rule

Global Service Relation Numbers (GSRNs) can be used to identify the service provider and/or service recipient in any service relationship. A separate, unique number can be issued, normally by the organisation offering the service to identify the service provider and/or the service recipient, to identify any given service relationship. Once assigned, the GSRN becomes a unique and universal reference that can be used by all parties involved in the service relationship.

A GSRN with either AI (8018) or AI (8017) are mutually exclusive, that is, a GSRN can only be assigned to a single role, recipient or provider, but not both.

4.6.1.2 Changes in a service relationship

From time to time the details related to a Global Service Relation Numbers (GSRNs) may change. The following are general cases that may occur if the circumstances under which the GSRN were originally set up change:

If an organisation providing a service ceases trading (possibly because of liquidation), any

• GSRNs allocated by that organisation SHOULD be phased out. If the activity covered by the GSRN is transferred, the new organisation providing the service may continue to use existing GSRNs if it has taken over the GS1 Company Prefix of the original organisation providing the service; if not, the GSRN SHOULD be phased out and a new GSRN allocated using the new organisation’s GS1 Company Prefix.

If the range of services identified by a GSRN changes, the organisation that provides the service

• SHOULD change the details associated with the GSRN on the related computer file record. The assignment of a new GSRN is not required in this case. A GSRN used to identify a particular service relationship that has terminated SHOULD NOT be

• reallocated for a period well beyond the lifetime of the relevant records.

4.6.1.3 Recommendation for allocating Global Service Relation Numbers

The exact method used to allocate the Global Service Relation Number (GSRN) is left to the discretion of the issuing organisation. However, the GSRN must be unique for each individual service provider and for each individual service recipient and each must remain unique for a period well beyond the lifetime of the records relevant to the service relationship.

All issuers of Global Service Relationship Numbers (GSRNs) must ensure that GSRNs allocated for healthcare service providers and service recipients SHALL NOT be reused. For ease of administration, GS1 recommends that GSRNs be allocated sequentially and not contain classifying elements.

4.6.1.4 Information associated with a Global Service Relation Number

Global Service Relation Number (GSRN) may be used as a standalone element strings where all information required is established on a computer file using the individual GSRN as the key to access the information. The type of information stored is determined by the nature of the service relationship. Typical information includes the service recipient’s or provider’s full name, address and details of the services received or rendered.

If the identification of a GSRN needs to be further qualified with a sequence indicator corresponding to specific encounters during a service relationship, a Service Relation Instance Number (SRIN), AI (8019), may be associated to the GSRN.

When a GSRN is encoded to a data carrier and applied to AIDC media (e.g., membership card or patient wristband), a Version Control Number (VCN), AI (7242) may be associated to the GSRN to enable distinction between different versions of the same identification, displayed on one or more of the same AIDC media type. For example, when AIDC media is needed for access control purposes, this distinction between versions can facilitate processes managed with a service providers system to validate current versions and deactivate previously issued versions of the AIDC media.

4.7 GDTI rules

4.7.1 Allocating Global Document Type Identifiers

The Global Document Type Identifier (GDTI) is used to identify any document for document control purposes. A separate, unique GDTI is required whenever any of the characteristics of a document are different in any way that is relevant to the business process. As a guiding principle, if the end user is expected to distinguish between documents and process them accordingly, each document SHOULD be allocated its own GDTI.

The Global Document Type Identifier (GDTI) is assigned by the document issuer. The GDTI is used as a key to access database information (normally held by the issuing organisation). The same document type is used for all document classes that are issued with an identical purpose.

This can then be used to reference the main characteristics of the document, such as: The exact right or obligation the document imposes.

• The document purpose (e.g., insurance policy, governmental paper, product image).

• A different document type SHALL be used whenever the main characteristics of the document are different. Example: An application form for membership to an organisation would be identified with a specific document type and all filled forms would be uniquely identified through the serial component.

If the limits of the membership were to change (now subject to legal constraints) the document type shall change, to document the modification. Subsequent applications with the modified form would then be tracked through the serial component.

The identification of each individually issued document requires a unique serial component in addition to the document type. Any duplicates of the individually issued document SHOULD use the same serial component as the original. The serial component is optional and assigned by the document issuer and is unique in a series of documents issued under the same Document Type. Ideally the serial component SHOULD be sequentially allocated for each new document generated. The serial component is used to communicate detailed characteristics pertinent to the individual document such as:

The name and address of the recipient

• The document details

• The definition of main characteristics (identified with the document type) and detailed characteristics (identified with the serial component) is at the discretion of the document issuer. All issuers of Global Document Type Identifiers (GDTIs) must ensure that GDTIs allocated for documents relevant to patient treatment/care SHALL NOT be reused.

4.7.2 GDTI change rules

If the function, type, or major content (determined by the document issuer) of the document changes, the document type identifier SHALL change. The document issuer will determine if changes to the content of the document require changing the document type identifier, or adding or changing a serial component.

Embedded metadata changes do usually not impact the functionality of the document and are not considered content changes. These would not require a change in the GDTI.

4.8 GINC rules

4.8.1 Allocating Global Identification Numbers for Consignment (GINC)

4.8.1.1 General rule

An individual Global Identification Number for Consignment is a unique number, which remains the same for the life of a grouping of logistics or transport units to which it is assigned. When assigning a GINC, the rule is that an individual GINC number must not be reallocated within one year of the shipment date from the freight forwarder assigning the GINC to a transport. However, prevailing regulatory or industry organisation specific requirements may extend this period.

4.9 GSIN rules

4.9.1 Allocating Global Shipment Identification Numbers

4.9.1.1 General rule

An individual Global Shipment Identification Number (GSIN) is a unique number, which remains the same for the life of the grouping of logistics or transport units to which it is assigned. When assigning a GSIN, the rule is that an individual GSIN number must not be reallocated within ten years of the shipment date from the seller or third party logistics provider (sender) of the GSIN to a trading partner buyer (recipient) to comply with the regulations of the World Customs Organisation (WCO). For goods that circulate within one country (domestic transport), the period of reuse is based on either governmental, industry or the discretion of the seller (sender) of the goods.

4.10 CPID rules

4.10.1 Allocating Component/Part Identifiers

The exact method used to allocate the Component/Part Identifier (CPID) is left to the discretion of the issuing organisation.

4.11 GCN rules

4.11.1 Allocating Global Coupon Numbers

The exact method used to allocate the Global Coupon Number (GCN) is left to the discretion of the issuing organisation. However, the GCN must remain unique for a period well beyond the lifetime of the records relevant to the coupon. For ease of administration, GS1 recommends that GCNs be allocated sequentially and not contain classifying elements.

4.12 GMN rules

4.12.1 Allocating Global Model Numbers

Global Model Numbers can be used to identify base product designs or specifications from which trade items are derived and/or registered. The exact method used to allocate the GMN is left to the discretion of the brand owner. However, each GMN must be unique for each product model being identified and once assigned to one product model, SHALL NOT be reissued to identify another product model.

For regulated healthcare medical devices, the following applies: Allocation of the Basic UDI-DI (GMN) is made per the discretion of the brand owner, but in compliance with regulatory rules.

4.12.1.1 Responsibility

The brand owner is responsible for the issuance and allocation of Global Model Numbers.

4.12.2 Information associated with Global Model Numbers

The data related to the product model SHOULD be recorded and shared using the Global Model Number as the key to the information. Examples of the type of information related to a GMN, may include the brand, certifications obtained, sewing pattern (e.g., in apparel sector), form / material/classification scheme (e.g., in construction sector), product line (e.g., in cosmetic sector).The following points highlight the relationship between GMN and GTIN:

All GMN level attributes are common for all GTINs associated with it.

• Additional attributes across all GTINs associated with one GMN may not be common.

• If any attribute defined for a GMN changes in a way that trading partners are expected to distinguish the changed or new product model from previous/current product model, a new GMN must be assigned. Since all GMN attributes are common for all associated GTINs, this also implies the change of these GTINs according to guiding principle 1 of the GS1 GTIN Management Standard (see https://www.gs1.org/1/gtinrules/en).

For regulated healthcare medical devices, the following applies: Basic UDI-DI attributes are common for all GTINs (UDI-DIs) associated with it. The identifier can be attributed to GTINs (UDI-DIs) associated with it, in the UDI database (e.g., EUDAMED).

4.13 Data relationships

This section defines the rules for allowed combinations of element strings on the same physical entity, irrespective of the data carrier(s) applied to the entity. The rules are application-neutral, which means that they apply to all applications listed in section 2 and to any other application where multiple element strings are combined on the same physical entity.

The rules are presented in two tables: 1. Invalid pairs of element strings, indicating which combinations of element strings are not allowed on the same physical entity. 2. Mandatory pairs of element strings, indicating which element strings must occur in combination with one or more other element strings.

Note: In both tables, the GS1 Application Identifiers (AIs) are used to indicate the element string. But when evaluating the rule the complete element string, i.e. the AI and the data field, needs to be taken into account.

Note: GTINs encoded in an EAN/UPC and ITF-14 symbols are to be regarded as element strings prefixed by an inferred AI (01). Note: Duplicate element strings (e.g., two serial numbers, two batch/lot numbers, two Extended Packaging URLs) MAY appear on the same physical entity (for example in multiple barcodes). In that case they SHALL have the same value in each occurrence on that entity.

4.13.1 Invalid pairs of element strings

This section defines the pairs of element strings that SHALL NOT appear together on the same physical entity. The table does not provide a finite list of all possible rules, only situations that have proven to pose difficulties in practice are included.

Some explanation on Table 4-4: The table is sorted by AI value, with the lowest AI value displayed in the first column.

• Multiple AIs may be listed in the first or third column, separated by commas. This means that

• the same rule applies to all listed AIs.

The rules work in both directions, e.g., if it states AI (01) SHALL NOT be combined with AI (37)

• this implies that AI (37) SHALL NOT be combined with AI (01).

For the purpose of this table Made-to-Stock (MtS) GTIN AI (01) and Made-to-Order (MtO) GTIN

• AI (03) are simply referred to as GTIN.

Table 4-4 Invalid pairs of element strings

Invalid pairs of element strings	Rule
AI	Designation	AI	Designation
01	GTIN	01	GTIN	All occurrences of GTIN SHALL have one value. It is for example not allowed to include GTINs of other packaging levels.
01	GTIN	02	GTIN of contained trade items	GTIN of contained trade items is intended to list the trade items contained in a logistic unit and SHALL NOT be used to identify the contents of a trade item.
01	GTIN	03	GTIN	The same GTIN value SHALL NOT be used with AI (01) and AI (03) and a trade item identified with (01) GTIN SHALL NOT be identified by a MtO GTIN with AI (03).
01, 03	GTIN	37	Count of units contained	The count of units contained SHALL only be used with GTIN of contained trade items or trade item pieces.
01	GTIN	255	Global Coupon Number	A trade item SHALL NOT also be identified as a coupon.
03	GTIN	02	GTIN of contained trade items	GTIN of contained trade items is intended to list the trade items contained in a logistic unit and SHALL NOT be used to identify the contents of a MtO trade item.
21	Serial Number	235	Third Party Controlled, Serialised Extension of GTIN	Only Serial Number or Third Party Controlled, Serialised Extension of GTIN SHALL be used with GTIN.

Invalid pairs of element strings	Rule
AI	Designation	AI	Designation
420	Ship to postal code, single postal authority	421	Ship to postal code with ISO country code	Only one ship to postal code SHALL be applied on the same physical entity.
421	Ship-to / Deliver- to postal code with three-digit ISO country code	4307	Ship-to / Deliver- to country code	Only one ship to country code SHALL be applied on the same physical entity.
422, 423, 424, 425	Country of origin, initial processing, processing, or disassembly	426	Country of full processing	Country of origin, initial processing, processing, or disassembly SHALL NOT be used in combination with country of full processing, since this would lead to ambiguous data.
390n	Amount payable – single monetary area	391n	Amount payable – with ISO currency code	Only one amount payable element string SHALL be applied on a payment slip.
390n	Coupon value	394n, 8111	Percentage discount of a coupon, Loyalty points of a coupon	The element strings coupon value, percentage discount of a coupon and loyalty points of a coupon SHALL NOT be applied in combination.
392n	Amount payable for a variable measure trade item – single monetary area	393n, 395n	Amount payable for a variable measure trade item and ISO currency code, Amount payable per unit of measure single monetary area (variable measure trade item)	Only one amount payable element string SHALL be applied on a variable measure trade item.
394n	Percentage discount of a coupon	8111	Loyalty points of a coupon	The element strings percentage discount of a coupon and loyalty points of a coupon SHALL NOT be applied in combination.
395n	Amount payable per unit of measure single monetary area (variable measure trade item)	8005	Price per unit of measure	The element strings Amount payable per unit of measure single monetary area (variable measure trade item) and Price per unit of measure SHALL NOT be applied in combination.
395n	Amount payable per unit of measure single monetary area (variable measure trade item)	392n, 393n	Applicable amount payable, single monetary area (variable measure trade item), Applicable amount payable with ISO currency code (variable measure trade item)	Only one amount payable element string SHALL be applied on a variable measure trade item.
4330	Maximum temperature in Fahrenheit	4331	Maximum temperature in Celsius	Only a single maximum temperature SHALL be used in combination with an SSCC
4332	Minimum temperature in Fahrenheit	4333	Minimum temperature in Celsius	Only a single minimum temperature SHALL be used in combination with an SSCC
7250	Date of birth	7251	Date and time of birth	Only one date of birth SHALL be used

Invalid pairs of element strings	Rule
AI	Designation	AI	Designation
7256	Full name of person	7253, 7254, 7255, 7259	Family name of person, given name of person and name suffix of person, baby of family name	Either full name of person or a combination of family name of person, given name of person and name suffix of person SHALL be used.
7259	Baby of family name	7253, 7254, 7255, 7256	Family name of person, given name of person, name suffix of person, full name of person	Where the recipient of care identified by a GSRN is a baby, the name of the baby SHALL either be provided through AI (7259) (possibly in conjunction with AI (7258), to handle situations of multiple births) or through the combination of one or more of AIs (7253), (7254), (7255), (7256).
8006	ITIP	01	GTIN	The GTIN SHALL NOT be used in combination with the identification of an individual trade item piece. The GTIN of the trade item to which the individual trade item piece belongs is contained in the element string.
8006	ITIP	37	Count of units contained	The count of units contained SHALL only be used with GTIN of contained trade items or trade item pieces.
8018	GSRN for the recipient	8017	GSRN for the provider	Only one Global Service Relation Number (recipient or provider) SHALL be applied at one time for identification of an individual in a given service relationship
8026	Identification of a trade item piece contained in a logistic unit	02, 8006	GTIN of contained trade items, Identification of an individual trade item piece	Identification of the trade item piece contained in a logistic unit SHALL NOT be used in combination with GTIN of contained trade items or identification of an individual trade item piece.

4.13.2 Mandatory association of element strings

This section defines the element strings that mandate the appearance of another element string on the same physical entity. Note: This does not necessarily mean that the element strings need to appear in the same data carrier. For example, multiple GS1-128 barcode symbols may be used in combination on a GS1 Logistic Label.

Table 4-5 reflects the use case requirements to date. Should future applications arise that require associations they will be added at that time. Some explanation on Table 4-5: The table is sorted by AI value, with the AI that is the trigger for the rule displayed in the first

• column. This means that this table cannot be read in both directions. For example, a rule that states AI (17) must be used together with AI (01), does not imply that AI (01) can only be used together with AI (17), since it can also be used with other AIs. Multiple AIs may be listed in the first column, separated by commas. This means that the rule

• applies to all of the listed AIs (element strings).

The same AI can occur in the first column multiple times, in different rows. This means that

• depending on the value of the element string different rules need to be applied.

When multiple AIs are included in the third column, this is always done with an AND, OR or XOR

• logical operator between them:

AND means that all element strings SHALL appear on the physical entity

• OR means that one or a combination of the element strings SHALL appear on the physical

• entity.

XOR means that one of the element strings SHALL appear on the physical entity and the

• other element string SHALL NOT.

Table 4-5 Mandatory association of element strings

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
01 with N1 = 0	GTIN of a variable measure trade item scanned at POS	30 OR 3nnn*	The GTIN of a variable measure trade item scanned at POS SHALL occur in combination with:  variable count of items; or  a trade measure Note: Master data will be needed to determine whether the GTIN represents a variable measure trade item scanned at POS. Also see the note below this table.
01 with N1 = 9, 02 with N1 = 9	GTIN of a variable measure trade item not scanned at POS	30 OR 3nnn* OR 8001	The GTIN of a variable measure trade item not scanned at POS SHALL occur in combination with:  variable count of items; or  a trade measure; or  the dimensions of a roll product. Note: The first position of the GTIN is “9” for such trade items. Also see the note below this table.
01 with N1 = 9	GTIN of a custom trade item per section 2.6.8	242	The GTIN of a custom trade item using AI (01) and indicator digit “9” SHALL be used in combination with the Made-to-Order variation number. Note: The first position of the GTIN is “9” for such trade items.
02	GTIN of contained trade items	00 AND 37	The GTIN of contained trade items SHALL occur in combination with an SSCC and the count of the trade items.
10	Batch/lot number	01 XOR 02 XOR 03 XOR 8006 XOR 8026 ***	Batch/lot number SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  Identification of a Made-to-Order (MtO) trade item (GTIN): or  an ITIP; or  an ITIP of contained trade item pieces
11, 13, 15, 16, 17	Production date, packaging date, best before date, sell by date, expiration date (of a trade item)	01 XOR 02 XOR 03 XOR 8006 XOR 8026 ***	These dates SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  Identification of a Made-to-Order (MtO) trade item (GTIN); or  an ITIP; or  an ITIP of contained trade item pieces
12	Due date	8020 AND 415	The due date SHALL occur in combination with the payment slip reference number and the GLN of the invoicing party
17	Expiration date (of a coupon)	255	The expiration date of a coupon SHALL occur in combination with the GCN.
20	Internal product variant	01 XOR 02 XOR 8006 XOR 8026 ***	Internal product variant SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces
21	Serial number	01 XOR 03 XOR 8006***	The serial number SHALL occur in combination with:  a GTIN; or  Identification of a Made-to-Order (MtO) trade item (GTIN); or  an ITIP Note: SGTIN is a common term for the combination of GTIN and serial number.

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
22	Consumer product variant	01	The consumer product variant SHALL occur in combination with a GTIN of a retail consumer trade item.
235	Third Party Controlled Serialised Extension of GTIN	01	The Third Party Controlled Serialised Extension of GTIN SHALL occur in combination with a GTIN of a trade item.
240	Additional product identification	01 XOR 02 XOR 8006 XOR 8026 ***	The additional product identification SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces
241	Customer part number	01 XOR 02 XOR 8006 XOR 8026 ***	The customer part number SHALL occur in combination with:  the GTIN; or  the GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces
242	Made-to-Order variation number	(01 with N1 = 9) XOR (02 with N1 = 9) XOR (8006 with N1 = 9) XOR (8026 with N1 = 9) ***	The Made-to-Order variation number SHALL occur in combination with:  the GTIN; or  the GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces Note: The GTIN must relate to a custom trade item. The first position of the GTIN is “9” for such trade items.
243	Packaging Component Number	01	The Packaging Component Number SHALL occur in combination with the GTIN
250	Secondary serial number	(01 XOR 8006***) AND 21	The secondary serial number SHALL occur in combination with the serial number and:  a GTIN; or  an ITIP
251	Reference to source entity	01 XOR 8006***	The reference to source entity SHALL occur in combination with:  a GTIN; or  An ITIP
254	GLN extension component	414	The GLN extension component SHALL occur with the Identification of a physical location (GLN).
30	Variable count of items	01 XOR 02	The variable count of items SHALL occur with:  a GTIN; or  a GTIN of contained trade items. Note: The GTIN must relate to a variable measure trade item.
3nnn*	Trade measures	01 XOR 02	Trade measures SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items. Note: The GTIN must relate to a variable measure trade item.
3nnn**	Logistic measures	00 OR 01	Logistic measures SHALL occur in combination with:  an SSCC  a GTIN
337n	Kilograms per square metre	01	Kilograms per square metre SHALL occur in combination with a GTIN.

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
37	Count of units contained	00 AND (02 XOR 8026)	The count of units contained SHALL occur in combination with the SSCC and:  GTIN of contained trade items, or  ITIP of contained trade item pieces.
390n	Amount payable – single monetary area	8020 AND 415	The amount payable (single monetary area) SHALL occur in combination with the payment slip reference number and the GLN of the invoicing party.
390n	Coupon value – single monetary area	255	The coupon value (single monetary area) SHALL occur in combination with the Global Coupon Number.
391n	Amount payable – with ISO currency code	8020 AND 415	The amount payable (with ISO currency code) SHALL occur in combination with the payment slip reference number and the GLN of the invoicing party.
392n	Applicable amount payable - single monetary unit	01 AND (30 XOR 31nn XOR 32nn XOR 35nn XOR 36nn *)	The applicable amount payable (single monetary area) SHALL occur in combination with the GTIN and either:  variable count of items; or  a trade measure. Note: The GTIN must relate to a variable measure trade item.
393n	Applicable amount payable – with ISO currency code	01 AND (30 XOR 31nn XOR 32nn XOR 35nn XOR 36nn *)	The applicable amount payable (with ISO currency code) SHALL occur in combination with the GTIN and either:  variable count of items; or  a trade measure. Note: The GTIN must relate to a variable measure trade item.
394n	Percentage of a coupon	255	The percentage of a coupon SHALL occur in combination with the Global Coupon Number.
395n	Amount payable per unit of measure single monetary area (variable measure trade item)	01 AND (30 XOR 31nn XOR 32nn XOR 35nn XOR 36nn *)	The applicable amount payable per unit of measure (single monetary area) SHALL occur in combination with the GTIN and either:  variable count of items; or  a trade measure. Note: The GTIN must relate to a variable measure trade item.
403	Routing code	00	The routing code SHALL occur in combination with an SSCC.
415	GLN of the invoicing party	8020	The GLN of the invoicing party SHALL occur in combination with the payment slip reference number.
422	Country of origin	01 XOR 02 XOR 8006 XOR 8026 ***	The country of origin SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces
423	Country of initial processing	01 XOR 02	The country of initial processing SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
424	Country of processing	01 XOR 02	The country of processing SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
425	Country of disassembly	01 XOR 02	The country of disassembly SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
426	Country of full processing	01 XOR 02	The country of full processing SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
427	Country subdivision of origin	(01 XOR 02) AND 422	The country subdivision of origin SHALL occur in combination with the country of origin and:  a GTIN; or  a GTIN of contained trade items.
430N	Ship-to / Deliver- to address GS1 Application Identifiers	00	Ship-to / Deliver-to address GS1 Application Identifiers SHALL occur in combination with an SSCC
4303	Ship-to / Deliver- to address line 2	4302 and 00	Ship-to / Deliver-to address line 2 SHALL occur in combination with line 1 of a ship-to address and an SSCC
4309	Ship-to / Deliver- to GEO location	00	Ship-to / Deliver-to GEO location SHALL occur in combination with an SSCC
431N	Return-to address GS1 Application Identifiers	00	Return-to address GS1 Application Identifiers SHALL occur in combination with an SSCC
4313	Return-to address line 2	4312 AND 00	Return-to address line 2 SHALL occur in combination with line 1 of a return-to address
432N	Service-related GS1 application identifiers for transport process	00	Service-related GS1 application identifiers SHALL occur in combination with an SSCC
4330	Maximum temperature in Fahrenheit	00	Maximum temperature in Fahrenheit SHALL occur in combination with an SSCC
4331	Maximum temperature in Celsius	00	Maximum temperature in Celsius SHALL occur in combination with an SSCC
4332	Minimum temperature in Fahrenheit	00	Minimum temperature in Fahrenheit SHALL occur in combination with an SSCC
4333	Minimum temperature in Celsius	00	Minimum temperature in Celsius SHALL occur in combination with an SSCC
7001	NATO stock number	01 XOR 02 XOR 8006 XOR 8026 ***	The NATO stock number SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items; or  an ITIP  an ITIP of contained trade item pieces
7002	UNECE meat carcasses and cuts classification	01 XOR 02	The UNECE meats carcasses and cuts classification SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7003	Expiration date and time	01 XOR 02	The expiration date and time SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7004	Active potency	01 AND 10	The active potency SHALL occur in combination with the batch/lot number and the GTIN.
7005	Catch area	01 XOR 02	The catch area SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7006	First freeze date	01 XOR 02	The first freeze date SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
7007	Harvest date	01 XOR 02	The harvest date SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7008	Species for fishery purposes	01 XOR 02	The species for fishery purposes SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7009	Fishing gear type	01 XOR 02	The fishing gear type SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7010	Production method	01 XOR 02	The production method SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
7011	Test by date	01 XOR 02	The test by date and optional time SHALL occur in combination with:  a GTIN; or a GTIN of contained trade items.
703(s)	Number of processor	01 XOR 02	The number of processor SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
710, 711, 712, 713, 714, 715, 716, 717	National Healthcare Reimbursement Number	01	National Healthcare Reimbursement Number(s) SHALL occur in combination with the GTIN.
7020	Refurbishment lot ID	(01 XOR 8006***) AND 416	The refurbishment lot ID SHALL occur in combination with the GLN of production/service location and:  a GTIN; or  an ITIP
7021	Functional status	01 XOR 8006***	The functional status SHALL occur in combination with:  a GTIN; or  an ITIP
7022	Revision status	(01 XOR 8006***) AND 7021	The revision status SHALL occur in combination with the functional status and:  a GTIN; or  an ITIP
7041	UN/CEFACT freight unit type	00	The UN/CEFACT freight unit type SHALL occur with an SSCC.
723s	Certification reference	01 XOR 8004	Certification reference SHALL occur in combination with:  a GTIN; or  a GIAI
7240	Protocol ID	01 XOR 8006	The protocol ID SHALL occur in combination with a GTIN
7241	AIDC media type	8017 XOR 8018	The AIDC media type SHALL occur in combination with:  the GSRN for the provider; or  the GSRN for the recipient
7242	Version Control Number (VCN)	8017 XOR 8018	The Version Control Number SHALL occur in combination with:  the GSRN for the provider; or  the GSRN for the recipient

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
7250, 7251, 7252, 7257, 7259	Date of birth, date and time of birth, biological sex, address of person, baby of family name	8018	Date of birth, date and time of birth, biological sex, address of person and baby of family name SHALL occur in combination with a Global Service Relation Number – Recipient
7253, 7254, 7255, 7256	Family name of person, given name of person, name suffix of person, full name of person	8017 XOR 8018	Family name of person, Given name of person, Full name of person and Name suffix of person SHALL occur in combination with:  Global Service Relation Number – Provider; or  Global Service Relation Number – Recipient
7258	Baby birth sequence indicator	8018 AND 7259	Baby birth sequence indicator SHALL occur in combination with a Global Service Relation Number – Recipient and Baby of family name.
8001	Dimensions of roll products	01	Dimensions of roll products SHALL occur in combination with the GTIN. Note: The GTIN must relate to a variable measure trade item.
8005	Price per unit of measure	01 XOR 02	The price per unit of measure SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items. Note: The GTIN must relate to a variable measure trade item.
8007	International Bank Account Number	8020 AND 415	The International Bank Account Number SHALL occur in combination with the payment slip reference number and the GLN of the invoicing party.
8008	Date and time of production	01 XOR 02	The date and time of production SHALL occur in combination with:  a GTIN; or  a GTIN of contained trade items.
8009	Optically readable sensor indicator	01 OR 00	The Optically Readable Sensor Indicator Number SHALL occur in combination with the GTIN or SSCC. Note the two data elements may or may not appear in the same data carrier.
8011	CPID serial number	8010	The CPID serial number SHALL occur in combination with the CPID.
8012	Software Version	01 XOR 8006***	The software version SHALL occur in combination with:  a GTIN; or  an ITIP
8014	Highly Individualised Device Registration Identifier (HIDRI)	01	Highly Individualised Device Registration Identifier SHALL occur in combination with:  a GTIN with AI (01)
8019	Service Relation Instance Number	8017 XOR 8018	The Service Relation Instance Number SHALL occur in combination with:  the GSRN for the provider; or  the GSRN for the recipient.
8020	Payment slip reference number	415	The payment slip reference number SHALL occur in combination with the GLN of the invoicing party.
8026	ITIP of contained pieces	00 AND 37	The ITIP of contained pieces SHALL occur in combination with an SSCC and the count of the pieces.

If element string	Then mandatory	Rule
associated
element string
AI	Designation	AI
8030	Digital Signature (DigSig)	(01 AND 21) XOR (8006 AND 21) XOR (8010 AND 8011) XOR 8003 XOR 8004 XOR 8017 XOR 8018 XOR 00 XOR 253 XOR 255	The Digital Signature (DigSig) SHALL occur in combination with one of the following:  Global Trade Item Number and Serial number  Identification of an individual trade item piece and Serial number  Component/Part Identifier and Component/Part Identifier serial number  Global Returnable Asset Identifier including Serial component  Global Individual Asset Identifier  Global Service Relation Number - Provider  Global Service Relation Number - Recipient  Serial Shipping Container Code  Global Document Type Identifier including Serial component  Global Coupon Number including Serial component
8040	IMEI	01 AND 21	The IMEI number SHALL occur in combination with a Global Trade Item Number and serial number
8041	IMEI2	01 AND 21 AND 8040	The IMEI2 number SHALL occur in combination with a Global Trade Item Number, serial number, and the IMEI number.
8042	Embedded SIM number	01 AND 21 AND 8040	The embedded SIM number SHALL occur in combination with a Global Trade Item Number, serial number and IMEI.
8043	Physical SIM number	01 AND 21 AND 8040	The physical SIM number SHALL occur in combination with a Global Trade Item Number, serial number and IMEI.
8111	Loyalty points of a coupons	255	Loyalty points of a coupon SHALL occur in combination with the GCN.
8200	Extended packaging URL	01	The extended packaging URL SHALL occur in combination with the GTIN.
* The AIs for trade measures are set out in section 3.6.2 Trade measures: AIs (31nn, 32nn, 35nn, 36nn). Note: All AIs in section 3.6.2 can be used with this AI 395n. ** The AIs for logistics measures are set out in section 3.6.3 Logistic measures: AIs (33nn, 34nn, 35nn, 36nn) *** If used in combination with the identification of trade item pieces (ITIP), the optional AIs on all individual pieces of the trade item SHALL be identical. N Any digit from 0 to 9

Note: Exception for point-of-sale. See Table 2-37. Areas of GS1 system application.

4.14 Human readable interpretation (HRI) rules

Human readable interpretation (HRI) rules are provided to standardise printing requirements and facilitate training of staff on how to deal with GS1 AIDC data carriers that fail to scan or read. There are two categories of rules:

General rules that apply independent of sector, intended application or product category.

• Sector or application specific rules which must be aligned with the general rules and can be found in sections: 4.14.1 Healthcare human readable interpretation

• 4.14.2 General retail consumer trade item human readable text rules

• 4.14.3 Manual date marking

• There are two types of text that appear on an object: human readable interpretation (HRI) and nonHRI text. Human readable interpretation (HRI) represents the same data encoded in the barcode or RFID

• tag (see section 9 for full definition).

Non-HRI text is all other text on the object which may or may not be encoded in the barcode or

• RFID tag (see section 9 for full definition).

Figure 4-3. Example of human readable text

Note: The following rules are intended for global use. Exceptions may occur only when local regulatory or legal requirements mandate otherwise. Note: At present, HRI rules are applicable to barcodes as rules for EPC/RFID tags are under development.

Note: HRI rules for the EAN/UPC symbology and the add-on symbols are explained in section 5.2.5 Human readable interpretation. General human readable text rules 1. HRI Placement a. Whether a barcode encodes a GS1 identification key, GS1 key attributes, or a combination of both, the HRI SHOULD be included and placed adjacent to the barcode. HRI SHOULD be grouped together wherever physically possible while maintaining the HRI legibility, minimum barcode height and/or Quiet Zones as specified in the appropriate symbol specification table in section 5.12.3.

b. In cases where the HRI must be printed above, to the left, or to the right of the barcode due to packaging or space constraints, HRI SHOULD be printed adjacent so that is obviously associated with the barcode. This rule applies to all barcodes independent of printing orientation (e.g., ladder orientation).

Figure 4-4 Locations of HRI for barcode in ladder orientation c. When HRI is grouped together, it SHOULD be placed adjacent to the barcode and it SHALL always follow the sequence of the encoded data in the barcode. d. If the HRI for GS1 identification keys and GS1 key attributes is split, the GS1 identification key HRI SHOULD be placed adjacent to the barcode. For example, the GS1 identification key HRI is below the barcode and the GS1 key attributes HRI is above the barcode.

Figure 4-5 Example of split HRI placement e. An element string (application identifier and associated data) SHALL NOT be broken into multiple lines of HRI, for example the data for a serial number would appear on one line of HRI, e.g., (21) ABCDEF12345.

f. When using non-HRI text, the element strings SHOULD NOT be broken into multiple lines. g. HRI SHALL appear except in rare circumstances for specific applications where there are extreme space constraints (e.g., direct part marking, loose fresh produce). If the barcode cannot be read or scanned and the HRI does not appear on the object, non-HRI text SHOULD be used as backup information.

2. Font and legibility a. A clearly legible font SHALL be used e.g., OCR-B as defined in ISO/IEC 30116. Reasonable alternative fonts and character sizes are acceptable provided the interpretation is clearly legible. When applying the “clearly legible” principle, the following principles and examples separate a best practice versus below average implementation.

i. Monospaced font types such as OCR-B or Sans serif font types such as Arial are preferred. ii. Bold, italics, light or narrow versions of a font SHOULD NOT be used. iii. The font size SHOULD be at least 2 mm (0.08 in) in height iv. Spaces SHALL NOT be encoded in the barcode.

v. Spaces may be used in the HRI itself to ease manual data input. vi. The spaces between characters driven by the font type SHOULD NOT be reduced. b. HRI SHALL be limited to element strings and will not include barcode overhead such as separator characters.

c. When using GS1 element string syntax, although parentheses are not encoded in the barcode, parentheses SHALL surround AIs in HRI. 3. URL a. When the GS1 Digital Link URI syntax for trade item extended packaging applications is encoded in a barcode, it is left to the brand owner’s discretion to use the GS1 Digital Link URI in non-HRI text (e.g., GTIN only 09520123456788 or URL https://brand.example.com/01/09520123456788).

b. When AI (8200) appears on the object, the expression of the URL SHALL NOT appear in HRI. If it appears in non-HRI text, it SHALL be expressed as http://brandownerassignedURL.com/GTIN (where GTIN expressed as 14 digits).

4. Data titles As a non-HRI text option, the data title (see section 3.2) may be associated with the data instead of using the AI numbers. See Figure 4-3 which shows expiration date and lot number identified with non-HRI text and where, in the same figure, the same data is shown using the all-AI format.

5. GS1 Logistics Label a. HRI alongside a 2D barcode on a logistic label is not required if this is already present with the GS1-128 symbol, or is present as data titles and data content elsewhere on the label.

b. When a logistic label displays a 2D barcode encoding transport process information that is otherwise represented in text or graphic on the label, HRI of this information is not required.

c. On GS1 Logistics Labels HRI characters SHALL be no less than 3 mm (0.1181 in) high.

4.14.1 Healthcare human readable interpretation rules

The GS1 system requires printing both the GS1 AIDC data carrier and the HRI that represents all the information encoded within that GS1 AIDC data carrier. If the GS1 AIDC data carrier cannot be read or scanned, the HRI should be used as back up information. The GS1 preferred format for HRI when applied on healthcare trade items SHALL be as noted in the general HRI rules found in section 4.14.

When considering the practical implementation and application of HRI during the creation of the product packaging, many factors must be taken into account to determine if and how HRI is included with the symbol. These factors may include the type of product being labelled or marked, product use, available space for marking, alternate data availability, regulatory or legal requirements, technical constraints, etc.

However, printing both the GS1 AIDC data carrier and the associated HRI may not be possible due to many factors such as the intended use of the item, available space for marking, etc. Deviation from the HRI format should be minimised and consider impacts to downstream trading partners and users.

Typical examples are shown the figures below. (01)

09524000059109 (21)

12345678p901 (10) 1234567p (17) 271120

Figure 4-6 Preferred HRI format GS1 DataMatrix example

Figure 4-7 Preferred HRI format GS1-128 example

If a deviation from the preferred format is required that results in HRI not being printed, then a combination of HRI and non-HRI text may be used. When doing so, the following rules apply:

If the data represented in the non-HRI text is exactly as in the HRI, then the appropriate AI

• SHALL be printed along with the data title. See Figure 4-8.

If data represented in the non-HRI text does not match the HRI, then only a data title may be

• used. The AI SHALL NOT be printed. This is illustrated in Figure 4-9 by the GTIN and Expiry.

The selection of data titles may be determined by the manufacturer based on regulatory, local

• language requirements, relevant standards (e.g., ISO/IEC 15223) or appropriate abbreviations.

GTIN (01) 09524000059109 SERIAL (21) 12345678p901 LOT (10) 1234567p EXPIRY (17) 271120

Figure 4-8 Combination of HRI with AIs, non-HRI text and data titles example

GTIN 09524000059109 SERIAL (21) 12345678p901 LOT (10) 1234567p EXPIRY 20 Nov 2027

Figure 4-9 Combination of HRI with AIs, non-HRI text (GTIN and Expiry) and data titles example

If it is not possible to print both the GS1 AIDC data carrier and the HRI, Figure 4-10 SHOULD be used to determine how HRI will be implemented. When it is not possible to print all of the HRI, preference for printing SHALL be given to the GS1 key.

Figure 4-10 Healthcare human readable interpretation (HRI) decision tree (to be used only when limited space is available) Note: Figure 4-10 is intended for use when there is no regulatory mandate that conflicts with this guidance and where space constraints limit the ability to provide both the GS1 AIDC marking and the associated HRI text—this document does not impact the non-HRI text that is required for compliance with labelling regulations. In all situations, applicable regulatory requirements SHALL take precedence. Brand owners are responsible to understand and comply with applicable regulations and to document deviations from those regulations and their justifications for such deviations in the product master record files or other formal document control files.

Note: Active potency, AI (7004) HRI rule. Printing of the active potency on the item is controlled by regulation. Human readable interpretation of the active potency is not required on the trade item.

4.14.2 General retail consumer trade item human readable text rules

General retail consumer trade items have specific rules that build on the general human readable interpretation (HRI) rules in section 4.14. Note: The following rules are intended for global use. Exceptions may occur only when mandated by regulatory or legal requirements. For example, refer to the sections related to healthcare section 4.14 for regulated healthcare trade items sold in retail.

The barcodes for point-of-sale (POS) SHALL have GTIN in HRI adjacent to the barcode. HRI for any additional consumer engagement (extended packaging) barcode encoding GS1 Digital Link URI SHALL be left to the discretion of the brand owner. See Figure 4-11.

Front panel Back panel Adjacent POS barcodes Consumer engagement barcode

Figure 4-11 Example of extended packaging and POS barcodes (See 6.3.3.1 preferred placement) For EAN/UPC barcodes the HRI SHALL show the GTIN-8, GTIN-12, or GTIN-13 and SHALL be placed below the barcode.

Figure 4-12 Example of EAN-13 with EAN/UPC HRI format

GS1 DataBar Retail POS family, GS1 DataMatrix, Data Matrix (GS1 Digital Link URI) and QR Code (GS1 Digital Link URI) SHALL display (01) followed by the encoded GTIN in a 14-digit format.

GS1 DataMatrix QR Code (GS1 element string syntax) (GS1 Digital Link URI syntax)

Figure 4-13 Example of GTIN-13 in 14-digit format

Note: The example.com domain name (reserved in RFC 2606) is used in the example as a place holder for any domain name. The 14-digit GTIN HRI is not required for any 2D barcode displayed on the packaging when it is adjacent to a linear barcode with HRI or if the 2D barcode is intended for consumer engagement.

When a 2D barcode will be the only barcode for the GTIN, it SHALL display the 14-digit GTIN HRI as shown in Figure 4-13. When a linear EAN-8, EAN-13 or UPC-A barcode and 2D barcode are adjacent on a general retail consumer trade item, HRI for the GTIN is only required for the linear barcode. If the linear EAN-8, EAN-13, UPC-A or UPC-E barcode and 2D barcode are unable to be adjacent, then the GTIN SHOULD accompany both.

Figure 4-14 Example of adjacent barcode HRI

Figure 4-15 Example of non-adjacent barcode HRI

When a UPC-E barcode and 2D barcode are adjacent on a general retail consumer trade item, HRI for the GTIN is required and SHOULD accompany both. UPC-E encodes a GTIN-12 using a zero- suppression process described in section 5.2.2.4.

Figure 4-16 Example of adjacent UPC-E barcode HRI

HRI beyond GTIN is not required when using barcodes encoded with GS1 element string or GS1 Digital Link URI syntax on general retail consumer trade items. If additional GS1 element strings are used by downstream trading partners (e.g., retailer and/or consumers), they SHOULD appear on the object in human readable text.

Figure 4-17 Example of human readable placement

GS1 element strings encoded in a data carrier which are intended for internal use, e.g., AI (243), may appear on the object in either non-HRI text or HRI. Non-HRI SHOULD NOT be placed adjacent to the barcode as this can make it difficult for the GTIN to be identified.

Figure 4-18 Example of internal use application identifier human readable placement

4.14.3 Manual date marking

Where regulations and/or trade partner agreements require applied date markings for stock rotation and manual identification, the ISO standard (8601) for date sequence SHOULD be used. The format SHOULD be YYYY-MM-DD preceded by the date type short form (See Figure 4-19 for respective date types) based on ISO standard abbreviations (15223).

Date type	Short form
Production	PROD
Packaging	PACK
Best Before	BEST
Expiration	EXP

Figure 4-19 Short forms by date type

AIDC techniques are suggested over any manual process to ensure accurate and timely stock rotation. Every effort should be made to adopt an automated process to increase productivity and date management.

4.15 Multiple AIDC data carrier management practices(cross-sector)

When additional data carriers are introduced into an existing scanning environment or business application, all application standard conformant data carriers SHALL remain as choices. This section provides a set of management practices intended to permit the use of multiple data carriers on the same entity. Among these multiple data carriers, at least one SHALL be from the mandatory AIDC data carrier choices in the appropriate application standard profile, see section 8.

4.15.1 Multiple AIDC data carrier management practices (all sectors and applications)

1. Barcode symbology identifiers: All barcode scanning systems SHALL deploy symbology identifiers (see section 5.1.3) and when using GS1 Application Identifiers, process them according to GS1 rules (see section 7.8).

2. Use of GS1 identifier: All GS1 data carriers that are used for the same application on an entity SHALL encode the same GS1 identifier (e.g., same GTIN, same GRAI, etc.). 3. Use of GS1 identifier attributes: When the GS1 identifier and GS1 identifier attributes occur in multiple data carriers on a single entity, the attribute values SHALL be the same.

3. GTIN plus attribute(s) flag: When applications require GTIN plus additional data to be captured in multiple data carriers, modifications to systems SHOULD be made to automate this requirement.

4. Adjacent placement of barcodes: a. When two barcodes can be used for the same application (i.e., point-of-sale, point of care, general distribution) they SHOULD be placed adjacent to each other while maintaining their Quiet Zones. The orientation (stack or row of barcodes) or sequence (which barcode is placed on the left, right, top, or bottom) SHALL be determined by the brand owner.

b. When adjacent placement on one surface of an entity is not possible, the barcodes SHOULD be placed on an adjoining surface of the entity. This practice does not supersede any section 6 barcode placement rule (e.g., 8 mm (0.3 inch) free space between barcodes and panel edge).

c. When there is more than one barcode with a GS1 identifier on an entity, it is essential that the scanning systems will ensure: i. The system SHALL only process one set of the desired data.

ii. Scanning systems SHOULD only produce one acknowledgement (e.g., beep) when multiple barcodes are scanned from the same entity. 6. Non-adjacent placement of barcodes: When two barcodes are used for different applications (e.g., point-of-sale, extended packaging), they SHOULD be placed non-adjacent to one another.

7. Obscure placement of barcodes: When a barcode is used for production control purposes only (e.g., Data Matrix encoded with a non-GS1 syntax to match label to product), it SHOULD be made as obscure as possible or even obstructed on the trade item package.

8. Use of GS1-128, 2D barcode, EPC/RFID or NFC tags as supplemental data carrier with EAN/UPC or ITF-14 as the main barcode: In general retail and general distribution, where EAN/UPC or ITF-14 is used to encode the GTIN and where a GS1-128, a 2D barcode, an EPC/RFID tag or NFC tag is used to encode GTIN attributes, the same GTIN SHALL be encoded in all GS1 AIDC data carriers.

9. GS1-128 as supplemental barcode: When an EAN/UPC or ITF-14 is used to encode GTIN and where GS1-128 is used to encode GTIN attributes, GS1-128 SHOULD encode GTIN and the GTIN attributes in a single barcode to ensure accurate data association.

10. Use of 2D barcode as supplemental barcode with GS1-128 as main barcode: In general distribution, where GS1-128 is used to encode a GS1 identifier and attributes, these element strings at a minimum SHALL be encoded in the supplemental 2D barcode.

4.15.2 Use of EPC/RFID as supplemental AIDC data carrier (all sectors and

applications) An EPC/RFID data carrier can only encode globally unique instance level identifiers (see section 3.11 and the current version of the GS1 EPC Tag Data Standard (TDS)). When EPC/RFID is used as an additional data carrier, particular attention must be paid to the identifier used.

a. GTIN, AI (01): When EPC/RFID is used as in addition to a barcode that encodes a GTIN, the SGTIN EPC (SGTIN-96, SGTIN-198, SGTIN+, SGTIN++, DSGTIN+ and DSGTIN++), corresponding to a compound key of AI (01) and AI (21), SHALL be used. When the associated barcode encodes AI (21), it SHALL encode the same, brand-owner assigned Serial Number used to encode the Serial Number component of the SGTIN EPC on the EPC/RFID tag, taking care not to change any characters and neither add nor remove any leading zeros.

b. ITIP, AI (8006): When EPC/RFID is used in addition to a barcode that encodes AI (8006), the ITIP EPC (ITIP-110, ITIP-212, ITIP+ and ITIP++), corresponding to a compound key of AI (8006) and AI (21), SHALL be used. When the associated barcode encodes AI (21), this SHALL encode the same, brand-owner assigned Serial Number used to encode the Serial Number component of the ITIP EPC on the EPC/RFID tag, taking care not to change any characters and neither add nor remove any leading zeros.

c. GRAI, AI (8003): When EPC/RFID is used in addition to a barcode that encodes AI (8003), the GRAI EPC (GRAI-96, GRAI-170, GRAI+ and GRAI++) SHALL be serialised. When there is a business need, the associated barcode can also encode a serialised GRAI. In that case the value of the serialised GRAI in the EPC/RFID and associated barcode SHALL be the same.

d. GLN, AI (414): When EPC/RFID is used in addition to a barcode that encodes AI (414), and when there is a business need, the associated barcode can also encode a GLN extension component (AI (254)). In that case, the value of AI (414) and AI (254) in the EPC/RFID tag (SGLN-96, SGLN-195, SGLN+ and SGLN++) and associated barcode SHALL be the same.

e. GDTI, AI (253): When EPC/RFID is used in addition to a barcode that encodes AI (253), the GDTI EPC (GDTI-96, GDTI-113, GDTI-174, GDTI+ and GDTI++) must be serialised. When there is a business need, the associated barcode can also encode a serialised GDTI. In that case the value of the serialised GDTI in the EPC/RFID and associated barcode SHALL be the same.

4.15.3 Use of NFC tags as supplemental AIDC data carrier (extended packaging

applications) The NFC tag SHALL carry the same hostname and GS1 identifier values in the GS1 Digital Link URI as 2D barcodes and if additional data elements appear in the GS1 Digital Link URI they also SHALL contain the same values.

The GS1 Digital Link URI SHALL be encoded in the first record of an NFC Forum NDEF message, as defined in the NFC Forum Data Exchange Format (NDEF) Technical Specification. NFC tags SHALL encode the GS1 Digital Link URI using a Well-Known Type URI record as defined in the NFC Forum URI Record Type Definition Technical Specification. Identifier Code 2 (https://www.) or Identifier Code 4 (https://), SHALL be used as defined in the NFC Forum URI Record Type Definition Technical Specification.

The URI Identifier Code that is used SHALL ensure http protocol alignment between the NFC tag and the accompanied QR Code or Data Matrix. In other words, if https:// is encoded in the QR Code, https:// SHALL also be encoded on the NFC tag, using NFC Forum URI Identifier Code 4.

4.15.4 GS1 multiple barcode management practice for general retail

In addition to the requirements outlined in section 4.15.1, the following rules apply to the use of multiple barcodes for general retail. 1. Migration to 2D barcodes: A GS1 DataMatrix, QR Code (GS1 Digital Link URI) or Data Matrix (GS1 Digital Link URI), SHALL be used in addition to the EAN/UPC, or a GS1 DataBar retail POS family of barcodes, to ensure stakeholders that are not yet able to consistently scan 2D barcodes are not negatively impacted. Application Standard Profiles in section 8 provide information on conformance requirements for the transition period and future use of 2D barcodes at retail POS.

When there is more than one barcode with GTIN on trade items, it is essential that the POS systems will ensure:

• The system SHALL only process one set of the desired data in the final transaction.

• Scanning systems SHOULD only produce one acknowledgement (e.g., beep) when multiple barcodes are scanned from the same trade item. Important: If the points above are not implemented, unintended POS transactions may occur. 2. Placement when using a 2D barcode for multiple applications: When a 2D barcode will be scanned in multiple applications (e.g., point-of-sale, inventory management and consumer engagement), placement for POS takes precedence. The same adjacent placement rules as stated in section 4.15.1 are applicable.

Note: Where GS1 DataBar and 2D barcodes are used, GTIN and GTIN attributes SHALL be encoded in a single barcode to ensure accurate data association.

4.15.5 GS1 multiple barcode management practices for healthcare

In addition to the requirements outlined in section 4.15.1, the following rules apply to the use of multiple barcodes for healthcare. 1. GTIN in GS1 DataMatrix and GS1 DataBar processing (retail healthcare): In order to facilitate migration away from a multiple barcode environment where one retail pharmacy requires EAN/UPC and another retail pharmacy requires GS1 DataMatrix or GS1 DataBar Expanded, at a minimum, retail pharmacies SHALL have the capability to process the AI (01) GTIN from GS1 DataMatrix and GS1 DataBar in addition to the capability for EAN/UPC.

2. GTIN in GS1 DataMatrix, GS1 DataBar and GS1-128 processing (non-retail healthcare): In order to facilitate migration away from a multiple barcode environment where one healthcare provider requires EAN/UPC or ITF-14 and another healthcare provider requires GS1 DataMatrix, GS1 DataBar Expanded, or GS1-128, at a minimum, non-retail pharmacies SHALL have the capability to process AI (01) GTIN from GS1 DataMatrix, GS1 DataBar and GS1128 in addition to the capability for EAN/UPC and ITF-14.

3. GS1-128 as secondary symbol: In point-of-care applications, where EAN/UPC or ITF-14 is used to encode GTIN and where GS1-128 is used to encode GTIN attributes, GS1-128 SHOULD encode GTIN as it is best practice to encode the GTIN attributes and the GTIN in a single symbol whenever possible to ensure accurate data association.

Note: Where GS1 DataBar and GS1 DataMatrix are used, GTIN and GTIN attributes SHALL be concatenated to ensure accurate data association. 4. Scenario-based management practices: Multiple barcode practices which apply to all sectors are found in section 4.15.1 and take precedence over those specific only to healthcare. While industry best practice focuses on using only one barcode per package, a product package that serves multiple markets may have the need for application of multiple barcodes. When this occurrence is unavoidable, the management practices for use of multiple symbols found in Table 4-6 apply for regulated healthcare trade items. Table 4-6 separates solutions based on combinations of scanner environments encountered for each scenario:

Scanners encountered combination #1: Package scanned in retail pharmacies (Yes or No).

• Scanners encountered combination #2: Package scanned in general distribution (Yes or No).

• Table 4-6 Multiple barcode management practices

Combinations	Barcode data scenario	Scanner environment	Symbol	Barcode options	Gen Specs	Proposal
of scanners	arrange-
encountered	ment
Symbol 1	Symbol 2	Retail	Auto- mated conveyor	Vertical or horizontal	Section
pharmacy
or non-
retail
pharmacy/
bedside
#1	GTIN A	Only attributes for GTIN A	Y	Y	N	NA	GS1 DataMatrix	2.1.4 2.1.5 4.15.1	See Note 1 See Note 10 For * see Note 2 For ** see Note 3
GS1-128
GS1 DataBar
* EAN/UPC plus GS1
DataMatrix, GS1 DataBar
Expanded, GS1-128,
or
* EAN/UPC, GS1 DataBar,
or GS1-128 plus **
Composite Component
#2	GTIN A	Only attributes for GTIN A	Y	Y	Horizontal	GS1 DataMatrix GS1-128 *EAN/UPC plus GS1 DataMatrix or GS1-128	GS1 DataMatrix	2.1.7 4.15.1	See Note 1
GS1-128	See Note 10
*EAN/UPC plus GS1	For * see
DataMatrix or GS1-128
Note 2
#1	GTIN A	GTIN A + GTIN A attributes	Y	N	Depends upon packaging limitations	GS1 DataMatrix	2.1.4 2.1.5 4.15.1	See Note 1 See Note 4 See Note 10 For * see Note 6 For ** see Note 3	See Note 1
GS1-128	See Note 4
GS1 DataBar	See Note 10
* EAN/UPC plus GS1	For * see
DataMatrix, GS1 DataBar
Note 6
Expanded, GS1-128,
or	For ** see
GS1 DataBar, or GS1-128	Note 3
plus ** Composite
Component
or
* EAN/UPC with **
Composite Component
#2	GTIN A	GTIN A + GTIN A attributes	Y	Y	Depends upon packaging limitations	GS1 DataMatrix GS1-128 *EAN/UPC plus GS1 DataMatrix or GS1-128	GS1 DataMatrix	2.1.7 4.15.1	See Note 1
GS1-128	See Note 2
*EAN/UPC plus GS1 DataMatrix or GS1-128	See Note 4
For * see
Note 6
See Note 10
#1	GTIN A + Attribute Set 1	GTIN A + Attribute Set 1	Y	N	Duplicate symbols on bulky packages	GS1	Duplicate of first symbol	2.1.4 2.1.5	See Note 1 See Note 5 See Note 7 See Note 10	See Note 1
DataMatrix	See Note 5
GS1-128	See Note 7
GS1
DataBar	See Note 10
Expanded
EAN/UPC
plus
Composite
Component
#2	GTIN A + Attribute Set 1	GTIN A + Attribute Set 1	Y	Y	Duplicate symbols on bulky packages	GS1	Duplicate of first symbol	2.1.7	See Note 1 See Note 5 See Note 7 See Note 10
DataMatrix
GS1-128
EAN/UPC
plus
Composite
Component

Combinations	Barcode data scenario	Scanner environment	Symbol	Barcode options	Gen Specs	Proposal
of scanners	arrange-
encountered	ment
Symbol 1	Symbol 2	Retail	Auto- mated conveyor	Vertical or horizontal	Section
pharmacy
or non-
retail
pharmacy/
bedside
#1	GTIN A + Attribute Set 1	GTIN A + Attribute Set 2	Y	Y	N	Depends upon packaging limitations	GS1	GS1	2.1.4 2.1.5	See Note 1 See Note 5 See Note 8 See Note 10
DataMatrix	DataMatrix
GS1-128	GS1-128
GS1	GS1
DataBar	DataBar
Expanded	Expanded
EAN/UPC	EAN/UPC
plus	plus
Composite	Composite
Component	Component
#2	GTIN A + Attribute Set 1	GTIN A + Attribute Set 2	Y	Y	Horizontal	GS1 DataMatrix GS1-128	GS1	GS1 DataMatrix GS1-128	GS1	2.1.7	See Note 1
DataMatrix	DataMatrix	See Note 5
GS1-128	GS1-128
See Note 8
See Note 10
#1	GTIN with serial number	GIAI or GRAI	Not permitted in regulated healthcare on small surgical instruments where only one
mark can be made based on the available marking surface and SGTIN is source-
marked by brand owner on that surface
See Note 10
#1 or #2	GTIN A	GTIN B	Not permitted
#2	GTIN A	GTIN A	SSCC	SSCC	Permitted on trade items which also serve as logistics units. Symbol placement per
section 6 (All clauses contained in sections 6.2, 6.4, 6.6, 6.7 and 6.8).
See Note 10
#1	SSCC	AI (02) +	Y	Y	N	Vertical	GS1-128	GS1-128	2.2.1	See Note
AI (37)	9
#2	SSCC	AI (02) +	Y	Y	Vertical	GS1-128	GS1-128	2.2.1	See Note
AI (37)	9
#1 and #2	GS1 data carried by 1 or 2 symbols	Non-GS1 data	Non-GS1	Symbols encoding internal or proprietary data SHOULD NOT be placed in a location
data	where they could be scanned in the open supply chain (e.g., retail POS, by an
automated conveyor line scanner per GS1 specifications)
See section 4.15.1 – Obscure placement and Note 10 below

Combinations	Barcode data scenario	Scanner environment	Symbol	Barcode options	Gen Specs	Proposal
of scanners	arrange-
encountered	ment
Symbol 1	Symbol 2	Retail	Auto- mated conveyor	Vertical or horizontal	Section
pharmacy
or non-
retail
pharmacy/
bedside
Notes:
 Note 1: Concatenation of GTIN and GTIN attributes into one symbol is the preferred option for Regulated healthcare
retail consumer trade items to validate connectivity between GTIN and attributes. Separating GTIN attributes from the
GTIN in the barcode SHOULD be avoided wherever possible as improper association is possible. The scenario takes into
account the use of EAN/UPC which is widely used in retail pharmacies to capture GTIN but once a market is prepared to
support a data carrier which can encode GTIN plus the GTIN attributes, this data carrier SHOULD replace EAN/UPC when
GTIN attributes are required.
 Note 2: Symbols which are not preferred for regulated healthcare retail consumer trade items because they do not allow
for concatenation but remain permissible options.
 Note 3: GS1 Composite Component does not stand alone as a complete symbol; it is necessary to associate the
composite component with a linear symbol such as EAN/UPC, ITF-14, GS1-128 or GS1 DataBar. GS1 Composite
Component therefore remains a legitimate option but only in non-retail applications, GS1 DataMatrix is preferred for
regulated healthcare retail consumer trade items based on its ability to encode all information in one symbol and do so
efficiently in terms of print speed and panel size.
 Note 4: It is recommended to use only one symbol that encodes the GTIN and attributes.
 Note 5: When two symbols are required to encode a large number of GTIN attributes, both symbols SHOULD be the
same symbology and both encode GTIN.
 Note 6: Symbols which are not preferred for regulated healthcare retail consumer trade items because they do not allow
for concatenation but remain permissible options.
 Note 7: Recommended for bulky or large trade items or pallets.
 Note 8: Wherever possible use of one symbol to encode GTIN plus all attributes is preferred to encoding attributes in
two symbols.
 Note 9: AI (02) + AI (37) not recommended in regulated healthcare supply chain.
 Note 10: Since June 2007 GS1 has recommended all trading partners in the healthcare sector invest exclusively in
imaging-based scanners. Now that GS1 DataMatrix has been approved within the standard, it is important to inform all
trading partners of a process within GS1 to establish target deployment dates. Without these dates, brand owners do
not have a way to know when to deploy GS1 DataMatrix on their packaging and those needing to invest in scanning
equipment may inadvertently purchase equipment that will not support the standards. To see GS1 healthcare’s position
paper on GS1 DataMatrix adoption, visit https://www.gs1.org/healthcare.

4.16 Deprecated rules

This section contains rules that have been deprecated. The rules are included as reference for pre- existing situations where the rules may still apply.

4.16.1 Deprecated GTIN reuse rules

These rules are deprecated as of 1 January 2019. A GTIN allocated to a trade item that has become obsolete must not be reused for another trade item until at least 48 months have elapsed after:

the expiration date of the last original trade items produced with that number.

• -orthe last original trade items produced with that number have been supplied to the customer.

• The following sector-specific rules apply:

Apparel: In the case of clothing the minimum retention period is reduced to 30 months.

• Healthcare: Companies must ensure that GTINs allocated to regulated healthcare trade items

• SHALL NOT be reused.

Exception: regulated healthcare trade items that have been withdrawn from the market and are reintroduced may use the original GTIN if they are reintroduced without any modifications or changes which require a new GTIN as specified by the GTIN Management Standard.

Technical industries: GTINs that are marked directly on components and parts, such as used in

• rail rolling stock and infrastructure, SHALL NOT be reused (also see 2.6.14).

For other trade items, brand owners should consider a longer period depending upon the type of goods and/or any regulatory framework. For example, steel beams may be stored for many years before entering the supply chain, and processes should be put in place to ensure that the GTIN is not reallocated for a significant period of time.

In addition, when contemplating the reuse of a GTIN, consideration should be given to the use of data associated with the original GTIN by trading partners for statistical analysis or service records, which may continue long after the original trade item was last supplied.

If a GTIN has been assigned to an item, which was then never actually produced, the GTIN may be deleted from any catalogue immediately without first being marked as discontinued. In this exceptional case the GTIN may be reused 12 months after deletion from the seller’s catalogue.

4.16.2 Deprecated GLN reuse rules

These rules are deprecated as of 1 July 2022. A Global Location Number (GLN) that has been previously used and has become obsolete must not be reused for another location until at least 48 months have elapsed. A longer period may be needed in accordance with government requirements, such as invoicing and taxation or requirements related to the nature of the location (e.g., a bonded warehouse). This period provides time for all references of the old GLN to be removed from trading partner files.

All issuers of Global Location Numbers (GLNs) must ensure that GLNs allocated for locations used in the healthcare supply chain SHALL NOT be reused, e.g., locations where treatment of patients takes place, etc.

---

返回目录

上一篇：3 GS1 Application Identifier definitions

下一篇：5 Data carriers

原文链接：GS1 General Specifications Standard