+ All Categories
Home > Documents > Data Synchronization Data Model for Trade Item

Data Synchronization Data Model for Trade Item

Date post: 06-Apr-2015
Category:
Upload: rajsherk
View: 219 times
Download: 3 times
Share this document with a friend
202
Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM (DATA DEFINITION) COPYRIGHT 2005, GS1Version 7.7.1 Page 0 of 195 1 Business Requirements Group 2 (BRG) 3 4 Business Requirement 5 Document For 6 7 Data Synchronization Data Model 8 for Trade Item 9 (Data Definition) 10 11 12 13 Version 7.7.1 14 15 May 24, 2005 16 17 18
Transcript
Page 1: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 0 of 195

1

Business Requirements Group 2

(BRG) 3

4

Business Requirement 5

Document For 6

7

Data Synchronization Data Model 8

for Trade Item 9

(Data Definition) 10

11

12

13

Version 7.7.1 14

15

May 24, 2005 16

17

18

Page 2: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 1 of 195

19 DOCUMENT HISTORY 20

21 22

Document Number: 7.7.1 Document Version: 7.7.1 Document Issue Date May 23, 2005

23 Document Summary 24

Document Title EAN•UCC – Business Requirements Document For Data Synchronization Data Model for Trade Item – (Data Definition)

Owner Align Data BRG Grant Kille - Co-Chair -Julia Holden – Vice Chair Vic Hansen –Co-Chair-Olivier Mouton –Vice Chair UCC - [email protected] UCC – [email protected]

Status For ITRGapproval – BRG Approved 25

Document Change History Log 26 Date of Change Version Reason for

Change Summary of Change CCR #

February 17, 2001 X.0 Messaging Architecture

Documentation to support the Core Item Business Process and to reflect the UCC UML methodology standards

XXXXX

February 28, 2001 2.0.1 Common Data Item Rpt

Edited the Common data item report.

April 27, 2001 2.0.4 Added the Item Containment

Item Containment is described and has models but no attribute lists

May 8, 2001 3.1 Comments at Vote Approved BRD with the title of “Core Item & Extension of Relationship Dependent Data to Enable Trade” (This document input to approved July 2001 Business Message Standard – Simpl eb)

June 5, 2001 4.1 Meeting in Orlando See section 4.4 Change Summary that was documented on change request 01-000009

01-000009

May 9, 2002 5.0 UCC work group meeting and submittal to Align Data BRG (Item Task Group)

BRD format was upgraded to GSMP standards. Changed title of the document to “Core Item & Extension of Cross industry Data”

01-000011 01-000064 01-000065

May 10, 2002 V0.6.0 Models upgraded to match text changes

Class diagrams in the BRD were upgraded to reflect the text changes made in V0.5.0

Page 3: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 2 of 195

July 19, 2002 V0.6.1 Change to Section 3.0

Combined GCI and UCC standards work.

02-000065

August 12, 2002

V0.6.2

Change to Section 3.0. Add Section 5.0

Changes to data dictionary.

Sept. 11, 2002 V0.6.3 Merged updates Implementation Section incorporated

Updates made to text from Item Project Team.

Oct. 10, 2002 V0.6.4 Merged updates Updates made to text from Item Project Team.

Oct. 22, 2002 V7.0 Merged updates Models upgraded Implementation Section upgraded

Updates made to text from Item Project Team

Nov. 21, 2002 V7.1 Models upgraded, Text upgraded, Attributes grouped to reflect UML.

Updates made to text based on comments resulting from Public Review by Align BRG. Changes to document agreed by project team.

March 14, 2003 V7.2 Model Harmonization

Version 7.2 Model Harmonization Summary

April 9, 2003 V7.2.1 Errata Changes Reference separate document titled “TRADE ITEM – CORE AND EXTENSION – V. 7.2.1- Errata Change Summary

May 5, 2003 V7.2.2 Errata Changes Table on Appendix A – Attribute Variations checked to match the attribute conditions in the text.

June 4, 2003 V7.3 Errata Changes Incorporates Errata resulting from ITRG’s review.

June 7, 2004 V 7.4 Incorporation of Item Regional Attributes

Changed Trading Partner Neutral Information Model to eliminate Is Item Green Dot.

03-000082

July 19, 2004 V 7.5 Added the code list into section 4.8.1

Additional code list added to section 4.8.1

04-000035

December 15, 2004

V 7.6 Added Appendix E: Trade Item Implementation Feedback

Incorporated Trade Item Implementation Feedback

04-000044

April 4, 2005 V 7.7 Feedback from 1.3.1 BRD vs. XML .

May 24, 2005 V 7.7.1 Errata - Update of Trade Item Classification

Changed to GDSN Trade Item Classification. Removed remaining references to alternate party and item identifiers. Corrected formatting issues.

27 28 29 30

Approvals 31 Name Title Signature Date

Page 4: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 3 of 195

32

33

34

TABLE OF CONTENTS 35

FOREWORD........................................................................................................................5 36

1.0 BUSINESS OPPORTUNITY:.........................................................................................5 37

1.1 PROBLEM STATEMENT:.........................................................................................5 38 1.2 AUDIENCE: ..........................................................................................................5 39 1.3 REFERENCES: ......................................................................................................5 40 1.4 ACKNOWLEDGEMENTS:.........................................................................................7 41

2.0 PROCESS VIEW – GENERAL REQUIREMENTS:.......................................................8 42

2.1 USE CASE SCENARIO:................................................................................................8 43

2.1.1 BUSINESS OPPORTUNITY/PROBLEM STATEMENT .................................................9 44 2.1.2 ACTORS............................................................................................................9 45 2.1.3 PRECONDITIONS ..............................................................................................10 46 2.1.4 PROCESS START .............................................................................................10 47 2.1.5 PROCESS END ................................................................................................10 48 2.1.6 POST CONDITIONS...........................................................................................10 49 2.1.7 PROCESS ACTIVITIES.......................................................................................10 50

3.0 LOGICAL VIEW...........................................................................................................10 51

3.1 DEFINITION OF CONDITIONS......................................................................................11 52

MASTER DATA/TRANSACTIONAL DATA – ...................................................................11 53 MASTER DATA ALIGNMENT.......................................................................................11 54 CORE ATTRIBUTES: ..................................................................................................11 55 EXTENSION ATTRIBUTES: ..........................................................................................11 56 TRADING PARTNER NEUTRAL/TRADING PARTNER DEPENDENT....................................12 57 MARKET GROUP ......................................................................................................12 58 TARGET MARKET COUNTRY CODE ............................................................................13 59 TARGET MARKET SUB-COUNTRY CODE.....................................................................13 60 GLOBAL/GLOBAL-LOCAL/LOCAL ..............................................................................13 61 HOW DOES THE GLOBAL/GLOBAL-LOCAL/LOCAL CONDITION, AND TARGET MARKET 62 VALUE INTERACT TO AFFECT ATTRIBUTE VALUES? ......................................................14 63 TRADE ITEM.............................................................................................................15 64 PARTY 15 65

PRODUCT HIERARCHY REFERENCE LEVEL ...............................................................15 66

Page 5: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 4 of 195

COMMON VALUE TO ALL PRODUCT HIERARCHY ......................................................15 67

3.2 TRADE ITEM: ..............................................................................................................17 68

3.3 TRADE ITEM IDENTIFICATION: ................................................................................20 69

3.4 GDSN TRADE ITEM CLASSIFICATION: ...................................................................22 70

3.5 TRADE ITEM INFORMATION:....................................................................................28 71

3.6 TRADING PARTNER NEUTRAL TRADE ITEM INFORMATION:..............................38 72

3.7 TRADE ITEM TAX INFORMATION: .........................................................................125 73

3.8 FMCG (FAST MOVING CONSUMER GOODS) – INDUSTRY SPECIFIC:...............128 74

4.0 IMPLEMENTATION CONSIDERATIONS AND CONCERNS ..........................................132 75

KEY DATA ATTRIBUTES...............................................................................................134 76

4.1 PRODUCT HIERARCHY...........................................................................................135 77

GTIN HIERARCHY ..................................................................................................135 78

ITEM CONTAINMENT:....................................................................................................148 79

4.2 PRODUCT CLASSIFICATION ..................................................................................148 80

4.3 PRODUCT ORIENTATION........................................................................................149 81

4.4 LANGUAGE (REFERENCE APPENDIX 13 AND APPENDIX 17) ...........................149 82

4.5 CURRENCY (REFERENCE APPENDIX 12).............................................................149 83

4.6 UNIT OF MEASURE (REFERENCE APPENDIX 14)................................................150 84

4.7 PRODUCT DESCRIPTION........................................................................................150 85

4.8 CODE LISTS..............................................................................................................151 86

4.8.1 CODE LISTS ..................................................................................................151 87

4.9 RELATIONSHIP TO GLOBAL DATA SYNCHRONIZATION PROCESS.................178 88

APPENDIX A: ATTRIBUTE VARIATIONS .....................................................................181 89

APPENDIX B ATTRIBUTE ASSOCIATION BY TRADE ITEM HIERARCHY LEVEL 90 FOR DATA SYNCHRONIZATION...................................................................................188 91

APPENDIX C ATTRIBUTES MANDATORY FOR DATA SYNCHRONIZATION............198 92

APPENDIX D: TRADE ITEM IMPLEMENTATION FEEDBACK.....................................199 93

94

Page 6: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 5 of 195

FOREWORD 95 96

“Implementation of this Item standard requires adherence to the business rules 97 contained in this document in addition to adherence to the technical schema as it is 98 designed. In order to enable reusability and commonality across the EAN.UCC 99 Business Message Standards, a common library has been developed to support the 100 technical implementation of the EAN.UCC standards into XML schemas resulting in 101 standardized data types and field sizes. As a result, the schema will accommodate 102 the data types and field sizes as defined in this standard, however, the schema does 103 not enforce any specific field sizes as defined by the business requirements.” 104 105

106 107

1.0 Business Opportunity: 108

Item is the second message in the trade process following the Party message. Item 109 elements are the mandatory attributes needed to align the item information between 110 trading partners. These attributes in combination ensure the uniqueness of the data 111 set associated with a GTIN. The use, definition, and relevance of these attributes is 112 the same for ALL EAN.UCC industries. Following the Item attributes is an extension 113 of cross industry. These are data attributes that may be required in conducting 114 commerce between partners for the trade of an item or service. These attributes are 115 relevant to more than one industry. The definition of these attributes must be the 116 same for all industries. 117

118 1.1 Problem Statement: 119

Item and the extension of the cross industry data processes include communicating 120 the data elements necessary to support the core business requirements in the global 121 trading environment. The Party and Item process are mandatory in the completion of 122 the price, purchase order, invoice, etc. messages that follow in the global trade 123 process. 124

125 1.2 Audience: 126

The audience of the standards would be any participant in the global supply chain. 127 This would include retailers, manufacturers, service providers and other third parties. 128 129

1.3 References: 130 131 • The legacy: the Global Data Alignment System (GDAS) 132 133

“ELECTRONIC CATALOGUES EAN RECOMMENDATIONS COMMON SET 134 OF DATA” (June 1998-June 1999) 135 136 “GLOBAL DATA ALIGNMENT – GCI – DRAFT” (21 Jan. 2000 – 24 July 137 2000) 138

139 • GLOBAL DATA DICTIONARY- Item Data Model – General Overview, 140

Version 1, Global Commerce Initiative, Global Data Dictionary Group, March 141 31, 2002 142

Page 7: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 6 of 195

143 • EAN.UCC Business Message Standards Version 1.0, July 2001 144

• Core Party Business Requirements Document, Version 6.0 of May 10, 2002 145

• Core Item and Extension of Trading Partner Neutral Data, Version 0.6.0 of 146 May 10, 2002 147

• EAN.UCC Global Business Model (Process and Data), October 1999 148

• Java Framework for SIMPL-EDI Requirements Specification, April 2000 149

• Simple eb(electronic business), March 2000 150

• BPAWG Model of the International Supply Chain Domain (interim report), 151 January 2000 152

• Change Requests: 01-000009, 01-000010, 01-000064, 01-000065. 153

• Change Request 02-00065 154

• GSMP –Technical Steering Team, Policy Paper “Policy on the use of 155 identification keys in standards and recommendations developed in GSMP”, 156 January 2003 157 158

Note: The following text was extracted from a letter sent to the Align Data BRG on March 159 31, 2003: “Due to the timing of this policy paper and the dialogue going on within the 160 user community regarding how it will affect the standards, the Executive Management 161 Team decided that the policy would be implemented in version 2.0 of the standards, 162 which should be published in 2004.” 163

Additionally, the existing Electronic Data Interchange messages in widespread use 164 were mined for their business content. 165

• UCS 888 Item Maintenance 166

• VICS EDI 832 Price Sales Catalog 167

• I/C EDI 832 Price Sales Catalog 168

• EANCOM© PRICAT 169

Acknowledgement is also due to the work going on in the XML environment. 170

• ebXML/SOAP 171

• eCo Framework (Common Business Library) 172

• Rosettanet 173

• W3C 174 175

Page 8: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 7 of 195

1.4 Acknowledgements: 176 177 Members of the Item Project Team as of October 17, 2002 178 179 Buckley, Greg Pepsi-Cola USA Costello, Aidan QRS Funk, Jim SC Johnson Geyer, Terrie Sears Roebuck & Company Gore, Harshal E-centre-UK Harris, Mike Vialink Hawkins, Bruce Wal-Mart Iwicka, Ewa EAN International Kasper, Sascha EAN Germany, CCG Kille, Grant WWRE Laskero, Nancy Sears Roebuck & Company Laur, Rita ECCC, Canada Lerch, Hanjörg Metro AG, Germany Licul, Ed Transora Lockhead, Sean UCCNet Merulla, Mike Wegmans Moise, Michael Nestle Mouton, Olivier Carrefour, France Ngo, Aileen Nestle Panaccio, Robert (Co-chair) Procter & Gamble Pottier, Natascha (Co-chair) EAN Germany, CCG Sadiwnyk, Mike ECCC, Canada Schneck, Joy General Mills Sheldon, Emma UDEX Spooner, Karen Kraft Foods Vacval, Milan Vista CPG Walton, Mike UDEX Warde, Nadim Equadis Watt, Anna (Co-chair) Cadbury/Schweppes Wasielewski, David Connective Commerce Zielinski , Felix The Coca Cola Company 180 Eggert, Jack EAN.UCC, BRG Manager Ryu, John EAN.UCC, Business Process Modeler Schneider, Maria EAN.UCC, Project Team Manager Steck, Terry EAN.UCC, Database Support

Page 9: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 8 of 195

181 2.0 Process View – General Requirements: 182

183

The buyer and seller must make contact and set up a business relationship before 184 trade can proceed. This is a prerequisite to all of the other steps. This initial contact 185 can be made in many different ways. Following the establishment of the trading 186 agreement the parties must exchange their basic business data such as trading 187 partner names, addresses, locations, item attributes, price lists, contracts and trading 188 partner agreements. Specifically, the Core Item message follows the Core Party 189 message in the data alignment process. This process creates a common 190 understanding between the trading parties which can be used as a resource 191 throughout the trading process. 192

193 2.1 Use Case Scenario: 194

There is only one scenario in the Item data communication process as described in 195 problem statement of section 1.1. Item data alignment is the process of 196 communicating the core item and cross industry data elements following the 197 establishment of a business relationship between suppier, buyer or third party. 198

Page 10: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 9 of 195

Seller Buyer

Align Data - Party

Align Data - Item and Price

Order

Despatch Advice

Invoice

199 200

201 2.1.1 Business Opportunity/Problem Statement 202

The objective of this document is to elaborate the Data Synchronization Data Model 203 for Trade Item (hereafter referred to as ‘Data Sync Trade Item’) business process in 204 enough detail to support the construction of standards. It is assumed that the 205 players, both seller and buyer, have established a business understanding of the 206 trading partner relationship. The challenge is to provide the core elements necessary 207 to complete all supply chain processes without duplicates. 208

209 2.1.2 Actors 210

The two general players in the Data Sync Trade Item business process are the 211 "seller" and the "buyer". Depending on the specific nature of the relationship other 212 players may have a role, such as a Third Party. The graphic flow below pictures the 213 core sequence of messages, and is expanded to account for additional scenarios. 214

Page 11: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 10 of 195

215 216

Actor’s Name

Description Buyer Seller Third Party

Seller Manufacturer or supplier of the item. X X Buyer Retailer or distributor of the item X X Third Party Other parties that somehow influence the

item and may include creation, distribution, publication, and/or maintenance of the item.

X X X

217 2.1.3 Preconditions 218

The Data Sync Trade Item business process begins when the parties decide to do 219 business together. The next step is for the buyer to communicate the Party 220 organizational information to the seller. The seller provides his Party organizational 221 information to buyer. Other data alignment follows such as item and price attributes. 222

223 2.1.4 Process Start 224

The start-state of the Data Sync Trade Item business process begins during the 225 initial discussions between the trading partners and the need to exchange item 226 information. 227

228 2.1.5 Process End 229

Once the Data Sync Trade Item business message has been accepted by both the 230 seller and buyer, then data alignment has been achieved. This process can be an 231 ongoing process as item business information changes or new parties are added. 232 The process of trading goods and services can now occur. 233

234 2.1.6 Post Conditions 235

The end-state of the Data Sync Trade Item business process occurs when the 236 parties have achieved Party and Item data alignment. 237

238 2.1.7 Process Activities 239

Step #

Actor Activity Step

1 All All preconditions have been met. 2 Seller Communicates item data. 3 Buyer Receives item data. 4 Buyer Applies item data or notifies the seller of any errors in the data.

240 See the work completed by the data synchronization project team for a detailed view of 241 data communication. 242 243 3.0 Logical View 244

The Data Sync Trade Item messages include the item’s unique identification, 245 descriptions, and characteristics. 246

Page 12: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 11 of 195

247 3.1 Definition of Conditions 248

To help with the implementation of this data model, several key definitions are listed 249 below. 250

251 Master Data/Transactional Data – 252

253 • Master data is considered to be that set of data that describes the 254

specifications and structure of each item and party involved in the supply 255 chain processes. The uniqueness of the data associated with a trade item is 256 given only by the GTIN. This data is static, not dependent on a transaction. 257

258 • Transactional data is that set of data that can only be determined during a 259

business transaction, i.e., plan, sell, buy, and deliver cycle. (E.g. actual 260 amount of cases delivered). 261

262 • NOTE – this data model only includes master data 263

264 Master Data Alignment 265

• Master Data Alignment is the process of timely distribution of accurate Master 266 Data from one partner to others and the correct use of this data. Such 267 synchronization and use of Master Data leads to more accurate business 268 transactions and therefore reinforces the efficiency of the supply chain 269 operations. 270

• Successful Master Data Alignment is achieved via the use of EAN.UCC 271 coding specifications throughout the supply chain, communication of all 272 changes and new information between trading partners and use of the 273 information exchanged in subsequent transactions. 274

• Master Data Alignment relies on EAN.UCC specifications concerning the 275 Unique Identification of Items, GTIN and Parties GLN. 276

277 Core attributes: 278

• An attribute whose definition is common across all Industries 279 • Core attributes are common across all geographies. I.e. ALL Target Markets 280 • These attributes do not necessary need to be maintained by the Registry. 281 • Core attributes CANNOT be relationship dependant. They are trading partner 282

neutral only 283 284 Extension attributes: 285

• An extension is an attribute that is relevant to one or more industries (not all 286 EAN.UCC Industries) 287

• The definition of an extension attribute is common to all Industries who use 288 the attribute. 289

• Each Industry is responsible for determining the extension attributes that are 290 relevant to their Industry. 291

• New extension attributes may be submitted/requested for a specific Industry 292 as necessary. 293

Page 13: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 12 of 195

• The conditions of extension attributes can vary by each industry. E.g. 294 Mandatory/Optional, Global/Local, Trading Partner Neutral/Relationship 295 Dependent, and Common to all Hierarchy levels. 296

• Industry user groups should be developed in concert with the EAN.UCC 297 GSMP Process, to determine their relevant extension attributes and the 298 conditions associated with those attributes. 299

• Process user groups such as CPFR and local (target market) extensions. 300 301 Trading Partner Neutral/Trading Partner Dependent 302

303 Values for an attribute can vary depending on the relationship with the party 304 receiving the data. The Trading Partner Neutral/Trading Partner Dependent 305 status indicates this rule. 306 307 • The condition Trading Partner Neutral is applied to any attribute whose value 308

is independent on a buyer and seller relationship. An attribute, which has the 309 condition Trading Partner Neutral, can have only one set of values . 310

311 • The condition Trading Partner Dependent is applied to any attribute whose 312

value is dependent on a buyer and seller relationship. An attribute, which has 313 the condition Trading Partner Dependent, can have only one set of values per 314 GLN of Party Receiving Data. These are attributes whose value is dependent 315 on a specific point-to-point agreement between a buyer and a seller. 316

317 An attribute which has the condition Trading Partner Neutral & Trading 318

Partner Dependent, can have only one set of values for the Trading Partner 319 Neutral value AND one set of values per GLN of Party Receiving Data 320

321 322 Multiple Values allowed: 323 324

This condition is used to indicate that multiple values can be submitted for a 325 trade item. 326 327 E.g. multiple types of packaging on a trade item e.g. plastic, cardboard etc 328 329 Where there is a need to express multiple measures, these are handled through 330 indicating the attribute type as ‘Measurement’. Both the value and UOM can be 331 repeated, and must be used together. See section 4.6 on Unit of Measure in the 332 implementation consideration and concerns. 333 334 Where there is a need to express multiple language versions, these are handled 335 through indicating the attribute type as ‘Text Description’. See section 4.4 on 336 Language in the implementation consideration and concerns. 337 338

339 Market Group 340

• A Market Group is used to identify a proprietary group of data recipients. It is 341 normally determined by the information provider although it can also be 342

Page 14: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 13 of 195

created by buyers and third parties. This group is used and developed by the 343 information provider to control del publication of data to a specific group of 344 customers. This should not be confused with Target Market. 345

346 Target Market Country Code 347

• The purpose of the target market country code is to organize master data to 348 meet the requirements of specific geographies 349

350 • The purpose of this field is to explain where a manufacturer is intending to 351

sell its product(s) to a buyer. It does not control where the buyer can resell 352 the product (s) to the end consumer. 353

354 • It is the country, (the geopolitical area) where the product is to be sold and 355

available for publication in an Item Catalog. 356 357 • Target Market Country Code in relationship to Master Data, can be Trading 358

Partner Neutral only. A Target Market Country Code is not used to control 359 Distribution or Consumer Market Area geographies. E.g. product available for 360 shipment from a single Distribution Center. 361

362 363

Target Market Sub-Country Code 364 • A sub-country code level used to address/comply with a “law making” 365

requirement associated with a country. 366 • The number of sub-country codes will vary by each country. These will match 367

with the legislation requirements of each country. (Local bottle deposit tax 368 laws, State and country taxes) 369

• Not all countries will have sub-country codes. 370 • A sub-country code must be associated with a Target Market Country Code. 371

It cannot stand-alone. 372 373

Global/Global-Local/Local 374 • All attributes are impacted by their geo-political relevance. This condition can 375

be used by information providers as they build data models. With this 376 information, they can limit the attributes communicated to those relevant for 377 that geography. 378

• A global attribute indicates that the attribute is relevant for business cases 379 around the world, and can only have a single value throughout the world. 380 (E.g. GTIN) 381

382 • A global/local attribute indicates that the field is relevant for business cases 383

around the world, that its definition is the same around the world, but may 384 have a different value depending on the geography. (E.g. VAT tax values, 385 1.00 in France, 1.05 in Belgium) 386

387 • A local attribute is only relevant in certain geographical areas, and the values 388

may change based on where the product is offered for sale. (E.g. green dot – 389 only relevant in certain European countries) 390

391

Page 15: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 14 of 195

How does the Global/Global-Local/Local condition, and Target Market value 392 interact to affect attribute values? 393

394 An attribute, which has the condition ‘Global’, can have only one global value (except 395

where there are multiple values allowed). 396 397

An attribute which has the condition Global / Local can have one value per Target 398 Market specified (except where there are multiple values allowed). A Global/Local 399 attribute indicates that the field is relevant for business cases around the world, that 400 its definition is the same around the world, but may have a different value depending 401 on the geography. (E.g. the attribute - VAT tax values are relevant globally, but the 402 actual value, 1.00 in France, 1.05 in Belgium varies by country) 403 As long as the attribute values apply consistently to the GTIN, GLN, TM combination 404 the values are repeatable. 405

406 Example: 407 408 GTINa + GLNa + TMa + b, = Ohio, Indiana. Start availability date = January 1, 409 2003 410 Target Market can be repeated where the values for the attribute are the same 411 e.g. start availability date is the same for the GTIN + GLN + TM combination data 412 set. 413 414 GTINa + GLNa + TMc = Kentucky. Start availability date = January 15, 2003 415 416

An attribute, which has the condition Local, can have only one value for the Target 417 Market that is valid for (except where there are multiple values allowed). 418

419 Attribute Cardinality 420 421

Mandatory 422 An attribute in this model is mandatory when its value is required. 423

424 Optional 425

An attribute in this model is Optional when its value is not required. 426 427 Dependent 428 An attribute in this model is depended when its value is conditional on some 429 other attribute’s value. 430 431 Type 432 The following data types are used in this model: 433

434 Alphanumeric (AN) 435 Amount 436 Boolean 437 Char 438 Description 439 Date 440

Page 16: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 15 of 195

DateTime 441 Integer 442 Long Description 443 Long Text Description 444 Measurement 445 Measurement Value 446 Numeric (N) 447 Party Identification 448 Percentage 449 Text Description 450

451 Trade Item 452

