How to comply with the EU 1169/2011 regulation via GDSN prepj

Transcription

prepj
Belgium & Luxembourg
How to comply with the EU
1169/2011 regulation via GDSN
Version 7 - March 2014
www.gs1belu.org
The global language of business
How to comply with the EU 1169/2011 regulation via GDSN
Contents
How to comply with the EU 1169/2011 regulation via GDSN ............................................... 1
Review of the document ................................................................................................. 3
Process for publishing to Belgilux data recipients (via trustbox) .......................................... 3
Introduction .................................................................................................................. 5
Instructions for data entry .............................................................................................. 6
Process for publishing to Belgilux data recipients (via trustbox) .......................................... 7
1.
General information ................................................................................................. 8
2.
List of ingredients .................................................................................................. 12
3.
Origin .................................................................................................................. 14
4.
Preparation, use and storage .................................................................................. 15
5.
Allergens .............................................................................................................. 16
6.
Nutrients .............................................................................................................. 18
7.
Claims ................................................................................................................. 23
8.
Labels .................................................................................................................. 24
9.
How to add a packshot image? (not mandatory)........................................................ 26
10. Particular cases / General recommandations ............................................................. 27
11. Appendixes ........................................................................................................... 28
12. Contact ................................................................................................................ 31
2014, version 6
All contents copyright © GS1 2014
page 2 of 32
Review of the document
When
13/11/2013
Who
MS
MS
MS
MS
20/11/2013
MS
MS
5/12/2013
SD
27/12/2013
SD
27/12/2013
SD
27/12/2013
SD
27/12/2013
SD
6/01/2014
SD
6/01/2014
SD
13/02/2014
SD
13/02/2014
SD
2014, version 6
What
“label description” is available as AV
Pair attribute
“contactName” is not yet available in
AV Pair
“Additional particulars” is an AV Pair
attribute that can only be completed in
one language. Enter all the languages
in the same field
“marketing message” can only be
completed in one language. Enter all
the languages in the same field
Addition of UoM in nutrient code list
Allergens must be specified in the
ingredient statement using capital
letters.
“Product Description” will no longer be
identified
with
the
attribute
‘tradeItemDescription’ but via the AV
Pair attribute ‘labelDescription’
Product description: how to add
multiple languages for an AV Pair
attribute
‘Brand owner GLN’ information added
to attribute ‘Name of Brand Owner’
‘Legal name’ can be filled with the legal
name of the product + some specific
‘particulars’ indicated in annex 6 of the
EU
1169/2011
regulation.
+
instructions on how to add this
attributes in multiple languages added
Process for publishing to Belgilux data
recpients
changed
(automatic
validation + add info via webtool
process) + add remark about the
trustbox test environment to test the
connection GDSN <-> trustbox prior to
publication to trustbox production
environment
Definition and instructions for “Food
Business Operator” have been updated
Definition
and
instructions
for
“Company Address” have been updated
Added the attribute ‘descriptiveSize’
base on the EU guidelines
‘nameOfManufacturer’ was removed as
an attribute as it is not mandatory
localisation
1.
;
attribute
“product
description”
1. ; attribute “Food business
operator”
1.
;
attribute
“Additional
particulars”
7. ; Claims
9. ; Appendixes
2. List of ingredients
1. General information
Process for publishing
to
Belgilux
data
recipients
(via trustbox)
page 3 of 32
13/02/201
SD
13/02/2014
SD
13/02/2014
SD
13/02/2014
SD
4/03/2014
RG
7/03/2014
RG
2014, version 6
The attribute ‘allergenStatement’ was
added based on the EU guidelines
fishCathZone was removed from the
attributes based on the EU guidelines.
This
will
be
express
in
the
ingredientStatment from now on
Place of provenance was removed from
the attributes based on EU guidelines
Use code ‘approximately’ or ‘less then’
but not ‘exact’ to indicate the level of
presence of a nutrient in a product.
Multilingual information via AV Pair
attributes
Adapting documentation to conform
with
EU
GDSN
Implementation
guidelines
3.origin
6.nutrients
page 4 of 32
Introduction
In November 2011, the European Union (EU) has published a new regulation regarding food
information which will come into force on December 13, 2014. The goal of this regulation is to
ensure that consumers can make informed purchases, having access to information about the
product such as nutritional value, ingredients, instructions for use, etc. The regulation specifies
certain labeling rules such as colors, printing, font size and also specifies that this (extra)
information must be available to the consumer who buys prepackaged food online (via means
of distance selling).
Short summary of the distance selling chapter of the regulation:
The EU Food Information Regulation (EU 1169/2011) requires that a
significant amount of food information must be available to the consumer
before purchase of the prepacked food on a web shop, app or via another
distance sale method.
This mandatory information must be available on or through the website or via
another electronic channel. If the pre-purchase information is not available,
the pre-packed food cannot be sold online.
The EU Food Information Regulation (1169/2011) requires that a significant amount
If theinformation
brand owner
doesbe
not
make available
relevant
information
to the
of food
must
available
to the the
consumer
before
purchase
of the
retailer
in
an
electronic
format,
it
will
be
difficult
for
the
retailer
to
sell
the
prepackaged food on a website, app or via another distance sale method.
on its website.
Nevertheless,
the brand
is not
obligated
Thisfood
mandatory
information
must be available
onowner
or through
the
websiteto
or provide
via another
such
information
in
a
website
friendly
format
to
the
distance
seller.
electronic channel. If the pre-purchase information is not available, the prepackaged
food cannot be sold online.
Yet,
a system
ofdoes
co-operation
owner
and retailer
would
be in
If the
brand
owner
not makebetween
availablethe
thebrand
relevant
information
to the
retailer
required
to
ensure
that
accurate
and
complete
mandatory
food
information
is
an electronic to the consumer prior to purchas
available to the consumer prior to purchase. This regulation places a clear
responsibility on those involved in the supply chain to make sure that the
information available on the package is also available to the consumer when
.
buying food products online.
This document aims to provide information on how to share product information starting from
information available in a GDSN-certified data pool (e.g. CDB from GS1 Belgium & Luxembourg).
The document should be used as a guide to where the different attributes are situated, and how
to fill them in to comply with the regulation. The manual will not explain the regulation itself into
detail, but references to specific parts of it on an attribute level. Please note that the starting
point for entering data is (for a large part of the attributes) the data available on the label.
2014, version 6
page 5 of 32
Instructions for data entry
This guide contains all label information that is required to enter to comply with EU 1169/2011.
All attributes are described in order to create a product description sheet in a GDSN compliant
data pool (e.g.CDB). It will not repeat the 24 mandatory fields that have to be filled in if they
are not a specific part of the regulation. For a specific manual on the use of CDB/GDSN and the
24 mandatory fields we refer to www.gs1belu.org or CDB.support@gs1belu.org.
Each attribute is presented as follows:
The “i.Where” indicates where in the CDB webforms (data pool of GS1 Belgium & Luxembourg)
you can enter the specific information. The name of the tab will be displayed, the name of the
specific subtab will be highlighted.
“ii. GDSN name ” and “iii. GDSN definition” specify the attributes in the GDS network.
“iv. Instruction, v. Remark and vi. Example” will provide directions on how to fill in the
attributes.
For target market Belgium the label information has to be entered in at least Dutch and French.
Extra languages (e.g. German, English, Spanish, …) are optional and can be entered by adding
language fields in GDSN if relevant/stated on the package.
PLEASE NOTE that the screenshots have a goal of illustrating the written explanation on a
certain topic. They are taken from the web environment of the certified data pool of GS1 Belgium
& Luxembourg ‘Central Data Bank’ (CDB) and can thus be different from the environment of
other GDSN data pools.
2014, version 6
page 6 of 32
Process for publishing to Belgilux data recipients
(via trustbox)
Please note that in order to reach the Belgilux data recipients (retailers and third parties)
with data coming from GDSN, the following steps of the ‘trustbox process’ have to be followed:
1. Request a trustbox account so that the published data from GDSN can later be
integrated in the trustbox live environment. Visit http://www.gs1belu.org/nl/trustboxapplication and follow the steps in order to subscribe to trustbox.
2. Create, save and release the products (and/or hierarchies) in the GDSN data pool (for a
manual for the CDB data pool, please visit
http://www.gs1belu.org/nl/publicaties/handleidingen/cdb-user-guide).
3. Publish the product(s) in the GDSN data pool to the data recipient GLN (retailer(s) +
GLN of trustbox: 5488888001428). The ‘how to’ on publishing can also be found in
the manual (see 2).
4. Trustbox will now act as a data recipient; it will receive the data and integrate this data
into the trustbox environment of this supplier (which was set up during step 1) and
validate this data automatically (it is thus available for the Belgilux data recipients) .
5. If necessary: add certain elements or add a pack shot of the product in the trustbox
webtool after putting the status to ‘loaded’. In order to make the changes available to
data recipients again, put the status back to ‘validated’.
IMPORTANT: A test connection between GDSN and the test environment of trustbox can be set
up by publishing data from the GDSN test environment to trustbox UAT. All procedures
remain te same, only the environment changes.
2014, version 6
page 7 of 32
This series of attributes provides information allowing to identify the food products, their
manufacturer(s), the brand owner.

Product Description
i.
ii.
iii.
iv.
Where: Extension: ‘AV Pair/ Specific technical Characteristics’
GDSN name : labelDescription
GDSN definition : /
Instruction : A literal reproduction of the text featured on a product’s label in the
same word-by-word order in which it appears on the front of the product’s
packaging. See appendix for more information about entering AV Pair attributes in
CDB.
v. Remark : The lack of this attribute was formely solved by using the attribute
‘productDescription’, but has now been integrated in AV Pair and can thus be filled.
In order to enter this attribute in multiple languages, please duplicate the
attribute and use the ISO language codes followed by a colon and the label
description. For instructions on how to add AV Pair attributes see below.
This is a mandatory attribute for trustbox!
It’s mandatory to provide an ISO 639-1 language code!
vi. Example: ‘nl: Danone Breakfast aardbei yoghurt’, ‘fr: Danone breakfast yaourt à
la fraise’, etc.

Brand name
i. Where : ID/Classification / Description / Taxes / Production / BarCode
ii. GDSN name : brandName
iii. GDSN definition : The recognizable name used by a brand owner to uniquely
identify a line of trade items or services. This is recognizable by the consumer.
iv. Instruction : /
v. Remark : /
vi. Example : ‘Spa’

Name of brand owner
i.
ii.
iii.
iv.
v.
Where : ID/Classification / Description / Taxes / Production / BarCode
GDSN name : brand owner
GDSN definition : Name of the party who owns the brand of the item.
Instruction : /
Remark : only one name can be entered here. This is not a language dependant
attribute.
vi. Example : « Nestlé »
2014, version 6
page 8 of 32

Net content + UoM
i. Where : Hierarchy / Dimensions / Components / Display Space Planning /
Referenced Items
ii. GDSN name : netContent
iii. GDSN definition : The amount of the trade item contained by a package, usually
as claimed on the label.
iv. Instruction: For fixed value trade items use the value claimed on the package.
In case of variable quantity trade items, indicates the average quantity.
v. Remark: Has to be associated with a valid Unit of Measure (UoM).
vi. Example: Water 750ml - net content = "750 ML".

descriptiveSize
i. Where: Order / Shipment / Marketing / Prices / Season / Colour
ii. GDSN definition : An alphanumeric size factor the brand owner wishes to
communicate to the consumer. Please use the specific definition of this data type
and field, 1-35, as defined in the Trade Item BRD.
iii. Instruction: To be used for prepacked item consists of two or more individual
prepacked items containing the same quantity of the same product if relevant.
iv. Remark: free text field.
v. Example: 4 x 50g

Drained weight + UoM
i. Where : Hierarchy / Dimensions / Components / Display Space Planning /
Referenced Items
ii. GDSN name : drainedWeight
iii. GDSN definition : The weight of the trade item when drained of its liquid.
iv. Instruction : Where a solid food is represented in a liquid medium, the drained net
weight of the food shall also be indicated.
v. Remark : Has to be associated with a valid UoM (Unit of Measure).
vi. Example : “225 GR"= pickles drained of its vinegar (if net weight is e.g. 350 GR).

Food business operator
i. Where : Extension: ‘AV Pair/ Specific technical Characteristics’
ii. GDSN name : contactName
iii. GDSN definition : The name of the individual or department that can be contacted
to provide additional information.
iv. Instruction : Populate as stated on the label. See appendix for more information
about entering AV Pair attributes in CDB.
v. Remark : The name of the food business operator can be the same as the brand
owner and/or manufacturer, but can also be the name of the party that has the right
to distribute/import the product in a specific market.
2014, version 6
page 9 of 32
vi. Example : company XYZ

Company address
i.
ii.
iii.
iv.
Where : Extension: ‘AV Pair/ Specific technical Characteristics’
GDSN name : communicationAddress
GDSN definition : used to communicate the physical location of a contact party.
Instruction : Free text field. Populate as stated on the label. Do not use ‘enters’ to
try and format the text. All information should be provided in a simple text string.
v. Remark : the company communication address associated with the Food
Business Operator as stated on the label. Also insert telephone numbers in this
field, if available on the packaging.
vi. Since the company address can be mentioned in multiple languages, it’s
mandatory to provide an ISO 639-1 language code for every repetition of
the AV Pair attribute! See appendix for more information about entering AV Pair
attributes in CDB.
vii. Example : ‘nl: Koningsstraat 76, 1000 Brussel’; ‘fr: Rue Royale 76, 1000 Bruxelles’.

Product url:
i. Where : Trade Item External Information / Contact Information
ii. GDSN name : /
iii. GDSN definition : Uniform Resource Locator (URL) that references a World-Wide
Web resource providing information about the product.
iv. Instruction :
1. Complete the attribute “type of information” with the value
“WEBSITE”
2. Complete the attribute “Uniform Ressource Identifier” with
the url of the product/brand/company website
v. Remark : Link to the website of the product/manufacturer/brand owner. This is not
a mandatory attribute for the EU 1169/2011 regulation.
vi. Example : ‘www.gs1belu.org’.

Legal name
ii. GDSN name : regulatedProductName
iii. GDSN definition : The prescribed, regulated (legal) or generic product name or
denomination that describes the true nature of the food and is sufficiently precise
to distinguish it from other foods according to the country specific regulation.
iv. Instruction : Should be the same as the regulated name on the pack. See appendix
for more information about entering AV Pair attributes in CDB.
v. Remark : this is not the label description or commercial name of the product, but
a more generic/legal name of the product. In annex 6 of the EU regulation
1169/2011, some particulars are mentioned that need to accompany the legal
2014, version 6
page 10 of 32
name. Please take a look at this list before entering this attribute and make sure all
information is filled in to comply with the regulation via a GDSN data pool. See also
the next attribute ‘additional particulars’.
Since the legal name can be mentioned in multiple languages, it’s
mandatory to provide an ISO 639-1 language code for every repetition of
the AV Pair attribute!
vi. Example : ‘nl: soep’; en: soup’ or ‘en: biscuits’ or ‘en: instant soup’.

Additional particulars
i. Where : Extension: Food & Beverage - Diet / Preparation / Product Yield /
Additive Information
ii. GDSN name : compulsoryAdditivesLabelInformation
iii. GDSN definition : A description of any compulsory label information on the product
for the serving counter.
iv. Instruction : Info from Annex III and VI of the regulation. Except for 2.1 ‘with
sweetener(s)’ and 2.2 ‘with sugar(s) and sweetener(s)’ these statements shall
accompany the name of the food.
v. Remark : These will NOT be part of regulatedProductName, except for “‘with
sweetener(s)’ and 2.2 ‘with sugar(s) and sweetener(s)’. These additional particulars
are described in annex III and VI of the regulation 1169/2011 (http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:304:0018:01:NL:HTML).
vi. Example : ‘Packed in a protective atmosphere’, etc.
2014, version 6
page 11 of 32

Ingredient statement
i. Where : Extension: Food & Beverage - Serving / Ingredient / Nutrient
Information
ii. GDSN name : ingredientStatement
iii. GDSN definition : Information on the constituent ingredient make up of the
product, specified as one string.
iv. Instruction : Exact copy of ingredient statement on packaging. Must be entered in
all relevant languages (on physical package). The field should always start with
the word “Ingredients:” in the relevant language. Do not use ‘enters’ to try
and format the text. All information should be provided in a simple text string.
If information about the fish catch zone, or method of catching is stated on the
label. This information can also be entered after the ingredient list in the same way
as it’s stated on the label. Foot notes are also part of the ingredient statement.
v. Remark : The percentages can be included in this statement. This also applies for
categories. Bold, italic or underlined text cannot be uploaded in the datapool. It’s
therefore recommended that allergens or ingredients containing allergens are
entered using CAPITAL LETTERS in order to make them more visible in the
ingredient statement for the data receiver (and the consumer). Additionally,
allergens should be entered separately in specific fields (see below).
vi. Example : Ingredients: tomatoes (20%), water,MILK, salt.
In order to add extra languages for the ingredient statement, choose the language codes
in the dropdown list on the to right (purple box) and click the green ‘plus’ sign. The new
language fields will appear (green boxes).
2014, version 6
page 12 of 32

AllergenStatement (Not yet available in trustbox)
i. Where: Extension: Food & Beverage - Allergy Related / Microbiological /
Physiochemical Information
ii. GDSN definition : Textual description of the present or absence of allergens as
governed by local rules and regulation, specified as one string.
iii. Instruction : Declare here the ingredient or processing aid listed in annex II of the
EU 1169 regulation or derived from a substance or product listed in annex II causing
allergies or intolerances used in the manufacture or preparation of a food and still
present in the finished product, even if in an altered form as declared in the
ingredient list.
The separator ‘,’ should be used between the declaration of every allergen.
iv. Remark : The idea is to have an exact copy of the ingredients containing allergens,
or the actual allergens mentioned in Bold, Italic or Capital letter in the ingredient
statement. This will allow retailers to map the allergen information to the ingredient
statement, and making it possible to highlight the allergen information in the
ingredient statement on their website (preferably in Bold).
v. Example : Milk, celery.

Alcoholic strength by volume
i.
ii.
iii.
iv.
Where : ID/Classification / Description / Taxes / Production / BarCode
GDSN name : percentageOfAlcoholByVolume
GDSN definition : Percentage of alcohol contained in the base unit trade item.
Instruction : with respect to beverages containing more than 1,2% by volume of
alcohol, the actual alcoholic strength by volume is mandatory for the EU regulation
1169/2011.
v. Remark : Only indicate the value and don’t mention the ‘%’ symbol.
vi. Example : “12”
2014, version 6
page 13 of 32
3. Origin
The following attributes allow to specifically mention the origin of the products.
The attributes related to the life of animals (cattle, sheep,…) shall only be completed
when relevant.

Country of origin (will be replaced by AVP CountryOfOriginStatement)
i. Where : ID / Classification / Description / Taxes / Production / BarCode
ii. GDSN name : tradeItemCountryOfOrigin
iii. GDSN definition : the country code(s) in which the goods have been produced or
manufactured, according to criteria established for the purposes of application of
the value may or may not be presented on the trade item label.
iv. Instruction : use the country codes used in GDSN to indicate the relevant country.
v. Remark : the regulation 1169/2011 is, at this point, not 100% clear about the
information and use cases concerning this attribute. We will keep the community
updated if the method or content that has to be introduced in this attribute changes.
For now, we advise to enter the most correct information/country code possible.
vi. Example : 056 for Belgium, 528 for The Netherlands

Place of birth (not yet available in trustbox)
ii. GDSN name : placeOfBirth
iii. GDSN definition : The place the mammal, species was born. The place may be a
country, region (land or sea), city, etc. Since a company may have multiple facilities
in multiple countries, the attribute needs to be repeating to reflect the potential
places. The actual birth place of a particular animal would be transactional.
iv. Instruction : /
v. Remark : free text field
vi. Example : Mediterranean see

Place of rearing (not yet available in trustbox)
ii. GDSN name : placeOfRearing
iii. GDSN definition : Is the place the mammal, species was raised after birth to the
end of the animals’ life. The place maybe a country, region (land or sea), city, etc.
Since a company may have multiple facilities in multiple countries, the attribute
needs to be repeating to reflect the potential places. The actual rearing place(s) of
a particular animal would be transactional.
iv. Instruction : /
vi. Example : South-Africa
2014, version 6
page 14 of 32

Place of slaughter (not yet available in trustbox)
ii. GDSN name : placeOfSlaughter
iii. GDSN definition : Is the place the mammal, species was killed to be processed for
food, or other purposes. The place maybe a country, region (land or sea), city, etc.
Since a company may have multiple facilities in multiple countries, the attribute
needs to be repeating to reflect the potential places. The actual slaughter place of
a particular animal would be transactional.
iv. Instruction : /
vi. Example : Belgium
4. Preparation, use and storage
The next attributes give indications on how to prepare the product, and how to store it.

Instructions for use (will be replaced by AVP
UnspecifiedPreparationTypePreparationInstructions)
i. Where: Extension Food & Beverage - Diet / Preparation / Product Yield / Additive
Information
ii. GDSN names: preparationType and preparationInstructions
iii. GDSN definition:
1. preparationType: A code specifying the technique used to make the
product ready for consumption.
2. preparationInstructions: Textual instruction on how to prepare the
product before serving.
iv. Instruction: Instructions for use where it would be difficult to make appropriate
use of the food in absence of instructions
v. Remark: Complete this information in all relevant languages for the target market
as mentioned on the physical package.
vi. Example:
1. Baking, boiling
2. Heat the oven to 200°C, unpack the pizza from the box, remove the
plastic foil, bake the pizza for 12minutes, remove carefully from the
oven, slice the pizza before serving
2014, version 6
page 15 of 32

Special storage conditions
i. Where: Handling / Storage / Transport / Packaging
ii. GDSN name: consumerUsageStorageInstructions
iii. GDSN definition: Expresses in text the consumer storage and usage instructions
of a product which are normally held on the label or accompanying the product. This
information may or may not be labelled on the pack. Instructions may refer to a
suggested storage temperature, a specific storage requirement or a reference to
environment or duration.
iv. Instruction: /
v. Remark: Complete this information in all relevant languages for the target market
as mentioned on the physical package.
vi. Examples: “Refrigerate After Opening”, “Consume within 4 days” “Keep Out Of
Direct Sunlight” ,”Store at an Ambient Temperature”, “Store in a Clean, Cool, Dry
Place”, “Store Away From Sunlight, Strong Odours and Chemicals”, etc.
5. Allergens
Please indicate following attributes for each allergen where relevant. You can use the
add or the copy function to duplicate the allergen box in order to insert multiple allergens:

Allergen specification agency :
vii. Where : Food and Beverage extension - Allergy Related / Microbiological /
viii. GDSN name : allergenSpecificationAgency
ix. GDSN definition : Agency that controls the allergen definition.
x. Instruction : The applicable legal regulatory agency. Currently the EU.
xi. Remark : /
xii. Example : EU
2014, version 6
page 16 of 32

Allergen specification name :
i. Where : Food and Beverage extension - Allergy Related / Microbiological /
ii. GDSN name : allergenSpecificationName
iii. GDSN definition : Free text field containing the name and version of the regulation
or standard that contains the definition of the allergen.
iv. Instruction : most applicable legislation as used to fill the following attributes: EU
1169/2011. For labels that have not yet been adjusted to the new legislation, use
2003/89.
v. Remark : /
vi. Example : 1169/2011

Allergen type code :
ii. GDSN name : allergenTypeCode
iii. GDSN definition : Code indicating the type of allergen.
iv. Instruction : Use the code list in appendix with the following rules:
 14 allergens are legally mandatory to mention if present
 Other allergens are optional
 If the product is free from an allergen, it is optional to mention
this here.
 If the product may contain an allergen, it is optional to mention
this here.
 If an allergen is not mentioned here, it may not be
interpreted as free-from.
v. Remark :
vi. Example : AF, AE, AM,…

Level of containment :
ii. GDSN name : levelOfContainment
iii. GDSN definition : Code indicating the level of presence of the allergen.
iv. Instruction : /
v. Remark : /
vi. Example : MAY_CONTAIN, CONTAINS,
2014, version 6
page 17 of 32
6. Nutrients
Per product it’s possible to enter the number of servings contained in a package:

Number of household servings per package
(at the top of the Food&Beverage Extension Tab):
i. Where :
Extension Food & Beverage - Serving/Ingredient/Nutrient
Information
ii. GDSN name : numberOfServingsperPackage
iii. GDSN definition : The total number of servings contained in the package
iv. Instruction : /
v. Remark : The household serving is defined with attribute householdServingSize
vi. Example : 5
First, for each product it’s necessary to define if the information for the nutrients is provided
for the PREPARED or UNPREPRARED product. A PREPARED state is for example the state of
the product after adding water, milk, etc.

preparationState
i. Where :
Information
ii. GDSN name : preparationState
iii. GDSN definition : Code specifying whether the nutrient information applies to the
prepared or unprepared state of the product.
iv. Instruction : Use PREPARED or UNPREPARED
v. Remark : /
vi. Example : UNPREPARED
If it’s necessary to provide both nutritional information for the PREPARED AND UNPREPRARED
state of a product, it is necessary to duplicate the attribute and all it’s related sub-attributes:
Duplicate the box in CDB under the “Nutrient” title by clicking either on the “add” button
(green “+”) or the “copy” button (white sheet) in the [purple box]).
Select the “preparation state” for the box that will be completed [orange box]: prepared or
unprepared.
When the preparation state distinction is not relevant, select the “unprepared” state of the
product in order to insert nutrient information for the product.
2014, version 6
page 18 of 32
Second, define the Nutrients that you want to enter:
The 3 dependent attributes that need to be completed for each nutrient are:
-

