2 Data Preparation Stage 2
DATA INTEGRATION STAGE 2
New assortment
The goal of the second stage is the complete creation and enrichment of your product portfolio. This includes mapping your entire assortment using extended master data and supplementing items with additional information.
For product creation, we require additional product data used for the clear identification, categorization, and presentation of items. The required files and fields are described in this chapter.
A separate file is mandatory for specifications. An optional accessory file allows you to clearly assign accessories to the main items.
A prerequisite for implementing Stage 2 (product creation and enrichment) is the completion of Stage 1.
DATA STRUCTURE
In addition to the existing offer data, additional aspects are now added to the master data, including specifications, media, and accessory links. The specifications must be provided in a separate file. We also recommend preparing the product media as well as other relevant master data in their own separate files.
Option 1 | Option 2 |
|---|---|
|
|
The ProviderKey is the partner’s unique item number for a product. It is used as an identification number and must be included in all delivered files. The ProviderKey is used to consolidate the information.
DOCUMENTATION NOTES
The documentation of the data structure contains technical terms and notes in several places. These are essential for correct data preparation and—if implemented correctly in the files—greatly simplify the technical integration. In the table below, you will find further explanations and examples.
ALL PRODUCT-TYPES
To provide the best possible shopping experience, we need to adapt our structure to our customers' needs. That's why it's constantly changing. To get an overview of our product types (categories), you can download the extract.
For new assortment, correct product type assignment is critical. To achieve the best possible quality, we recommend sending us all the raw data rather than trying to map to our categories yourself. Our product type AI achieves the best results with original data.
Download:
DATA STRUCTURE PRODUCT DATA
General notes on product data
File name: ProductData_[ProviderName].[FILE FORMAT] (e.g., ProductData_digitecgalaxus.csv)
Transmission frequency: every 24 hours (optimal: every 12 hours)
Information marked with is already included in the master data in Stage 1. The information listed in Stage 2 can be added as a supplement to the product data files already implemented.
Use our CSV-Templates
Use our XLSX-Template
Minimum requirements: Product Data
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Partner-specific item number | Unique identification number of the partner item.
|
Gtin | Int(8)
| EAN/GTIN Code of the article | Unique and globally valid identification number of the item. The following data structures within the GTIN family are permitted:
|
BrandName | Str(100) | Brand / Publisher | Manufacturer brand of the item. Products can only be created/processed if a corresponding brand is provided. |
CategoryGroup_[index]
| Str(200) | Category groups of the article | The category groups, starting with the highest level CategoryGroup_1, together form a category tree that assigns the item hierarchically.
|
ProductCategory | Str(200) | Product category of the article | The product category represents the lowest (most detailed) level of the category tree.
|
PackagingWeight_[unit] | Dec(8,4) | Packagin weight [mg,g,kg] | Packaging weight / gross weight: product weight plus the original packaging of a retail unit.
|
ProductTitle_[language] | Str(100) | Article/Product name | Cleaned item name in one of the following languages: German, English, French, or Italian. Product titles must be consistent and free of specifications.
|
CountryOfOrigin | Str(2) | Country of origin | The country of origin is the country in which the goods were wholly obtained or produced, or in which the last substantial processing was carried out.
|
Additional requirements for EU partners
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).
|
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).
|
WEEENumber | Str(10) | WEEE Number | Example: “DE12345678”
|
Warnings can be transmitted as before via the specification feed .
Optional criteria for optimising data quality: ProductData
DATA STRUCTURE MEDIA
General notes on media
File name: MediaData_[ProviderName].[FILE FORMAT] (e.g., MediaData_digitecgalaxus.csv)
Transmission frequency: every 48 hours (optimal: every 24 hours)
Use our CSV-Template
Use our XLSX-Template
Minimum requirements: Media
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Partner-specific item number | Unique identification number of the partner item.
|
MainImageURL | Str(500) | First image link (HTTPS) | Cropped product image with white background, preferably frontal view. The longest edge of the images must be at least 600px (without border around the product). The size of 8 MB per image must not be exceeded.
Below you will find a selection of tools that enable you to do this: https://i-converter.com/files/jpg-to-url https://app.photobucket.com/explore Digitec Galaxus recommends the tools mentioned above. However, there are no agreements or special conditions for the platforms mentioned. |
ImageURL_[index] | Str(500) | Additional image links (HTTPS) | One link per column. The link must be freely accessible. JPG, JPEG and PNG are supported. The longest edge of the images must be at least 600px (without border around the product). The size of 8 MB per image must not be exceeded.
|
EnergyLabel | Str(300) | Energy label Image link (HTTPS) | One link per column and indication of energy efficiency class.
|