• A Trade Item is any product or service upon which there is a need to retrieve 453 pre-defined information and that may be priced, ordered or invoiced at any 454 point in any supply chain. The term “trade item” is not to be confused with the 455 legacy term “traded item” (now referred to within the General EAN.UCC 456 Specifications as ‘standard trade item group’ which can mean a specific 457 product containment level, which is also called case. “Trade item” can 458 represent any level of product containment, and also can represent a service. 459

460 In addition, the supply chain is any point from the inception of the product 461 through the final consumption and disposal/reuse/recycling/return of that 462 trade item. Reference General EAN.UCC Specifications for definitions of the 463 term ‘trade item’, ‘retail consumer trade item’, and ‘standard trade item 464 grouping’. 465

466 Party 467

• A Party (or) Location is any legal, functional or physical entity involved at any 468 point in any supply chain and upon which there is a need to retrieve pre-469 defined information. 470

471 Product Hierarchy Reference Level 472

This condition is used to indicate at what level of the product hierarchy each 473 attribute is relevant. For some attributes, business requirements are such that the 474 attribute only needs to be provided at a specific level. 475 476 Example – “netContent” this field is only required at the consumer unit level. 477 For most attributes, a value must be entered for all attribute levels. 478 479

Common Value to all Product Hierarchy 480 Common value condition indicates when the value for the attribute is equal for all 481 levels of a hierarchy. 482 483 Example – “orderingLeadTime” is common across all levels of the product 484 hierarchy; common value = Yes 485 486 Example – “grossWeight” is not common from each to case to pallet; 487 Common value = No 488

Page 17: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 16 of 195

489

Page 18: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 17 of 195

3.2 TRADE ITEM: 490 491 Class Name: NextLowerLevelTradeItemInformation 492 493 Item Name: totalQuantityOfNextLowerLevelTradeItem 494 495

Core/Extension: E 496 Global Local Status: G 497 M/O/D: M 498 Multiple Values Allowed: N 499 Neutral/RelationshipDependant: T.P.Neutral 500 Product Hierarchy Reference Level: Despatch units only 501 Common value to all product hierarchy: No 502 Type: N 503 Size: 6 504

505 Definition: This represents the Total quantity of next lower level trade 506 items that this trade item contains. 507

508 Examples: 509 510 NextLowerLevelTradeItem

(GTIN description)

QuantityofNextLowerLevelTradeItem

TotalQuantityofNextLowerLevel TradeItem

GTIN 1 Orange nail varnish

2

GTIN 2 Purple nail varnish

2

GTIN 3 Green nail varnish

2

GTIN 4 Red nail varnish

2

GTIN 5 Grey nail varnish

2

10 511

512 Business Rules: e.g. in a mixed module, with 2 x five different types of 513 nail varnish, this number = 10. 514

515 Where this differs from “QuantityofNextLowerLevelTradeItem” is that this 516 field is used in conjunction with each GTIN identified in the field 517 ‘NextLowerLevelTradeItem’. E.g. in the example of 2 x five different types 518 of nail varnish, this number = 2. 519

520 If the item is not mixed, then this number will equal the value submitted 521 for the “QuantityofNextLowerLevelTradeItem” field. 522 523

524 525 Class Name: NextLowerLevelTradeItemInformation 526 527

Page 19: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 18 of 195

Item Name: quantityOfChildren 528 529

Core/Extension: E 530 Global Local Status: G 531 M/O/D: M 532 Multiple Values Allowed: N 533 Neutral/Relationship Dependant: T.P.Neutral 534 Product Hierarchy Reference Level: Despatch units only 535 Common value to all product hierarchy: No 536 Type: N 537 Size: ..10 538

539 Definition: Value indicates the number of unique next lower level trade 540 items contained in a complex trade item. A complex trade item can 541 contain at least 2 different GTINs. 542

543 Examples: Ready to sell display of cosmetics contains 2 bottles each of 544 five different colors (each with their own GTIN) of blush. The value for this 545 field would be "5". See tables in Section 4.1 of the Implementation 546 Considerations and Concerns. 547

548 Business Rules: Only applies to dispatch units (cases, pallets, etc.) 549

550 551 Class Name: ChildTradeItem 552 553 Item Name: quantityOfNextLowerLevelTradeItem 554 555

Core/Extension: E 556 Global Local Status: G 557 M/O/D: M 558 Multiple Values Allowed: Y 559 Neutral/Relationship Dependant: T.P.Neutral 560 Product Hierarchy Reference Level: All 561 Common value to all product hierarchy: No 562 Type: N 563 Size: 6 564

565 Definition: The number of next lower level trade item that this trade item 566 contains. 567

568 Examples: See tables in Section 4.1 of the Implementation 569 Considerations and Concerns. 570

571 Business Rules: This trade item may repeat if the GTIN of the lower 572 level configuration repeats (e.g. if a combo-pack (mixed trade item) such 573 as an assortment of crisps contains both chicken and cheese packets, 574 the lowest level GTIN is that of each trade item in the assortment, not the 575 GTIN of the assortment) 576

577

Page 20: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 19 of 195

578 Class Name: ChildTradeItem 579 580 Item Name: tradeItemIdentificationOfNextLowerLevelTradeItem Represented 581 as association of ChildTradeItem Class to TradeItemIdentification Class. 582 583

Core/Extension: E 584 Global Local Status: G 585 M/O/D: M 586 Multiple Values Allowed: Y 587 Neutral/Relationship Dependant: T.P.Neutral 588 Product Hierarchy Reference Level: All 589 Common value to all product hierarchy: No 590 Type: N 591 Size: 14 592

593 Definition: A reference to the GTIN of the next lower level of trade item 594 that this trade item contains. 595

596 Examples: GTIN "00037000123415" contained in GTIN 597 00037000123330. See tables in Section 4.1 of the Implementation 598 Considerations and Concerns for more examples. 599

600 Business Rules: Allowed for more than 1 reference to lower levels to 601 allow for the registration of Mixed Assortments. The sequence of entering 602 GTINs is important when a next lower level GTIN is to be linked. The next 603 lower level GTIN must already exist, therefore the order of trade items to 604 be entered should be from lowest to highest e.g. consumer, then 605 intermediate, then traded, etc. While there can be multiple child trade 606 items, there can only be one trade item identification per child item. 607

608 609 Class Name: Trade Item Identification 610 611 Item Name: replacedTradeItemIdentification represented as a role in Trade 612 Item Diagram 613 614

Core/Extension: E 615 Global Local Status: G/L 616 M/O/D: O 617 Multiple Values Allowed: N 618 Neutral/Relationship Dependant: T.P.Neutral 619 Product Hierarchy Reference Level: All 620 Common value to all product hierarchy: No 621 Type: N 622 Size: ..14 623

624 Definition: Indicates the trade item identification of an item that is being 625 permanently replaced by this trade item. 626

627

Page 21: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 20 of 195

Examples: "01234567890128" 628 629

Business Rules: The trade item identification that is being permanently 630 replaced must already be in the home data pool in order to ensure data 631 integrity. The old trade item identification specified in this field should be 632 discontinued. 633

634 635 Class Name: TradeItemUnitIndicatorList 636 637 Item Name: tradeItemUnitDescriptor 638 639

Core/Extension: C 640 Global Local Status: G 641 M/O/D: M 642 Multiple Values Allowed: N 643 Neutral/Relationship Dependant: T.P.Neutral 644 Product Hierarchy Reference Level: All 645 Common value to all product hierarchy: No 646 Type: Enumerated List 647 Size: Not Applicable 648

649 Definition: Describes the hierarchical level of the trade item. See 650 implementation notes for full definition and rules for each value. 651

652 Examples: "CASE" , ”PALLET” 653

654 Business Rules: See implementation notes for complete description of 655 each product hierarchy level. Reference TradeItemUnitDescriptorList 656 which is an enumeration list in the Trade Item Class Diagram. 657

658 659 3.3 TRADE ITEM IDENTIFICATION: 660

661 Class Name: GlobalTradeItemNumber 662 663 Item Name: globalTradeItemNumber 664 665

Core/Extension: C 666 Global Local Status: G 667 M/O/D: O 668 Multiple Values Allowed: N 669 Neutral/Relationship Dependant: T.P.Neutral 670 Product Hierarchy Reference Level: All 671 Common value to all product hierarchy: No 672 Type: Integer 673 Size: 14 674

675 Definition: A particular Global trade item Number, a numerical value used to 676 uniquely identify a trade item. A trade item is any trade item (product or 677 service) upon which there is a need to retrieve pre-defined information and 678

Page 22: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 21 of 195

that may be planned, priced, ordered, delivered and or invoiced at any point 679 in any supply chain. 680

681 Examples: 14 digit code. Please see PTRG directions for creating GTINs 682

683 Business Rules: EAN.UCC numbering structures will be used for the 684 identification of trade items. All of them will be considered as 14-digit Global 685 Trade Item Number (GTIN). Must be present to enable data to be presented 686 to trade item catalogue. Must be submitted by the owner of the data (who 687 may be the original manufacturer, the importer, the broker or the agent of the 688 original manufacturer) See to the EAN.UCC specifications. This field is 689 mandatory within the Global Data Synchronization work process. See 690 implementation notes. 691 692

693

Page 23: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 22 of 195

3.4 GDSN TRADE ITEM CLASSIFICATION: 694 695

Class Name: ClassificationCategory 696 697 Item Name: additionalClassificationAgencyName 698 699

Core/Extension: E 700 Global Local Status: G 701 M/O/D: Dependent on additionalClassifcationCategoryCode 702 Multiple Values Allowed: Y 703 Neutral/Relationship Dependant: T.P.Neutral 704 Product Hierarchy Reference Level: Each 705 Common value to all product hierarchy: No 706 Type: AN 707 Size: 35 708

709 Definition: Text name of the additional external classification agency 710 whose schema is being provided in addition to the Global EAN.UCC 711 schema. 712

713 Examples: 714

715 Business Rules: Required if additional classification schema field are populated. 716 717 718 Class Name: ClassificationCategory 719 720 Item Name: additionalClassificationCategoryCode 721 722

Core/Extension: E 723 Global Local Status: G 724 M/O/D: O 725 Multiple Values Allowed: Y 726 Neutral/Relationship Dependant: T.P.Neutral 727 Product Hierarchy Reference Level: Each 728 Common value to all product hierarchy: No 729 Type: AN 730 Size: ..15 731

732 Definition: Category code based on alternate classification schema 733 chosen in addition to EAN.UCC classification schema. 734

735 Examples: "34001030" 736

737 Business Rules: The additional classification bundle 738 (code/agency+descriptions) can be repeated for each classification 739 agency used. 740

Page 24: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 23 of 195

741 Class Name: ClassificationCategory 742 743 ItemName: additionalClassificationCategoryDescription 744 745

Core/Extension: E 746 Global Local Status: G 747 M/O/D: Dependent on additionalClassifcationCategoryCode 748 Multiple Values Allowed: Y 749 Neutral/Relationship Dependant: T.P.Neutral 750 Product Hierarchy Reference Level: Each 751 Common value to all product hierarchy: No 752 Type: AN 753 Size: ..70 754

755 Definition: Description of the additional classification bundle 756 (code/agency + description). 757

758 Examples: "Special Breads" 759

760 Business Rules: The description of the additional classification bundle 761 (code/agency + description) can be repeated for each classification 762 agency used. Required if ClassificationCategoryCode field is populated. 763

764 765 Class Name: GDSNTradeItemClassification 766 767 Item Name: classificationCategoryCode 768 769

Core/Extension: C 770 Global Local Status: G 771 M/O/D: O 772 Multiple Values Allowed: N 773 Neutral/Relationship Dependant: T.P.Neutral 774 Product Hierarchy Reference Level: Each 775 Common value to all product hierarchy: No 776 Type: N 777 Size: 8 778

779 Definition: Global EAN.UCC classification category code. Unique, 780 permanent 8-digit key. 781

782 Examples: "10000276" 783

784 Business Rules: The system will assign Bricks on a first-approved, first-785 served basis. Mandatory within the Data Sync process. 786

Page 25: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 24 of 195

787 788 Class Name: GDSNTradeItemClassification 789 790 Item Name: classificationCategoryDefinition 791 792

Core/Extension: C 793 Global Local Status: G 794 M/O/D: Dependent on classificationCategoryCode 795 Multiple Values Allowed: N 796 Neutral/Relationship Dependant: T.P.Neutral 797 Product Hierarchy Reference Level: Each 798 Common value to all product hierarchy: No 799 Type: AN 800 Size: ..700 801

802 Definition: System generated explanation of Global EAN.UCC category. 803

804 Examples: distilled alcoholic grape drink without carbonation 805

806 Business Rules: This field is mandatory when 807 classificationCategoryCode is populated. 808

809 810 811 Class Name: GDSNTradeItemClassification 812 813 Item Name: classificationCategoryName 814 815

Core/Extension: C 816 Global Local Status: G 817 M/O/D: Dependent on classificationCategoryCode 818 Multiple Values Allowed: N 819 Neutral/Relationship Dependant: T.P.Neutral 820 Product Hierarchy Reference Level: Each 821 Common value to all product hierarchy: No 822 Type: AN 823 Size: ..105 824

825 Definition: The system generated text equivalent of the Global EAN.UCC 826 classification category code. 827

828 Examples: wine-still 829

830 Business Rules: Being system generated, if ClassificationCategoryCode 831 is populated, this field becomes mandatory 832 833

Page 26: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 25 of 195

834 Class Name: GDSNTradeItemClassification AttributeType 835 836 Item Name: eANUCCClassificationAttributeTypeCode 837 838

Core/Extension: E 839 Global Local Status: G 840 M/O/D: O 841 Multiple Values Allowed: Y 842 Neutral/Relationship Dependant: T.P.Neutral 843 Product Hierarchy Reference Level: Each 844 Common value to all product hierarchy: No 845 Type: N 846 Size: 8 847

848 Definition: Unique 8 digit code which identifies the Global EAN.UCC 849 classification attribute. 850

851 Examples: "20000212" wine-still variant 852

853 Business Rules: If used, the first attribute, which is the primary attribute, 854 is mandatory. The remaining 6 are optional. This field is repeatable seven 855 times. Mandatory in the Data Sync process. 856

857 858 Class Name: GDSNTradeItemClassificationAttributeType 859 860 Item Name: eANUCCClassificationAttributeTypeName 861 862

Core/Extension: E 863 Global Local Status: G 864 M/O/D: O 865 Multiple Values Allowed: Y 866 Neutral/Relationship Dependant: T.P.Neutral 867 Product Hierarchy Reference Level: Each 868 Common value to all product hierarchy: No 869 Type: AN 870 Size: ..105 871

872 Definition: The system generated text equivalent of the Global EAN.UCC 873 classification attribute code. 874

875 Examples: "grape variety " 20000081 876

877 Business Rules: Being system generated, if 878 ClassificationAttributeTypeCode is populated, this field becomes 879 mandatory. 880

Page 27: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 26 of 195

881 882 Class Name: GDSNTradeItemClassificationAttributeType 883 884 Item Name: eANUCCClassificationAttributeTypeDefinition 885 886

Core/Extension: E 887 Global Local Status: G 888 M/O/D: O 889 Multiple Values Allowed: Y 890 Neutral/Relationship Dependant: T.P.Neutral 891 Product Hierarchy Reference Level: Each 892 Common value to all product hierarchy: No 893 Type: AN 894 Size: ..700* 895

896 Definition: System generated explanation of Global EAN.UCC attribute. 897

898 Examples: 899

900 Business Rules: 901 *Waiting for the final publication of the EAN.UCC classification. 902

903 904 Class Name: GDSNTradeItemClassification AttributeValue 905 906 Item Name: eANUCCClassificationAttributeValueCode 907 908

Core/Extension: E 909 Global Local Status: G 910 M/O/D: O 911 Multiple Values Allowed: N 912 Neutral/Relationship Dependant: T.P.Neutral 913 Product Hierarchy Reference Level: Each 914 Common value to all product hierarchy: No 915 Type: N 916 Size: 8 917

918 Definition: Unique 8 digit code which identifies the Global EAN.UCC 919 classification attribute value. 920

921 Examples: See Implementation notes for full illustration. 922

923 Business Rules: One valid value may be submitted per GTIN. Once an 924 attribute code is selected, it is mandatory to submit an associated value 925 code. 926

Page 28: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 27 of 195

927 928 Class Name: GDSNTradeItemClassificationAttributeValue 929 930 Item Name: eANUCCClassificationAttributeValueName 931 932

Core/Extension: E 933 Global Local Status: G 934 M/O/D: O 935 Multiple Values Allowed: N 936 Neutral/Relationship Dependant: T.P.Neutral 937 Product Hierarchy Reference Level: Each 938 Common value to all product hierarchy: No 939 Type: AN 940 Size: ..105 941

942 Definition: The system generated text equivalent of the Global EAN.UCC 943 classification attribute value code. 944

945 Examples: See Implementation notes for full illustration. 946 947 Business Rules: 948

Page 29: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 28 of 195

949 3.5 TRADE ITEM INFORMATION: 950

951 Class Name: Information Provider 952 953 Item Name: informationProvider 954 955

Core/Extension: C 956 Global Local Status: G 957 M/O/D: M 958 Multiple Values Allowed: N 959 Neutral/Relationship Dependant: T.P.Neutral 960 Product Hierarchy Reference Level: All 961 Common value to all product hierarchy: Yes 962 Type: PartyIdentification 963 Size: Not Applicable 964

965 Definition: Unique location number identifying the information owner. E.g. 966 Distributor, broker, Manufacturer, Franchisee. This is not a third party service 967 provider. The purpose of this field is to identify the originator of the data. 968 Example Trade Item A - is availavble to retailer B from manufacter C or 969 distributor D. The retailer could receive information from both sellers and this 970 field declares the information owner. 971

972 Examples: Refer to the following websites for specific directions on how 973 to construct global location numbers - www.uc-council.org or www.ean-974 int.org 975 Business Rules: Combination of this field (gln) + gtin + target market 976 uniquely identifies a set of attributes for a trade item. The data owner is not 977 necessarily the source of the data, but has the responsibility to provide and 978 maintain the data in the catalogue. This field is mandatory within the Global 979 Data Synchronization work process. See implementation notes. 980

981 982 Class Name: InformationProvider 983 984 Item Name: nameOfInformation Provider 985 986

Core/Extension: E 987 Global Local Status: G 988 M/O/D: Dependent on informationProvider 989 Multiple Values Allowed: N 990 Neutral/Relationship Dependant: T.P.Neutral 991 Product Hierarchy Reference Level: All 992 Common value to all product hierarchy: Yes 993 Type: AN 994 Size: ..35 995

996 Definition: Name of the party who owns the data. Name of the 997 information provider on the trade item. 998

999

Page 30: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 29 of 195

Examples: Names of suppliers, wholesalers, manufacturers, distributors, 1000 or retailers 1001

1002 Business Rules: Mandatory when Information Provider is provided. 1003

1004 1005 Class Name: TargetMarketInformation 1006 1007 Item Name: targetMarketCountryCode 1008 1009

Core/Extension: C 1010 Global Local Status: G 1011 M/O/D: O 1012 Multiple Values Allowed: Y 1013 Neutral/Relationship Dependant: T.P.Neutral 1014 Product Hierarchy Reference Level: All 1015 Common value to all product hierarchy: Yes 1016 Type: N 1017 Size: 3 1018

1019 Definition: The target market code indicates the country level or higher 1020 geographical definition in which the information provider will make the 1021 GTIN available to buyers. This Indicator does not in any way govern 1022 where the buyer may re-sell the GTIN to consumers. 1023

1024 Examples: “036”=Australia, “300” = Greece, “524”= Nepal 1025

1026 Business Rules:ISO 3166-1 format 3 digit numerical; following AIDC 1027 guidelines. This information drives data synchronization rules linked to 1028 global/local, local status. Combination of this field +GTIN+GLN uniquely 1029 identifies a set of attributes or a trade item. This is a repeatable field. This 1030 field is mandatory within the Global Data Synchronization process. See 1031 implementation notes. 1032

1033 Class Name: TargetMarketInformation 1034 1035 Item Name: targetMarketDescription 1036 1037

Core/Extension: C 1038 Global Local Status: G 1039 M/O/D: D 1040 Multiple Values Allowed: N 1041 Neutral/Relationship Dependant:T.P.Neutral 1042 Product Hierarchy Reference Level: All 1043 Common value to all product hierarchy: Yes 1044 Type: Short Description 1045 Size: 35 1046

1047 Definition: The name for the specific target market identified with the 1048 Target Market Country Code . Target market description is composed of 1049

Page 31: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 30 of 195

both text and a language code. The description will be generated from the 1050 ISO 3166-1 code list. The language code will be generated from the ISO 1051 639 code list. 1052

1053 Examples: ISO 3166-1 840= "United States", 276= "Federal Republic of 1054 Germany, 156 = "China" 1055 1056 Business Rules: This is the textual indication of the target market code. 1057 See Section 4.4 of Implementation Considerations and Concerns for 1058 more details. 1059

1060 Class Name: TargetMarketInformation 1061 1062 Item Name: targetMarketSubdivisionCode 1063 1064

Core/Extension: C 1065 Global Local Status: G 1066 M/O/D: D 1067 Multiple Values Allowed: Y 1068 Neutral/Relationship Dependant:T.P.Neutral 1069 Product Hierarchy Reference Level: All 1070 Common value to all product hierarchy: Yes 1071 Type: AN 1072 Size: 7 1073

1074 Definition: The Target Market Subdivision Code is the secondary code of 1075 the Target Market and must be a subdivision of a Target Market Country 1076 Code. The Target Market Subdivision Code describes the "geo-political 1077 subdivision of a country" where the trade item is available for sale, as 1078 determined by the information provider. For example, "State" in the US, 1079 "Land" in Germany, "Region" in France, or "Province" in Canada. Not all 1080 countries have subdivisions. This code is represented by the three-1081 character ISO 3166-2 code. This Target Market Subdivision Code is a 1082 dependent attribute. It is important to note that the lack of the Target 1083 Market Subdivision code implies that the trade item is available in the 1084 entire target market country. 1085

1086 Examples: “ 1087 “208-025” where “208” represents Denmark from the ISO 3166-1 and 025 1088 represents the Danish county of Roskilde from the ISO 3166-2. 1089 “554-BOP” where “554” represents New Zealand from the ISO 3166-1 1090 and “BOP’ represents the Bay of Plenty. 1091

1092 Business Rules: ISO 3166-2 format 3 digit numerical/3 character alpha 1093 which represents country and subcountry code; following AIDC 1094 guidelines. This information drives data synchronization rules linked to 1095 global/local, local status. This optional field helps further define trade item 1096 availability. The target market code consists of a country code and an 1097 optional subdivision code. A subdivision code must be used in tandem 1098 with a corresponding higher level country code. (e.g. Ohio with US). 1099

Page 32: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 31 of 195

There can only be one targetMarketSubdivisionCode per 1100 targetMarketCountryCode. 1101

1102 Class Name: TradeItemDescriptionInformation 1103 1104 Item Name: additionalTradeItemDescription 1105 1106

Core/Extension: E 1107 Global Local Status: G/L 1108 M/O/D: O 1109 Multiple Values Allowed: N 1110 Neutral/Relationship Dependant:T.P.Neutral 1111 Product Hierarchy Reference Level: Consumer Unit 1112 Common value to all product hierarchy: No 1113 Type: LongTextDescription 1114 Size: ..350 1115

1116 Definition: Additional variants necessary to communicate to the industry to help 1117 define the product. Multiple variants can be established for each GTIN. This is a 1118 repeatable field, e.g. Style, Color, and Fragrance. 1119 1120 Examples: 1121 1122 Business Rules: May be used for additional technical or commercial 1123 information. . As a descriptive text field, this data element is repeatable for each 1124 language used and must be associated with a valid ISO language code from the 1125 attached table. See Section 4.4 of Implementation Considerations and Concerns 1126 for more details. 1127 1128 1129 Class Name: TradeItemDescriptionInformation 1130 1131 Item Name: brandName 1132 1133

Core/Extension: E 1134 Global Local Status: G 1135 M/O/D: M 1136 Multiple Values Allowed: N 1137 Neutral/Relationship Dependant:T.P.Neutral 1138 Product Hierarchy Reference Level: All 1139 Common value to all product hierarchy: No 1140 Type: AN 1141 Size: .. 35 1142

1143 Definition: The recognizable name used by a brand owner to uniquely 1144 identify a line of trade item or services. This is recognizable by the 1145 consumer. See examples. 1146

1147 Examples: ACME 1148

1149

Page 33: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 32 of 195

Business Rules: Free form text field, but not necessarily tied to 1150 language. Brands are more likely to be language independent. If a trade 1151 item does not have a brand, Use ‘unbranded’ in the description. This is a 1152 Mandatory field. If a trade item is changed from being "Unbranded" to a 1153 brand, this requires a new GTIN. GTIN allocation rules may vary by 1154 industry. 1155

1156 Class Name: TradeItemDescriptionInformation 1157 1158 Item Name: descriptionShort 1159 1160

Core/Extension: E 1161 Global Local Status: G 1162 M/O/D: O 1163 Multiple Values Allowed: N 1164 Neutral/Relationship Dependant:T.P.Neutral 1165 Product Hierarchy Reference Level: Each 1166 Common value to all product hierarchy: No 1167 Type: Multi-Short Description 1168 Size: 35 1169

1170 Definition: A free form short length description of the trade item that can 1171 be used to identify the trade item at point of sale. 1172

1173 Examples: Kel CrnF750g. 1174

1175 Business Rules: Free form text field, this data element is repeatable for 1176 each language used and must be associated with a valid ISO language 1177 code from the attached table. See Section 4.4 of the Implementation 1178 Considerations and Concernsfor more details. 1179

1180 Class Name: TradeItemDescriptionInformation 1181 1182 Item Name: functionalName 1183 1184

Core/Extension: E 1185 Global Local Status: G 1186 M/O/D: M 1187 Multiple Values Allowed: N 1188 Neutral/Relationship Dependant:T.P.Neutral 1189 Product Hierarchy Reference Level: All 1190 Common value to all product hierarchy: Yes 1191 Type: Multi-Short Description 1192 Size: ..35 1193

1194 Definition: Describes use of the product or service by the consumer. 1195 Should help clarify the product classification associated with the GTIN. 1196

1197 Examples: drill, salad dressing, soup, beer. 1198

1199

Page 34: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 33 of 195

Business Rules: Free form text field, this data element is repeatable for 1200 each language used and must be associated with a valid ISO language 1201 code from the attached table. See Section 4.4 of the Implementation 1202 Considerations and Concernsfor more details. 1203

1204 1205

Class Name: TradeItemDescriptionInformation 1206 1207 Item Name: invoiceName 1208 1209

Core/Extension: E 1210 Global Local Status: G 1211 M/O/D: O 1212 Multiple Values Allowed: N 1213 Neutral/Relationship Dependant:T.P.Neutral 1214 Product Hierarchy Reference Level: All 1215 Common value to all product hierarchy: No 1216 Type: Multi Short Description 1217 Size: ..35 1218

1219 Definition: Free form information provider assigned trade item 1220 description designed to match trade item/service description as noted on 1221 invoices. 1222

1223 Examples: 1224

1225 Business Rules: Free form text field, this data element is repeatable for 1226 each language used and must be associated with a valid ISO language 1227 code from the attached table. See Section 4.4 of the Implementation 1228 Considerations and Concerns for more details. Most likely will include 1229 several abbreviations. 1230

1231 Class Name: TradeItemDescriptionInformation 1232 1233 Item Name: linkToExternalDescription 1234 1235

Core/Extension: E 1236 Global Local Status: G 1237 M/O/D: O 1238 Multiple Values Allowed: N 1239 Neutral/Relationship Dependant:T.P.Neutral 1240 Product Hierarchy Reference Level: All 1241 Common value to all product hierarchy: No 1242 Type: AN 1243 Size: ..70 1244

1245 Definition: The link (e.g. URL) to the external description. 1246 1247 Examples: 1248

1249

Page 35: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 34 of 195

Business Rules: 1250 1251 Class Name: TradeItemDescriptionInformation 1252 1253 Item Name: tradeItemDescription 1254 1255

Core/Extension: C 1256 Global Local Status: G 1257 M/O/D: M 1258 Multiple Values Allowed: N 1259 Neutral/Relationship Dependant:T.P.Neutral 1260 Product Hierarchy Reference Level: All 1261 Common value to all product hierarchy: Yes 1262 Type:LongText Description 1263 Size: ..143 1264

1265 Definition*: The concatenated product description of a product or 1266 service. See business rules. 1267

1268 Examples*: When a supplier sends all information in maximum size the 1269 retailer will get for example following information: 1270 YummyCola_________________________Yummy_________________1271 _____________Drink______________________________Big Size__ 1272 ________________________ 1273 For automatic use of this information, e.g. on a tag, a separator should be 1274 given between all elements. E.g: Yummy-Cola; Yummy; Drink; Big Size. 1275

1276 Business Rules*: This field is automatically generated by the 1277 concatenation of the "brand"," sub-brand", "functional name" and 1278 "variant". Free form text field, this data element is repeatable for each 1279 language used and must be associated with a valid ISO language code . 1280 See implementation notes for more details. 1281

1282 * This is a derived attribute resulting from the concatenation of 4 other 1283 attributes of up to 35 characters each (see Business Rules above). When 1284 implemented, these four attributes may be concatenated as appropriate. 1285 Item description is part of the set of core data that will be stored in the 1286 Registry. 1287

1288 1289 Class Name: TradeItemDescriptionInformation 1290 1291 Item Name: productRange 1292 1293

Core/Extension: E 1294 Global Local Status: G 1295 M/O/D: O 1296 Multiple Values Allowed: N 1297 Neutral/Relationship Dependant:T.P.Neutral 1298 Product Hierarchy Reference Level: Each 1299

Page 36: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 35 of 195

Common value to all product hierarchy: No 1300 Type: AN 1301 Size: ..35 1302

1303 Definition: A name, used by a BrandOwner, that span multiple consumer 1304 categories or uses. E.g. (Waist Watchers) 1305

1306 Examples: The waist watcher product range includes salad dressings, 1307 receipt books, kitchen utensils, etc. 1308

1309 Business Rules: Text field 1310

1311 1312

Class Name: TradeItemDescriptionInformation 1313 1314 Item Name: subBrand 1315 1316

Core/Extension: E 1317 Global Local Status: G 1318 M/O/D: O 1319 Multiple Values Allowed: N 1320 Neutral/Relationship Dependant:T.P.Neutral 1321 Product Hierarchy Reference Level: All 1322 Common value to all product hierarchy: Yes 1323 Type: AN 1324 Size: ..35 1325

1326 Definition: Second level of brand. Can be a trademark. It is the primary 1327 differentiating factor that a brand owner wants to communicate to the 1328 consumer or buyer. E.g. Yummy-Cola Classic. In this example Yummy-1329 Cola is the brand and Classic is the subBrand. 1330

1331 Examples: 1332

1333 Business Rules: Text field 1334

1335 1336 Class Name: TradeItemDescriptionInformation 1337 1338 Item Name: tradeItemFormDescription 1339 1340

Core/Extension: E 1341 Global Local Status: G 1342 M/O/D: O 1343 Multiple Values Allowed: Y 1344 Neutral/Relationship Dependant:T.P.Neutral 1345 Product Hierarchy Reference Level: Each 1346 Common value to all product hierarchy: No 1347 Type: AN 1348 Size: ..35 1349

Page 37: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 36 of 195

1350 Definition: The physical form or shape of the product. Used, for 1351 example, in pharmaceutical industry to indicate the formulation of the 1352 trade item. Defines the form the trade item takes and is distinct from the 1353 form of the packaging. 1354

1355 Examples: "tablet", "powder", "gel", "shredded", "liquid","granules" 1356

1357 Business Rules: Optional field that can be used to further describe a 1358 trade item's benefit delivery method. Free form text. (See examples) 1359 1360 1361

Class Name: TradeItemDescriptionInformation 1362 1363 Item Name: tradeItemGroupIdentificationCode 1364 1365

Core/Extension: E 1366 Global Local Status: G 1367 M/O/D: O 1368 Multiple Values Allowed: N 1369 Neutral/Relationship Dependant:T.P.Neutral 1370 Product Hierarchy Reference Level: Each 1371 Common value to all product hierarchy: No 1372 Type: AN 1373 Size: ..20 1374

1375 Definition: A code assigned by the supplier or manufacturer to logically 1376 group trade item independently from the Global trade item Classification. 1377

1378 Examples: Code representing a group of GTINs for all 501 Blue Jeans 1379 sizes and colors 1380 123= 1381 GTIN1 501 Blue/38 1382 GTIN2 501 Blue/40 1383 GTIN3 501 Black/38 1384 GTIN4 501 Black/40 1385

1386 Business Rules: Manufacturer assigned. This code is typically assigned 1387 to multiple GTINs. 1388

1389 1390

Class Name: TradeItemDescriptionInformation 1391 1392 Item Name: tradeItemGroupIdentificationDescription 1393 1394

Core/Extension: E 1395 Global Local Status: G 1396 M/O/D: D 1397 Multiple Values Allowed: Y 1398 Neutral/Relationship Dependant: T.P.Neutral 1399

Page 38: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 37 of 195

Product Hierarchy Reference Level: Each 1400 Common value to all product hierarchy: No 1401 Type: Multi Short Description 1402 Size: ..35 1403

1404 Definition: The text description of the value represented by the trade 1405 itemGroupIDCode 1406

1407 Examples: "501 Blue Jeans", represent all sized and colors of this trade 1408 item 1409

1410 Business Rules: If trade itemGroupIDCode is present, description must 1411 be present. A description text field, this data element is repeatable for 1412 each language used and linked to data element "Description language". 1413

1414 1415

Class Name: TradeItemDescriptionInformation 1416 1417 Item Name: variant 1418 1419

Core/Extension: E 1420 Global Local Status: G 1421 M/O/D: O 1422 Multiple Values Allowed: Y 1423 Neutral/Relationship Dependant: T.P.Neutral 1424 Product Hierarchy Reference Level: Each 1425 Common value to all product hierarchy: No 1426 Type: Multi Short Description 1427 Size: ..35 1428

1429 Definition: Free text field used to identify the variant of the product. 1430 Variants are the distinguishing characteristics that differentiate products 1431 with the same brand and size including such things as the particular 1432 flavor, fragrance, taste. 1433

1434 Examples: Examples: Bananna, Strawberry, Lemon Scented. 1435

1436 Business Rules: This is different from the Global EAN.UCC product 1437 classification variant. Free form text field, this data element is repeatable 1438 for each language used and must be associated with a valid ISO 1439 language code from the attached table. See Section 4.4 of the -1440 Implementation Considerations and Concerns for more details. 1441 1442

Page 39: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 38 of 195

3.6 TRADING PARTNER NEUTRAL TRADE ITEM INFORMATION: 1443 1444

Class Name: TradingPartnerNeutralTradeItemInformation 1445 1446 Item Name: barCodeType 1447 1448

Core/Extension: E 1449 Global Local Status: G 1450 M/O/D: O 1451 Multiple Values Allowed: Y 1452 Neutral/Relationship Dependant: T.P.Neutral 1453 Product Hierarchy Reference Level: All 1454 Common value to all product hierarchy: No 1455 Type: Enumerated List 1456 Size: Not Applicable 1457

1458 Definition: The type of bar code or codes, which are visible on a trade 1459 item. 1460

1461 Examples: RSS Expanded Stacked 1462

1463 Business Rules: Multiple values allowed. Use enumerated BarCode 1464 Type List in Trading Partner Neutral Trade Item Information Class 1465 Diagram 1466

1467 1468 Class Name: TradingPartnerNeutralTradeItemInformation 1469 1470 Item Name: .classComplianceRegulationCode 1471 1472

Core/Extension: E 1473 Global Local Status: G 1474 M/O/D: O 1475 Multiple Values Allowed: Y 1476 Neutral/Relationship Dependant: T.P.Neutral 1477 Product Hierarchy Reference Level: All 1478 Common value to all product hierarchy: No 1479 Type: Enumerated List 1480 Size: Not Applicable 1481

1482 Definition: A code that indicates that a trade item is in compliance with 1483 specific applicable government regulations. Different municipalities 1484 require this on items shipped-to or sold-in the municipality. 1485

1486 Examples: Compliant With Flammability Act 1487

1488 Business Rules: 1489

1490 1491 1492

Page 40: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 39 of 195

Class Name: TradingPartnerNeutralTradeItemInformation 1493 1494 Item Name: tradeItemCountryOfAssembly 1495 1496

Core/Extension: E 1497 Global Local Status: G 1498 M/O/D: O 1499 Multiple Values Allowed: Y 1500 Neutral/Relationship Dependant: T.P.Neutral 1501 Product Hierarchy Reference Level: Each 1502 Common value to all product hierarchy: No 1503 Type: N 1504 Size: 3 1505

1506 Definition: Country where product is assembled. Uses ISO country 1507 codes.. 1508

1509 Examples: "Canada, United States 1510

1511 Business Rules: 1512

1513 Class Name: TradingPartnerNeutralTradeItemInformation 1514 1515 Item Name: tradeItemCountryOfOrigin 1516 1517

Core/Extension: E 1518 Global Local Status: G 1519 M/O/D: M 1520 Multiple Values Allowed: Y 1521 Neutral/Relationship Dependant: T.P.Neutral 1522 Product Hierarchy Reference Level: Each 1523 Common value to all product hierarchy: No 1524 Type: N 1525 Size: 3 1526

1527 Definition: The country code (codes) in which the goods have been 1528 produced or manufactured, according to criteria established for the 1529 purposes of application of the value may or may not be presented on the 1530 trade item label. 1531

1532 Examples: Canada, United States 1533

1534 Business Rules: This information is for customs purpose in case of 1535 importation or legal requirements regarding customer information for 1536 some categories of trade item (e.g. meats and fruits) Information can be 1537 repeated if multiple countries are valid. In this case, the buyer will only 1538 know the actual country of origin at the time of delivery. Code list ISO 1539 3166-1 code. 1540

1541 1542

Page 41: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 40 of 195

1543 Class Name: BrandOwnerOfTradeItem 1544 1545 Item Name: brandOwner - represented by relation to Party Identification 1546 1547

Core/Extension: E 1548 Global Local Status: G 1549 M/O/D: O 1550 Multiple Values Allowed: N 1551 Neutral/Relationship Dependant: T.P.Neutral 1552 Product Hierarchy Reference Level: All 1553 Common value to all product hierarchy: Yes 1554 Type: PartyIdentification 1555 Size: ..Not Applicable 1556

1557 Definition: Unique location number identifying the brand owner. May or 1558 may not be the same entity as the information provider, which actually 1559 enters and maintains data in data pools. 1560

1561 Examples: GLN, DUNS_PLUS_FOUR 1562

1563 Business Rules: The brand owner is the source of the data relating to 1564 the trade item, but is not necessarily responsible for providing and 1565 maintaining the data in the catalogue. 1566 This is the responsibility of the information provider. 1567 While the class BrandOwnerOfTradeItem is optional, the party 1568 identification for the brand owner is required when a brand owner is 1569 present. 1570

1571 1572 Class Name: BrandOwnerOfTradeItem 1573

1574 Item Name: nameOfBrandOwner 1575 1576

Core/Extension: E 1577 Global Local Status: G 1578 M/O/D: D 1579 Multiple Values Allowed: N 1580 Neutral/Relationship Dependant: T.P.Neutral 1581 Product Hierarchy Reference Level: All 1582 Common value to all product hierarchy: Yes 1583 Type: AN 1584 Size: ..35 1585

1586 Definition: Name of the party who owns the brand of the trade item. 1587

1588 Examples: Manufacturer of branded trade item - Can also be distributor 1589 or retailer that licenses a brand name to various private label 1590 manufacturers. 1591

1592

Page 42: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 41 of 195

Business Rules: Mandatory when brandOwner Party identification is 1593 provided 1594 1595

Class Name: HazardousInformationDetail 1596 1597 Item Name: classOfDangerousGoods 1598 1599

Core/Extension: E 1600 Global Local Status: G 1601 M/O/D: D 1602 Multiple Values Allowed: Y 1603 Neutral/Relationship Dependant: T.P.Neutral 1604 Product Hierarchy Reference Level: All 1605 Common value to all product hierarchy: No 1606 Type: AN 1607 Size: 4 1608

1609 Definition: Dangerous goods classification of the trade item. There are 9 1610 danger classes, some classes are further subdivided into subclasses. 1611 "Class" number explains in general terms the nature and properties of the 1612 goods and serves to classify them together in terms of their most 1613 significant risk. 1614

1615 Examples: Class “4.2”: Substances liable to spontaneous combustion. 1616 Class “6.1”: Toxic substances 1617

1618 Business Rules: Information required when dangerousGoodsIndicator 1619 equals Y. Subsidiary risks given by repeating attribute value. Repeatable 1620 per dangerousGoodsRegulation code. Refer to UNECE code list. 1621 Hazardous attributes relate to supply chain handling (e.g., transport, 1622 storage, handling). 1623

1624 1625 Class Name: HazardousInformationDetail 1626 1627 Item Name: dangerousGoodsAMarginNumber 1628 1629

Core/Extension: E 1630 Global Local Status: L 1631 M/O/D: D 1632 Multiple Values Allowed: Y 1633 Neutral/Relationship Dependant: T.P.Neutral 1634 Product Hierarchy Reference Level: All 1635 Common value to all product hierarchy: No 1636 Type: AN 1637 Size: ..30 1638

1639 Definition: Information, whether for the base trade item or further 1640 packaging trade item a dangerous goods a-margin number does exist in 1641 the European dangerous goods agreements (and in the respective 1642

Page 43: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 42 of 195

national dangerous goods legislation), thus facilitations for the transport of 1643 defined limited quantity by road or rail are possible or not. If they are 1644 possible, they must be indicated, whether they are used by the data 1645 supplier. 1646

1647 Examples: "not possible" 1648

1649 Business Rules: Information required when dangerousGoodsIndicator 1650 equals Y. 1651 Repeatable per dangerousGoodsRegulation code. 1652 List of authorized values : 1653 - not possible 1654 - possible (but not used) 1655 - used (by the data supplier) 1656 Hazardous attributes relate to supply chain handling (e.g., transport, 1657 storage, handling). 1658

1659 1660 Class Name: HazardousInformationDetail 1661 1662 Item Name: dangerousGoodsHazardousCode 1663 1664

Core/Extension: E 1665 Global Local Status: G 1666 M/O/D: D 1667 Multiple Values Allowed: Y 1668 Neutral/Relationship Dependant: T.P.Neutral 1669 Product Hierarchy Reference Level: All 1670 Common value to all product hierarchy: No 1671 Type: AN 1672 Size: 10 1673

1674 Definition: Dangerous goods hazard ID number, which must be applied 1675 to the vehicle, when transporting this trade item (dangerous good) by 1676 road or rail, to inform the police, the fire brigade and others in case of an 1677 accident about the kind of danger caused by the cargo. 1678

1679 Examples: - 1680

1681 Business Rules: Information required when dangerousGoodsIndicator 1682 equals Y. Repeatable per dangerousGoodsRegulationcode. Hazardous 1683 attributes relate to supply chain handling (e.g., transport, storage, 1684 handling). 1685

Page 44: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 43 of 195

1686 1687

Class Name: HazardousInformationDetail 1688 1689 Item Name: dangerousGoodsPackingGroup 1690 1691

Core/Extension: E 1692 Global Local Status: G 1693 M/O/D: D 1694 Multiple Values Allowed: Y 1695 Neutral/Relationship Dependant: T.P.Neutral 1696 Product Hierarchy Reference Level: All 1697 Common value to all product hierarchy: No 1698 Type: AN 1699 Size: 3 1700

1701 Definition: Identifies the degree of risk these dangerous goods present 1702 during transport according to IATA/IMDG/ADR/RID regulations. 1703

1704 Examples: Group I : Great danger - Packaging meeting criteria to pack 1705 hazardous materials with great danger. 1706

1707 Business Rules: Information required when 1708 dangerousGoodsRegulationcode is populated. Repeatable per 1709 dangerousGoodsRegulation code. 1710 http://www.unece.org/trade/untdid/d99b/tred/tred8339.htm 1711 1712 Hazardous attributes relate to supply chain handling (e.g., transport, 1713 storage, handling). 1714 1715

Class Name: HazardousInformationDetail 1716 1717 Item Name: dangerousGoodsShippingName 1718 1719

Core/Extension: E 1720 Global Local Status: G 1721 M/O/D: D 1722 Multiple Values Allowed: Y 1723 Neutral/Relationship Dependant: T.P.Neutral 1724 Product Hierarchy Reference Level: All 1725 Common value to all product hierarchy: No 1726 Type: AN 1727 Size: ..200 1728

1729 Definition: Shipping name of the trade item (dangerous goods). The 1730 recognized agencies (see dangerousGoodsRegulationsCodes), in their 1731 regulations, provide a list of all acceptable proper shipping names. 1732

1733 Examples: "Flammable Liquid" 1734

1735

Page 45: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 44 of 195

Business Rules: Information required when 1736 dangerousGoodsRegulationCode is populated. Repeatable per 1737 dangerousGoodsRegulation code. Hazardous attributes relate to supply 1738 chain handling (e.g., transport, storage, handling). 1739

1740 1741

Class Name: HazardousInformationDetail 1742 1743 Item Name: dangerousGoodsTechnicalName 1744 1745

Core/Extension: E 1746 Global Local Status: G 1747 M/O/D: D 1748 Multiple Values Allowed: Y 1749 Neutral/Relationship Dependant: T.P.Neutral 1750 Product Hierarchy Reference Level: All 1751 Common value to all product hierarchy: No 1752 Type: LongTextDescription 1753 Size: .200 1754

1755 Definition: Chemical term of the trade item, listed by name and allowed 1756 in the substance list of GGVS (Dangerous Goods Ordinance for Roads) 1757 or GGVE (Dangerous Goods Ordinance for Rail). This is composed of 1758 both text and a language code. The language for text is specified using 1759 the two-digit ISO 639 list. 1760

1761 Examples: "TRINITROCHLORO-BENZENE (PICRYL CHLORIDE), 1762 WETTED" 1763

1764 Business Rules: Information required when 1765 dangerousGoodsRegulationcode is populated. The technical names are 1766 listed in the order that they contribute to the danger (main hazard, not 1767 necessarily the highest concentration). 1768 Repeatable per dangerousGoodsRegulation code. Hazardous attributes 1769 relate to supply chain handling (e.g., transport, storage, handling). 1770 See Section 4.4 of Implementation Considerations and Concerns for 1771 more details. 1772 1773 1774

Class Name: HazardousInformationDetail 1775 1776 Item Name: unitedNationsDangerousGoodsNumber 1777 1778

Core/Extension: E 1779 Global Local Status: G 1780 M/O/D: D 1781 Multiple Values Allowed: Y 1782 Neutral/Relationship Dependant: T.P.Neutral 1783 Product Hierarchy Reference Level: All 1784 Common value to all product hierarchy: No 1785

Page 46: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 45 of 195

Type: N 1786 Size: 4 1787

1788 Definition: The four-digit number assigned by the United Nations 1789 Committee of Experts on the Transport of Dangerous Goods to classify a 1790 substance or a particular groups of substances. Abbreviation: UNDG 1791 Number 1792

1793 Examples: UN "1155" ETHYLENEGLYCOLDIETHYLETHER 1794

1795 Business Rules: Information required when 1796 dangerousGoodsRegulationcode is populated 1797 Repeatable per dangerousGoodsRegulation code. 1798 http://www.unece.org/trans/danger/publi/adr/adr2001/English/ 1799

1800 Hazardous attributes relate to supply chain handling (e.g., transport, 1801 storage, handling). 1802

Page 47: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 46 of 195

1803 Class Name: ManufacturerOfTradeItem 1804 1805 Item Name: manufacturer- represented by relationship to Party Identification 1806 1807

Core/Extension: E 1808 Global Local Status: G 1809 M/O/D: D 1810 Multiple Values Allowed: Y 1811 Neutral/Relationship Dependant: T.P.Neutral 1812 Product Hierarchy Reference Level: All 1813 Common value to all product hierarchy: Yes 1814 Type: PartyIdentification 1815 Size: Not Applicable. 1816

1817 Definition: GLN identifying the manufacturer of a trade item. May or may 1818 not be the brand owner, could be a contract manufacturer. GLN 1819 identifying manufacturer of a trade item: this is repeatable field. 1820

1821 Examples: Brand owner A uses contract manufacturers B and C to 1822 produce trade item D. This field would provide a GLN for manufacturers B 1823 and or C 1824

1825 Business Rules: While the class ManufacturerOfTradeItem is optional, 1826 the party identification for the manufacturer is required when the 1827 manufacturer of trade item is populated. 1828 1829 1830

Class Name: ManufacturerOfTradeItem 1831 1832 Item Name: nameOfManufacturer 1833 1834

Core/Extension: E 1835 Global Local Status: G 1836 M/O/D: O 1837 Multiple Values Allowed: Y 1838 Neutral/Relationship Dependant: T.P.Neutral 1839 Product Hierarchy Reference Level: All 1840 Common value to all product hierarchy: Yes 1841 Type: AN 1842 Size: ..35 1843

1844 Definition: Descriptive name of the manufacturer of the trade item. 1845

1846 Examples: 1847

1848 Business Rules: May or may not be the brand owner. This is not the 1849 name of a party that assembles trade item. It is an optional field, manually 1850 maintained, that can identify the company that manufactures the product. 1851 This is a repeatable field. 1852

Page 48: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 47 of 195

1853 Class Name: MarketingInformation 1854

1855 Item Name: campaignName 1856 1857

Core/Extension: E 1858 Global Local Status: G 1859 M/O/D: O 1860 Multiple Values Allowed: N 1861 Neutral/Relationship Dependant: T.P.Neutral 1862 Product Hierarchy Reference Level: All 1863 Common value to all product hierarchy: Yes 1864 Type: Description 1865 Size: ..70 1866 1867 Definition: Name of the sales or marketing campaign, for which the 1868 textile trade item is intended. Input of user-defined text in order to assign 1869 the item to a specific marketing campaign. Used to specify promotions, 1870 marketing. 1871 1872 Examples: Home Fashion theme such as 'Alexandra' or an Apparel 1873 theme such as '501 Blue'. 1874 1875 Business Rules: 1876

1877 Class Name: MarketingInformation 1878 1879 Item Name: campaignStartDate 1880 1881

Core/Extension: E 1882 Global Local Status: G 1883 M/O/D: O 1884 Multiple Values Allowed: N 1885 Neutral/Relationship Dependant: T.P.Neutral 1886 Product Hierarchy Reference Level: All 1887 Common value to all product hierarchy: Yes 1888 Type: Date 1889 Size: CCYY-MM-DD 1890

1891 Definition: The date suggested by the supplier for the campaign to start. 1892 It indicates the beginning of a marketing campaign. 1893 1894 Examples: 2005-02-01. 1895

1896 Business Rules: 1897

1898 Class Name: MarketingInformation 1899 1900 Item Name: campaignEndDate 1901 1902

Page 49: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 48 of 195

Core/Extension: E 1903 Global Local Status: G 1904 M/O/D: O 1905 Multiple Values Allowed: N 1906 Neutral/Relationship Dependant: T.P.Neutral 1907 Product Hierarchy Reference Level: All 1908 Common value to all product hierarchy: Yes 1909 Type: Date 1910 Size: CCYY-MM-DD 1911 1912 Definition: The date suggested by the supplier for the campaign to end. 1913 It indicates the end of a marketing campaign. 1914 1915 Examples: 2005-05-01 1916 1917 Business Rules: 1918 1919

1920 Class Name: MarketingInformation 1921 1922 Item Name: specialItemCode 1923 1924

Core/Extension: E 1925 Global Local Status: G 1926 M/O/D: O 1927 Multiple Values Allowed: Y 1928 Neutral/Relationship Dependant: T.P.Neutral 1929 Product Hierarchy Reference Level: All 1930 Common value to all product hierarchy: Yes 1931 Type: Enumerated List 1932 Size: Not Applicable 1933

1934 Definition: This element identifies specific items for promotional or 1935 special tracking purposes. For example Dynamic Assortment: Chia Pets 1936 are sold individually to the consumer and each different Chia Pet is 1937 marked with a unique GTIN. The items are ordered by the case, which 1938 has its own unique GTIN. The case will contain a random assortment of 1939 Chia Pets. There is no guarantee that the same ratio of child items will be 1940 in a case from order to order but the total quantity of items in the case will 1941 remain the same. 1942

1943 A collateral item is a trade item delivered from a manufacturer to the retail 1944 selling floor that is not considered inventory and has no retail value. 1945 1946 A Gift with Purchase (GWP) is a trade item given to a consumer as part of 1947 a promotional event, contingent on the consumer making a purchase of 1948 another item or items. A Gift with Purchase is considered inventory and 1949 has no retail value. 1950 1951

Page 50: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 49 of 195

A Purchase with Purchase (PWP) is a trade item sold to a consumer at a 1952 special price as part of a promotional event, contingent on the consumer 1953 purchasing another item or items. A Purchase with Purchase is 1954 considered inventory and has a retail value. 1955 1956 A Dynamic Assortment is when the quantity of the case remains fixed, 1957 however the mix of the lower level GTINs may vary from case to case. If 1958 Next Lower Level Trade Item Information is specified the actual quantity 1959 of each child item may be different from pack to pack. The pack may 1960 even contain only one of the child items, however the pack will always 1961 contain the number of items specified in the 1962 totalQuantityOfNextLowerLevelTradeItem. 1963 1964 If Next Lower Level Trade Item Information is specified the actual quantity 1965 of each child item may be different from pack to pack. The pack may 1966 even contain only one of the child items, however the pack will always 1967 contain the number of items specified in the 1968 totalQuantityOfNextLowerLevelTradeItem. 1969 1970 Examples: 1971 1972 Business Rules: Dynamic Assortment may only be specified when the 1973 tradeItemUnitDescriptor specifies PREPACK. 1974

1975 Class Name: MarketingInformation 1976 1977 Item Name: tradeItemFeatureBenefit: 1978 1979

Core/Extension: E 1980 Global Local Status: G 1981 M/O/D: O 1982 Multiple Values Allowed: Y 1983 Neutral/Relationship Dependant: T.P.Neutral 1984 Product Hierarchy Reference Level: All 1985 Common value to all product hierarchy: Yes 1986 Type: Description 1987 Size: 70 1988

1989 Definition: Element for consumer facing marketing content to describe 1990 the key features or benefits of the style suitable for display purposes. 1991 Needed for marketing to enable product comparison. 1992 1993 Examples: 'pre-shrunk'. 1994 1995 Business Rules: 1996

Page 51: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 50 of 195

1997 Class Name: MarketingInformation 1998 1999 Item Name: tradeItemMarketingMessage 2000 2001

Core/Extension: E 2002 Global Local Status: G 2003 M/O/D: O 2004 Multiple Values Allowed: N 2005 Neutral/Relationship Dependant: T.P.Neutral 2006 Product Hierarchy Reference Level: All 2007 Common value to all product hierarchy: Yes 2008 Type: Long Description 2009 Size: 1000 2010

2011 Definition: Marketing message associated to the Trade item. 2012 2013 Examples:'Quality in Style'. 2014 2015 Business Rules: 2016 2017 2018

Class Name: MaterialComposition 2019 2020 Item Name: materialCode 2021

2022 Core/Extension: E 2023 Global Local Status: G 2024 M/O/D: O 2025 Multiple Values Allowed: N 2026 Neutral/Relationship Dependant: T.P.Neutral 2027 Product Hierarchy Reference Level: All 2028 Common value to all product hierarchy: Yes 2029 Type: Multi Description 2030 Size: 70 2031

2032 Definition: This element indicates the product material code that gives 2033 the composition of the trade item's first main material up to six material 2034 short codes that can be given in descending order of their respective 2035 percentages. This element may be used to specify agency code or 2036 country specific code used to indicate materials that the trade item 2037 consists of. 2038 2039 Examples: CO Cotton; PE Polyethylene; PA Polyamide. 2040

2041 Business Rules: materialCode and materialAgencyCode are paired 2042 elements; if one is used, the other must be present. These fields are 2043 used in conjunction with the percentage. materialCode should match the 2044 value of materialContent if both are populated. 2045

2046

Page 52: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 51 of 195

Class Name: MaterialComposition 2047 2048 Item Name: materialAgencyCode: 2049 2050

Core/Extension: E 2051 Global Local Status: G 2052 M/O/D: O 2053 Multiple Values Allowed: N 2054 Neutral/Relationship Dependant: T.P.Neutral 2055 Product Hierarchy Reference Level: All 2056 Common value to all product hierarchy: Yes 2057 Type: Enumerated List 2058 Size: Not Applicable 2059

2060 Definition: This element indicates the agency that is maintaining the 2061 Trade Item Material codes. This may include a specific code list. 2062 Reference “DIN 60001, Part 4 - Textile Fibers Codes. Available from DIN 2063 - Deutsches Institut für Normung E.V (German Institute for 2064 Standardization E.V). 2065

2066 Examples:. 2067

2068 Business Rules: materialCode and materialAgencyCode are paired 2069 elements; if one is used the other must be present. These fields are used 2070 in conjunction with the percentage. 2071

2072 2073 2074 Class Name: MaterialComposition 2075 2076 Item Name: materialPercentage: 2077 2078

Core/Extension: E 2079 Global Local Status: G 2080 M/O/D: O 2081 Multiple Values Allowed: N 2082 Neutral/Relationship Dependant: T.P.Neutral 2083 Product Hierarchy Reference Level: All 2084 Common value to all product hierarchy: Yes 2085 Type: Percentage 2086 Size: 3.2 2087

2088 Definition: Net weight percentage of a product material of the first main 2089 material. The percentages must add up to 100. 2090 2091 Example: CO Cotton 50%; PE Polyethylene 40%; PA Polyamide 10%. 2092

2093 Business Rules: This field can be used in conjunction with the fields 2094 'materialCode' or 'materialContent' 2095

2096

Page 53: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 52 of 195

Class Name: MaterialComposition 2097 2098 Item Name: materialContent 2099

2100 Core/Extension: E 2101 Global Local Status: G 2102 M/O/D: O 2103 Multiple Values Allowed: N 2104 Neutral/Relationship Dependant: T.P.Neutral 2105 Product Hierarchy Reference Level: All 2106 Common value to all product hierarchy: Yes 2107 Type: Description 2108 Size: 70 2109

2110 Definition: This element is used to indicate the material composition. 2111 This element is used in conjunction with materialPercentage. 2112 2113 Example: cotton and acetate. It describes the composition of each 2114 material (e.g., plastic, rubber) contained in the trade item. 2115

2116 Business Rules: materialContent should match the value of 2117 materialCode if both are populated. 2118

2119 Class Name: MaterialSafetyData 2120 2121 Item Name: materialSafetyDataSheetNumber 2122 2123

Core/Extension: E 2124 Global Local Status: G 2125 M/O/D: Dependent on MaterialSafetyData 2126 Multiple Values Allowed: N 2127 Neutral/Relationship Dependant: T.P.Neutral 2128 Product Hierarchy Reference Level: All 2129 Common value to all product hierarchy: No 2130 Type: AN 2131 Size: ..20 2132

2133 Definition: Manufacturer's identification number for the material safety 2134 data sheet for a trade item. 2135

2136 Examples: "4711", "ag34784", "zruifk" 2137

2138 Business Rules: This is an internal number which is distributed by the 2139 manufacturer. Can be in any format. This attribute is mandatory if the 2140 Material Safety Data Sheet attribute is “Y”. 2141

2142 2143 2144 2145 2146

Page 54: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 53 of 195

Class Name: MaterialSafetyData 2147 2148 Item Name: materialSafetyDataSheet- this boolean question is answered by 2149 the population of materialSafetyDataSheetNumber. It is thus not represented in 2150 the model and the schemas. 2151 2152

Core/Extension: E 2153 Global Local Status: G 2154 M/O/D: M 2155 Multiple Values Allowed: NNeutral/Relationship Dependant: 2156 T.P.Neutral 2157 Product Hierarchy Reference Level: All 2158 Common value to all product hierarchy: No 2159 Type: Boolean 2160 Size: 1 2161

2162 Definition: Indicates whether there exists a material safety data sheet for 2163 the trade item. This is a data sheet with the most important 2164 characteristics, protected measures and regulations to be adhered to 2165 when handling this trade item. It is relevant above all for dangerous 2166 substances. 2167

2168 Example: 2169

2170 Business Rules: 2171

2172 2173 Class Name: NonPackageTradeItemDimension 2174 2175 Item Name: sizeGroup 2176 2177

Core/Extension: E 2178 Global Local Status: G 2179 M/O/D: O 2180 Multiple Values Allowed: N 2181 Neutral/Relationship Dependant: T.P.Neutral 2182 Product Hierarchy Reference Level: All 2183 Common value to all product hierarchy: Yes 2184 Type: Enumerated List 2185 Size: Not Applicable 2186

2187 Definition: A description of the variable size that is necessary to uniquely 2188 specify the size of the item in conjunction with the non-packaged size 2189 dimension. 2190 2191 Example: The size group would be Petite and the size would be “8”. 2192

2193 Business Rules: 2194

2195 2196

Page 55: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 54 of 195

Class Name: NonPackageTradeItemDimension 2197 2198 Item Name: sizeSystem 2199 2200

Core/Extension: E 2201 Global Local Status: G 2202 M/O/D: O 2203 Multiple Values Allowed: N 2204 Neutral/Relationship Dependant: T.P.Neutral 2205 Product Hierarchy Reference Level: All 2206 Common value to all product hierarchy: Yes 2207 Type: Enumerated List 2208 Size: Not Applicable 2209

2210 Definition: This is the system that is being used to define the size. It is 2211 used in conjunction with size group to completely define the size 2212 dimension. 2213 2214 Example: A shoe that is 10 inches or 25.4 centimeters could be specified 2215 without using this attribute, however, the same 10 inch shoe is a men size 2216 71/2 in U.S., women size 9 in the U.S., men size 7 in the U.K., 40 in 2217 Europe (no distinction between men and women), women size 25 in 2218 Japan, and size 6 in Mexico. This will allow for the size dimensions to be 2219 specified in using different size systems. 2220 2221 Business Rules: 2222 2223

2224 Class Name: NonPackageTradeItemDimension 2225 2226 Item Name: sizeType: 2227 2228

Core/Extension: E 2229 Global Local Status: G 2230 M/O/D: M 2231 Multiple Values Allowed: N 2232 Neutral/Relationship Dependant: T.P.Neutral 2233 Product Hierarchy Reference Level: All 2234 Common value to all product hierarchy: Yes 2235 Type: Enumerated List 2236 Size: Not Applicable 2237

2238 Definition: The type of size dimension being specified by the size 2239 measurement 2240 2241 Example: The size type would be Back and the size would be 34”. 2242

2243 Business Rules: 2244

2245 2246

Page 56: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 55 of 195

Class Name: NonPackageTradeItemDimension 2247 2248 Item Name: sizeDimension 2249

2250 Core/Extension: E 2251 Global Local Status: G 2252 M/O/D: M 2253 Multiple Values Allowed: N 2254 Neutral/Relationship Dependant: T.P.Neutral 2255 Product Hierarchy Reference Level: All 2256 Common value to all product hierarchy: Yes 2257 Type: Measurement 2258 Size: Decimal 15, String 3 for Unit Of Measure 2259

2260 Definition: The numerical size measurement of the size dimension 2261 specified by the size type. 2262 2263 Example: The size type would be Back and the size would be 34 inches. 2264 2265 Business Rules: The size dimension is specified using a decimal value 2266 and a valid Unit Of Measure (UOM). Either sizeDimension or 2267 descriptiveSizeDimension must be present, but not both. sizeDimension 2268 is a measurement value and is part of a mandatory choice (the other 2269 choice value being descriptiveSizeDimension). 2270

2271 2272

Class Name: NonPackageTradeItemDimension 2273 2274 Item Name: descriptiveSizeDimension 2275 2276

Core/Extension: E 2277 Global Local Status: G 2278 M/O/D: M 2279 Multiple Values Allowed: N 2280 Neutral/Relationship Dependant: T.P.Neutral 2281 Product Hierarchy Reference Level: All 2282 Common value to all product hierarchy: Yes 2283 Type: Description 2284 Size: 70 2285

2286 Definition: The textual representation of the size dimension specified by 2287 the size type. 2288 2289 Example: The size type would be Sleeve and the size would be “32/33 2290 inches”. 2291 2292 Business Rules: Either sizeDimension or descriptiveSizeDimension 2293 must be present, but not both. descriptiveSizeDimension is a description 2294 and is part of a mandatory choice (the other choice value being 2295 sizeDimension). 2296

Page 57: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 56 of 195

2297 Class Name: Ordering And Selling Unit Of Measure 2298 2299 Item Name: orderingUnitOfMeasure 2300

2301 Core/Extension: E 2302 Global Local Status: G 2303 M/O/D: O 2304 Multiple Values Allowed: N 2305 Neutral/Relationship Dependant: T.P.Neutral 2306 Product Hierarchy Reference Level: All 2307 Common value to all product hierarchy: Yes 2308 Type: String 2309 Size: 70 2310

2311 Definition: The alternate Unit of Measure of how Trade Items are 2312 ordered by the Retailer under one Unit of Measure, but sold under 2313 another Unit of Measure. 2314 2315 Example: A Spool of wire ordered by the spool and sold by lineal foot; 2316 Lumber ordered by board footage and sold by piece. 2317 2318 Business Rules: EAN.UCC standards reference the UN/CEFACT 2319 Recommendation 20 list for the possible Unit of Measure. 2320 orderingUnitOfMeasure is a string and is optional. 2321 2322

2323 Class Name: Ordering And Selling Unit Of Measure 2324 2325 Item Name: sellingUnitOfMeasure 2326 2327

Core/Extension: E 2328 Global Local Status: G 2329 M/O/D: O 2330 Multiple Values Allowed: N 2331 Neutral/Relationship Dependant: T.P.Neutral 2332 Product Hierarchy Reference Level: All 2333 Common value to all product hierarchy: Yes 2334 Type: String 2335 Size: 70 2336 2337 Definition: Describes the measurement used for selling unit of the Trade 2338 Item to the end consumer. A Trade Item may have only one Unit of 2339 Measure. 2340 2341 Example: Each, pair, case, roll, set box, by the foot, by the sheet. The 2342 Retailers require this if the Item is marked as a Consumer Unit. Only 2343 values from the enumerated list can be chosen from the UN/CEFACT. 2344

2345 Business Rules: 2346

Page 58: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 57 of 195

Class Name: OrganicTradeItemCharacteristics 2347 2348 Item Name: organicClaimAgency 2349 2350

Core/Extension: E 2351 Global Local Status: G/L 2352 M/O/D: O 2353 Multiple Values Allowed: Y 2354 Neutral/Relationship Dependant: T.P.Neutral 2355 Product Hierarchy Reference Level: Each 2356 Common value to all product hierarchy: No 2357 Type: AN 2358 Size: ..35 2359

2360 Definition: A governing body that creates and maintain standards related 2361 to organic products./Brules: only registered values may be used. See 2362 implementation section 4.8 for reference to code list. It's a repeatable 2363 field. 2364

2365 Examples: 2366

2367 Business Rules: 2368

2369 2370 ClassName: OrganicTradeItemCharacteristics 2371 2372 Item Name: organicTradeItemCode 2373 2374

Core/Extension: E 2375 Global Local Status: G/L 2376 M/O/D: O 2377 Multiple Values Allowed: N 2378 Neutral/Relationship Dependant: T.P.Neutral 2379 Product Hierarchy Reference Level: Each 2380 Common value to all product hierarchy: No 2381 Type: AN 2382 Size: ..35 2383

2384 Definition: Used to indicate the organic status of a trade item or of one or 2385 more of its components. 2386

2387 Examples: See code list 2388

2389 Business Rules: Approved values are : 2390

01 100% organic 2391 02 Organic 2392 03 Made with Organic Ingredients 2393 04 Some Organic Ingredients 2394 05 Not Organic 2395 06 Unknown 2396

Page 59: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 58 of 195

2397 2398

Class Name: PackagingMarking 2399 2400 Item Name: isBarcodeOnThePackage- this boolean question is answered by 2401 the population of Bar Code Type. It is thus not represented in the model and the 2402 schemas. 2403

2404 Core/Extension: E 2405 Global Local Status: G 2406 M/O/D: M 2407 Multiple Values Allowed: N 2408 Neutral/Relationship Dependant: T.P.Neutral 2409 Product Hierarchy Reference Level: All 2410 Common value to all product hierarchy: No 2411 Type: Boolean 2412 Size: Not Applicable 2413

2414 Definition: Indication if the trade item is physically bar-coded with the 2415 primary trade item identification number. This is a y/n (Boolean) where Y 2416 equals trade item is bar-coded. 2417

2418 Examples: 2419

2420 Business Rules: Boolean Y/N; Y= bar-coded N= not bar-coded 2421 Technical Note: This Boolean question is answered by the application of 2422 class “Bar Code Type List”. If the Bar Code Type List class (telling which 2423 barcodes are on the package) exists, then there is a barcode on the 2424 package. The attribute is derived from the Bar Code Type List and is not 2425 in the model. 2426

2427 2428 Class Name: PackagingMarking 2429 2430 Item Name: isPackagingMarkedReturnable 2431 2432

Core/Extension: E 2433 Global Local Status: G 2434 M/O/D: M 2435 Multiple Values Allowed: N 2436 Neutral/Relationship Dependant: T.P.Neutral 2437 Product Hierarchy Reference Level: All 2438 Common value to all product hierarchy: No 2439 Type: Boolean 2440 Size: Not Applicable 2441

2442 Definition: trade item has returnable packaging. This is a yes/no 2443 (Boolean) where yes equals package can be returned. 2444

2445 Examples: 2446

Page 60: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 59 of 195

2447 Business Rules: Boolean Y/N; Y= marked returnable, N= not returnable. 2448 Attribute applies to returnable packaging with or without deposit. 2449

2450 2451 Class Name: PackagingMarking 2452 2453 Item Name: isPackagingMarkedWithIngredients 2454 2455

Core/Extension: E 2456 Global Local Status: L 2457 M/O/D: O 2458 Multiple Values Allowed: N 2459 Neutral/Relationship Dependant: T.P.Neutral 2460 Product Hierarchy Reference Level: Each 2461 Common value to all product hierarchy: No 2462 Type: Boolean 2463 Size: Not Applicable 2464

2465 Definition: trade item packaging contains information pertaining to its 2466 ingredients. trade item ingredients are required to be shown on the trade 2467 item (normally at base trade item level). This is a yes/no (Boolean) where 2468 yes equals marked with ingredients. 2469

2470 Examples: 2471

2472 Business Rules: Boolean Y/N where Y=marked with ingredients , N=not 2473 marked with ingredients. trade item ingredients are required to be shown 2474 on the trade item (normally consumer unit level) Sector specific and 2475 geographical extension. List of ingredients can be legally required in 2476 some countries for limited trade item sectors. 2477

2478 2479 Class Name: PackagingMarking 2480 2481 Item Name: OfferOnPack 2482 2483

Core/Extension: E 2484 Global Local Status: L 2485 M/O/D: O 2486 Multiple Values Allowed: N 2487 Neutral/Relationship Dependant: T.P.Neutral 2488 Product Hierarchy Reference Level: Each 2489 Common value to all product hierarchy: No 2490 Type: String 2491 Size: 70 2492

2493 Definition: Contains details of any on pack product offer (consumer or 2494 traded). 2495

2496

Page 61: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 60 of 195

Examples: Extra 20 percent free, free gift. 2497 2498

Business Rules: If the physical dimensions of the product change as a 2499 result of the promotion, then a new GTIN must be allocated. If only a 2500 token is added to the product, then no need to change GTIN. 2501

2502 2503 Class Name: PackagingMarking 2504 2505 Item Name: packageMarksDietAllergen 2506 2507

Core/Extension: E 2508 Global Local Status: L 2509 M/O/D: O 2510 Multiple Values Allowed: Y 2511 Neutral/Relationship Dependant: T.P.Neutral 2512 Product Hierarchy Reference Level: Each 2513 Common value to all product hierarchy: No 2514 Type: Enumerated List 2515 Size: Not Applicable 2516

2517 Definition: Indication of which dietary or allergen marks that are on the 2518 package. 2519

2520 Business Rules: 2521

2522 2523

Class Name: PackagingMarking 2524 2525 Item Name:packageMarksEnvironment: 2526 2527

Core/Extension: E 2528 Global Local Status: L 2529 M/O/D: O 2530 Multiple Values Allowed: Y 2531 Neutral/Relationship Dependant: T.P.Neutral 2532 Product Hierarchy Reference Level: Each 2533 Common value to all product hierarchy: No 2534 Type: Enumerated List 2535 Size: Not Applicable 2536

2537 Definition: Indication of which environmental marks (e.g. recycling 2538 schemes) that are on trade item package. This attribute is an enumerated 2539 list and is optional. 2540 2541 Business Rules: 2542 2543

2544 2545 2546

Page 62: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 61 of 195

Class Name: PackagingMarking 2547 2548 Item Name: packageMarksEthical: 2549 2550

Core/Extension: E 2551 Global Local Status: L 2552 M/O/D: O 2553 Multiple Values Allowed: Y 2554 Neutral/Relationship Dependant: T.P.Neutral 2555 Product Hierarchy Reference Level: Each 2556 Common value to all product hierarchy: No 2557 Type: Enumerated List 2558 Size: Not Applicable 2559

2560 Definition: Indication of which ethical trading marks that are on the 2561 package. 2562 2563 Business Rules: 2564

2565 2566

Class Name: PackagingMarking 2567 2568 Item Name: packageMarksFreeFrom 2569 2570

Core/Extension: E 2571 Global Local Status: L 2572 M/O/D: O 2573 Multiple Values Allowed: Y 2574 Neutral/Relationship Dependant: T.P.Neutral 2575 Product Hierarchy Reference Level: Each 2576 Common value to all product hierarchy: No 2577 Type: Enumerated List 2578 Size: Not Applicable 2579

2580 Definition: Indication of which free-from marks that are on the package. 2581 This attribute is and enumerated list and is optional. 2582

2583 2584

Class Name: PackagingMarking 2585 2586 Item Name: packagingMarkedExpirationDateType 2587 2588

Core/Extension: E 2589 Global Local Status: L 2590 M/O/D: O 2591 Multiple Values Allowed: Y 2592 Neutral/Relationship Dependant: T.P.Neutral 2593 Product Hierarchy Reference Level: Each 2594 Common value to all product hierarchy: No 2595 Type: Enumerated List 2596

Page 63: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 62 of 195

Size: Not Applicable 2597 2598

Definition: Indicates the type of expiration date marked on the 2599 packaging. 2600 2601 Business Rules: 2602

2603 2604 Class Name: PackagingMarking 2605 2606 Item Name: packagingMarkedRecyclableScheme 2607 2608

Core/Extension: E 2609 Global Local Status: L 2610 M/O/D: O 2611 Multiple Values Allowed: N 2612 Neutral/Relationship Dependant: T.P.Neutral 2613 Product Hierarchy Reference Level: Each 2614 Common value to all product hierarchy: No 2615 Type: AN 2616 Size: 70 2617

2618 Definition: The package of this GTIN is marked to indicate under which 2619 scheme it is recyclable. Applies to recyclable packaging with or without 2620 deposit. 2621 2622 Examples: Aluminum can be marked as recyclable. 2623

2624 Business Rules: 2625

2626 2627

Page 64: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 63 of 195

Class Name: PackagingMaterial 2628 2629 Item Name: depositValueEffectiveDate 2630 2631

Core/Extension: E 2632 Global Local Status: L 2633 M/O/D: O 2634 Multiple Values Allowed: N 2635 Neutral/Relationship Dependant: T.P.Neutral 2636 Product Hierarchy Reference Level: Each 2637 Common value to all product hierarchy: No 2638 Type: Date 2639 Size: CCYYMMDD 2640

2641 Definition: First date that the deposit value is valid for the deposit code. 2642 2643 Examples: 2644

2645 Business Rules: 2646 2647

2648 Class Name: PackagingMaterial 2649 2650 Item Name: depositValueEndDate 2651 2652

Core/Extension: E 2653 Global Local Status: L 2654 M/O/D: O 2655 Multiple Values Allowed: N 2656 Neutral/Relationship Dependant: T.P.Neutral 2657 Product Hierarchy Reference Level: Each 2658 Common value to all product hierarchy: No 2659 Type: Date 2660 Size: CCYYMMDD 2661

2662 Definition: Last date that the deposit value in the currency is valid for the 2663 deposit code. 2664

2665 Examples: 2666

2667 Business Rules: 2668

2669

Page 65: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 64 of 195

2670 Class Name: PackagingMaterial 2671 2672 Item Name: packagingMaterialCode 2673 2674

Core/Extension: E 2675 Global Local Status: G/L 2676 M/O/D: O 2677 Multiple Values Allowed: Y 2678 Neutral/Relationship Dependant: T.P.Neutral 2679 Product Hierarchy Reference Level: All 2680 Common value to all product hierarchy: No 2681 Type: AN 2682 Size: ..3 2683

2684 Definition: Code source needs to be defined. Currently a European 2685 Union table of code lists exists for this requirement. The code list 2686 required to identify the packaging material of the trade item. 2687

2688 Examples: "GL" (glass) "AL" (Aluminum) 2689

2690 Business Rules: Can be repeated for multi-material packaging and 2691 linked to packaging weight. 2692

2693 2694 Class Name: PackagingMaterial 2695 2696 Item Name: packagingMaterialCodeListMaintenanceAgency 2697 2698

Core/Extension: E 2699 Global Local Status: G/L 2700 M/O/D: D 2701 Multiple Values Allowed: Y 2702 Neutral/Relationship Dependant: T.P.Neutral 2703 Product Hierarchy Reference Level: All 2704 Common value to all product hierarchy: No 2705 Type: AN 2706 Size: ..35 2707

2708 Definition: Agency needs to be defined. The agency or agencies 2709 controlling the packaging code lists of each country. Mandatory if 2710 packaging material code is populated. 2711

2712 Examples: 2713

2714 Business Rules: Dependent on field packagingMaterialCode 2715

2716

Page 66: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 65 of 195

2717 Class Name: PackagingMaterial 2718 2719 Item Name: packagingMaterialCompositionQuantity 2720 2721

Core/Extension: E 2722 Global Local Status: G/L 2723 M/O/D: D 2724 Multiple Values Allowed :Y 2725 Neutral/Relationship Dependant: T.P.Neutral 2726 Product Hierarchy Reference Level: All 2727 Common value to all product hierarchy: No 2728 Type: Multi-Measurement 2729 Size: Decimal 15, String 3 for Unit Of Measure 2730

2731 Definition: The quantity of the packaging of the trade item. Can be 2732 weight, volume or surface, can vary by country. 2733

2734 Examples: "15 grm", Value, amount, eaches, etc. 2735

2736 Business Rules: Can be repeated for multi-material packaging and must 2737 be associated with a valid ISO language code from the attached table. 2738 Has to be associated with valid UOM. See Section 4.6 of the 2739 Implementation Considerations and Concerns for more details. 2740 2741 2742

Class Name: PackagingMaterial 2743 2744 Item Name: packagingMaterialDescription 2745 2746

Core/Extension: E 2747 Global Local Status: G/L 2748 M/O/D: D 2749 Multiple Values Allowed: Y 2750 Neutral/Relationship Dependant: T.P.Neutral 2751 Product Hierarchy Reference Level: All 2752 Common value to all product hierarchy: No 2753 Type: Multi Short Description 2754 Size: 35 2755

2756 Definition: The system generated text description equivalent of the 2757 packaging material code. 2758

2759 Examples: "Glass" "Aluminum" 2760

2761 Business Rules: Can be repeated for multi-material packaging and 2762 linked to packaging weight. As a description text field, this data element is 2763 repeatable for each language used and must be associated with a valid 2764 ISO language code from the attached table. Dependent on the field 2765

Page 67: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 66 of 195

packagingMaterialCode See Section 4.4 of the Implementation 2766 Considerations and Concerns for more detail. 2767

2768 2769 Class Name: PackagingMaterial 2770 2771 Item Name: packagingTermsAndConditions 2772 2773

Core/Extension: E 2774 Global Local Status: G 2775 M/O/D: O 2776 Multiple Values Allowed: N 2777 Neutral/Relationship Dependant: T.P.Neutral 2778 Product Hierarchy Reference Level: All 2779 Common value to all product hierarchy: No 2780 Type: AN 2781 Size: 3 2782

2783 Definition: Indicates if the packaging given in the described packaging 2784 configuration is a rented, exchangeable, against deposit or one way/not 2785 reusable. 2786

2787 Examples: Codes to be defined. See Section 4.8 2788

2789 Business Rules: List of authorized values based on EANCOM 7073, 2790 X12 DE102 and X12 DE399. 2791

2792 2793 Class Name: PackagingMaterial 2794 2795 Item Name: returnablePackageDepositAmount 2796 2797

Core/Extension: E 2798 Global Local Status: G 2799 M/O/D: O 2800 Multiple Values Allowed: N 2801 Neutral/Relationship Dependant: T.P.Neutral 2802 Product Hierarchy Reference Level: All 2803 Common value to all product hierarchy: No 2804 Type: Float 2805 Size: Not Applicable 2806

2807 Definition: The monetary amount for the individual returnable package.. 2808

2809 Examples: 2810 2811 Business Rules: 2812

2813 2814 2815

Page 68: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 67 of 195

Class Name: PackagingMaterial 2816 2817 Item Name: returnablePackageDepositCode 2818 2819

Core/Extension: E 2820 Global Local Status: G 2821 M/O/D: O 2822 Multiple Values Allowed: N 2823 Neutral/Relationship Dependant: T.P.Neutral 2824 Product Hierarchy Reference Level: All 2825 Common value to all product hierarchy: No 2826 Type: AN 2827 Size: 14 2828

2829 Definition: In some markets the deposit information is specified by a 2830 GTIN giving the type of returnable package on which a deposit is 2831 charged. Each deposit code is associated with an amount specified 2832 elsewhere. 2833

2834 Examples: 2835 2836 Business Rules: 2837

2838 2839 Class Name: PackagingType 2840 2841 Item Name: packagingTypeCode 2842 2843

Core/Extension: E 2844 Global Local Status: G 2845 M/O/D: O 2846 Multiple Values Allowed: Y 2847 Neutral/Relationship Dependant: T.P.Neutral 2848 Product Hierarchy Reference Level: All 2849 Common value to all product hierarchy: No 2850 Type: Char 2851 Size: 3 2852

2853 Definition: The code identifying the type of package used as a container 2854 of the trade item. 2855

2856 Examples: Codes to be defined. See code list for possible values 2857 (packagingTypeDescription). 2858

2859 Business Rules: List of authorized code values based on UN-ECE 21 2860 Recommendations. Code list can be found in Implementatio Section 4.8 2861 Can be repeated. 2862

2863 2864 Class Name: PackagingType 2865

Page 69: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 68 of 195

2866 Item Name: packagingTypeDescription 2867 2868

Core/Extension: E 2869 Global Local Status: G 2870 M/O/D: O 2871 Multiple Values Allowed: Y 2872 Neutral/Relationship Dependant: T.P.Neutral 2873 Product Hierarchy Reference Level: All 2874 Common value to all product hierarchy: No 2875 Type: AN 2876 Size: ..35 2877

2878 Definition: System generated text description of the type of packaging 2879 used for the trade item. For example, box or carton. 2880

2881 Examples: "Box", "Bottle" 2882

2883 Business Rules: List of authorized text description values based on UN-2884 ECE 21 Recommendations - EANCOM 7065. Can be repeated. System 2885 generated field. 2886

2887 2888

Class Name: PegMeasurements (child class of TradeItemMeasurements) 2889 2890

Item Name: pegHoleNumber 2891 2892

Core/Extension: E 2893 Global Local Status: G 2894 M/O/D: D 2895 Multiple Values Allowed: N 2896 Neutral/Relationship Dependant: T.P.Neutral 2897 Product Hierarchy Reference Level: Each 2898 Common value to all product hierarchy: No 2899 Type: N 2900 Size: Unbounded 2901

2902 Definition: Used to indicate the peg hole numbers when more than one 2903 hole is present in the product or packaging. Peg holes should be 2904 numbered from the upper left corner of the front of the package to the 2905 bottom right corner. The peg holes should be identified from left to right, 2906 top to bottom with left to right having precedence. The number of peg 2907 holes and their measurements must be determined following the 2908 orientation of the product. Product orientation is based upon the General 2909 EAN.UCC Specification. Required if the trade item is displayed on a peg 2910 board. 2911

2912 Examples: 1 2913

2914

Page 70: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 69 of 195

Business Rules: Required if the item has a peg hole. Multiple peg holes 2915 are allowed per product. 2916 2917

2918 Class Name: PegMeasurements (child class of TradeItemMeasurements) 2919 2920 Item Name: pegHorizontal 2921 2922

Core/Extension: E 2923 Global Local Status: G 2924 M/O/D: O 2925 Multiple Values Allowed: N 2926 Neutral/Relationship Dependant: T.P.Neutral 2927 Product Hierarchy Reference Level: Each 2928 Common value to all product hierarchy: No 2929 Type: Multi-Measurement Value 2930 Size: Decimal 15, String 3 for Unit Of Measure 2931 2932

2933 Definition: Used to indicate the horizontal distance from the edge of the 2934 trade item to the center of the hole into which the peg is inserted when 2935 the trade item is displayed on a pegboard. 2936

2937 Examples: "2 INH" 2938

2939 Business Rules: Required if the trade item is displayed on a peg board. 2940 Has to be associated with a valid UOM. 2941

2942 2943 Class Name: PegMeasurements (child class of TradeItemMeasurements) 2944 2945 Item Name: pegVertical 2946 2947

Core/Extension: E 2948 Global Local Status: G 2949 M/O/D: O 2950 Multiple Values Allowed: N 2951 Neutral/Relationship Dependant: T.P.Neutral 2952 Product Hierarchy Reference Level: Each 2953 Common value to all product hierarchy: No 2954 Type: Multi-Measurement Value 2955 Size: Decimal 15, String 3 for Unit Of Measure 2956 2957 Definition: Used to indicate the vertical distance from the edge of the 2958 trade item to the center of the hole into which the peg is inserted when 2959 the trade item is displayed on a pegboard. The hole into which the peg is 2960 inserted when the trade item is displayed on a pegboard. The 2961 measurement is always taken from the top edge of the trade item to the 2962 hole. 2963

2964

Page 71: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 70 of 195

Examples: "2 INH" 2965 2966

Business Rules: Required if the trade item is displayed on a peg board. 2967 Has to be associated with a valid UOM.. 2968

2969 2970

Class Name: PriceOnTradeItem 2971 2972 Item Name: priceOnPackIndicator- this boolean question is answered by 2973 populating retailPriceOnTradeItem. 2974

2975 Core/Extension: E 2976 Global Local Status: G 2977 M/O/D: M 2978 Multiple Values Allowed: N 2979 Neutral/Relationship Dependant: T.P.Neutral 2980 Product Hierarchy Reference Level: Each 2981 Common value to all product hierarchy: No 2982 Type: Boolean 2983 Size: Not Applicable 2984

2985 Definition: Indication of whether there is a retail price physically on or 2986 attached to the trade item packaging of the trade item by the 2987 manufacturer or information provider. This is a y/n (Boolean) where y 2988 equals pricing on the trade item. 2989

2990 Examples: - 2991

2992 Business Rules: Boolean Y/N where Y = there is a retail price on the 2993 trade item; N = not pre-priced 2994

2995 2996 Class Name: PriceOnTradeItem 2997 2998 Item Name: retailPriceOnTradeItem 2999 3000

Core/Extension: E 3001 Global Local Status: G 3002 M/O/D: D 3003 Multiple Values Allowed: N 3004 Neutral/Relationship Dependant: T.P.Neutral 3005 Product Hierarchy Reference Level: Each 3006 Common value to all product hierarchy: No 3007 Type: Amount 3008 Size: 17.4 3009

3010 Definition: The retail price as marked on the trade item package. This 3011 field is dependent on a value of "yes" for field priceOnPackIndicator. 3012

3013 Examples: "USD 1.00", "EUR 36", “USD 17.45” 3014

Page 72: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 71 of 195

3015 Business Rules: As monetary amount field, this data element must be 3016 associated with a valid unit of measure. See implementation notes for 3017 complete table. GTIN allocation rules state that price is not a relevant 3018 criteria for changing a GTIN except when the price is printed as a part of 3019 the trade item’s packaging. 3020 Becomes mandatory when priceOnPackIndicator = "Y". In this case, the 3021 priceOnPack becomes Global (can not vary per Target Market). 3022 See Section 4.5 of Implementation Considerations and Concerns for 3023 more details. 3024

3025 3026 Class Name: PrivateInformation 3027 3028 Item Name: isTradeItemInformationPrivate this boolean question is answered 3029 by populating partyReceivingPrivateData. 3030 3031 3032

Core/Extension: E 3033 Global Local Status: G 3034 M/O/D: M 3035 Multiple Values Allowed: N 3036 Neutral/Relationship Dependant: T.P.Neutral 3037 Product Hierarchy Reference Level: All 3038 Common value to all product hierarchy: Yes 3039 Type: Boolean 3040 Size: Not Applicable 3041

3042 Definition: Indicator to qualify whether master data is publicly available to 3043 any inquirer or is restricted to specific private user. This is a y/n (Boolean) 3044 where y equals non-public. If yes, then must have associated PARTY ID 3045 for whom the information is intended. 3046

3047 Examples: Consumer unit A is public. Display configuration B, which 3048 contains public consumer unit A, is marked non-public, as it was built for 3049 retailer C. Pallet GTIN D, which is made up of Display B, is also marked 3050 non-public, only available to retailer C. 3051

3052 Business Rules: Trade item hierarchy level impact - if GTIN is marked 3053 non-public, all higher trade item hierarchy levels are non-public. Lower 3054 trade item hierarchy levels can still be public. This Boolean question is 3055 answered by application of class Private Information. 3056

Page 73: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 72 of 195

3057 3058 Class Name: PrivateInformation 3059 3060 Item Name: partyReceivingPrivateData – represented by relationship to Party 3061 Identification. 3062 3063

Core/Extension: E 3064 Global Local Status: G 3065 M/O/D: D 3066 Multiple Values Allowed: Y 3067 Neutral/Relationship Dependant:T.P.Dependent 3068 Product Hierarchy Reference Level: All 3069 Common value to all product hierarchy: Yes* 3070 Type: PartyIdentification 3071 Size: Not Applicable 3072

3073 Definition: Unique location number identifying the party who is allowed 3074 access to the information by the data owner. 3075

3076 Examples: Refer to the following websites for specific directions on how 3077 to construct global location numbers - www.uc-council.org or www.ean-3078 int.org 3079

3080 Business Rules: There can be multiple instances of 3081 partyReceivingPrivateData. This is handled through the zero to many 3082 relationship between PrivateInformation and 3083 TradingPartnerNeutralTradeItemInformation. 3084 3085 While the class ManufacturerOfTradeItem is optional, the party 3086 identification for the brand owner is required when a manufacturer is 3087 present. 3088 3089

3090 Class Name: Season 3091 3092 Item Name: seasonalAvailabilityEndDate 3093 3094

Core/Extension: E 3095 Global Local Status: L 3096 M/O/D: O 3097 Multiple Values Allowed: N 3098 Neutral/Relationship Dependant: T.P.Neutral 3099 Product Hierarchy Reference Level: Each 3100 Common value to all product hierarchy: No 3101 Type: Date 3102 Size: CCYYMMDD 3103

3104 Definition: This element indicates the end date of the trade item's 3105 seasonal availability.The seasonal availability can be different from the 3106

Page 74: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 73 of 195

ordering time and especially from the dispatching time. The availability is 3107 more like an intention of the supplier as to how long he wants to offer the 3108 product. The dispatching time is more useful for the DC and the outlet 3109 warehousing. 3110 3111 Examples: 3112 3113 Business Rules: 3114

3115 Class Name: Season 3116 3117 Item Name: seasonalAvailabilityStartDate 3118 3119

Core/Extension: E 3120 Global Local Status: L 3121 M/O/D: O 3122 Multiple Values Allowed: N 3123 Neutral/Relationship Dependant: T.P.Neutral 3124 Product Hierarchy Reference Level: Each 3125 Common value to all product hierarchy: No 3126 Type: Date 3127 Size: CCYYMMDD 3128

3129 Definition: This element indicates the start date of the trade item's 3130 seasonal availability. Reference related attribute in Item document. 3131 3132 European Requirement. The seasonal availability can be different from 3133 the ordering time and especially from the dispatching time. The 3134 availability is more like an intention of the supplier as to how long he 3135 wants to offer the product. The dispatching time is more useful for the DC 3136 and the outlet warehousing. 3137 3138 Examples: 3139 3140 Business Rules: 3141 3142

3143 Class Name: Season 3144 3145 Item Name: seasonCalendarYear: 3146 3147

Core/Extension: E 3148 Global Local Status: L 3149 M/O/D: O 3150 Multiple Values Allowed: Y 3151 Neutral/Relationship Dependant: T.P.Neutral 3152 Product Hierarchy Reference Level: Each 3153 Common value to all product hierarchy: No 3154 Type: Year 3155 Size: CCYY 3156

Page 75: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 74 of 195

3157 Definition: This element indicates the calendar year in which the trade 3158 item is seasonally available.This item is seasonally available in the year 3159 “2002". European Requirement. This element applies to cases where the 3160 supplier has items in many different seasons or if multiple calendar years 3161 were involved. This attribute might be considered as an implementation 3162 attribute that could be done in different manners in the GDSN and in the 3163 one-to-one environment. Can be used for merchandising. 3164

3165 Examples: 3166 3167 Business Rules: 3168

3169 3170 Class Name: Season 3171 3172 Item Name: seasonParameter: 3173 3174

Core/Extension: E 3175 Global Local Status: L 3176 M/O/D: O 3177 Multiple Values Allowed: Y 3178 Neutral/Relationship Dependant: T.P.Neutral 3179 Product Hierarchy Reference Level: Each 3180 Common value to all product hierarchy: No 3181 Type: Enumerated List 3182 Size: Not Applicable 3183

3184 Definition: Indication of the season, in which the trade item is available, 3185 i.e. assignment to one of the following collection periods: spring/summer, 3186 autumn/ winter or all year around. It is repeatable if more than one 3187 season is indicated: Spring, Summer, Autumn, Winter, and All year 3188 (available throughout the year). The seasonal parameter is more an 3189 information for the search of data. 3190

3191 Examples: 3192 3193 Business Rules: 3194

3195 Class Name: Season 3196 3197 Item Name: seasonName: 3198

3199 Core/Extension: E 3200 Global Local Status: L 3201 M/O/D: O 3202 Multiple Values Allowed: Y 3203 Neutral/Relationship Dependant: T.P.Neutral 3204 Product Hierarchy Reference Level: Each 3205 Common value to all product hierarchy: No 3206

Page 76: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 75 of 195

Type: Description 3207 Size: 70 3208

3209 Definition: This element defines the season applicable to the item. 3210 3211 Example: Holiday, back to school, Summer, Winter, etc. Special 3212 advertising actions, Winter end-of-season sales (WSV) or summer end-3213 of-season sales (SSV). 3214 3215 Business Rules: There can be a grouping of GTINs by season. Not 3216 covered by collection as a collection can have multiple seasons or vice 3217 versa, a season can have multiple collections. 3218

3219 Examples: 3220 3221 Business Rules: 3222

3223 3224 Class Name: SecurityTagInformation 3225 3226 Item Name: securityTagType: 3227 3228

Core/Extension: E 3229 Global Local Status: L 3230 M/O/D: O 3231 Multiple Values Allowed: N 3232 Neutral/Relationship Dependant: T.P.Neutral 3233 Product Hierarchy Reference Level: Each 3234 Common value to all product hierarchy: No 3235 Type: Enumerated List 3236 Size: Not Applicable 3237

3238 Definition: This is a code to indicate the type of EAS tag located on the 3239 Trade Item. 3240 3241 Examples: Values include Acousto-Magnetic, Electro-Magnetic, Ink or 3242 dye, Microwave, Radio Frequency. 3243 3244 Business Rules: Used on Consumer Units only. 3245 3246

3247 Class Name: SecurityTagInformation 3248 3249 Item Name: securityTagLocation: 3250 3251

Core/Extension: E 3252 Global Local Status: L 3253 M/O/D: O 3254 Multiple Values Allowed: N 3255 Neutral/Relationship Dependant: T.P.Neutral 3256

Page 77: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 76 of 195

Product Hierarchy Reference Level: Each 3257 Common value to all product hierarchy: No 3258 Type: Enumerated List 3259 Size: Not Applicable 3260

3261 Definition: This is a code to indicate where the EAS tag is located on the 3262 Trade Item. 3263 3264 Example: Values include On outside of Trade Item, Concealed inside 3265 Trade Item, Integrated Inside Trade Item. 3266 3267 Business Rules: Used on Consumer Units only. 3268

3269 3270 Class Name: TargetConsumer 3271 3272 Item Name: targetConsumerAge: 3273 3274

Core/Extension: E 3275 Global Local Status: L 3276 M/O/D: O 3277 Multiple Values Allowed: N 3278 Neutral/Relationship Dependant: T.P.Neutral 3279 Product Hierarchy Reference Level: Each 3280 Common value to all product hierarchy: No 3281 Type: Description 3282 Size: 70 3283

3284 Definition: Identifies the target consumer age range for which a trade 3285 item has been designed. 3286 3287 Example: 0-6 months, 2-4 years, and juniors. The field format allows 3288 including a number (6), a number range (0-6 months, 2-4 years) or a 3289 category such as infants, teens, etc. target 3290 3291 Business Rules: 3292

3293 3294 Class Name: TargetConsumer 3295 3296 Item Name: targetConsumerGender: 3297 3298

Core/Extension: E 3299 Global Local Status: L 3300 M/O/D: O 3301 Multiple Values Allowed: N 3302 Neutral/Relationship Dependant: T.P.Neutral 3303 Product Hierarchy Reference Level: Each 3304 Common value to all product hierarchy: No 3305 Type: Enumerated List 3306

Page 78: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 77 of 195

Size: Not Applicable 3307 3308

Definition: Identifies the target consumer gender for which a product has 3309 been designed. 3310 3311 Example: male, female, unisex (suitable to both genders). 3312 3313 Business Rules: 3314 3315 3316

Class Name: TradeItemColorDescription 3317 3318 Item Name: colorCodeListAgency 3319 3320

Core/Extension: E 3321 Global Local Status: G 3322 M/O/D: D 3323 Multiple Values Allowed: Y 3324 Neutral/Relationship Dependant: T.P.Neutral 3325 Product Hierarchy Reference Level: Each 3326 Common value to all product hierarchy: No 3327 Type: AN 3328 Size: ..3 3329

3330 Definition: The parties controlling the color code lists. Dependent on 3331 color code value. 3332

3333 Examples: "PMS", "RAL", "TGA", "91" 3334

3335 Business Rules: If color code is indicated, colorCodeListAgency is 3336 requires. Sector specific extension. 3337

3338 3339 Class Name: TradeItemColorDescription 3340 3341 Item Name: colorCodeValue 3342 3343

Core/Extension: E 3344 Global Local Status: G 3345 M/O/D: O 3346 Multiple Values Allowed: Y 3347 Neutral/Relationship Dependant: T.P.Neutral 3348 Product Hierarchy Reference Level: Each 3349 Common value to all product hierarchy: No 3350 Type: AN 3351 Size: .. 20 3352

3353 Definition: The code list required to identify the color of the trade item. 3354 No ISO standards exist. Each industry needs to determine which code 3355 agency is will use. 3356

Page 79: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 78 of 195

3357 Examples: 3358

3359 Business Rules: If color code is indicated, colorCodeListAgency is 3360 required. EANCOM code list is to be used. This is used by certain 3361 industries which maintain specific color code lists. 3362

3363 3364 Class Name: TradeItemColorDescription 3365 3366 Item Name: colorDescription 3367 3368

Core/Extension: E 3369 Global Local Status: G 3370 M/O/D: O 3371 Multiple Values Allowed: Y 3372 Neutral/Relationship Dependant: T.P.Neutral 3373 Product Hierarchy Reference Level: Each 3374 Common value to all product hierarchy: No 3375 Type: Multi Description 3376 Size: ..70 3377

3378 Definition: Free text description of the color of the trade item. 3379

3380 Examples: "Dark burgundy" 3381

3382 Business Rules: Free from text. As description text field. This data 3383 element is repeatable for each language used and must be associated 3384 with a valid ISO language code from the attached table. 3385 3386

3387 Class Name: TradeItemCoupon 3388 3389 Item Name: couponFamilyCode 3390 3391

Core/Extension: E 3392 Global Local Status: L 3393 M/O/D: O 3394 Multiple Values Allowed: N 3395 Neutral/Relationship Dependant: T.P.Neutral 3396 Product Hierarchy Reference Level: Each 3397 Common value to all product hierarchy: No 3398 Type: AN 3399 Size: 3 3400

3401 Definition: A code assigned by the vendor to a single trade item or to 3402 families of consumer trade items that can be used by in store scanners in 3403 conjunction with a U.P.C. coupon value code for coupon value discount 3404 when the proper trade item has been purchased. 3405

3406

Page 80: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 79 of 195

Examples: 3407 3408

Business Rules: It only applies to the consumer unit. Note this is treated 3409 in the XML as a mandatory attribute in an optional class. 3410

3411 3412 Class Name: TradeItemDateInformation 3413 3414 Item Name: canceledDate 3415 3416

Core/Extension: E 3417 Global Local Status: G 3418 M/O/D: O 3419 Multiple Values Allowed: N 3420 Neutral/Relationship Dependant: T.P.Neutral 3421 Product Hierarchy Reference Level: All 3422 Common value to all product hierarchy: No 3423 Type: Date 3424 Size: CCYY-MM-DD 3425

3426 Definition: Communicates cancelation of the launch of a trade item that 3427 was never and will never be manufactured, but may have been presented 3428 to buyers. Allows the reuse of the GTIN 12 months after cancellation. 3429

3430 Examples: “2002-11-20” 3431 3432 Business Rules: Use ISO 8601 date format CCYY-MM-DD 3433 3434

3435 Class Name: TradeItemDateInformation 3436 3437 Item Name: consumerAvailabilityDateTime 3438 3439

Core/Extension: E 3440 Global Local Status: G/L 3441 M/O/D: O 3442 Multiple Values Allowed: N 3443 Neutral/Relationship Dependant: T.P.Neutral 3444 Product Hierarchy Reference Level: Each 3445 Common value to all product hierarchy: No 3446 Type: DateTime 3447 Size: CCYY-MM-DDTHH:MM:SS 3448

3449 Definition: The first date/time that the buyer is allowed to sell the trade 3450 item to consumers. Usually related to a specific geography. ISO 8601 3451 date format CCYY-MM-DDTHH:MM:SS. 3452

3453 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3454

3455

Page 81: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 80 of 195

Business Rules: Time is expressed in the time zone of the target 3456 market where the trade item is intended for resale to consumers. ISO 3457 8601 date format CCYY-MM-DDTHH:MM:SS. 3458

3459 3460 Class Name: TradeItemDateInformation 3461 3462 Item Name: discontinuedDate 3463 3464

Core/Extension: E 3465 Global Local Status: G/L 3466 M/O/D: O 3467 Multiple Values Allowed: N 3468 Neutral/Relationship Dependant: T.P Neutral 3469 Product Hierarchy Reference Level: All 3470 Common value to all product hierarchy: No 3471 Type: Date 3472 Size: CCYY-MM-DD 3473

3474 Definition: Communicate the date on which the trade item is no longer to 3475 be manufactured. Allows the reuse of the GTIN after 48 months with the 3476 explicit exception of Apparel, being 30 months and the implicit exception 3477 for specialty products (e.g., steel beams). 3478

3479 Examples: “2002-02-05” 3480

3481 Business Rules: ISO 8601 date format CCYY-MM-DD 3482

3483 3484 Class Name: TradeItemDateInformation 3485 3486 Item Name: effectiveDate 3487 3488

Core/Extension: E 3489 Global Local Status: G/L 3490 M/O/D: M 3491 Multiple Values Allowed: N 3492 Neutral/Relationship Dependant: T.P.Neutral 3493 Product Hierarchy Reference Level: All 3494 Common value to all product hierarchy: No 3495 Type: Date 3496 Size: CCYY-MM-DD 3497

3498 Definition: The date on which the information contents of the master data 3499 version are valid. Valid = correct or true. This effective date can be used 3500 for initial trade item offering, or to mark a change in the information 3501 related to an existing trade item. This date would mark when these 3502 changes take effect. 3503

3504 Examples: "2002-02-05" 3505

Page 82: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 81 of 195

3506 Business Rules: This date will be used for version management. The 3507 effective date can be different from publication date. If a new user begins 3508 to synchronize data on this GTIN after the original effective date, the 3509 effective date = the publication date for the new user. Time zone of the 3510 information provider may be noted in future drafts of the GDD. ISO 8601 3511 date format CCYY-MM-DD 3512

3513 3514 Class Name: TradeItemDateInformation 3515 3516 Item Name: endAvailabilityDateTime 3517 3518

Core/Extension: E 3519 Global Local Status: G/L 3520 M/O/D: O 3521 Multiple Values Allowed: N 3522 Neutral/Relationship Dependant: N/T.P.Dependent 3523 Product Hierarchy Reference Level: All 3524 Common value to all product hierarchy: No 3525 Type: DateTime 3526 Size: CCYY-MM-DDTHH:MM:SS. 3527

3528 Definition: The date from which the trade item is no longer available from 3529 the information provider, including seasonal or temporary trade item and 3530 services. 3531

3532 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3533

3534 Business Rules: If the trade item is public only one date is valid per 3535 GTIN, GLN, TM combination. If Item is private there can be more than 1 3536 value per TM. There is only one "end availability date" per GTIN/GLN/TM 3537 combination at any given time. In the case of seasonal trade items, only 3538 one start/end cycle can be in the data set version being synchronized. 3539 Therefore, a trade item cannot have multiple start/stop availability dates 3540 associated with it at any given time. Field is optional since most trade 3541 items are offered in an open ended environment. Is trading partner 3542 neutral for public trade items, trading partner dependent for private trade 3543 items. 3544

3545 Class Name: TradeItemDateInformation 3546 3547 Item Name: endDateMaximumBuyingQuantity: 3548 3549

Core/Extension: E 3550 Global Local Status: G/L 3551 M/O/D: O 3552 Multiple Values Allowed: N 3553 Neutral/Relationship Dependant: N/T.P.Dependent 3554 Product Hierarchy Reference Level: All 3555

Page 83: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 82 of 195

Common value to all product hierarchy: No 3556 Type: DateTime 3557 Size: CCYY-MM-DDTHH:MM:SS. 3558

3559 Definition: The end date for when the maximum buying quantity is no 3560 longer available to the trading partner. 3561

3562 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3563

3564 Business Rules: 3565

3566 3567 Class Name: TradeItemDateInformation 3568 3569 Item Name: endDateMinimumBuyingQuantity 3570 3571

Core/Extension: E 3572 Global Local Status: G/L 3573 M/O/D: O 3574 Multiple Values Allowed: N 3575 Neutral/Relationship Dependant: N/T.P.Dependent 3576 Product Hierarchy Reference Level: All 3577 Common value to all product hierarchy: No 3578 Type: DateTime 3579 Size: CCYY-MM-DDTHH:MM:SS. 3580

3581 Definition: The end date for when the minimum buying quantity is no 3582 longer available to the trading partner. 3583

3584 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3585

3586 Business Rules: 3587 3588

3589 Class Name: TradeItemDateInformation 3590 3591 Item Name: endDateTimeOfExclusivity: 3592 3593

Core/Extension: E 3594 Global Local Status: G/L 3595 M/O/D: O 3596 Multiple Values Allowed: N 3597 Neutral/Relationship Dependant: N/T.P.Dependent 3598 Product Hierarchy Reference Level: All 3599 Common value to all product hierarchy: No 3600 Type: DateTime 3601 Size: CCYY-MM-DDTHH:MM:SS. 3602

3603 Definition: The Date & Time at which a product is no longer exclusive to 3604 that trading partner. 3605

Page 84: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 83 of 195

Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3606 3607

Business Rules: 3608 3609 3610 Class Name: TradeItemDateInformation 3611 3612 Item Name: firstOrderDate: 3613 3614

Core/Extension: E 3615 Global Local Status: G/L 3616 M/O/D: O 3617 Multiple Values Allowed: N 3618 Neutral/Relationship Dependant: N/T.P.Dependent 3619 Product Hierarchy Reference Level: All 3620 Common value to all product hierarchy: No 3621 Type: Date 3622 Size: CCYY-MM-DD 3623

3624 Definition: Indicates the earliest date that an order can be placed for the 3625 trade item. 3626 3627 Examples: "2002-02-05" 3628

3629 Business Rules: 3630 3631

3632 Class Name: TradeItemDateInformation 3633 3634 Item Name: firstShipDate: 3635 3636

Core/Extension: E 3637 Global Local Status: G/L 3638 M/O/D: O 3639 Multiple Values Allowed: N 3640 Neutral/Relationship Dependant: N/T.P.Dependent 3641 Product Hierarchy Reference Level: All 3642 Common value to all product hierarchy: No 3643 Type: Date 3644 Size: CCYY-MM-DD 3645

3646 Definition: Indicates the earliest date that the trade item can be shipped. 3647 This is independent of any specific ship-from location. 3648

3649 Examples: "2002-02-05" 3650

3651 Business Rules: 3652 3653 3654

3655

Page 85: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 84 of 195

Class Name: TradeItemDateInformation 3656 3657 Item Name: lastOrderDate: 3658 3659

Core/Extension: E 3660 Global Local Status: G/L 3661 M/O/D: O 3662 Multiple Values Allowed: N 3663 Neutral/Relationship Dependant: N/T.P.Dependent 3664 Product Hierarchy Reference Level: All 3665 Common value to all product hierarchy: No 3666 Type: Date 3667 Size: CCYY-MM-DD 3668

3669 Definition: Indicates the latest date that an order can be placed for the 3670 trade item. 3671

3672 Examples: "2002-02-05" 3673

3674 Business Rules: 3675 3676

3677 Class Name: TradeItemDateInformation 3678 3679 Item Name: lastShipDate: 3680 3681

Core/Extension: E 3682 Global Local Status: G/L 3683 M/O/D: O 3684 Multiple Values Allowed: N 3685 Neutral/Relationship Dependant: N/T.P.Dependent 3686 Product Hierarchy Reference Level: All 3687 Common value to all product hierarchy: No 3688 Type: Date 3689 Size: CCYY-MM-DD 3690

3691 Definition: Indicates the latest date that the trade item can be shipped. 3692 This is independent of any specific ship-from location. 3693

3694 Examples: "2002-02-05" 3695

3696 Business Rules: 3697

3698 3699 Class Name: TradeItemDateInformation 3700 3701 Item Name: lastChangeDateTime 3702 3703

Core/Extension: E 3704 Global Local Status: G 3705

Page 86: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 85 of 195

M/O/D: M 3706 Multiple Values Allowed: N 3707 Neutral/Relationship Dependant: T.P.Neutral 3708 Product Hierarchy Reference Level: All 3709 Common value to all product hierarchy: No 3710 Type: DateTime 3711 Size: CCYY-MM-DDTHH:MM:SS. 3712

3713 Definition: A system generated value identifying the date and time a 3714 record was last updated. This field allows the data pool to control the 3715 trade item data version, and allows the information user to determine if 3716 trade item data should be downloaded. Date format CCYY-MM-3717 DDTHH:MM:SS. 3718

3719 Examples: "2002-02-05T17:00:00" = February 5th 2002 5:00:00pm 3720

3721 Business Rules: System generated by the home data pool. Date format 3722 defined in ISO 8601- CCYY-MM-DDTHH:MM:SS 3723

3724 3725 3726

Class Name: TradeItemDateInformation 3727 3728 Item Name: publicationDate 3729 3730

Core/Extension: E 3731 Global Local Status: G/L 3732 M/O/D: M 3733 Multiple Values Allowed: N 3734 Neutral/Relationship Dependant: N/T.P.Dependent 3735 Product Hierarchy Reference Level: All 3736 Common value to all product hierarchy: No 3737 Type: Date 3738 Size: CCYY-MM-DD 3739

3740 Definition: A date on which all static data associated with the trade item 3741 becomes available for viewing and synchronization. 3742

3743 Examples: "2002-02-05" February 5th 2002 3744

3745 Business Rules: There is only one release date per GTIN/TM/GLN 3746 combination. If a private trade item, the date can be trading partner 3747 dependent, if public, it is a trading partner neutral field. Date format is 3748 defined in ISO8601 –CCYY-MM-DD. 3749 3750

Page 87: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 86 of 195

3751 Class Name: TradeItemDateInformation 3752 3753 Item Name: startAvailabilityDateTime 3754 3755

Core/Extension: E 3756 Global Local Status: G/L 3757 M/O/D: M 3758 Multiple Values Allowed: N 3759 Neutral/Relationship Dependant: N/T.P.Dependent 3760 Product Hierarchy Reference Level: All 3761 Common value to all product hierarchy: No 3762 Type: DateTime 3763 Size: CCYY-MM-DDTHH:MM:SS 3764

3765 Definition: The date (CCYY-MM-DDTHH:MM:SS) from which the trade 3766 item becomes available from the supplier, including seasonal or 3767 temporary trade item and services. 3768

3769 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3770

3771 Business Rules: If the trade item is public only one date (CCYY-MM-3772 DDTHH:MM:SS) is valid per GTIN, GLN, TM combination. If Item is 3773 private there can be more than 1 value per TM. Needs to be earlier than 3774 "end availability date" This date indicates when the trade item can first be 3775 ordered by the buyer from the information provider. This date can be 3776 trading partner dependent if the trade item or service is defined as 3777 private. It is trading partner neutral if the trade item/service is public. It 3778 does not indicate when this trade item becomes available to the end 3779 consumer (see first sale date) There is only one start availability date per 3780 GTIN/GLN/TM combination. Date format is ISO8601 – CCYY-MM-3781 DDTHH:MM:SS. 3782 3783

3784 Class Name: TradeItemDateInformation 3785 3786 Item Name: startDateMaximumBuyingQuantity 3787 3788

Core/Extension: E 3789 Global Local Status: G/L 3790 M/O/D: O 3791 Multiple Values Allowed: N 3792 Neutral/Relationship Dependant: N/T.P.Dependent 3793 Product Hierarchy Reference Level: All 3794 Common value to all product hierarchy: No 3795 Type: DateTime 3796 Size: CCYY-MM-DDTHH:MM:SS 3797

3798 Definition: The start dateand time for when the maximum buying quantity 3799 is available to the trading partner. 3800

Page 88: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 87 of 195

Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3801 3802

Business Rules: 3803 3804 3805 Class Name: TradeItemDateInformation 3806 3807 Item Name: startDateMinimumBuyingQuantity 3808 3809

Core/Extension: E 3810 Global Local Status: G/L 3811 M/O/D: O 3812 Multiple Values Allowed: N 3813 Neutral/Relationship Dependant: N/T.P.Dependent 3814 Product Hierarchy Reference Level: All 3815 Common value to all product hierarchy: No 3816 Type: DateTime 3817 Size: CCYY-MM-DDTHH:MM:SS 3818

3819 Definition: The start date for when the minimum buying quantity is 3820 available to the trading partner. 3821 3822 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm 3823

3824 Business Rules: 3825 3826 3827

Class Name: TradeItemFinish 3828 3829 Item Name: tradeItemFinishDescription 3830 3831

Core/Extension: E 3832 Global Local Status: G 3833 M/O/D: O 3834 Multiple Values Allowed: N 3835 Neutral/Relationship Dependant: T.P.Neutral 3836 Product Hierarchy Reference Level: Each 3837 Common value to all product hierarchy: No 3838 Type: Description 3839 Size: 70 3840

3841 Definition: Attribute which defines the outer surface/appearance of the 3842 product. 3843 3844 Example: Antique brass, bright brass, oak or walnut finishBusiness 3845 3846 Business Rules: Until approved in the standards, use of “color” Attribute 3847 to define finish is acceptable. Would only need to be added on Consumer 3848 Unit Items. 3849

3850

Page 89: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 88 of 195

Class Name: TradeItemHandlingInformation 3851 3852 Item Name: handlingInstructionsCode 3853 3854

Core/Extension: E 3855 Global Local Status: G 3856 M/O/D: O 3857 Multiple Values Allowed: Y 3858 Neutral/Relationship Dependant: T.P.Neutral 3859 Product Hierarchy Reference Level: Each 3860 Common value to all product hierarchy: No 3861 Type: AN 3862 Size: 5 3863

3864 Definition: Defines the information and processes needed to safely handle the 3865 trade item. Handling instructions is composed of both text and a language code. 3866 The language for text is specified using the two digit ISO 639-1988 list, for 3867 example, English is EN and French is FR. 3868

3869 Examples: 3870 "DNF" – Do Not Freeze 3871 “FTD” – Frost danger 3872 “HS” – Heat sensitive 3873 “HWC” – Handle with care 3874

3875 Business Rules: Repeatable values are accepted. See Implementation 3876 Considerations and Concerns for more details. 3877

3878 Class Name: TradeItemHandlingInformation 3879 3880 Item Name: minimumTradeItemLifespanFromTimeOfArrival 3881 3882

Core/Extension: E 3883 Global Local Status: G/L 3884 M/O/D: O 3885 Multiple Values Allowed: N 3886 Neutral/Relationship Dependant: T.P Neutral & T.P.Dependent 3887 Product Hierarchy Reference Level: Each 3888 Common value to all product hierarchy: No 3889 Type: N 3890 Size: ..4 3891

3892 Definition: The period of days, guaranteed by the manufacturer, before the 3893 expiration date of the trade item, based on arrival to a mutually agreed to point 3894 in the buyers distribution system. Can be repeatable upon use of GLN. 3895

3896 Examples: "35" 3897

3898 Business Rules: This field is indicative of the normal Minimum Shelf Life. 3899 It is recognized that this figure may vary slightly depending upon locations 3900 of DC or Stores, therefore it is repeatable. This information is linked to the 3901 Target Market. Must be expressed in number of days. 3902

Page 90: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 89 of 195

3903 3904 Class Name: TradeItemHandlingInformation 3905 3906 Item Name: stackingFactor 3907 3908

Core/Extension: E 3909 Global Local Status: G 3910 M/O/D: O 3911 Multiple Values Allowed: No 3912 Neutral/Relationship Dependant: T.P.Neutral 3913 Product Hierarchy Reference Level: All 3914 Common value to all product hierarchy: No 3915 Type: N 3916 Size: ..6 3917

3918 Definition: A factor that determines the maximum stacking for the 3919 product. Indicates the number of levels the product may be stacked. 3920

3921 Examples: Factor of "2" = trade item is stackable 2 high 3922

3923 Business Rules: Factor will indicate how many levels the particular 3924 product may be stacked in. The counting of the levels will always 3925 commence at 1 not 0. 3926

3927 3928 Class Name: TradeItemHandlingInformation 3929 3930 Item Name: stackingWeightMaximum 3931 3932

Core/Extension: E 3933 Global Local Status: G 3934 M/O/D: O 3935 Multiple Values Allowed: N 3936 Neutral/Relationship Dependant: T.P.Neutral 3937 Product Hierarchy Reference Level: All 3938 Common value to all product hierarchy: No 3939 Type: Multi Measurement Value 3940 Size: Decimal 15, String 3 for Unit Of Measure 3941

3942 Definition: The maximum admissible weight that can be stacked on the 3943 trade item. This uses a measurement consisting of a unit of measure and 3944 a value. This will be used for transport or storage to allow user to know by 3945 weight how to stack different trade item one on top of the other. 3946

3947 Examples: "500 KGM” 3948

3949 Business Rules: Used in conjunction with unit of measure. 3950 3951

3952

Page 91: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 90 of 195

Class Name: TradeItemHandlingInformation 3953 3954 Item Name: minimumTradeItemLifespanFromTimeOfProduction: 3955 3956

Core/Extension: E 3957 Global Local Status: G/L 3958 M/O/D: O 3959 Multiple Values Allowed: N 3960 Neutral/Relationship Dependant: T.P Neutral & T.P.Dependent 3961 Product Hierarchy Reference Level: Each 3962 Common value to all product hierarchy: No 3963 Type: N 3964 Size: 4 3965

3966 Examples: The period of day, guaranteed by the manufacturer, before 3967 the expiration date of the product, based on the production. 3968

3969 Business Rules: 3970 3971

3972 Class Name: TradeItemHazardousInformation 3973 3974 Item Name: dangerousGoodsIndicator—This boolean question is answered by 3975 the application of the class and is thus not included in model or schema. 3976 3977

Core/Extension: E 3978 Global Local Status: G/L 3979 M/O/D: M 3980 Multiple Values Allowed: N 3981 Neutral/Relationship Dependant: T.P.Neutral 3982 Product Hierarchy Reference Level: All 3983 Common value to all product hierarchy: No 3984 Type: Boolean 3985 Size: Not Applicable 3986

3987 Definition: Indication, whether the trade item and/or at least one of its 3988 packaging components because of its properties - according to the 3989 respective national or international legislation for transport by road, rail, 3990 river, sea or air (e.g. the European dangerous goods agreements 3991 (ADR/RID) for transport by road and rail) - must be classified as 3992 dangerous good, and thus is subject to the respective regulations. 3993

3994 Examples: 3995

3996 Business Rules: Boolean Y/N 3997 Hazardous attributes relate to supply chain handling (e.g., transport, 3998 storage, handling). 3999 Technical Note: This Boolean question is answered by the application of 4000 class “TradeItemHazardousInformation”. 4001

4002

Page 92: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 91 of 195

4003 Class Name: TradeItemHazardousInformation 4004 4005 Item Name: dangerousGoodsRegulationCode 4006 4007

Core/Extension: E 4008 Global Local Status: G 4009 M/O/D: D 4010 Multiple Values Allowed: Y 4011 Neutral/Relationship Dependant: T.P.Neutral 4012 Product Hierarchy Reference Level: All 4013 Common value to all product hierarchy: No 4014 Type: AN 4015 Size: 3 4016

4017 Definition: Code indicating the classification system(s) of dangerous 4018 goods and/or the Agency(ies) responsible for it. 4019

4020 Examples: "ADR" European agreement on the international carriage of 4021 dangerous goods on roads. 4022

4023 Business Rules: Various systems (ADR, RID, US49, IATA, etc.) exist 4024 and are used for hazard classification and identification. 4025 4026 Repeatable field 4027 http://www.unece.org/trade/untdid/d99b/tred/tred8273.htm 4028 4029 Hazardous attributes relate to supply chain handling (e.g., transport, 4030 storage, handling). 4031

4032 4033

Class Name: TradeItemHazardousInformation 4034 4035 Item Name: flashPointTemperature 4036 4037

Core/Extension: E 4038 Global Local Status: G 4039 M/O/D: D 4040 Multiple Values Allowed: Y 4041 Neutral/Relationship Dependant: T.P.Neutral 4042 Product Hierarchy Reference Level: Each 4043 Common value to all product hierarchy: No 4044 Type: Measurement 4045 Size: Decimal 15, String 3 for Unit Of Measure 4046

4047 Definition: The lowest temperature at which a substance gives off a 4048 sufficient vapor to support combustion. This uses a measurement 4049 consisting of a unit of measure and value. 4050

4051 Examples: - 4052

Page 93: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 92 of 195

4053 Business Rules: Information required when 4054 dangerousGoodsRegulationcode is populated. 4055 Expressed in Celsius (or Centigrade) or Fahrenheit 4056 Format defined by UN/EDIFACT 7106 4057 Has to be associated with valid UoM. Hazardous attributes relate to 4058 supply chain handling (e.g., transport, storage, handling). 4059

4060 4061 Class Name: TradeItemHierarchy 4062 4063 Item Name: quantityOfCompleteLayersContainedInATradeItem 4064 4065

Core/Extension: E 4066 Global Local Status: G 4067 M/O/D: O 4068 Multiple Values Allowed: N 4069 Neutral/Relationship Dependant: T.P.Neutral 4070 Product Hierarchy Reference Level: Mixed Mod, Pallet, Display/ 4071

Shipper, Case, Pack 4072 Common value to all product hierarchy: No 4073 Type: N 4074 Size: 6 4075

4076 Definition: The number of layers of the base trade item found in a trade 4077 item. Does not apply to the base trade item unit. 4078

4079 Examples: 4080

4081 Business Rules: Only applies to logistic units (e.g. pallet, case, etc) 4082

4083 4084 Class Name: TradeItemHierarchy 4085 4086 Item Name: quantityOfLayersPerPallet 4087

4088 Core/Extension: E 4089 Global Local Status: G 4090 M/O/D: O 4091 Multiple Values Allowed: N 4092 Neutral/Relationship Dependant: T.P.Neutral 4093 Product Hierarchy Reference Level: Each 4094 Common value to all product hierarchy: No 4095 Type: N 4096 Size: 6 4097

4098 Definition: The number of layers that a pallet contains. Only used if the 4099 pallet has no GTIN. It indicates the number of layers that a pallet 4100 contains, according to supplier or retailer preferences. 4101

4102

Page 94: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 93 of 195

Examples: 4103 4104

Business Rules: Only used if the pallet has no GTIN. In this case it 4105 applies to the highest level of the item hierarchy and only 1 pallet 4106 configuration can be provided. It is highly recommended to use GTIN for 4107 Pallet identification. 4108 4109

4110 Class Name: TradeItemHierarchy 4111 4112 Item Name: quantityOfTradeItemsContainedInACompleteLayer 4113 4114

Core/Extension: E 4115 Global Local Status: G 4116 M/O/D: O 4117 Multiple Values Allowed: N 4118 Neutral/Relationship Dependant: T.P.Neutral 4119 Product Hierarchy Reference Level: Mixed Mod, Pallet, 4120 Display/Shipper, Case, Pack 4121 Common value to all product hierarchy: No 4122 Type: N 4123 Size: 6 4124

4125 Definition: The number of trade items contained in a complete layer of a 4126 higher packaging configuration. Used in hierarchical packaging structure 4127 of a trade item. Cannot be used for trade item base unit. 4128

4129 Examples: 4130

4131 Business Rules: Only applies to logistic units (e.g. pallet, case, etc) 4132

4133 4134 Class Name: TradeItemHierarchy 4135 4136 Item Name: quantityOfTradeItemsPerPallet 4137 4138

Core/Extension: E 4139 Global Local Status: G 4140 M/O/D: O 4141 Multiple Values Allowed: N 4142 Neutral/Relationship Dependant: T.P.Neutral 4143 Product Hierarchy Reference Level: Pallet, Mixed Mod 4144 Common value to all product hierarchy: No 4145 Type: N 4146 Size: 6 4147

4148 Definition: The number of trade items contained in a pallet. Only used if 4149 the pallet has no GTIN. It indicates the number of trade items placed on a 4150 pallet according to supplier or retailer preferences. 4151

4152

Page 95: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 94 of 195

Examples: 4153 4154

Business Rules: Only used if the pallet has no GTIN. In this case it 4155 applies to the highest level of the item hierarchy and only 1 pallet 4156 configuration can be provided. It is highly recommended to use GTIN for 4157 Pallet identification. 4158

4159 4160 Class Name: TradeItemHierarchy 4161 4162 Item Name: quantityOfTradeItemsPerPalletLayer 4163 4164

Core/Extension: E 4165 Global Local Status: G 4166 M/O/D: O 4167 Multiple Values Allowed: N 4168 Neutral/Relationship Dependant: T.P.Neutral 4169 Product Hierarchy Reference Level: Pallet, MixedMod 4170 Common value to all product hierarchy: No 4171 Type: N 4172 Size: 6 4173

4174 Definition: The number of trade items contained on a single layer of a 4175 pallet. Only used if the pallet has no GTIN. It indicates the number of 4176 trade items placed on a pallet layer according to supplier or retailer 4177 preferences. 4178

4179 Examples: 4180

4181 Business Rules: Only used if the pallet has no GTIN. In this case it 4182 applies to the highest level of the item hierarchy. It is highly 4183 recommended to use GTIN for Pallet identification. 4184

4185 4186 Class Name: TradeItemHierarchy 4187 4188 Item Name: quantityOfInnerPack 4189 4190

Core/Extension: E 4191 Global Local Status: G 4192 M/O/D: O 4193 Multiple Values Allowed: N 4194 Neutral/Relationship Dependant: T.P.Neutral 4195 Product Hierarchy Reference Level: All 4196 Common value to all product hierarchy: No 4197 Type: N 4198 Size: ..3 4199

4200 Definition: Indicates the number of non-coded physical groupings 4201 (innerpacks) of next lower level trade items within the current GTIN level. 4202

Page 96: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 95 of 195

4203 Examples: Case of 12 bottles of shampoo contains two non-coded 4204 plastic wrapped bundles each with six bottles. Value = "2" 4205

4206 Business Rules: An inner pack can only contain the same GTIN, and 4207 inner pack sizing must be constant. Change of inner pack doesn't change 4208 higher or lower level GTINs 4209

4210 4211

Class Name: TradeItemHierarchy 4212 4213 Item Name: quantityOfNextLevelTradeItemWithinInnerPack 4214 4215

Core/Extension: E 4216 Global Local Status: G 4217 M/O/D: O 4218 Multiple Values Allowed: N 4219 Neutral/Relationship Dependant: T.P.Neutral 4220 Product Hierarchy Reference Level: All 4221 Common value to all product hierarchy: No 4222 Type: N 4223 Size: ..3 4224

4225 Definition: Indicates the number of next lower level trade items contained 4226 within the physical non-coded grouping (innerpack) 4227

4228 Examples: Case of 12 bottles of shampoo contains two non-coded 4229 plastic wrapped bundles each with six bottles. Value = "6" 4230

4231 Business Rules: An inner pack can only contain the same GTIN, and 4232 inner pack sizing must be constant. Change of inner pack doesn't change 4233 higher or lower level GTINs 4234

4235 4236 Class Name: TradeItemImportIdentification 4237 4238 Item Name: importClassificationType 4239 4240

Core/Extension: E 4241 Global Local Status: G/L 4242 M/O/D: O 4243 Multiple Values Allowed: N 4244 Neutral/Relationship Dependant: T.P.Neutral 4245 Product Hierarchy Reference Level: Each 4246 Common value to all product hierarchy: No 4247 Type: Enumerated List 4248 Size: Not Applicable 4249

4250 Definition: This is a code to indicate the type of import classification for 4251 the Trade Item. 4252

Page 97: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 96 of 195

4253 Examples: Values include Netherlands Import Code, Harmonized 4254 Commodity Description and Coding System, Customs tariff and 4255 INTRASTAT Code, Harmonized Tariff Schedule of the United States, 4256 INTRASTAT Combined Nomenclature, Tarif Intégré de la Communauté. 4257

4258 Class Name: TradeItemImportIdentification 4259 4260 Item Name: importClassificationValue: 4261 4262

Core/Extension: E 4263 Global Local Status: G/L 4264 M/O/D: O 4265 Multiple Values Allowed: N 4266 Neutral/Relationship Dependant: T.P.Neutral 4267 Product Hierarchy Reference Level: Each 4268 Common value to all product hierarchy: No 4269 Type: AN 4270 Size: 70 4271

4272 Definition: Imports and exports of trade items typically re-quire 4273 classification codes to determine appropriate duties and tariffs. Values 4274 include Netherlands Import Code, Harmonized Commodity Description 4275 and Coding System, Customs Tariff and INTRASTAT Code, Harmonized 4276 Tariff Schedule of the United States, INTRASTAT Combined 4277 Nomenclature, Tarif Intégré de la Communauté. 4278 4279 Business Rules: Required on Import Products only. 4280 4281

4282 Class Name: TradeItemMarking 4283 4284 Item Name: hasBatchNumber 4285 4286

Core/Extension: E 4287 Global Local Status: L 4288 M/O/D: O 4289 Multiple Values Allowed: N 4290 Neutral/Relationship Dependant: T.P.Neutral 4291 Product Hierarchy Reference Level: Each 4292 Common value to all product hierarchy: No 4293 Type: Boolean 4294 Size: Not Applicable 4295

4296 Definition: Indication whether the base trade item is batch or lot number 4297 requested by law, not batch or lot number requested by law but batch or lot 4298 number allocated, or not batch or lot number allocated. A batch or lot number 4299 is a manufacturer assigned code used to identify a trade item's trade item on 4300 batch or lot. Differs from Serial Number which is a manufacturer assigned 4301 code during the trade item on cycle to identify a unique trade item. 4302

Page 98: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 97 of 195

4303 Examples: 4304

4305 Business Rules: Local legal requirement (E.g. Austria). Relevant only for 4306 certain industries. 4307

4308 4309 Class Name: TradeItemMarking 4310 4311 Item Name: isNonSoldTradeItemReturnable 4312 4313

Core/Extension: E 4314 Global Local Status: G/L 4315 M/O/D: O 4316 Multiple Values Allowed: N 4317 Neutral/Relationship Dependant: T.P.Neutral 4318 Product Hierarchy Reference Level: Each 4319 Common value to all product hierarchy: No 4320 Type: Boolean 4321 Size: Not Applicable 4322

4323 Definition: Indicates that the buyer can return the articles that are not 4324 sold. Used, for example; with magazines and bread. This is a y/n 4325 (Boolean) where y equals right of return. This is at least relevant to 4326 General Merchandise, Publishing industries and for some FMCG trade 4327 item. 4328

4329 Examples: 4330

4331 Business Rules: This attribute applies to certain industries, and applies 4332 to return of salable goods. This indicator identifies the general rule, and is 4333 not transaction based. 4334

4335 4336 Class Name: TradeItemMarking 4337 4338 Item Name: isTradeItemMarkedAsRecyclable 4339 4340

Core/Extension: E 4341 Global Local Status: G/L 4342 M/O/D: O 4343 Multiple Values Allowed: N 4344 Neutral/Relationship Dependant: T.P.Neutral 4345 Product Hierarchy Reference Level: Each 4346 Common value to all product hierarchy: No 4347 Type: Boolean 4348 Size: Not Applicable 4349

4350 Definition: Trade item has a recyclable indication marked on it, This may 4351 be a symbol from one of many regional agencies. 4352

Page 99: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 98 of 195

4353 Examples: Battery recycling logo placed on the battery, Refrigerators, 4354 Heat Pumps and Air Conditioners symbol, Paper marked as recyclable 4355 symbol, Plastic types marked as recyclable symbols. 4356

4357 Business Rules: This is a yes/no (Boolean) where yes equals trade item 4358 marked with ISO markings. 4359

4360 4361 Class Name: TradeItemMaterial 4362 4363 Item Name: materialWeight: 4364 4365

Core/Extension: E 4366 Global Local Status: G/L 4367 M/O/D: O 4368 Multiple Values Allowed: N 4369 Neutral/Relationship Dependant: T.P.Neutral 4370 Product Hierarchy Reference Level: Each 4371 Common value to all product hierarchy: No 4372 Type: Measurement Value 4373 Size: Decimal 15, String 3 for Unit Of Measure 4374

4375 Definition: The measured weight of the material expressed in ounces per 4376 square yard or grams per square meter. For example: 20 OZ Denim 4377 would be specified as 20 UOM = ON. The fabrics range from gossamer 4378 fine to bulky and are described with the following terms: light, medium, 4379 medium-heavy, and heavy. Light weight fabrics weigh up to 6 oz./sq. yd. 4380 (200 g/m2). They include applications such as crisp café curtains and a 4381 number of sheer window coverings. Medium weight fabrics generally 4382 weigh from 6 oz./sq. yd. to 12 oz./sq. yd. (200 g/m2 to 400 g/m2). They 4383 hang well in drapes and are the common choice for slipcovers. Medium-4384 heavy weight fabrics weigh from 12 oz./sq. yd. to 18 oz./sq. yd. (400 g/m2 4385 to 600 g/m2). They comprise most upholstery fabrics, many drapery 4386 materials, and the most substantial terry toweling. Heavy weight fabrics 4387 weigh over 18 oz./sq. yd. (600 g/m2). They include a number of 4388 upholstery fabrics. The very heaviest consumer textiles are various types 4389 of carpet and other floor coverings. 4390 4391 Business Rules: Acceptable Units of Measure for fabric weight are: ON 4392 – Ounces per square yard (oz/yd2)GM - Grams per square meter (g/m²). 4393

4394 4395 Class Name: TradeItemMaterial 4396 4397 Item Name: threadCount: 4398 4399

Core/Extension: E 4400 Global Local Status: G/L 4401 M/O/D: O 4402

Page 100: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 99 of 195

Multiple Values Allowed: N 4403 Neutral/Relationship Dependant: T.P.Neutral 4404 Product Hierarchy Reference Level: Each 4405 Common value to all product hierarchy: No 4406 Type: Description 4407 Size: 70 4408

4409 Definition: This element is used to specify the quality of material (fabric) 4410 of a trade item. 4411 4412 Example: 300 threads per square inch for sheets. 4413 4414 Business Rules: May be used for marketing purposes (both to buyer and 4415 end consumer). 4416

4417 4418 Class Name: TradeItemMeasurements 4419 4420 Item Name: depth 4421 4422

Core/Extension: E 4423 Global Local Status: G 4424 M/O/D: M 4425 Multiple Values Allowed: N 4426 Neutral/Relationship Dependant: T.P.Neutral 4427 Product Hierarchy Reference Level: All 4428 Common value to all product hierarchy: No 4429 Type: Multi Measurement Value 4430 Size: Decimal 15, String 3 for Unit Of Measure 4431 4432 Definition: The measurement from front to back of the trade item. 4433

4434 Examples: "5 MMT" 4435

4436 Business Rules: Measurements are relative to how the customer 4437 normally views the trade item. Orientation guidelines to be determined by 4438 PTRG within CR 02-000102 by Needs to be associated with a valid UoM. 4439 See Section 4.6 of the Implementation Considerations and Concerns for 4440 more detail on UoM. 4441 4442 4443

Class Name: TradeItemMeasurements 4444 4445 Item Name: diameter 4446 4447

Core/Extension: E 4448 Global Local Status: G 4449 M/O/D: O 4450 Multiple Values Allowed: N 4451 Neutral/Relationship Dependant: T.P.Neutral 4452

Page 101: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 100 of 195

Product Hierarchy Reference Level: Each 4453 Common value to all product hierarchy: No 4454 Type: Multi Measurement Value 4455 Size: Decimal 15, String 3 for Unit Of Measure 4456 4457 Definition: The measurement of the diameter of the trade item at its 4458 largest point. 4459

4460 Examples: 165 "mmt", value - mmt, diameter 4461

4462 Business Rules: Has to be associated with valid UoM. See Section 4.6 4463 of the Implementation Considerations and Concerns for more detail on 4464 UoM. 4465

4466 4467

Class Name: TradeItemMeasurements 4468 4469 Item Name: drainedWeight 4470 4471

Core/Extension: E 4472 Global Local Status: G 4473 M/O/D: O 4474 Multiple Values Allowed: N 4475 Neutral/Relationship Dependant: T.P.Neutral 4476 Product Hierarchy Reference Level: Each 4477 Common value to all product hierarchy: No 4478 Type: Multi Measurement Value 4479 Size: Decimal 15, String 3 for Unit Of Measure 4480 4481 Definition: The weight of the trade item when drained of its liquid. 4482

4483 Examples: 225 "grm", Jar of pickles in vinegar. Value, ounces, pounds, 4484 etc. 4485

4486 Business Rules: Applies to defined bricks of GCI Global trade item 4487 Classification - Mainly food trade item. Has to be associated with a valid UoM. 4488 See Section 4.6 of the Implementation Considerations and Concerns for more 4489 detail on UoM. 4490 4491 4492

Class Name: TradeItemMeasurements 4493 4494 Item Name: genericIngredient 4495 4496

Core/Extension: E 4497 Global Local Status: L 4498 M/O/D: O 4499 Multiple Values Allowed: N 4500 Neutral/Relationship Dependant: T.P.Neutral 4501 Product Hierarchy Reference Level: Each 4502

Page 102: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 101 of 195

Common value to all product hierarchy: No 4503 Type: AN 4504 Size: ..35 4505

4506 Definition: Used, for pharmaceutical trade item to describe 1 or many 4507 generic ingredients within the trade item. 4508

4509 Examples: "Paracetamol", "Codeine" 4510

4511 Business Rules: Sector specific and local extension. Can be repeated. 4512

4513 4514 Class Name: TradeItemMeasurements 4515 4516 Item Name: genericIngredientStrength 4517 4518

Core/Extension: E 4519 Global Local Status: L 4520 M/O/D: O 4521 Multiple Values Allowed: N 4522 Neutral/Relationship Dependant: T.P.Neutral 4523 Product Hierarchy Reference Level: Each 4524 Common value to all product hierarchy: No 4525 Type: Multi Measurement Value 4526 Size: Decimal 15, String 3 for Unit Of Measure 4527 4528 Definition: Used, for pharmaceutical trade item to define the strength of 4529 each generic ingredient in a trade item or unit volume of the trade item. 4530

4531 Examples: 4532

4533 Business Rules: Sector specific and local extension. 4534 Repeated per generic Substance 4535 Needs to be associated with a valid UoM. See Section 4.6 of the 4536 Implementation Considerations and Concerns for more details on UoM. 4537 4538 4539

Class Name: TradeItemMeasurements 4540 4541 Item Name: grossWeight 4542 4543

Core/Extension: E 4544 Global Local Status: G 4545 M/O/D: O 4546 Multiple Values Allowed: N 4547 Neutral/Relationship Dependant: T.P.Neutral 4548 Product Hierarchy Reference Level: All 4549 Common value to all product hierarchy: No 4550 Type: Multi Measurement Value 4551 Size: Decimal 15, String 3 for Unit Of Measure 4552

4553

Page 103: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 102 of 195

Definition: Used to identify the gross weight of the trade item. The gross 4554 weight includes all packaging materials of the trade item. At pallet level 4555 the trade itemGrossWeight includes the weight of the pallet itself. 4556

4557 Examples: "200 grm", value - total pounds, total grams, etc. 4558

4559 Business Rules: Has to be associated with a valid UoM. See Section 4.6 4560 of the Implementation Considerations and Concerns for more detail on 4561 UoM. 4562 4563 4564

Class Name: TradeItemMeasurements 4565 4566 Item Name: height 4567 4568

Core/Extension: E 4569 Global Local Status: G 4570 M/O/D: M 4571 Multiple Values Allowed: N 4572 Neutral/Relationship Dependant: T.P.Neutral 4573 Product Hierarchy Reference Level: All 4574 Common value to all product hierarchy: No 4575 Type: Multi Measurement Value 4576 Size: Decimal 15, String 3 for Unit Of Measure 4577 4578 Definition: The measurement of the height of the trade item. The vertical 4579 dimension from the lowest extremity to the highest extremity, including 4580 packaging. At a pallet level the trade itemHeight will include the height of 4581 the pallet itself. 4582

4583 Examples: "60 CMT" 4584

4585 Business Rules: Measurements are relative to how the customer 4586 normally views the trade item. Orientation guidelines to be determined by 4587 PTRG within CR 02-000102 by Needs to be associated with a valid UoM. 4588 See Section 4.6 of the Implementation Considerations and Concerns for 4589 more detail on UoM. 4590 4591

4592 Class Name: TradeItemMeasurements 4593 4594 Item Name: ingredientStrength 4595 4596

Core/Extension: E 4597 Global Local Status: G/L 4598 M/O/D: O 4599 Multiple Values Allowed: N 4600 Neutral/Relationship Dependant: T.P.Neutral 4601 Product Hierarchy Reference Level: Each 4602 Common value to all product hierarchy: No 4603

Page 104: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 103 of 195

Type: AN 4604 Size: ..18 4605

4606 Definition: Used for pharmaceutical trade item to define the strength of 4607 each ingredient in a trade item or unit volume of the trade item. 4608 4609 Examples: "100mg" for a tablet, "2%" for a liquid or ointment, where 100 4610 and 2 represent the value, and mg and % are the units of measure 4611

4612 Business Rules: Sector specific extension pharmaceutical trade item. 4613 Can be locally mandatory based on each country's laws. Has to be 4614 associated with a valid unitBasisOfMeasure 4615

4616 4617 Class Name: TradeItemMeasurements 4618 4619 Item Name: isNetContentDeclarationIndicated 4620 4621

Core/Extension: E 4622 Global Local Status: G/L 4623 M/O/D: O 4624 Multiple Values Allowed: N 4625 Neutral/Relationship Dependant: T.P.Neutral 4626 Product Hierarchy Reference Level: Each 4627 Common value to all product hierarchy: No 4628 Type: Boolean 4629 Size: Not Applicable 4630

4631 Definition: This field is used to facilitate local business rules where a 4632 declaration of a trade item's net content is not on the product label 4633 e.g.,UK under 50g.legislation 4634

4635 Examples: 4636

4637 Business Rules: For a product without an on-pack net content 4638 declaration this field should be indicated as YES, weight should be 4639 communicated at the trade unit level. 4640 4641

4642 Class Name: TradeItemMeasurements 4643 4644 Item Name: netContent 4645 4646

Core/Extension: E 4647 Global Local Status: G 4648 M/O/D: O 4649 Multiple Values Allowed: N 4650 Neutral/Relationship Dependant: T.P.Neutral 4651 Product Hierarchy Reference Level: Each 4652 Common value to all product hierarchy: No 4653 Type: Multi Measurement Value 4654 Size: Decimal 15, String 3 for Unit Of Measure 4655

Page 105: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 104 of 195

4656 Definition: The amount of the trade item contained by a package, as 4657 claimed on the label. (See examples) 4658

4659 Examples: Evian Water 750ml - net content = "750 MLT" ; 20 count pack 4660 of diapers, net content = "20 ea." 4661

4662 Business Rules: In case of multi-pack, indicates the net content of the total 4663 trade item. For fixed value trade items use the value claimed on the package, 4664 to avoid variable fill rate issue that arises with some trade item which are sold 4665 by volume or weight, and whose actual content may vary slightly from batch to 4666 batch. In case of variable quantity trade items, indicates the average quantity. 4667 See Section 4.6 of the Implementation Considerations and Concerns for more 4668 detail on UoM. 4669

4670 Class Name: TradeItemMeasurements 4671 4672 Item Name: netWeight 4673 4674

Core/Extension: E 4675 Global Local Status: G 4676 M/O/D: O 4677 Multiple Values Allowed: N 4678 Neutral/Relationship Dependant: T.P.Neutral 4679 Product Hierarchy Reference Level: Mixed Mod, Pallet, Display 4680 /Shipper, Case Pack 4681 Common value to all product hierarchy: No 4682 Type: Multi Measurement Value 4683 Size: Decimal 15, String 3 for Unit Of Measure 4684 4685 Definition: Used to identify the net weight of the trade item. Net weight 4686 excludes any packaging materials and applies to all levels but consumer 4687 unit level. 4688

4689 Examples: "11.5 kgm" value - pounds, grams, etc. 4690

4691 Business Rules: For consumer unit, Net Content replaces Net Weight 4692 (can then be weight, size, volume). Has to be associated with a valid 4693 UoM. See Section 4.6 of the Implementation Considerations and 4694 Concerns for more detail on UoM. 4695 4696

Class Name: TradeItemMeasurements 4697 4698 Item Name: priceComparisonContentType: 4699

4700 Core/Extension: E 4701 Global Local Status: G 4702 M/O/D: O 4703 Multiple Values Allowed: N 4704 Neutral/Relationship Dependant: T.P.Neutral 4705

Page 106: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 105 of 195

Product Hierarchy Reference Level: All 4706 Common value to all product hierarchy: No 4707 Type: Enumerated List 4708 Size: Not Applicable 4709

4710 Definition: Code indicating how the value in 4711 priceComparisonMeasurement is used to calculate the comparative price, 4712 which is printed on shelf labels. 4713

4714 Examples: 4715

4716 Business Rules: 4717

4718 Class Name: TradeItemMeasurements 4719 4720 Item Name: priceComparisonMeasurement 4721

4722 Core/Extension: E 4723 Global Local Status: G 4724 M/O/D: O 4725 Multiple Values Allowed: N 4726 Neutral/Relationship Dependant: T.P.Neutral 4727 Product Hierarchy Reference Level: All 4728 Common value to all product hierarchy: No 4729 Type: Multi Measurement Value 4730 Size: Decimal 15, String 3 for Unit Of Measure 4731

4732 Definition: The quantity of the product at usage. Applicable for 4733 concentrated products and products where the comparison price is 4734 calculated based on a measurement other than netContent. 4735 4736 Business Rules: This field is dependent on the population of 4737 priceComparisonContentType and is required when 4738 priceComparisonContentType is used. 4739 4740

4741 Class Name: TradeItemMeasurements 4742 4743 Item Name: tradeItemCompositionWidth: 4744 4745

Core/Extension: E 4746 Global Local Status: G 4747 M/O/D: O 4748 Multiple Values Allowed: N 4749 Neutral/Relationship Dependant: T.P.Neutral 4750 Product Hierarchy Reference Level: All 4751 Common value to all product hierarchy: No 4752 Type: Multi Measurement Value 4753 Size: Decimal 15, String 3 for Unit Of Measure 4754 4755

Page 107: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 106 of 195

Definition: The number of child-items that are packaged beside each 4756 other in a trade unit (on the side facing the consumer). This information is 4757 used in the space process, especially when allocating whole Trade Units 4758 (intermediate) into the shelf. The Space Manager always allocates Base 4759 Units in the shelf. Usually there are no pictures of Trade Units available 4760 and for Hypermarkets/Big Supermarkets there is a need to allocate whole 4761 trade units into the shelves. 4762

4763 4764 Class Name: TradeItemMeasurements 4765 4766 Item Name: width 4767 4768

Core/Extension: E 4769 Global Local Status: G 4770 M/O/D: M 4771 Multiple Values Allowed: N 4772 Neutral/Relationship Dependant: T.P.Neutral 4773 Product Hierarchy Reference Level: All 4774 Common value to all product hierarchy: No 4775 Type: Multi Measurement Value 4776 Size: Decimal 15, String 3 for Unit Of Measure 4777 4778 Definition: The measurement from left to right of the trade item. 4779

4780 Examples: "10 INH" 4781

4782 Business Rules: Measurements are relative to how the customer 4783 normally views the trade item. Orientation guidelines to be determined by 4784 PTRG within CR 02-000102 by Needs to be associated with a valid UoM. 4785 See Section 4.6 of the Implementation Considerations and Concerns for 4786 more detail on UoM. 4787 4788 4789

Class Name: TradeItemOrderInformation 4790 4791

Item Name: agreedMaximumBuyingQuantity 4792 4793 Core/Extension: E 4794 Global Local Status: G/L 4795 M/O/D: O 4796 Multiple Values Allowed: N 4797 Neutral/Relationship Dependant:T.P.Dependent 4798 Product Hierarchy Reference Level: All 4799 Common value to all product hierarchy: No 4800 Type: N 4801 Size: ..9 4802

4803 Definition: The maximum quantity of the product available to the retailer. 4804

4805

Page 108: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 107 of 195

4806 Class Name: TradeItemOrderInformation 4807 4808 Item Name: agreedMinimumBuyingQuantity: 4809

4810 Core/Extension: E 4811 Global Local Status: G/L 4812 M/O/D: O 4813 Multiple Values Allowed: N 4814 Neutral/Relationship Dependant:T.P.Dependent 4815 Product Hierarchy Reference Level: All 4816 Common value to all product hierarchy: No 4817 Type: N 4818 Size: ..9 4819

4820 Definition: Minimum buying quantity agreed between trading partners. 4821 4822

4823 Class Name: TradeItemOrderInformation 4824 4825 Item Name: firstDeliveryDateTime: 4826 4827

Core/Extension: E 4828 Global Local Status: G/L 4829 M/O/D: O 4830 Multiple Values Allowed: N 4831 Neutral/Relationship Dependant:T.P.Dependent 4832 Product Hierarchy Reference Level: All 4833 Common value to all product hierarchy: No 4834 Type: Date Time 4835 Size: CCYY-MM-DDTHH:MM:SS 4836

4837 Definition: The earliest date at which the supplier can deliver the 4838 product to the trading partner. 4839

4840 4841 Class Name: TradeItemOrderInformation 4842 4843 Item Name: goodsPickUpLeadTime: 4844 4845

Core/Extension: E 4846 Global Local Status: G/L 4847 M/O/D: O 4848 Multiple Values Allowed: N 4849 Neutral/Relationship Dependant:T.P.Dependent 4850 Product Hierarchy Reference Level: All 4851 Common value to all product hierarchy: No 4852 Type: Multi Measurement Value 4853 Size: Decimal 15, String 3 for Unit Of Measure 4854

4855

Page 109: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 108 of 195

Definition: Time (in weeks, days, hours …) required between order entry 4856 and the earliest goods release (use for pick-up, not use for delivery). 4857 Remark about ordering lead-time : Geographic distance from 4858 manufacturing / distribution point to delivery point impacts this value 4859 (relationship dependant data). 4860

4861 4862 Class Name: TradeItemOrderInformation 4863 4864 Item Name: isTradeItemReorderable 4865 4866

Core/Extension: E 4867 Global Local Status: G/L 4868 M/O/D: O 4869 Multiple Values Allowed: N 4870 Neutral/Relationship Dependant:T.P.Dependent 4871 Product Hierarchy Reference Level: All 4872 Common value to all product hierarchy: No 4873 Type: Boolean 4874 Size: Not Applicable 4875

4876 Definition: This element is an indicator that selected styles or trade items 4877 may or may not be re-ordered. It does not imply any information on 4878 current availability. Example: Some Designer's Merchandise, T-shirts 4879 printed out for a special event (commemorative items). 4880

4881 4882 Class Name: TradeItemOrderInformation 4883 4884 Item Name: isTradeItemSizeBasedPricing: 4885 4886

Core/Extension: E 4887 Global Local Status: G/L 4888 M/O/D: O 4889 Multiple Values Allowed: N 4890 Neutral/Relationship Dependant:T.P.Dependent 4891 Product Hierarchy Reference Level: All 4892 Common value to all product hierarchy: No 4893 Type: Boolean 4894 Size: Not Applicable 4895 4896 Definition: This is an indicator that an item may be at a different price 4897 point than other similar SKUs (GTIN's price within a Style may differ). 4898

4899 4900 Class Name: TradeItemOrderInformation 4901 4902 Item Name: orderingLeadTime 4903 4904

Core/Extension: E 4905

Page 110: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 109 of 195

Global Local Status: G/L 4906 M/O/D: O 4907 Multiple Values Allowed: N 4908 Neutral/Relationship Dependant: T.P.Neutral 4909 Product Hierarchy Reference Level: All 4910 Common value to all product hierarchy: No 4911 Type: Multi-Measurement 4912 Size: Decimal 15, String 3 for Unit Of Measure 4913 4914 Definition: The normal delivery time measured from receipt of order by 4915 the seller until trade item is shipped by the seller. 4916

4917 Examples: 12 hours, 48 hours, 4 days. 4918

4919 Business Rules: Geographic distance from manufacturing/distribution 4920 point to delivery point may impact this value. Related to time unit field. 4921 Must be associated with valid unit of measure. 4922

4923 Class Name: TradeItemOrderInformation 4924 4925 Item Name: orderQuantityMaximum 4926 4927

Core/Extension: E 4928 Global Local Status: G/L 4929 M/O/D: O 4930 Multiple Values Allowed: N 4931 Neutral/Relationship Dependant:T.P.Dependent 4932 Product Hierarchy Reference Level: All 4933 Common value to all product hierarchy: No 4934 Type: N 4935 Size: ..9 4936

4937 Definition: The maximum quantity of the trade item that can be ordered. 4938 A number or a count. This value can represent the total number of units 4939 ordered over a set period of time with multiple orders. 4940

4941 Examples: - “when a manufacturer chooses to control manufacturing 4942 costs by limiting the amount of product that a customer can buy per order 4943 – example – Geneva watchmaker only allows orders of 10 watches per 4944 customer per order so as to control their production for quality control 4945 reasons, and to ensure that all of his customers receive some product.” 4946

4947 Business Rules: Value can vary on Trading Partner dependent basis. 4948 Quantity means number of this trade item level hierarchy. This field is 4949 relevant at any trade item hierarchy level, but does not need to be 4950 populated for all levels. 4951

4952 4953 4954 4955

Page 111: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 110 of 195

Class Name: TradeItemOrderInformation 4956 4957 Item Name: orderQuantityMinimum 4958 4959

Core/Extension: E 4960 Global Local Status: G/L 4961 M/O/D: O 4962 Multiple Values Allowed: N 4963 Neutral/Relationship Dependant:T.P.Dependent 4964 Product Hierarchy Reference Level: All 4965 Common value to all product hierarchy: No 4966 Type: N 4967 Size: ..9 4968

4969 Definition: Represent an agreed to minimum quantity of the trade item 4970 that can be ordered. A number or a count. This applies to each individual 4971 order. Can be a fixed amount for all customers in a target market. 4972

4973 Examples: - 4974

4975 Business Rules: Value refers to the minimum order for this trade item 4976 hierarchy level. Cannot be a monetary figure. E.g. minimum order = $100 4977 of goods at cost. This field is relevant at any trade item hierarchy level, 4978 but does not need to be populated for all levels. 4979

4980 4981 Class Name: TradeItemOrderInformation 4982 4983 Item Name: orderQuantityMultiple 4984 4985

Core/Extension: E 4986 Global Local Status: G/L 4987 M/O/D: O 4988 Multiple Values Allowed: N 4989 Neutral/Relationship Dependant: T.P.Neutral 4990 Product Hierarchy Reference Level: All 4991 Common value to all product hierarchy: No 4992 Type: N 4993 Size: ..9 4994

4995 Definition: The order quantity multiples in which the trade item may be 4996 ordered. If the Order Quantity Minimum is 100, and the Order Quantity 4997 Multiple is 20, then the trade item can only be ordered in quantities which 4998 are divisible by the Order Quantity Multiple of 20. 4999

5000 Examples:100, 120, 140, 200. A number or a count. 5001

5002 Business Rules: If the order quantity minimum is 100, and the order 5003 quantity multiple is 20, then the product can only be ordered in quantities 5004

Page 112: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 111 of 195

which are divisible by the order quantity multiple of 20, eg 100, 120, 140 5005 200 etc. 5006

5007 5008 Class Name: TradeItemOrderInformation 5009 5010 Item Name: orderSizingFactor 5011 5012

Core/Extension: E 5013 Global Local Status: G/L 5014 M/O/D: O 5015 Multiple Values Allowed: N 5016 Neutral/Relationship Dependant: T.P.Neutral 5017 Product Hierarchy Reference Level: All 5018 Common value to all product hierarchy: No 5019 Type: Multi Measurement Value 5020 Size: Decimal 15, String 3 for Unit Of Measure 5021 5022 Definition: A trade item specification other than gross, net weight, or 5023 cubic feet for a line trade item or a transaction, used for order sizing and 5024 pricing purposes. For example, factors may be used to cube a truck, 5025 reflecting different weights, and dimensions of trade item. 5026

5027 Examples: 5028

5029 Business Rules: Assumes a standard size truck or lorry 5030

5031 5032 Class Name: Trade Item Pallet Information 5033 5034 Item Name: palletTypeCode 5035 5036

Core/Extension: E 5037 Global Local Status: G/L 5038 M/O/D: O 5039 Multiple Values Allowed: N 5040 Neutral/Relationship Dependant: T.P.Neutral 5041 Product Hierarchy Reference Level: Pallet 5042 Common value to all product hierarchy: No 5043 Type: Char 5044 Size: 3 5045

5046 Definition: Indicates whether the described dispatch unit is delivered on 5047 a pallet and on which type of pallet, or if it is non-palletized. If the 5048 dispatch unit is delivered on a pallet the pallet type must be given here. 5049 The range of the pallet types/codes is listed in code sets. 5050

5051 Examples: "200" = pallet ISO 0, 1/2 Euro pallet. 5052

5053

Page 113: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 112 of 195

Business Rules: Only used if the pallet has no GTIN. In this case it 5054 applies to the highest level of the item hierarchy and only 1 pallet 5055 configuration can be provided. It is highly recommended to use GTIN for 5056 Pallet identification. 5057

5058 5059

Class Name: TradeItemPalletInformation 5060 5061 Item Name: palletTermsAndConditions 5062 5063

Core/Extension: E 5064 Global Local Status: G/L 5065 M/O/D: O 5066 Multiple Values Allowed: N 5067 Neutral/Relationship Dependant: T.P.Neutral 5068 Product Hierarchy Reference Level: Pallet 5069 Common value to all product hierarchy: No 5070 Type: AN 5071 Size: 2 5072

5073 Definition: Indicates if the pallet in the prescribed pallet configuration is 5074 rented, exchangeable, against deposit or one way (not reusable). 5075

5076 Examples: "7E" for non-returnable pallet 5077

5078 Business Rules: Used in conjunction with a pallet GTIN. List of 5079 authorized values based on EANCOM 7073, X12 DE102 and X12 DE399. 5080

5081 5082

Class Name: TradeItemPriceDateInformation 5083 5084 Item Name: cataloguePrice –represented by UML role 5085 5086

Core/Extension: E 5087 Global Local Status: G/L 5088 M/O/D: O 5089 Multiple Values Allowed: N 5090 Neutral/Relationship Dependant: T.P.Neutral 5091 Product Hierarchy Reference Level: All 5092 Common value to all product hierarchy: No 5093 Type: Amount 5094 Size: 17.4 5095

5096 Definition: The gross price before application of any discounts, 5097 allowances, charges, taxes, etcetera. The value represented is the price 5098 that the manufacturer expects to receive for the trade item or service from 5099 any buyer prior to any relationship specific negotiations (E.g. a public 5100 catalogue population). Synonym: List price 5101

5102 Examples: "USD 49.50", "EUR 350,00 5103

Page 114: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 113 of 195

5104 Business Rules: CatalogPrice would reside within the Item master data. 5105 The Core Price model would contain class and price along with the class 5106 price type. These will be one of the numerated values for class price type 5107 in Core Price model. 5108 Implementation Note: This attribute is represented by UML role. 5109 5110 5111

Class Name: TradeItemPriceDateInformation 5112 5113 Item Name: effectiveStartDate 5114 5115

Core/Extension: E 5116 Global Local Status: G/L 5117 M/O/D: D 5118 Multiple Values Allowed: N 5119 Neutral/Relationship Dependant: N/T.P.Dependent* 5120 Product Hierarchy Reference Level: All 5121 Common value to all product hierarchy: No 5122 Type: Date 5123 Size: CCYY-MM-DD 5124

5125 Definition: This is the effective start date of the price agreed to by the 5126 trading partners. This start date is mandatory and, if no end date is 5127 communicated, then implies that the price is effective until further notice. 5128 Various types of dates may be pre-aligned between buyer and seller. For 5129 example, based upon a prior agreement between trading partners this 5130 date may relate to any of the following events, first order date, first ship 5131 date, and first arrival date. 5132 Examples: -2002-11-15 5133

5134 Business Rules: Format defined in ISO8601 5135

5136 5137

Class Name: TradeItemPriceDateInformation 5138 5139 Item Name: effectiveEndDate 5140 5141

Core/Extension: E 5142 Global Local Status: G/L 5143 M/O/D: O 5144 Multiple Values Allowed: N 5145 Neutral/Relationship Dependant: N/T.P.Dependent* 5146 Product Hierarchy Reference Level: All 5147 Common value to all product hierarchy: No 5148 Type: Date 5149 Size: CCYY-MM-DD 5150

5151 Definition: The effective end date of the price is optional based upon the 5152 agreement by the trading partners. If an invalid end date is 5153

Page 115: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 114 of 195

communicated, then it is implied that the price and its effective date are 5154 effective until further notice. Examples of invalid dates include 5155 99/99/9999, 00/00/0000, blank, etc. These invalid end dates should not 5156 be communicated. Various types of dates may be pre-aligned between 5157 buyer and seller. For example, based upon a prior agreement between 5158 trading partners this date may relate to any of the following events, last 5159 order date, last ship date, and last arrival date. 5160

5161 Examples: 2005-12-31 5162

5163 Business Rules: PriceEndDate not required at time of initial price 5164 amount. Format defined by ISO8601 5165

5166 5167 Class Name: TradeItemPriceDateInformation 5168 5169 Item Name: suggestedRetailPrice represented by UML role 5170 5171

Core/Extension: E 5172 Global Local Status: G/L 5173 M/O/D: O 5174 Multiple Values Allowed: N 5175 Neutral/Relationship Dependant: T.P.Neutral 5176 Product Hierarchy Reference Level: Each 5177 Common value to all product hierarchy: No 5178 Type: Amount 5179 Size: 17.4 5180

5181 Definition: The retail (to consumer) price as suggested by the 5182 manufacturer. This is normally used to establish a proposed value for the 5183 trade item for marketing purposes. May or may not appear on the 5184 package. May be used as a guideline by the retailer to establish their 5185 actual retail price. 5186

5187 Examples: "value" USD1.90", "EUR 36" 5188

5189 Business Rules: As monetary amount field, this data element must be 5190 associated with a valid unit of measures. Changes in this value do not 5191 require a change in GTIN. ISO 4217 format three digit alpha code. 5192 When the suggestedRetailPrice is provided for information (and not on 5193 the package : priceOnPackIndicator = 'N') , it can be different per Target 5194 Market and becomes G / L. See Section 4.5 of Implementation 5195 Considerations and Concerns for more details. 5196 5197

Page 116: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 115 of 195

5198 Class Name: TradeItemSizeDescription 5199 5200 Item Name: descriptiveSize 5201 5202

Core/Extension: E 5203 Global Local Status: G 5204 M/O/D: O 5205 Multiple Values Allowed: N 5206 Neutral/Relationship Dependant: T.P.Neutral 5207 Product Hierarchy Reference Level: All 5208 Common value to all product hierarchy: Yes 5209 Type: Description 5210 Size: ..35 5211

5212 Definition: An alphanumeric size factor the brand owner wishes to 5213 communicate to the consumer. IE Jumbo, Capri, Full Length, Maxi 5214

5215 Examples: "Maxi", "Jumbo", "Mini", “7”, “10 ½”, “small”, 5216

5217 Business Rules: A descriptive size other than net content as labeled on 5218 consumer unit. Must be associated with a valid ISO language code from 5219 the attached table. 5220 5221 5222

Class Name: TradeItemSizeDescription 5223 5224 Item Name: sizeCodeListAgency 5225 5226

Core/Extension: E 5227 Global Local Status: G 5228 M/O/D: D 5229 Multiple Values Allowed: Y 5230 Neutral/Relationship Dependant: T.P.Neutral 5231 Product Hierarchy Reference Level: Each 5232 Common value to all product hierarchy: No 5233 Type: AN 5234 Size: ..3 5235

5236 Definition: The parties controlling the size code list. Dependent on size 5237 code value. 5238

5239 Examples: "25" EDITEX. 5240

5241 Business Rules: If size code is indicated, sizeCodeListAgency is 5242 required. Sector specific extension. 5243

5244 5245 Class Name: TradeItemSizeDescription 5246 5247

Page 117: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 116 of 195

Item Name: sizeCodeValue 5248 5249

Core/Extension: E 5250 Global Local Status: G 5251 M/O/D: O 5252 Multiple Values Allowed: Y 5253 Neutral/Relationship Dependant: T.P.Neutral 5254 Product Hierarchy Reference Level: Each 5255 Common value to all product hierarchy: No 5256 Type: AN 5257 Size: ..20 5258

5259 Definition: The value from a industry specific code list required to identify 5260 the size of the trade item. Can be a combination of values which fully 5261 describe the trade item size (32 waist, 36 inseam) 5262

5263 Examples: Used in industries such as shoes, apparel, home linens. "12 5264 1/2 Med". Shoe, pants which are "32W by 36" I, Oval Table Cover that is 5265 "36x" 5266

5267 Business Rules: 5268 Sector specific extension. Refer to Attribute code list in Implementation 5269 section. 5270

5271 Class Name: TradeItemTemperatureInformation 5272 5273 Item Name: deliveryToDistributionCenterTemperatureMaximum 5274 5275

Core/Extension: E 5276 Global Local Status: G 5277 M/O/D: O 5278 Multiple Values Allowed: N 5279 Neutral/Relationship Dependant: T.P.Neutral 5280 Product Hierarchy Reference Level: Each 5281 Common value to all product hierarchy: No 5282 Type: Multi Measurement Value 5283 Size:. Decimal 15, String 3 for Unit Of Measure 5284 5285 Definition: Permitted maximum temperature of the trade item on 5286 transport to the distribution center. 5287

5288 Examples: "+6 C" or degrees F, value 5289

5290 Business Rules: Temperature information is important for dairy trade 5291 item, dangerous goods and other trade items for which certain 5292 temperature limits are necessary during transport or storage, for quality or 5293 safety reasons. Has to be associated with valid UoM. See Section 4.6 of 5294 the Implementation Considerations and Concerns for more details of 5295 UoM. 5296

Page 118: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 117 of 195

5297 5298 Class Name: TradeItemTemperatureInformation 5299 5300 Item Name: deliveryToDistributionCenterTemperatureMinimum 5301 5302

Core/Extension: E 5303 Global Local Status: G 5304 M/O/D: O 5305 Multiple Values Allowed: N 5306 Neutral/Relationship Dependant: T.P.Neutral 5307 Product Hierarchy Reference Level: Each 5308 Common value to all product hierarchy: No 5309 Type: Multi Measurement Value 5310 Size: Decimal 15, String 3 for Unit Of Measure 5311

5312 Definition: Permitted minimum temperature of the trade item on transport 5313 to the distribution center. 5314

5315 Examples: "+2 C" or degrees F, value 5316

5317 Business Rules: Temperature information is important for dairy trade 5318 item, dangerous goods and other trade items for which certain 5319 temperature limits are necessary during transport or storage, for quality or 5320 safety reasons. Has to be associated with valid UoM. See Section 4.6 of 5321 the Implementation Considerations and Concerns for more details of 5322 UoM. 5323 5324

5325 Class Name: TradeItemTemperatureInformation 5326 5327 Item Name: deliveryToMarketTemperatureMaximum 5328 5329

Core/Extension: E 5330 Global Local Status: G 5331 M/O/D: O 5332 Multiple Values Allowed: N 5333 Neutral/Relationship Dependant: T.P.Neutral 5334 Product Hierarchy Reference Level: Each 5335 Common value to all product hierarchy: No 5336 Type: Multi Measurement Value 5337 Size: Decimal 15, String 3 for Unit Of Measure 5338

5339 Definition: Permitted maximum temperature of the trade item during 5340 delivery to market. 5341

5342 Examples: "+7 C" or degrees F, value 5343

5344 Business Rules: Temperature information is important for dairy trade 5345 item, dangerous goods and other trade items for which certain 5346

Page 119: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 118 of 195

temperature limits are necessary during transport or storage, for quality or 5347 safety reasons. Has to be associated with valid UoM. See Section 4.6 of 5348 the Implementation Considerations and Concerns for more details of 5349 UoM. 5350

5351 Class Name: TradeItemTemperatureInformation 5352 5353 Item Name: deliveryToMarketTemperatureMinimum 5354 5355

Core/Extension: E 5356 Global Local Status: G 5357 M/O/D: O 5358 Multiple Values Allowed: N 5359 Neutral/Relationship Dependant: T.P.Neutral 5360 Product Hierarchy Reference Level: Each 5361 Common value to all product hierarchy: No 5362 Type: Multi Measurement Value 5363 Size: Decimal 15, String 3 for Unit Of Measure 5364 5365 Definition: Permitted minimum temperature of the trade item during 5366 delivery to market to market. 5367

5368 Examples: "+3 C" or degrees F, value 5369

5370 Business Rules: Temperature information is important for dairy trade 5371 item, dangerous goods and other trade items for which certain 5372 temperature limits are necessary during transport or storage, for quality or 5373 safety reasons. Has to be associated with valid UoM. See Section 4.6 of 5374 theImplementation Considerations and Concerns for more details of 5375 UoM. 5376

5377 Class Name: TradeItemTemperatureInformation 5378 5379 Item Name: storageHandlingHumidityMaximum: 5380 5381

Core/Extension: E 5382 Global Local Status: G 5383 M/O/D: O 5384 Multiple Values Allowed: N 5385 Neutral/Relationship Dependant: T.P.Neutral 5386 Product Hierarchy Reference Level: Each 5387 Common value to all product hierarchy: No 5388 Type: Multi Measurement Value 5389 Size: Decimal 15, String 3 for Unit Of Measure 5390 5391 Definition: The maximum humidity in percentages that the goods should 5392 be stored in. 5393

5394 Examples: 5395 5396 Business Rules: 5397

Page 120: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 119 of 195

5398 Class Name: TradeItemTemperatureInformation 5399 5400 Item Name: storageHandlingHumidityMinimum: 5401 5402

Core/Extension: E 5403 Global Local Status: G 5404 M/O/D: O 5405 Multiple Values Allowed: N 5406 Neutral/Relationship Dependant: T.P.Neutral 5407 Product Hierarchy Reference Level: Each 5408 Common value to all product hierarchy: No 5409 Type: Multi Measurement Value 5410 Size: Decimal 15, String 3 for Unit Of Measure 5411 5412 Definition: The minimum humidity in percentages that the goods should 5413 be stored in. 5414

5415 Examples: 5416 5417 Business Rules: 5418

5419 5420 Class Name: TradeItemTemperatureInformation 5421 5422 Item Name: storageHandlingTemperatureMaximum 5423 5424

Core/Extension: E 5425 Global Local Status: G 5426 M/O/D: O 5427 Multiple Values Allowed: N 5428 Neutral/Relationship Dependant: T.P.Neutral 5429 Product Hierarchy Reference Level: All 5430 Common value to all product hierarchy: Yes 5431 Type: Multi Measurement Value 5432 Size: Decimal 15, String 3 for Unit Of Measure 5433 5434 Definition: The maximum temperature at which the trade item can be 5435 stored. This uses a measurement consisting of a unit of measure and a 5436 value. 5437

5438 Examples: "+15 F" or degrees C, value 5439

5440 Business Rules: When no other information is provided (temperatures to 5441 market or/and distribution center), this value applies at any point of the 5442 supply chain. Temperature information is important for fresh trade item, 5443 dangerous goods and other trade items for which certain temperature limits 5444 are necessary for quality or safety reasons. Has to be associated with a 5445 valid UoM. See Section 4.6 of the Implementation Considerations and 5446 Concerns for more details on UoM. 5447

5448

Page 121: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 120 of 195

5449 Class Name: TradeItemTemperatureInformation 5450 5451 Item Name: storageHandlingTemperatureMinimum 5452 5453

Core/Extension: E 5454 Global Local Status: G 5455 M/O/D: O 5456 Multiple Values Allowed: N 5457 Neutral/Relationship Dependant: T.P.Neutral 5458 Product Hierarchy Reference Level: All 5459 Common value to all product hierarchy: Yes 5460 Type: Multi Measurement Value 5461 Size: Decimal 15, String 3 for Unit Of Measure 5462

5463 Definition: The minimum temperature at which the trade item can be 5464 stored. This uses a measurement consisting of a unit of measure and a 5465 value. 5466

5467 Examples: "-30 C" or degrees F, value 5468

5469 Business Rules: When no other information is provided (temperatures to 5470 market or/and distribution center), this value applies at any point of the 5471 supply chain. Temperature information is important for fresh trade item, 5472 dangerous goods and other trade items for which certain temperature 5473 limits are necessary for quality or safety reasons. Has to be associated 5474 with a valid UoM. See Section 4.6 of the Implementation Considerations 5475 and Concerns for more details of UoM. 5476

5477 5478

Class Name: TradeItemUnitIndicator 5479 5480 Item Name: isTradeItemABaseUnit 5481 5482

Core/Extension: E 5483 Global Local Status: G 5484 M/O/D: M 5485 Multiple Values Allowed: N 5486 Neutral/Relationship Dependant: T.P.Neutral 5487 Product Hierarchy Reference Level: All 5488 Common value to all product hierarchy: No 5489 Type: Boolean 5490 Size: Not Applicable 5491

5492 Definition: An indicator identifying the trade item as the base unit level of 5493 the trade item hierarchy. This is a (Boolean) where y indicates the trade 5494 item is a base unit. 5495

5496 Examples: A bundle pack of product is composed of packages without 5497 GTINs that cannot be sold individually. This bundle pack would then be a 5498

Page 122: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 121 of 195

base item. If that same bundle pack contained individual packages that 5499 have a GTIN + could be individually sold it would not 5500

5501 Business Rules: 5502 5503 5504

Class Name: TradeItemUnitIndicator 5505 5506 Item Name: isTradeItemAConsumerUnit 5507 5508

Core/Extension: E 5509 Global Local Status: G 5510 M/O/D: M 5511 Multiple Values Allowed: N 5512 Neutral/Relationship Dependant: T.P.Neutral 5513 Product Hierarchy Reference Level: All 5514 Common value to all product hierarchy: No 5515 Type: Boolean 5516 Size: Not Applicable 5517

5518 Definition: Identifies whether the current hierarchy level of a trade item is 5519 intended for a ultimate consumption. For retail, this trade item will be 5520 scanned at point of sale. At retail, this data is commonly used to select 5521 which GTINs should be used for shelf planning and for front end POS 5522 databases. This value reflects the intention of the Information Provider 5523 which may not necessarily be the intention of the retailer. 5524

5525 Examples: A multi-pack of paper towels and the individual paper towels 5526 contained in the multi-pack are both identified as a consumer unit. 5527

5528 Business Rules: There can be more than one consumer unit in one 5529 hierarchy 5530 5531

5532 Class Name: TradeItemUnitIndicator 5533 5534 Item Name: isTradeItemADespatchUnit 5535 5536

Core/Extension: E 5537 Global Local Status: G/L 5538 M/O/D: M 5539 Multiple Values Allowed: N 5540 Neutral/Relationship Dependant:T.P.Dependent 5541 Product Hierarchy Reference Level: All 5542 Common value to all product hierarchy: No 5543 Type: Boolean 5544 Size: Not Applicable 5545

5546 Definition: An indicator identifying that the information provider considers 5547 the trade item as a dispatch (shipping) unit. This may be Trading Partner 5548

Page 123: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 122 of 195

dependent based on channel of trade or other point to point agreement. 5549 This is y/n (Boolean) where y indicates the trade item is a dispatch unit.. 5550

5551 Examples: - 5552

5553 Business Rules: There can be more than one logistic unit in one 5554 hierarchy 5555 5556

5557 Class Name: TradeItemUnitIndicator 5558 5559 Item Name: isTradeItemAnInvoiceUnit 5560 5561

Core/Extension: E 5562 Global Local Status: G/L 5563 M/O/D: M 5564 Multiple Values Allowed: N 5565 Neutral/Relationship Dependant:T.P.Dependent 5566 Product Hierarchy Reference Level: All 5567 Common value to all product hierarchy: No 5568 Type: Boolean 5569 Size: Not Applicable 5570

5571 Definition: An indicator identifying that the information provider will 5572 include this trade item on their billing or invoice. This may be Trading 5573 Partner dependent based on channel of trade or other point to point 5574 agreement. This is y/n (Boolean) where y indicates the trade item is an 5575 invoicing unit. 5576

5577 Examples: - 5578

5579 Business Rules: There can be more than one invoicing unit in one 5580 hierarchy 5581

5582 5583 Class Name: TradeItemUnitIndicator 5584 5585 Item Name: isTradeItemAnOrderableUnit 5586 5587

Core/Extension: E 5588 Global Local Status: G/L 5589 M/O/D: M 5590 Multiple Values Allowed: N 5591 Neutral/Relationship Dependant:T.P.Dependent 5592 Product Hierarchy Reference Level: All 5593 Common value to all product hierarchy: No 5594 Type: Boolean 5595 Size: Not Applicable 5596

5597

Page 124: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 123 of 195

Definition: An indicator identifying that the information provider considers 5598 this trade item to be at a hierarchy level where they will accept orders 5599 from customers. This may be different from what the information provider 5600 identifies as a despatch unit. This may be relationship dependent based 5601 on channel of trade or other point to point agreement. This is y/n 5602 (Boolean) where y indicates the trade item is an ordering unit 5603

5604 Examples: 5605

5606 Business Rules: There can be more than one ordering unit in one 5607 hierarchy 5608

5609 5610 Class Name: TradeItemUnitIndicator 5611 5612 Item Name: isTradeItemAVariableUnit 5613 5614

Core/Extension: E 5615 Global Local Status: G 5616 M/O/D: M 5617 Multiple Values Allowed: N 5618 Neutral/Relationship Dependant: T.P.Neutral 5619 Product Hierarchy Reference Level: All 5620 Common value to all product hierarchy: No 5621 Type: Boolean 5622 Size: Not Applicable 5623

5624 Definition: Indicates that an article is not a fixed quantity, but that the 5625 quantity is variable. Can be weight, length, volume. trade item is used or 5626 traded in continuous rather than discrete quantities. 5627

5628 Examples: Wheel of Cheese: The weight is about 25 kilograms, but it 5629 can be 24 kilogram or 27 kilogram. 5630

5631 Business Rules: Boolean Yes=variable, No=fixed. Applies to EAN.UCC 5632 bricks: Meat, Cheese, Fruits, Dairy trade item. 5633 5634

5635 Class Name: TradeItemUnitIndicator 5636 5637 Item Name: priceByMeasureType 5638 5639

Core/Extension: E 5640 Global Local Status: G/L 5641 M/O/D: O 5642 Multiple Values Allowed: N 5643 Neutral/Relationship Dependant:T.P.Dependent 5644 Product Hierarchy Reference Level: All 5645 Common value to all product hierarchy: No 5646 Type: Enumerated List 5647

Page 125: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 124 of 195

Size: Not Applicable 5648 5649

Definition: Indicator to show how a product is sold. 5650 5651 Examples: 5652

5653 Business Rules: 5654 5655 5656

Class Name: TradeItemUnitIndicator 5657 5658 Item Name: variableTradeItemType: 5659 5660

Core/Extension: E 5661 Global Local Status: G/L 5662 M/O/D: O 5663 Multiple Values Allowed: N 5664 Neutral/Relationship Dependant:T.P.Dependent 5665 Product Hierarchy Reference Level: All 5666 Common value to all product hierarchy: No 5667 Type: Enumerated List 5668 Size: Not Applicable 5669

5670 Definition: Indicator to show if a product is loose or pre-packed. 5671 5672 Examples: Wheel of Cheese: The weight is about 25 kilograms, but it 5673 can be 24 kilogram or 27 kilogram. 5674

5675 Business Rules: 5676 5677 5678

Page 126: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 125 of 195

5679 3.7 TRADE ITEM TAX INFORMATION: 5680

5681 Class Name: TaxAgency 5682 5683 Item Name: taxAgencyCode 5684 5685

Core/Extension: E 5686 Global Local Status: G/L 5687 M/O/D: O 5688 Multiple Values Allowed: N 5689 Neutral/Relationship Dependant: T.P.Neutral 5690 Product Hierarchy Reference Level: All 5691 Common value to all product hierarchy: No 5692 Type: AN 5693 Size: ..3 5694

5695 Definition: Identifies the agency responsible for the tax code list 5696

5697 Examples: X1 = BE, ICODIF/EAN Belgium - Luxembourg 5698

5699 Business Rules: 5700

5701 5702 Class Name: TaxAgency 5703 5704 Item Name: taxTypeCode 5705 5706

Core/Extension: E 5707 Global Local Status: G/L 5708 M/O/D: O 5709 Multiple Values Allowed: N 5710 Neutral/Relationship Dependant: T.P.Neutral 5711 Product Hierarchy Reference Level: All 5712 Common value to all product hierarchy: No 5713 Type: AN 5714 Size: 14 5715

5716 Definition: Identification of the type of duty or tax or fee applicable to the 5717 trade item. 5718

5719 Examples: "3001000002138" 5720

5721 Business Rules: This will vary by target market. Repeatable field inside 5722 each possible target market. 5723

5724

Page 127: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 126 of 195

Class Name: TaxAgency 5725 5726 Item Name: taxTypeDescription 5727 5728

Core/Extension: E 5729 Global Local Status: G/L 5730 M/O/D: O 5731 Multiple Values Allowed: N 5732 Neutral/Relationship Dependant: T.P.Neutral 5733 Product Hierarchy Reference Level: All 5734 Common value to all product hierarchy: No 5735 Type: AN 5736 Size: 35 5737

5738 Definition: Automatically generated text description of tax type code. 5739

5740 Examples: "Taxes sure les supports audio" 5741

5742 Business Rules: - 5743

5744 5745 Class Name: TradeItemTaxRate 5746 5747 Item Name: taxRate 5748 5749

Core/Extension: E 5750 Global Local Status: G/L 5751 M/O/D: O 5752 Multiple Values Allowed: Y 5753 Neutral/Relationship Dependant: T.P.Neutral 5754 Product Hierarchy Reference Level: All 5755 Common value to all product hierarchy: No 5756 Type: N 5757 Size: 3.2 5758

5759 Definition: The current tax or duty rate percentage applicable to the trade 5760 item. 5761

5762 Examples: - 5763

5764 Business Rules: This will vary by target market. taxRate and taxAmount 5765 are mutually exclusive for each tax type. Percentage is implicit. 5766

Page 128: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 127 of 195

5767 5768 Class Name: TradeItemTaxAmount 5769 5770 Item Name: taxAmount 5771 5772

Core/Extension: E 5773 Global Local Status: G/L 5774 M/O/D: O 5775 Multiple Values Allowed: Y 5776 Neutral/Relationship Dependant: T.P.Neutral 5777 Product Hierarchy Reference Level: All 5778 Common value to all product hierarchy: No 5779 Type: Amount 5780 Size: 13.4 5781

5782 Definition: The current tax or duty or fee amount applicable to the trade 5783 item. 5784

5785 Examples: Value – “ USD 1.06”, "EUR 36" 5786

5787 Business Rules: As monetary amount field, this data element is must be 5788 associated with a valid unit of measure. taxRate and taxAmount are 5789 mutually exclusive for each tax type. 5790

5791 5792 5793

Page 129: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 128 of 195

5794 3.8 FMCG (Fast Moving Consumer Goods) – INDUSTRY SPECIFIC: 5795

5796 5797 Class Name: FMCGTradeItemMarking 5798 5799 Item Name: isIngredientIrradiated 5800 5801

Core/Extension: E 5802 Global Local Status: G/L 5803 M/O/D: M 5804 Multiple Values Allowed: N 5805 Neutral/Relationship Dependant: T.P.Neutral 5806 Product Hierarchy Reference Level: Each 5807 Common value to all product hierarchy: No 5808 Type: Boolean 5809 Size: Not Applicable 5810

5811 Definition: Indicates if radiation has been applied to a trade item’s 5812 ingredient. 5813

5814 Examples: 5815

5816 Business Rules: 5817 Note: This requirement is handled through the FMCG Extension. 5818 5819 Should only be submitted if a claim is made on the trade item. 5820

5821 5822 Class Name: FMCGTradeItemMarking 5823 5824 Item Name: isRawMaterialIrradiated 5825 5826

Core/Extension: E 5827 Global Local Status: G/L 5828 M/O/D: M 5829 Multiple Values Allowed: N 5830 Neutral/Relationship Dependant: T.P.Neutral 5831 Product Hierarchy Reference Level: Each 5832 Common value to all product hierarchy: No 5833 Type: Boolean 5834 Size: Not Applicable 5835

5836 Definition: Indicates if radiation has been applied to a trade item’s raw 5837 material. 5838

5839 Examples: 5840

5841 Business Rules: 5842 Note: This requirement is handled through the FMCG Extension. 5843 5844

Page 130: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 129 of 195

Should only be submitted if a claim is made on the trade item. This field is 5845 trade item specific, indicating that radium has been applied to the trade 5846 item. 5847 5848

5849 Class Name: FMCGTradeItemMarking 5850 5851 Item Name: isTradeItemGeneticallyModified 5852 5853

Core/Extension: E 5854 Global Local Status: G/L 5855 M/O/D: M 5856 Multiple Values Allowed: N 5857 Neutral/Relationship Dependant: T.P.Neutral 5858 Product Hierarchy Reference Level: Each 5859 Common value to all product hierarchy: No 5860 Type: Boolean 5861 Size: Not Applicable 5862

5863 Definition: Used to indicate whether trade item contains genetically 5864 modified contents. 5865

5866 Examples: See code list 5867

5868 Business Rules: 5869 Note: This requirement is handled through the FMCG Extension. 5870

5871 5872 Class Name: FMCGTradeItemMarking 5873 5874 Item Name: isTradeItemIrradiated 5875 5876

Core/Extension: E 5877 Global Local Status: G/L 5878 M/O/D: M 5879 Multiple Values Allowed: N 5880 Neutral/Relationship Dependant: T.P.Neutral 5881 Product Hierarchy Reference Level: Each 5882 Common value to all product hierarchy: No 5883 Type: Boolean 5884 Size: Not Applicable 5885

5886 Definition: Indicates if radiation has been applied to an trade item. 5887

5888 Examples: 5889

5890 Business Rules: 5891 5892 Note: This requirement is handled through the FMCG Extension. 5893

Page 131: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 130 of 195

Should only be submitted if a claim is made on the trade item. This field 5894 is trade item specific, indicating that radium has been applied to the trade 5895 item. 5896

5897 5898 Class Name: FMCGTradeItemMeasurements 5899 5900 Item Name: degreeOfOriginalWort 5901 5902

Core/Extension: E 5903 Global Local Status: L 5904 M/O/D: O 5905 Multiple Values Allowed: N 5906 Neutral/Relationship Dependant: T.P.Neutral 5907 Product Hierarchy Reference Level: All 5908 Common value to all product hierarchy: No 5909 Type: Char 5910 Size: 3 5911

5912 Definition: Specification of the degrees of original wort. 5913

5914 Examples: The beer degree for the allocation of different original wort 5915 proportions in different kinds of beer to the respective beer tax group and 5916 beer tax rate. 5917

5918 Business Rules: 5919 Note: This requirement is handled through the FMCG Extension. 5920 5921 Sector specific extension (alcoholic beverages) Local legal requirement 5922 (Austria) 5923

5924 5925

Class Name: FMCGTradeItemMeasurements 5926 5927 Item Name: fatPercentageInDryMatter 5928 5929

Core/Extension: E 5930 Global Local Status: G 5931 M/O/D: O 5932 Multiple Values Allowed: N 5933 Neutral/Relationship Dependant: T.P.Neutral 5934 Product Hierarchy Reference Level: Each 5935 Common value to all product hierarchy: No 5936 Type: Percentage 5937 Size: 3.2 5938

5939

Definition: The amount of fat contained in the base product expressed 5940 in percentage. 5941

5942

Page 132: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 131 of 195

Examples: ‘10’ 5943 5944

Business Rules: 5945 Note: This requirement is handled through the FMCG Extension. 5946 5947 Mainly concerns cheese and dairy trade items. Percentage is implicit. 5948

5949 5950 Class Name: FMCGTradeItemMeasurements 5951 5952 Item Name: percentageOfAlcoholByVolume 5953 5954

Core/Extension: E 5955 Global Local Status: G 5956 M/O/D: O 5957 Multiple Values Allowed: N 5958 Neutral/Relationship Dependant: T.P.Neutral 5959 Product Hierarchy Reference Level: Each 5960 Common value to all product hierarchy: No 5961 Type: N 5962 Size: 3.2 5963

5964 Definition: Percentage of alcohol contained in the base unit trade item. 5965

5966 Examples: ‘12’ 5967

5968 Business Rules: 5969 Note: This requirement is handled through the FMCG Extension. 5970 5971 Sector specific extension. Percentage is implicit 5972 5973 5974

Page 133: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 132 of 195

4.0 Implementation Considerations and Concerns 5975 5976 This section includes Best Practices and Examples explaining how to best use this data 5977 model. It also includes implementation guides for a variety of the more complicated 5978 issues encountered when designing the standards outlined by this document. It also 5979 provides an overal review of the basic precepts used when developing this data model. 5980 5981 Basic precepts of this data model: 5982 5983

a) This model was designed with the intent of providing all industries with a generic 5984 template with which to build their own data model. EAN.UCC currently has 5985 identified 23 different industries which participate in its standards development 5986 and application processes. While it is recognized that each industry has different 5987 needs, this model attempts to provide a flexible data model framework, which 5988 covers what is common accross industries and upon which these industries can 5989 append their own unique needs. 5990

b) The data model assumes a base level of business transactions and agreements 5991 between buyer and seller, which then lead to an exchange of information 5992 deemed to be necessary for conducting normal business transactions. This set of 5993 information is herein called a data dictionary. 5994

