Stage 1: Alternative Approach
DATA STRUCTURE
For the fastest possible activation of the complete assortment, the master data of the items as well as stock and price data are required. For a successful data flow, it is essential to provide structurally stable files. Therefore, it is strongly recommended that these three information areas be split into three separate files, provided that stock levels are transmitted with a delay.
ASSORTMENT DETERMINING FILE
One of the files is the assortment-determining file (assortment file), which controls the active assortment. Only items that are included in the assortment file are activated.
Items that can no longer be delivered or are considered EOL products (products with no active offer in the system), must be removed from the respective file—ideally from all files—no later than with the next transmission.
We recommend controlling the assortment via the price data.
The file name must include the identifier for the assortment file:
Example: StockData_BeispielAG_assortment.csv
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.
MASTER DATA FILE STRUCTURE
General notes on master data
File name: ProductData_[ProviderName].[FILE FORMAT] (e.g., ProductData_digitecgalaxus.csv)
Transmission frequency: every 24 hours (optimal: every 12 hours)
The minimum criteria listed here are only relevant for offer data creation and assignment.
We recommend that anyone who wants to benefit from the automated creation of new assortments implements the advanced data preparation of the master data directly in “Stage 2: Product creation”.
→ Go directly to Master Data Preparation "Stage 2: Product creation"
Use our CSV template
Use our XLSX-Template
Minimum Criteria: Master Data
Header | Data type | Designation | Description |
|---|---|---|---|
ProviderKey | Str(50) | Partner-specific item number | Unique identification number of the partner item.
|
MainGtin | Int(8)
| Main EAN/GTIN code of the sales unit (consumer unit) | Unique and globally valid identification number of the manufacturer’s item. The following data structures within the GTIN family are permitted:
|
Gtin_[index] | Int(8) | Additional / new EAN/GTIN code of the sales unit (consumer unit) | If multiple GTINs exist for the same sales unit, they must be submitted here. GTINs of the trade unit or logistic unit must not be submitted. GTINs to be submitted as additional GTINs include those that:
The main GTIN once assigned to an item should not be changed.
|
ManufacturerKey | Str(4-50) | Manufacturer Key of the article | Unique identification number of the manufacturer of a product. Manufacturer numbers must be unique within the same brand/manufacturer.
|
PRICE DATA FILE STRUCTURE
General notes on price data
File name: PriceData_[ProviderName].[FILE FORMAT] (e.g., PriceData_digitecgalaxus.csv)
Transmission frequency: every 12 hours (optimal: every 2 hours)
Use our CSV-Template
Use our XLSX-Template
Minimum Criteria: Price Data
Kopfzeile | Datentyp | Bezeichnung | Beschreibung |
|---|---|---|---|
ProviderKey | Str(50) | Partner-specific item number | Unique identification number of the partner item.
|
PriceExclVat_[currency] | Dec(8,4) | Price excluding vat | Digitec Galaxus price excluding VAT and including/excluding product fees.
|
SuggestedRetailPriceInclVat_[currency] | Dec(8,4) | Suggested retail price incl. VAT. | Suggested retail price incl. VAT. "currency": currency specified in the header row as CHF or EUR Not required for merchants. |
VatRatePercentage | Dec(2,2) | Vat Rate | VAT rate as a numeric value without the % sign. Example (Switzerland): 8.1, 2.6, 0.0 Not required for supplier. |
STOCK DATA FILE STRUCTURE
General Notes on Stock Data
Filename: StockData_[ProviderName].[FILEFORMAT] (e.g. StockData_digitecgalaxus.csv)
Transmission Frequency:
Quantity information
All quantity information listed here refers to retail packaging units (Consumer Unit, CU).
If no minimum order quantities and order quantity steps are explicitly provided, all retail packaging units are processed without minimum quantities. Mandatory order quantities (> 1) must therefore be specified according to the fields described below under “Additional criteria to optimize availability and order processing”.
Use our CSV-Template
Minimal:
Extenden:
Use our XLSX-Template
Minimal:
Extenden:
Minimum Criteria: Stock Data
Kopfzeile | Datentyp | Bezeichnung | Beschreibung |
|---|---|---|---|
ProviderKey | Str(50) | Partner-specific item number | Unique identification number of the partner item.
|
QuantityOnStock | Int(5) | Exact stock quantity | We recommend submitting the exact stock level. This value influences the prioritization of the merchant/supplier when selecting sales offers. Negative stocks are treated as backlogs. |
We primarily use “QuantityOnStock” for availability calculation. | |||
RestockTime | Int(3)* | Restock time in business days | Restock or provisioning lead time in business days until the item is back in the partner’s stock (RestockDate – today). National public holidays can be ignored
|
RestockDate | Date | Restock Date | Date when the item is back in the partner’s stock. |
ExpectedRestockQuantity | Int(5) | Expected restock quantity | Expected available stock level at the time the item is back in the partner’s stock.
|
Additional criteria for optimizing availability and order processing