/
2 Data Preparation Stage 2

2 Data Preparation Stage 2

DATA INTEGRATION STAGE 2

Product creation/New assortment

The aim of the second integration stage is to map their full range by expanding the master data. Additional product data is needed for the realisation. They serve to clearly identify, categorise and present the products so that they can be purchased by the end customer.

The new files or required extensions are documented in this chapter.

A prerequisite for the implementation of stage 2: product creation is a completed and productive stage 1!

Back to stage 1: offer creation and allocation

Table of Contents

DATA STRUCTURE

In addition to the existing offer data, further aspects are now added to the master data as well as the media for the products. We recommend preparing the media in another separate file.

Illustration 5: Data structure in stage 2

 

The provider key is the unique article number for an article of the supplier/retailer/provider. It is used as an identification number and must be included in all files supplied.

 

DATA FORMAT

We offer various file formats for data preparation. Select the standard suitable for your application and note the file structure requirements in the following overview. We recommend the CSV standard for automated data preparation, while XLSX files are more suitable for manual interventions in the files.

 

NOTES ON DOCUMENTATION

The documentation of the data structure contains technical terms and notes in various places. These are central to correct data preparation and - if correctly implemented in the files - simplify technical integration enormously. You will find more detailed explanations and examples in the table below.

 

DATA STRUCTURE PRODUCTDATA

General notes on the ProductData

  • File name: ProductData_[ProviderName]. [FILE FORMAT] (Eg: ProductData_digitecgalaxus.csv)

  • Transmission frequency: every 24 hours (optimal: every 12 hours)

Information marked with is already listed in the master data stage 1. The remaining master data listed here can be regarded as an extension of the existing data

Use the following CSV-sample

Use the following XLSX-sample

 

Minimal criteria: ProductData

Header

Data type

Designation

Description

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126

Gtin

Int(8)
Int(12)
Int(13)
Int(14)



EAN/GTIN code of the article

Unique and globally valid identification number of the article. The following data structures are permitted within the GTIN family:

  • GTIN-12 (UPC), GTIN-13 (EAN-13, ISSN, ISBN), GTIN-14 (EAN/UCC-128 or ITF-14), GTIN-8 (EAN-8)

  • The EAN/GTIN forms the basis for our automated allocation and product creation processes. Therefore, request GTINs for your products for a smooth data transfer: GS1 Switzerland: Request barcode, GS1 Germany: Request barcode

  • The EAN/GTINs must be unique and globally valid. Duplicates are not permitted.

  • The EAN/GTIN must be visible on the retail packaging.

  • Further information on Gtins and GS1 at: http://gtin.info

  • or GS1 Switzerland.

BrandName

Str(100)

Brand / Publisher

Manufacturer's brand of the item.

Products can only be created/processed with an associated mark.

CategoryGroup_[index]

Str(200)

Category groups of the article

The category groups, starting with the highest level CategoryGroup _1, together form a category family tree that assigns the item hierarchically.

  • "index" - Consecutive numbering of the CategoryGroups, E.g.: CategoryGroup_1, CategoryGroup_2, CategoryGroup_3, …

  • The category groups are not mandatory if the product categories (see ProductCategory) are complete and clearly assignable.

ProductCategory

Str(200)

Product category of the article

The product category is the deepest (most detailed) level of all categories.

  • The Digitec Galaxus category structure is available for download here:

  • It is not mandatory to name the categories in the data transmission exactly the same as Digitec Galaxus. A partner-specific categorisation can also be used, from which Digitec Galaxus will automatically create a category matching.

  • For the preparation of product specifications (also known as product attributes) 3 Data Preparation Stage 3, a property structure per ProductCategory can be provided on request.

Weight_[unit]

Dec(8,4)

Packaging weight [mg,g,kg]

Packaging weight: Product weight plus original packaging of a retail package.

  • Items without weight are categorically excluded for EU hub merchants

  • "unit" - mögliche Einheiten: mg (Milligramm), g (Gramm), kg (Kilogramm)

ProductTitle_de