c) This model was developed with the understanding that there are three different 5995 types of attributes, as type relates to industry: 5996

a. Core – these attributes are absolutely necessary to facilitate the accurate 5997 sharing of data sets between parties of all industries. The combination of 5998 these five attributes guarantees the uniqueness of that data set. The 5999 definition and use of these attributes is common to all industries. In this 6000 data model, the five core attributes are: GTIN of the trade item, the GLN 6001 of the information provider, the target market in which this data set is 6002 valid, a EAN.UCC external classification value, and a system generated 6003 product description (see below) 6004 Product identification as a process is mandatory. A GTIN must be used. 6005 Party identification as a process is mandatory. A GLN must be used. 6006

6007 b. Extension – these attributes are shared among several industries. The 6008

definition for each attribute is agreed to by all industries. The 6009 determination of whether these attributes are mandatory or optional is 6010 made based on the business need of each industry. It is important to 6011 share the responsibility for maintenance of these attributes and to 6012 maintain a common definition across industries since the buyer receiving 6013 data may receive it from multiple industries. Where industries use an 6014 attribute in different ways, a new attribute must be developed. (e.g. size) 6015 In addition to mandatory/optional, when industries build their own data 6016 models from this generic base, they may also choose to change the other 6017 conditions attached to each attribute as it is relevant to their industry. 6018 6019

