The GS1 Architecture Group responds to architectural "requests for finding" (RFF) submitted by members of the GSMP community. Published Findings are considered open, when relevant to current GSMP discussion or awaiting action. Findings are closed when the recommended actions are completed but remain available for historic reference.
Sort order
Analysis and Recommendations - GPC and GDSN
This RFF addresses uses of GPC attributes in GDSN that cause duplication of information.
- Current finding
- https://ref.gs1.org/architecture/findings/gpc-gdsn-analysis/
- Current version
- 1.0.0
- Last modified
- April 2020
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gpc-gdsn-analysis/archive
- Primary landing page
- GS1 Architecture
Analysis and Recommendations - GS1 Company Prefix Sub-Team
This purpose of this paper is to create a consistent definition of the GS1 Company Prefix, evaluate the impacts of such a definition, and identify the steps required to realize the definition across all standards. Additional deliverables may include actions and recommendations for other governance groups.
- Current finding
- https://ref.gs1.org/architecture/findings/gcp-use-defintion-in-gs1-standards/
- Current version
- 1.2.0
- Last modified
- 30 September 2015
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gcp-use-defintion-in-gs1-standards/archive
- Primary landing page
- GS1 Architecture
Analysis and Recommendations, Brand Owner Sub-Team
The term "brand owner" is very closely associated with a product as products are the only objects that have a brand. Other objects may be associated with a brand (e.g. a department location for the brand's managers) but their association is ultimately through the underlying products. Identification keys other than the GTIN have other terms associated with them.
- Current finding
- https://ref.gs1.org/architecture/findings/brand-owner-terminology/
- Current version
- 1.0.0
- Last modified
- 5 December 2012
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/brand-owner-terminology/archive
- Primary landing page
- GS1 Architecture
Attributes Association with GS1 Key
Two work requests have indicated a potential need to associate attribute data currently requiring mandatory association with a GTIN to other GS1 identifiers, namely Global Coupon Number and Global Individual Asset Identifiers. The question raised was can a system that has been programmed to associate attribute data with a particular key, also identify the same attribute data with a different GS1 key.
- Current finding
- https://ref.gs1.org/architecture/findings/attribute-association-with-gs1-keys/
- Current version
- 1.0.0
- Last modified
- 28 March 2014
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/attribute-association-with-gs1-keys/archive
- Primary landing page
- GS1 Architecture
Compatibility of EANCOM & GS1 XML
This RFF addrresses the compatibility of the GS1 EANCOM and the GS1 XML message standards with a focus on master data synchronisation (and hence not on transactional messages).
- Current finding
- https://ref.gs1.org/architecture/findings/gs1-eancom-and-gs1-xml/
- Current version
- 1.0.0
- Last modified
- 15 June 2011
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gs1-eancom-and-gs1-xml/archive
- Primary landing page
- GS1 Architecture
Data Carriers and GS1
In early 2020, the following request was brought to the attention of the GS1 Architecture Group (AG): "What should be the GS1 policy regarding the reference on non-GS1 data carriers (both open and commercial) in the GS1 system of standards?" This document contains the AG's findings related to this subject.
- Current finding
- https://ref.gs1.org/architecture/findings/data-carriers-and-gs1/
- Current version
- 1.0.2
- Last modified
- 17 March 2021
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/data-carriers-and-gs1/archive
- Primary landing page
- GS1 Architecture
Framework for consistent GTIN allocation
In an era of digital transformation, a new framework of terminology, roles & responsibilities and best practices is needed as input to GSMP teams who are challenged with how to best extend and optimise the GS1 System for the consistent and efficient allocation of GTIN.
- Current finding
- https://ref.gs1.org/architecture/findings/consistent-GTIN-allocation/
- Current version
- 1.0.0
- Last modified
- 2 September 2021
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/consistent-GTIN-allocation/archive
- Primary landing page
- GS1 Architecture
GRAI in eCom trade messages?
This RFF addresses the question: can GRAI, under specific conditions, be used instead of GTIN in the LIN Segment of EANCOM Message to identify RTIs for ORDERS, INVOIC and DESADV?
- Current finding
- https://ref.gs1.org/architecture/findings/grai-in-eCom-trade-messages/
- Current version
- 1.0.0
- Last modified
- 15 June 2011
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/grai-in-eCom-trade-messages/archive
- Primary landing page
- GS1 Architecture
GS1 Identification and Data – Integrity and Security
This Finding outlines how integrity and security underpin trust in GS1 identification and data exchange, and provides a framework for evaluating emerging technologies as the GS1 system evolves.
- Current finding
- https://ref.gs1.org/architecture/findings/integrity-and-security/
- Current version
- 1.0.0
- Last modified
- 17 February 2026
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/integrity-and-security/archive
- Primary landing page
- GS1 Architecture
GS1 identification keys allocation by third parties
The purpose is to document the impact on the GS1 system architecture of allocating GS1 identification keys to End Users through third parties, to highlight the related business issues and to recommend the adoption of adequate policies.
- Current finding
- https://ref.gs1.org/architecture/findings/gs1-keys-allocation-3rd-parties/
- Current version
- 1.0.0
- Last modified
- 24 January 2018
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gs1-keys-allocation-3rd-parties/archive
- Primary landing page
- GS1 Architecture
GTIN allocation when not assigned at source
Sometimes products are not assigned a GTIN by the brand owner at source and an issue arises where two, or more, importers of these products wish to assign a GTIN prior to commercialisation. This Finding outlines the potential solutions available.
- Current finding
- https://ref.gs1.org/architecture/findings/gtin-allocation-not-at-source/
- Current version
- 1.0.0
- Last modified
- 5 December 2012
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gtin-allocation-not-at-source/archive
- Primary landing page
- GS1 Architecture
GTIN Reuse
This RFF sets out the architectural position that GTINs should not be reused.
- Current finding
- https://ref.gs1.org/architecture/findings/gtin-reuse/
- Current version
- 1.0.0
- Last modified
- 11 January 2017
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gtin-reuse/archive
- Primary landing page
- GS1 Architecture
ICOM: an integrated view on communicating business data
This RFF identifies overlaps and intends to help to guide GS1 to where it should look to further streamline its standards offerings.
- Current finding
- https://ref.gs1.org/architecture/findings/gs1-icom/
- Current version
- 1.0.0
- Last modified
- 5 January 2011
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/gs1-icom/archive
- Primary landing page
- GS1 Architecture
Principles and Criteria for High-Capacity Data Carriers in the GS1 system
This Finding provides a guide for the Global Standards Management Process (GSMP) and the GS1 community, to ensure a consistent approach when assessing requests for new GS1 AIs required for encoding in high-capacity data carriers.
- Current finding
- https://ref.gs1.org/architecture/findings/principles-for-high-capacity-data-carriers/
- Current version
- 1.0.0
- Last modified
- 19 November 2025
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/principles-for-high-capacity-data-carriers/archive
- Primary landing page
- GS1 Architecture
Support Emerging Use Cases for GS1 Identification Part 1
This Request for Finding asked the GS1 Architecture Group to review, improve, then approve a series of recommendations to support expansion of the GS1 identification system's relevance to new entities, in new application areas and in ways that supports interoperability and efficiency across sectors, regulations, and regions.
- Current finding
- https://ref.gs1.org/architecture/findings/emerging-ID-use-cases-part-1/
- Current version
- 1.0.0
- Last modified
- 8 December 2022
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/emerging-ID-use-cases-part-1/archive
- Primary landing page
- GS1 Architecture
Support Emerging Use Cases for GS1 Identification Part 2
This Request for Finding asked the GS1 Architecture Group to review, improve, then approve a series of recommendations to support expansion of the GS1 identification system's relevance to new entities, in new application areas and in ways that supports interoperability and efficiency across sectors, regulations, and regions.
- Current finding
- https://ref.gs1.org/architecture/findings/emerging-ID-use-cases-part-2/
- Current version
- 1.0.0
- Last modified
- 25 May 2023
- Open/closed
- Open
- Archive
- https://ref.gs1.org/architecture/findings/emerging-ID-use-cases-part-2/archive
- Primary landing page
- GS1 Architecture
The Future Encoding Format of the Electronic Product Code
This RFF addresses the fact that nearly 15 years after the initial publication of the EPC Tag Data Standard 1.0, the "parsing" of GS1 identification keys in the EPC suite of standards remains a barrier to implementation.
- Current finding
- https://ref.gs1.org/architecture/findings/future-encoding-format-EPC/
- Current version
- 1.0.2
- Last modified
- 12 November 2020
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/future-encoding-format-EPC/archive
- Primary landing page
- GS1 Architecture
Typing within the GS1 System Finding
This finding from the GS1 Architecture Group addressed the questions arising from mass detection of a large number of similar objects which are identified with the same GS1 Key.
- Current finding
- https://ref.gs1.org/architecture/findings/typing-within-gs1-system/
- Current version
- 1.0.0
- Last modified
- 6 March 2015
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/typing-within-gs1-system/archive
- Primary landing page
- GS1 Architecture
Unique GS1 Identification Finding
This finding clarifies the concept of "unique GS1 identification" especially in the context of marketplace resellers but also in the development and implementation of services such as Verified by GS1 and the GLN Registry.
- Current finding
- https://ref.gs1.org/architecture/findings/unique-gs1-identification/
- Current version
- 1.0.0
- Last modified
- 8 September 2022
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/unique-gs1-identification/archive
- Primary landing page
- GS1 Architecture
Using external identifiers in the GS1 System
This RFF addresses "how to integrate external identifiers for transport equipment (such as BIC codes (containers) and EVNs (rail vehicles)) in the GS1 System". Reason is that "embedding" of such external codes is recommended in at least one guideline (GS1 in Rail).
- Current finding
- https://ref.gs1.org/architecture/findings/external-identifiers/
- Current version
- 1.0.0
- Last modified
- 7 November 2014
- Open/closed
- Closed
- Archive
- https://ref.gs1.org/architecture/findings/external-identifiers/archive
- Primary landing page
- GS1 Architecture