Nutrient type code
Measurement precision
Quantity contained + UoM
Nutrient type code
i. Where :
Information
ii. GDSN name : nutrientTypeCode
iii. GDSN definition : Code from the list of the INFOODS food component tagnames
(in annex) identifying nutrients contained in the product.
iv. Instruction : Nutrient type code can be found in the NutrientCodeList in appendix,
or by using the search function in the web UI.
v. Remark : /
vi. Example : ENER- (remark: this is the energy code for both kcal and joule)

Measurement precision
i. Where :
Information
ii. GDSN name : measurementPrecision
iii. GDSN definition : Code indicating whether the specified nutrient content is exact
or approximate.
2014, version 6
page 19 of 32
iv. Instruction : /
v. Remark : /
vi. Example : LESS_THAN or APPROXIMATELY

Quantity contained + UoM
i. Where :
Information
i. GDSN name : quantityContained + UoM (Unit of Measure)
ii. GDSN definition : Measurement value indicating the amount of nutrient contained
in the product. Is expressed relative to the serving size.
iii. Instruction : This has to be accompanied by a valid UoM (e.g. GR for grams).
iv. Remark : The nutrient UoM must strictly conform to the values specified in the
appendix; today trustbox cannot convert values from one UoM to another.
v. Example : 2 GR
For minerals and vitamins, 3 more attributes should be used :