c. Industry specific extension – these attributes are such that they are only 6020 relevant to one industry. The definition of these values is determined by 6021 this industry. If a buyer or seller does not deal in this trade item class, it is 6022 not expected that they build attributes related to this industry into their 6023

Page 134: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 133 of 195

Extension

FMCG Extension

General Merchandise Extension Currently 23

EAN.UCC Sectors identified

Food Service Extension

Core GTIN, GLN

Target Market EAN.UCC Product

Classification, Product Description

Transactional Extension e.g. for CPFR

data model. (e.g. degree of wort is specifically relevant to the beer 6024 industry) 6025

6026 Application notes – The complete data model for an industry is made up of a 6027 combination of these three types of attributes. It is expected that attributes may 6028 be added or deleted from the model in the future.Also, as more industries 6029 become involved in the EAN.UCC GSMP process, it is expected that more 6030 industry specific extensions will be created. 6031 6032 In most cases, the agreement reached by the two parties that will be 6033 communicating data will include only a portion of the data model. This is because 6034 this model is designed to capture all possible business needs of the industry. In 6035 many cases, the buyer will only require a subset of these attributes in order to 6036 conduct business in the manner that they are accustomed. 6037 6038

6039 6040

6041 6042 6043 6044

Page 135: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 134 of 195

