/
3 Data Preparation Stage 3

3 Data Preparation Stage 3

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

Table of Contents

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.

Illustration 6: Data structure in stage 3

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

After consultation, an alternative representation of the specifications can be used (variant 2: Column). This variant offers more flexibility in terms of presentation and format. This special case allows the preparation in .xlsx format as well as the combination with other data (e.g. ProductData or MediaData).

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

  • 1 line per article and specification

  • Specification and value in combination per line

  • 1 line per article

  • Specifications in the headers

  • Specification values in the cells

Sorting

  • Sorted by ProviderKey (ascending)

  • free

Suitable for

  • Many different specifications

  • few different specifications

 

Requirements for the structure

Specifications with multiple values can be delivered in two options:

One SpecificationValue per line (preferred)

ProviderKey

SpecificationKey

SpecificationValue

item_01

color

black

item_01

color

yellow

item_01

color

blue

item_01

material

plastic

item_01

material

metal

Alternativ: Multiple SpecificationValue per SpecificationKey

Within a key-value pair, we can handle only one delimiter.

Allowed delimiters for multiple values are: "," (comma),"/" (slash), "|" (pipe), ";" (semicolon).

Delimiters are searched in the order listed above ( , / | ; ).

Once a delimiter is detected, any subsequent different delimiters are ignored.

ProviderKey

SpecificationKey

SpecificationValue

item_01

color

black|yellow|blue

item_01

material

plastic|metal

What happens with different delimiters:

Provider_SpecificationValue

DG_SpecificationValue

Schwarz , Gelb | Blau

Schwarz Gelb | Blau

Obermaterial 1: 100% Polyester; Obermaterial 2: 95% Polyester, 5% Elasthan

Obermaterial 1: 100% Polyester; Obermaterial 2: 95% Polyester 5% Elasthan

ProviderKey

color

material

size

target group

item_10

blue

Cotton

M

women

item_11

red

Polyester

M

women

item_12

yellow

Cotton

M

men

item_13

yellow, black

Cotton

L

men

Use the following CSV-sample

Use the following XLSX-sample

 

Option 1: Key-Value-Pair (Standard)

Header

Data type

Designation

Description

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

  • German and English are preferred languages. For other languages, please contact your Digitec Galaxus representative.

  • For each item number listed in this file, there must be at least one "SpecificationKey" and one "SpecificationValue" in one language.

SpecificationValue

Str(200)

Specification value

Specification value

  • German and English are preferred languages. For other languages, please contact your Digitec Galaxus representative.

  • For each item number listed in this file, there must be at least one "SpecificationKey" and one "SpecificationValue" in one language