Percentage of daily value intake
i. Where: Extension Food & Beverage - Serving/Ingredient/Nutrient Information
ii. GDSN name : percentageOfDailyValueIntake
iii. GDSN definition : The percentage of the recommended daily intake of a nutrient as
recommended by authorities of the target market. Is expressed relative to the
serving size and base daily value reference intake.
iv. Instruction : /
v. Remark : Mandatory only for minerals and vitamins per 100ml or 100gr.
vi. Example : 15

Reference intake + language
i. Where :
Information
ii. GDSN name : dailyValueIntakeReference
iii. GDSN definition : Free text field specifying the daily value intake base for on which
the daily value intake per nutrient has been based
iv. Instruction : insert the descriptions of reference intake in each relevant language
(use the add/copy function) and choose language code (e.g. ‘en’ for English, ‘nl’ for
Dutch, ‘fr’ for French, ‘de’ for German, etc.)
v. Remark : Mandatory only for Minerals and Vitamins.
vi. Example : “Based on a 2000 calorie diet.”
2014, version 6
page 20 of 32

Percentage of daily value intake measurement precision (not yet available in
trustbox or GDSN)
i. Where : AVP to be added
ii. GDSN name : DailyValueIntakePercentMeasurementPrecisionCode
iii. GDSN definition : Code indicating whether the specified nutrient content for the
Daily Value Intake % is exact or approximate or less than.
iv. Instruction : This attribute is an AVP in GDSN v2.8. The structure of this AVP is :
“nutrientTypeCode:MeasurementPrecision”. The value of nutrientTypeCode is used
in the AVP to indicate the nutrient the measurement precision is given for.
v. Remark : This attribute should be populated only if the following signs “<”, “<=”,
“>”, “>=” appear on the pack for the percentage of daily value intake.
vi. Example : If the percentage of daily value intake for vitamin D is “< 1 µg” then the
value of DailyValueIntakePercentMeasurementPrecisionCode is:
“VITD-:LESS_THAN”
To enter the information for a second nutrient, please duplicate the ‘Nutrient box’, by clicking
on the add or the copy button in the [purple box]. You will now be able to re-enter the
nutritional attributes for the second nutrients.
GOOD TO KNOW: When selecting the “copy” option, the duplicated box will contain the
same information than the original box; which can be useful when product information is
similar for different attributes.
2014, version 6
page 21 of 32
Energy in kJ or kCAL (ENER-)
Starch
Vitamin K
Fat of which
Fibre
Vitamin C
Saturates
Protein
Thiamin
Mono-unsaturates
Salt
Riboflavin
Polyunsaturates
Sodium
Niacin
Vitamin A
Vitamin B6
Sugars
Vitamin D
Folic Acid
Polyols
Zinc
Vitamin B12
Pantothenic Acid
Copper
Molybdenum
Potassium
Manganese
Iodine
Chloride
Fluoride
Magnesium
Calcium
Selenium
Iron
Phosphorus
Chromium
Vitamin E
Carbohydrate of which
Biotin
Third, define the size for which the nutritional information is stated.