6045 Key data attributes 6046

6047 This data model works off a basic principle. The entire set of data attributes assigned to 6048 a GTIN may vary depending on who provides the information, and in which target market 6049 the data is relevant. 6050

6051 Within the global data synchronization environment, the combination of three key 6052 attributes, GLN of information provider, GTIN of the trade item, and the Target Market 6053 identifies a unique set of values for the trade items’ attributes. This combination can also 6054 affect which attributes are communicated. The values of attributes can vary for a GTIN 6055 when GLN of information provider or Target market are changed. 6056

6057 Example – “orderingLeadTime” may vary depending on target market. (US delivery 6058 within 3 days, delivery within Belgium is less than 1 day) 6059 Example – “cataloguePrice” may vary depending on the information provider (catalogue 6060 price equals $1.00 from manufacturer, but is $1.05 in the information set communicated 6061 by a distributor) 6062

6063 All variation must be compliant with GTIN allocation rules per the General EAN.UCC 6064 Specifications. Variations that do not comply will require a new GTIN. 6065

6066 As stated above, in addition possible variations in values for the same attribute, the list 6067 of attributes communicated may change based on these three keys. Changes in the 6068 information provider can change the list of attributes associated with a GTIN. 6069 Example – Information provider A chooses to provide values for 50 attributes for a GTIN, 6070 while information provider B chooses to provide values for 100, seeing this as a 6071 competitive advantage. 6072

