3 Data Preparation Stage 3
- Digitec Galaxus AG
- Nikita Stanimirovic
- Digitec Galaxus AG
- Pier-Luca
DATA INTEGRATION STAGE 3
Enrichment Specifications/Properties
The aim of the third stage is to enrich the created products with further information. This can include properties, accessories and declarations. The more information provided, the higher the filterability and visibility of the products.
For the specifications, preparation in a separate data sheet is mandatory (alternative presentation of the specifications is only possible after consultation). We recommend to transmit the declarations as specifications to enable efficient processing. Finally, the additional Accessory File allows suppliers to display accessories on the product detail page of the main article.
A prerequisite for the implementation of stage 3 are completed and productive stages 1 and 2!
Back to stage 1: Offer creation and allocation
Back to stage 2: Product creation
DATA STRUCTURE
DATA SHARING
In addition to the existing product data and offer data, the specifications, declarations and accessory links are now added.
The specifications must be presented in a separate file (alternative presentation of specifications only possible after consultation). The remaining two files are recommended to be presented separately.
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 SPECIFICATION
Specification
File name: SpecificationData_[ProviderName]. [FILE FORMAT] (e.g.. SpecificationData_digitecgalaxus.csv)
Transmission frequency: every 48 hours (optimal: every 24 hours)
File structure:
Variant 1: Key-Value-Pair (Standard)
Variant 2: Column (special case; only possible after consultation )
The fields must not contain HTML tags
The data quality of the specifications is essential for the buyability f the products. Follow our guidelines on data quality
The data preparation of the specifications can be prepared in two file structures. The following is an overview of the two variants.
| Option 1: Key-Value-Pair (Standard) | Option 2: Column (special case) |
|---|---|---|
Format | CSV-Standard UTF-8 (see data format) | Format according to file formats specified above |
Structure |
|
|
Sorting |
|
|
Suitable for |
|
|
Requirements for the structure
Specifications with multiple values can be delivered in two options:
Option 1: Key-Value-Pair (Standard)
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Partner specific item number | Lines with the same ProviderKeys must be listed one after the other. I.e. the document must be sorted numerically ascending by ProviderKey. |
SpecificationKey | Str(200) | Specification name | Specification name
|
SpecificationValue | Str(200) | Specification value | Specification value
|
Variante 2: Column (Spezialfall)
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Partner specific item number | The item numbers must be unique. Duplicates are not permitted. |
[Specification_1] | Str(200) | Values of the first specification | Specification values of the articles for the specification contained in the header line E.g.. header: "colour", specification values: blue, black, red, etc. |
[Specification_2] | Str(200) | Values of the second specification | Specification values of the articles for the specification contained in the header line E.g. header: "Material", specification values: cotton, polyester, leather, etc. |
… | … | … | … |
[Specification_n] | Str(200) | Values of the n-th specification | Specification values of the articles for the specification contained in the header line E.g. header: "Target group", specification values: ladies, men, children, etc. |
Sustainability as Specifications
Header (SpecificationKey) | Description | Value (SpecificationValue) |
|---|---|---|
Country of Origin | Country of Origin (corresponds to Production Country/Country of Origin) | Origin (Production Country) of the delivered item or country where the majority of value creation has taken place The EU Rules of Origin must be observed. If a GTIN or product has multiple countries of origin because it was manufactured in different countries (usually only the case for large manufacturers), all countries of origin must be provided. Possible values are country names or country codes: Switzerland, China, Ecuador, Thailand, US, UK |
DeclarationData as Specifications
FILE STRUCTURE ACCESSORYDATA
Minimal criteria AccessoryData
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Article number of main article | Article number of the main article |
AccessoryProviderKey | Str(100) | Article number of accessory | Article number of the accessory article (matching to the main article) |