Serving size + UoM
i. Where :
Information
ii. GDSN name : ServingSize + ServingSize UOM
iii. GDSN definition : Indicates the size of a typical serving of the food product as it
should be displayed on the package.
iv. Instruction : ! Use per 100g or 100ml since this is the legally required way of
stating the information as mentioned in the EU 1169/2011 regulation.
v. Remark : /
vi. Example : 100 GR or 100 ML
2014, version 6
page 22 of 32
7. Claims
These attributes are free-text fields that can be used to express health, nutritional
(chosen from an approved EU list) or marketing claims.

Health Claim
i. Where : Extension Food and Beverage – Marketing Information
ii. GDSN name : healthClaim
iii. GDSN definition : Free text field for any health claims according to regulations of
the target market.
iv. Instruction : Warning - consult http://ec.europa.eu/nuhclaims to select an
authorized claim as not all claims are authorized.
v. Remark : mandatory when stated on the label
vi. Example : “Fluoride contributes to the maintenance of tooth mineralization”

Nutritional Claim
i.
ii.
iii.
iv.
Where : Extension Food and Beverage – Marketing Information
GDSN name : nutritionalClaim
GDSN definition : Free text field for any additional nutritional claims.
Instruction : Warning - consult http://ec.europa.eu/nuhclaims to select an
authorized claim as not all claims are authorized.
v. Remark : mandatory when stated on the label
vi. Example : “ENERGY-REDUCED”