6073 The relevant target market can also affect the selection of attributes. Certain target 6074 markets will have legal requirements for some attributes, while other target markets will 6075 not. 6076 6077 Example – “dangerous goods” attributes are currently required in certain countries. 6078 Parties that do not operate in these countries will not be required to communicate these 6079 attributes to their customers. 6080

6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096

Page 136: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 135 of 195

6097 6098

6099 6100

6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121

6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133

4.1 Product hierarchy 6134 6135 There has been a long running debate within the EAN.UCC item project team regarding 6136 the application of a principle which states that if information about a product hierarchy is 6137 to be communicated, it is required that a GTIN be allotted to that level and the 6138 information only be attached to that GTIN. At the time this document was being 6139 finalized, this debate was still taking place. It is the intent of the Item group to present to 6140 the Align Data BRG a paper describing the current industry practices as they relate to 6141 hierarchy with the proper industry endorsement and representation . 6142 6143 This model is designed in conjunction with a widely accepted view of product 6144 containment hierarchy found in the commercial products industries. Attached is a chart 6145 describing the currently accepted definitions and guidelines for this hierarchy 6146 6147 GTIN Hierarchy 6148

6149 Preface 6150 • Eight discreet “levels” of GTIN Hierarchy have been identified. 6151

Extension

Core

Master Data

Neutral Neutral

+ Relationship dependant

Page 137: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 136 of 195

• “tradeItemUnitDescriptor has been used as the field to describe the GTIN 6152 hierarchy level. 6153

6154 • Implementation with any level of automation will require the programs to map 6155

discreetly from each of these GTIN hierarchy layers. Each attribute has the 6156 potential for a different meaning depending on which layer it’s attached to. Each 6157 attribute may also vary in cardinality or condition depending on the ‘product type 6158 name’ of the GTIN. 6159

• The following guidelines have been created, debated, practiced, reviewed, and 6160 endorsed by the UCCnet community over the last 3 years. The Guidelines Task 6161 Group, represented by over 60 individuals and participating companies has 6162 endorsed these Guidelines. 6163 6164 o (MX) Mixed Mod: A “mixed mod” or “display ready pallet” that is not the 6165

normal ‘turn’ for ordering. May NOT have any parents. May have children 6166 (DS, CA, PK, EA) in multiple instances. Orderable: True / ConsumerUnit: 6167 False. 6168

6169 o (PL) Pallet: A pallet of turn product. May NOT have any parents. May have 6170

children (DS, CA, PK, EA) in a single instance. Orderable: True or False / 6171 ConsumerUnit: False. 6172

6173 o (DS) Display / Shipper: A display, a shipper. May have a “PL” parent. May 6174

have (CA or EA) children in multiple instances. Orderable: True / 6175 ConsumerUnit: True or False. 6176

6177 o (CA) Case: The standard shipping unit level. May be contained in one or 6178

more (PL, MX, or DS). May contain children (PK or EA) in a single instance. 6179 Orderable: True or False / Consumable: True or False. 6180

6181 o (PK) Pack / Innerpack: A logistical unit between case and each. This may 6182

be a consumable innerpack (i.e. Carton of Cigarettes) or it may be simply a 6183 logistical pack (i.e. Dozens of toothbrushes). Multiple instances of a (EA) 6184 child are allowed. Multiple instances of (DS or CA) parents are allowed. 6185 Orderable: true or False / ConsumerUnit: True or False. 6186

6187 o (EA) Each: The lowest level of the item hierarchy intended or labeled for 6188

individual retail sale. May not have any children. May have multiple 6189 instances of (PK, CA, DS, PL, or MX) parents. Orderable:True or False / 6190 ConsumerUnit:True. 6191

6192 o Prepack/Assortment: Contains multiple components, each of which 6193

represents a unique consumer unit item by color and size. Includes 6194 “prepacks” and “setpacks.” 6195

6196 Prepack: or standard assortment of trade items, each different 6197

item within the prepack will be assigned a GTIN maintaining the 6198 one-to-one relationship between trade item/color ID/size ID and 6199 GTIN. Each of the component GTINs is scannable at the Point-of-6200 Sale and may or may not be orderable separately outside of the 6201

Page 138: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 137 of 195

prepack. In addition, a separate, unique GTIN is assigned to each 6202 orderable prepack. This GTIN is not scanned by the retailer at the 6203 Point-of-Sale. For example, the NRF size code for the orderable 6204 prepack GTIN will be assigned in the 90001-91999 range, 6205 reserved for prepacks and setpacks. A valid NRF color code will 6206 be assigned to the GTIN when all trade items are of the same 6207 color in the prepack; otherwise, the NRF color code 999- assorted 6208 is assigned. The 90001-91999 size code assignment denotes 6209 prepacks whether the prepack is assorted by size only, color only, 6210 or both size and color. Different prepacks of trade items are 6211 assigned different GTINs when either the component item or 6212 quantity contents of the prepacks are different. 6213

6214 Setpack: each different trade item within the setpack will be 6215

assigned a GTIN, maintaining the one-to-one relationship between 6216 trade item/color ID/size ID and the GTIN. The individual trade item 6217 GTIN must be scannable at the Point-of-Sale and may or may not 6218 be orderable separately outside the setpack(s). A separate and 6219 unique GTIN is assigned to each setpack. This GTIN is also 6220 scannable at Point-of-Sale. For example, the NRF size code for 6221 the orderable setpack GTIN will be assigned in the 90001-91999 6222 range, reserved for prepacks and setpacks. A valid NRF color 6223 code will be assigned to the setpack GTIN when all trade items 6224 are of the same color in the setpack, otherwise the NRF color 6225 code 999-assorted is assigned. Different setpacks are assigned 6226 different GTINs when either the trade item or quantity contents are 6227 different. 6228

6229 o Multipack: is a group of trade items (the same or different) that are 6230

