GDSN Validation Rules

Standard
Document
for
Validation Rules for

Global Data Synchronisation
Network
BRG: GDSN
Document Version: 1.2.2
Date: 02-Sep-2009
1 General Information
1.1 Problem Statement / Business Need
Distributed Global Validation Rules are required to support the Global Data
Synchronisation process. The scope of this CR addresses the validation of rules that
actors in the GDSN will perform. Global Validation Rules are the foundation to ensure
that Item data passed within the Global Data Synchronisation Network conforms to a
common structure and complies with global standards.
1.2 Objective
The objective is to define validation rules within the Global Data Synchronisation
Network.
The validation rules specified in this document are mandatory for parties that make up
the Global Data Synchronisation Network (GDSN); namely, the Global Registry, Source
Data Pools and Recipient Data Pools.
1.3 Audience
The audience of the standards would be any participant in the global supply chain that
is a member of the Global Data Synchronization Network. The entities wishing to
become a certified Source and/or Recipient Data Pool within the Global Data
Synchronisation Network will be the adopters of this Global Validation Rules
1.4 Artefacts
Artefact name Artefact description

1.1 Acknowledgements
1.1.1 Task/Project Group Participants (where applicable)
Function Name Company / organisation

Participant Brad Papietro Wegmans
Participant Bruce Hawkins Wal-Mart
Participant Budi Saputra P&G
Participant Colin Robinson Nestle
Participant David Peet eXchangeBridge
Participant Gina Tomassi Pepsi Cola
Participant Grant Kille WWRE
Participant Jim Funk SC Johnson
Participant Jim Sheehan Shaw's
Participant Karen Spooner Kraft
Participant Lionel Tussau Georgia-Pacific
Participant Lol Kieran Unilever-UK
Participant Marcel Yska Ahold
Participant Maurol Vecchiotti Johnson & Johnson
Participant Nadine Radomski Dean Foods
Participant Peter Porri Coca-Cola
Participant Randy Mercer LANSA
Participant Sean Lockhead UCCnet
Participant Steve Vazzano Transora
Participant Susan Schmidt-Thomson Fiskars Brands
Participant William Rosenfeld TR2 Consulting
Participant Giovanni Biffi EAN Colombia
Participant Tan Jin Soon EAN Singapore
Participant Hideki Ichihara DCC Japan
1.1.1 Global Business Process Modellers (GBPM)

1 Business Process View
1.1 Requirements
For the information that details the harmonization of BRADs, BSDs and Schemas to be
used in validation, the reader is referred to the following document:
Harmonization of BRADs, BSDs and Schemas in v2.0.2
1.2 Consistent Use of Error Code
This section describes the usage of GDSN Error Codes and Error Messages for GDSN
validations. The Error Message ID and Error Message (text) specified in the GDSN
Validation rules (approved by the GDSN Task Group vote ending July 15, 2005) must
be sent on the EAN.UCC Exception message when a validation error is detected by the
Data Pool or the GS1 Global Registry.
 GDSN Error Codes are sent in the EAN.UCC Exception message using the
attribute/tag <errorCode>.
 GDSN Error Messages are sent using the attribute/tag <errorDescription
o The following convention MUST be used in formatting the
errorDescription. The content of the errorDescription
following attributes appended to the end of the text:
 ATTRIBUTE NAME and
 ATTRIBUTE VALUE
o This will assist the recipient of the error message to identify the cause of
the error.
The following example illustrates the proper format which would be used for application
of Validation Rule 16 – “GTIN (attribute) is required but not provided.”
< errorCode>”1”< /errorCode>

< errorDescription>”GTIN is required but not provided. attributeName “gtin”
attributeValue ”” “</ errorDescription>
The <errorCode> attribute may contain only the number of the Error Message ID and
may not contain additional characters (such as a prefix).
the error.
The following example illustrates the proper format which would be used for application
of Validation Rule 16 – “GTIN (attribute) is required but not provided.”