Str(100)

German article/product name

Cleaned name of the item for the German-speaking region. Product names must be uniform and cleansed of specifications.

  • The provieded product title will be used as title in german.

  • The quality of the product names is crucial for a consistent appearance in the online shop and the buyability of the products. Please note our guidelines on data quality.

TARICCode

Int(6-11) od. Str(14)

Commodity code (TARIC) for the EU

TARIC database, normally consists of 11 characters (without spaces) or 14 characters (with spaces), e.g. "49019900009" or "4901 9900 00 9".

The validation of the content only allows optional spaces. Other special characters are not allowed. Tariccodes with less than 11 characters are padded with zeros at the end (right).

CountryOfOrigin

Str(2)

Country of origin

The country of origin is considered to be the country in which the goods were entirely obtained or produced, or in which the last substantial processing was carried out.

Please note EU Rules of Origin

  • CountryOfOrigin in the ISO 3166 ALPHA-2 standard, e.g. CH, DE

  • Only one CountryOfOrigin may be transmitted per article number

 

Supplementary criteria for product safety regulations: ProductData

Header

Data type

Designation

Description

Header

Data type

Designation

Description

GPSRNameAddress

Str(300)

Name and postal address of manufacturer

The company name and the postal address of the manufacturer importing the product into the European Economic Area (EEA).

  • Format: "{name}, {street} {number}, {zip code} {town}, {country}"

  • Example: "Mustermann GmbH, Musterstraße 123A, 12345 Musterstadt, Deutschland"

  • Commas separate the different parts of the address (name, street and number, zip code and city, country).

  • Spaces separate street and house number as well as zip code and city.

  • Country: Use the full country name or the ISO 3166-1 alpha-2 code (e.g. "Deutschland" or "DE").

  • Address suffix (optional): If necessary, you can add additional information such as "c/o" or "floor" after the name, e.g. "Mustermann GmbH, c/o Max Mustermann, Musterstraße 123A, 12345 Musterstadt, Germany".

GPSREmailUrl

Str(200)

Email address or URL

The email address or the URL of the manufacturer importing the product into the European Economic Area (EEA).

  • The URLs must be accessible.

Warnings can be transmitted as before via the specification feed (stage 3).

Supplementary criteria for optimising data quality: ProductData

Header

Data type

Designation

Description

Header

Data type

Designation

Description

ManufacturerKey

Str(4-50)

Manufacturer number of the article

Unique identification number of the manufacturer of a product. Manufacturer numbers must be unique within the same brand/manufacturer.

  • Manufacturer numbers must contain at least four characters.

  • Duplicate manufacturer number-brand combinations are categorically excluded.

Length_[unit]

Dec(8,4)

Packing length

Width of the original packaging

"unit" - possible units: mm (millimeter), cm (centimeter), m (meter)

Width_[unit]

Dec(8,4)

Packaging width

Width of the original packaging

"unit" - possible units: mm (millimeter), cm (centimeter), m (meter)

Height_[unit]

Dec(8,4)

Packing height

Height of the original packaging

"unit" - possible units: mm (millimeter), cm (centimeter), m (meter)

ReleaseDate_[country]

Date

Publication date

Date information for new publications. The date is displayed in the shop.

"country" based on standard ISO 3166 ALPHA-2, e.g. ReleaseDate_CH

TARESCode

Str(9)

Swiss customs tariff number (TARES)

TARES database, e.g. "12345678" od. "1234.5678"

  • The validation of the content only allows the optional character "." (dot). Other special characters are not allowed

  • Regex for validation: /^([0-9]{4})\.?([0-9]{4})$/

WEEENumber

Str(10)

WEEE Number

e.g. “DE12345678”

  • Only transmit valid WEEE numbers. If the partner deregisters from the EAR register (market exit), the number may no longer be transmitted.

  • If more than one WEEE number are maintained, the most recent number should be transmitted.

VariantName

Str(100)

Family name/variant name

Unique identification for items that belong together. Digitec Galaxus uses this information to create product variants