intended to be sold as a single consumer unit at the Point-of-Sale (e.g., a 6231 three-pack of men's white T-shirts or a 12-piece set of glassware). A 6232 multipack is not intended to be broken apart and sold as individual trade 6233 items. A multipack is assigned a GTIN that is different from the GTIN that 6234 may be assigned to the individual trade items. Generally components of a 6235 multipack are not marked with individual trade item GTINs. Each different 6236 multipack of the same trade items (e.g., three-pack socks versus six-pack 6237 socks) must have a different GTIN assigned. Each different multipack 6238 GTIN must also have its own trade item/color ID/size ID. 6239

6240 Note: The hierarchy levels Pre-pack/Assortment and Multipack are not included in the 6241 next table, as the discussions of hierarchy were not finalized.6242

Page 139: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 138 of 195

6243

Attributes in the data model are designed such that they can and are used to describe 6244 the same value for any product hierarchy level. “Height“ for example, means the height 6245 of a consumer unit, case or pallet, depending on the product type being described by the 6246 GTIN. See Examples in the tables below: 6247 6248

Product type Description Parents Parents

Instance Children Children Instance Orderable Consumable

(MX) Mixed Module

A “mixed mod” or “display ready

pallet” that is not the normal ‘turn’

for ordering

None N/A DS, CA, PK, EA Multiple True False

(PL) Pallet A pallet of turn product None N/A DS, CA, PK,

EA Single True or False False

(DS) Display/ Shipper

A display or shipper PL CA, EA Single/

Multiple True True or False

(CA) Case The standard shipping unit

level. PL, MX, DS Multiple PK, EA Single/

Multiple True or False True or False

(PK) Pack / Innerpack

A logistical unit between case and

each DS, CA Multiple EA Single/

Multiple True or False True or False

(EA) Each

The lowest level of the item hierarchy

intended or labeled for

individual resale

PK, CA, DS, PL, MX Multiple None N/A True or False True

Page 140: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 139 of 195

6249

Simple Product Description GTIN Next Lower Level

GTIN

Quantity Next Lower

Level GTINs

Quantity ofchildren (number of different GTIN)

Quantity

Pack Quantity in Each

Pallet (PL) 60 cases 00123456 33333c 00123456 22222c 60 1 60 X

Case (CA) 2 of Inner Packs

00123456 22222c 00123456 11111c 2 1 2 X

Inner Pack (PK)

1 Sleeve of 6 bottles (6 in total)

00123456 11111c X 6 1 6 X

Each (EA) 1 bottle of salad dressing

X X X X X 1

6250 X= Not applicable 6251 6252

Complex- Banded Description GTIN Next Lower Level

GTIN Quantity

Next Lower Level GTINs

Quantity of children

(number of different

GTIN)

Quantity Pack

Quantity in Each

Pallet (PL) 2 Cases 00123456 66666c 00123456 55555c 2 1 2 X

Case (CA) 4 Inner Packs 00123456 55555c 00123456 44444c 4 1 4 X

Inner Pack (PK)

1 Sleeve of 12 cases

00123456 44444c 00123456 33333c 12 1 12 X

Each (EA) 1 shampoo + 1 Conditioner Banded

00123456 33333c 00123456 22222c

00123456 11111c

1

2

1

2

2 3

Each A 1 Shampoo 00123456 22222c X X X X 1

Each B 1 Conditioner 00123456 11111c X X X X 1

6253 X= Not applicable 6254 6255 6256 6257 6258 6259

Page 141: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL

FOR TRADE ITEM (DATA DEFINITION)

COPYRIGHT 2005, GS1™ Version 7.7.1 Page 140 of 195

6260

Description GTIN Next Lower Level GTINQuantity of Next Lower Level

Quantity of Children Net Content

Pallet (PL)

20 Cases 00123456 77777c 00123456 66666c

Case (CA)

2 Sleeves (24) 00123456 66666c 00123456 55555c

Inner Pack (PK)

1 Sleeve (12) 00123456 55555c 00123456 44444c

Inner Pack (PK)

3 Eaches of 4 Pack Cookies

Chocolate Cookies

Raisin Cookies

Vanilla Cookies

00123456 44444c

00123456 33333c

00123456 22222c

00123456 11111c

1

1

1

3 9 ounces

3 count

Each A 4 pack

Cookies

00123456 33333c X X X 3 ounces

4 count

Each B 4 pack

Chips

00123456 22222c X X X 3 ounces

4 count

Each C 4 pack

Fig

00123456 11111c X X X 3 ounces

4 count

6261 X= Not applicable 6262

6263 6264 The next page shows a table which lists all the attributes contained in this data model 6265 and notes at which product hierarchy level they are relevant. 6266 6267

Page 142: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 141 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

isTradeItemABaseUnit M N M N M N M N M N M N isTradeItemAConsumerUnit M N M N M N M N M N M N isTradeItemADespatchUnit M N M N M N M N M N M N isTradeItemAnOrderableUnit M N M N M N M N M N M N isTradeItemAninvoiceUnit M N M N M N M N M N M N orderQuantityMultiple O N orderQuantityMinimum O N O N O N O N O N O N orderQuantityMaximum O N O N O N O N O N O N orderSizingFactor O N O N O N O N O N O N nameOfInformation Provider O Y O Y O Y O Y O Y O Y brandOwner O Y O Y O Y O Y O Y O Y nameOfBrandOwner O Y O Y O Y O Y O Y O Y partyReceivingPrivateData D Y D Y D Y D Y D Y D Y manufacturer O Y O Y O Y O Y O Y O Y nameOfManufacturer O Y O Y O Y O Y O Y O Y netContent D N isNetContentDeclarationIndicated O N height M N M N M N M N M N M N width M N M N M N M N M N M N depth M N M N M N M N M N M N

Attribute Association by Trade Item Hierarchy Level for Aligning Data

Page 143: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 142 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

grossWeight D N D N D N D N D N D N netWeight O N O N O N O N O N diameter O N drainedWeight O N effectiveDate M N M N M N M N M N M N lastChangeDateTime M N M N M N M N M N M N publicationDate M N M N M N M N M N M N startAvailabilityDateTime M N M N M N M N M N M N endAvailabilityDateTime O N O N O N O N O N O N consumerAvailibilityDateTime O N discontinuedDate O N O N O N O N O N O N canceledDate O N O N O N O N O N O N dangerousGoodsIndicator M N M N M N M N M N M N dangerousGoodsRegulationCode D N D N D N D N D N D N unitedNationsDangerousGoodsNumber D N D N D N D N D N D N dangerousGoodsShippingName D N D N D N D N D N D N dangerousGoodsTechnicalName D N D N D N D N D N D N dangerousGoodsPackingGroup D N D N D N D N D N D N dangerousGoodsHazardousCode D N D N D N D N D N D N dangerousGoodsAMarginNumber D N D N D N D N D N D N flashPointTemperature D N stackingWeightMaximum O N O N O N O N O N O N storageHandlingTemperatureMaximum O Y O Y O Y O Y O Y O Y storageHandlingTemperatureMinimum O Y O Y O Y O Y O Y O Y

Page 144: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 143 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

handlingInstructionsCode O N deliveryToMarketTemperatureMaximum O N deliveryToMarketTemperatureMinimum O N deliveryToDistributionCenterTemperatureMaximum O N deliveryToDistributionCenterTemperatureMinimum O N orderingLeadTime O N palletTypeCode O N quantityOfTradeItemsPerPallet O N O N O N O N O N O N quantityOfLayersPerPallet O N O N O N O N O N O N quantityOfTradeItemsPerPalletLayer O N O N O N O N O N O N palletTermsAndConditions O N tradeItemUnitDescriptor M N M N M N M N M N M N invoiceName O N O N O N O N O N O N tradeItemFormDescription O N productRange O N subBrand O Y functionalName M Y M Y M Y M Y M Y M Y descriptiveSize O Y O Y O Y O Y O Y O Y variant O N colorCodeValue O N colorDescription O N colorCodeListAgency O N isTradeItemInformationPrivate M Y M Y M Y M Y M Y M Y priceOnPackIndicator M N

Page 145: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 144 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

suggestedRetailPrice O N retailPriceOnTradeItem O N couponFamilyCode O N genericIngredient O N genericIngredientStrength O N hasBatchNumber O N isTradeItemGeneticallyModified O N isTradeItemIrradiated O N organicTradeItemCode O N organicClaimAgency O N isTradeItemAVariableUnit M N M N M N M N M N M N percentageOfAlcoholByVolume O N fatPercentageInDryMatter O N degreeOfOriginalWort O N O N O N O N O N O N isBarcodeOnThePackage M N M N M N M N M N M N isPackagingMarkedReturnable M N M N M N M N M N M N isPackagingMarkedWithExpirationDate O N minimumTradeItemLifespanFromTimeOfArrival O N countryOfOrigin O N packagingMarkedRecyclableScheme O N isNonSoldTradeItemReturnable O N taxTypeCode O N O N O N O N O N O N taxTypeDescription O N O N O N O N O N O N taxRate O N O N O N O N O N O N

Page 146: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 145 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

taxAmount O N O N O N O N O N O N taxAgencyCode O N O N O N O N O N O N targetMarketCountryCode O Y O Y O Y O Y O Y O Y targetMarketSubdivisionCode O Y O Y O Y O Y O Y O Y targetMarketDescription O Y O Y O Y O Y O Y O Y ingredientStrength O N sizeCodeValue O N sizeCodeListAgency O N cataloguePrice O N O N O N O N O N O N effectiveStartDate D N D N D N D N D N D N effectiveEndDate O N O N O N O N O N O N packagingTypeCode O N O N O N O N O N O N packagingTypeDescription O N O N O N O N O N O N pegHorizontal O N pegVertical O N quantityOfInnerPack O N O N O N O N O N O N quantityOfNextLevelTradeItemWithinInnerPack O N O N O N O N O N O N packagingMaterialCode O N O N O N O N O N O N packagingMaterialDescription D N D N D N D N D N D N packagingMaterialCompositionQuantity D N D N D N D N D N D N isPackagingMarkedWithIngredients O N quantityOfCompleteLayersContainedInATradeItem O N O N O N O N O N quantityOfTradeItemsContainedInACompleteLayer O N O N O N O N O N packagingMaterialCodeListMaintenanceAgency D A D A D A D A D A D A

Page 147: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 146 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

packagingMarkedRecyclableScheme M N M N M N M N M N M N materialSafetyDataSheet M N M N M N M N M N M N materialSafetyDataSheetNumber O N O N O N O N O N O N descriptionShort O N brandName M N tradeItemDescription M Y M Y M Y M Y M Y M Y informationProvider O Y O Y O Y O Y O Y O Y globalTradeItemNumber O N O N O N O N O N O N classificationCategoryCode O N classificationCategoryName O N classificationCategoryDefinition O N classificationAttributeTypeCode O N classificationttributeTypeName O N classificationAttributeTypeDefinition O N classificationAttributeValueCode O N classificationAttributeValueName O N additionalClassificationCategoryCode O N additionalClassificationCategoryDescription O N additionalClassificationAgencyName D N nextLowerLevelGtin M N M N M N M N M N M N quantityOfNextLowerLeveTradeItem M N M N M N M N M N M N

quantityOfChildren M N M N M N M N M N tradeItemGroupIdentificationCode O N tradeItemGroupIdentificationDescription D N

Page 148: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 147 of 195

Mixed Module (MX) Pallet (PL) Displays, Shippers or Mixed Cases (DS) Case (CS) Pack/InnerPack

(PK) Each (EA)

Resolved Item Name M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common M/O/D Status

Common

replacedTradeItemIdentification O N O N O N O N O N O N ISBN_NUMBER O N ISSN_NUMBER classOfDangerousGoods D N D N D N D N D N D N packagingTermsAndConditions barCodeType additionalTradeItemDescription totalQuantityOfNextLowerLevelTradeItem M N N M N N M M N stackingFactor

M/O/D Status Key Common Status Key M=Mandatory Y=Attribute value is the same O=Optional N=Attribute value can be different

D=Dependent

Page 149: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 148 of 195

Item Containment:

Refer to Class Diagram for Trade Item in the UML section where item hierarchy is handled. Item containment provides a method of identifying the contents of a GTIN that is a packaging hierarchy rather than a consumer unit. This can occur multiple times depending upon the number of levels in the hierarchy. All components of each potential level of packaging must already be defined in order to be used in Item Containment. Each level has to be identified with a product identifier and each level defines the containment (GTIN) of the next level. It is recommended that only GTINs be used in Item containment.

4.2 Product Classification The attribute structure for classification included in this document reflects the learnings from the work that the GCI Product Classification workgroup is conducting at this point in time and applies to the Food, Beverage and Tobacco (grocery) sector. Potential modifications to the codification structure may result in the inclusion in the Data Sync Trade Item model of additional attributes coming from other industry sectors (e.g. General Merchandise). These potential modifications will be considered after the EAN.UCC's final agreement on a global classification schema is announced.

Global EAN.UCC product classification – Examples At category level: classificationCategoryCode: 10000222 classificationCategoryName: Juice Drinks (Perishable) classificationCategoryDefinition: “Includes any products that can be described/observed as a perishable non carbonated beverage, that has some fruit or vegetable juice content but contain other ingredients such as water, sugar, colorings and flavorings. These products have been treated or packaged in such a way as to extend their consumable life. Includes products that may be described as Nectar, Fruit Drink or Juice Drink and available in single flavors such as carrot, tomato, orange, apple etc or they may be blends of more than one such as orange & apricot, cranberry & raspberry etc. Excludes products such as Frozen and Shelf Stable Juice Drinks, Juice, Syrups, Juice Concentrate, Flavored Mixers, Mineral Water.” At attribute type level: classificationAttributeTypeCode: 20000045 classificationAttributeTypeName:

Page 150: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 149 of 195

CONSUMER LIFESTAGE classificationAttributeTypeDefinition: "Indicates the broad period or stage (e.g. Adult, Child) in the consumer's life at which the product is considered to be suitable/appropriate for the intended consumer." At attribute value level: classificationAttributeValueCode classificationAttributeValueName 147 ADULT 167 ALL AGES 245 BABY 246 BABY & CHILD 644 CHILD 105 UNCLASSIFIED 106 UNIDENTIFIED N.B.: Only one possible attribute value per attribute type.

4.3 Product Orientation

Change Request (CR) 02-000102 was submitted to the EAN.UCC GSMP process and relates to how to measure the physical dimension of a product. At the July 10, 2002 conference call of the Align BRG, this Change Request was reviewed and the BRG agreed to forward to the Physical Technical Requirements Group (PTRG) for the definition of the physical requirements. This work is being developed by a subgroup of PTRG and will go through ballot cycles, which are estimated to conclude sometime in the first quarter of 2003. The work resulting from PTRG will go to the Align Data BRG which will determine the impact of the output on the Item work. Product orientation principles developed by the PTRG will affect the following attributes: width, depth, and height.

4.4 Language (Reference Appendix 13 and Appendix 17) EAN.UCC currently has the following classes related to Language. Description Class: it contains two attributes, one is language and the other is text. Text Description Class: it contains one or more Description Classes. It allows for multiple combinations of language and text Long Description Class: it contains two attributes, one is language and the other is long text. Long Text Description Class: it contains one or more Long Description Classes. It allows for multiple combinations of language and longtext. These classes allow users to fill in the language and the text. The language for the text is identified using a two character code from the ISO 639 language code list.

4.5 Currency (Reference Appendix 12)

Page 151: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 150 of 195

EAN.UCC currently has two classes related to Monetary Amount. One is Amount’ and the other is ’MonetaryAmount’. Monetary Amount allows for multiple currencies and value or Amount. Amount allows for one currency and value. These classes allow users to fill in the currency ISO Code and the value. The currency for the value is identified using a code from the ISO4217 currency code list. 4.6 Unit of Measure (Reference Appendix 14) The following describes how unit of measure is handled in the data model.

EAN.UCC currently has two classes related to measurement. One is 'Measurement class' and the other is 'Measurement Value'.

Measurement allows for multiple Measurement Values. Measurement Value allows for one Measurement Value.

These classes allow the users to fill in the unit of measure and the float (allows decimal value). Example: 100 degree Fahrenheit or 38 degree Celsius.

100°F is equal to: Unit Of Measure will be FAH and Float will be 100.00 38°C is equal to: Unit Of Measure will be CEL and Float will be 38.00

There was no need to create another attribute for unit of measure because it is fulfilled by the use of the Measurement class because the Measurement class is reused.

There is multiple and numerous possible unit of measures. The EAN.UCC system refers to the UN/Cefact #20 list for the possible unit of measure. The unit of measure is not broken down into categories of UOM such as "time UOM, Weight UOM, dimensional UOM, or net content UOM. Its a list of all the possible units of measure.

4.7 Product Description Product Description is one of the four attributes designated as being mandatory (within the Global Data Synchronization process) for uniquely identifying a set of data associated with a GTIN. The product description field which is considered core, “tradeItemDescription“ is automatically generated by the model from the four attributes listed below. If an attribute is left blank or not defined, the product description exists only of attributes populated. While two of the four attributes are designated as optional, since they may or may not exist, it is widely recognized that most information providers will seek to provide values for all of these attributes so as to provide a product description that is as accurate as possible. The Product Description attributes replaces the Item Description Long and Medium found in the previous GCI model.

The structure for the product description is:

Brand.......................................MANDATORY

Page 152: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 151 of 195

Sub Brand ...............................OPTIONAL Functional Name .....................MANDATORY Variant .....................................OPTIONAL

Examples:

ACME Regular Salad Dressing Italian ACME Regular Salad Dressing Ranch Seven Islands Reduced Cal Salad Dressing Ranch Seven Islands Reduced Cal Salad Dressing Italian Unbranded Plants Tropical Unbranded Plants Lily

For more accurate product description, several new attributes have been added to the model. These are in most cases optional.

productRange brandName subBrand functionalName (formerly known as Product Name) tradeItemFormDescription variant descriptive Size

Fields were included with the recognition that the great majority of categories have not yet had classification schemas deployed at the time of this document’s publication. 4.8 Code Lists 4.8.1 Code Lists This section presents the issues concerning code lists that users have identified in implementing the current EAN UCC Trade Item Data Synchronization Standards. It would be better for all communities to adopt one set of code lists now. The analysis that resulted in these code list recommendations took into account all definitions, examples, and business rules contained in the Trade Item BRD. Code lists from EANCOM, UNCEFACT, ISO, ANSI X12, VICS EDI, and UCS/WINS were also examined. The goal was to develop code lists that reflected the intent of the original developers of the Trade Item. Note these code lists are documentation only. It is envisioned these code list will be added to as new requirements are introduced. It is not an exclusive or all-inclusive list but this is a living list.

External Code Lists There are several code lists used within the EAN•UCC system that are maintained by agencies other than EAN•UCC. The code lists that are reference in this section apply to several attributes within the trade item as well as other business message standards. Language Code

Page 153: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 152 of 195

The Trade Item BMS restricts the use to just the two character language code as specified in ISO 639-1; these codes are lower case. ISO Code Lists The following ISO codes lists are used to represent languages (for text attributes), Country and Subdivision (for country of origin and target market), and currencies (for amounts), and the source for the code list.

EAN•UCC has three choices for code values: Reference an external source like ISO. Maintain a code list unique to the EAN•UCC system. Maintain a code list based on an external code list. Any code list EAN•UCC maintains will need to be accessible to the community and maintained in such a way as to be detached from the schema versioning. The end result is the code lists will be managed outside of the schemas in such a way to remain easy to update and allow for the syntax checking of code values as is done with enumerated lists.

Unit of Measure The Unit of Measure (UOM) code is used throughout the EAN•UCC System. In order to provide the best value to the EAN•UCC community the UOM code list will be maintained by EAN•UCC for its community. It is anticipated additional code values will be required. When the business requirements are defined additional code values can be added. The following is the starting point.

EEAANN••UUCCCC UUnniitt OOff MMeeaassuurreess

CCooddee CCooddee DDeessccrriippttiioonn

26 Actual Ton

Z51 Application (e.g. in hair colorant, 6 applications)

AS Assortment BG Bag BA Bale BI Bar BR Barrel

ISO 639-1

Codes for the representation of names of languages -- Part 1:Alpha-2 code 2002 Available from: http://www.iso.ch or http://www.loc.gov/standards/iso639-2/langcodes.html#ef See Code List Source Bibliography section of this document.

ISO 3166-1 Part 1 - Country Codes (Three Digit Format) Available from: http://www.iso.ch

ISO 3166-2 Part 2 - Alpha Country Subdivision Code Available from: http://www.iso.ch

ISO 4217 Codes for the representation of currencies and funds 2001 Available from: http://www.iso.ch

Page 154: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 153 of 195

EEAANN••UUCCCC UUnniitt OOff MMeeaassuurreess

CCooddee CCooddee DDeessccrriippttiioonn

BL Block B8 Board BF Board Feet BO Bottle BX Box BN Bulk BD Bundle BU Bushel CN Can CG Card

Page 155: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 154 of 195

EEAANN••UUCCCC UUnniitt OOff MMeeaassuurreess

CCooddee CCooddee DDeessccrriippttiioonn

CT Carton CQ Cartridge CA Case AF Centigram C3 Centiliter CM Centimeter 1N Count CV Cover CC Cubic Centimeter C8 Cubic Decimeter CF Cubic Feet CI Cubic Inches CR Cubic Meter CO Cubic Meters (Net)

MMQ Cubic Millimetre CU Cup DA Days DG Decigram DL Deciliter DM Decimeter CE Degrees Celsius (Centigrade) FA Degrees Fahrenheit DS Display DO Dollars, U.S. DZ Dozen DR Drum EA Each EV Envelope FT Feet UZ Fifty Count UY Fifty Square Feet FO Fluid Ounce GA Gallon GR Gram GT Gross Kilogram HD Half Dozen HC Hundred Count HL Hundred Feet CW Hundred Pounds (CWT) IN Inches

Page 156: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 155 of 195

EEAANN••UUCCCC UUnniitt OOff MMeeaassuurreess

CCooddee CCooddee DDeessccrriippttiioonn

JR Jar KE Keg KG Kilogram DK Kilometer KT Kit LR Layer(s) LF Linear Foot LM Linear Meter LK Link LT Liter MR Meter MP Metric Ton MC Microgram 4G Microliter ME Milligram ML Milliliter MM Millimeter MX Mod Pallet (Mixed) 58 Net Kilograms OZ Ounces PH Pack PK Package PA Pail PR Pair PL Pallet PY Peck, Dry U.S. P1 Percent PC Piece PT Pint

PTN Portion V2 Pouch LB Pounds PE Pounds Equivalent PG Pounds Gross PN Pounds Net QT Quart QS Quart, Dry RL Roll ST Set SH Sheet

Page 157: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 156 of 195

EEAANN••UUCCCC UUnniitt OOff MMeeaassuurreess

CCooddee CCooddee DDeessccrriippttiioonn

SX Shipment FJ Sizing Factor SF Square Foot SM Square Meter SY Square Yard 15 Stick TK Tank TM Thousand Feet TE Tote NT Trailer TY Tray

Z25 Usage (e.g. in laundry, 24 usage)

UN Unit YD Yard

Page 158: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 157 of 195

Additional Classification Agency Name Comments Attribute Name Code Code Description

Part of AdditionalClassification class. It is currently a string 1 to 35 Characters. This should be an EAN*UCC maintained code List. Values should be: 1 UDEX, LTD 2 IRI 3 AC Nielsen 4 ECCC Interim Class Codes

additionalClassificationAgencyName

5 UNSPSC – United Nations Standard Products and Services Code

6 UNSPSC - Electronic Commerce Code Management Association

Page 159: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 158 of 195

Color Code List Agency Comments Attribute Name Code Code Description

Part of TradeItemColorDescription class It is String 1 to 3 characters. This should be an EAN*UCC maintained code List. Values should be:

1

National Retail Federation – Standard Color & Size Codes This handbook provides guidelines for use in retailers' and vendors' merchandising and communications systems. http://www.nrf.com

2

PANTONE MATCHING SYSTEM The definitive international reference for selecting, specifying, matching and controlling ink colors. The PANTONE formula guide, a three-guide set consisting of 1,114 solid PANTONE Colors on coated, uncoated and matte stock, shows corresponding printing ink formulas for each color, and the three-book set of solid chips provides coated, uncoated and matte perforated tear-out chips that can be used for quality control. Pantone® Inc http://www.pantone.com

ColorCodeListAgency

3

PANTONE Process Color System® Provides a comprehensive palette of more than 3,000 colors achievable in four-color (CMYK) process printing. The PANTONE solid to process guide compares a solid PANTONE Color to the closest possible match in CMYK four-color process that can be achieved on a computer monitor, output device or printing press. Other PANTONE Color Reference Guides for the graphic arts include metallics, pastels, tints, duotones, film and foil. The PANTONE Hexachrome® Color System Pantone® Inc http://www.pantone.com

Page 160: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 159 of 195

Color Code List Agency Comments Attribute Name Code Code Description

colorCodeListAgency (continued)

4

The PANTONE Hexachrome® Color System A six-color ultra high quality printing process, reproduces a dynamic range of more brilliant continuous-tone images and simulates brighter, more vivid colors than standard four-color process printing Pantone® Inc http://www.pantone.com

5

PANTONE TEXTILE Color System® A vital tool for designers in the apparel, home furnishings and interior design industries for selecting and specifying color used in the manufacture of textiles and fashion. The System - consisting of 1,932 colors in cotton or paper format - is ideal for assembling creative palettes and conceptual color schemes, and for providing color communication and control in the manufacturing process. In January of 2001 Pantone Inc. included the NRF Color Codes into the PANTONE TEXTILE Color System. Pantone® Inc http://www.pantone.com

6 Assigned by Buyer

7 Assigned by Seller

Page 161: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 160 of 195

Size Code List Agency Comments Attribute Name Code Code Description

Part of TradeItemSizeDescription class It is String 1 to 3 characters. This should be an EAN*UCC maintained code List. Values should be

1

National Retail Federation – Standard Color & Size Codes This handbook provides guidelines for use in retailers' and vendors' merchandising and communications systems.

http://www.nrf.com 2 Assigned by Buyer

sizeCodeListAgency

3 Assigned by Seller

Page 162: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 161 of 195

Organic Trade Item Code Comments Attribute Name Code Code Description

Part of OrganicTradeItemCharacteristics class It is String 1 to 35 characters. This should be an EAN*UCC maintained code List. Values should be (as specified in the BRD)

1 100% Organic 2 Organic (at least 95% by

weight) 3 Made with organic ingredients

(at least 70% by weight) 4 Some organic ingredients (less

than 70% by weight) 5 Not Organic 6 In conversion (products

presently in conversion to the organic standard)

7 Bio Dynamic (a cousin to the organic system)

organicTradeItemCode

8 Disqualified (GTINs that violate organic principles, with attributes such as isTradeItemGeneticallyModified or isTradeItemIrradiated being true)

Page 163: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 162 of 195

Organic Claim Agency Comments Attribute Name Code Code Description

Part of OrganicTradeItemCharacteristics class It is String 1 to 35 characters. It is still not real clear what the usage or intended usage is. This should be an EAN*UCC maintained code List. Values should be

1 EPA – US Environmental Protection Agency

2 FSA – UK Food Standards Agency

3 FDA – US Food and Drug Agency

organicClaimAgency

4 International Foundation for Organic Agriculture

Page 164: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 163 of 195

Packaging Type Code Comments Attribute Name Code Code Description

Part of PackagingType class. It is String 1 to 3 characters. The BRD states “List of authorized code values based on UN-ECE 21 Recommendations”, however the attribute with code list table suggest a merger of ANSI DE 103 and EANCOM DE 7065. It would be a very large list to combine DE103 and DE7065 because DE103 is a two-part list. Recommend using ANSI DE 103 Part 1 – Packaging Form and making it a EAN UCC maintained code list. This seems to be more in-line with the intent of this attribute and packagingMaterialCode

AAA Pallet, Returnable

AAB

Splash Blend Splash blending is the mixing of two gasoline products, of different octane levels, in a tank on the delivery vehicle to produce a third blended grade of motor fuel for resale

AE Aerosol AMM Ammo Pack AMP Ampoule AT Atomizer

ATH

Attachment In containers and shipping devices, a component that can be added to provide additional functionality or security as required by the contents or method of transportation/handling

BAG Bag BAL Bale BBL Barrel

BRC

Bracing Material or devices used to hold articles or sections of loads in position to prevent shifting during transportation

BDG

Banding Something that binds, ties, or encircles the package/container to secure and maintain unit integrity

BDL Bundle BEM Beam BIC Bing Chest BIN Bin

packagingTypeCode

BLK Bulk

Page 165: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 164 of 195

Packaging Type Code

Comments Code Code Description

BLT

Belting As pertains to containers and shipping devices, a method of securing the contents to the conveyance device (or securing components of the shipping device to each other) using one or more bands of flexible material having high-tensile strength and a buckle or ratchet device for removing slack and maintaining tension

BME Blister Pack BOB Bobbin BOT Bottle BOX Box BRG Barge BSK Basket or hamper BXI Box, with inner container BXT Bucket CAB Cabinet CAG Cage CAN Can CNA Household Goods Container, Wood CAR Carrier CAS Case CBC Containers of Bulk Cargo CBY Carboy CCS Can Case CG Card

CHE Cheeses CHS Chest CLD Car Load, Rail CMS Clamshell

CNB Container, MAC-ISO, LT. WGT. 8x8x20 Foot Air

CNC Container, Navy Cargo Transporter CND Container, Commercial Highway Lift CNE Container, Engine

CNF Container, Multi-walled, Secured to Warehouse Pallet

CNT Container COL Coil CON Cones COR Core CRD Cradle

CRF

Corner Reinforcement Usually in boxes or crates, additional material or components attached to adjacent panels to add support or prevent crushing or separation

Page 166: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 165 of 195

Packaging Type Code

Comments Code Code Description CRT Crate CSK Cask CTN Carton

CX2 CONEX A reusable container for shipment of cargo

CU Cup CYL Cylinder DBK Dry Bulk DRK Double-length Rack DRM Drum DSK Double-length Skid DTB Double-length Tote Bin DUF Duffelbag

EGG

Egg Crating In containers and shipping devices, usually describes a type of interior dunnage which allows the contents to be individually segregated, horizontally and vertically, to provide protection during transportation and storage

ENV Envelope

EPR

Edge Protection A right-angle piece placed over the outermost perimeter edges of a container to distribute pressure and prevent collapse or cutting from banding, strapping, or handling

FIR Firkin FLO Flo-bin FRM Frame FSK Flask FWR Forward Reel HPR Hamper HPT Hopper Truck HRB On Hanger or Rack in Boxes HRK Half-Standard Rack HTB Half-Standard Tote Bin INT Intermediate Container JAR Jar KEG Keg KIT Kit KRK Knockdown Rack KTB Knockdown Tote Bin

Page 167: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 166 of 195

Packaging Type Code Comments

Code Code Description LAB Label Tag

LID

Lip/Top In packaging, the top or bottom of a container, usually the part that closes the opening; may also be known as cap, over, or top

LIF Lifts

LNR

Liners Any material that separates a product within a container from the basic walls of the container

LOG Log LSE Loose LUG Lug LVN Lift Van

MIX

Mixed Container Types More than one type of container is included in a shipment (shipment could consist of 3 pieces that include 1 box, 1 crate, and 1 basket)

ML2

MILVAN A military owned demountable container that conforms to US and international standards and operates in a centrally controlled fleet for movement of military cargo

MPE Multipack MRP Multi-Roll Pack

MS2

MSCVAN A commercial (leased) or Government-owned shipping container controlled by the Military Sealift Command.

MXD Mixed NOL Noil PA Packet

PAF Pallet – 4 Way A pallet that permits entry of handling equipment on each of its four sides

PAL Pail

PAT

Pallet - 2 Way A pallet that permits entry of handling equipment on opposing two of its four sides

PCK Packed - not otherwise specified PCS Pieces PIR Pirns PKG Package

Page 168: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 167 of 195

Packaging Type Code Comments

Code Code Description

PLC

Primary Lift Container The largest (outermost) unitized package or articles secured together that can be handled (usually mechanically) in common shop floor/warehouse applications as a single entity; "primary" indicates preferred or mandatory

PLF Platform PLN Pipeline PLT Pallet PO Pouch

POV Private Vehicle PRK Pipe Rack

PRT Partitioning The proceeds of applying separators or dividers

PUN Punnet PWT Plastic-Wrapped Tray RAL Rail (Semiconductor) RCK Rack REL Reel

RFT

Reinforcement In containers and shipping devices, a component (usually temporary) added to a container for a particular application to lend additional support under severe applications

ROL Roll RVR Reverse Reel SAK Sack SCS Suitcase SHK Shook

SHT

Sheet A thin layer of material usually used as a pad for extra protection by isolating/separating tiers or layers of parts within the package

SKD Skid

SKE Skid, elevating or lift truck

SLP

Slip Sheet Shipping containers utilizing slip sheets, which are cardboard platforms used to hold product for storage or transportation

SLV Sleeve SPI Spin Cylinders SPL Spool

Page 169: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 168 of 195

Packaging Type Code

Comments Code Code Description

SPR

Separator/Divider In packaging, any material inserted between tiers or layers of articles to prevent contact and provide protection

SRW

Shrink Wrap In packaging, a method of securing a unit load by placing a large "bag" of plastic film over the components and applying heat to induce shrinkage and cause the bag to tighten around the contents

STW

Stretch Wrap In packaging, a high-tensile plastic film, stretched and wrapped repeatedly around a unitized load to secure and maintain unit integrity

SV2

SEAVAN A commercial or government-owned (or leased) shipping container which is moved via ocean transportation without wheels attached and is lifted on and off a ship

TBE Tube TBN Tote Bin TKR Tank Car TKT Tank Truck TLD Intermodal Trailer/Container Load (Rail) TNK Tank TRC Tierce TRK Trunk and Chest TRU Truck TRY Tray TSS Trunk, Salesmen Sample TUB Tub UNP Unpacked UNT Unit UVQ Wrapped in Plastic VEH Vehicles VIL Vial VOC Vehicle in Operating Condition VPK Van Pack VP Vacuum Packed

WHE On Own Wheel WLC Wheeled Carrier WRP Wrapped

Page 170: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 169 of 195

Packaging Material Code

Packaging Material Code List Maintenance Agency Comments Attribute Name Code Code Description

packagingMaterialCode Part of PackagingMaterialType class. It is String 1 to 3 characters. The BRD states “Code source needs to be defined. Currently a EuropeanUnion table of code lists exists for this requirement”. However, it would seem that the packagingMaterialCodeListMaintenanceAgency would qualify this attribute since the agency code is required if this attribute is populated. The definition should read: “The code specifying the packaging material from the code list identified in packagingMaterialCodeListMaintenanceAgency. Part of PackagingMaterialType class. It is String 1 to 3 characters. This should be an EAN*UCC maintained code List. Values should be

1

UN/CEFACT – Recommendation 21 Codes for Passengers, Types of Cargo, Packages, and Packaging Material. Available at http://www.unece.org/cefact/

packagingMaterialCodeListMaintenanceAgency

E EAN UCC maintained Packaging Material code list. (see appendix for code list)

Page 171: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 170 of 195

Packaging Terms and Conditions Comments Attribute Name Code Code Description

Part of PackagingMaterialType class. It is String 1 to 3 characters. The BRD states authorized values based on EANCOM 7073, X12 DE102 and X12 DE399. The following list represents DE 7073 and DE399; DE102 does not apply. This should be an EAN*UCC maintained code List. Values should be:

1 Packaging cost paid by supplier The cost of packaging is paid by the supplier

2 Packaging cost paid by recipient. The cost of packaging is paid by the recipient

3 Packaging cost not charged (returnable) There is no charge for packaging because it is returnable.

4 Safe return deposit A deposit paid to guarantee the safe return of the package.

5

Not reusable The package is not reusable. The equipment may only be used once and is not reusable for the purpose for which it was designed

6

Package exchangeable at the point of delivery The package may be exchanged at the point of delivery.

7 Repack in Code identifying that goods should be repacked from the identified package.

8 Unpack from Code identifying that goods should be unpacked from the identified package.

9 Pack in Code identifying that goods should be packed from the identified package.

10 Rented The package has been/will be rented from a rental agency (e.g. CHEP pallets).

packagingTermsAndConditions

11 Labelled The package is labelled

Page 172: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 171 of 195

Pallet Type Code Comments Attribute Name Code Code Description

Part of TradeItemPalletInformation class. It is String 1 to 3 characters. The descriptions are from X12 DE883 and EANCOM DE7065. This should be an EAN*UCC maintained code List. Values should be

1 Soft Wood 2 Aluminum

3 As Specified by the Department of Transportation (DOT)

4 Hard Wood 5 Metal 6 Standard 7 Steel 8 Wood

9

Slip sheet Typically cardboard or plastic sheets used to hold product for storage or transportation

10 Pallet ISO 0 - 1/2 EURO Pallet Standard pallet with dimensions 80 X 60 cm.

11 Pallet ISO 1 - 1/1 EURO Pallet Standard pallet with dimensions 80 X 120 cm.

12 Pallet ISO 2 Standard pallet with dimensions 100 X 120 cm.

13 1/4 EURO Pallet Standard pallet with dimensions 60 X 40 cm.

14 1/8 EURO Pallet Standard pallet with dimensions 40 X 30 cm.

15

Synthetic pallet ISO 1 A standard pallet with standard dimensions 80*120cm made of a synthetic material for hygienic reasons.

16

Synthetic pallet ISO 2 A standard pallet with standard dimensions 100*120cm made of a synthetic material for hygienic reasons.

17 Wholesaler pallet Pallet provided by the wholesaler

18 Pallet 80 X 100 cm Pallet with dimensions 80 X 100 cm.

19 Pallet 60 X 100 cm Pallet with dimensions 60 X 100 cm.

20 Pallet, modular, collars 80cms * 100cms 21 Pallet, modular, collars 80cms * 120cms 22 CHEP Pallet 40 X 60 cm 23 CHEP Pallet 80 X 120 cm

palletTypeCode

24 CHEP Pallet 100 X 120 cm

Page 173: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 172 of 195

Comments Attribute Name Code Code Description

25 AS 4068-1993 Australian Pallet with dimension 115.5 X 116.5 cm

Pallet Terms and Conditions Comments Attribute Name Code Code Description

Part of TradeItemPalletInformation class. It is String 1 to 2 characters. List of authorized values based on EANCOM 7073, X12 DE102 and X12 DE399. This is the same code source referenced by packagingTermsAndConditions This should be an EAN*UCC maintained code list. It should be extended to 1 to 3 characters. Values should be

1 No Exchange / No Return Pallet 2 Exchange Pallets 3 Return Pallets 4 Pallets to be Purchased by Customer

5

Pallet – Third Party Exchange A pallet exchange program where a third party rents pallets for internal or external use.

6 One-way pallet Pallet need not be returned to the point of expedition.

palletTermsAndConditions

7 Returnable pallet Pallet must be returned to the point of expedition.

Page 174: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 173 of 195

EAN UCC Packaging Material Codes

Comments Attribute Name Code Code Description

The following is the two-character code list to be used with element packageMaterialCode when packageMaterialCodeListMaintenanceAgency contains a value of “E”.

01 Aluminium 03 Hard Wood 04 As Specified by the DOT 05 Soft Wood 07 Burlap 10 Chemically Hardened Fibre 13 Cloth 16 Cloth Top 19 Cloth or Fabric 22 Compressed 25 Corrugated or Solid 28 Double-wall Paper 31 Fibre 34 Fibre (Paperboard) 37 Fiberboard 40 Fiberboard Metal 43 Glass 46 In Inner Containers

48

Wire/Cord Something that binds, ties, or encircles the package/container to secure and maintain unit integrity

49 Insulated

50 Steel - Vinyl Coated Steel that has been covered with a plastic material

51 Wire Mesh 52 Iron or Steel 53 Jumbo 54 Special Jumbo 55 Lead 58 Metal 59 Metal Cans 61 Moisture Resistant 64 Molded Plastic 67 Multiple-wall Paper (2 or more walls) 70 Multiple-wall Paper (3 or more walls) 71 Not Otherwise Specified

packagingMaterialCode

72

Paper – VCI Water-resistant paper that is treated by the addition of materials to provide resistance to damage or deterioration by water in liquid form

73 Other than Glass 74 Other than Metal or Plastic Tubes, or Glass

Page 175: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 174 of 195

Comments Attribute Name Code Code Description

75

Plastic - Vacuum Formed Packaging material that is formed by heating plastic sheet and drawing it against the mold surface by evacuating the air between the sheet and the mold

76 Paper

77

Plastic - Structural Foam A method of manufacturing containers and shipping devices by mixing plastic resins with a foaming agent, heating it and injecting the mix into a two-piece machined aluminum mold

78

Plastic - Injection Molded Packaging material that is formed by melting the material and then forcing it under pressure into a cavity of a closed mold

79 Plastic 80 Polyethylene Lined

81

Plastic – Virgin Plastic in the form of pellets, granules, powder, floc, or liquid that has not been subjected to use or processing other than for its initial manufacture

82 Pulpboard

83

Plastic – Regrind A plastic prepared from discarded articles that have been reprocessed, often changing some of its original properties

84 Polystyrene A polymer prepared by the polymerization of styrene as the sole monomer

85 Rubber

86 Foam In packaging, a cushioning material used to reduce shock and vibration or abrasion

88 Rubber and Fabric 89 Special 90 Standard 91 Stainless Steel 92 Tubes, Metal or Plastic 94 Wood

95

Single Wall Corrugated Board The structure formed by one corrugated inner member between two flat facings; also known as double face

96 Double Wall Corrugated Board The structure formed by three flat facings and two intermediate corrugated members

97

Triple Wall Corrugated Board The structure formed by four flat facings and three intermediate corrugated members

Page 176: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 175 of 195

The table below lists all of the attributes whose values are contained in code lists. The Item team created a subgroup to handle the code lists. The work of the subgroup was based on the following:

- Identifying which data elements require a code list - When maintaining body or agency exists, refer to the body or agency - When required, define unique list of valid values, using existing lists or

documentation (E.g. EANCOM and X12) The subgroup’s objective was to keep the lists as short as possible, removing inconsistent, repeated, unclear or too generic values and also removing information handled through other data elements (E.g., Hazardous related information is handled by specific Des). The issue of governance and maintenance of these code lists is still being developed. Several of the code lists are maintained by outside agencies such as ISO. Other code lists are unique to this data model, and will need to be maintained by an EAN.UCC entity. The table enclosed in the following page represents the work of the group at the time this document was released for Align BRG’s approval. A separate and more complete Addendum may need to be added at a later time.

Class Name

Item Name

Code List

TargetMarketInformation targetMarketCountryCode Country Codes ISO3166-1

TargetMarketInformation targetMarketSubdivisionCode Country Subdivision Code ISO3166-2

TradeItemPriceDateInformation cataloguePrice Codes for the repres. of currencies and funds ISO 4217:2001

TradeItemPriceDateInformation suggestedRetailPrice Codes for the repres. of currencies and funds ISO 4217:2001

PriceOnTradeItem retailPriceOnTradeItem Codes for the repres.of agencies and codesISO 4217;2001

TradeItemClassification classificationCategoryCode Classification Attribute Type Code

EANUCCTradeItemClassification eANUCCClassificationAttributeTypeCode Classification Attribute Type Code

EANUCCTradeItemClassificationValue eANUCCClassificationAttributeValueCode Classification Attribute Value Code

ClassificationCategory additionalClassificationAgencyName Additional Classification Agency Name Reference 4.8.1

TradeItemDescriptionInformation invoiceName Codes for the representation of names of languages –Part 1: Alpha-2 code- ISO 639-1

Attributes with Code List

Page 177: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 176 of 195

Class Name

Item Name

Code List

TradeItemDescriptionInformation descriptionShort Codes for the representation of names of languages –Part 1: Alpha-2 code- ISO 639-1

TradeItemDescriptionInformation tradeItemFormDescription Codes for the representation of names of languages –Part 1: Alpha-2 code- ISO 639-1

TradeItemColorDescription tradeItemcolorDescription Codes for the representation of names of languages –Part 1: Alpha-2 code- ISO 639-1

TradeItemColorDescription colorCodeListAgency Color Code List Agency Reference 4.8.1

TradeItemSizeDescription sizeCodeListAgency Size Code List Agency Reference 4.8.1

TradeItemMeasurements ingredientStrength Measure Unit Qualifier-TBD

TradeItemMeasurements genericIngredientStrength Measure Unit Qualifier-TBD

TradeItemMarking hasBatchNumber Batch Lot Number Indicator Code-TBD

FMCGTradeItemMarking isTradeItemGeneticallyModified GeneticModificationIndicator-TBD

FMCGTradeItemMarking isTradeItemIrradiated Irradiated Item Code List - TBD

OrganicTradeItemCharacteristics organicTradeItemCode Organic Item Code Reference 4.8.1

TradeItemMeasurements height UN/CEFACT Recommendation 20

TradeItemMeasurements width UN/CEFACT Recommendation 20

TradeItemMeasurements depth UN/CEFACT Recommendation 20

TradeItemMeasurements grossWeight UN/CEFACT Recommendation 20

FMCGTradeItemMeasurements netWeight UN/CEFACT Recommendation 20

FMCGTradeItemMeasurements diameter UN/CEFACT Recommendation 20

FMCGTradeItemMeasurements drainedWeight UN/CEFACT Recommendation 20

PackagingType packagingTypeCode Packaging Type Code Reference 4.8.1

FMCGTradeItemMeasurements pegHorizontal Measure Unit Qualifier-TBD

FMCGTradeItemMeasurements pegVertical Measure Unit Qualifier-TBD

PackagingMaterial packagingMaterialCode Packaging Material Code List Maintenance Agency Reference 4.8.1

PackagingMaterial packagingMaterialCompositionQuantity Measure Unit Qualifier-TBD

PackagingMaterial packagingTermsAndConditions Packaging Terms and Conditions Reference 4.8.1

Page 178: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 177 of 195

Class Name

Item Name

Code List

TradeItemHandlingInformation stackingWeightMaximum UN/CEFACT Recommendation 20

TradeItemTemperatureInformation storageHandlingTemperatureMaximum UN/CEFACT Recommendation 20

TradeItemTemperatureInformation storageHandlingTemperatureMinimum UN/CEFACT Recommendation 20

TradeItemHandlingInformation handlingInstructionsCode Handling Instructions - TBD

TradeItemHandlingInformation minimumTradeItemLifespanFromTimeOfArrival Unit of Time Period - TBD

TradeItemTemperatureInformation deliveryToMarketTemperatureMaximum UN/CEFACT Recommendation 20

TradeItemTemperatureInformation deliveryToMarketTemperatureMinimum UN/CEFACT Recommendation 20

TradeItemTemperatureInformation deliveryToDistributionCenterTemperatureMaximum UN/CEFACT Recommendation 20

TradeItemTemperatureInformation deliveryToDistributionCenterTemperatureMinimum UN/CEFACT Recommendation 20

TradeItemOrderInformation orderingLeadTime Unit of Time Period - TBD

TradeItemCountryOfOrigin countryOfOrigin Country Codes ISO3166-1

TradeItemPalletInformation palletTypeCode Pallet Type Code Reference 4.8.1

TradeItemPalletInformation palletTermsAndConditions Pallet Terms and Condition Reference 4.8.1

TradeItemHazardousInformation dangerousGoodsRegulationCode Dangerous Goods Regulations - TBD

Packaging Material packagingMaterialCodeListMaintenanceAgency Household Packaging Recovery and Recycling Agencies

TradeItemHazardousInformation unitedNationsDangerousGoodsNumber UNDG Number -DE7124

TradeItemHazardousInformation classOfDangerousGoods UN -Class of Dangerous Goods

TradeItemHazardousInformation flashPointTemperature UN/CEFACT Recommendation 20

TradeItemDescriptionInformation productRange Codes for the representation of names of languages -- Part 1:Alpha-2 code -ISO 639-1

TradeItemDescriptionInformation functionalName Codes for the representation of names of languages -- Part 1:Alpha-2 code -ISO 639-1

TradeItemSizeDescription descriptiveSize Codes for the representation of names of languages -- Part 1:Alpha-2 code -ISO 639-1

TradeItemDescriptionInformation tradeItemDescription Codes for the representation of names of languages -- Part 1:Alpha-2 code -ISO 639-1

TradeItemDescriptionInformation variant Codes for the representation of names of languages -- Part 1:Alpha-2 code -ISO 639-1

Page 179: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 178 of 195

4.9 Relationship to Global Data Synchronization process The Data Sync Trade Item model was built keeping in mind the design of the data synchronization process being developed by the Data Sync Project Team under the Align Data BRG. The key principle that is carried over from that work is the assumption that when a trade item’s information is transmitted from an information provider to a data pool, and data pool to data pool (in network data synchronization) that the entire product hiearchy is transmitted. In the grocery industry, that product hiearchy will normally include item, case and pallet, and may also include other levels. A message detailing information about a trade item must include at least one consumable and one orderable unit. Included in this product hiearchy, it is understood that each link connecting the various levels is also considered to be a part of the message.

Page 180: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 179 of 195

Page 181: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 180 of 195

The following four Appendixes were incorporated for informational purposes. APPENDIX A – Attribute Variations Shows how do attributes vary (by Target Market, by Relationship) or how can attributes be repeated (Multiple Values Allowed). APPENDIX B – Attribute Association by Trade Item Hierarchy Level for Data Sync Shows the attribute association by each hierarchy level as it applies to Data Synchronization. APPENDIX C – Attributes Mandatory for Data Synchronization It is recognized that the attributes listed in this data model may be used for a ‘one-to-many’ global data synchronization process. In light of this use, the table in Appendix 3 lists which attributes are mandatory within this process. Please note, this does not mean that only mandatory attributes are communicated via data sync. All other attributes, marked as optional here, can also be included in messages. APPENDIX D – Version 7.2 Model Harmonization Summary Summary of harmonized models.

Page 182: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 181 of 195

Appendix A: Attribute Variations

Resolved Item Name

Multiple Values Allowed

Can vary by TarMarket i.e has status: N (GlobaY (Global/Local)(Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

additionalClassificationAgencyName Yes N (Global) T.P.Neutral

additionalClassificationCategoryCode Yes N (Global) T.P.Neutral

additionalClassificationCategoryDescription Yes N (Global) T.P.Neutral

additionalTradeItemDescription No Y (Global/Local) T.P.Neutral

agreedMaximumBuyingQuantity No Y (Global/Local) T.P.Neutral

agreedMinimumBuyingQuantity No Y (Global/Local) T.P.Neutral

barCodeType Yes N (Global) T.P.Neutral

brandName No N (Global) T.P.Neutral

brandOwner No N (Global) T.P.Neutral

campaignEndDate No N (Global) T.P.Neutral

campaignName No N (Global) T.P.Neutral

campaignStartDate No N (Global) T.P.Neutral

canceledDate No N (Global) T.P.Neutral

cataloguePrice No Y (Global/Local) T.P.Neutral

classComplianceRegulationCode Yes N (Global) T.P.Neutral

classOfDangerousGoods Yes N (Global) T.P.Neutral

colorCodeListAgency Yes N (Global) T.P.Neutral

colorCodeValue Yes N (Global) T.P.Neutral

colorDescription Yes N (Global) T.P.Neutral

consumerAvailibilityDateTime No Y (Global/Local) T.P.Neutral

couponFamilyCode No Y (Local) T.P.Neutral

dangerousGoodsAMarginNumber Yes Y (Local) T.P.Neutral

dangerousGoodsHazardousCode Yes N (Global) T.P.Neutral

dangerousGoodsIndicator No Y (Global/Local) T.P.Neutral

dangerousGoodsPackingGroup Yes N (Global) T.P.Neutral

dangerousGoodsRegulationCode Yes N (Global) T.P.Neutral

dangerousGoodsShippingName Yes N (Global) T.P.Neutral

dangerousGoodsTechnicalName Yes N (Global) T.P.Neutral

deliveryToDistributionCenterTemperatureMaximum No N (Global) T.P.Neutral

deliveryToDistributionCenterTemperatureMinimum No N (Global) T.P.Neutral

deliveryToMarketTemperatureMaximum No N (Global) T.P.Neutral

deliveryToMarketTemperatureMinimum No N (Global) T.P.Neutral depositValueEffectiveDate No Y (Global/Local) T.P.Neutral depositValueEndDate No Y (Global/Local) T.P.Neutral

depth No N (Global) T.P.Neutral

descriptionShort No N (Global) T.P.Neutral

descriptiveSize No N (Global) T.P.Neutral

descriptiveSizeDimension No N (Global) T.P.Neutral

diameter No N (Global) T.P.Neutral

Page 183: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 182 of 195

Resolved Item Name

Multiple Values Allowed

Can vary by Target Market i.e has status: N (Global), Y (Global/Local), Y (Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

discontinuedDate No Y (Global/Local) T.P.Neutral

drainedWeight No N (Global) T.P.Neutral

eANUCCClassificationAttributeTypeCode Yes N (Global) T.P.Neutral eANUCCClassificationAttributeTypeDefinition Yes N (Global) T.P.Neutral

eANUCCClassificationAttributeTypeName Yes N (Global) T.P.Neutral

eANUCCClassificationAttributeValueCode No N (Global) T.P.Neutral

eANUCCClassificationAttributeValueName No N (Global) T.P.Neutral

eANUCCClassificationCategoryCode No N (Global) T.P.Neutral

eANUCCClassificationCategoryDefinition No N (Global) T.P.Neutral

eANUCCClassificationCategoryName No N (Global) T.P.Neutral

effectiveDate No Y (Global/Local) T.P.Neutral

effectiveEndDate No Y (Global/Local) T.P.Neutral & T.P.Dependent

effectiveStartDate No Y (Global/Local) T.P.Neutral & T.P.Dependent

endAvailabilityDateTime No Y (Global/Local) T.P.Neutral & T.P.Dependent

endDateMaximumBuyingQuantity No Y (Global/Local) T.P.Neutral & T.P.Dependent

endDateMinimumBuyingQuantity No Y (Global/Local) T.P.Neutral & T.P.Dependent

endDateTimeOfExclusivity No Y (Global/Local) T.P.Neutral & T.P.Dependent

firstdeliverydatetime No Y (Global/Local) T.P.Neutral & T.P.Dependent

firstOrderDate No Y (Global/Local) T.P.Neutral & T.P.Dependent

firstShipDate No Y (Global/Local) T.P.Neutral & T.P.Dependent

flashPointTemperature Yes N (Global) T.P.Neutral

functionalName No N (Global) T.P.Neutral

genericIngredient No Y (Local) T.P.Neutral

genericIngredientStrength No Y (Local) T.P.Neutral

globalTradeItemNumber No N (Global) T.P.Neutral

goodsPickUpLeadTime No Y (Global/Local) T.P.Neutral

grossWeight No N (Global) T.P.Neutral

handlingInstructionsCode Yes N (Global) T.P.Neutral

hasBatchNumber No Y (Local) T.P.Neutral

height No N (Global) T.P.Neutral importClassificationType No Y (Local) T.P.Neutral importClassificationValue No Y (Local) T.P.Neutral

informationProvider No N (Global) T.P.Neutral

ingredientStrength No Y (Global/Local) T.P.Neutral

invoiceName No N (Global) T.P.Neutral

isBarcodeOnThePackage No N (Global) T.P.Neutral

Page 184: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 183 of 195

Resolved Item Name

Multiple Values Allowed

Can vary by Target Market i.e has status: N (Global), Y (Global/Local), Y (Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

isnetContentDeclarationIndicated No Y (Global/Local) T.P.Neutral

isNonSoldTradeItemReturnable No Y (Global/Local) T.P.Neutral

isPackagingMarkedReturnable No N (Global) T.P.Neutral

isPackagingMarkedWithIngredients No Y (Local) T.P.Neutral

isTradeItemABaseUnit No N (Global) T.P.Neutral

isTradeItemAConsumerUnit No N (Global) T.P.Neutral

isTradeItemADispatchUnit No Y (Global/Local) T.P.Dependent

isTradeItemAnInvoiceUnit No Y (Global/Local) T.P.Dependent

isTradeItemAnOrderableUnit No Y (Global/Local) T.P.Dependent

isTradeItemAVariableUnit No N (Global) T.P.Neutral

isTradeItemInformationPrivate No N (Global) T.P.Neutral

isTradeItemMarkedAsRecyclable No Y (Global/Local) T.P.Neutral

isTradeItemReorderable No Y (Global/Local) T.P.Neutral

isTradeItemSizedBasedPricing No Y (Global/Local) T.P.Neutral

lastChangeDateTime No N (Global) T.P.Neutral

lastOrderDate No Y (Global/Local) T.P.Neutral

lastShipDate No Y (Global/Local) T.P.Neutral

linktoexternaldescription No Y (Global/Local) T.P.Neutral

manufacturer Yes N (Global) T.P.Neutral

manufacturerpartnumber Yes Y (Global/Local) T.P.Neutral materialAgencyCode No N (Global) T.P.Neutral materialCode No N (Global) T.P.Neutral materialContent No N (Global) T.P.Neutral materialPercentage No N (Global) T.P.Neutral

materialSafetyDataSheet No N (Global) T.P.Neutral

materialSafetyDataSheetNumber No N (Global) T.P.Neutral

materialWeight No N (Global) T.P.Neutral

maximumBuyingQuantity No Y (Global/Local) T.P.Neutral minimumTradeItemLifespanFromTimeOfArrival No Y (Global/Local)

T.P.Neutral & T.P.Dependent

minimumTradeItemLifespanFromTimeOfProduction No Y (Global/Local)

T.P.Neutral & T.P.Dependent

nameOfBrandOwner No N (Global) T.P.Neutral

nameOfInformationProvider No N (Global) T.P.Neutral

nameOfManufacturer Yes N (Global) T.P.Neutral

netContent No N (Global) T.P.Neutral

netWeight No N (Global) T.P.Neutral

offerOnPack No N (Global) T.P.Neutral

orderingLeadTime No Y (Global/Local) T.P.Neutral

orderQuantityMaximum No Y (Global/Local) T.P.Dependent

orderQuantityMinimum No Y (Global/Local) T.P.Dependent

orderQuantityMultiple No Y (Global/Local) T.P.Neutral

Page 185: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 184 of 195

Resolved Item Name

Multiple Values Allowed

Can vary by Target Market i.e has status: N (Global), Y (Global/Local), Y (Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

orderSizingFactor No Y (Global/Local) T.P.Neutral

orderingUnitOfMeasure No Y (Global/Local) T.P.Neutral

organicClaimAgency Yes Y (Global/Local) T.P.Neutral

organicTradeItemCode No Y (Global/Local) T.P.Neutral packageMarksEnvironment Yes Y (Local) T.P.Neutral packageMarksDietAllergen Yes Y (Local) T.P.Neutral packageMarksFreeFrom Yes Y (Local) T.P.Neutral packageMarksEthical Yes Y (Local) T.P.Neutral

packagingMarkedExpirationDateType Yes Y (Local) T.P.Neutral

packagingMarkedRecyclableScheme No Y (Local) T.P.Neutral

packagingMaterialCodeListMaintenanceAgency Yes Y (Global/Local) T.P.Neutral

packagingMaterialCompositionQuantity Yes Y (Global/Local) T.P.Neutral

packagingMaterialDescription Yes Y (Global/Local) T.P.Neutral

packagingTermsAndConditions No N (Global) T.P.Neutral

packagingTypeCode Yes N (Global) T.P.Neutral

packagingTypeDescription Yes N (Global) T.P.Neutral

palletTermsAndConditions No Y (Global/Local) T.P.Neutral

palletTypeCode No Y (Global/Local) T.P.Neutral

partyReceivingPrivateData Yes N (Global) T.P.Dependent

pegHoleNumber Yes N (Global) T.P.Neutral

pegHorizontal No N (Global) T.P.Neutral

pegVertical No N (Global) T.P.Neutral priceByMeasureType No Y (Global/Local) T.P.Dependent priceComparisonContentType No Y (Global/Local) T.P.Neutral priceComparisonMeasurement No Y (Global/Local) T.P.Neutral

priceOnPackIndicator No N (Global) T.P.Neutral

productRange No N (Global) T.P.Neutral

publicationDate No Y (Global/Local) T.P.Neutral & T.P.Dependent

quantityOfChildren No N (Global) T.P.Neutral quantityOfCompleteLayersContainedInATradeItem No N (Global) T.P.Neutral

quantityOfInnerPack No N (Global) T.P.Neutral

quantityOfLayersPerPallet No N (Global) T.P.Neutral

quantityOfNextLevelTradeItemWithinInnerPack No N (Global) T.P.Neutral

quantityOfNextLowerLeverTradeItem Yes N (Global) T.P.Neutral quantityOfTradeItemsContainedInACompleteLayer No N (Global) T.P.Neutral

quantityOfTradeItemsPerPallet No N (Global) T.P.Neutral

quantityOfTradeItemsPerPalletLayer No N (Global) T.P.Neutral

replacedTradeItemIdentification No Y (Global/Local) T.P.Neutral

retailPriceOnTradeItem No N (Global) T.P.Neutral

Page 186: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 185 of 195

Resolved Item Name

Multiple Values Allowed

Can vary by Target Market i.e has status: N (Global), Y (Global/Local), Y (Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

returnablePackageDepositCode No Y (Global/Local) T.P.Neutral returnablePackageDepositAmount No Y (Global/Local) T.P.Neutral seasonCalendarYear Yes Y (Local) T.P.Neutral seasonParameter Yes Y (Local) T.P.Neutral seasonalAvailabilityEndDate No Y (Local) T.P.Neutral seasonalAvailabilityStartDate No Y (Local) T.P.Neutral seasonName Yes Y (Local) T.P.Neutral securityTagLocation No Y (Local) T.P.Neutral securityTagType No Y (Local) T.P.Neutral sellingUnitOfMeasure No Y (Global/Local) T.P.Neutral sizeCodeListAgency Yes N (Global) T.P.Neutral sizeCodeValue Yes N (Global) T.P.Neutral sizeDimension No N (Global) T.P.Neutral sizeGroup No N (Global) T.P.Neutral sizeSystem No N (Global) T.P.Neutral sizeType No N (Global) T.P.Neutral

specialItemCode Yes Y (Global/Local) T.P.Neutral stackingFactor No N (Global) T.P.Neutral stackingWeightMaximum No N (Global) T.P.Neutral startAvailabilityDateTime

No Y (Global/Local) T.P.Neutral & T.P.Dependent

startDateMinimumBuyingQuantity No Y (Global/Local) T.P.Neutral startDateMaximumBuyingQuantity No Y (Global/Local) T.P.Neutral storageHandlingHumidityMaximum No Y (Global/Local) T.P.Neutral storageHandlingHumidityMinimum No Y (Global/Local) T.P.Neutral storageHandlingTemperatureMaximum No N (Global) T.P.Neutral storageHandlingTemperatureMinimum No N (Global) T.P.Neutral subBrand No N (Global) T.P.Neutral suggestedRetailPrice No Y (Global/Local) T.P.Neutral targetConsumerAge No Y (Local) T.P.Neutral targetConsumerGender No Y (Local) T.P.Neutral targetMarketCountryCode Yes N (Global) T.P.Neutral targetMarketDescription Yes N (Global) T.P.Neutral targetMarketSubdivisionCode Yes N (Global) T.P.Neutral taxAgencyCode No Y (Global/Local) T.P.Neutral taxAmount Yes Y (Global/Local) T.P.Neutral taxRate Yes Y (Global/Local) T.P.Neutral taxTypeCode No Y (Global/Local) T.P.Neutral taxTypeDescription No Y (Global/Local) T.P.Neutral threadCount No N (Global) T.P.Neutral totalQuantityOfNextLowerLevelTradeItem No N (Global) T.P.Neutral

tradeItemCompositionWidth No N (Global) T.P.Neutral

tradeItemCountryOfAssembly Yes N (Global) T.P.Neutral

tradeItemCountryOfOrigin Yes N (Global) T.P.Neutral tradeItemDescription No N (Global) T.P.Neutral

Page 187: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 186 of 195

Resolved Item Name Multiple

Values Allowed

Can vary by Target Market i.e has status: N (Global), Y (Global/Local), Y (Local)

Is Trading Partner Dependent (T.P.Dependent) , Trading Partner Neutral (T.P.Neutral+F53) OR Both

tradeItemFeatureBenefit Yes N (Global) T.P.Neutral

tradeItemFinishDescription No N (Global) T.P.Neutral

tradeItemFormDescription Yes N (Global) T.P.Neutral

tradeItemGroupIdentificationCode No N (Global) T.P.Neutral

tradeItemGroupIdentificationDescription Yes N (Global) T.P.Neutral

tradeItemidentificationOfNextLowerLevelTradeItem

Yes N (Global) T.P.Neutral

tradeItemMarketingMessage No Y (Global/Local) T.P.Neutral tradeItemUnitDescriptor No N (Global) T.P.Neutral

unitedNationsDangerousGoodsNumber Yes N (Global) T.P.Neutral

variant Yes N (Global) T.P.Neutral

variableTradeItemType No Y (Global/Local) T.P.Neutral

width No N (Global) T.P.Neutral

Page 188: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 187 of 195

Page 189: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 188 of 195

APPENDIX B Attribute Association by Trade Item Hierarchy Level for Data Synchronization

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

isTradeItemABaseUnit M N M N M M N M N M N isTradeItemAConsumerUnit M N M N M M N M N M N isTradeItemADespatchUnit M N M N M M N M N M N isTradeItemAnOrderableUnit M N M N M M N M N M N isTradeItemAninvoiceUnit M N M N M M N M N M N orderQuantityMultiple O N orderQuantityMinimum O N O N O O N O N O N orderQuantityMaximum O N O N O O N O N O N orderSizingFactor O N O N O O N O N O N nameOfInformation Provider O Y O Y O O Y O Y O Y

Attribute Association by Trade Item Hierarchy Level for Data Sync globaltrade

Page 190: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 189 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

totalQuantityOfNextLowerLevelTradeIterm M N M N M M N M N brandOwner O Y O Y O O Y O Y O Y nameOfBrandOwner O Y O Y O O Y O Y O Y partyReceivingPrivateData D Y D Y D D Y D Y D Y manufacturer O Y O Y O O Y O Y O Y nameOfManufacturer O Y O Y O O Y O Y O Y netContent D N isNetContentDeclarationIndicated O N height M N M N M M N M N M N width M N M N M M N M N M N depth M N M N M M N M N M N grossWeight D N D N D D N D N D N netWeight O N O N O O N O N diameter O N drainedWeight O N effectiveDate M N M N M M N M N M N

Page 191: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 190 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

lastChangeDateTime M N M N M M N M N M N publicationDate M N M N M M N M N M N startAvailabilityDateTime M N M N M M N M N M N endAvailabilityDateTime O N O N O O N O N O N consumerAvailibilityDateTime O N discontinuedDate O N O N O O N O N O N canceledDate O N O N O O N O N O N dangerousGoodsIndicator M N M N M M N M N M N dangerousGoodsRegulationCode D N D N D D N D N D N unitedNationsDangerousGoodsNumber D N D N D D N D N D N dangerousGoodsShippingName D N D N D D N D N D N dangerousGoodsTechnicalName D N D N D D N D N D N dangerousGoodsPackingGroup D N D N D D N D N D N dangerousGoodsHazardousCode D N D N D D N D N D N dangerousGoodsAMarginNumber D N D N D D N D N D N flashPointTemperature D N

Page 192: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 191 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

stackingWeightMaximum O N O N O O N O N O N storageHandlingTemperatureMaximum O Y O Y O O Y O Y O Y storageHandlingTemperatureMinimum O Y O Y O O Y O Y O Y handlingInstructionsCode O N deliveryToMarketTemperatureMaximum O N deliveryToMarketTemperatureMinimum O N deliveryToDistributionCenterTemperatureMaximum O N deliveryToDistributionCenterTemperatureMinimum O N orderingLeadTime O N palletTypeCode O N quantityOfTradeItemsPerPallet O N O N O O N O N O N quantityOfLayersPerPallet O N O N O O N O N O N quantityOfTradeItemsPerPalletLayer O N O N O O N O N O N palletTermsAndConditions O N tradeItemUnitDescriptor M N M N M M N M N M N invoiceName O N O N O O N O N O N

Page 193: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 192 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

tradeItemFormDescription O N productRange O N subBrand O Y functionalName M Y M Y M M Y M Y M Y descriptiveSize O Y O Y O O Y O Y O Y variant O N colorCodeValue O N colorDescription O N colorCodeListAgency O N isTradeItemInformationPrivate M Y M Y M M Y M Y M Y priceOnPackIndicator M N suggestedRetailPrice O N retailPriceOnTradeItem O N couponFamilyCode O N genericIngredient O N genericIngredientStrength O N

Page 194: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 193 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

hasBatchNumber O N isTradeItemGeneticallyModified O N isTradeItemIrradiated O N organicTradeItemCode O N organicClaimAgency O N isTradeItemAVariableUnit M N M N M M N M N M N percentageOfAlcoholByVolume O N fatPercentageInDryMatter O N degreeOfOriginalWort O N O N O O N O N O N isBarcodeOnThePackage M N M N M M N M N M N isPackagingMarkedReturnable M N M N M M N M N M N isPackagingMarkedWithExpirationDate O N minimumTradeItemLifespanFromTimeOfArrival O N countryOfOrigin O N isTradeItemMarkedAsRecyclable O N isNonSoldTradeItemReturnable O N

Page 195: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 194 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

taxTypeCode O N O N O O N O N O N taxTypeDescription O N O N O O N O N O N taxRate O N O N O O N O N O N taxAmount O N O N O O N O N O N taxAgencyCode O N O N O O N O N O N targetMarketCountryCode O Y O Y O O Y O Y O Y targetMarketSubdivisionCode O Y O Y O O Y O Y O Y targetMarketDescription O Y O Y O O Y O Y O Y ingredientStrength O N sizeCodeValue O N sizeCodeListAgency O N cataloguePrice O N O N O O N O N O N effectiveStartDate D N D N D D N D N D N effectiveEndDate O N O N O O N O N O N packagingTypeCode O N O N O O N O N O N packagingTypeDescription O N O N O O N O N O N

Page 196: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 195 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

pegHorizontal O N pegVertical O N quantityOfInnerPack O N O N O O N O N O N quantityOfNextLevelTradeItemWithinInnerPack O N O N O O N O N O N isPackagingMarkedWithGreenDot O N packagingMaterialCode O N O N O O N O N O N packagingMaterialDescription D N D N D D N D N D N packagingMaterialCompositionQuantity D N D N D D N D N D N isPackagingMarkedWithIngredients O N

quantityOfCompleteLayersContainedInATradeItem N O N O O N O N quantityOfTradeItemsContainedInACompleteLayer O N O N O O N O N packagingMaterialCodeListMaintenanceAgency D A D A D D A D A D A packagingMarkedRecyclableScheme M N M N M M N M N M N materialSafetyDataSheet M N M N M M N M N M N materialSafetyDataSheetNumber O N O N O O N O N O N descriptionShort O N

Page 197: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 196 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

brandName M N tradeItemDescription M Y M Y M M Y M Y M Y informationProvider O Y O Y O O Y O Y O Y globalTradeItemNumber O N O N O O N O N O N classificationCategoryCode O N classificationCategoryName O N classificationCategoryDefinition O N eANUCCClassificationAttributeTypeCode O N eANUCCClassificationttributeTypeName O N eANUCCClassificationAttributeTypeDefinition O N eANUCCClassificationAttributeValueCode O N eANUCCClassificationAttributeValueName O N additionalClassificationCategoryCode O N additionalCassificationCategoryDescription O N additionalClassificationAgencyName D N nextLowerLevelGtin M N M N M M N M N M N

Page 198: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 197 of 195

Mixed Module

(MX) Pallet (PL)

Displays, Shippers or Mixed Cases

(DS) Case (CS) Pack/InnerPack (PK) Each (EA)

Resolved Item Name M/O/D Status Common

M/O/D Status Common

M/O/D Status

M/O/D Status

Common

M/O/D Status Common

M/O/D Status Common

quantityOfNextLowerLevelTradeItem M N M N M M N M N M N quantityOfChildren M N M N M M N M N tradeItemGroupIdentificationCode O N tradeItemGroupIdentificationDescription D N replacedTradeItemIdentification O N O N O O N O N O N classOfDangerousGoods D N D N D D N D N D N packagingTermsAndConditions O N O N O O N O N O N barCodeType O N O N O O N O N O N additionalTradeItemDescription O N O N O O N O N O N stackingFactor O N O N O O N O N O N

Page 199: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 198 of 195

APPENDIX C Attributes Mandatory for Data Synchronization

Class Name Item Name Mandatory to Data Sync

EANUCCTradeItemClassification eANUCCClassificationAttributeTypeCode Yes EANUCCTradeItemClassificationValue eANUCCClassificationAttributeValueCode Yes TradeItem totalQuantityOfNextLowerLevelTradeItem Yes GlobalTradeItemNumber globalTradeItemNumber Yes Information Provider informationProvider Yes TargetMarketInformation targetMarketCountryCode Yes TradeItemClassification classificationCategoryCode Yes TradeItemHierarchy quantityOfCompleteLayersContainedInATradeItem Yes TradeItemHierarchy quantityOfTradeItemsContainedInACompleteLayer Yes

Attributes Mandatory for Data Synchronization

Page 200: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 199 of 195

Appendix D: Trade Item Implementation Feedback

Based on the Trade Item Implementation feedback presentation on July 7, 2004, the following modifications will be made to the Trade Item. Deletion of attributes:

Delete Class Attribute Model Location Note

1 TradeItemPriceDateInformation effectiveStartDateTrading Partner Neutral Trade Item Information (TPNTII) appendix 4

2 TradeItemPriceDateInformation effectiveEndDate (TPNTII) appendix 4

3 PackagingMarking isBarcodeOnThePackage Does not exist in model.

The textual business requirement lines (1506-1531)will be removed from the BRD. No change needed to model as this attribute does not exist in the model.

4 PackagingMarking isPackagingMarkedAsRecyclable (TPNTII) appendix 45 BrandOwnerOfTradeItem nameOfBrandOwner (TPNTII) appendix 46 InformationProvider nameOfInformationProvider Trade Item Information appendix 37 ManufacturerOfTradeItem nameOfManufacturer (TPNTII) appendix 48 PackagingMaterial packagingMaterialDescription (TPNTII) appendix 49 PackagingType packagingTypeDescription (TPNTII) appendix 4

10 TradeItemPalletInformation palletTermsAndConditions (TPNTII) appendix 411 TradeItemPalletInformation palletTypeCode (TPNTII) appendix 412 TargetMarketInformation targetMarketDescription Trade Item Information appendix 313 NextLowerLevelTradeItemInformation totalQuantityOfNextLowerLevelTradeItem Trade Item appendix 114 TradeItemDescriptionInformation tradeItemDescription Trade Item Information appendix 3

15 PriceOnTradeItem priceOnPackIndicator Does not exist in model.

The textual business requirement lines (1826-1851) will be removed from the BRD. No change needed to model as this attribute does not exist in the model.

Page 201: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 200 of 195

Attributes that will be handled with the Hierarchy Proposal: These four attributes are in the Trade Item appendix 1 class diagram. • Quantity of layers per pallet • Quantity of children • Quantity of trade items per pallet • Quantity of trade items per pallet layers

Attributes recommended to change from Mandaotry or Dependent to Optional

Change Class Attribute Model Location Note1 ClassificationCategory additionalClassificationCategoryDescription Trade Item Classification appendix 6

2 TradeItemCountryOfOrigin countryOfOrigin (TPNTII) appendix 4 and 5

The Trade Item Country of Origin is optional, if the class is used, then the country of Origin is mandatory.

3 TradeItemHazardousInformation flashPointTemperature(TPNTII) appendix 4 and Trade Item Common appendix 17

4 PriceOnTradeItem retailPriceOnTradeItem (TPNTII) appendix 4 and 5

The Price On Trade Item class is optional, if the class is used, then the retail price on trade item is mandatory.

Page 202: Data Synchronization Data Model for Trade Item

Business Requirements Document DATA SYNCHRONIZATION DATA MODEL FOR TRADE ITEM

(DATA DEFINITION)

COPYRIGHT 2005, GS1™

Version 7.7.1 Page 201 of 195

Conversion of Mandatory Boolean attributes into code list solution.

• isIngredientIrradiated

• isRawMaterialIrradiated

• isTradeItemIrradiated

• isTradeItemGeneticallyModified The Boolean attribute should be replaced by a code list. Below is the current model for the FMCGTradeItemMarking class and revised solution.

________________________________________________________________________________

FMCGTradeItemMarkingisIngredientIrradiated : BooleanisRawMaterialIrradiated : BooleanisTradeItemGeneticallyModified : BooleanisTradeItemIrradiated : Boolean

FMCGTradeItemMarking_RevisedingredientIrradiated[0..1] : AnswerListrawMaterialIrradiated[0..1] : AnswerListtradeItemGeneticallyModified[0..1] : AnswerListtradeItemIrradiated[0..1] : AnswerList

AnswerListFALSETRUEUNSPECIFIED

<<enumeration>>

CodeList Solution


Recommended