< errorDescription>”GTIN is required but not provided. attributeName “gtin”
attributeValue ”” “</ errorDescription>
The <errorCode> attribute may contain only the number of the Error Message ID and
may not contain additional characters (such as a prefix).
The <errorDescription> attribute may contain only the message text of the Error
Message (in double quotes) attributeName (literal), “Attribute XML Tag Name”,
attributeValue (literal)and “Attribute Value” and may not contain additional characters
(such as a prefix).
The data pool (or registry) which detects a GDSN validation error is required to send a
minimum of one error. The data pool may optionally send additional errors if they are
1.1 GTIN Validations
The GTIN (Global Trade Item Number) is used for the unique identification of trade
items worldwide. This is specified in the General EAN.UCC Specification section
1.3.1. There are several data structures for GTIN as follows:-
1. 8 digit GTIN
2. 12 digit GTIN
3. 13 digit GTIN
4. EAN.UCC -14 Data Structure GTIN
The GTIN Format is defined as the format in which Global Trade Item Numbers®
(GTINs®) must be represented in a 14-digit reference field (key) in computer files to
ensure uniqueness of the identification numbers.
This GDSN Validation document refers to the GTIN format and not the GTIN. In this
way, the GTIN specific Rules reading "If position one in the GTIN Format equals 9
then the field variable measure must be valid" can be supported.
1.2 GLN Validations
The EAN.UCC Global Location Number (GLN) makes possible the unique and
unambiguous identification of physical, functional, and legal entities. The EAN/UCC-13
Data Structure is used for this purpose, and the numbers represented are non-
significant. There is no restriction on the allocation of the same EAN/UCC-13
Identification Number to a trade item and to a location.
In business operations, location numbers are meaningless if they are not associated
with a particular function or purpose. All Element Strings described in this section
indicate the particular function of the GLN represented in the bar code symbol.
Each company or organisation holding an EAN.UCC Company Prefix may assign
GLNs to its own locations. It is the responsibility of the company using the GLNs to
keep business partners informed of all numbers issued as well as the company’s name
and address details. Special care is needed if ownership of the company changes.
The use of GLNs is a pre-requisite for efficient Electronic Data Interchange (e.g.,
EANCOM®). Special procedures may be applied to provide GLNs for small companies
Data Structure is used for this purpose, and the numbers represented are non-
significant. There is no restriction on the allocation of the same EAN/UCC-13
Identification Number to a trade item and to a location.
with a particular function or purpose. All Element Strings described in this section
indicate the particular function of the GLN represented in the bar code symbol.
Each company or organisation holding an EAN.UCC Company Prefix may assign
GLNs to its own locations. It is the responsibility of the company using the GLNs to
keep business partners informed of all numbers issued as well as the company’s name
and address details. Special care is needed if ownership of the company changes.
The use of GLNs is a pre-requisite for efficient Electronic Data Interchange (e.g.,
EANCOM®). Special procedures may be applied to provide GLNs for small companies
or businesses that have not been assigned an EAN.UCC Company Prefix.
In addition to the GLN, the EAN.UCC System provides for a standard data structure to
encode the official postal code of the "ship to" address. Postal codes are normally
maintained by the national postal body in conjunction with the Universal Postal Union
(UPU).
2.4.1 General Rule
The GLN must be unique for each individual location being identified.
EAN.UCC Global Location Numbers (GLNs) can be used to identify anything that can
be addressed (e.g., companies, departments, functions, rooms, factories, shelves,
delivery points, EDI network addresses). A separate unique number is required to
identify each different location. Once assigned at the source (e.g., usually by the party
owning the location), the GLN becomes a unique and universal reference that can be
used by all.
2.4.2 Location Changes
From time to time the details related to an EAN.UCC Global Location Number (GLN)
might change. The location identified by the GLN may change ownership or the
business carried out at one address may be transferred to a new address. The
following are general cases on the use (or re-use) of GLNs due to a change in the
circumstances in which the number was originally established.
If a company (possibly because of liquidation) sells a location to another party who
may or may not be using GLNs, the GLN for the address that is associated with the
previous owner should be closed. If the new owner of the address wishes to identify
the location with a GLN, a new number should be assigned.
If a company closes one address and opens a similar operation at a new address, the
company may either transfer the existing GLN to the new address or assign a new
GLN for the new address. The reason for requesting a new GLN may be that the
owner wants to maintain records on his computer files that show the performance of
the old location. At a later date, this performance may be compared with the
performance of the new location.
If a function identified by a GLN changes, the details associated with the GLN should
be changed by the party responsible for it on the related computer file record.
A GLN that has stopped being used should remain so for at least three years before
being reallocated. The delay must allow time for all references of the old GLN to be
removed from trading partners' files. When the GLN is put into use once again, the
details relating to the new party and/or location must be retransmitted (e.g., using a
®
If a company closes one address and opens a similar operation at a new address, the
company may either transfer the existing GLN to the new address or assign a new
GLN for the new address. The reason for requesting a new GLN may be that the
owner wants to maintain records on his computer files that show the performance of
the old location. At a later date, this performance may be compared with the
performance of the new location.
If a function identified by a GLN changes, the details associated with the GLN should
be changed by the party responsible for it on the related computer file record.
being reallocated. The delay must allow time for all references of the old GLN to be
removed from trading partners' files. When the GLN is put into use once again, the
details relating to the new party and/or location must be retransmitted (e.g., using a
PARTIN EANCOM® message).
DOCUMENT HISTORY
Document Version:
Document Date:
Document Summary
Document Title:
Owner:
Status:
Date of Version Reason for Change

Change:
9-Jun-04 0.0.1 Initial Draft
29-Jun-04 0.0.2 Revised after Task Group review
1-Jul-04 0.0.3 Revised after Task Group review
7-Jul-04 0.0.3 Revised after Task Group review
8-Apr-05 0.0.3 Revised after Task Group review
18-Apr-05 0.0.6 Revised after Task Group motion to progress at Vienna
Physical Meeting Apr-2005
22-Jun-05 0.0.7 Validation Team Review

6-Jul-09 0.0.7 error codes were same for 81, 36, 47
21-Jul-09 0.0.7 GDSN Validations Sub-team Decision
28-Jul-09 0.0.7 Motion by GDSN Validation Sub-Team
28-Jul-09 0.0.7 Motion by GDSN Validation Sub-Team
0.0.7 New Section
0.0.7 New Section
0.0.7 New Section
Oct. 0.0.7 Multi-Source Validation Rules

Nov. 8, 2005 0.0.7 Columns Removed: Rule Classification Name and Formal
Rule Statement
Jan. 24, 2006 1.0.0 Publication document.
Jan. 24, 2006 1.0.1 e-ballot.
3-Mar-06 1.0.2 New Publication for Certification.
18-Apr-06 1.03 Fix overwriting of rule 363

12-Jul-06 1.04 Fix overwriting of rule 347
18-Aug-06 1.0.5 removed rule 347; added new rules (428, price sync) ;
moved rule 325 to Target Market Specific; modified rule
353;
18-Oct-06 1.0.7 Added new rules and newly updated rules
15-Dec-06 1.0.8 Added new rules
28-Jun-07 1.0.9 Added new price synchronization rules; changed to GDSN

BRG approved GDD format; fixed numeric error id in VR
437
Sept. 11, 2007 1.0.10 Added new / modified Price Sync Validation Rules
Nov.29, 2007 1.0.11 Removed Rule 419

12-Jun-08 1.1.0 Changed rule 416 and added 442, 443, and 444.
12-Jun-08 1.1.1 Added Rules 445 and 446
15-Oct-08 1.1.1 Added Error Codes for new rules

5-May-09 1.2.0 New Validation Rules added
28-May-09 1.2.1 New Validation Rules added
20-Jun-09 1.2.2 New Validation Rules added
29-Jul-09 1.2.2 New Validation Rules added

2-Sep-09 1.2.2 New Validation Rules added
HISTORY
1.2.0
5-May-09
ummary
Standard Document for Validation Rules for Global Data
Synchronisation Network
BRG: GDSN / Validations Sub-Team
(Check one box) Draft  Approved
All validation rules in this document have been motioned
to progress by the GDSN BRG (or the previous group the
GDSN Task Group, Validations Sub-Team)
Summary of Model CR #
Change Build #
NA 04-00031
NA 04-00031
NA 04-00031
NA 04-00031
NA 04-00031
Updated Business NA 04-00031
Requirements, added
removed validation rules,
consistent use of error-
code (approved at
Vienna Physical
Meeting)
Added GTIN definitions NA TBD
Changed error codes for NA NA
81, 36, 47
Added GLN / GTIN NA NA
Validation Rules text
Wording modified for NA NA
Rules #106, 107
Addition of rules 341-360 NA NA
and 362
Consistent Use of Error
Code contributed by
Steve Vazzano
GTIN Validations
contributed by Tan Jin
Soon
GLN Validations
contributed by Tan Jin
Soon
Contributed by Nadine
Radomski for the Multi-
Source Sub-Team
No Longer Used NA NA
Renumbered to 1.0.0. NA NA
Added implementation NA NA
dates from e-ballot.
Removed all tabs but
approved, rejected and
target market tabs
because these are
relevant to the working
draft and not the final
standard.
Removed NA NA
Implementation Dates;
removed withdrawn
Multi-Source CRs;
revised #363.
Fixed errata NA NA
Fixed errata NA NA
347 duplicate with rule NA 06-000156; 06-
353; additions, removals, 000176; 06-000102;
moves, modifications 06-000151; 06-
result of eballot August 00066;
2006
Validation Rules 23, 97, CR 06-66; CR06-
98, 104, 105, 325, 353, 155; CR06-156;
428, 429, 430. Rejected: CR06-176; CR06-
394 102; CR 06-183
Error messages VRs, 06-189, 06-190, 06-
Price Sync VRs, 244, 06-183
Dangerous Goods,
revised VR#431 ->437
(already used #)
Validation Rule 438 CR07-146;
Validation Rules 439, CR 237; 07-242

440, 441; 416 changed
Validation Rule 419 CR07-275
Price Maintenance CR 07-375
Release
Trade Item MR3 CR 05-000005, CR
07-000348
Trade Item MR3
Validation Rules 447-456 WO08-230, 08-245,
08-249
08-249
08-249
08-249
Validation Rules 493-498 & WO09-103
504
Acknowledgements
Function Name Company / organisation

Participant Brad Papietro Wegmans
Participant Bruce Hawkins Wal-Mart
Participant Budi Saputra P&G
Participant Colin Robinson Nestle
Participant David Peet eXchangeBridge
Participant Gina Tomassi Pepsi Cola
Participant Grant Kille SA2
Participant Jim Funk SC Johnson
Participant Jim Sheehan Shaw's
Participant Karen Spooner Kraft
Participant Lionel Tussau Georgia-Pacific
Participant Lol Kieran Unilever-UK
Participant Marcel Yska Ahold
Participant Maurol Vecchiotti Johnson & Johnson
Participant Nadine Radomski Dean Foods
Participant Peter Porri Coca-Cola
Participant Randy Mercer LANSA
Participant Sean Lockhead UCCnet
Participant Steve Vazzano Transora
Participant Susan Schmidt-Thomson Fiskars Brands
Participant William Rosenfeld TR2 Consulting
Participant Giovanni Biffi EAN Colombia
Participant Tan Jin Soon EAN Singapore
Participant Robin Kidd Nestle
Participant Carlos Ramos GS1 Mexico
Participant Justin Middleton GS1 Australia
Participant Scott Brown GS1 US
Participant Staffan Olsson GS1 Sweden
Participant John Papadopoulos GS1 Australia
Participant Joanna Stewart GXS
Participant Gabriel Sobrino GS1 Netherlands
Participant Sara Novak GS1 US
Participant Joseph Bohning Purina Nestle
1 General Information
1.1 Problem Statement / Business Need
Distributed Global Validation Rules are required to support the Global Data Synchronisati
process. The scope of this CR addresses the validation of rules that actors in the GDSN
perform. Global Validation Rules are the foundation to ensure that Item data passed with
the Global Data Synchronisation Network conforms to a common structure and complies
global standards.
1.2 Objective
The objective is to define validation rules within the Global Data Synchronisation Network
The validation rules specified in this document are mandatory for parties that make up th
Global Data Synchronisation Network (GDSN); namely, the Global Registry, Source Data
Pools and Recipient Data Pools.
1.3 Audience
The audience of the standards would be any participant in the global supply chain that is
member of the Global Data Synchronization Network. The entities wishing to become a
1.1 Requirements
For the information that details the harmonization of BRADs, BSDs and Schemas to be u
in validation, the reader is referred to the following document:
Harmonization of BRADs, BSDs and Schemas in v2.0.2
validations. The Error Message ID and Error Message (text) specified in the GDSN Valida
rules (approved by the GDSN Task Group vote ending July 15, 2005) must be sent on the
EAN.UCC Exception message when a validation error is detected by the Data Pool or the
Global Registry.
 GDSN Error Codes are sent in the GS1 Exception message using the attribute/tag
<errorCode>.
o The following convention MUST be used in formatting the errorDescriptio
validations. The Error Message ID and Error Message (text) specified in the GDSN Valida
rules (approved by the GDSN Task Group vote ending July 15, 2005) must be sent on the
EAN.UCC Exception message when a validation error is detected by the Data Pool or the
Global Registry.
 GDSN Error Codes are sent in the GS1 Exception message using the attribute/tag
<errorCode>.
o The following convention MUST be used in formatting the errorDescriptio
The content of the errorDescription MUST have the following attributes
appended to the end of the text:
 ATTRIBUTE NAME and
 ATTRIBUTE VALUE
o This will assist the recipient of the error message to identify the cause of th
error.
The following example illustrates the proper format which would be used for application o
Validation Rule 16 – “GTIN (attribute) is required but not provided.”

< errorDescription>”GTIN is required but not provided. attributeName “gtin” attributeValue
“</ errorDescription>
The <errorCode> attribute may contain only the number of the Error Message ID and ma
contain additional characters (such as a prefix).
The <errorDescription> attribute may contain only the message text of the Error Messag
double quotes) attributeName (literal), “Attribute XML Tag Name”, attributeValue (literal)a
“Attribute Value” and may not contain additional characters (such as a prefix).
The data pool (or registry) which detects a GDSN validation error is required to send a
minimum of one error. The data pool may optionally send additional errors if they are dete
1.1 GTIN Validations
The GTIN (Global Trade Item Number) is used for the unique identification of trade items
worldwide. This is specified in the General GS1 Specification section 1.3.1. There are s
data structures for GTIN as follows:-
1. 8 digit GTIN
2. 12 digit GTIN
3. 13 digit GTIN
The GTIN Format is defined as the format in which Global Trade Item Numbers® (GTINs
must be represented in a 14-digit reference field (key) in computer files to ensure unique
of the identification numbers.
This GDSN Validation document refers to the GTIN format and not the GTIN. In this way
GTIN specific Rules reading "If position one in the GTIN Format equals 9 then the field
variable measure must be valid" can be supported.
1. 8 digit GTIN
2. 12 digit GTIN
3. 13 digit GTIN
The GTIN Format is defined as the format in which Global Trade Item Numbers® (GTINs
must be represented in a 14-digit reference field (key) in computer files to ensure unique
of the identification numbers.
This GDSN Validation document refers to the GTIN format and not the GTIN. In this way
GTIN specific Rules reading "If position one in the GTIN Format equals 9 then the field
variable measure must be valid" can be supported.
1.2 GLN Validations
The GS1 Global Location Number (GLN) makes possible the unique and unambi
identification of physical, functional, and legal entities. The GTIN-13 Data Structure is us
this purpose, and the numbers represented are non-significant. There is no restriction
allocation of the same GTIN-13 Identification Number to a trade item and to a location.
particular function or purpose. All Element Strings described in this section indica
particular function of the GLN represented in the bar code symbol.
Each company or organisation holding an GS1 Company Prefix may assign GLNs to it
locations. It is the responsibility of the company using the GLNs to keep business pa
informed of all numbers issued as well as the company’s name and address details. S
care is needed if ownership of the company changes.
The use of GLNs is a pre-requisite for efficient Electronic Data Interchange (e.g., EANC
Special procedures may be applied to provide GLNs for small companies or businesse
have not been assigned an GS1 Company Prefix.
In addition to the GLN, the GS1 System provides for a standard data structure to enco
official postal code of the "ship to" address. Postal codes are normally maintained b
national postal body in conjunction with the Universal Postal Union (UPU).
1.7.1 General Rule
The GLN must be unique for each individual location being identified.
GS1 Global Location Numbers (GLNs) can be used to identify anything that can be addre
(e.g., companies, departments, functions, rooms, factories, shelves, delivery points
network addresses). A separate unique number is required to identify each different loc
Once assigned at the source (e.g., usually by the party owning the location), the
becomes a unique and universal reference that can be used by all.
From time to time the details related to an GS1 Global Location Number (GLN) might ch
The location identified by the GLN may change ownership or the business carried out a
address may be transferred to a new address. The following are general cases on the u
re-use) of GLNs due to a change in the circumstances in which the number was orig
established.
If a company (possibly because of liquidation) sells a location to another party who m
(e.g., companies, departments, functions, rooms, factories, shelves, delivery points
network addresses). A separate unique number is required to identify each different loc
Once assigned at the source (e.g., usually by the party owning the location), the
becomes a unique and universal reference that can be used by all.
From time to time the details related to an GS1 Global Location Number (GLN) might ch
The location identified by the GLN may change ownership or the business carried out a
address may be transferred to a new address. The following are general cases on the u
re-use) of GLNs due to a change in the circumstances in which the number was orig
established.
If a company (possibly because of liquidation) sells a location to another party who m
may not be using GLNs, the GLN for the address that is associated with the previous o
should be closed. If the new owner of the address wishes to identify the location with a G
new number should be assigned.
If a company closes one address and opens a similar operation at a new address
company may either transfer the existing GLN to the new address or assign a new GLN f
new address. The reason for requesting a new GLN may be that the owner wants to ma
records on his computer files that show the performance of the old location. At a later
this performance may be compared with the performance of the new location.
If a function identified by a GLN changes, the details associated with the GLN shou
changed by the party responsible for it on the related computer file record.
reallocated. The delay must allow time for all references of the old GLN to be removed
trading partners' files. When the GLN is put into use once again, the details relating to the
party and/or location must be retransmitted (e.g., using a PARTIN EANCOM®
the Global Data Synchronisation
rules that actors in the GDSN will
sure that Item data passed within
ommon structure and complies with
Data Synchronisation Network.
ory for parties that make up the

e Global Registry, Source Data
the global supply chain that is a

entities wishing to become a
Ds, BSDs and Schemas to be used

ent:
nd Error Messages for GDSN

t) specified in the GDSN Validation
y 15, 2005) must be sent on the
etected by the Data Pool or the GS1
message using the attribute/tag
tag <errorDescription
formatting the errorDescription
nd Error Messages for GDSN
t) specified in the GDSN Validation
y 15, 2005) must be sent on the
etected by the Data Pool or the GS1
message using the attribute/tag
tag <errorDescription
formatting the errorDescription
have the following attributes
ssage to identify the cause of the
would be used for application of