Marketing Message
i.
ii.
iii.
iv.
v.
Where : Order / Shipment / Marketing / Prices / Season / Colour
GDSN name : tradeItemMarketingMessage
GDSN definition : marketing message associated with the trade item.
Instruction : insert free text. For marketing claims as stated on the label.
Remark : optional field to comply with EU 1169/2011 regulation. This attribute can
only be entered in one language. Enter all marketing messages in all languages in
this attribute.
vi. Example : “better taste” “new formula”
2014, version 6
page 23 of 32
8. Labels
« Labels » regroups the attributes providing the possibility to identify certain hallmarks
the trade item complies with.

Diet allergen marks
i. Where : Handling / Storage / Transport / Packaging
ii. GDSN name : packageMarksDietAllergen
iii. GDSN definition : Indication of which dietary or allergen marks that are on the
package.
iv. Instruction : use a code from the dropdown list in CDB.
v. Remark : not mandatory fields to comply with the EU 1169/2011 regulation.
Optional.
vi. Example : VEGETARIAN, HALAL, KOSHER,…

Free from marks
ii. GDSN name : packageMarksFreeFrom
iii. GDSN definition : Indication of the food ingredients that the package is marked
free from.
Optional.
vi. Example : FREE_FROM_GLUTEN, FREE_FROM_EGG

