1 Data Preparation Stage 1


DATA INTEGRATION STAGE 1

Offer creation and allocation

By implementing this integration stage, you enable us to create and assign your offers. Here you benefit from the existing product portfolio of our online shop by attaching your offer data to already maintained products (existing assortment).

For the creation and allocation of the data, we need at least your offer data and the identifying product data characteristics of the products. These are automatically matched and assigned with our product portfolio after activation. The minimum criteria are item number, price, stock and EAN/GTIN.

We recommend transmitting the price and stock data separately from the other master data (see figure 4), as this allows different upload frequencies to be configured and makes data processing less error-prone. The article number of the partner article (ProviderKey) must be in the "leading column" of each data sheet. It is used as an identification and allocation feature for their articles throughout the entire data processing chain.


DATA STRUCTURE

The product data of the articles as well as stock and price data are required for the quickest possible activation of the existing assortment. It is essential to provide structurally stable files for a successful data flow. Therefore, it is clearly recommended that these three information areas are divided into three separate files.

Deviating files are possible for the first stage, but should be revised again in the following stages of integration. The revision is additional work on both sides and should be eliminated whenever possible.

 

Illustration 4: Data structure in stage 1

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. The provider key is also shown on all orders to you as the identification number for the article.

 


ASSORTMENT DETERMINING FILE

One of the files corresponds to the assortment file, which controls the active assortment. Only articles listed in the "assortment file" will be uploaded. Articles that can no longer be supplied must at least be removed from the corresponding file (ideally from all files) in the next transmission.

We recommend to define the PriceData as assortment determining file.

The specification of the "assortment file" must be specified in the file name

  • E.g.: StockData_SampleLTD_assortment.csv

 


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.

 


FILE STRUCTURE PRICE DATA SUPPLIER MODEL (RETAIL)

General notes to PriceData

  • File name: PriceData_[ProviderName].[DATEIFORMAT] (Bsp: PriceData_digitecgalaxus.csv)

  • Transmission frequency: each 12 hours (best: each 2 hours)

 

Minimal criteria: PriceData Supplier Model (Retail / Vendor)

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.

PurchasePriceExclVat_[currency]

Dec(8,4)

Purchase price excl. VAT

Digitec Galaxus expects purchase prices excl. VAT and incl./excl. product fees.

 

Supplementary criteria: Price data supplier model (Retail / Vendor)

Header

Data type

Designation

Description

Header

Data type

Designation

Description

SuggestedRetailPriceInclVat_[currency]

Dec(8,4)

Recommended retail price incl. VAT.

Recommended retail price incl. VAT.

VatRatePercentage

Dec(2,2)

VAT rate

VAT rate as a figure without % sign.


FILE STRUCTURE PRICE DATA MERCHANT

 

 

Minimal criteria: PriceData Merchant

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.

SalesPriceExclVat_[currency]

Dec(8,4)

Sales price excl. VAT

Sales price of a retail pack (ConsumerUnit, CU) excl. VAT

VatRatePercentage

Dec(2,2)

VAT rate

VAT rate as a figure without % sign.

 

Optional criteria for future optimization of PriceData Merchant

Header

Data type

Designation

Description

Header

Data type

Designation

Description

SalesPriceInclVat_[currency]

Dec(8,4)

Selling price incl. VAT

Sales price of a retail pack (ConsumerUnit, CU) incl. VAT.


FILE STRUCTURE STOCKDATA

 

Minimal criteria: StockData

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

QuantityOnStock

Int(5)

Exact stock quantity

We recommend submitting the exact stock quantity. This value influences the prioritisation of the dealer/supplier when selecting sales offers.

 

Supplementary criteria for optimizing availability and order processing

Header

Data type

Designation

Description

Header

Data type

Designation

Description

RestockTime

Int(3)*

Repurchase period in working days

Restocking or provisioning time in working days until the item is back in the partner's warehouse. (RestockDate - today), national holidays do not have to be considered

RestockDate

Date

Repurchase date

Date from which the item is back in stock at the partner.

ExpectedRestockQuantity

Int(5)

Expected repurchase quantity

The expected available stock at the time the item is back in stock with the partner.

MinimumOrderQuantity

Short

Minimum order quantity (MOQ

The minimum orderable quantity of retail packaging (consumer units). In contrast to the outer packaging quantity (TU), the quantity specified here is binding for warehouse deliveries as well as end customer deliveries. Eg: MOQ = 5 → possible order quantities: 5,6,7,8,...

OrderQuantitySteps

Short

Order quantity step (OQS)

The minimum orderable quantity and step size of retail packaging (ConsumerUnits). In contrast to the outer packaging quantity (TU), the quantity specified here is binding for warehouse deliveries as well as end customer deliveries. Eg: OQS = 5 → possible order quantities: 5,10,15,...

TradeUnit

Ushort

Overpack unit (TU)

Number of retail items (ConsumerUnits) per repackaging quantity. The TU is only relevant for stock deliveries. Eg: TU = 6 → probable order quantities: 6,12,18,...

LogisticUnit

Ushort

Full Pallet quantity(LU)

Number of items in retail packaging (ConsumerUnits) per pallet. The LU specification is only relevant for warehouse deliveries.

WarehouseCountry

Str(2)

Warehouse country of origin

The country of the warehouse from which the item is shipped. This information is relevant for assortments with several warehouses and different delivery times.

WarehouseId

Str(50)

Warehouse identification number

The identification number of the warehouse. This information is relevant for assortments with multiple warehouses located in the same country.

DirectDeliverySupported

Bool

Direct delivery supported

For suppliers with activated end customer delivery, individual articles can be approved for or excluded from end customer delivery.

 

Optional criteria for future optimization of the StockData


FILE STRUCTURE PRODUCTDATA

 

 

Minimum criteria: ProductData for offer creation and allocation (identification features)

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.

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)