rovided.”
buteName “gtin” attributeValue ””
f the Error Message ID and may not
ssage text of the Error Message (in

Name”, attributeValue (literal)and
s (such as a prefix).
n error is required to send a

additional errors if they are detected.
ue identification of trade items

ion section 1.3.1. There are several
Trade Item Numbers® (GTINs®)

omputer files to ensure uniqueness
and not the GTIN. In this way, the

ormat equals 9 then the field
Trade Item Numbers® (GTINs®)
omputer files to ensure uniqueness
and not the GTIN. In this way, the

ormat equals 9 then the field
sible the unique and unambiguous

e GTIN-13 Data Structure is used for
ficant. There is no restriction on the
trade item and to a location.
ss if they are not associated with a

scribed in this section indicate the
symbol.
y Prefix may assign GLNs to its own

he GLNs to keep business partners
s name and address details. Special
Data Interchange (e.g., EANCOM

small companies or businesses that
andard data structure to encode the

des are normally maintained by the
al Union (UPU).
g identified.
ntify anything that can be addressed
ries, shelves, delivery points, EDI
d to identify each different location.
rty owning the location), the GLN
ed by all.
cation Number (GLN) might change.

p or the business carried out at one
ng are general cases on the use (or
in which the number was originally
cation to another party who may or

ries, shelves, delivery points, EDI
d to identify each different location.
rty owning the location), the GLN
ed by all.
cation Number (GLN) might change.

p or the business carried out at one
ng are general cases on the use (or
in which the number was originally
cation to another party who may or

associated with the previous owner
to identify the location with a GLN, a
operation at a new address, the

address or assign a new GLN for the
be that the owner wants to maintain
of the old location. At a later date,
of the new location.
associated with the GLN should be
puter file record.
or at least three years before being
of the old GLN to be removed from
again, the details relating to the new
PARTIN EANCOM®
GDSN Approved Validation
Approved Current Numeric Rule Description Actor Name Numeric

Date as Rule Status Rule ID Selections: Source Error
Data Pool,
Standard as of Recipient Data Message ID
Approved Pool or GS1
Global Registry
Date:
Selections:
- Approved
Standard
- Marked for
Deletion
- Marked for
Modification
- Effective in
18-Apr-05 Approved 2 Cancel Date must be equal or larger than Source Data Pool 101
Future Release
Standard; Today's Date. This will allow the date to
- Current - In
Current - In Pilot be distributed to the Data Recipient prior
Pilot or
or Production to its effect on the distribution process.
Production
18-Apr-05 Approved 16 The GTIN is missing from the Registry Source Data Pool 1
Standard; Catalogue Item message.
Current - In Pilot
18-Apr-05 Approved
or Production 17 The GTIN Check Digit must be valid. Source Data Pool 2
Standard;
Current - In Pilot
or Production
18-Apr-05 Approved 20 GTIN, GLN and Target Market constitute Global Registry, 4
Standard; the unique key of a Trade Item within the Source Data Pool
Current - In Pilot Global Registry.
or Production
18-Apr-05; Approved 23 Values for mandatory and conditional Source Data Pool 8
revised 09-Mar- Standard; attributes MUST exist in GDSN instance
06; approved 18 Current - In Pilot messages.
Aug. 2006 or Production
18-Apr-05 Approved 28 targetMarketCountryCode MUST BE 3 Source Data Pool, 18

Standard; digit numeric IN LIST ISO 3166-1. GS1 Global
Current - In Pilot Registry
or Production
18-Apr-05 Approved 29 targetMarketSubDivisionCode MUST BE All Senders 19
Standard; IN LIST ISO 3166-2.
Current - In Pilot
or Production
18-Apr-05 Approved 30 targetMarketSubDivisionCode must be All Senders 20

Standard; correctly associated with the appropriate
Current - In Pilot targetMarketCountryCode.
18-Apr-05 Approved 35 The GLN Check Digit MUST be a Valid All Senders 27
or Production
Standard; Check Digit.
Current - In Pilot
or Production
18-Apr-05 Approved 36 GLN of information provider/data source Global Registry, 138
Standard; MUST BE Registered in Global Registry Source Data Pool
Current - In Pilot
or Production
18-Apr-05 Approved 37 GTIN MUST BE present in the Registry Global Registry 102
Standard; Catalogue Item message
Current - In Pilot
or Production
18-Apr-05 Approved 39 classificationCategoryCode MUST BE Source Data Pool, 31
Standard; found in GPC Category List. Recipient Data
Current - In Pilot Pool
or Production
18-Apr-05 Approved 41 A GTIN number cannot be Changed or Global Registry 34
Standard; Corrected if it already exists in the Global
Current - In Pilot Registry.
or Production
18-Apr-05 Approved 42 The dataSource MUST NOT change after Global Registry 35
Standard; the Registry Catalogue Item exists in the
Current - In Pilot Global Registry.
or Production
18-Apr-05 Approved 44 Once the discontinue period has lapsed, Global Registry 37
Standard; the Global Registry cannot set the Cancel
Current - In Pilot Date. The Change by Refresh Command
or Production cannot be used to update this field. Only
the Correct Command can be used.
18-Apr-05 Approved 45 Once the discontinue date has been set, Source Data Pool 38
Standard; the Global Registry cannot change it.
Current - In Pilot The Change by Refresh Command
or Production cannot be used to update this field. Only
the Correct Command can be used.
18-Apr-05 Approved 47 GTIN/GLN/TM record must previously Global Registry 139

Standard; been Registered in order to make
Current - In Pilot changes or corrections using the Registry
or Production Catalogue Item message. A record for
18-Apr-05 Approved 74 cancelDate MUST be
the GTIN/GLN/TM greateronthan
provided the Global Registry 22
Standard; registrationDate
Registry Catalogue Item message does
Current - In Pilot not exist in the GS1 Global Registry.
or Production
18-Apr-05 Approved 76 discontinuedDate MUST be greater than Global Registry 25
Standard; registrationDate
Current - In Pilot
or Production
18-Apr-05 Approved 78 GTIN is required on all Catalogue Item Source Data Pool 29
Standard; Notification messages.
Current - In Pilot
or Production
18-Apr-05 Approved 81 Subscription GTIN MUST exist in Registry Source Data Pool 140
Standard;
Current - In Pilot
or Production
18-Apr-05 Approved 82 Data Recipient GLN MUST exist in Party Global Registry 45
Standard; Registry.
Current - In Pilot
or Production
18-Apr-05 Approved 86 CatalogueItemSubscription MUST contain Global Registry, 50

Standard; one ore more: targetMarket or gtin or Recipient Data
Current - In Pilot classification or GLN Pool
or Production
18-Apr-05 Approved 87 Catalogue Item Subscription MUST not Global Registry, 51
Standard; include classification and gtin Recipient Data
Current - In Pilot Pool
or Production
18-Apr-05 Approved 96 A parent item with a Source Data Pool 95

Standard; tradeItemUnitDescriptor of
Current - In Pilot BASE_UNIT_OR_EACH may not contain
or Production the class
nextLowerLevelTradeItemInformation
4/18/2005' Approved 97 If grossWeight is populated on both Source Data Pool 96
August 22, Standard; parent and child Trade Items, then
2006; CR 06- Current - In Pilot grossWeight of the parent MUST BE
155 or Production greater than or equal to the sum of the
gross weight of all the children except
when special item code =
dynamic_assortment".
4/18/2005' Approved 98 If net weight is populated on both parent Source Data Pool 97
August 22, Standard; and child items, then net weight of the
2006; CR 06- Current - In Pilot parent must be greater than or equal to
155 or Production the sum of the net weight of all the
children except when special item code =
18-Apr-05; Approved 104 <attribute> <value> does not comply with Source Data Pool 9
revised 09-Mar- Standard; attribute value as defined in the current
06; approved 18 Current - In Pilot Business Requirements Document
18-Apr-05; Approved 105 Values must comply with attribute data Source Data Pool 10
revised 09-Mar- Standard; type as defined in the current Business
06; approved 18 Current - In Pilot Requirements Document
25-Aug-05; Modified Approved 106 You can pass a null value when using a Global Registry, 99
28- July-05 and 18-
Apr-05.
Standard; CORRECT command to reset Source Data Pool
Current - In Pilot Discontinue Date or Cancel Date, but you
or Production cannot set the Discontinue Date or
Cancel Date earlier than yesterday's date.
25-Aug-05; Modified
Approved 107 Discontinue Date and Cancel Date cannot Global Registry, 100
28- July-05 and 18-
Apr-05.
Standard; be set on the same item at the same time Source Data Pool
Current - In Pilot
or Production
18-Apr-05 Approved 108 For each supported classification agency Global Registry, 103
Standard; a GTIN may only have one classification Source Data Pool
Current - In Pilot code
or Production
18-Apr-05 Approved 115 Only an originating Data Pool for that Global Registry 110
Standard; party record should be able to change it.
Current - In Pilot
or Production
18-Apr-05 Approved 200 If isTradeItemAnOrderableUnit = True, Source Data Pool 104
Standard; grossWeight must be populated
Current - In Pilot
or Production
18-Apr-05 Approved 201 If grossWeight and netWeight are Source Data Pool 105
Standard; provided on the same record,
Current - In Pilot grossWeight must be greater than or
or Production equal to netWeight
18-Apr-05 Approved 202 Sum of Source Data Pool 106

Standard; quantityofNextLowerLevelTradeItem must
Current - In Pilot equal
or Production totalQuantityOfNextLowerLevelTradeItem
except when special item code =
dynamic_assortment". See the approved
validations rule document for certification
18-Apr-05 Approved 203 Attribute dataRecipient is required to be Source Data Pool 107
Standard; populated on a Catalog Item Notification
Current - In Pilot message.
or Production
18-Apr-05 Approved 204 If isTradeItemADespatchUnit = True then Source Data Pool 108
Standard; grossWeight must be populated
Current - In Pilot
or Production
26-May-05 Approved 205 priceComparisonMeasurement, must Source Data Pool 109

Standard; have a measurement unit matching the
Current - In Pilot values of priceComparisonContentType.
or Production
18-Apr-05 Approved 300 Value for contentOwner must be the GLN Global Registry, 112
Standard; of the dataSource and must be consistent Source Data Pool
Current - In Pilot in all three levels of all messages
or Production
18-Apr-05 Approved 312 isTradeItemAnOrderableUnit must be Source Data Pool, 111

Standard; True for at least one GTIN within a Recipient Data
Current - In Pilot hierarchical configuration Pppl
or Production
18-Apr-05 Approved 314 minimumTradeItemLifespanFromTimeOfProdu Source Data Pool 114
Standard; ction must be greater than or equal to
Current - In Pilot minimumTradeItemLifespanFromTimeOfArrival
or Production
5 Sept. 2006 Approved 325 For the Target Market = 528, the Source Data Pool 141
Standard; percentageOfAlcoholByVolume must be
Current - In Pilot populated for all items on the lowest level
or Production of the hierarchy where
isTradeItemABaseUnit = true and
classificationCategoryCode is a brick in
the 50202200 class except for bricks
10000142
Dec. 11, 2006 Approved 338 If the target market equals “528” Source Data Pool 118
Standard; (Netherlands), "276" (Germany), or "040"
Current - In Pilot (Austria) and the class
or Production tradeItemHazardousInformation exists,
then the
dangerousGoodsRegulationCode in at
least 1 of those occurrences must equal
“ADR”.
Dec. 15, 2006 Approved 339 If the class tradeItemHazardousInformation Source Data Pool 206
Standard; Current - exists and dangerousGoodsRegulationCode
In Pilot or equals “ADR”, then
Production dangerousGoodsPackingGroup, if populated,
must be one of the following values: “I”, “II”,
“III” (Roman numeral 1, 2, or 3)
18-May-05 Approved 341 Start dates cannot occur after their Source Data Pool 116
Standard; corresponding end dates if both dates are
Current - In Pilot populated
or Production
18-May-05 Approved 343 Sender Identifier in Standard Business Source Data Pool, 120
Standard; Document Header must be a valid GLN Recipient Data Pool,
Current - In Pilot Global Registry
or Production
18-May-05 Approved 344 Receiver Identifier in Standard Business Source Data Pool, 121
Standard; Document Header must be a valid GLN Recipient Data Pool,
or Production
18-May-05 Approved 345 EAN.UCC must be used as the ‘Authority’ for Source Data Pool, 122
Standard; Sender and Receiver in Standard Business Recipient Data Pool,
Current - In Pilot Document Header value. Global Registry
or Production
18-May-05 Approved 346 EAN.UCC must be used as the ‘Standard’ Source Data Pool, 123
Standard; Document Identification value in the Standard Recipient Data Pool,
Current - In Pilot Business Document Header Global Registry
or Production
18-May-05 Approved 348 The value of Type in the Standard Business Source Data Pool, 125
Standard; Document Header Document Identification Recipient Data Pool,
Current - In Pilot must be set to a valid EAN.UCC document Global Registry
name.
or Production
26-May-05 Approved 350 Standard Business Document Header Source Data Pool, 127
Standard; Business Scope must present in the response Recipient Data Pool,
Current - In Pilot message Global Registry
or Production
26-May-05 Approved 351 The value of Standard Business Document Source Data Pool, 128
Standard; Header Business Scope type must be GDSN Recipient Data Pool,
or Production
26-May-05 Approved 352 The Value of Source Data Pool, 129
Standard; ‘RequestingDocumentInstanceIdentifier’ must Recipient Data Pool,
Current - In Pilot be the same as the original message instance Global Registry
identifier
or Production
5/26/2005; Approved 353 If the Document contentVersion is provided it Source Data Pool, 130
approved 20 Aug Standard; must match the TypeVersion. Recipient Data Pool,
2006 Current - In Pilot Global Registry
or Production
26-May-05 Approved 354 The same Document ID may not be Source Data Pool, 131
Standard; repeated within the same Command Recipient Data Pool,
or Production
26-May-05 Approved 355 The same Command ID may not be Source Data Pool, 132
Standard; repeated within the same Transaction Recipient Data Pool,
or Production
26-May-05 Approved 356 The same Transaction ID may not be Source Data Pool, 133
Standard; repeated within the same Message Recipient Data Pool,
or Production
26-May-05 Approved 357 The same Document Identification Source Data Pool, 134
Standard; InstanceIdentifier may not be repeated Recipient Data Pool,
Current - In Pilot on multiple messages Global Registry
or Production
26-May-05 Approved 361 General XSD failure - not well formed, not Source Data Pool, 136
Standard; referencing correct namespaces, etc. Recipient Data Pool,
or Production
This rule Approved 362 Minimums cannot be greater than their Source Data Pool 115
modification was Standard; corresponding maximums if both are
proposed on July Current - In Pilot populated
18, 2006
or Production
26-May-05 Approved 363 Must limit to 1 document type per message Source Data Pool, 137
updated 16-Feb- Standard; and 1 command type per transaction. Recipient Data Pool,
06 Current - In Pilot Global Registry
or Production
03-Nov-05 Approved 382 If the class Source Data Pool 158
Standard; nextLowerLevelTradeItemInformation is
Current - In Pilot absent for a catalogue item, the value of
or Production isTradeItemABaseUnit must be "true" for
that catalogue item.
03-Nov-05 Approved 383 If the class Source Data Pool 159

Standard; nextLowerLevelTradeItemInformation is
Current - In Pilot present for a catalogue item the value of
or Production isTradeItemABaseUnit must be "false" for
that catalogue item
18-Apr-05; Approved 385 The Source Data Pool 161
revised 09-Mar- Standard; priceSynchronisationDocumentIdentificati
06 Current - In Pilot on must be unique within a Price
or Production Synchronisation relationship.
20-Apr-06 Approved 386 The Source Data Pool 162

Standard; priceSynchronisationDocumentIdentificati
Current - In Pilot on must be sequential within a Price
or Production Synchronisation relationship.

Standard; priceSynchronisationRelationshipIdentific
Current - In Pilot ation must be unique within a data source
or Production in Price Synchronisation.
23-Mar-06 Approved 388 The Source Data Pool is required to Source Data Pool 164
Standard; enforce the enumeration list in the BRAD
Current - In Pilot for Price Synchronization code lists.
or Production

Current - In Pilot ation in the Relationship Segment must
or Production be equal to the Relationship ID in the
price synchronization header.
20-Apr-06 Approved 390 The Currency code must be the 3 Source Data Pool 166
Standard; character representation found in the ISO
Current - In Pilot 4217 list.
or Production
20-Apr-06 Approved 391 The Language code must be the 2-5 Source Data Pool 167
Standard; character representation found in the ISO
Current - In Pilot 639 list.
or Production
20-Apr-06 Approved 392 If IncotermCodeLocation is populated, the Source Data Pool 168
Standard; IncotermCode must also be populated.
Current - In Pilot
or Production
Standard; priceSynchronizationConditionIdentificatio
Current - In Pilot n must be unique within a data source in
or Production Price Synchronization.
20-Apr-06 Approved 395 If ConditionType = bracket, must provide Source Data Pool 171
Standard; both bracket tier minimum and bracket
Current - In Pilot range qualifier.
or Production
20-Apr-06 Approved 397 In the condition segment, if Information Source Data Pool 173
Standard; Provider, GTIN, Target Market Country
Current - In Pilot Code and Target Market Subdivision
or Production Code are populated, then Classification
Category Code cannot be populated.
20-Apr-06 Approved 398 If populated, the Classification Category Source Data Pool 174
Standard; Code must be a valid GPC value that has
Current - In Pilot been implemented in GDSN.
or Production
20-Apr-06 Approved 401 conditionApplicationSequence is Source Data Pool 177
Standard; populated only if the Condition Type is
Current - In Pilot equal to Allowance or Charge.
or Production
20-Apr-06 Approved 402 If the conditionApplicationSequence is Source Data Pool 178
Standard; populated, it must be greater than 1.
Current - In Pilot
or Production
20-Apr-06 Approved 403 The ItemPriceTypeSegmentIdentification Source Data Pool 179
Standard; must be unique within an information
Current - In Pilot provider in Price Synchronization.
or Production
20-Apr-06 Approved 405 If multiple business location ship froms Source Data Pool 182
Standard; exist, there can be only 1 business
Current - In Pilot location ship to.
or Production
20-Apr-06 Approved 406 If multiple business location ship tos exist, Source Data Pool 183
Standard; there can be only 1 business location ship
Current - In Pilot from.
or Production
20-Apr-06 Approved 407 The Target Condition must be unique Source Data Pool 184
Standard; within an information provider in Price
Current - In Pilot Synchronization.
or Production
20-Apr-06 Approved 408 If populated, the Target Condition must Source Data Pool 185
Standard; have an effective end date value that is
Current - In Pilot not in the past.
or Production
20-Apr-06 Approved 409 The Target Condition must be in the Source Data Pool 186
Standard; accept, synchronize or review status in
Current - In Pilot the price sync list except for First Initial
or Production Load.
20-Apr-06 Approved 410 If the Target Condition Type is populated, Source Data Pool 187
Standard; then Target Price Type cannot be
Current - In Pilot populated.
or Production
20-Apr-06 Approved 411 If the Target Condition is referenced, it Source Data Pool 188
Standard; must be of type = bracket.
Current - In Pilot
or Production
20-Apr-06 Approved 412 If the Target Condition is populated, the Source Data Pool 189
Standard; bracket tier minimum, bracket tier
Current - In Pilot maximum, bracket range qualifier and
or Production bracket operator for the Item Price Type
cannot be populated.
20-Apr-06 Approved 413 The TargetPriceType must be unique Source Data Pool 190
Standard; within a information provider in Price
Current - In Pilot Synchronization.
or Production
20-Apr-06 Approved 414 If populated, the effectiveEndDate in the Source Data Pool 191
Standard; TargetPriceType cannot have a date that
Current - In Pilot is in the past.
or Production
20-Apr-06 Approved 415 The TargetPriceType must be in the Source Data Pool 192
Standard; accept, synchronize or review status in
Current - In Pilot the price sync list except for First Initial
or Production Load.
4-Sept. 2007 Approved 416 If the TargetPriceType is populated, the Source Data Pool 193
Standard; Price Type Code must be equal to
Current - In Pilot Allowance, Charge, Promotional Price or
or Production any of the Transaction Price Types
identified by the word TRANSACTION in
the code list value.
20-Apr-06 Approved 417 If the TargetPriceType is referenced, the Source Data Pool 194
Standard; PriceType code of that TargetPriceType
Current - In Pilot must not be Allowance or Charge.
or Production
20-Apr-06 Approved 420 All PriceTypes, other than PriceType = Source Data Pool 197
Standard; ‘Allowance’ or ‘Charge’, must be assigned
Current - In Pilot a PriceTypeApplicationSequence = 1.
or Production
20-Apr-06 Approved 421 ConditionApplicationSequence = 1 is not Source Data Pool 198
Standard; a valid Application Sequence for
Current - In Pilot Summary Conditions.
or Production
Standard; priceSynchronisationDocumentIdentificati
Current - In Pilot on must be present and unique within a
or Production information provider in Price
Synchronization.
20-Apr-06 Approved 423 Within the header, the Source Data Pool 200
Current - In Pilot ation must be present and unique within
or Production a information provider in Price
Synchronization.
20-Apr-06 Approved 424 Both Reason Code and ActionNeeded Recipient Data 201
Standard; must be provided if both fields are Pool
Current - In Pilot conditional on the
or Production priceSynchronisationConfirmationStatusR
eason being "REVIEW".
Standard; PriceSynchronisationRelationshipIdentific
Current - In Pilot ation included in the
or Production PriceSynchronisationConfirmation must
reference an existing Price
Synchronisation Relationship identified by
a
priceSynchronsiationRelationshipIdentific
ation.
Standard; PriceSynchronisationConditionIdentificati
Current - In Pilot on included in the
or Production PriceSynchronisationConfirmation must
reference an existing Price
Synchronisation Condition identified by a
priceSynchronsiationConditionIdentificatio
n..
20-Apr-06 Approved 427 The itemPriceTypeSegmentIdentification Source Data Pool 204

Standard; included in the
Current - In Pilot PriceSynchronisationConfirmation must
or Production reference an existing Item Price Type
Segment identified by a
itemPriceTypeSegmentIdentification.
July 18, 2006; Approved 428 If populated, Source Data Pool, 205
CR 06-102; Standard; percentageOfAlcoholByVolume or Recipient Data Pool
approved 20 Aug Current - In Pilot fatPercentageInDryMatter, must be
2006 or Production greater than or equal to 0.00 and smaller
than or equal to 100.00 by definition.
Aug. 22, 2006; Approved 429 The receiving data pool can fail optional Recipient Data 207
CR 06-183 Standard; messages within the network that are not Pool
Current - In Pilot supported by the receiving data pool.
or Production The scope of this rule is the document
type, therefore, extensions to an existing
document cannot be failed.
Aug. 22, 2006 Approved 430 The receiving party can fail message Source Data 999
Standard; within GDSN network that fails GDSN Pool,Recipient
Current - In Pilot choreography and synchronization rules. Data Pool,Global
or Production Registry
10-Oct-06 Approved 431 If condition type = "bracket", then Source Data Pool 208
Standard; Condition Value, Condition Value Type,
Current - In Pilot Qualifier, Basis Quantity, Basis Quantity
or Production UOM, and Application Sequence cannot
be populated.
10-Oct-06 Approved 432 If Condition Type = bracket, then at least Source Data Pool 209
Standard; one bracket qualifier sub-class must be
Current - In Pilot provided.
or Production
10-Oct-06 Approved 433 In the condition segment, if classification Source Data Pool 210
Standard; category code is populated, then,
Current - In Pilot Information Provider, GTIN, Target Market
or Production Country Code and Target market
Subdivision Code cannot be populated.
10-Oct-06 Approved 434 If the Target Price Type is populated, then Source Data Pool 211
Standard; Target Condition Type cannot be
Current - In Pilot populated.
or Production
10-Oct-06 Approved 435 If you provide more than one bracket Source Data Pool 212
Standard; qualifier in a Condition segment, then the
Current - In Pilot bracket operators must either be all "and"
or Production or all "or".
10-Oct-06 Approved 436 If you provide more than one bracket Source Data Pool 213
Standard; qualifier in a Item Price Type segment,
Current - In Pilot then the bracket operators must either be
or Production all "and" or all "or".
Dec. 15, 2006 Approved 437 If the class tradeItemHazardousInformation Source Data Pool 215
Standard; exists and dangerousGoodsRegulationCode
Current - In Pilot equals “ADR”, then classOfDangerousGoods
must be one of the following values: "1", "2",
or Production
"3", "4.1", "4.2", "4.3", "5.1", "5.2", "6.1", "6.2",
"7", "8", "9"
25-Jun-07 Approved 438 The Content Owner GLN within the Price Source Data Pool 214
Standard; Synchronization message must contain
Current - In Pilot the same GLN value as found at the
or Production relationship segment id.
4-Sept. 2007 Approved 439 The price data is not valid for price Source Data Pool 216
Standard; synchronization because the recipient
Current - In Pilot previously rejected the relationship and it
or Production is in reject state.
4-Sept. 2007 Approved 440 A reject response to a trade item price Source Data Pool 217
Standard; type segment indicates that the recipient
Current - In Pilot no longer wishes to receive any price type
or Production segment related to that catalogue trade
item. As a result no subsequent pricing
can be made on that trade item in the
reject state.
4-Sept. 2007 Approved 441 It is invalid to send a reject on a condition Source Data Pool 218
Standard; segment.
Current - In Pilot
or Production
3-Sep-08 Approved 442 If the Price Document Type = RESTART, Source Data Pool 219
Standard; the Synchronisation Header Action Code
Current - In Pilot must = ‘CHANGE_BY_REFRESH’ and all
or Production - Item Price Types sent must have a
For MR3 segment Action Code equal to ADD.
Release
3-Sep-08 Approved 443 If a Price Synchronisation Source Data Pool 220

Standard; confirmationStatusReasonCode or action
Current - In Pilot Needed is provided
or Production - priceSynchronisationConfirmationStatus
For MR3 must be in the status of "REVIEW".
Release
3-Sep-08 Approved 444 A PriceSynchronisationConfirmation for a Source Data Pool 221
Standard; segment is not valid when a previous
Current - In Pilot PriceSynchronisationConfirmation has
or Production - been received for that segment with a
For MR3 priceSynchronisationConfirmationStatus
Release of REJECTED.
3-Sep-08 Approved 445 Source Data Pool 222

Standard;
Current - In Pilot
or Production -
For MR3
Release
The value in
tradeItemCountryOfLastProcessing
MUST be 3 digit numeric and in the ISO
3166-1 code.
3-Sep-08 Approved 446 Source Data Pool 223
Standard;
Current - In Pilot
or Production -
For MR3 If tradeItemCompositionWidth,
Release tradeItemCompositionDepth and
quantityOfCompleteLayersContainedInAT
radeItem are all supplied, the product of
the three attributes should equal the
totalQuantityOfNextLowerLevelTradeItem.
should equal the
totalQuantityOfNextLowerLevelTradeItem.
8-Apr-09 Approved 447 All GS1 system keys that are defined to Source Data Pool, 224
Standard have check digits must have a valid check Global Registry
digit.
8-Apr-09 Approved 448 All GS1 system keys that are defined to Source Data Pool, 225
Standard have check digits must have a valid check GS1 Global
digit. Registry
8-Apr-09 Approved 449 A Change_By_Refresh cannot be used to Source Data Pool 226
Standard modify the netContent. GTIN allocation
rules must be followed independent of
data source, data recipient and target
market.
Standard modify the value for
priceComparisonMeasurement. GTIN
allocation rules must be followed
independent of data source, data
recipient and target market.
Standard modify the value for brandName.
Additional information as VIM to VIM
CITRUS is OK. GTIN allocation rules
must be followed independent of data
source, data recipient and target market.
Standard modify the value for
totalQuantityOfNextLowerLevelTradeItem
is not allowed to be changed. GTIN
allocation rules must be followed
independent of data source, data
recipient and target market.
Standard modify the value for childTradeItem
GTIN. childTradeItem GTIN is not allowed
to be changed. GTIN allocation rules
must be followed independent of data
source, data recipient and target market.
8-Apr-09 Approved 454 A GTIN cannot be a child of itself. Source Data Pool 231
Standard
8-Apr-09 Approved 455 A GTIN can appear in a lower level only Source Data Pool 232
Standard under a different parent.
8-Apr-09 Approved 456 isPriceOnPack may only be true if Source Data Pool
Standard isTradeItemAConsumerUnit = true. 233
14-May-09 Approved 457 Within each hierarchy one or more Source Data Pool
Standard trade items must have
'isTradeItemAnInvoiceUnit' equals
true 234
14-May-09 Approved 458 For a given Price ID, Source Data Pool 235
Standard priceTypeEffectiveEndDateContext and
priceTypeEffectiveStartDateContext are
allowed to repeat. However, the repeat
can only be from the remaining un-used
code values
14-May-09 Approved 459 If provided priceTypeEffectiveEndDate Source Data Pool 236
Standard must be greater than or equal to Today's
date, i.e. Today()
14-May-09 Approved 460 priceValue must be provided and value Source Data Pool 237
Standard must be greater than or equal to 0
14-May-09 Approved 461 If alternateLocationGrouping is not null, Source Data Pool 238
Standard then targetMarketSubdivisionCode and
shipTo must be null
14-May-09 Approved 462 priceValueType must be provided; allow Source Data Pool 239
Standard PERCENTAGE or VALUE
14-May-09 Approved 463 Price Action Reason Code Must be Source Data Pool 240
Standard provided
20-Jun-09 Approved 464 Description must be identical for all items Source Data Pool 241
Standard with the same Trade Item Group ID
20-Jun-09 Approved 465 packagingMaterialCode and Source Data Pool 242

Standard packagingMaterialCompositionQuantity are
used in pairs. I.e. if one is populated the other
one must be populated, too.
20-Jun-09 Approved 466 Zero or negative values are not allowed Source Data Pool 243
Standard for
packagingMaterialCompositionQuantity
20-Jun-09 Approved 467 Source Data Pool 244

Standard
Catalogue Price is mandatory if
isTradeItemAnOrderableUnit = true and
documentCommand = ADD
20-Jun-09 Approved 468 For items with isTradeItemABaseUnit = true, Source Data Pool 245
Standard packagingMaterialCode and
packagingMaterialCompositionQuantity are
mandatory unless:
Alternative 1: The item has the
packagingTermsAndCondition = 12 (package
recycling fee paid).
isPackagingMarkedReturnable = true .
packagingTypeCode = NE (not packed) (Verify
the latest code for not packed packaging type )
20-Jun-09 Approved 469 For Tarket Market 528 (Netherlands) Source Data Pool, 246
Standard internal (restricted distribution) Recipient Data
GTINs can not be used (i.e. codes Pool
begining with: 0020-0029, 0040-
0049, 0200-0299).
20-Jun-09 Approved 471 Must be a valid GTIN-8, GTIN-12, Source Data Pool 247
Standard GTIN-13 or GTIN-14 number,
expressed as a 14-digit number with
vaild check digit
20-Jun-09 Approved 472 The Trade Item Declaration item hierarchy Source Data Pool 249
Standard must be consistent. Observe that there can be
more than one Trade Item at all levels except
the top of the hierarchy.
20-Jun-09 Approved 473 if isTradeItemPacked Irregularly = False then Source Data Pool 250
Standard Value in quantityofNextLowerLevelTradeItem
must be equal to value in
quantityOfCompleteLayersContainedInATradeI
tem multiplied by value in
quantityOfTradeItemsContainedInACompleteL
ayer
29-Jul-09 Approved 475 The Target Market Country Code and Source Data Pool 252
Standard when populated the
targetMarketSubdivisionCode, must be
consistent within a hierarchy. A higher
level TM subdivision code is a valid
Subdivision code for the TMs of all its
lower levels. A lower level cannot be
more specific than the higher level. Ex. 1
VALID: CA - 840-TN EA - 840-TN ; Ex. 2
NOT VALID: CA - 840 EA - 840-TN ; Ex
3 VALID: CA - 840-TN EA – 840; Ex 4
VALID CA - 840 EA - 840
29-Jul-09 Approved 476 grossWeight must be greater than or Source Data Pool 253
Standard equal to netWeight
29-Jul-09 Approved 477 Unit of measure for Source Data Pool 254
Standard storageHandlingTemperatureMaximum,
storageHandlingTemperatureMinimum and
flashPointTemperature may only be degrees
Celsius (CEL).
29-Jul-09 Approved 478 If nestingIncrement is populated it must be Source Data Pool 255
Standard greater than zero(0).
29-Jul-09 Approved 479 For TM 528 (Netherlands) the value of Source Data Pool, 256
Standard stacking factor can not be more than 99. Recipient Data
Pool
29-Jul-09 Approved 480 For TM 528 (Netherlands) the value of the Source Data Pool, 257
Standard stacking factor of the non-GTIN logistic Recipient Data
unit can not be more than 99. Pool
29-Jul-09 Approved 481 For TM 528 (Netherlands) the value of Source Data Pool, 258
Standard layers per pallet can not exceed 999. Recipient Data
Pool
29-Jul-09 Approved 483 endAvailabilityDateTime must be after Source Data Pool 260
Standard yesterday's date.
29-Jul-09 Approved 485 discontinuedDate can only be updated when Source Data Pool 262
Standard documentCommand = CORRECT.
29-Jul-09 Approved 488 lastChangeDateTime for a trade item must be the Source Data Pool 265
Standard same or later than previously sent value
29-Jul-09 Approved 489 tradeItemCountryOfOrigin must be the 3 digit 266

Standard numeric representation found in the ISO 3167-
1 list.
29-Jul-09 Approved 490 When netcontent is provided, its Source Data Pool 267
Standard associated unitOfMeasure must be from
the Unit Of Measure Code List from the
Trade Item Standard.
29-Jul-09 Approved 491 storageHandlingHumidityMaximum and Source Data Pool 268

Standard storageHandlingHumidityMinimum using
percentage must have a value between 0 and
100.
9/2/2009 (not in Approved 493 There is a limit of 100 Transactions within 1 Source Data Pool, 270
MR-4) Standard Message Recipient Data Pool,
GS1 Global Registry
9/2/2009 (not in Approved 494 There is a limit of 1 Command type within 1 Source Data Pool, 271
MR-4) Standard Transaction Recipient Data Pool,
GS1 Global Registry
9/2/2009 (not in Approved 495 There is a limit of 100 Documents within 1 Source Data Pool, 272
MR-4) Standard Transaction Recipient Data Pool,
GS1 Global Registry
9/2/2009 (not in Approved 496 There is a limit of 1 Message within a Standard Source Data Pool, 273
MR-4) Standard Business Document Recipient Data Pool,
GS1 Global Registry
9/2/2009 (not in Approved 497 GLN for sender in Standard Business Source Data Pool, 274
MR-4) Standard Document Header and content owner at Recipient Data Pool,
message level must be the same. GS1 Global Registry
9/2/2009 (not in Approved 498 Header version in Standard Business Source Data Pool, 275
MR-4) Standard Document Header must be the current version Recipient Data Pool,
approved for the network GS1 Global Registry
02-Sep-09 Approved 504 Maximum number of occurrences of Source Data Pool 281
Standard GDSNTradeItemClassificationAttributeTyp
e is 25
Approved Validation Rules
Error Message Business Process Attribute Name Geopolitical

Description (Message Name) Selections: Global,
Target Market Name
cancelDate must be equal or larger Register Catalogue Item cancelDate Global

than Today's Date.
GTIN is required but not provided. Register Catalogue Item gtin Global
GTIN checksum failed. Register Catalogue Item gtin Global

GTIN already exists in GDS Global Register Catalogue Item gtin, dataSource, targetMarket Global
Registry.
Please check the contents of XML All GDSN Messages As defined in the current Business Global
that was sent. Missing element Requirements Document. (*Caution: Not all
attributes have defined lengths in the BSD.
Schemas enforce some restrictions, but
these are not always documented in the
BSD, making enforcement of this
targetMarketCountryCode is a not a Registry Catalogue Item, Validation Rule not complete or consistent. Global
targetMarketCountryCode
valid Country Code Request For Catalogue Item GS1 SD notified on Mar 22, 2006.)
Notification
targetMarketSub-DivisionCode is a Register Catalogue Item, targetMarketSubDivisionCode Global

not a valid Subdivision Code Request For Catalogue Item
Notification
targetMarketSubDivisionCode is not Catalogue Item Subscription, targetMarketSubDivisionCode, Global

valid with the Registry Catalogue Item targetMarketCountryCode
targetMarketCountryCode.
GLN checksum failed Request For Catalogue Item gln Global
Notification
GLN of information provider/data Register Catalogue Item dataPool, dataSource, Global

source does not exist registryCatalogueIemIdentification,
entityIdentification, PartyIdentification, gln
GTIN not present in the Registry Register Catalogue Item gtin Global
Catalogue Item message
Invalid category Register Catalogue Item, classificationCategoryCode Global
Catalogue Item Subscription,
Request For Catalogue Item
Notification, Catalogue Item
GTIN number cannot changed or Register Catalogue Item
Notification gtin Global
cannot be corrected
Data Source GLN cannot change Register Catalogue Item dataSource, gln Global
Cancel date cannot change; must Register Catalogue Item cancelDate Global
be corrected
Discontinued date cannot change; Register Catalogue Item discontinuedDate Global

must be corrected
GLN, GTIN, Target Market Key Register Catalogue Item gtin, dataSource, targetMarket Global
does not exist in the Global Registry
Cancel Date must be after Register Catalogue Item cancelDate Global

Registration Date
Discontinued Date must be after Register Catalogue Item discontinuedDate, registrationDate Global
Registration Date
GTIN is required Catalogue Item Notification gtin Global
GTIN does not exist Catalogue Item Subscription gtin Global
Data Recipient GLN does not exist Catalogue Item Subscription, dataRecipient, gln Global
Request for Notification
(RFCIN)
Data Recipient needs to provide at Catalogue Item Subscription gtin, dataSource GLN, targetMarket, Global
least one key attribute (GTIN, classificationCategoryCode
Category, Target Market or Data
Source GLN)
Category code and gtin cannot be Catalogue Item Subscription gtin, classificationCategoryCode Global
an input together
A parent item with a Catalogue Item Notification tradeItemUnitDescriptor, Global

tradeItemUnitDescriptor of nextLowerLevelTradeItemInformation
BASE_UNIT_OR_EACH may not
contain the class
nextLowerLevelTradeItemInformatio
n
If grossWeight is populated on both Catalogue Item Notification grossWeight Global
parent and child Trade Items, then
grossWeight of the parent MUST
BE greater than or equal to the sum
of the gross weight of all the
children except when special item
code = dynamic_assortment".
If net weight is populated on both Catalogue Item Notification netWeight Global
parent and child items, then net
weight of the parent must be
greater than or equal to the sum of
the net weight of all the children
except when special item code =
<attribute> <value> does not All GDSN Messages As defined in the current Business Global
comply with attribute value as Requirements Document. (*Caution: Not all
defined in the current Business attributes have defined lengths in the BSD.
Requirements Document Schemas enforce some restrictions, but
Validation Rule not complete or consistent.
GS1 SD notified on Mar 22, 2006.)
Values do not comply with attribute All GDSN Messages As defined in the current Business Global
data type as defined in the current Requirements Document. (*Caution: Not all
Business Requirements Document attributes have defined lengths in the BSD.
Schemas enforce some restrictions, but
Validation Rule not complete or consistent.
GS1 SD notified on Mar 22, 2006.)
The Discontinue Date or Cancel Register Catalogue Item Register Catalogue Item Global
Date was set with a date earlier DiscontinuedDate, CancelDate (*The rule
than yesterday's date. applies to both dates. Data Pools must
ensure that they are populated with a valid
date. Time should not be used in
validation.)
The Discontinue Date and the Register Catalogue Item, Catalogue Item Notification CatalogueItem Global
Cancel Date were both set for the Catalogue Item Notification DiscontinueDate, CancelDate; Catalogue
same item or the CatalogueItem Item Notification TradeItem
and TradeItem Discontinue Dates DiscontinueDate, CancelDate; Registry
and each
For Cancel Dates were
supported not the
classification Catalogue Item Notification Catalogue Item DiscontinuedDate,
additionalClassificationCategoryCode Global
same. a GTIN may only have one
agency CancelDate (*The rule applies to all dates.
classification code Data Pools must ensure that they are
populated with the same date. Time should
not be used in validation.)
Only an originating Data Pool for Basic Party Sync GLN Global
that party record should be able to
change it
If isTradeItemAnOrderableUnit = Catalogue Item Notification isTradeItemAnOrderableUnit, grossWeight Global

True, grossWeight must be
populated
If grossWeight and netWeight are Catalogue Item Notification grossWeight, netWeight Global
provided on the same record,
grossWeight must be greater than
or equal to netWeight
Sum of Catalogue Item Notification quantityofNextLowerLevelTradeItem, Global

quantityofNextLowerLevelTradeItem totalQuantityOfNextLowerLevelTradeItem
must equal
totalQuantityOfNextLowerLevelTrad
eItem except when special item
code = dynamic_assortment". See
the approved validations rule
document for certification
Attribute dataRecipient is required Catalogue Item Notification dataRecipient Global
to be populated on a Catalog Item
Notification message.
If isTradeItemADespatchUnit = True Catalogue Item Notification isTradeItemADespatchUnit, grossWeight Global

then grossWeight must be
populated
priceComparisonMeasurement, Catalogue Item Notification priceComparisonMeasurement, Global

must have a measurement unit priceComparisonContentType
matching the values of
priceComparisonContentType.
Value for contentOwner must be the Register Catalogue Item, contentOwner, dataSource Global
GLN of the dataSource and must Catalogue Item Notification,
be consistent in all three levels of all Catalogue Item Registration
messages Response, EAN.UCC
Exception and GDSN
Response
isTradeItemAnOrderableUnit must Catalogue Item Notification isTradeItemAnOrderableUnit Global

be True for at least one GTIN within
a hierarchical configuration
minimumTradeItemLifespanFromTimeO Catalogue Item Notification minimumTradeItemLifespanFromTimeOfProduct Global

fProduction must be greater than or ion,
equal to minimumTradeItemLifespanFromTimeOfArrival
minimumTradeItemLifespanFromTimeO
fArrival
For the Target Market = 528, the Catalogue Item Notification percentageOfAlcoholByVolume, Netherlands
percentageOfAlcoholByVolume isTradeItemABaseUnit
must be populated for all items on
the lowest level of the hierarchy
where isTradeItemABaseUnit = true
and classificationCategoryCode is a
brick in the 50202200 class except
for bricks 10000142
If the target market equals “528” Catalogue Item Notification dangerousGoodsRegulationCode Austria, Germany,
(Netherlands), "276" (Germany), or Netherlands
"040" (Austria) and the class
tradeItemHazardousInformation
exists, then the
dangerousGoodsRegulationCode in
at least 1 of those occurrences
must equal “ADR”.
If the class Catalogue Item Notification dangerousGoodsPackingGroup. Dependent Global

tradeItemHazardousInformation exists upon Change Request CR 06-000277 which
and dangerousGoodsRegulationCode states: In fMCGTradeItemExtension, change the
equals “ADR”, then FMCGTradeItemExtensionType elements
dangerousGoodsPackingGroup, if fMCGTradeItemMeasurements and
populated, must be one of the following fMCGTradeItemMarking and in
values: “I”, “II”, “III” (Roman numeral 1, FMCGTradeItemMarkingType the elements
2, or 3) isIngredientIrradiated isRawMaterialIrradiated,
isTradeItemGeneticallyModified,
isTradeItemIrradiated from mandatory to
optional.
Start dates cannot occur after their Catalogue Item Notification campaignEndDate, Global
corresponding end dates if both campaignStartDate,
dates are populated depositValueEffectiveDate,
depositValueEndDate,
effectiveStartDate,
effectiveEndDate,
endAvailabilityDateTime,
endDateMaximumBuyingQuantity,
endDateMinimumBuyingQuantity,
firstOrderDate,
firstShipDate,
lastOrderDate,
lastShipDate,
seasonalAvailabilityEndDate,
seasonalAvailabilityStartDate,
startAvailabilityDateTime,
startDateMaximumBuyingQuantity,
startDateMinimumBuyingQuantity,
Sender Identifier must be a valid GLN All GDSN Messages Sender/Identifier Global
Receiver Identifier must be a valid GLN All GDSN Messages Receiver/Identifier Global
The ‘Authority’ value in Sender and All GDSN Messages Sender/Authority and Receiver/Authority Global
Receiver must be set to EAN.UCC.
The Document Identification Standard All GDSN Messages Document Identification/Standard Global
value must be set to EAN.UCC.
The value of Type must be set to a All GDSN Messages Document Identification/Type Global
valid EAN.UCC document name.
Business Scope must present in the All GDSN Messages BusinessScope Global
response or exception message
The value of Business Scope type must All GDSN Messages BusinessScope/Type Global
be set to GDSN
Value of CorrelationInformation All GDSN Messages CorrelationInformation/ Global

RequestingDocumentInstanceIdentifier RequestingDocumentInstanceIdentifier
is not recognized, it must be original
message instance identifier
If the Document contentVersion is All GDSN Messages Document Identification/TypeVersion , Global

provided it must match the TypeVersion. contentVersion
The same Document ID may not be All GDSN Messages Document ID Global
repeated within the same
Command
The same Command ID may not All GDSN Messages Command ID Global
be repeated within the same
Transaction
The same Transaction ID may not All GDSN Messages Transaction ID Global
be repeated within the same
Message
The same Document Identification All GDSN Messages Document Identification InstanceIdentifier Global
InstanceIdentifier may not be
repeated on multiple messages
General XSD failure - not well All GDSN Messages N/A Global
formed, not referencing correct
namespaces
Minimums cannot be greater than their Catalogue Item Notification; [from BRAD 7.7] Catalogue Item Global
corresponding maximums Price Synchronisation Notification
Document agreedMaximumBuyingQuantity,
agreedMinimumBuyingQuantity,
deliveryToDistributionCenterTemperatureM
aximum,
deliveryToDistributionCenterTemperatureMi
nimum,
deliveryToMarketTemperatureMaximum,
deliveryToMarketTemperatureMinimum,
orderQuantityMaximum,
orderQuantityMinimum,
storageHandlingTemperatureMaximum,
storageHandlingTemperatureMinimum,
storageHandlingHumidityMaximum,
storageHandlingHumidityMinimum;
from Price Synchronisation Document
bracketTierMaximum,
bracketTierMinimum
Must limit to 1 document type per All GDSN Messages N/A Global
message and 1 command type per
transaction.
If the class Catalogue Item Notification isTradeItemABaseUnit Global

n is absent for a catalogue item, the
value of isTradeItemABaseUnit
must be "true" for that catalogue
item.
If the class Catalogue Item Notification isTradeItemABaseUnit Global

n is present for a catalogue item the
value of isTradeItemABaseUnit
must be "false" for that catalogue
item
The Price Synchronisation priceSynchronisationDocumentIdentificatio Global
priceSynchronisationDocumentIden Document n
tification is not unique for this
relationship in Price
Synchronisation.

priceSynchronisationDocumentIden Document n
tification is not sequential for this
Price Synchronisation relationship.
The Price Synchronisation priceSynchronisationRelationshipIdentificat Global

priceSynchronisationRelationshipId Document ion
entification is not unique within this
data source in Price
Synchronisation.
The enumeration list in the BRAD Price Synchronisation All enumeration lists in Price Global
for Price Synchronisation is not Document Synchronization
properly applied.

priceSynchronisationRelationshipId Document ion
entification in the Relationship
Segment and the Relationship ID in
the price synchronization header
are not equal.
The Currency code must be the 3 All GDSN Messages currency Global
character representation found in
the ISO 4217 list.
The Language code must be the 2- All GDSN Messages language code Global
5 character representation found in
the ISO 639 list.
If IncotermCodeLocation is Price Synchronisation IncotermCode, IncotermCodeLocation Global
populated, the IncotermCode must Document
also be populated.
The Price Synchronisation priceSynchronisationConditionIdentification Global

priceSynchronizationConditionIdenti Document
fication is not unique within this data
source in Price Synchronization.
If ConditionType = bracket, must Price Synchronisation conditionType Global

provide both bracket tier minimum Document
and bracket range qualifier.
In the condition segment, if Price Synchronisation classificationCategoryCode Global

Information Provider, GTIN, Target Document
Market Country Code and Target
Market Subdivision Code are
populated, then Classification
Category Code cannot be
populated.
If populated, the Classification All GDSN Messages Classification Category Code Global
Category Code must be a valid
GPC value that has been
implemented in GDSN.
conditionApplicationSequence is Price Synchronisation conditionApplicationSequence Global
populated and the Condition Type Document
does not equal Allowance or
Charge.
If the conditionApplicationSequence Price Synchronisation conditionApplicationSequence Global
is populated, it must be greater than Document
1.
The Price Synchronisation ItemPriceTypeSegmentIdentification Global
ItemPriceTypeSegmentIdentification Document
must be unique within an
information provider in Price
Synchronization.
If multiple business location ship Price Synchronisation shipFrom, shipTo Global
froms exist, there can be only 1 Document
business location ship to.
If multiple business location ship tos Price Synchronisation shipFrom, shipTo Global
exist, there can be only 1 business Document
location ship from.
The Target Condition must be Price Synchronisation Target Condition Global

unique within an information Document
provider in Price Synchronization.
If populated, the Target Condition Price Synchronisation Target Condition Global

must have an effective end date Document
value that is not in the past.
The Target Condition must be in the Price Synchronisation Target Condition Global
accept, synchronize or review Document
status in the price sync list except
for First Initial Load.
If the Target Condition Type is Price Synchronisation Target Condition Type, Target Price Type Global
populated, then Target Price Type Document
cannot be populated.
If the Target Condition is Price Synchronisation Target Condition Global

referenced, it must be of type = Document
bracket.
If the Target Condition is populated, Price Synchronisation Target Condition, bracketTierMinimum, Global
the bracket tier minimum, bracket Document bracket TierMaximum,
tier maximum, bracket range bracketRangeQualifierCode,
qualifier and bracket operator for bracketOperator
the Item Price Type cannot be
populated.
The TargetPriceType must be Price Synchronisation TargetPriceType Global

unique within a information provider Document
in Price Synchronization.
If populated, the effectiveEndDate Price Synchronisation effectiveEndDate of the TargetPriceType Global

in the TargetPriceType cannot have Document
a date that is in the past.
The TargetPriceType must be in the Price Synchronisation TargetPriceType Global

accept, synchronize or review Document
status in the price sync list except
for First Initial Load.
If the TargetPriceType is populated, Price Synchronisation TargetPriceType, Price Type Code Global
the Price Type Code must be equal Document
to Allowance, Charge, Promotional
Price or any of the Transaction
Price Types identified by the word
TRANSACTION in the code list
value.
If the TargetPriceType is Price Synchronisation TargetPriceType Global

referenced, the PriceType code of Document
that TargetPriceType must not be
Allowance or Charge.
All PriceTypes, other than Price Synchronisation Price Type, PriceTypeApplicationSequence Global
PriceType = ‘Allowance’ or ‘Charge’, Document
must be assigned a
PriceTypeApplicationSequence = 1.
ConditionApplicationSequence = 1 Price Synchronisation ConditionApplicationSequence Global
is not a valid Application Sequence Document
for Summary Conditions.

priceSynchronisationDocumentIden Confirmation n
tificationmust be present and
unique within a information provider
Within the header, the Price Synchronisation priceSynchronisationRelationshipIdentificat Global
priceSynchronisationRelationshipId Confirmation ion
entification must be present and
unique within a information provider
If Price Synchronisation priceSynchronisationConfirmationStatusRe Global
priceSynchronisationConfirmationSt Confirmation ason, actionNeeded,
atusReason is Review, both confirmationStatusReasonCode
Reason Code and ActionNeeded
must be provided.
PriceSynchronisationRelationshipId Confirmation ion
entification included in the
PriceSynchronisationConfirmation
must reference an existing Price
Synchronisation Relationship
identified by a
priceSynchronsiationRelationshipId
entification.
The Price Synchronisation PriceSynchronisationConditionIDentificatio Global
PriceSynchronisationConditionIdent Confirmation n and
ification included in the priceSynchronisationConditionIdentification
PriceSynchronisationConfirmation (from priceSynchronisationDocument)
must reference an existing Price
Synchronisation Condition identified
by a
priceSynchronsiationConditionIdenti
fication..
The Price Synchronisation ItemPriceTypeSegmentIdentification Global

itemPriceTypeSegmentIdentification Confirmation
included in the
must reference an existing Item
Price Type Segment identified by a
itemPriceTypeSegmentIdentification
.
If populated, Catalogue Item Notification percentageOfAlcoholByVolume, Global

percentageOfAlcoholByVolume or fatPercentageInDryMatter
fatPercentageInDryMatter, must
be greater than or equal to 0.00
and smaller than or equal to
100.00 by definition.
The receiving DP is failing this All optional GDSN compliant Not Applicable. A list of mandatory Global
message because it does not messages (where the message types must be made available vs.
support this optional functionality. Document Identification Type what is considered optional inside the
is not supported.) network. The optional messaging would
be most applicable to pricing messages
primarily.
Note: No canned text - Free form All GDSN messages Not Applicable. Global
text provided by recipient - See
comment
If condition type = "bracket", then Price Synchronisation ConditionType, Condition Value, Condition Global
Condition Value, Condition Value Document Value Type, Qualifier, Basis Quantity UOM,
Type, Qualifier, Basis Quantity, Application Sequence
Basis Quantity UOM, and
Application Sequence cannot be
populated.
If Condition Type = bracket, then at Price Synchronisation Condition Type Global

least one bracket qualifier sub-class Document
must be provided.
In the condition segment, if Price Synchronisation Condition Segment, Classification Global

classification category code is Document Category Code, Information Provider,
populated, then, Information Target Market Country Code, Gtin, Target
Provider, GTIN, Target Market Market Subdivision Code
Country Code and Target market
Subdivision Code cannot be
populated.
If the Target Price Type is Price Synchronisation Target Price Type, Target Condition Type Global
populated, then Target Condition Document
Type cannot be populated.
If you provide more than one Price Synchronisation Bracket Qualifier, Bracket Operator Global
bracket qualifier in a Condition Document
segment, then the bracket
operators must either be all "and" or
all "or".
If you provide more than one Price Synchronisation Bracket Qualifier, Bracket Operator Global
bracket qualifier in a Item Price Document
Type segment, then the bracket
operators must either be all "and" or
all "or".
If the class Catalogue Item Notification classOfDangerousGoods Global

tradeItemHazardousInformation exists
and dangerousGoodsRegulationCode
equals “ADR”, then
classOfDangerousGoods must be one
of the following values: "1", "2", "3",
"4.1", "4.2", "4.3", "5.1", "5.2", "6.1",
"6.2", "7", "8", "9"
Content Owner GLN must be same Price Synchronisation Price Synchornisation Document, Content Global
as relationship segment GLN Document Owner; Price Synchronisation Relationship
Identification, Content Owner
The price data is not valid for price Price Synchronization Relationship segment, condition segment, Global
synchronization because the Document price type (item depiction)
recipient previously rejected the
relationship and it is in reject state.
The trade item is not valid for price Price Synchronization Price type segment Global
synchronization because the Document
recipient previously rejected a price
type segment for the trade item.
A reject segment cannot be sent on Price Synchronization Confirmation status, segment type Global
a condition segment Confirmation
If the Price Document Type = Price Synchronization Price Document Type, Price Global
RESTART, Document Synchronisation Header Action Code, Price
the Synchronisation Header Action Type Segment Action Code
Code must =
‘CHANGE_BY_REFRESH’ and all
Item Price Types sent must have a
segment Action Code equal to ADD.
If a Price Synchronisation Price Synchronization priceSynchronisationConfirmationStatus, Global

confirmationStatusReasonCode or Confirmation confirmationStatusReasonCode, action
action Needed is provided Needed
priceSynchronisationConfirmationSt
atus must be in the status of
"REVIEW".
If a Price Price Synchronization priceSynchronisationConfirmationStatus, Global
SynchronisationConfirmation is Confirmation itemPriceTypeSegmentIdentification,
received from a data recipient after priceSynchronisationConditionIdentification
a previous confirmation has been ,
sent for the segment with a priceSynchronisationRelationshipIdentificat
priceSynchronisationConfirmationSt ion.
atus of REJECTED, the newly
received
is invalid. Note: Having the Data
Source send a RESTART is the
only way to again start
synchronising rejected Price Types.
The valuse in Catalogue Item Notification tradeItemCountryOfLastProcessing Global

tradeItemCountryOfLastProcessing
MUST BE 3 digit numeric and in the
ISO 3166-1 code list.
Catalogue Item Notification tradeItemCompositionWidth, Global
If tradeItemCompositionWidth, tradeItemCompositionDepth,
tradeItemCompositionDepth and quantityOfCompleteLayersContainedInATr
quantityOfCompleteLayersContaine adeItem
dInATradeItem are all supplied, the totalQuantityOfNextLowerLevelTradeItem
product of the three attributes
should equal the
eItem.
should equal the
eItem.
This GTIN has an incorrect check All applies to any attribute in which a GTIN global
digit. may be populated
This GLN has an incorrect check All applies to any attribute in which a GLN global
digit. may be populated
The value for netContent is not Catalogue Item Notification netContent global
allowed to be changed according to
GTIN allocation rules.
The value of Catalogue Item Notification priceComparisonMeasurement global

priceComparisonMeasurement is
not allowed to be changed
according to GTIN allocation rules.
The value for brandName is not Catalogue Item Notification brandName global
allowed to be changed according to
GTIN allocation rules.
totalQuantityOfNextLowerLevelTrad Catalogue Item Notification totalQuantityOfNextLowerLevelTradeItem global
eItem is not allowed to be changed
according to GTIN allocation rules.
childTradeItem GTIN is not allowed Catalogue Item Notification tradeItemIdentificationOfNextLowerLevelTr global

to be changed according to GTIN adeItem
allocation rules
The GTIN cannot be a child of Catalogue Item Notification globalTradeItemNumber, global

itself. tradeItemIdentificationOfNextLowerLevelTr
adeItem
A GTIN cannot be repeated under Catalogue Item Notification globalTradeItemNumber, global
the same parent. tradeItemIdentificationOfNextLowerLevelTr
adeItem
isPriceOnPack may only be true for Catalogue Item Notification isTradeItemAConsumerUnit , global
consumer units. isPriceOnPack
One or more of the GTINs in each Catalogue Item Notification isTradeItemAnInvoiceUnit global
hierarchy must be marked as an
INVOICE UNIT
Price Type Effective Start or End Catalogue Price Notification 'priceTypeEffectiveEndDateContext; global
Date Contexts may only repeat priceTypeEffectiveStartDateContext
using a previously un-used code
value
The Price Type Effective End Date Catalogue Price Notification priceTypeEffectiveEndDate targetMarket=036
must be a date equal to or after (Australia)
Today's date targetMarket=554
(New Zealand)
You must populate a Price Value; Catalogue Price Notification priceValue targetMarket=036
this value must be greater than or (Australia)
equal to zero. targetMarket=554
(New Zealand)
When the Alternate Location Catalogue Price Notification alternateLocationGrouping; targetMarket=036
Grouping is populated, then the priceTargetMarketSubdivision; shipTo (Australia)
Target Market Subdivision Code targetMarket=554
and Ship To locations must be null. (New Zealand)
You must populate a Price Value Catalogue Price Notification priceValueType global
Type as either 'Value' or
'Percentage'
Reason for Price Action Reason Catalogue Price Notification priceActionReasonCode targetMarket=036
Code must be provided (Australia)
targetMarket=554
(New Zealand)
The Trade Item Group ID Catalogue Item Notification tradeItemGroupIdentificationDescription targetMarket=036
Description must be the same for all (Australia)
GTINs within a Trade Item Group ID targetMarket=554 (New
Zealand)
packagingMaterialCode and Catalogue Item Notification packagingMaterialCode, targetMarket=752

packagingMaterialCompositionQuantity packagingMaterialCompositionQuantity (Sweden)
are used in pairs. I.e. if one is populated
the other one must be populated, too.
Zero or negative values are not Catalogue Item Notification packagingMaterialCompositionQuantity global
allowed for Packaging Material
Composition Quantity where
provided
Catalogue is mandatory for all new Catalogue Item Notification cataloguePrice targetMarket=752
orderable trade items (Sweden)
For items with isTradeItemABaseUnit = Catalogue Item Notification packagingMaterialCode targetMarket=752

true, packagingMaterialCode and packagingMaterialCompositionQuantity (Sweden)
packagingMaterialCompositionQuantity
are mandatory unless package
recycling fee has been paid or the
package is returnable or the trade item
is unpacked.
For Target Market 528 All, Office Supplies global Trade Item Number, replaced TMS = NL(528)
(Netherlands) codes starting Extension, Free Quantity Trade Item Identification, Trade Item
with 0020-0029, 0040-0049, Promotional Trade Item Identification of Next Lower Level
0200-0299 are not allowed. Extension Trade Item, returnable Package
Deposit Code, primary Alternate Trade
Item, dependent Proprietary Trade
Item, non Promotional Item
GTIN has not been expressed All global Trade Item Number, replaced global
as a valid 14-digit syntax with Trade Item Identification, Trade Item
valid check digit. Identification of Next Lower Level
Trade Item, returnable Package
Deposit Code, primary Alternate Trade
Item, dependent Proprietary Trade
Item, non Promotional Item
For each GTIN in the hierarchy, Catalogue Item Notification TradeItemIdentification globalTradeItemNumber global
populated in the next lower level trade
item information the GTIN must have a
corresponding item record.
if isTradeItemPacked Irregularly = False Catalogue Item Notification isTradeItemPacked Irregularly global

then Value in quantityofNextLowerLevelTradeItem
quantityofNextLowerLevelTradeItem quantityOfCompleteLayersContainedInATradeIt
must be equal to value in em
quantityOfCompleteLayersContainedInA quantityOfTradeItemsContainedInACompleteLa
TradeItem multiplied by value in yer
quantityOfTradeItemsContainedInACom
pleteLayer
The Target Market Country Catalogue Item Notification targetMarketCountryCode, global

Code and targetMarketSubdivisionCode
targetMarketSubdivisionCode when
populated, will be consistent for
all GTINs within a given
hierarchy
grossWeight must be greater Catalogue Item Notification grossWeight; netWeight global

than or equal to Net Weight
where Net Weight is Provided
Unit of measure for Catalogue Item Notification storageHandlingTemperatureMaximum, targetMarket=752
storageHandlingTemperatureMaximum, storageHandlingTemperatureMinimum, (Sweden)
storageHandlingTemperatureMinimum flashPointTemperature
and flashPointTemperature may only be
specified as degrees Celsius.
If nestingIncrement is populated it must Catalogue Item Notification nestingIncrement global
be greater than zero(0).
Invalid value for trade item stacking Catalogue Item Notification stackingFactor targetMarket=
factor NL(528)
Invalid value for the non-GTIN Catalogue Item Notification logisticsUnitStackingFactor targetMarket=
logistic unit stacking factor NL(528)
Invalid value for trade layers per Catalogue Item Notification quantityOfLayersPerPallet targetMarket=
pallet NL(528)
endAvailabilityDateTime must be after Catalogue Item Notification endAvailabilityDateTime global

yesterday's date.
discontinuedDate can only be updated Catalogue Item Notification discontinuedDate global
with a documentCommant = CORRECT.
lastChangeDateTime for a trade item must Catalogue Item Notification lastChangeDateTime global
be the same or later than previously sent
value
tradeItemCountryOfOrigin must have a Catalogue Item Notification tradeItemCountryOfOrigin global
valid country code (3 digit numeric
representation found in the ISO 3166-1
list).
When netcontent is provided, its Catalogue Item Notification netContent global

associated unitOfMeasure must be
from the Unit Of Measure Code List
storageHandlingHumidityMaximum and Catalogue Item Notification storageHandlingHumidityMaximum, global

storageHandlingHumidityMinimum storageHandlingHumidityMinimum
using percentage must have a value
between 0 and 100.
There is a limit of 100 Transactions Catalogue Item Notification transaction, message global
within 1 Message
There is a limit of 1 Command type All GDSN Messages documentCommandHeader type, transaction global
within 1 Transaction
There is a limit of 100 Documents within All GDSN Messages transaction, documentCommandOperand global
1 Transaction
There is a limit of 1 Message within a All GDSN Messages StandardBusinessDocumentHeader, message global
Standard Business Document
GLN for sender in Standard Business All GDSN Messages Sender Identifier, contentOwner gln global
Document Header and content owner at
message level must be the same.
Header version in Standard Business All GDSN Messages HeaderVersion global

Document Header is not the current
version approved for the network. See
documentation for expected value.
Maximum number of occurrences of Catalogue Item Notification gdsnTradeItemClassificationAttributeType global

GDSNTradeItemClassificationAttrib
uteType is 25

GDSN Validation Rules

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GDSN Validation Rules

Uploaded by

Copyright:

Available Formats

Standard

Validation Rules for

Document Version: 1.2.2

1.1 Problem Statement / Business Need

Artefact name Artefact description

1.1.1 Task/Project Group Participants (where applicable)

Function Name Company / organisation

1.1.1 Global Business Process Modellers (GBPM)

1.2 Consistent Use of Error Code

< errorCode>”1”< /errorCode>

< errorCode>”1”< /errorCode>

1.1 GTIN Validations

1.2 GLN Validations

2.4.1 General Rule

2.4.2 Location Changes

Date of Version Reason for Change

22-Jun-05 0.0.7 Validation Team Review

21-Jul-09 0.0.7 GDSN Validations Sub-team Decision

28-Jul-09 0.0.7 Motion by GDSN Validation Sub-Team

28-Jul-09 0.0.7 Motion by GDSN Validation Sub-Team

0.0.7 New Section

0.0.7 New Section

0.0.7 New Section

Oct. 0.0.7 Multi-Source Validation Rules

3-Mar-06 1.0.2 New Publication for Certification.

18-Apr-06 1.03 Fix overwriting of rule 363

18-Oct-06 1.0.7 Added new rules and newly updated rules

15-Dec-06 1.0.8 Added new rules

28-Jun-07 1.0.9 Added new price synchronization rules; changed to GDSN

Nov.29, 2007 1.0.11 Removed Rule 419

12-Jun-08 1.1.1 Added Rules 445 and 446

15-Oct-08 1.1.1 Added Error Codes for new rules

28-May-09 1.2.1 New Validation Rules added

20-Jun-09 1.2.2 New Validation Rules added

29-Jul-09 1.2.2 New Validation Rules added

Validation Rules 439, CR 237; 07-242

Function Name Company / organisation

1.1 Problem Statement / Business Need

1.2 Consistent Use of Error Code

< errorCode>”1”< /errorCode>

1.1 GTIN Validations

1.2 GLN Validations

1.7.1 General Rule

1.7.2 Location Changes

1.7.2 Location Changes

Data Synchronisation Network.

ory for parties that make up the

the global supply chain that is a

Ds, BSDs and Schemas to be used

nd Error Messages for GDSN

message using the attribute/tag

message using the attribute/tag

ssage to identify the cause of the

would be used for application of

buteName “gtin” attributeValue ””

f the Error Message ID and may not

ssage text of the Error Message (in

n error is required to send a

ue identification of trade items

Trade Item Numbers® (GTINs®)

and not the GTIN. In this way, the

and not the GTIN. In this way, the

sible the unique and unambiguous

ss if they are not associated with a