Professional Documents
Culture Documents
5 Business Requirement
6 Document For
7
12
13
14 Version 7.7.1
15
18
19
20 DOCUMENT HISTORY
21
22
Document Number: 7.7.1
Document Version: 7.7.1
Document Issue Date May 23, 2005
23
24 Document Summary
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 - Jeggert@uc-council.org
UCC – Mschneider@uc-council.org
Status For ITRGapproval – BRG Approved
25
26 Document Change History Log
Date of Change Version Reason for Summary of Change CCR #
Change
February 17, 2001 X.0 Messaging Documentation to support the XXXXX
Architecture Core Item Business Process and
to reflect the UCC UML
methodology standards
February 28, 2001 2.0.1 Common Data Item Edited the Common data item
Rpt report.
April 27, 2001 2.0.4 Added the Item Item Containment is described
Containment 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 01-000009
Summary that was documented
on change request 01-000009
May 9, 2002 5.0 UCC work group BRD format was upgraded to 01-000011
01-000064
meeting and GSMP standards. Changed title
01-000065
submittal to Align of the document to “Core Item &
Data BRG (Item Extension of Cross industry
Task Group) Data”
May 10, 2002 V0.6.0 Models upgraded Class diagrams in the BRD were
to match text upgraded to reflect the text
changes changes made in V0.5.0
July 19, 2002 V0.6.1 Change to Section Combined GCI and UCC 02-000065
3.0 standards work.
August 12, 2002 V0.6.2 Change to Section Changes to data dictionary.
3.0. Add Section
5.0
Sept. 11, 2002 V0.6.3 Merged updates Updates made to text from Item
Implementation Project Team.
Section
incorporated
Oct. 10, 2002 V0.6.4 Merged updates Updates made to text from Item
Project Team.
Oct. 22, 2002 V7.0 Merged updates Updates made to text from Item
Models upgraded Project Team
Implementation
Section upgraded
Nov. 21, 2002 V7.1 Models upgraded, Updates made to text based on
Text upgraded, comments resulting from Public
Attributes grouped Review by Align BRG. Changes
to reflect UML. to document agreed by project
team.
March 14, 2003 V7.2 Model Version 7.2 Model Harmonization
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 Changed Trading Partner Neutral 03-000082
Regional Attributes Information Model to eliminate Is
Item Green Dot.
July 19, 2004 V 7.5 Added the code list Additional code list added to 04-000035
into section 4.8.1 section 4.8.1
December 15, V 7.6 Added Appendix E: Incorporated Trade Item 04-000044
2004 Trade Item Implementation Feedback
Implementation
Feedback
April 4, 2005 V 7.7 Feedback from 1.3.1
BRD vs. XML .
May 24, 2005 V 7.7.1 Errata - Update of Changed to GDSN Trade Item
Trade Item Classification. Removed remaining
Classification references to alternate party and
item identifiers. Corrected
formatting issues.
27
28
29
30
31 Approvals
Name Title Signature Date
32
33
34
35 TABLE OF CONTENTS
36 FOREWORD........................................................................................................................ 5
95 FOREWORD
96
97 “Implementation of this Item standard requires adherence to the business rules
98 contained in this document in addition to adherence to the technical schema as it is
99 designed. In order to enable reusability and commonality across the EAN.UCC
100 Business Message Standards, a common library has been developed to support the
101 technical implementation of the EAN.UCC standards into XML schemas resulting in
102 standardized data types and field sizes. As a result, the schema will accommodate
103 the data types and field sizes as defined in this standard, however, the schema does
104 not enforce any specific field sizes as defined by the business requirements.”
105
106
107
108 1.0 Business Opportunity:
109 Item is the second message in the trade process following the Party message. Item
110 elements are the mandatory attributes needed to align the item information between
111 trading partners. These attributes in combination ensure the uniqueness of the data
112 set associated with a GTIN. The use, definition, and relevance of these attributes is
113 the same for ALL EAN.UCC industries. Following the Item attributes is an extension
114 of cross industry. These are data attributes that may be required in conducting
115 commerce between partners for the trade of an item or service. These attributes are
116 relevant to more than one industry. The definition of these attributes must be the
117 same for all industries.
118
119 1.1 Problem Statement:
120 Item and the extension of the cross industry data processes include communicating
121 the data elements necessary to support the core business requirements in the global
122 trading environment. The Party and Item process are mandatory in the completion of
123 the price, purchase order, invoice, etc. messages that follow in the global trade
124 process.
125
126 1.2 Audience:
127 The audience of the standards would be any participant in the global supply chain.
128 This would include retailers, manufacturers, service providers and other third parties.
129
130 1.3 References:
131
132 • The legacy: the Global Data Alignment System (GDAS)
133
134 “ELECTRONIC CATALOGUES EAN RECOMMENDATIONS COMMON SET
135 OF DATA” (June 1998-June 1999)
136
137 “GLOBAL DATA ALIGNMENT – GCI – DRAFT” (21 Jan. 2000 – 24 July
138 2000)
139
140 • GLOBAL DATA DICTIONARY- Item Data Model – General Overview,
141 Version 1, Global Commerce Initiative, Global Data Dictionary Group, March
142 31, 2002
143
144 • EAN.UCC Business Message Standards Version 1.0, July 2001
145 • Core Party Business Requirements Document, Version 6.0 of May 10, 2002
146 • Core Item and Extension of Trading Partner Neutral Data, Version 0.6.0 of
147 May 10, 2002
148 • EAN.UCC Global Business Model (Process and Data), October 1999
149 • Java Framework for SIMPL-EDI Requirements Specification, April 2000
150 • Simple eb(electronic business), March 2000
151 • BPAWG Model of the International Supply Chain Domain (interim report),
152 January 2000
153 • Change Requests: 01-000009, 01-000010, 01-000064, 01-000065.
154 • Change Request 02-00065
155 • GSMP –Technical Steering Team, Policy Paper “Policy on the use of
156 identification keys in standards and recommendations developed in GSMP”,
157 January 2003
158
159 Note: The following text was extracted from a letter sent to the Align Data BRG on March
160 31, 2003: “Due to the timing of this policy paper and the dialogue going on within the
161 user community regarding how it will affect the standards, the Executive Management
162 Team decided that the policy would be implemented in version 2.0 of the standards,
163 which should be published in 2004.”
164 Additionally, the existing Electronic Data Interchange messages in widespread use
165 were mined for their business content.
166 • UCS 888 Item Maintenance
167 • VICS EDI 832 Price Sales Catalog
168 • I/C EDI 832 Price Sales Catalog
169 • EANCOM© PRICAT
170 Acknowledgement is also due to the work going on in the XML environment.
171 • ebXML/SOAP
172 • eCo Framework (Common Business Library)
173 • Rosettanet
174 • W3C
175
181
182 2.0 Process View – General Requirements:
183
184 The buyer and seller must make contact and set up a business relationship before
185 trade can proceed. This is a prerequisite to all of the other steps. This initial contact
186 can be made in many different ways. Following the establishment of the trading
187 agreement the parties must exchange their basic business data such as trading
188 partner names, addresses, locations, item attributes, price lists, contracts and trading
189 partner agreements. Specifically, the Core Item message follows the Core Party
190 message in the data alignment process. This process creates a common
191 understanding between the trading parties which can be used as a resource
192 throughout the trading process.
193
194 2.1 Use Case Scenario:
195 There is only one scenario in the Item data communication process as described in
196 problem statement of section 1.1. Item data alignment is the process of
197 communicating the core item and cross industry data elements following the
198 establishment of a business relationship between suppier, buyer or third party.
Buyer Seller
O rder
D espatch Advice
Invoice
199
200
201
202 2.1.1 Business Opportunity/Problem Statement
203 The objective of this document is to elaborate the Data Synchronization Data Model
204 for Trade Item (hereafter referred to as ‘Data Sync Trade Item’) business process in
205 enough detail to support the construction of standards. It is assumed that the
206 players, both seller and buyer, have established a business understanding of the
207 trading partner relationship. The challenge is to provide the core elements necessary
208 to complete all supply chain processes without duplicates.
209
210 2.1.2 Actors
211 The two general players in the Data Sync Trade Item business process are the
212 "seller" and the "buyer". Depending on the specific nature of the relationship other
213 players may have a role, such as a Third Party. The graphic flow below pictures the
214 core sequence of messages, and is expanded to account for additional scenarios.
215
216
Actor’s Description Buyer Seller Third
Name 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 X X X
item and may include creation, distribution,
publication, and/or maintenance of the item.
217
218 2.1.3 Preconditions
219 The Data Sync Trade Item business process begins when the parties decide to do
220 business together. The next step is for the buyer to communicate the Party
221 organizational information to the seller. The seller provides his Party organizational
222 information to buyer. Other data alignment follows such as item and price attributes.
223
224 2.1.4 Process Start
225 The start-state of the Data Sync Trade Item business process begins during the
226 initial discussions between the trading partners and the need to exchange item
227 information.
228
229 2.1.5 Process End
230 Once the Data Sync Trade Item business message has been accepted by both the
231 seller and buyer, then data alignment has been achieved. This process can be an
232 ongoing process as item business information changes or new parties are added.
233 The process of trading goods and services can now occur.
234
235 2.1.6 Post Conditions
236 The end-state of the Data Sync Trade Item business process occurs when the
237 parties have achieved Party and Item data alignment.
238
239 2.1.7 Process Activities
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
241 See the work completed by the data synchronization project team for a detailed view of
242 data communication.
243
244 3.0 Logical View
245 The Data Sync Trade Item messages include the item’s unique identification,
246 descriptions, and characteristics.
247
248 3.1 Definition of Conditions
249 To help with the implementation of this data model, several key definitions are listed
250 below.
251
252 Master Data/Transactional Data –
253
254 • Master data is considered to be that set of data that describes the
255 specifications and structure of each item and party involved in the supply
256 chain processes. The uniqueness of the data associated with a trade item is
257 given only by the GTIN. This data is static, not dependent on a transaction.
258
259 • Transactional data is that set of data that can only be determined during a
260 business transaction, i.e., plan, sell, buy, and deliver cycle. (E.g. actual
261 amount of cases delivered).
262
263 • NOTE – this data model only includes master data
264
265 Master Data Alignment
266 • Master Data Alignment is the process of timely distribution of accurate Master
267 Data from one partner to others and the correct use of this data. Such
268 synchronization and use of Master Data leads to more accurate business
269 transactions and therefore reinforces the efficiency of the supply chain
270 operations.
271 • Successful Master Data Alignment is achieved via the use of EAN.UCC
272 coding specifications throughout the supply chain, communication of all
273 changes and new information between trading partners and use of the
274 information exchanged in subsequent transactions.
275 • Master Data Alignment relies on EAN.UCC specifications concerning the
276 Unique Identification of Items, GTIN and Parties GLN.
277
278 Core attributes:
279 • An attribute whose definition is common across all Industries
280 • Core attributes are common across all geographies. I.e. ALL Target Markets
281 • These attributes do not necessary need to be maintained by the Registry.
282 • Core attributes CANNOT be relationship dependant. They are trading partner
283 neutral only
284
285 Extension attributes:
286 • An extension is an attribute that is relevant to one or more industries (not all
287 EAN.UCC Industries)
288 • The definition of an extension attribute is common to all Industries who use
289 the attribute.
290 • Each Industry is responsible for determining the extension attributes that are
291 relevant to their Industry.
292 • New extension attributes may be submitted/requested for a specific Industry
293 as necessary.
294 • The conditions of extension attributes can vary by each industry. E.g.
295 Mandatory/Optional, Global/Local, Trading Partner Neutral/Relationship
296 Dependent, and Common to all Hierarchy levels.
297 • Industry user groups should be developed in concert with the EAN.UCC
298 GSMP Process, to determine their relevant extension attributes and the
299 conditions associated with those attributes.
300 • Process user groups such as CPFR and local (target market) extensions.
301
302 Trading Partner Neutral/Trading Partner Dependent
303
304 Values for an attribute can vary depending on the relationship with the party
305 receiving the data. The Trading Partner Neutral/Trading Partner Dependent
306 status indicates this rule.
307
308 • The condition Trading Partner Neutral is applied to any attribute whose value
309 is independent on a buyer and seller relationship. An attribute, which has the
310 condition Trading Partner Neutral, can have only one set of values .
311
312 • The condition Trading Partner Dependent is applied to any attribute whose
313 value is dependent on a buyer and seller relationship. An attribute, which has
314 the condition Trading Partner Dependent, can have only one set of values per
315 GLN of Party Receiving Data. These are attributes whose value is dependent
316 on a specific point-to-point agreement between a buyer and a seller.
317
318 An attribute which has the condition Trading Partner Neutral & Trading
319 Partner Dependent, can have only one set of values for the Trading Partner
320 Neutral value AND one set of values per GLN of Party Receiving Data
321
322
323 Multiple Values allowed:
324
325 This condition is used to indicate that multiple values can be submitted for a
326 trade item.
327
328 E.g. multiple types of packaging on a trade item e.g. plastic, cardboard etc
329
330 Where there is a need to express multiple measures, these are handled through
331 indicating the attribute type as ‘Measurement’. Both the value and UOM can be
332 repeated, and must be used together. See section 4.6 on Unit of Measure in the
333 implementation consideration and concerns.
334
335 Where there is a need to express multiple language versions, these are handled
336 through indicating the attribute type as ‘Text Description’. See section 4.4 on
337 Language in the implementation consideration and concerns.
338
339
340 Market Group
341 • A Market Group is used to identify a proprietary group of data recipients. It is
342 normally determined by the information provider although it can also be
343 created by buyers and third parties. This group is used and developed by the
344 information provider to control del publication of data to a specific group of
345 customers. This should not be confused with Target Market.
346
347 Target Market Country Code
348 • The purpose of the target market country code is to organize master data to
349 meet the requirements of specific geographies
350
351 • The purpose of this field is to explain where a manufacturer is intending to
352 sell its product(s) to a buyer. It does not control where the buyer can resell
353 the product (s) to the end consumer.
354
355 • It is the country, (the geopolitical area) where the product is to be sold and
356 available for publication in an Item Catalog.
357
358 • Target Market Country Code in relationship to Master Data, can be Trading
359 Partner Neutral only. A Target Market Country Code is not used to control
360 Distribution or Consumer Market Area geographies. E.g. product available for
361 shipment from a single Distribution Center.
362
363
364 Target Market Sub-Country Code
365 • A sub-country code level used to address/comply with a “law making”
366 requirement associated with a country.
367 • The number of sub-country codes will vary by each country. These will match
368 with the legislation requirements of each country. (Local bottle deposit tax
369 laws, State and country taxes)
370 • Not all countries will have sub-country codes.
371 • A sub-country code must be associated with a Target Market Country Code.
372 It cannot stand-alone.
373
374 Global/Global-Local/Local
375 • All attributes are impacted by their geo-political relevance. This condition can
376 be used by information providers as they build data models. With this
377 information, they can limit the attributes communicated to those relevant for
378 that geography.
379 • A global attribute indicates that the attribute is relevant for business cases
380 around the world, and can only have a single value throughout the world.
381 (E.g. GTIN)
382
383 • A global/local attribute indicates that the field is relevant for business cases
384 around the world, that its definition is the same around the world, but may
385 have a different value depending on the geography. (E.g. VAT tax values,
386 1.00 in France, 1.05 in Belgium)
387
388 • A local attribute is only relevant in certain geographical areas, and the values
389 may change based on where the product is offered for sale. (E.g. green dot –
390 only relevant in certain European countries)
391
392 How does the Global/Global-Local/Local condition, and Target Market value
393 interact to affect attribute values?
394
395 An attribute, which has the condition ‘Global’, can have only one global value (except
396 where there are multiple values allowed).
397
398 An attribute which has the condition Global / Local can have one value per Target
399 Market specified (except where there are multiple values allowed). A Global/Local
400 attribute indicates that the field is relevant for business cases around the world, that
401 its definition is the same around the world, but may have a different value depending
402 on the geography. (E.g. the attribute - VAT tax values are relevant globally, but the
403 actual value, 1.00 in France, 1.05 in Belgium varies by country)
404 As long as the attribute values apply consistently to the GTIN, GLN, TM combination
405 the values are repeatable.
406
407 Example:
408
409 GTINa + GLNa + TMa + b, = Ohio, Indiana. Start availability date = January 1,
410 2003
411 Target Market can be repeated where the values for the attribute are the same
412 e.g. start availability date is the same for the GTIN + GLN + TM combination data
413 set.
414
415 GTINa + GLNa + TMc = Kentucky. Start availability date = January 15, 2003
416
417 An attribute, which has the condition Local, can have only one value for the Target
418 Market that is valid for (except where there are multiple values allowed).
419
420 Attribute Cardinality
421
422 Mandatory
423 An attribute in this model is mandatory when its value is required.
424
425 Optional
426 An attribute in this model is Optional when its value is not required.
427
428 Dependent
429 An attribute in this model is depended when its value is conditional on some
430 other attribute’s value.
431
432 Type
433 The following data types are used in this model:
434
435 Alphanumeric (AN)
436 Amount
437 Boolean
438 Char
439 Description
440 Date
441 DateTime
442 Integer
443 Long Description
444 Long Text Description
445 Measurement
446 Measurement Value
447 Numeric (N)
448 Party Identification
449 Percentage
450 Text Description
451
452 Trade Item
453 • A Trade Item is any product or service upon which there is a need to retrieve
454 pre-defined information and that may be priced, ordered or invoiced at any
455 point in any supply chain. The term “trade item” is not to be confused with the
456 legacy term “traded item” (now referred to within the General EAN.UCC
457 Specifications as ‘standard trade item group’ which can mean a specific
458 product containment level, which is also called case. “Trade item” can
459 represent any level of product containment, and also can represent a service.
460
461 In addition, the supply chain is any point from the inception of the product
462 through the final consumption and disposal/reuse/recycling/return of that
463 trade item. Reference General EAN.UCC Specifications for definitions of the
464 term ‘trade item’, ‘retail consumer trade item’, and ‘standard trade item
465 grouping’.
466
467 Party
468 • A Party (or) Location is any legal, functional or physical entity involved at any
469 point in any supply chain and upon which there is a need to retrieve pre-
470 defined information.
471
472 Product Hierarchy Reference Level
473 This condition is used to indicate at what level of the product hierarchy each
474 attribute is relevant. For some attributes, business requirements are such that the
475 attribute only needs to be provided at a specific level.
476
477 Example – “netContent” this field is only required at the consumer unit level.
478 For most attributes, a value must be entered for all attribute levels.
479
480 Common Value to all Product Hierarchy
481 Common value condition indicates when the value for the attribute is equal for all
482 levels of a hierarchy.
483
484 Example – “orderingLeadTime” is common across all levels of the product
485 hierarchy; common value = Yes
486
487 Example – “grossWeight” is not common from each to case to pallet;
488 Common value = No
489
578
579 Class Name: ChildTradeItem
580
581 Item Name: tradeItemIdentificationOfNextLowerLevelTradeItem Æ Represented
582 as association of ChildTradeItem Class to TradeItemIdentification Class.
583
584 Core/Extension: E
585 Global Local Status: G
586 M/O/D: M
587 Multiple Values Allowed: Y
588 Neutral/Relationship Dependant: T.P.Neutral
589 Product Hierarchy Reference Level: All
590 Common value to all product hierarchy: No
591 Type: N
592 Size: 14
593
594 Definition: A reference to the GTIN of the next lower level of trade item
595 that this trade item contains.
596
597 Examples: GTIN "00037000123415" contained in GTIN
598 00037000123330. See tables in Section 4.1 of the Implementation
599 Considerations and Concerns for more examples.
600
601 Business Rules: Allowed for more than 1 reference to lower levels to
602 allow for the registration of Mixed Assortments. The sequence of entering
603 GTINs is important when a next lower level GTIN is to be linked. The next
604 lower level GTIN must already exist, therefore the order of trade items to
605 be entered should be from lowest to highest e.g. consumer, then
606 intermediate, then traded, etc. While there can be multiple child trade
607 items, there can only be one trade item identification per child item.
608
609
610 Class Name: Trade Item Identification
611
612 Item Name: replacedTradeItemIdentification Ærepresented as a role in Trade
613 Item Diagram
614
615 Core/Extension: E
616 Global Local Status: G/L
617 M/O/D: O
618 Multiple Values Allowed: N
619 Neutral/Relationship Dependant: T.P.Neutral
620 Product Hierarchy Reference Level: All
621 Common value to all product hierarchy: No
622 Type: N
623 Size: ..14
624
625 Definition: Indicates the trade item identification of an item that is being
626 permanently replaced by this trade item.
627
679 that may be planned, priced, ordered, delivered and or invoiced at any point
680 in any supply chain.
681
682 Examples: 14 digit code. Please see PTRG directions for creating GTINs
683
684 Business Rules: EAN.UCC numbering structures will be used for the
685 identification of trade items. All of them will be considered as 14-digit Global
686 Trade Item Number (GTIN). Must be present to enable data to be presented
687 to trade item catalogue. Must be submitted by the owner of the data (who
688 may be the original manufacturer, the importer, the broker or the agent of the
689 original manufacturer) See to the EAN.UCC specifications. This field is
690 mandatory within the Global Data Synchronization work process. See
691 implementation notes.
692
693
741
742 Class Name: ClassificationCategory
743
744 ItemName: additionalClassificationCategoryDescription
745
746 Core/Extension: E
747 Global Local Status: G
748 M/O/D: Dependent on additionalClassifcationCategoryCode
749 Multiple Values Allowed: Y
750 Neutral/Relationship Dependant: T.P.Neutral
751 Product Hierarchy Reference Level: Each
752 Common value to all product hierarchy: No
753 Type: AN
754 Size: ..70
755
756 Definition: Description of the additional classification bundle
757 (code/agency + description).
758
759 Examples: "Special Breads"
760
761 Business Rules: The description of the additional classification bundle
762 (code/agency + description) can be repeated for each classification
763 agency used. Required if ClassificationCategoryCode field is populated.
764
765
766 Class Name: GDSNTradeItemClassification
767
768 Item Name: classificationCategoryCode
769
770 Core/Extension: C
771 Global Local Status: G
772 M/O/D: O
773 Multiple Values Allowed: N
774 Neutral/Relationship Dependant: T.P.Neutral
775 Product Hierarchy Reference Level: Each
776 Common value to all product hierarchy: No
777 Type: N
778 Size: 8
779
780 Definition: Global EAN.UCC classification category code. Unique,
781 permanent 8-digit key.
782
783 Examples: "10000276"
784
785 Business Rules: The system will assign Bricks on a first-approved, first-
786 served basis. Mandatory within the Data Sync process.
787
788
789 Class Name: GDSNTradeItemClassification
790
791 Item Name: classificationCategoryDefinition
792
793 Core/Extension: C
794 Global Local Status: G
795 M/O/D: Dependent on classificationCategoryCode
796 Multiple Values Allowed: N
797 Neutral/Relationship Dependant: T.P.Neutral
798 Product Hierarchy Reference Level: Each
799 Common value to all product hierarchy: No
800 Type: AN
801 Size: ..700
802
803 Definition: System generated explanation of Global EAN.UCC category.
804
805 Examples: distilled alcoholic grape drink without carbonation
806
807 Business Rules: This field is mandatory when
808 classificationCategoryCode is populated.
809
810
811
812 Class Name: GDSNTradeItemClassification
813
814 Item Name: classificationCategoryName
815
816 Core/Extension: C
817 Global Local Status: G
818 M/O/D: Dependent on classificationCategoryCode
819 Multiple Values Allowed: N
820 Neutral/Relationship Dependant: T.P.Neutral
821 Product Hierarchy Reference Level: Each
822 Common value to all product hierarchy: No
823 Type: AN
824 Size: ..105
825
826 Definition: The system generated text equivalent of the Global EAN.UCC
827 classification category code.
828
829 Examples: wine-still
830
831 Business Rules: Being system generated, if ClassificationCategoryCode
832 is populated, this field becomes mandatory
833
834
835 Class Name: GDSNTradeItemClassificationAttributeType
836
837 Item Name: eANUCCClassificationAttributeTypeCode
838
839 Core/Extension: E
840 Global Local Status: G
841 M/O/D: O
842 Multiple Values Allowed: Y
843 Neutral/Relationship Dependant: T.P.Neutral
844 Product Hierarchy Reference Level: Each
845 Common value to all product hierarchy: No
846 Type: N
847 Size: 8
848
849 Definition: Unique 8 digit code which identifies the Global EAN.UCC
850 classification attribute.
851
852 Examples: "20000212" wine-still variant
853
854 Business Rules: If used, the first attribute, which is the primary attribute,
855 is mandatory. The remaining 6 are optional. This field is repeatable seven
856 times. Mandatory in the Data Sync process.
857
858
859 Class Name: GDSNTradeItemClassificationAttributeType
860
861 Item Name: eANUCCClassificationAttributeTypeName
862
863 Core/Extension: E
864 Global Local Status: G
865 M/O/D: O
866 Multiple Values Allowed: Y
867 Neutral/Relationship Dependant: T.P.Neutral
868 Product Hierarchy Reference Level: Each
869 Common value to all product hierarchy: No
870 Type: AN
871 Size: ..105
872
873 Definition: The system generated text equivalent of the Global EAN.UCC
874 classification attribute code.
875
876 Examples: "grape variety " 20000081
877
878 Business Rules: Being system generated, if
879 ClassificationAttributeTypeCode is populated, this field becomes
880 mandatory.
881
882
883 Class Name: GDSNTradeItemClassificationAttributeType
884
885 Item Name: eANUCCClassificationAttributeTypeDefinition
886
887 Core/Extension: E
888 Global Local Status: G
889 M/O/D: O
890 Multiple Values Allowed: Y
891 Neutral/Relationship Dependant: T.P.Neutral
892 Product Hierarchy Reference Level: Each
893 Common value to all product hierarchy: No
894 Type: AN
895 Size: ..700*
896
897 Definition: System generated explanation of Global EAN.UCC attribute.
898
899 Examples:
900
901 Business Rules:
902 *Waiting for the final publication of the EAN.UCC classification.
903
904
905 Class Name: GDSNTradeItemClassificationAttributeValue
906
907 Item Name: eANUCCClassificationAttributeValueCode
908
909 Core/Extension: E
910 Global Local Status: G
911 M/O/D: O
912 Multiple Values Allowed: N
913 Neutral/Relationship Dependant: T.P.Neutral
914 Product Hierarchy Reference Level: Each
915 Common value to all product hierarchy: No
916 Type: N
917 Size: 8
918
919 Definition: Unique 8 digit code which identifies the Global EAN.UCC
920 classification attribute value.
921
922 Examples: See Implementation notes for full illustration.
923
924 Business Rules: One valid value may be submitted per GTIN. Once an
925 attribute code is selected, it is mandatory to submit an associated value
926 code.
927
928
929 Class Name: GDSNTradeItemClassificationAttributeValue
930
931 Item Name: eANUCCClassificationAttributeValueName
932
933 Core/Extension: E
934 Global Local Status: G
935 M/O/D: O
936 Multiple Values Allowed: N
937 Neutral/Relationship Dependant: T.P.Neutral
938 Product Hierarchy Reference Level: Each
939 Common value to all product hierarchy: No
940 Type: AN
941 Size: ..105
942
943 Definition: The system generated text equivalent of the Global EAN.UCC
944 classification attribute value code.
945
946 Examples: See Implementation notes for full illustration.
947
948 Business Rules:
949
950 3.5 TRADE ITEM INFORMATION:
951
952 Class Name: Information Provider
953
954 Item Name: informationProvider
955
956 Core/Extension: C
957 Global Local Status: G
958 M/O/D: M
959 Multiple Values Allowed: N
960 Neutral/Relationship Dependant: T.P.Neutral
961 Product Hierarchy Reference Level: All
962 Common value to all product hierarchy: Yes
963 Type: PartyIdentification
964 Size: Not Applicable
965
966 Definition: Unique location number identifying the information owner. E.g.
967 Distributor, broker, Manufacturer, Franchisee. This is not a third party service
968 provider. The purpose of this field is to identify the originator of the data.
969 Example Trade Item A - is availavble to retailer B from manufacter C or
970 distributor D. The retailer could receive information from both sellers and this
971 field declares the information owner.
972
973 Examples: Refer to the following websites for specific directions on how
974 to construct global location numbers - www.uc-council.org or www.ean-
975 int.org
976 Business Rules: Combination of this field (gln) + gtin + target market
977 uniquely identifies a set of attributes for a trade item. The data owner is not
978 necessarily the source of the data, but has the responsibility to provide and
979 maintain the data in the catalogue. This field is mandatory within the Global
980 Data Synchronization work process. See implementation notes.
981
982
983 Class Name: InformationProvider
984
985 Item Name: nameOfInformation Provider
986
987 Core/Extension: E
988 Global Local Status: G
989 M/O/D: Dependent on informationProvider
990 Multiple Values Allowed: N
991 Neutral/Relationship Dependant: T.P.Neutral
992 Product Hierarchy Reference Level: All
993 Common value to all product hierarchy: Yes
994 Type: AN
995 Size: ..35
996
997 Definition: Name of the party who owns the data. Name of the
998 information provider on the trade item.
999
1050 both text and a language code. The description will be generated from the
1051 ISO 3166-1 code list. The language code will be generated from the ISO
1052 639 code list.
1053
1054 Examples: ISO 3166-1 840= "United States", 276= "Federal Republic of
1055 Germany, 156 = "China"
1056
1057 Business Rules: This is the textual indication of the target market code.
1058 See Section 4.4 of Implementation Considerations and Concerns for
1059 more details.
1060
1061 Class Name: TargetMarketInformation
1062
1063 Item Name: targetMarketSubdivisionCode
1064
1065 Core/Extension: C
1066 Global Local Status: G
1067 M/O/D: D
1068 Multiple Values Allowed: Y
1069 Neutral/Relationship Dependant:T.P.Neutral
1070 Product Hierarchy Reference Level: All
1071 Common value to all product hierarchy: Yes
1072 Type: AN
1073 Size: 7
1074
1075 Definition: The Target Market Subdivision Code is the secondary code of
1076 the Target Market and must be a subdivision of a Target Market Country
1077 Code. The Target Market Subdivision Code describes the "geo-political
1078 subdivision of a country" where the trade item is available for sale, as
1079 determined by the information provider. For example, "State" in the US,
1080 "Land" in Germany, "Region" in France, or "Province" in Canada. Not all
1081 countries have subdivisions. This code is represented by the three-
1082 character ISO 3166-2 code. This Target Market Subdivision Code is a
1083 dependent attribute. It is important to note that the lack of the Target
1084 Market Subdivision code implies that the trade item is available in the
1085 entire target market country.
1086
1087 Examples: “
1088 “208-025” where “208” represents Denmark from the ISO 3166-1 and 025
1089 represents the Danish county of Roskilde from the ISO 3166-2.
1090 “554-BOP” where “554” represents New Zealand from the ISO 3166-1
1091 and “BOP’ represents the Bay of Plenty.
1092
1093 Business Rules: ISO 3166-2 format 3 digit numerical/3 character alpha
1094 which represents country and subcountry code; following AIDC
1095 guidelines. This information drives data synchronization rules linked to
1096 global/local, local status. This optional field helps further define trade item
1097 availability. The target market code consists of a country code and an
1098 optional subdivision code. A subdivision code must be used in tandem
1099 with a corresponding higher level country code. (e.g. Ohio with US).
1150 Business Rules: Free form text field, but not necessarily tied to
1151 language. Brands are more likely to be language independent. If a trade
1152 item does not have a brand, Use ‘unbranded’ in the description. This is a
1153 Mandatory field. If a trade item is changed from being "Unbranded" to a
1154 brand, this requires a new GTIN. GTIN allocation rules may vary by
1155 industry.
1156
1157 Class Name: TradeItemDescriptionInformation
1158
1159 Item Name: descriptionShort
1160
1161 Core/Extension: E
1162 Global Local Status: G
1163 M/O/D: O
1164 Multiple Values Allowed: N
1165 Neutral/Relationship Dependant:T.P.Neutral
1166 Product Hierarchy Reference Level: Each
1167 Common value to all product hierarchy: No
1168 Type: Multi-Short Description
1169 Size: 35
1170
1171 Definition: A free form short length description of the trade item that can
1172 be used to identify the trade item at point of sale.
1173
1174 Examples: Kel CrnF750g.
1175
1176 Business Rules: Free form text field, this data element is repeatable for
1177 each language used and must be associated with a valid ISO language
1178 code from the attached table. See Section 4.4 of the Implementation
1179 Considerations and Concernsfor more details.
1180
1181 Class Name: TradeItemDescriptionInformation
1182
1183 Item Name: functionalName
1184
1185 Core/Extension: E
1186 Global Local Status: G
1187 M/O/D: M
1188 Multiple Values Allowed: N
1189 Neutral/Relationship Dependant:T.P.Neutral
1190 Product Hierarchy Reference Level: All
1191 Common value to all product hierarchy: Yes
1192 Type: Multi-Short Description
1193 Size: ..35
1194
1195 Definition: Describes use of the product or service by the consumer.
1196 Should help clarify the product classification associated with the GTIN.
1197
1198 Examples: drill, salad dressing, soup, beer.
1199
1200 Business Rules: Free form text field, this data element is repeatable for
1201 each language used and must be associated with a valid ISO language
1202 code from the attached table. See Section 4.4 of the Implementation
1203 Considerations and Concernsfor more details.
1204
1205
1206 Class Name: TradeItemDescriptionInformation
1207
1208 Item Name: invoiceName
1209
1210 Core/Extension: E
1211 Global Local Status: G
1212 M/O/D: O
1213 Multiple Values Allowed: N
1214 Neutral/Relationship Dependant:T.P.Neutral
1215 Product Hierarchy Reference Level: All
1216 Common value to all product hierarchy: No
1217 Type: Multi Short Description
1218 Size: ..35
1219
1220 Definition: Free form information provider assigned trade item
1221 description designed to match trade item/service description as noted on
1222 invoices.
1223
1224 Examples:
1225
1226 Business Rules: Free form text field, this data element is repeatable for
1227 each language used and must be associated with a valid ISO language
1228 code from the attached table. See Section 4.4 of the Implementation
1229 Considerations and Concerns for more details. Most likely will include
1230 several abbreviations.
1231
1232 Class Name: TradeItemDescriptionInformation
1233
1234 Item Name: linkToExternalDescription
1235
1236 Core/Extension: E
1237 Global Local Status: G
1238 M/O/D: O
1239 Multiple Values Allowed: N
1240 Neutral/Relationship Dependant:T.P.Neutral
1241 Product Hierarchy Reference Level: All
1242 Common value to all product hierarchy: No
1243 Type: AN
1244 Size: ..70
1245
1246 Definition: The link (e.g. URL) to the external description.
1247
1248 Examples:
1249
1350
1351 Definition: The physical form or shape of the product. Used, for
1352 example, in pharmaceutical industry to indicate the formulation of the
1353 trade item. Defines the form the trade item takes and is distinct from the
1354 form of the packaging.
1355
1356 Examples: "tablet", "powder", "gel", "shredded", "liquid","granules"
1357
1358 Business Rules: Optional field that can be used to further describe a
1359 trade item's benefit delivery method. Free form text. (See examples)
1360
1361
1362 Class Name: TradeItemDescriptionInformation
1363
1364 Item Name: tradeItemGroupIdentificationCode
1365
1366 Core/Extension: E
1367 Global Local Status: G
1368 M/O/D: O
1369 Multiple Values Allowed: N
1370 Neutral/Relationship Dependant:T.P.Neutral
1371 Product Hierarchy Reference Level: Each
1372 Common value to all product hierarchy: No
1373 Type: AN
1374 Size: ..20
1375
1376 Definition: A code assigned by the supplier or manufacturer to logically
1377 group trade item independently from the Global trade item Classification.
1378
1379 Examples: Code representing a group of GTINs for all 501 Blue Jeans
1380 sizes and colors
1381 123=
1382 GTIN1 501 Blue/38
1383 GTIN2 501 Blue/40
1384 GTIN3 501 Black/38
1385 GTIN4 501 Black/40
1386
1387 Business Rules: Manufacturer assigned. This code is typically assigned
1388 to multiple GTINs.
1389
1390
1391 Class Name: TradeItemDescriptionInformation
1392
1393 Item Name: tradeItemGroupIdentificationDescription
1394
1395 Core/Extension: E
1396 Global Local Status: G
1397 M/O/D: D
1398 Multiple Values Allowed: Y
1399 Neutral/Relationship Dependant: T.P.Neutral
1543
1544 Class Name: BrandOwnerOfTradeItem
1545
1546 Item Name: brandOwner - represented by relation to Party Identification
1547
1548 Core/Extension: E
1549 Global Local Status: G
1550 M/O/D: O
1551 Multiple Values Allowed: N
1552 Neutral/Relationship Dependant: T.P.Neutral
1553 Product Hierarchy Reference Level: All
1554 Common value to all product hierarchy: Yes
1555 Type: PartyIdentification
1556 Size: ..Not Applicable
1557
1558 Definition: Unique location number identifying the brand owner. May or
1559 may not be the same entity as the information provider, which actually
1560 enters and maintains data in data pools.
1561
1562 Examples: GLN, DUNS_PLUS_FOUR
1563
1564 Business Rules: The brand owner is the source of the data relating to
1565 the trade item, but is not necessarily responsible for providing and
1566 maintaining the data in the catalogue.
1567 This is the responsibility of the information provider.
1568 While the class BrandOwnerOfTradeItem is optional, the party
1569 identification for the brand owner is required when a brand owner is
1570 present.
1571
1572
1573 Class Name: BrandOwnerOfTradeItem
1574
1575 Item Name: nameOfBrandOwner
1576
1577 Core/Extension: E
1578 Global Local Status: G
1579 M/O/D: D
1580 Multiple Values Allowed: N
1581 Neutral/Relationship Dependant: T.P.Neutral
1582 Product Hierarchy Reference Level: All
1583 Common value to all product hierarchy: Yes
1584 Type: AN
1585 Size: ..35
1586
1587 Definition: Name of the party who owns the brand of the trade item.
1588
1589 Examples: Manufacturer of branded trade item - Can also be distributor
1590 or retailer that licenses a brand name to various private label
1591 manufacturers.
1592
1643 national dangerous goods legislation), thus facilitations for the transport of
1644 defined limited quantity by road or rail are possible or not. If they are
1645 possible, they must be indicated, whether they are used by the data
1646 supplier.
1647
1648 Examples: "not possible"
1649
1650 Business Rules: Information required when dangerousGoodsIndicator
1651 equals Y.
1652 Repeatable per dangerousGoodsRegulation code.
1653 List of authorized values :
1654 - not possible
1655 - possible (but not used)
1656 - used (by the data supplier)
1657 Hazardous attributes relate to supply chain handling (e.g., transport,
1658 storage, handling).
1659
1660
1661 Class Name: HazardousInformationDetail
1662
1663 Item Name: dangerousGoodsHazardousCode
1664
1665 Core/Extension: E
1666 Global Local Status: G
1667 M/O/D: D
1668 Multiple Values Allowed: Y
1669 Neutral/Relationship Dependant: T.P.Neutral
1670 Product Hierarchy Reference Level: All
1671 Common value to all product hierarchy: No
1672 Type: AN
1673 Size: 10
1674
1675 Definition: Dangerous goods hazard ID number, which must be applied
1676 to the vehicle, when transporting this trade item (dangerous good) by
1677 road or rail, to inform the police, the fire brigade and others in case of an
1678 accident about the kind of danger caused by the cargo.
1679
1680 Examples: -
1681
1682 Business Rules: Information required when dangerousGoodsIndicator
1683 equals Y. Repeatable per dangerousGoodsRegulationcode. Hazardous
1684 attributes relate to supply chain handling (e.g., transport, storage,
1685 handling).
1686
1687
1688 Class Name: HazardousInformationDetail
1689
1690 Item Name: dangerousGoodsPackingGroup
1691
1692 Core/Extension: E
1693 Global Local Status: G
1694 M/O/D: D
1695 Multiple Values Allowed: Y
1696 Neutral/Relationship Dependant: T.P.Neutral
1697 Product Hierarchy Reference Level: All
1698 Common value to all product hierarchy: No
1699 Type: AN
1700 Size: 3
1701
1702 Definition: Identifies the degree of risk these dangerous goods present
1703 during transport according to IATA/IMDG/ADR/RID regulations.
1704
1705 Examples: Group I : Great danger - Packaging meeting criteria to pack
1706 hazardous materials with great danger.
1707
1708 Business Rules: Information required when
1709 dangerousGoodsRegulationcode is populated. Repeatable per
1710 dangerousGoodsRegulation code.
1711 http://www.unece.org/trade/untdid/d99b/tred/tred8339.htm
1712
1713 Hazardous attributes relate to supply chain handling (e.g., transport,
1714 storage, handling).
1715
1716 Class Name: HazardousInformationDetail
1717
1718 Item Name: dangerousGoodsShippingName
1719
1720 Core/Extension: E
1721 Global Local Status: G
1722 M/O/D: D
1723 Multiple Values Allowed: Y
1724 Neutral/Relationship Dependant: T.P.Neutral
1725 Product Hierarchy Reference Level: All
1726 Common value to all product hierarchy: No
1727 Type: AN
1728 Size: ..200
1729
1730 Definition: Shipping name of the trade item (dangerous goods). The
1731 recognized agencies (see dangerousGoodsRegulationsCodes), in their
1732 regulations, provide a list of all acceptable proper shipping names.
1733
1734 Examples: "Flammable Liquid"
1735
1786 Type: N
1787 Size: 4
1788
1789 Definition: The four-digit number assigned by the United Nations
1790 Committee of Experts on the Transport of Dangerous Goods to classify a
1791 substance or a particular groups of substances. Abbreviation: UNDG
1792 Number
1793
1794 Examples: UN "1155" ETHYLENEGLYCOLDIETHYLETHER
1795
1796 Business Rules: Information required when
1797 dangerousGoodsRegulationcode is populated
1798 Repeatable per dangerousGoodsRegulation code.
1799 http://www.unece.org/trans/danger/publi/adr/adr2001/English/
1800
1801 Hazardous attributes relate to supply chain handling (e.g., transport,
1802 storage, handling).
1803
1804 Class Name: ManufacturerOfTradeItem
1805
1806 Item Name: manufacturer- represented by relationship to Party Identification
1807
1808 Core/Extension: E
1809 Global Local Status: G
1810 M/O/D: D
1811 Multiple Values Allowed: Y
1812 Neutral/Relationship Dependant: T.P.Neutral
1813 Product Hierarchy Reference Level: All
1814 Common value to all product hierarchy: Yes
1815 Type: PartyIdentification
1816 Size: Not Applicable.
1817
1818 Definition: GLN identifying the manufacturer of a trade item. May or may
1819 not be the brand owner, could be a contract manufacturer. GLN
1820 identifying manufacturer of a trade item: this is repeatable field.
1821
1822 Examples: Brand owner A uses contract manufacturers B and C to
1823 produce trade item D. This field would provide a GLN for manufacturers B
1824 and or C
1825
1826 Business Rules: While the class ManufacturerOfTradeItem is optional,
1827 the party identification for the manufacturer is required when the
1828 manufacturer of trade item is populated.
1829
1830
1831 Class Name: ManufacturerOfTradeItem
1832
1833 Item Name: nameOfManufacturer
1834
1835 Core/Extension: E
1836 Global Local Status: G
1837 M/O/D: O
1838 Multiple Values Allowed: Y
1839 Neutral/Relationship Dependant: T.P.Neutral
1840 Product Hierarchy Reference Level: All
1841 Common value to all product hierarchy: Yes
1842 Type: AN
1843 Size: ..35
1844
1845 Definition: Descriptive name of the manufacturer of the trade item.
1846
1847 Examples:
1848
1849 Business Rules: May or may not be the brand owner. This is not the
1850 name of a party that assembles trade item. It is an optional field, manually
1851 maintained, that can identify the company that manufactures the product.
1852 This is a repeatable field.
1853
1854 Class Name: MarketingInformation
1855
1856 Item Name: campaignName
1857
1858 Core/Extension: E
1859 Global Local Status: G
1860 M/O/D: O
1861 Multiple Values Allowed: N
1862 Neutral/Relationship Dependant: T.P.Neutral
1863 Product Hierarchy Reference Level: All
1864 Common value to all product hierarchy: Yes
1865 Type: Description
1866 Size: ..70
1867
1868 Definition: Name of the sales or marketing campaign, for which the
1869 textile trade item is intended. Input of user-defined text in order to assign
1870 the item to a specific marketing campaign. Used to specify promotions,
1871 marketing.
1872
1873 Examples: Home Fashion theme such as 'Alexandra' or an Apparel
1874 theme such as '501 Blue'.
1875
1876 Business Rules:
1877
1878 Class Name: MarketingInformation
1879
1880 Item Name: campaignStartDate
1881
1882 Core/Extension: E
1883 Global Local Status: G
1884 M/O/D: O
1885 Multiple Values Allowed: N
1886 Neutral/Relationship Dependant: T.P.Neutral
1887 Product Hierarchy Reference Level: All
1888 Common value to all product hierarchy: Yes
1889 Type: Date
1890 Size: CCYY-MM-DD
1891
1892 Definition: The date suggested by the supplier for the campaign to start.
1893 It indicates the beginning of a marketing campaign.
1894
1895 Examples: 2005-02-01.
1896
1897 Business Rules:
1898
1899 Class Name: MarketingInformation
1900
1901 Item Name: campaignEndDate
1902
1903 Core/Extension: E
1904 Global Local Status: G
1905 M/O/D: O
1906 Multiple Values Allowed: N
1907 Neutral/Relationship Dependant: T.P.Neutral
1908 Product Hierarchy Reference Level: All
1909 Common value to all product hierarchy: Yes
1910 Type: Date
1911 Size: CCYY-MM-DD
1912
1913 Definition: The date suggested by the supplier for the campaign to end.
1914 It indicates the end of a marketing campaign.
1915
1916 Examples: 2005-05-01
1917
1918 Business Rules:
1919
1920
1921 Class Name: MarketingInformation
1922
1923 Item Name: specialItemCode
1924
1925 Core/Extension: E
1926 Global Local Status: G
1927 M/O/D: O
1928 Multiple Values Allowed: Y
1929 Neutral/Relationship Dependant: T.P.Neutral
1930 Product Hierarchy Reference Level: All
1931 Common value to all product hierarchy: Yes
1932 Type: Enumerated List
1933 Size: Not Applicable
1934
1935 Definition: This element identifies specific items for promotional or
1936 special tracking purposes. For example Dynamic Assortment: Chia Pets
1937 are sold individually to the consumer and each different Chia Pet is
1938 marked with a unique GTIN. The items are ordered by the case, which
1939 has its own unique GTIN. The case will contain a random assortment of
1940 Chia Pets. There is no guarantee that the same ratio of child items will be
1941 in a case from order to order but the total quantity of items in the case will
1942 remain the same.
1943
1944 A collateral item is a trade item delivered from a manufacturer to the retail
1945 selling floor that is not considered inventory and has no retail value.
1946
1947 A Gift with Purchase (GWP) is a trade item given to a consumer as part of
1948 a promotional event, contingent on the consumer making a purchase of
1949 another item or items. A Gift with Purchase is considered inventory and
1950 has no retail value.
1951
1997
1998 Class Name: MarketingInformation
1999
2000 Item Name: tradeItemMarketingMessage
2001
2002 Core/Extension: E
2003 Global Local Status: G
2004 M/O/D: O
2005 Multiple Values Allowed: N
2006 Neutral/Relationship Dependant: T.P.Neutral
2007 Product Hierarchy Reference Level: All
2008 Common value to all product hierarchy: Yes
2009 Type: Long Description
2010 Size: 1000
2011
2012 Definition: Marketing message associated to the Trade item.
2013
2014 Examples:'Quality in Style'.
2015
2016 Business Rules:
2017
2018
2019 Class Name: MaterialComposition
2020
2021 Item Name: materialCode
2022
2023 Core/Extension: E
2024 Global Local Status: G
2025 M/O/D: O
2026 Multiple Values Allowed: N
2027 Neutral/Relationship Dependant: T.P.Neutral
2028 Product Hierarchy Reference Level: All
2029 Common value to all product hierarchy: Yes
2030 Type: Multi Description
2031 Size: 70
2032
2033 Definition: This element indicates the product material code that gives
2034 the composition of the trade item's first main material up to six material
2035 short codes that can be given in descending order of their respective
2036 percentages. This element may be used to specify agency code or
2037 country specific code used to indicate materials that the trade item
2038 consists of.
2039
2040 Examples: CO Cotton; PE Polyethylene; PA Polyamide.
2041
2042 Business Rules: materialCode and materialAgencyCode are paired
2043 elements; if one is used, the other must be present. These fields are
2044 used in conjunction with the percentage. materialCode should match the
2045 value of materialContent if both are populated.
2046
2297
2298 Class Name: Ordering And Selling Unit Of Measure
2299
2300 Item Name: orderingUnitOfMeasure
2301
2302 Core/Extension: E
2303 Global Local Status: G
2304 M/O/D: O
2305 Multiple Values Allowed: N
2306 Neutral/Relationship Dependant: T.P.Neutral
2307 Product Hierarchy Reference Level: All
2308 Common value to all product hierarchy: Yes
2309 Type: String
2310 Size: 70
2311
2312 Definition: The alternate Unit of Measure of how Trade Items are
2313 ordered by the Retailer under one Unit of Measure, but sold under
2314 another Unit of Measure.
2315
2316 Example: A Spool of wire ordered by the spool and sold by lineal foot;
2317 Lumber ordered by board footage and sold by piece.
2318
2319 Business Rules: EAN.UCC standards reference the UN/CEFACT
2320 Recommendation 20 list for the possible Unit of Measure.
2321 orderingUnitOfMeasure is a string and is optional.
2322
2323
2324 Class Name: Ordering And Selling Unit Of Measure
2325
2326 Item Name: sellingUnitOfMeasure
2327
2328 Core/Extension: E
2329 Global Local Status: G
2330 M/O/D: O
2331 Multiple Values Allowed: N
2332 Neutral/Relationship Dependant: T.P.Neutral
2333 Product Hierarchy Reference Level: All
2334 Common value to all product hierarchy: Yes
2335 Type: String
2336 Size: 70
2337
2338 Definition: Describes the measurement used for selling unit of the Trade
2339 Item to the end consumer. A Trade Item may have only one Unit of
2340 Measure.
2341
2342 Example: Each, pair, case, roll, set box, by the foot, by the sheet. The
2343 Retailers require this if the Item is marked as a Consumer Unit. Only
2344 values from the enumerated list can be chosen from the UN/CEFACT.
2345
2346 Business Rules:
2397
2398
2399 Class Name: PackagingMarking
2400
2401 Item Name: isBarcodeOnThePackage- this boolean question is answered by
2402 the population of Bar Code Type. It is thus not represented in the model and the
2403 schemas.
2404
2405 Core/Extension: E
2406 Global Local Status: G
2407 M/O/D: M
2408 Multiple Values Allowed: N
2409 Neutral/Relationship Dependant: T.P.Neutral
2410 Product Hierarchy Reference Level: All
2411 Common value to all product hierarchy: No
2412 Type: Boolean
2413 Size: Not Applicable
2414
2415 Definition: Indication if the trade item is physically bar-coded with the
2416 primary trade item identification number. This is a y/n (Boolean) where Y
2417 equals trade item is bar-coded.
2418
2419 Examples:
2420
2421 Business Rules: Boolean Y/N; Y= bar-coded N= not bar-coded
2422 Technical Note: This Boolean question is answered by the application of
2423 class “Bar Code Type List”. If the Bar Code Type List class (telling which
2424 barcodes are on the package) exists, then there is a barcode on the
2425 package. The attribute is derived from the Bar Code Type List and is not
2426 in the model.
2427
2428
2429 Class Name: PackagingMarking
2430
2431 Item Name: isPackagingMarkedReturnable
2432
2433 Core/Extension: E
2434 Global Local Status: G
2435 M/O/D: M
2436 Multiple Values Allowed: N
2437 Neutral/Relationship Dependant: T.P.Neutral
2438 Product Hierarchy Reference Level: All
2439 Common value to all product hierarchy: No
2440 Type: Boolean
2441 Size: Not Applicable
2442
2443 Definition: trade item has returnable packaging. This is a yes/no
2444 (Boolean) where yes equals package can be returned.
2445
2446 Examples:
2447
2448 Business Rules: Boolean Y/N; Y= marked returnable, N= not returnable.
2449 Attribute applies to returnable packaging with or without deposit.
2450
2451
2452 Class Name: PackagingMarking
2453
2454 Item Name: isPackagingMarkedWithIngredients
2455
2456 Core/Extension: E
2457 Global Local Status: L
2458 M/O/D: O
2459 Multiple Values Allowed: N
2460 Neutral/Relationship Dependant: T.P.Neutral
2461 Product Hierarchy Reference Level: Each
2462 Common value to all product hierarchy: No
2463 Type: Boolean
2464 Size: Not Applicable
2465
2466 Definition: trade item packaging contains information pertaining to its
2467 ingredients. trade item ingredients are required to be shown on the trade
2468 item (normally at base trade item level). This is a yes/no (Boolean) where
2469 yes equals marked with ingredients.
2470
2471 Examples:
2472
2473 Business Rules: Boolean Y/N where Y=marked with ingredients , N=not
2474 marked with ingredients. trade item ingredients are required to be shown
2475 on the trade item (normally consumer unit level) Sector specific and
2476 geographical extension. List of ingredients can be legally required in
2477 some countries for limited trade item sectors.
2478
2479
2480 Class Name: PackagingMarking
2481
2482 Item Name: OfferOnPack
2483
2484 Core/Extension: E
2485 Global Local Status: L
2486 M/O/D: O
2487 Multiple Values Allowed: N
2488 Neutral/Relationship Dependant: T.P.Neutral
2489 Product Hierarchy Reference Level: Each
2490 Common value to all product hierarchy: No
2491 Type: String
2492 Size: 70
2493
2494 Definition: Contains details of any on pack product offer (consumer or
2495 traded).
2496
2670
2671 Class Name: PackagingMaterial
2672
2673 Item Name: packagingMaterialCode
2674
2675 Core/Extension: E
2676 Global Local Status: G/L
2677 M/O/D: O
2678 Multiple Values Allowed: Y
2679 Neutral/Relationship Dependant: T.P.Neutral
2680 Product Hierarchy Reference Level: All
2681 Common value to all product hierarchy: No
2682 Type: AN
2683 Size: ..3
2684
2685 Definition: Code source needs to be defined. Currently a European
2686 Union table of code lists exists for this requirement. The code list
2687 required to identify the packaging material of the trade item.
2688
2689 Examples: "GL" (glass) "AL" (Aluminum)
2690
2691 Business Rules: Can be repeated for multi-material packaging and
2692 linked to packaging weight.
2693
2694
2695 Class Name: PackagingMaterial
2696
2697 Item Name: packagingMaterialCodeListMaintenanceAgency
2698
2699 Core/Extension: E
2700 Global Local Status: G/L
2701 M/O/D: D
2702 Multiple Values Allowed: Y
2703 Neutral/Relationship Dependant: T.P.Neutral
2704 Product Hierarchy Reference Level: All
2705 Common value to all product hierarchy: No
2706 Type: AN
2707 Size: ..35
2708
2709 Definition: Agency needs to be defined. The agency or agencies
2710 controlling the packaging code lists of each country. Mandatory if
2711 packaging material code is populated.
2712
2713 Examples:
2714
2715 Business Rules: Dependent on field packagingMaterialCode
2716
2717
2718 Class Name: PackagingMaterial
2719
2720 Item Name: packagingMaterialCompositionQuantity
2721
2722 Core/Extension: E
2723 Global Local Status: G/L
2724 M/O/D: D
2725 Multiple Values Allowed :Y
2726 Neutral/Relationship Dependant: T.P.Neutral
2727 Product Hierarchy Reference Level: All
2728 Common value to all product hierarchy: No
2729 Type: Multi-Measurement
2730 Size: Decimal 15, String 3 for Unit Of Measure
2731
2732 Definition: The quantity of the packaging of the trade item. Can be
2733 weight, volume or surface, can vary by country.
2734
2735 Examples: "15 grm", Value, amount, eaches, etc.
2736
2737 Business Rules: Can be repeated for multi-material packaging and must
2738 be associated with a valid ISO language code from the attached table.
2739 Has to be associated with valid UOM. See Section 4.6 of the
2740 Implementation Considerations and Concerns for more details.
2741
2742
2743 Class Name: PackagingMaterial
2744
2745 Item Name: packagingMaterialDescription
2746
2747 Core/Extension: E
2748 Global Local Status: G/L
2749 M/O/D: D
2750 Multiple Values Allowed: Y
2751 Neutral/Relationship Dependant: T.P.Neutral
2752 Product Hierarchy Reference Level: All
2753 Common value to all product hierarchy: No
2754 Type: Multi Short Description
2755 Size: 35
2756
2757 Definition: The system generated text description equivalent of the
2758 packaging material code.
2759
2760 Examples: "Glass" "Aluminum"
2761
2762 Business Rules: Can be repeated for multi-material packaging and
2763 linked to packaging weight. As a description text field, this data element is
2764 repeatable for each language used and must be associated with a valid
2765 ISO language code from the attached table. Dependent on the field
2866
2867 Item Name: packagingTypeDescription
2868
2869 Core/Extension: E
2870 Global Local Status: G
2871 M/O/D: O
2872 Multiple Values Allowed: Y
2873 Neutral/Relationship Dependant: T.P.Neutral
2874 Product Hierarchy Reference Level: All
2875 Common value to all product hierarchy: No
2876 Type: AN
2877 Size: ..35
2878
2879 Definition: System generated text description of the type of packaging
2880 used for the trade item. For example, box or carton.
2881
2882 Examples: "Box", "Bottle"
2883
2884 Business Rules: List of authorized text description values based on UN-
2885 ECE 21 Recommendations - EANCOM 7065. Can be repeated. System
2886 generated field.
2887
2888
2889 Class Name: PegMeasurements (child class of TradeItemMeasurements)
2890
2891 Item Name: pegHoleNumber
2892
2893 Core/Extension: E
2894 Global Local Status: G
2895 M/O/D: D
2896 Multiple Values Allowed: N
2897 Neutral/Relationship Dependant: T.P.Neutral
2898 Product Hierarchy Reference Level: Each
2899 Common value to all product hierarchy: No
2900 Type: N
2901 Size: Unbounded
2902
2903 Definition: Used to indicate the peg hole numbers when more than one
2904 hole is present in the product or packaging. Peg holes should be
2905 numbered from the upper left corner of the front of the package to the
2906 bottom right corner. The peg holes should be identified from left to right,
2907 top to bottom with left to right having precedence. The number of peg
2908 holes and their measurements must be determined following the
2909 orientation of the product. Product orientation is based upon the General
2910 EAN.UCC Specification. Required if the trade item is displayed on a peg
2911 board.
2912
2913 Examples: 1
2914
2915 Business Rules: Required if the item has a peg hole. Multiple peg holes
2916 are allowed per product.
2917
2918
2919 Class Name: PegMeasurements (child class of TradeItemMeasurements)
2920
2921 Item Name: pegHorizontal
2922
2923 Core/Extension: E
2924 Global Local Status: G
2925 M/O/D: O
2926 Multiple Values Allowed: N
2927 Neutral/Relationship Dependant: T.P.Neutral
2928 Product Hierarchy Reference Level: Each
2929 Common value to all product hierarchy: No
2930 Type: Multi-Measurement Value
2931 Size: Decimal 15, String 3 for Unit Of Measure
2932
2933
2934 Definition: Used to indicate the horizontal distance from the edge of the
2935 trade item to the center of the hole into which the peg is inserted when
2936 the trade item is displayed on a pegboard.
2937
2938 Examples: "2 INH"
2939
2940 Business Rules: Required if the trade item is displayed on a peg board.
2941 Has to be associated with a valid UOM.
2942
2943
2944 Class Name: PegMeasurements (child class of TradeItemMeasurements)
2945
2946 Item Name: pegVertical
2947
2948 Core/Extension: E
2949 Global Local Status: G
2950 M/O/D: O
2951 Multiple Values Allowed: N
2952 Neutral/Relationship Dependant: T.P.Neutral
2953 Product Hierarchy Reference Level: Each
2954 Common value to all product hierarchy: No
2955 Type: Multi-Measurement Value
2956 Size: Decimal 15, String 3 for Unit Of Measure
2957
2958 Definition: Used to indicate the vertical distance from the edge of the
2959 trade item to the center of the hole into which the peg is inserted when
2960 the trade item is displayed on a pegboard. The hole into which the peg is
2961 inserted when the trade item is displayed on a pegboard. The
2962 measurement is always taken from the top edge of the trade item to the
2963 hole.
2964
3015
3016 Business Rules: As monetary amount field, this data element must be
3017 associated with a valid unit of measure. See implementation notes for
3018 complete table. GTIN allocation rules state that price is not a relevant
3019 criteria for changing a GTIN except when the price is printed as a part of
3020 the trade item’s packaging.
3021 Becomes mandatory when priceOnPackIndicator = "Y". In this case, the
3022 priceOnPack becomes Global (can not vary per Target Market).
3023 See Section 4.5 of Implementation Considerations and Concerns for
3024 more details.
3025
3026
3027 Class Name: PrivateInformation
3028
3029 Item Name: isTradeItemInformationPrivate Æthis boolean question is answered
3030 by populating partyReceivingPrivateData.
3031
3032
3033 Core/Extension: E
3034 Global Local Status: G
3035 M/O/D: M
3036 Multiple Values Allowed: N
3037 Neutral/Relationship Dependant: T.P.Neutral
3038 Product Hierarchy Reference Level: All
3039 Common value to all product hierarchy: Yes
3040 Type: Boolean
3041 Size: Not Applicable
3042
3043 Definition: Indicator to qualify whether master data is publicly available to
3044 any inquirer or is restricted to specific private user. This is a y/n (Boolean)
3045 where y equals non-public. If yes, then must have associated PARTY ID
3046 for whom the information is intended.
3047
3048 Examples: Consumer unit A is public. Display configuration B, which
3049 contains public consumer unit A, is marked non-public, as it was built for
3050 retailer C. Pallet GTIN D, which is made up of Display B, is also marked
3051 non-public, only available to retailer C.
3052
3053 Business Rules: Trade item hierarchy level impact - if GTIN is marked
3054 non-public, all higher trade item hierarchy levels are non-public. Lower
3055 trade item hierarchy levels can still be public. This Boolean question is
3056 answered by application of class Private Information.
3057
3058
3059 Class Name: PrivateInformation
3060
3061 Item Name: partyReceivingPrivateData – represented by relationship to Party
3062 Identification.
3063
3064 Core/Extension: E
3065 Global Local Status: G
3066 M/O/D: D
3067 Multiple Values Allowed: Y
3068 Neutral/Relationship Dependant:T.P.Dependent
3069 Product Hierarchy Reference Level: All
3070 Common value to all product hierarchy: Yes*
3071 Type: PartyIdentification
3072 Size: Not Applicable
3073
3074 Definition: Unique location number identifying the party who is allowed
3075 access to the information by the data owner.
3076
3077 Examples: Refer to the following websites for specific directions on how
3078 to construct global location numbers - www.uc-council.org or www.ean-
3079 int.org
3080
3081 Business Rules: There can be multiple instances of
3082 partyReceivingPrivateData. This is handled through the zero to many
3083 relationship between PrivateInformation and
3084 TradingPartnerNeutralTradeItemInformation.
3085
3086 While the class ManufacturerOfTradeItem is optional, the party
3087 identification for the brand owner is required when a manufacturer is
3088 present.
3089
3090
3091 Class Name: Season
3092
3093 Item Name: seasonalAvailabilityEndDate
3094
3095 Core/Extension: E
3096 Global Local Status: L
3097 M/O/D: O
3098 Multiple Values Allowed: N
3099 Neutral/Relationship Dependant: T.P.Neutral
3100 Product Hierarchy Reference Level: Each
3101 Common value to all product hierarchy: No
3102 Type: Date
3103 Size: CCYYMMDD
3104
3105 Definition: This element indicates the end date of the trade item's
3106 seasonal availability.The seasonal availability can be different from the
3107 ordering time and especially from the dispatching time. The availability is
3108 more like an intention of the supplier as to how long he wants to offer the
3109 product. The dispatching time is more useful for the DC and the outlet
3110 warehousing.
3111
3112 Examples:
3113
3114 Business Rules:
3115
3116 Class Name: Season
3117
3118 Item Name: seasonalAvailabilityStartDate
3119
3120 Core/Extension: E
3121 Global Local Status: L
3122 M/O/D: O
3123 Multiple Values Allowed: N
3124 Neutral/Relationship Dependant: T.P.Neutral
3125 Product Hierarchy Reference Level: Each
3126 Common value to all product hierarchy: No
3127 Type: Date
3128 Size: CCYYMMDD
3129
3130 Definition: This element indicates the start date of the trade item's
3131 seasonal availability. Reference related attribute in Item document.
3132
3133 European Requirement. The seasonal availability can be different from
3134 the ordering time and especially from the dispatching time. The
3135 availability is more like an intention of the supplier as to how long he
3136 wants to offer the product. The dispatching time is more useful for the DC
3137 and the outlet warehousing.
3138
3139 Examples:
3140
3141 Business Rules:
3142
3143
3144 Class Name: Season
3145
3146 Item Name: seasonCalendarYear:
3147
3148 Core/Extension: E
3149 Global Local Status: L
3150 M/O/D: O
3151 Multiple Values Allowed: Y
3152 Neutral/Relationship Dependant: T.P.Neutral
3153 Product Hierarchy Reference Level: Each
3154 Common value to all product hierarchy: No
3155 Type: Year
3156 Size: CCYY
3157
3158 Definition: This element indicates the calendar year in which the trade
3159 item is seasonally available.This item is seasonally available in the year
3160 “2002". European Requirement. This element applies to cases where the
3161 supplier has items in many different seasons or if multiple calendar years
3162 were involved. This attribute might be considered as an implementation
3163 attribute that could be done in different manners in the GDSN and in the
3164 one-to-one environment. Can be used for merchandising.
3165
3166 Examples:
3167
3168 Business Rules:
3169
3170
3171 Class Name: Season
3172
3173 Item Name: seasonParameter:
3174
3175 Core/Extension: E
3176 Global Local Status: L
3177 M/O/D: O
3178 Multiple Values Allowed: Y
3179 Neutral/Relationship Dependant: T.P.Neutral
3180 Product Hierarchy Reference Level: Each
3181 Common value to all product hierarchy: No
3182 Type: Enumerated List
3183 Size: Not Applicable
3184
3185 Definition: Indication of the season, in which the trade item is available,
3186 i.e. assignment to one of the following collection periods: spring/summer,
3187 autumn/ winter or all year around. It is repeatable if more than one
3188 season is indicated: Spring, Summer, Autumn, Winter, and All year
3189 (available throughout the year). The seasonal parameter is more an
3190 information for the search of data.
3191
3192 Examples:
3193
3194 Business Rules:
3195
3196 Class Name: Season
3197
3198 Item Name: seasonName:
3199
3200 Core/Extension: E
3201 Global Local Status: L
3202 M/O/D: O
3203 Multiple Values Allowed: Y
3204 Neutral/Relationship Dependant: T.P.Neutral
3205 Product Hierarchy Reference Level: Each
3206 Common value to all product hierarchy: No
3357
3358 Examples:
3359
3360 Business Rules: If color code is indicated, colorCodeListAgency is
3361 required. EANCOM code list is to be used. This is used by certain
3362 industries which maintain specific color code lists.
3363
3364
3365 Class Name: TradeItemColorDescription
3366
3367 Item Name: colorDescription
3368
3369 Core/Extension: E
3370 Global Local Status: G
3371 M/O/D: O
3372 Multiple Values Allowed: Y
3373 Neutral/Relationship Dependant: T.P.Neutral
3374 Product Hierarchy Reference Level: Each
3375 Common value to all product hierarchy: No
3376 Type: Multi Description
3377 Size: ..70
3378
3379 Definition: Free text description of the color of the trade item.
3380
3381 Examples: "Dark burgundy"
3382
3383 Business Rules: Free from text. As description text field. This data
3384 element is repeatable for each language used and must be associated
3385 with a valid ISO language code from the attached table.
3386
3387
3388 Class Name: TradeItemCoupon
3389
3390 Item Name: couponFamilyCode
3391
3392 Core/Extension: E
3393 Global Local Status: L
3394 M/O/D: O
3395 Multiple Values Allowed: N
3396 Neutral/Relationship Dependant: T.P.Neutral
3397 Product Hierarchy Reference Level: Each
3398 Common value to all product hierarchy: No
3399 Type: AN
3400 Size: 3
3401
3402 Definition: A code assigned by the vendor to a single trade item or to
3403 families of consumer trade items that can be used by in store scanners in
3404 conjunction with a U.P.C. coupon value code for coupon value discount
3405 when the proper trade item has been purchased.
3406
3407 Examples:
3408
3409 Business Rules: It only applies to the consumer unit. Note this is treated
3410 in the XML as a mandatory attribute in an optional class.
3411
3412
3413 Class Name: TradeItemDateInformation
3414
3415 Item Name: canceledDate
3416
3417 Core/Extension: E
3418 Global Local Status: G
3419 M/O/D: O
3420 Multiple Values Allowed: N
3421 Neutral/Relationship Dependant: T.P.Neutral
3422 Product Hierarchy Reference Level: All
3423 Common value to all product hierarchy: No
3424 Type: Date
3425 Size: CCYY-MM-DD
3426
3427 Definition: Communicates cancelation of the launch of a trade item that
3428 was never and will never be manufactured, but may have been presented
3429 to buyers. Allows the reuse of the GTIN 12 months after cancellation.
3430
3431 Examples: “2002-11-20”
3432
3433 Business Rules: Use ISO 8601 date format CCYY-MM-DD
3434
3435
3436 Class Name: TradeItemDateInformation
3437
3438 Item Name: consumerAvailabilityDateTime
3439
3440 Core/Extension: E
3441 Global Local Status: G/L
3442 M/O/D: O
3443 Multiple Values Allowed: N
3444 Neutral/Relationship Dependant: T.P.Neutral
3445 Product Hierarchy Reference Level: Each
3446 Common value to all product hierarchy: No
3447 Type: DateTime
3448 Size: CCYY-MM-DDTHH:MM:SS
3449
3450 Definition: The first date/time that the buyer is allowed to sell the trade
3451 item to consumers. Usually related to a specific geography. ISO 8601
3452 date format CCYY-MM-DDTHH:MM:SS.
3453
3454 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm
3455
3456 Business Rules: Time is expressed in the time zone of the target
3457 market where the trade item is intended for resale to consumers. ISO
3458 8601 date format CCYY-MM-DDTHH:MM:SS.
3459
3460
3461 Class Name: TradeItemDateInformation
3462
3463 Item Name: discontinuedDate
3464
3465 Core/Extension: E
3466 Global Local Status: G/L
3467 M/O/D: O
3468 Multiple Values Allowed: N
3469 Neutral/Relationship Dependant: T.P Neutral
3470 Product Hierarchy Reference Level: All
3471 Common value to all product hierarchy: No
3472 Type: Date
3473 Size: CCYY-MM-DD
3474
3475 Definition: Communicate the date on which the trade item is no longer to
3476 be manufactured. Allows the reuse of the GTIN after 48 months with the
3477 explicit exception of Apparel, being 30 months and the implicit exception
3478 for specialty products (e.g., steel beams).
3479
3480 Examples: “2002-02-05”
3481
3482 Business Rules: ISO 8601 date format CCYY-MM-DD
3483
3484
3485 Class Name: TradeItemDateInformation
3486
3487 Item Name: effectiveDate
3488
3489 Core/Extension: E
3490 Global Local Status: G/L
3491 M/O/D: M
3492 Multiple Values Allowed: N
3493 Neutral/Relationship Dependant: T.P.Neutral
3494 Product Hierarchy Reference Level: All
3495 Common value to all product hierarchy: No
3496 Type: Date
3497 Size: CCYY-MM-DD
3498
3499 Definition: The date on which the information contents of the master data
3500 version are valid. Valid = correct or true. This effective date can be used
3501 for initial trade item offering, or to mark a change in the information
3502 related to an existing trade item. This date would mark when these
3503 changes take effect.
3504
3505 Examples: "2002-02-05"
3506
3507 Business Rules: This date will be used for version management. The
3508 effective date can be different from publication date. If a new user begins
3509 to synchronize data on this GTIN after the original effective date, the
3510 effective date = the publication date for the new user. Time zone of the
3511 information provider may be noted in future drafts of the GDD. ISO 8601
3512 date format CCYY-MM-DD
3513
3514
3515 Class Name: TradeItemDateInformation
3516
3517 Item Name: endAvailabilityDateTime
3518
3519 Core/Extension: E
3520 Global Local Status: G/L
3521 M/O/D: O
3522 Multiple Values Allowed: N
3523 Neutral/Relationship Dependant: N/T.P.Dependent
3524 Product Hierarchy Reference Level: All
3525 Common value to all product hierarchy: No
3526 Type: DateTime
3527 Size: CCYY-MM-DDTHH:MM:SS.
3528
3529 Definition: The date from which the trade item is no longer available from
3530 the information provider, including seasonal or temporary trade item and
3531 services.
3532
3533 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm
3534
3535 Business Rules: If the trade item is public only one date is valid per
3536 GTIN, GLN, TM combination. If Item is private there can be more than 1
3537 value per TM. There is only one "end availability date" per GTIN/GLN/TM
3538 combination at any given time. In the case of seasonal trade items, only
3539 one start/end cycle can be in the data set version being synchronized.
3540 Therefore, a trade item cannot have multiple start/stop availability dates
3541 associated with it at any given time. Field is optional since most trade
3542 items are offered in an open ended environment. Is trading partner
3543 neutral for public trade items, trading partner dependent for private trade
3544 items.
3545
3546 Class Name: TradeItemDateInformation
3547
3548 Item Name: endDateMaximumBuyingQuantity:
3549
3550 Core/Extension: E
3551 Global Local Status: G/L
3552 M/O/D: O
3553 Multiple Values Allowed: N
3554 Neutral/Relationship Dependant: N/T.P.Dependent
3555 Product Hierarchy Reference Level: All
3706 M/O/D: M
3707 Multiple Values Allowed: N
3708 Neutral/Relationship Dependant: T.P.Neutral
3709 Product Hierarchy Reference Level: All
3710 Common value to all product hierarchy: No
3711 Type: DateTime
3712 Size: CCYY-MM-DDTHH:MM:SS.
3713
3714 Definition: A system generated value identifying the date and time a
3715 record was last updated. This field allows the data pool to control the
3716 trade item data version, and allows the information user to determine if
3717 trade item data should be downloaded. Date format CCYY-MM-
3718 DDTHH:MM:SS.
3719
3720 Examples: "2002-02-05T17:00:00" = February 5th 2002 5:00:00pm
3721
3722 Business Rules: System generated by the home data pool. Date format
3723 defined in ISO 8601- CCYY-MM-DDTHH:MM:SS
3724
3725
3726
3727 Class Name: TradeItemDateInformation
3728
3729 Item Name: publicationDate
3730
3731 Core/Extension: E
3732 Global Local Status: G/L
3733 M/O/D: M
3734 Multiple Values Allowed: N
3735 Neutral/Relationship Dependant: N/T.P.Dependent
3736 Product Hierarchy Reference Level: All
3737 Common value to all product hierarchy: No
3738 Type: Date
3739 Size: CCYY-MM-DD
3740
3741 Definition: A date on which all static data associated with the trade item
3742 becomes available for viewing and synchronization.
3743
3744 Examples: "2002-02-05" February 5th 2002
3745
3746 Business Rules: There is only one release date per GTIN/TM/GLN
3747 combination. If a private trade item, the date can be trading partner
3748 dependent, if public, it is a trading partner neutral field. Date format is
3749 defined in ISO8601 –CCYY-MM-DD.
3750
3751
3752 Class Name: TradeItemDateInformation
3753
3754 Item Name: startAvailabilityDateTime
3755
3756 Core/Extension: E
3757 Global Local Status: G/L
3758 M/O/D: M
3759 Multiple Values Allowed: N
3760 Neutral/Relationship Dependant: N/T.P.Dependent
3761 Product Hierarchy Reference Level: All
3762 Common value to all product hierarchy: No
3763 Type: DateTime
3764 Size: CCYY-MM-DDTHH:MM:SS
3765
3766 Definition: The date (CCYY-MM-DDTHH:MM:SS) from which the trade
3767 item becomes available from the supplier, including seasonal or
3768 temporary trade item and services.
3769
3770 Examples: "2002-02-05T17:00:00" February 5th 2002 5:00:00pm
3771
3772 Business Rules: If the trade item is public only one date (CCYY-MM-
3773 DDTHH:MM:SS) is valid per GTIN, GLN, TM combination. If Item is
3774 private there can be more than 1 value per TM. Needs to be earlier than
3775 "end availability date" This date indicates when the trade item can first be
3776 ordered by the buyer from the information provider. This date can be
3777 trading partner dependent if the trade item or service is defined as
3778 private. It is trading partner neutral if the trade item/service is public. It
3779 does not indicate when this trade item becomes available to the end
3780 consumer (see first sale date) There is only one start availability date per
3781 GTIN/GLN/TM combination. Date format is ISO8601 – CCYY-MM-
3782 DDTHH:MM:SS.
3783
3784
3785 Class Name: TradeItemDateInformation
3786
3787 Item Name: startDateMaximumBuyingQuantity
3788
3789 Core/Extension: E
3790 Global Local Status: G/L
3791 M/O/D: O
3792 Multiple Values Allowed: N
3793 Neutral/Relationship Dependant: N/T.P.Dependent
3794 Product Hierarchy Reference Level: All
3795 Common value to all product hierarchy: No
3796 Type: DateTime
3797 Size: CCYY-MM-DDTHH:MM:SS
3798
3799 Definition: The start dateand time for when the maximum buying quantity
3800 is available to the trading partner.
3903
3904
3905 Class Name: TradeItemHandlingInformation
3906
3907 Item Name: stackingFactor
3908
3909 Core/Extension: E
3910 Global Local Status: G
3911 M/O/D: O
3912 Multiple Values Allowed: No
3913 Neutral/Relationship Dependant: T.P.Neutral
3914 Product Hierarchy Reference Level: All
3915 Common value to all product hierarchy: No
3916 Type: N
3917 Size: ..6
3918
3919 Definition: A factor that determines the maximum stacking for the
3920 product. Indicates the number of levels the product may be stacked.
3921
3922 Examples: Factor of "2" = trade item is stackable 2 high
3923
3924 Business Rules: Factor will indicate how many levels the particular
3925 product may be stacked in. The counting of the levels will always
3926 commence at 1 not 0.
3927
3928
3929 Class Name: TradeItemHandlingInformation
3930
3931 Item Name: stackingWeightMaximum
3932
3933 Core/Extension: E
3934 Global Local Status: G
3935 M/O/D: O
3936 Multiple Values Allowed: N
3937 Neutral/Relationship Dependant: T.P.Neutral
3938 Product Hierarchy Reference Level: All
3939 Common value to all product hierarchy: No
3940 Type: Multi Measurement Value
3941 Size: Decimal 15, String 3 for Unit Of Measure
3942
3943 Definition: The maximum admissible weight that can be stacked on the
3944 trade item. This uses a measurement consisting of a unit of measure and
3945 a value. This will be used for transport or storage to allow user to know by
3946 weight how to stack different trade item one on top of the other.
3947
3948 Examples: "500 KGM”
3949
3950 Business Rules: Used in conjunction with unit of measure.
3951
3952
4003
4004 Class Name: TradeItemHazardousInformation
4005
4006 Item Name: dangerousGoodsRegulationCode
4007
4008 Core/Extension: E
4009 Global Local Status: G
4010 M/O/D: D
4011 Multiple Values Allowed: Y
4012 Neutral/Relationship Dependant: T.P.Neutral
4013 Product Hierarchy Reference Level: All
4014 Common value to all product hierarchy: No
4015 Type: AN
4016 Size: 3
4017
4018 Definition: Code indicating the classification system(s) of dangerous
4019 goods and/or the Agency(ies) responsible for it.
4020
4021 Examples: "ADR" European agreement on the international carriage of
4022 dangerous goods on roads.
4023
4024 Business Rules: Various systems (ADR, RID, US49, IATA, etc.) exist
4025 and are used for hazard classification and identification.
4026
4027 Repeatable field
4028 http://www.unece.org/trade/untdid/d99b/tred/tred8273.htm
4029
4030 Hazardous attributes relate to supply chain handling (e.g., transport,
4031 storage, handling).
4032
4033
4034 Class Name: TradeItemHazardousInformation
4035
4036 Item Name: flashPointTemperature
4037
4038 Core/Extension: E
4039 Global Local Status: G
4040 M/O/D: D
4041 Multiple Values Allowed: Y
4042 Neutral/Relationship Dependant: T.P.Neutral
4043 Product Hierarchy Reference Level: Each
4044 Common value to all product hierarchy: No
4045 Type: Measurement
4046 Size: Decimal 15, String 3 for Unit Of Measure
4047
4048 Definition: The lowest temperature at which a substance gives off a
4049 sufficient vapor to support combustion. This uses a measurement
4050 consisting of a unit of measure and value.
4051
4052 Examples: -
4053
4054 Business Rules: Information required when
4055 dangerousGoodsRegulationcode is populated.
4056 Expressed in Celsius (or Centigrade) or Fahrenheit
4057 Format defined by UN/EDIFACT 7106
4058 Has to be associated with valid UoM. Hazardous attributes relate to
4059 supply chain handling (e.g., transport, storage, handling).
4060
4061
4062 Class Name: TradeItemHierarchy
4063
4064 Item Name: quantityOfCompleteLayersContainedInATradeItem
4065
4066 Core/Extension: E
4067 Global Local Status: G
4068 M/O/D: O
4069 Multiple Values Allowed: N
4070 Neutral/Relationship Dependant: T.P.Neutral
4071 Product Hierarchy Reference Level: Mixed Mod, Pallet, Display/
4072 Shipper, Case, Pack
4073 Common value to all product hierarchy: No
4074 Type: N
4075 Size: 6
4076
4077 Definition: The number of layers of the base trade item found in a trade
4078 item. Does not apply to the base trade item unit.
4079
4080 Examples:
4081
4082 Business Rules: Only applies to logistic units (e.g. pallet, case, etc)
4083
4084
4085 Class Name: TradeItemHierarchy
4086
4087 Item Name: quantityOfLayersPerPallet
4088
4089 Core/Extension: E
4090 Global Local Status: G
4091 M/O/D: O
4092 Multiple Values Allowed: N
4093 Neutral/Relationship Dependant: T.P.Neutral
4094 Product Hierarchy Reference Level: Each
4095 Common value to all product hierarchy: No
4096 Type: N
4097 Size: 6
4098
4099 Definition: The number of layers that a pallet contains. Only used if the
4100 pallet has no GTIN. It indicates the number of layers that a pallet
4101 contains, according to supplier or retailer preferences.
4102
4103 Examples:
4104
4105 Business Rules: Only used if the pallet has no GTIN. In this case it
4106 applies to the highest level of the item hierarchy and only 1 pallet
4107 configuration can be provided. It is highly recommended to use GTIN for
4108 Pallet identification.
4109
4110
4111 Class Name: TradeItemHierarchy
4112
4113 Item Name: quantityOfTradeItemsContainedInACompleteLayer
4114
4115 Core/Extension: E
4116 Global Local Status: G
4117 M/O/D: O
4118 Multiple Values Allowed: N
4119 Neutral/Relationship Dependant: T.P.Neutral
4120 Product Hierarchy Reference Level: Mixed Mod, Pallet,
4121 Display/Shipper, Case, Pack
4122 Common value to all product hierarchy: No
4123 Type: N
4124 Size: 6
4125
4126 Definition: The number of trade items contained in a complete layer of a
4127 higher packaging configuration. Used in hierarchical packaging structure
4128 of a trade item. Cannot be used for trade item base unit.
4129
4130 Examples:
4131
4132 Business Rules: Only applies to logistic units (e.g. pallet, case, etc)
4133
4134
4135 Class Name: TradeItemHierarchy
4136
4137 Item Name: quantityOfTradeItemsPerPallet
4138
4139 Core/Extension: E
4140 Global Local Status: G
4141 M/O/D: O
4142 Multiple Values Allowed: N
4143 Neutral/Relationship Dependant: T.P.Neutral
4144 Product Hierarchy Reference Level: Pallet, Mixed Mod
4145 Common value to all product hierarchy: No
4146 Type: N
4147 Size: 6
4148
4149 Definition: The number of trade items contained in a pallet. Only used if
4150 the pallet has no GTIN. It indicates the number of trade items placed on a
4151 pallet according to supplier or retailer preferences.
4152
4153 Examples:
4154
4155 Business Rules: Only used if the pallet has no GTIN. In this case it
4156 applies to the highest level of the item hierarchy and only 1 pallet
4157 configuration can be provided. It is highly recommended to use GTIN for
4158 Pallet identification.
4159
4160
4161 Class Name: TradeItemHierarchy
4162
4163 Item Name: quantityOfTradeItemsPerPalletLayer
4164
4165 Core/Extension: E
4166 Global Local Status: G
4167 M/O/D: O
4168 Multiple Values Allowed: N
4169 Neutral/Relationship Dependant: T.P.Neutral
4170 Product Hierarchy Reference Level: Pallet, MixedMod
4171 Common value to all product hierarchy: No
4172 Type: N
4173 Size: 6
4174
4175 Definition: The number of trade items contained on a single layer of a
4176 pallet. Only used if the pallet has no GTIN. It indicates the number of
4177 trade items placed on a pallet layer according to supplier or retailer
4178 preferences.
4179
4180 Examples:
4181
4182 Business Rules: Only used if the pallet has no GTIN. In this case it
4183 applies to the highest level of the item hierarchy. It is highly
4184 recommended to use GTIN for Pallet identification.
4185
4186
4187 Class Name: TradeItemHierarchy
4188
4189 Item Name: quantityOfInnerPack
4190
4191 Core/Extension: E
4192 Global Local Status: G
4193 M/O/D: O
4194 Multiple Values Allowed: N
4195 Neutral/Relationship Dependant: T.P.Neutral
4196 Product Hierarchy Reference Level: All
4197 Common value to all product hierarchy: No
4198 Type: N
4199 Size: ..3
4200
4201 Definition: Indicates the number of non-coded physical groupings
4202 (innerpacks) of next lower level trade items within the current GTIN level.
4203
4204 Examples: Case of 12 bottles of shampoo contains two non-coded
4205 plastic wrapped bundles each with six bottles. Value = "2"
4206
4207 Business Rules: An inner pack can only contain the same GTIN, and
4208 inner pack sizing must be constant. Change of inner pack doesn't change
4209 higher or lower level GTINs
4210
4211
4212 Class Name: TradeItemHierarchy
4213
4214 Item Name: quantityOfNextLevelTradeItemWithinInnerPack
4215
4216 Core/Extension: E
4217 Global Local Status: G
4218 M/O/D: O
4219 Multiple Values Allowed: N
4220 Neutral/Relationship Dependant: T.P.Neutral
4221 Product Hierarchy Reference Level: All
4222 Common value to all product hierarchy: No
4223 Type: N
4224 Size: ..3
4225
4226 Definition: Indicates the number of next lower level trade items contained
4227 within the physical non-coded grouping (innerpack)
4228
4229 Examples: Case of 12 bottles of shampoo contains two non-coded
4230 plastic wrapped bundles each with six bottles. Value = "6"
4231
4232 Business Rules: An inner pack can only contain the same GTIN, and
4233 inner pack sizing must be constant. Change of inner pack doesn't change
4234 higher or lower level GTINs
4235
4236
4237 Class Name: TradeItemImportIdentification
4238
4239 Item Name: importClassificationType
4240
4241 Core/Extension: E
4242 Global Local Status: G/L
4243 M/O/D: O
4244 Multiple Values Allowed: N
4245 Neutral/Relationship Dependant: T.P.Neutral
4246 Product Hierarchy Reference Level: Each
4247 Common value to all product hierarchy: No
4248 Type: Enumerated List
4249 Size: Not Applicable
4250
4251 Definition: This is a code to indicate the type of import classification for
4252 the Trade Item.
4253
4254 Examples: Values include Netherlands Import Code, Harmonized
4255 Commodity Description and Coding System, Customs tariff and
4256 INTRASTAT Code, Harmonized Tariff Schedule of the United States,
4257 INTRASTAT Combined Nomenclature, Tarif Intégré de la Communauté.
4258
4259 Class Name: TradeItemImportIdentification
4260
4261 Item Name: importClassificationValue:
4262
4263 Core/Extension: E
4264 Global Local Status: G/L
4265 M/O/D: O
4266 Multiple Values Allowed: N
4267 Neutral/Relationship Dependant: T.P.Neutral
4268 Product Hierarchy Reference Level: Each
4269 Common value to all product hierarchy: No
4270 Type: AN
4271 Size: 70
4272
4273 Definition: Imports and exports of trade items typically re-quire
4274 classification codes to determine appropriate duties and tariffs. Values
4275 include Netherlands Import Code, Harmonized Commodity Description
4276 and Coding System, Customs Tariff and INTRASTAT Code, Harmonized
4277 Tariff Schedule of the United States, INTRASTAT Combined
4278 Nomenclature, Tarif Intégré de la Communauté.
4279
4280 Business Rules: Required on Import Products only.
4281
4282
4283 Class Name: TradeItemMarking
4284
4285 Item Name: hasBatchNumber
4286
4287 Core/Extension: E
4288 Global Local Status: L
4289 M/O/D: O
4290 Multiple Values Allowed: N
4291 Neutral/Relationship Dependant: T.P.Neutral
4292 Product Hierarchy Reference Level: Each
4293 Common value to all product hierarchy: No
4294 Type: Boolean
4295 Size: Not Applicable
4296
4297 Definition: Indication whether the base trade item is batch or lot number
4298 requested by law, not batch or lot number requested by law but batch or lot
4299 number allocated, or not batch or lot number allocated. A batch or lot number
4300 is a manufacturer assigned code used to identify a trade item's trade item on
4301 batch or lot. Differs from Serial Number which is a manufacturer assigned
4302 code during the trade item on cycle to identify a unique trade item.
4303
4304 Examples:
4305
4306 Business Rules: Local legal requirement (E.g. Austria). Relevant only for
4307 certain industries.
4308
4309
4310 Class Name: TradeItemMarking
4311
4312 Item Name: isNonSoldTradeItemReturnable
4313
4314 Core/Extension: E
4315 Global Local Status: G/L
4316 M/O/D: O
4317 Multiple Values Allowed: N
4318 Neutral/Relationship Dependant: T.P.Neutral
4319 Product Hierarchy Reference Level: Each
4320 Common value to all product hierarchy: No
4321 Type: Boolean
4322 Size: Not Applicable
4323
4324 Definition: Indicates that the buyer can return the articles that are not
4325 sold. Used, for example; with magazines and bread. This is a y/n
4326 (Boolean) where y equals right of return. This is at least relevant to
4327 General Merchandise, Publishing industries and for some FMCG trade
4328 item.
4329
4330 Examples:
4331
4332 Business Rules: This attribute applies to certain industries, and applies
4333 to return of salable goods. This indicator identifies the general rule, and is
4334 not transaction based.
4335
4336
4337 Class Name: TradeItemMarking
4338
4339 Item Name: isTradeItemMarkedAsRecyclable
4340
4341 Core/Extension: E
4342 Global Local Status: G/L
4343 M/O/D: O
4344 Multiple Values Allowed: N
4345 Neutral/Relationship Dependant: T.P.Neutral
4346 Product Hierarchy Reference Level: Each
4347 Common value to all product hierarchy: No
4348 Type: Boolean
4349 Size: Not Applicable
4350
4351 Definition: Trade item has a recyclable indication marked on it, This may
4352 be a symbol from one of many regional agencies.
4353
4354 Examples: Battery recycling logo placed on the battery, Refrigerators,
4355 Heat Pumps and Air Conditioners symbol, Paper marked as recyclable
4356 symbol, Plastic types marked as recyclable symbols.
4357
4358 Business Rules: This is a yes/no (Boolean) where yes equals trade item
4359 marked with ISO markings.
4360
4361
4362 Class Name: TradeItemMaterial
4363
4364 Item Name: materialWeight:
4365
4366 Core/Extension: E
4367 Global Local Status: G/L
4368 M/O/D: O
4369 Multiple Values Allowed: N
4370 Neutral/Relationship Dependant: T.P.Neutral
4371 Product Hierarchy Reference Level: Each
4372 Common value to all product hierarchy: No
4373 Type: Measurement Value
4374 Size: Decimal 15, String 3 for Unit Of Measure
4375
4376 Definition: The measured weight of the material expressed in ounces per
4377 square yard or grams per square meter. For example: 20 OZ Denim
4378 would be specified as 20 UOM = ON. The fabrics range from gossamer
4379 fine to bulky and are described with the following terms: light, medium,
4380 medium-heavy, and heavy. Light weight fabrics weigh up to 6 oz./sq. yd.
4381 (200 g/m2). They include applications such as crisp café curtains and a
4382 number of sheer window coverings. Medium weight fabrics generally
4383 weigh from 6 oz./sq. yd. to 12 oz./sq. yd. (200 g/m2 to 400 g/m2). They
4384 hang well in drapes and are the common choice for slipcovers. Medium-
4385 heavy weight fabrics weigh from 12 oz./sq. yd. to 18 oz./sq. yd. (400 g/m2
4386 to 600 g/m2). They comprise most upholstery fabrics, many drapery
4387 materials, and the most substantial terry toweling. Heavy weight fabrics
4388 weigh over 18 oz./sq. yd. (600 g/m2). They include a number of
4389 upholstery fabrics. The very heaviest consumer textiles are various types
4390 of carpet and other floor coverings.
4391
4392 Business Rules: Acceptable Units of Measure for fabric weight are: ON
4393 – Ounces per square yard (oz/yd2)GM - Grams per square meter (g/m²).
4394
4395
4396 Class Name: TradeItemMaterial
4397
4398 Item Name: threadCount:
4399
4400 Core/Extension: E
4401 Global Local Status: G/L
4402 M/O/D: O
4554 Definition: Used to identify the gross weight of the trade item. The gross
4555 weight includes all packaging materials of the trade item. At pallet level
4556 the trade itemGrossWeight includes the weight of the pallet itself.
4557
4558 Examples: "200 grm", value - total pounds, total grams, etc.
4559
4560 Business Rules: Has to be associated with a valid UoM. See Section 4.6
4561 of the Implementation Considerations and Concerns for more detail on
4562 UoM.
4563
4564
4565 Class Name: TradeItemMeasurements
4566
4567 Item Name: height
4568
4569 Core/Extension: E
4570 Global Local Status: G
4571 M/O/D: M
4572 Multiple Values Allowed: N
4573 Neutral/Relationship Dependant: T.P.Neutral
4574 Product Hierarchy Reference Level: All
4575 Common value to all product hierarchy: No
4576 Type: Multi Measurement Value
4577 Size: Decimal 15, String 3 for Unit Of Measure
4578
4579 Definition: The measurement of the height of the trade item. The vertical
4580 dimension from the lowest extremity to the highest extremity, including
4581 packaging. At a pallet level the trade itemHeight will include the height of
4582 the pallet itself.
4583
4584 Examples: "60 CMT"
4585
4586 Business Rules: Measurements are relative to how the customer
4587 normally views the trade item. Orientation guidelines to be determined by
4588 PTRG within CR 02-000102 by Needs to be associated with a valid UoM.
4589 See Section 4.6 of the Implementation Considerations and Concerns for
4590 more detail on UoM.
4591
4592
4593 Class Name: TradeItemMeasurements
4594
4595 Item Name: ingredientStrength
4596
4597 Core/Extension: E
4598 Global Local Status: G/L
4599 M/O/D: O
4600 Multiple Values Allowed: N
4601 Neutral/Relationship Dependant: T.P.Neutral
4602 Product Hierarchy Reference Level: Each
4603 Common value to all product hierarchy: No
4604 Type: AN
4605 Size: ..18
4606
4607 Definition: Used for pharmaceutical trade item to define the strength of
4608 each ingredient in a trade item or unit volume of the trade item.
4609
4610 Examples: "100mg" for a tablet, "2%" for a liquid or ointment, where 100
4611 and 2 represent the value, and mg and % are the units of measure
4612
4613 Business Rules: Sector specific extension pharmaceutical trade item.
4614 Can be locally mandatory based on each country's laws. Has to be
4615 associated with a valid unitBasisOfMeasure
4616
4617
4618 Class Name: TradeItemMeasurements
4619
4620 Item Name: isNetContentDeclarationIndicated
4621
4622 Core/Extension: E
4623 Global Local Status: G/L
4624 M/O/D: O
4625 Multiple Values Allowed: N
4626 Neutral/Relationship Dependant: T.P.Neutral
4627 Product Hierarchy Reference Level: Each
4628 Common value to all product hierarchy: No
4629 Type: Boolean
4630 Size: Not Applicable
4631
4632 Definition: This field is used to facilitate local business rules where a
4633 declaration of a trade item's net content is not on the product label
4634 e.g.,UK under 50g.legislation
4635
4636 Examples:
4637
4638 Business Rules: For a product without an on-pack net content
4639 declaration this field should be indicated as YES, weight should be
4640 communicated at the trade unit level.
4641
4642
4643 Class Name: TradeItemMeasurements
4644
4645 Item Name: netContent
4646
4647 Core/Extension: E
4648 Global Local Status: G
4649 M/O/D: O
4650 Multiple Values Allowed: N
4651 Neutral/Relationship Dependant: T.P.Neutral
4652 Product Hierarchy Reference Level: Each
4653 Common value to all product hierarchy: No
4654 Type: Multi Measurement Value
4655 Size: Decimal 15, String 3 for Unit Of Measure
4656
4657 Definition: The amount of the trade item contained by a package, as
4658 claimed on the label. (See examples)
4659
4660 Examples: Evian Water 750ml - net content = "750 MLT" ; 20 count pack
4661 of diapers, net content = "20 ea."
4662
4663 Business Rules: In case of multi-pack, indicates the net content of the total
4664 trade item. For fixed value trade items use the value claimed on the package,
4665 to avoid variable fill rate issue that arises with some trade item which are sold
4666 by volume or weight, and whose actual content may vary slightly from batch to
4667 batch. In case of variable quantity trade items, indicates the average quantity.
4668 See Section 4.6 of the Implementation Considerations and Concerns for more
4669 detail on UoM.
4670
4671 Class Name: TradeItemMeasurements
4672
4673 Item Name: netWeight
4674
4675 Core/Extension: E
4676 Global Local Status: G
4677 M/O/D: O
4678 Multiple Values Allowed: N
4679 Neutral/Relationship Dependant: T.P.Neutral
4680 Product Hierarchy Reference Level: Mixed Mod, Pallet, Display
4681 /Shipper, Case Pack
4682 Common value to all product hierarchy: No
4683 Type: Multi Measurement Value
4684 Size: Decimal 15, String 3 for Unit Of Measure
4685
4686 Definition: Used to identify the net weight of the trade item. Net weight
4687 excludes any packaging materials and applies to all levels but consumer
4688 unit level.
4689
4690 Examples: "11.5 kgm" value - pounds, grams, etc.
4691
4692 Business Rules: For consumer unit, Net Content replaces Net Weight
4693 (can then be weight, size, volume). Has to be associated with a valid
4694 UoM. See Section 4.6 of the Implementation Considerations and
4695 Concerns for more detail on UoM.
4696
4697 Class Name: TradeItemMeasurements
4698
4699 Item Name: priceComparisonContentType:
4700
4701 Core/Extension: E
4702 Global Local Status: G
4703 M/O/D: O
4704 Multiple Values Allowed: N
4705 Neutral/Relationship Dependant: T.P.Neutral
4756 Definition: The number of child-items that are packaged beside each
4757 other in a trade unit (on the side facing the consumer). This information is
4758 used in the space process, especially when allocating whole Trade Units
4759 (intermediate) into the shelf. The Space Manager always allocates Base
4760 Units in the shelf. Usually there are no pictures of Trade Units available
4761 and for Hypermarkets/Big Supermarkets there is a need to allocate whole
4762 trade units into the shelves.
4763
4764
4765 Class Name: TradeItemMeasurements
4766
4767 Item Name: width
4768
4769 Core/Extension: E
4770 Global Local Status: G
4771 M/O/D: M
4772 Multiple Values Allowed: N
4773 Neutral/Relationship Dependant: T.P.Neutral
4774 Product Hierarchy Reference Level: All
4775 Common value to all product hierarchy: No
4776 Type: Multi Measurement Value
4777 Size: Decimal 15, String 3 for Unit Of Measure
4778
4779 Definition: The measurement from left to right of the trade item.
4780
4781 Examples: "10 INH"
4782
4783 Business Rules: Measurements are relative to how the customer
4784 normally views the trade item. Orientation guidelines to be determined by
4785 PTRG within CR 02-000102 by Needs to be associated with a valid UoM.
4786 See Section 4.6 of the Implementation Considerations and Concerns for
4787 more detail on UoM.
4788
4789
4790 Class Name: TradeItemOrderInformation
4791
4792 Item Name: agreedMaximumBuyingQuantity
4793
4794 Core/Extension: E
4795 Global Local Status: G/L
4796 M/O/D: O
4797 Multiple Values Allowed: N
4798 Neutral/Relationship Dependant:T.P.Dependent
4799 Product Hierarchy Reference Level: All
4800 Common value to all product hierarchy: No
4801 Type: N
4802 Size: ..9
4803
4804 Definition: The maximum quantity of the product available to the retailer.
4805
4806
4807 Class Name: TradeItemOrderInformation
4808
4809 Item Name: agreedMinimumBuyingQuantity:
4810
4811 Core/Extension: E
4812 Global Local Status: G/L
4813 M/O/D: O
4814 Multiple Values Allowed: N
4815 Neutral/Relationship Dependant:T.P.Dependent
4816 Product Hierarchy Reference Level: All
4817 Common value to all product hierarchy: No
4818 Type: N
4819 Size: ..9
4820
4821 Definition: Minimum buying quantity agreed between trading partners.
4822
4823
4824 Class Name: TradeItemOrderInformation
4825
4826 Item Name: firstDeliveryDateTime:
4827
4828 Core/Extension: E
4829 Global Local Status: G/L
4830 M/O/D: O
4831 Multiple Values Allowed: N
4832 Neutral/Relationship Dependant:T.P.Dependent
4833 Product Hierarchy Reference Level: All
4834 Common value to all product hierarchy: No
4835 Type: Date Time
4836 Size: CCYY-MM-DDTHH:MM:SS
4837
4838 Definition: The earliest date at which the supplier can deliver the
4839 product to the trading partner.
4840
4841
4842 Class Name: TradeItemOrderInformation
4843
4844 Item Name: goodsPickUpLeadTime:
4845
4846 Core/Extension: E
4847 Global Local Status: G/L
4848 M/O/D: O
4849 Multiple Values Allowed: N
4850 Neutral/Relationship Dependant:T.P.Dependent
4851 Product Hierarchy Reference Level: All
4852 Common value to all product hierarchy: No
4853 Type: Multi Measurement Value
4854 Size: Decimal 15, String 3 for Unit Of Measure
4855
4856 Definition: Time (in weeks, days, hours …) required between order entry
4857 and the earliest goods release (use for pick-up, not use for delivery).
4858 Remark about ordering lead-time : Geographic distance from
4859 manufacturing / distribution point to delivery point impacts this value
4860 (relationship dependant data).
4861
4862
4863 Class Name: TradeItemOrderInformation
4864
4865 Item Name: isTradeItemReorderable
4866
4867 Core/Extension: E
4868 Global Local Status: G/L
4869 M/O/D: O
4870 Multiple Values Allowed: N
4871 Neutral/Relationship Dependant:T.P.Dependent
4872 Product Hierarchy Reference Level: All
4873 Common value to all product hierarchy: No
4874 Type: Boolean
4875 Size: Not Applicable
4876
4877 Definition: This element is an indicator that selected styles or trade items
4878 may or may not be re-ordered. It does not imply any information on
4879 current availability. Example: Some Designer's Merchandise, T-shirts
4880 printed out for a special event (commemorative items).
4881
4882
4883 Class Name: TradeItemOrderInformation
4884
4885 Item Name: isTradeItemSizeBasedPricing:
4886
4887 Core/Extension: E
4888 Global Local Status: G/L
4889 M/O/D: O
4890 Multiple Values Allowed: N
4891 Neutral/Relationship Dependant:T.P.Dependent
4892 Product Hierarchy Reference Level: All
4893 Common value to all product hierarchy: No
4894 Type: Boolean
4895 Size: Not Applicable
4896
4897 Definition: This is an indicator that an item may be at a different price
4898 point than other similar SKUs (GTIN's price within a Style may differ).
4899
4900
4901 Class Name: TradeItemOrderInformation
4902
4903 Item Name: orderingLeadTime
4904
4905 Core/Extension: E
5005 which are divisible by the order quantity multiple of 20, eg 100, 120, 140
5006 200 etc.
5007
5008
5009 Class Name: TradeItemOrderInformation
5010
5011 Item Name: orderSizingFactor
5012
5013 Core/Extension: E
5014 Global Local Status: G/L
5015 M/O/D: O
5016 Multiple Values Allowed: N
5017 Neutral/Relationship Dependant: T.P.Neutral
5018 Product Hierarchy Reference Level: All
5019 Common value to all product hierarchy: No
5020 Type: Multi Measurement Value
5021 Size: Decimal 15, String 3 for Unit Of Measure
5022
5023 Definition: A trade item specification other than gross, net weight, or
5024 cubic feet for a line trade item or a transaction, used for order sizing and
5025 pricing purposes. For example, factors may be used to cube a truck,
5026 reflecting different weights, and dimensions of trade item.
5027
5028 Examples:
5029
5030 Business Rules: Assumes a standard size truck or lorry
5031
5032
5033 Class Name: Trade Item Pallet Information
5034
5035 Item Name: palletTypeCode
5036
5037 Core/Extension: E
5038 Global Local Status: G/L
5039 M/O/D: O
5040 Multiple Values Allowed: N
5041 Neutral/Relationship Dependant: T.P.Neutral
5042 Product Hierarchy Reference Level: Pallet
5043 Common value to all product hierarchy: No
5044 Type: Char
5045 Size: 3
5046
5047 Definition: Indicates whether the described dispatch unit is delivered on
5048 a pallet and on which type of pallet, or if it is non-palletized. If the
5049 dispatch unit is delivered on a pallet the pallet type must be given here.
5050 The range of the pallet types/codes is listed in code sets.
5051
5052 Examples: "200" = pallet ISO 0, 1/2 Euro pallet.
5053
5054 Business Rules: Only used if the pallet has no GTIN. In this case it
5055 applies to the highest level of the item hierarchy and only 1 pallet
5056 configuration can be provided. It is highly recommended to use GTIN for
5057 Pallet identification.
5058
5059
5060 Class Name: TradeItemPalletInformation
5061
5062 Item Name: palletTermsAndConditions
5063
5064 Core/Extension: E
5065 Global Local Status: G/L
5066 M/O/D: O
5067 Multiple Values Allowed: N
5068 Neutral/Relationship Dependant: T.P.Neutral
5069 Product Hierarchy Reference Level: Pallet
5070 Common value to all product hierarchy: No
5071 Type: AN
5072 Size: 2
5073
5074 Definition: Indicates if the pallet in the prescribed pallet configuration is
5075 rented, exchangeable, against deposit or one way (not reusable).
5076
5077 Examples: "7E" for non-returnable pallet
5078
5079 Business Rules: Used in conjunction with a pallet GTIN. List of
5080 authorized values based on EANCOM 7073, X12 DE102 and X12 DE399.
5081
5082
5083 Class Name: TradeItemPriceDateInformation
5084
5085 Item Name: cataloguePrice –represented by UML role
5086
5087 Core/Extension: E
5088 Global Local Status: G/L
5089 M/O/D: O
5090 Multiple Values Allowed: N
5091 Neutral/Relationship Dependant: T.P.Neutral
5092 Product Hierarchy Reference Level: All
5093 Common value to all product hierarchy: No
5094 Type: Amount
5095 Size: 17.4
5096
5097 Definition: The gross price before application of any discounts,
5098 allowances, charges, taxes, etcetera. The value represented is the price
5099 that the manufacturer expects to receive for the trade item or service from
5100 any buyer prior to any relationship specific negotiations (E.g. a public
5101 catalogue population). Synonym: List price
5102
5103 Examples: "USD 49.50", "EUR 350,00
5104
5105 Business Rules: CatalogPrice would reside within the Item master data.
5106 The Core Price model would contain class and price along with the class
5107 price type. These will be one of the numerated values for class price type
5108 in Core Price model.
5109 Implementation Note: This attribute is represented by UML role.
5110
5111
5112 Class Name: TradeItemPriceDateInformation
5113
5114 Item Name: effectiveStartDate
5115
5116 Core/Extension: E
5117 Global Local Status: G/L
5118 M/O/D: D
5119 Multiple Values Allowed: N
5120 Neutral/Relationship Dependant: N/T.P.Dependent*
5121 Product Hierarchy Reference Level: All
5122 Common value to all product hierarchy: No
5123 Type: Date
5124 Size: CCYY-MM-DD
5125
5126 Definition: This is the effective start date of the price agreed to by the
5127 trading partners. This start date is mandatory and, if no end date is
5128 communicated, then implies that the price is effective until further notice.
5129 Various types of dates may be pre-aligned between buyer and seller. For
5130 example, based upon a prior agreement between trading partners this
5131 date may relate to any of the following events, first order date, first ship
5132 date, and first arrival date.
5133 Examples: -2002-11-15
5134
5135 Business Rules: Format defined in ISO8601
5136
5137
5138 Class Name: TradeItemPriceDateInformation
5139
5140 Item Name: effectiveEndDate
5141
5142 Core/Extension: E
5143 Global Local Status: G/L
5144 M/O/D: O
5145 Multiple Values Allowed: N
5146 Neutral/Relationship Dependant: N/T.P.Dependent*
5147 Product Hierarchy Reference Level: All
5148 Common value to all product hierarchy: No
5149 Type: Date
5150 Size: CCYY-MM-DD
5151
5152 Definition: The effective end date of the price is optional based upon the
5153 agreement by the trading partners. If an invalid end date is
5154 communicated, then it is implied that the price and its effective date are
5155 effective until further notice. Examples of invalid dates include
5156 99/99/9999, 00/00/0000, blank, etc. These invalid end dates should not
5157 be communicated. Various types of dates may be pre-aligned between
5158 buyer and seller. For example, based upon a prior agreement between
5159 trading partners this date may relate to any of the following events, last
5160 order date, last ship date, and last arrival date.
5161
5162 Examples: 2005-12-31
5163
5164 Business Rules: PriceEndDate not required at time of initial price
5165 amount. Format defined by ISO8601
5166
5167
5168 Class Name: TradeItemPriceDateInformation
5169
5170 Item Name: suggestedRetailPrice Ærepresented by UML role
5171
5172 Core/Extension: E
5173 Global Local Status: G/L
5174 M/O/D: O
5175 Multiple Values Allowed: N
5176 Neutral/Relationship Dependant: T.P.Neutral
5177 Product Hierarchy Reference Level: Each
5178 Common value to all product hierarchy: No
5179 Type: Amount
5180 Size: 17.4
5181
5182 Definition: The retail (to consumer) price as suggested by the
5183 manufacturer. This is normally used to establish a proposed value for the
5184 trade item for marketing purposes. May or may not appear on the
5185 package. May be used as a guideline by the retailer to establish their
5186 actual retail price.
5187
5188 Examples: "value" USD1.90", "EUR 36"
5189
5190 Business Rules: As monetary amount field, this data element must be
5191 associated with a valid unit of measures. Changes in this value do not
5192 require a change in GTIN. ISO 4217 format three digit alpha code.
5193 When the suggestedRetailPrice is provided for information (and not on
5194 the package : priceOnPackIndicator = 'N') , it can be different per Target
5195 Market and becomes G / L. See Section 4.5 of Implementation
5196 Considerations and Concerns for more details.
5197
5198
5199 Class Name: TradeItemSizeDescription
5200
5201 Item Name: descriptiveSize
5202
5203 Core/Extension: E
5204 Global Local Status: G
5205 M/O/D: O
5206 Multiple Values Allowed: N
5207 Neutral/Relationship Dependant: T.P.Neutral
5208 Product Hierarchy Reference Level: All
5209 Common value to all product hierarchy: Yes
5210 Type: Description
5211 Size: ..35
5212
5213 Definition: An alphanumeric size factor the brand owner wishes to
5214 communicate to the consumer. IE Jumbo, Capri, Full Length, Maxi
5215
5216 Examples: "Maxi", "Jumbo", "Mini", “7”, “10 ½”, “small”,
5217
5218 Business Rules: A descriptive size other than net content as labeled on
5219 consumer unit. Must be associated with a valid ISO language code from
5220 the attached table.
5221
5222
5223 Class Name: TradeItemSizeDescription
5224
5225 Item Name: sizeCodeListAgency
5226
5227 Core/Extension: E
5228 Global Local Status: G
5229 M/O/D: D
5230 Multiple Values Allowed: Y
5231 Neutral/Relationship Dependant: T.P.Neutral
5232 Product Hierarchy Reference Level: Each
5233 Common value to all product hierarchy: No
5234 Type: AN
5235 Size: ..3
5236
5237 Definition: The parties controlling the size code list. Dependent on size
5238 code value.
5239
5240 Examples: "25" EDITEX.
5241
5242 Business Rules: If size code is indicated, sizeCodeListAgency is
5243 required. Sector specific extension.
5244
5245
5246 Class Name: TradeItemSizeDescription
5247
5297
5298
5299 Class Name: TradeItemTemperatureInformation
5300
5301 Item Name: deliveryToDistributionCenterTemperatureMinimum
5302
5303 Core/Extension: E
5304 Global Local Status: G
5305 M/O/D: O
5306 Multiple Values Allowed: N
5307 Neutral/Relationship Dependant: T.P.Neutral
5308 Product Hierarchy Reference Level: Each
5309 Common value to all product hierarchy: No
5310 Type: Multi Measurement Value
5311 Size: Decimal 15, String 3 for Unit Of Measure
5312
5313 Definition: Permitted minimum temperature of the trade item on transport
5314 to the distribution center.
5315
5316 Examples: "+2 C" or degrees F, value
5317
5318 Business Rules: Temperature information is important for dairy trade
5319 item, dangerous goods and other trade items for which certain
5320 temperature limits are necessary during transport or storage, for quality or
5321 safety reasons. Has to be associated with valid UoM. See Section 4.6 of
5322 the Implementation Considerations and Concerns for more details of
5323 UoM.
5324
5325
5326 Class Name: TradeItemTemperatureInformation
5327
5328 Item Name: deliveryToMarketTemperatureMaximum
5329
5330 Core/Extension: E
5331 Global Local Status: G
5332 M/O/D: O
5333 Multiple Values Allowed: N
5334 Neutral/Relationship Dependant: T.P.Neutral
5335 Product Hierarchy Reference Level: Each
5336 Common value to all product hierarchy: No
5337 Type: Multi Measurement Value
5338 Size: Decimal 15, String 3 for Unit Of Measure
5339
5340 Definition: Permitted maximum temperature of the trade item during
5341 delivery to market.
5342
5343 Examples: "+7 C" or degrees F, value
5344
5345 Business Rules: Temperature information is important for dairy trade
5346 item, dangerous goods and other trade items for which certain
5347 temperature limits are necessary during transport or storage, for quality or
5348 safety reasons. Has to be associated with valid UoM. See Section 4.6 of
5349 the Implementation Considerations and Concerns for more details of
5350 UoM.
5351
5352 Class Name: TradeItemTemperatureInformation
5353
5354 Item Name: deliveryToMarketTemperatureMinimum
5355
5356 Core/Extension: E
5357 Global Local Status: G
5358 M/O/D: O
5359 Multiple Values Allowed: N
5360 Neutral/Relationship Dependant: T.P.Neutral
5361 Product Hierarchy Reference Level: Each
5362 Common value to all product hierarchy: No
5363 Type: Multi Measurement Value
5364 Size: Decimal 15, String 3 for Unit Of Measure
5365
5366 Definition: Permitted minimum temperature of the trade item during
5367 delivery to market to market.
5368
5369 Examples: "+3 C" or degrees F, value
5370
5371 Business Rules: Temperature information is important for dairy trade
5372 item, dangerous goods and other trade items for which certain
5373 temperature limits are necessary during transport or storage, for quality or
5374 safety reasons. Has to be associated with valid UoM. See Section 4.6 of
5375 theImplementation Considerations and Concerns for more details of
5376 UoM.
5377
5378 Class Name: TradeItemTemperatureInformation
5379
5380 Item Name: storageHandlingHumidityMaximum:
5381
5382 Core/Extension: E
5383 Global Local Status: G
5384 M/O/D: O
5385 Multiple Values Allowed: N
5386 Neutral/Relationship Dependant: T.P.Neutral
5387 Product Hierarchy Reference Level: Each
5388 Common value to all product hierarchy: No
5389 Type: Multi Measurement Value
5390 Size: Decimal 15, String 3 for Unit Of Measure
5391
5392 Definition: The maximum humidity in percentages that the goods should
5393 be stored in.
5394
5395 Examples:
5396
5397 Business Rules:
5398
5399 Class Name: TradeItemTemperatureInformation
5400
5401 Item Name: storageHandlingHumidityMinimum:
5402
5403 Core/Extension: E
5404 Global Local Status: G
5405 M/O/D: O
5406 Multiple Values Allowed: N
5407 Neutral/Relationship Dependant: T.P.Neutral
5408 Product Hierarchy Reference Level: Each
5409 Common value to all product hierarchy: No
5410 Type: Multi Measurement Value
5411 Size: Decimal 15, String 3 for Unit Of Measure
5412
5413 Definition: The minimum humidity in percentages that the goods should
5414 be stored in.
5415
5416 Examples:
5417
5418 Business Rules:
5419
5420
5421 Class Name: TradeItemTemperatureInformation
5422
5423 Item Name: storageHandlingTemperatureMaximum
5424
5425 Core/Extension: E
5426 Global Local Status: G
5427 M/O/D: O
5428 Multiple Values Allowed: N
5429 Neutral/Relationship Dependant: T.P.Neutral
5430 Product Hierarchy Reference Level: All
5431 Common value to all product hierarchy: Yes
5432 Type: Multi Measurement Value
5433 Size: Decimal 15, String 3 for Unit Of Measure
5434
5435 Definition: The maximum temperature at which the trade item can be
5436 stored. This uses a measurement consisting of a unit of measure and a
5437 value.
5438
5439 Examples: "+15 F" or degrees C, value
5440
5441 Business Rules: When no other information is provided (temperatures to
5442 market or/and distribution center), this value applies at any point of the
5443 supply chain. Temperature information is important for fresh trade item,
5444 dangerous goods and other trade items for which certain temperature limits
5445 are necessary for quality or safety reasons. Has to be associated with a
5446 valid UoM. See Section 4.6 of the Implementation Considerations and
5447 Concerns for more details on UoM.
5448
5449
5450 Class Name: TradeItemTemperatureInformation
5451
5452 Item Name: storageHandlingTemperatureMinimum
5453
5454 Core/Extension: E
5455 Global Local Status: G
5456 M/O/D: O
5457 Multiple Values Allowed: N
5458 Neutral/Relationship Dependant: T.P.Neutral
5459 Product Hierarchy Reference Level: All
5460 Common value to all product hierarchy: Yes
5461 Type: Multi Measurement Value
5462 Size: Decimal 15, String 3 for Unit Of Measure
5463
5464 Definition: The minimum temperature at which the trade item can be
5465 stored. This uses a measurement consisting of a unit of measure and a
5466 value.
5467
5468 Examples: "-30 C" or degrees F, value
5469
5470 Business Rules: When no other information is provided (temperatures to
5471 market or/and distribution center), this value applies at any point of the
5472 supply chain. Temperature information is important for fresh trade item,
5473 dangerous goods and other trade items for which certain temperature
5474 limits are necessary for quality or safety reasons. Has to be associated
5475 with a valid UoM. See Section 4.6 of the Implementation Considerations
5476 and Concerns for more details of UoM.
5477
5478
5479 Class Name: TradeItemUnitIndicator
5480
5481 Item Name: isTradeItemABaseUnit
5482
5483 Core/Extension: E
5484 Global Local Status: G
5485 M/O/D: M
5486 Multiple Values Allowed: N
5487 Neutral/Relationship Dependant: T.P.Neutral
5488 Product Hierarchy Reference Level: All
5489 Common value to all product hierarchy: No
5490 Type: Boolean
5491 Size: Not Applicable
5492
5493 Definition: An indicator identifying the trade item as the base unit level of
5494 the trade item hierarchy. This is a (Boolean) where y indicates the trade
5495 item is a base unit.
5496
5497 Examples: A bundle pack of product is composed of packages without
5498 GTINs that cannot be sold individually. This bundle pack would then be a
5499 base item. If that same bundle pack contained individual packages that
5500 have a GTIN + could be individually sold it would not
5501
5502 Business Rules:
5503
5504
5505 Class Name: TradeItemUnitIndicator
5506
5507 Item Name: isTradeItemAConsumerUnit
5508
5509 Core/Extension: E
5510 Global Local Status: G
5511 M/O/D: M
5512 Multiple Values Allowed: N
5513 Neutral/Relationship Dependant: T.P.Neutral
5514 Product Hierarchy Reference Level: All
5515 Common value to all product hierarchy: No
5516 Type: Boolean
5517 Size: Not Applicable
5518
5519 Definition: Identifies whether the current hierarchy level of a trade item is
5520 intended for a ultimate consumption. For retail, this trade item will be
5521 scanned at point of sale. At retail, this data is commonly used to select
5522 which GTINs should be used for shelf planning and for front end POS
5523 databases. This value reflects the intention of the Information Provider
5524 which may not necessarily be the intention of the retailer.
5525
5526 Examples: A multi-pack of paper towels and the individual paper towels
5527 contained in the multi-pack are both identified as a consumer unit.
5528
5529 Business Rules: There can be more than one consumer unit in one
5530 hierarchy
5531
5532
5533 Class Name: TradeItemUnitIndicator
5534
5535 Item Name: isTradeItemADespatchUnit
5536
5537 Core/Extension: E
5538 Global Local Status: G/L
5539 M/O/D: M
5540 Multiple Values Allowed: N
5541 Neutral/Relationship Dependant:T.P.Dependent
5542 Product Hierarchy Reference Level: All
5543 Common value to all product hierarchy: No
5544 Type: Boolean
5545 Size: Not Applicable
5546
5547 Definition: An indicator identifying that the information provider considers
5548 the trade item as a dispatch (shipping) unit. This may be Trading Partner
5679
5680 3.7 TRADE ITEM TAX INFORMATION:
5681
5682 Class Name: TaxAgency
5683
5684 Item Name: taxAgencyCode
5685
5686 Core/Extension: E
5687 Global Local Status: G/L
5688 M/O/D: O
5689 Multiple Values Allowed: N
5690 Neutral/Relationship Dependant: T.P.Neutral
5691 Product Hierarchy Reference Level: All
5692 Common value to all product hierarchy: No
5693 Type: AN
5694 Size: ..3
5695
5696 Definition: Identifies the agency responsible for the tax code list
5697
5698 Examples: X1 = BE, ICODIF/EAN Belgium - Luxembourg
5699
5700 Business Rules:
5701
5702
5703 Class Name: TaxAgency
5704
5705 Item Name: taxTypeCode
5706
5707 Core/Extension: E
5708 Global Local Status: G/L
5709 M/O/D: O
5710 Multiple Values Allowed: N
5711 Neutral/Relationship Dependant: T.P.Neutral
5712 Product Hierarchy Reference Level: All
5713 Common value to all product hierarchy: No
5714 Type: AN
5715 Size: 14
5716
5717 Definition: Identification of the type of duty or tax or fee applicable to the
5718 trade item.
5719
5720 Examples: "3001000002138"
5721
5722 Business Rules: This will vary by target market. Repeatable field inside
5723 each possible target market.
5724
5767
5768
5769 Class Name: TradeItemTaxAmount
5770
5771 Item Name: taxAmount
5772
5773 Core/Extension: E
5774 Global Local Status: G/L
5775 M/O/D: O
5776 Multiple Values Allowed: Y
5777 Neutral/Relationship Dependant: T.P.Neutral
5778 Product Hierarchy Reference Level: All
5779 Common value to all product hierarchy: No
5780 Type: Amount
5781 Size: 13.4
5782
5783 Definition: The current tax or duty or fee amount applicable to the trade
5784 item.
5785
5786 Examples: Value – “ USD 1.06”, "EUR 36"
5787
5788 Business Rules: As monetary amount field, this data element is must be
5789 associated with a valid unit of measure. taxRate and taxAmount are
5790 mutually exclusive for each tax type.
5791
5792
5793
5794
5795 3.8 FMCG (Fast Moving Consumer Goods) – INDUSTRY SPECIFIC:
5796
5797
5798 Class Name: FMCGTradeItemMarking
5799
5800 Item Name: isIngredientIrradiated
5801
5802 Core/Extension: E
5803 Global Local Status: G/L
5804 M/O/D: M
5805 Multiple Values Allowed: N
5806 Neutral/Relationship Dependant: T.P.Neutral
5807 Product Hierarchy Reference Level: Each
5808 Common value to all product hierarchy: No
5809 Type: Boolean
5810 Size: Not Applicable
5811
5812 Definition: Indicates if radiation has been applied to a trade item’s
5813 ingredient.
5814
5815 Examples:
5816
5817 Business Rules:
5818 Note: This requirement is handled through the FMCG Extension.
5819
5820 Should only be submitted if a claim is made on the trade item.
5821
5822
5823 Class Name: FMCGTradeItemMarking
5824
5825 Item Name: isRawMaterialIrradiated
5826
5827 Core/Extension: E
5828 Global Local Status: G/L
5829 M/O/D: M
5830 Multiple Values Allowed: N
5831 Neutral/Relationship Dependant: T.P.Neutral
5832 Product Hierarchy Reference Level: Each
5833 Common value to all product hierarchy: No
5834 Type: Boolean
5835 Size: Not Applicable
5836
5837 Definition: Indicates if radiation has been applied to a trade item’s raw
5838 material.
5839
5840 Examples:
5841
5842 Business Rules:
5843 Note: This requirement is handled through the FMCG Extension.
5844
5845 Should only be submitted if a claim is made on the trade item. This field is
5846 trade item specific, indicating that radium has been applied to the trade
5847 item.
5848
5849
5850 Class Name: FMCGTradeItemMarking
5851
5852 Item Name: isTradeItemGeneticallyModified
5853
5854 Core/Extension: E
5855 Global Local Status: G/L
5856 M/O/D: M
5857 Multiple Values Allowed: N
5858 Neutral/Relationship Dependant: T.P.Neutral
5859 Product Hierarchy Reference Level: Each
5860 Common value to all product hierarchy: No
5861 Type: Boolean
5862 Size: Not Applicable
5863
5864 Definition: Used to indicate whether trade item contains genetically
5865 modified contents.
5866
5867 Examples: See code list
5868
5869 Business Rules:
5870 Note: This requirement is handled through the FMCG Extension.
5871
5872
5873 Class Name: FMCGTradeItemMarking
5874
5875 Item Name: isTradeItemIrradiated
5876
5877 Core/Extension: E
5878 Global Local Status: G/L
5879 M/O/D: M
5880 Multiple Values Allowed: N
5881 Neutral/Relationship Dependant: T.P.Neutral
5882 Product Hierarchy Reference Level: Each
5883 Common value to all product hierarchy: No
5884 Type: Boolean
5885 Size: Not Applicable
5886
5887 Definition: Indicates if radiation has been applied to an trade item.
5888
5889 Examples:
5890
5891 Business Rules:
5892
5893 Note: This requirement is handled through the FMCG Extension.
5894 Should only be submitted if a claim is made on the trade item. This field
5895 is trade item specific, indicating that radium has been applied to the trade
5896 item.
5897
5898
5899 Class Name: FMCGTradeItemMeasurements
5900
5901 Item Name: degreeOfOriginalWort
5902
5903 Core/Extension: E
5904 Global Local Status: L
5905 M/O/D: O
5906 Multiple Values Allowed: N
5907 Neutral/Relationship Dependant: T.P.Neutral
5908 Product Hierarchy Reference Level: All
5909 Common value to all product hierarchy: No
5910 Type: Char
5911 Size: 3
5912
5913 Definition: Specification of the degrees of original wort.
5914
5915 Examples: The beer degree for the allocation of different original wort
5916 proportions in different kinds of beer to the respective beer tax group and
5917 beer tax rate.
5918
5919 Business Rules:
5920 Note: This requirement is handled through the FMCG Extension.
5921
5922 Sector specific extension (alcoholic beverages) Local legal requirement
5923 (Austria)
5924
5925
5926 Class Name: FMCGTradeItemMeasurements
5927
5928 Item Name: fatPercentageInDryMatter
5929
5930 Core/Extension: E
5931 Global Local Status: G
5932 M/O/D: O
5933 Multiple Values Allowed: N
5934 Neutral/Relationship Dependant: T.P.Neutral
5935 Product Hierarchy Reference Level: Each
5936 Common value to all product hierarchy: No
5937 Type: Percentage
5938 Size: 3.2
5939
5940 Definition: The amount of fat contained in the base product expressed
5941 in percentage.
5942
6024 data model. (e.g. degree of wort is specifically relevant to the beer
6025 industry)
6026
6027 Application notes – The complete data model for an industry is made up of a
6028 combination of these three types of attributes. It is expected that attributes may
6029 be added or deleted from the model in the future.Also, as more industries
6030 become involved in the EAN.UCC GSMP process, it is expected that more
6031 industry specific extensions will be created.
6032
6033 In most cases, the agreement reached by the two parties that will be
6034 communicating data will include only a portion of the data model. This is because
6035 this model is designed to capture all possible business needs of the industry. In
6036 many cases, the buyer will only require a subset of these attributes in order to
6037 conduct business in the manner that they are accustomed.
6038
6039
6040
Core
GTIN, GLN
Target M arket Transactional
EAN.UCC Product Extension
Classification, e.g. for CPFR
Product Description
Food Service
Extension Extension
FM CG
Extension
General M erchandise
Currently 23
Extension
EAN.UCC Sectors
identified
6041
6042
6043
6044
6045
6046 Key data attributes
6047
6048 This data model works off a basic principle. The entire set of data attributes assigned to
6049 a GTIN may vary depending on who provides the information, and in which target market
6050 the data is relevant.
6051
6052 Within the global data synchronization environment, the combination of three key
6053 attributes, GLN of information provider, GTIN of the trade item, and the Target Market
6054 identifies a unique set of values for the trade items’ attributes. This combination can also
6055 affect which attributes are communicated. The values of attributes can vary for a GTIN
6056 when GLN of information provider or Target market are changed.
6057
6058 Example – “orderingLeadTime” may vary depending on target market. (US delivery
6059 within 3 days, delivery within Belgium is less than 1 day)
6060 Example – “cataloguePrice” may vary depending on the information provider (catalogue
6061 price equals $1.00 from manufacturer, but is $1.05 in the information set communicated
6062 by a distributor)
6063
6064 All variation must be compliant with GTIN allocation rules per the General EAN.UCC
6065 Specifications. Variations that do not comply will require a new GTIN.
6066
6067 As stated above, in addition possible variations in values for the same attribute, the list
6068 of attributes communicated may change based on these three keys. Changes in the
6069 information provider can change the list of attributes associated with a GTIN.
6070 Example – Information provider A chooses to provide values for 50 attributes for a GTIN,
6071 while information provider B chooses to provide values for 100, seeing this as a
6072 competitive advantage.
6073
6074 The relevant target market can also affect the selection of attributes. Certain target
6075 markets will have legal requirements for some attributes, while other target markets will
6076 not.
6077
6078 Example – “dangerous goods” attributes are currently required in certain countries.
6079 Parties that do not operate in these countries will not be required to communicate these
6080 attributes to their customers.
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106 Master Data
6107
6108
6109 Extension
6110
6111
6112
6113
6114
6115
6116 Core
6117
6118 Neutral
6119 Neutral
6120 +
6121 Relationship
6122
dependant
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134 4.1 Product hierarchy
6135
6136 There has been a long running debate within the EAN.UCC item project team regarding
6137 the application of a principle which states that if information about a product hierarchy is
6138 to be communicated, it is required that a GTIN be allotted to that level and the
6139 information only be attached to that GTIN. At the time this document was being
6140 finalized, this debate was still taking place. It is the intent of the Item group to present to
6141 the Align Data BRG a paper describing the current industry practices as they relate to
6142 hierarchy with the proper industry endorsement and representation .
6143
6144 This model is designed in conjunction with a widely accepted view of product
6145 containment hierarchy found in the commercial products industries. Attached is a chart
6146 describing the currently accepted definitions and guidelines for this hierarchy
6147
6148 GTIN Hierarchy
6149
6150 Preface
6151 • Eight discreet “levels” of GTIN Hierarchy have been identified.
6152 • “tradeItemUnitDescriptor has been used as the field to describe the GTIN
6153 hierarchy level.
6154
6155 • Implementation with any level of automation will require the programs to map
6156 discreetly from each of these GTIN hierarchy layers. Each attribute has the
6157 potential for a different meaning depending on which layer it’s attached to. Each
6158 attribute may also vary in cardinality or condition depending on the ‘product type
6159 name’ of the GTIN.
6160 • The following guidelines have been created, debated, practiced, reviewed, and
6161 endorsed by the UCCnet community over the last 3 years. The Guidelines Task
6162 Group, represented by over 60 individuals and participating companies has
6163 endorsed these Guidelines.
6164
6165 o (MX) Mixed Mod: A “mixed mod” or “display ready pallet” that is not the
6166 normal ‘turn’ for ordering. May NOT have any parents. May have children
6167 (DS, CA, PK, EA) in multiple instances. Orderable: True / ConsumerUnit:
6168 False.
6169
6170 o (PL) Pallet: A pallet of turn product. May NOT have any parents. May have
6171 children (DS, CA, PK, EA) in a single instance. Orderable: True or False /
6172 ConsumerUnit: False.
6173
6174 o (DS) Display / Shipper: A display, a shipper. May have a “PL” parent. May
6175 have (CA or EA) children in multiple instances. Orderable: True /
6176 ConsumerUnit: True or False.
6177
6178 o (CA) Case: The standard shipping unit level. May be contained in one or
6179 more (PL, MX, or DS). May contain children (PK or EA) in a single instance.
6180 Orderable: True or False / Consumable: True or False.
6181
6182 o (PK) Pack / Innerpack: A logistical unit between case and each. This may
6183 be a consumable innerpack (i.e. Carton of Cigarettes) or it may be simply a
6184 logistical pack (i.e. Dozens of toothbrushes). Multiple instances of a (EA)
6185 child are allowed. Multiple instances of (DS or CA) parents are allowed.
6186 Orderable: true or False / ConsumerUnit: True or False.
6187
6188 o (EA) Each: The lowest level of the item hierarchy intended or labeled for
6189 individual retail sale. May not have any children. May have multiple
6190 instances of (PK, CA, DS, PL, or MX) parents. Orderable:True or False /
6191 ConsumerUnit:True.
6192
6193 o Prepack/Assortment: Contains multiple components, each of which
6194 represents a unique consumer unit item by color and size. Includes
6195 “prepacks” and “setpacks.”
6196
6197 Prepack: or standard assortment of trade items, each different
6198 item within the prepack will be assigned a GTIN maintaining the
6199 one-to-one relationship between trade item/color ID/size ID and
6200 GTIN. Each of the component GTINs is scannable at the Point-of-
6201 Sale and may or may not be orderable separately outside of the
6243
Product Parents Children
Description Parents Children Orderable Consumable
type Instance Instance
A “mixed mod” or
“display ready
(MX) Mixed DS, CA, PK,
pallet” that is not None N/A Multiple True False
Module EA
the normal ‘turn’
for ordering
A pallet of turn DS, CA, PK,
(PL) Pallet None N/A Single True or False False
product EA
(DS)
A display or Single/
Display/ PL CA, EA True True or False
shipper Multiple
Shipper
The standard
Single/
(CA) Case shipping unit PL, MX, DS Multiple PK, EA True or False True or False
Multiple
level.
A logistical unit
(PK) Pack / Single/
between case and DS, CA Multiple EA True or False True or False
Innerpack Multiple
each
The lowest level
of the item
hierarchy PK, CA, DS,
(EA) Each Multiple None N/A True or False True
intended or PL, MX
labeled for
individual resale
6244 Attributes in the data model are designed such that they can and are used to describe
6245 the same value for any product hierarchy level. “Height“ for example, means the height
6246 of a consumer unit, case or pallet, depending on the product type being described by the
6247 GTIN. See Examples in the tables below:
6248
6249
Quantity of
Quantity
children Quan
Simple Next Lower Level Next Lower Quantity
Description GTIN (number of tity
Product GTIN Level in Each
different Pack
GTINs
GTIN)
6253
6254 X= Not applicable
6255
6256
6257
6258
6259
6260
Quantity of
Quantity of
Description GTIN Next Lower Level GTIN Next Lower Net Content
Children
Level
6261
6262 X= Not applicable
6263
6264
6265 The next page shows a table which lists all the attributes contained in this data model
6266 and notes at which product hierarchy level they are relevant.
6267
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Resolved Item Name M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common M/O/D Common
Status Status Status Status Status Status
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
Item Containment:
Refer to Class Diagram for Trade Item in the UML section where item hierarchy is handled.
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.”
classificationAttributeTypeName:
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."
Product orientation principles developed by the PTRG will affect the following attributes:
width, depth, and height.
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.
EAN.UCC currently has two classes related to Monetary Amount. One is Amount’ and the
other is ’MonetaryAmount’.
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.
EAN.UCC currently has two classes related to measurement. One is 'Measurement class'
and the other is '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.
Brand.......................................MANDATORY
Examples:
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.
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.
Language Code
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.
Codes for the representation of names of languages -- Part 1:Alpha-2 code 2002
Available from: http://www.iso.ch or
ISO 639-1
http://www.loc.gov/standards/iso639-2/langcodes.html#ef
See Code List Source Bibliography section of this document.
Part 1 - Country Codes (Three Digit Format)
ISO 3166-1
Available from: http://www.iso.ch
Part 2 - Alpha Country Subdivision Code
ISO 3166-2
Available from: http://www.iso.ch
Codes for the representation of currencies and funds 2001
ISO 4217
Available from: http://www.iso.ch
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.
EAN•UCC Unit Of Measures
Code Code Description
26 Actual Ton
Application
Z51
(e.g. in hair colorant, 6 applications)
AS Assortment
BG Bag
BA Bale
BI Bar
BR Barrel
Skid
SKD
SKE Skid, elevating or lift truck
Slip Sheet
Shipping containers utilizing slip sheets,
SLP
which are cardboard platforms used to
hold product for storage or transportation
SLV Sleeve
SPI Spin Cylinders
SPL Spool
Comments
Attribute Name
Code Code Description
AS 4068-1993
25 Australian Pallet with dimension 115.5 X
116.5 cm
Comments
Attribute Name
Code Code Description
packagingMaterialCode 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
Wire/Cord
Something that binds, ties, or encircles the
48
package/container to secure and maintain
unit integrity
49 Insulated
Steel - Vinyl Coated
50 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
Paper – VCI
Water-resistant paper that is treated by the
72 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
Comments
Attribute Name
Code Code Description
Plastic - Vacuum Formed
Packaging material that is formed by
75 heating plastic sheet and drawing it against
the mold surface by evacuating the air
between the sheet and the mold
76 Paper
Plastic - Structural Foam
A method of manufacturing containers and
shipping devices by mixing plastic resins
77
with a foaming agent, heating it and
injecting the mix into a two-piece
machined aluminum mold
Plastic - Injection Molded
Packaging material that is formed by
78 melting the material and then forcing it
under pressure into a cavity of a closed
mold
79 Plastic
80 Polyethylene Lined
Plastic – Virgin
Plastic in the form of pellets, granules,
81 powder, floc, or liquid that has not been
subjected to use or processing other than
for its initial manufacture
82 Pulpboard
Plastic – Regrind
A plastic prepared from discarded articles
83
that have been reprocessed, often changing
some of its original properties
Polystyrene
84 A polymer prepared by the polymerization
of styrene as the sole monomer
85 Rubber
Foam
86 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
Single Wall Corrugated Board
The structure formed by one corrugated
95
inner member between two flat facings;
also known as double face
Double Wall Corrugated Board
96 The structure formed by three flat facings
and two intermediate corrugated members
Triple Wall Corrugated Board
The structure formed by four flat facings
97
and three intermediate corrugated
members
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.
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.
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.
Is Trading Partner
Dependent
Can vary by Tar (T.P.Dependent) ,
Multiple Market i.e has Trading Partner
Values status: N (Globa Neutral
Allowe Y (Global/Local) (T.P.Neutral+F53)
Resolved Item Name d (Local) 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
Is Trading
Partner
Dependent
Can vary by Target (T.P.Dependent) ,
Market i.e has status: Trading Partner
Multiple N (Global), Y Neutral
Values (Global/Local), Y (T.P.Neutral+F53)
Resolved Item Name Allowed (Local) 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
minimumTradeItemLifespanFromTimeOfArriva T.P.Neutral &
l No Y (Global/Local) T.P.Dependent
minimumTradeItemLifespanFromTimeOfProd T.P.Neutral &
uction No Y (Global/Local) 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
Is Trading Partner
Dependent
(T.P.Dependent) ,
Can vary by Target Trading Partner
Multiple Market i.e has status: N Neutral
Values (Global), Y (T.P.Neutral+F53) OR
Resolved Item Name Allowed (Global/Local), Y (Local) 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
T.P.Neutral &
publicationDate No Y (Global/Local) T.P.Dependent
quantityOfChildren No N (Global) T.P.Neutral
quantityOfCompleteLayersContainedInATradeIt
em 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
quantityOfTradeItemsContainedInACompleteLa
yer 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
APPENDIX B Attribute Association by Trade Item Hierarchy Level for Data Synchronization
Attribute Association by Trade Item Hierarchy Level for Data Sync globaltrade
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Displays,
Shippers or
Mixed Module Mixed Cases
(MX) Pallet (PL) (DS) Case (CS) Pack/InnerPack (PK) Each (EA)
Mandatory to
Class Name Item Name
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
FMCGTradeItemMarking
isIngredientIrradiated : Boolean
isRawMaterialIrradiated : Boolean
isTradeItemGeneticallyModified : Boolean
isTradeItemIrradiated : Boolean
________________________________________________________________________________
CodeList Solution
FMCGTradeItemMarking_Revised <<enumeration>>
ingredientIrradiated[0..1] : AnswerList AnswerList
rawMaterialIrradiated[0..1] : AnswerList FALSE
tradeItemGeneticallyModified[0..1] : AnswerList TRUE
tradeItemIrradiated[0..1] : AnswerList UNSPECIFIED