It is recommended to use the ProductTitle without additions as this is already identical for many products with variants

ProductTitle_[language]

Str(100)

Item name/Product name [en,fr,it]

Cleaned name of the item in a complementary language English, French or Italian. Product names must be consistent and cleansed of specifications.

  • The quality of the product names is crucial for a consistent appearance in the online shop and the buyability of the products. Please note our guidelines on data quality.

  • "language" based on standard ISO 639-1, e.g. ProductTitle_en, ProductTitle_fr, ProductTitle_it

LongDescription_[language]

Str(4000)

Detailed description of the article [de,en,fr,it].

Detailed description of the item with relevant information about the product such as size, material, age range, special features, technical specifications, shape, pattern, fabric type, design).

  • The quality of the product description is crucial for a consistent appearance in the online shop and the buyability of the products. Please note our guidelines on data quality.

  • The product description is kept general and does not contain any advertising texts or partner-specific information.

  • Web links and bullet points are not allowed.

  • One of the languages German, English, French or Italian is compulsory.

    "language" based on ISO 639-1 standard, e.g. LongDescription_en, LongDescription_fr

Composition_[language]

Str(4000)

Composition [de,en,fr,it]

Description of the composition or ingredients of a product. These are required by law for specific product groups, i.e. they are compliance-relevant.

  • These are e.g.:

    • List of ingredients (all ingredients contained in a food must be listed)

    • Allergy declaration (ingredients and the products made from them that may cause allergies or other adverse reactions must be specifically identified)

    • Ingredients (e.g. perfume)

  • The quality of the product names is crucial for a consistent appearance in the online shop and the buyability of the products. Please note our guidelines on data quality.

  • “language” based on ISO 639-1, e.g. Composition_de, Composition_en, Composition_fr

Application_[language]

Str(4000)

Application [de,en,fr,it]

Description of the application of a product. These are required by law for specific product groups, i.e. they are compliance-relevant.

  • This applies to the following product groups:

    • Medical devices

    • Medicine

  • The quality of the product names is crucial for a consistent appearance in the online shop and the buyability of the products. Please note our guidelines on data quality.

  • “language” based on ISO 639-1, e.g. Application_de, Application_en, Application_fr

 

Optional criteria for future optimisation of ProductData

The following information cannot be processed at the moment. However, we are constantly optimising our technical systems and will expand the information processing for corresponding fields in due course. Supplying the information in the data files helps us to better assess the relevance and prioritisation of future extensions.

Header

Data type

Designation

Description

Header

Data type

Designation

Description

WarrantyPeriod

Int(3)

Warranty period

Service case type: Warranty. Manufacturer's specifications. (in months)

DeadOnArrivalPeriod

Int(3)

DOA deadline

Service case type: DOA (Dead on Arrival). Manufacturer's specifications. (in days)

A DOA case is considered to be all directly recognisable defects in the product that already existed at the time of delivery to the end customer or that occur within the specified DOA period.

ReturnType

Int(1)

Return type

1: BringIn, 2: OnSite, 3: PickUpAndReturn / manufacturer's information

MinimumAge_[country]

Int(2)

Legal age limit

Legal age limit (in years)

"country" based on standard ISO 3166 ALPHA-2, Bsp: MinimumAge_DE

NutritionalValue_language

Str(4000)

Nutrition labelling

Nutritional values in continuous text form

ProductRemark

Int(2)

Product remarks

1: small parts, 2: assorted colours, 3: biocidal products, 4: plant protection products, 5: electrical safety, 6: delivery of tyres, 7 animal encolusre, 8: CO2 Emissions

Product information is displayed in the shop on the product page.

FILE STRUCTURE MEDIA DATA

General information on the Media Data

  • File name: MediaData_[ProviderName]. [FILE FORMAT] (Ex: MediaData_digitecgalaxus.csv)

  • Transmission frequency: every 48 hours (optimal: every 24 hours)

Use the following CSV-sample

Use the following XLSX-sample

 

Minimal criteria: Media Data

Header

Data type

Designation

Description

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126