GS1 Architecture Group
The purpose of the Architecture Group (AG) is to develop the GS1 System Architecture and, by reference to the architecture, assure the technical integrity of the GS1 System and the consistent and efficient inter-operation of the various parts of the system.
The GS1 Architecture Principles
This document sets out the architectural principles that underpin the GS1 system.
The GS1 System Architecture (Second Publication March 2013)
This document defines and describes the GS1 System Architecture.
The GS1 System Landscape (Second Publication, March 2013)
This document provides a comprehensive inventory of the GS1 standards and catalogues and classifies them into topic areas.
GS1 ICOM (Integrated Communication) (January 2011)
A description of how types of business data and modes of communication are integrated in the GS1 system
Intro to the GS1 Architecture – Gain an understanding of the GS1 Architecture and the GS1 Architectural Principles by watching this short recorded presentation
Who are members of the GS1 Architecture?
The GS1 Architecture Group members include representatives from End Users, Solution Providers, GS1 Member Organisations and Global Office. The roles and responsibilities of the GS1 Architecture Group are defined in the GSMP Process Manual. This group reports to the Board Committee for Standards (BCS) within the GSMP framework.
Request For Finding
The GS1 Architecture Group is available to respond to architectural “requests for finding (RFF)” submitted by members of the GSMP community.
The work team developing guidelines for Management of Reusable Transport Items (RTIs) with eCom messages requested the Architecture Group to consider the use of the GS1 Identification Key Global Returnable Asset Identifier (GRAI) when ordering Reusable Transport Items. This Architecture Group finding clarifies that the Global Trade Item Number (GTIN) should be used for eCOM orders and highlights recommended changes to ensure consistency on this point across all GS1 standards.
This publication by the GS1 Architecture Group covers the compatibility of the two supported message standards, GS1 EANCOM and GS1 XML, with a strong focus on master data synchronization. GS1 EANCOM and GS1 XML were developed at different times, the former dating back to early nineties prior to the widespread adoption of the internet, and the latter compling with more recent web oriented rules. This paper outlines the recommendations on the use of each in particular with respect to the synchronisation of master data through GDSN and connected data pools.
Ideally all GTINs are assigned, at source, by the brand owner at the point of manufacture. A request for findings was submitted for the case a product is not assigned at GTIN by the brand owner at source and where two, or more, importers of the products wish to assign a GTIN prior to commercialisation. The paper outlines the potential solutions available and closes with a series of recommendations.