Ethical marks
ii. GDSN name : packageMarksEthical
iii. GDSN definition : Indication of which ethical trading marks that are on the
package.
v. Remark : many specific ethical marks are not (yet) available in CDB but these
attributes are not mandatory to comply with EU 1169/2011.
vi. Example : FAIR_TRADE_MARK
2014, version 6
page 24 of 32

Environmental marks
ii. GDSN name : packageMarksEnvironment
iii. GDSN definition : Indication of which environmental marks that are on trade item
package.
Optional.
vi. Example : (e.g. recycling schemes)

Hygienic marks
ii. GDSN name : packageMarksHygienic
iii. GDSN definition : An indication of which hygiene markings are present in the
product package. Hygiene markings are defined as those related to packaging
conditions or practices intended to the preservation or promotion of health.
Optional.
vi. Example : EXTREMELY_CLEAN, STERILE
2014, version 6
page 25 of 32
9. How to add a packshot image? (not mandatory)

Image URL: It’s possible to send a packshot to trustbox via a URL by using 4
dependent attributs in GDSN
i. Where : Trade Item External Information / Contact Information
ii. GDSN name : Type Of Information + File Name + File Format Name + Uniform
Resource Identifier +
iii. GDSN definition : Uniform Resource Locator (URL) that references a World-Wide
Web resource (e.g. pack shot) providing information about the product.
iv. Instruction :
1. Complete the attribute “type of information” with the value
“PRODUCT_IMAGE”
2. Complete the attribute “File Name” with the name of the file. E.g.
“Picture of product A”
3. Complete the attribute “File Format Name” with the format. E.g.
JPG, EPS, etc.
4. Complete the attribute “Uniform Resource Identifier” with the
url of the image
v. Remark : This is not a mandatory attribute for the EU 1169/2011 regulation. Since
the link to the image will be provided to the retailer, the image must be freely
accessible.
vi. Example : http://3.bp.blogspot.com/ApQR_7m9hXo/UD4ROSZgtuI/AAAAAAAAAGg/SSl3kQaAYq8/s200/mayonaise.jpg
Refers to the following picture:
2014, version 6
page 26 of 32
10.
Particular cases / General recommandations
Mixed products management
Example:
Certain products, that are a composition of different types of products, may have more than one
ingredient statement and/or nutritional tabel on their label. For these types of mixed products
the following guidelines have been determined within Europe:
Ingredients:
Mention all the ingredient statements for the different components in the ingredientStatement
attribute, starting with the name of the product described (text field limited to 5000 characters).
Example: “Ingredients Rice Krispies: Rice, sugar, contains 2% or less of salt, malt flavor. #
Ingredients Coco Pops: Rice, Sugar, Chocolate (4%)(Sugar, Cocoa Mass), Fat Reduced Cocoa
Powder, Salt, Barley Malt Flavouring, Flavouring, etc.
Nutrients:
For the nutritional declaration, it’s recommended to use an average of the nutritional
information.
Separator in text fields
Lots of fields described in this document are unformatted free text. To better stick with the
packaging layout, some formatting information may be transmitted. However, it’s forbidden to
use ‘enters’ in the text!
The target solution is to use formatting pattern to separate and format texts. As long as this
feature is not implemented, we recommend to use ‘#’ to separate two independent parts of the
field.
2014, version 6
page 27 of 32
11.
Appendixes
How to enter an attribute through the AV Pair Extension:
-
Open the tab ‘Extension: ‘AV Pair/ Specific technical Characteristics’
-
You can either enter the attribute name in the blue frame, or search for a specific
attribute in the orange frame. Once an attribute is selected, the description is available
in the green frame.
-
You can enter the value for the attribute in the big frame below:
-
To enter multiple ‘AV Pair’ attributes, copy the frame by clicking the green ‘plus’
sign at the right hand of the box (see purple arrow).
In order to enter this attribute in multiple languages, please duplicate the attribute
(icon next to the purple arrow) and use the ISO language codes followed by a double
colon and the label description. E.g. ‘nl: …..’, ‘fr: …..’,’de:…’, ‘en:…’, etc.
-
Note 1: There are no specific built-in validation rules in the AV Pair attributes.
Note 2: It is possible to insert data receiver specific values for AV pair attributes into GDSN. As
there is only one “data receiver” when sending information to trustbox, please don’t use this
functionality.
Note 3: Do not use ‘enters’ to format the text.
2014, version 6
page 28 of 32
Allergen code list
Code
AE
AF
AM
AN
AP
AS
AU
AW
AY
BC
BM
NL
UM
AC
UW
NC
NK
NM
NP
NR
NW
AH
AI
AL
AX
BA
BB
BE
BI
BS
CA
CL
CN
CO
CT
EG
EP
EV
FA
GB
Description
Eggs and their derivates
Fish and their derivates
Milk and it’s derivates
Nuts and their derivates
Peanuts and their derivates
Sesame Seeds and their derivates
Sulphur Dioxide and Sulphites and their derivates
Cereals containing gluten and their derivates
Soybeans and their derivates
Celery and their derivates
Mustard and it's derivates
Lupine and it's derivates
Molluscs and their derivates
Crustaceans and their derivates
Wheat and it's derivates
Cocoa and it's derivates
Coriander and it's derivates
Corn and it’s derivates
Pod Fruits and their derivates
Rye and it’s derivates
Carrots and their derivates
anise alcohol
alpha-Isomethyl Ionone
amyl cinnamal
other gluten containing grain and gluten containing grain
products
benzyl alcohol
benzyl benzoate
butylphenyl methylpropionate
benzyl cinnamate
benzyl salicylate
cinnamyl alcohol
cinnamal
citronellol
coumarin
citral
eugenol
evernia prunastri
evernia furfuracea
farnesol
barley and barley products (glutencontaining grain)
2014, version 6
Mandatory*
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
optional
not applicable
optional
optional
optional
optional
optional
optional
page 29 of 32
European nutrient code list (INFOODS)
Name of Nutrient
Energy
Code
ENER-
Fat
of which saturates
of which mono-unsaturates
of which polyunsaturates
Carbohydrate
of which sugars
of which polyols
of which starch
Fibre
Protein
Salt
Vitamin A
Vitamin C
Calcium
Iron
Vitamin D
Vitamin E
Vitamin K
Thiamin
Riboflavin
Niacin
Vitamin B6
Folic Acid
Vitamin B12
Biotin
Pantothenic acid
Potassium
Chloride
Phosphorus
Zinc
Copper
Manganese
Fluoride
Selenium
Chromium
Molybdenum
Iodine
Magnesium
FAT
FASAT
FAMSCIS
FAPUCIS
CHOAVL
SUGARPOLYL
STARCH
FIBTG
PROSALTEQ
VITAVITCCA
FE
VITDVITEVITK
THIA
RIBF
NIA
VITB6FOLDFE
VITB12
BIOT
PANTAC
K
CLD
P
ZN
CU
MN
FD
SE
CR
MO
ID
MG
2014, version 6
UoM
E14 (kilocalorie)
KJO (kilojoule)
GR
GR
GR
GR
GR
GR
GR
GR
GR
GR
GR
MC (microgram)
ME (milligram)
ME
ME
MC
ME
MC
ME
ME
ME
ME
MC
MC
MC
ME
ME
ME
ME
ME
ME
ME
ME
MC
MC
MC
MC
ME
page 30 of 32
12.
Contact
For helpdesk questions please contact the data team of GS1 Belgium & Luxembourg via
CDB.support@gs1belu.org. For a general CDB training, please visit www.gs1belu.org and go
to the ‘training’ section. There you will be able to subscribe to the next (free) seminar about
CDB.
2014, version 6
page 31 of 32
2014, version 6
GS1 Belgium &
Luxembourg
Koningstraat 76 b1
BE – 1000 Brussel
T +32 (0) 2 229 18 80
F +32 (0) 2 217 43 47
E
CDB.support@gs1belu.org
page
32 of 32
www.gs1belu.org
GS1 is a registered trademark of GS1 AISBL

How to comply with the EU 1169/2011 regulation via GDSN prepj

Transcription

Similar documents

How to Do Business With - Foodbuy

Nutrient Codes

Master Data Management and Data Synchronization

gs1 standards

Asian Market and ÆON Group Product Data Management

How to Do Business with SUPERVALU

How To Do Business with McLane

Ana Paola Negretto, Hospital and Maternity Santa Joana

205: Understanding Fulfillment Models – The Buyer`s