Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

⬅ Product Data overview

Stage 2: product creation ➡

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.

Table of Contents

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.

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.

 Expand here to show detailled data format

Type

CSV-Standard

XLSX-Standard

Exception/ Remark / Example

File format

CSV / TXT

XLSX

Other formats possible in consultation but not recommended

File name

  • File names for initial configuration - without spaces / special characters / umlaut.

  • File names for file updates - the files must be replaced by the old files for each transmission and have exactly the same file names as the previous ones.

Examples:

  • ProductData_DigitecGalaxus.csv

  • PriceData_DigitecGalaxus.xlsx

Character coding

UTF-8

-

Other character codes possible in consultation but not recommended

Separator

; (Semicolon)

-

Other limit signs possible in consultation

Header

Header with column designation is mandatory

  • Duplicates are not allowed for column names

  • Column name must be present

  • Column names must not contain line breaks

 Example XLSX - break in Header

Decimals

Decimal places must be separated with a . (dot) or , (comma).

  • Example - VatRatePercentage: 8.1

  • Thousands separators are not allowed: 1000 or 1',00

  • Comma must not be used if the separator in the CSV is also a comma

Text / Parsing

Strings (data type: text) must be enclosed in inverted commas (").

-

In the case of descriptions and product data, it is particularly important that these are enclosed in inverted commas because they can contain the characters that also act as separators (semicolon, comma, pipe) and/or line breaks which, if unmasked, prevent the import.

In the example, you can see the correct masking of inches, as well as the masking of the inverted commas that appear in the texts.

LongDescription_en: "TV with size 46"" and stand with white label ""Kings of E-Commerce""

Strcuture

The structuring of the data within the text file must be observed.

  • The data to be read in is in the first sheet tab and there are no hidden sheet tabs

  • Completely empty lines or notes in the file should be avoided if possible.

 ExampleXLSX - Multiple worksheets
 Example - Empty Line / notes

Scientific notations

Scientific notations are not allowed

Often csv files are opened and saved in Excel. This process changes the structure of the numbers contained in the file. Information such as Gtin, item number and others become unusable as a result. See example:

 Example - Scientific notations

Number format

-

  • ·Cells with numeric values may only be in standard or number format. Other formats, such as accounting or user-defined, are not allowed

  • Excel deletes leading zeros from numbers, which can lead to problems, especially with article numbers or GTINs. In such a case, the partner should format the affected column as text.

 Example - number formats
 Example - Leading zeros

Date

Option 1: YYYY-MM-DD

Option 2: DD.MM.YYYY

  • One-digit days/months must be supplemented with a leading zero, e.g. 2020-07-01 or 01.07.2020.

  • Separators are to be used according to the formats.

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.

 Expand here for detailled notes on documentation

Topic

Designation

Example

Data declaration

  • Str: String, Text

  • Int: Integer, Number

  • Short: (Signed short) 0 - 32'767

  • Ushort: (Unsigned short) 0 - 65’535

  • Dec: Decimal, Number with decimals

  • Bool: Boolean, true/false, 1/0

  • Date: Date

-

Information in brackets

After the data type, the permissible number range, the number of characters or the format is indicated in brackets.

  • (10): A maximum of 10 digits or characters are permitted.

  • (10,4): A maximum of 10 digits before and 4 digits after the decimal point are permitted.

  • (8-14): Between 8 and 14 digits or characters are allowed.

Str(100), Int(5), Dec(8,4)

Indexierung

*_index: Describes a consecutive numbering of columns with the same content.

ImageUrl_1, ImageUrl_2

Sprachen

*_language: Describes the language identification of language-dependent columns with the same content. (following standard ISO 639-1)

ProductTitle_de, ProductTitle_en

Währung

*_currency: Describes how to mark the currency of price columns. Prices can be indicated in CHF or in EUR.

SalesPriceExclVat_CHF, PurchasePriceExclVat_EUR

Einheiten

*_unit: Describes the labelling of the units of dimension-specific columns. The permissible units are indicated in the corresponding columns.

Weight_g, Length_cm

Länder

*_country: Describes the country identification of country-specific columns. (following standard ISO 3166 ALPHA-2)

ReleaseDate_CH, ReleaseDate_DE

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)

The data preparation of the price data depends on the integration model. The requirements are listed separately for supplier (retail) and marketplace models!

Use the following CSV-samples

Use the following XLSX-samples

Minimal criteria: PriceData Supplier Model (Retail / Vendor)

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item.

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126

PurchasePriceExclVat_[currency]

Dec(8,4)

Purchase price excl. VAT

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

  • Product charges must be included in the price quotations, depending on the supplier's registered office:

    • Suppliers with company headquarters in the same country as the purchasing party: Purchase price incl. product fees

    • Suppliers with registered office in another country than the purchasing party: Purchase price excl. product charges

  • "currency": Specification of the currency in the header in CHF or EUR.

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

 Expand here to view the supplementary criteria Price data Retail → Recommended retail price, VAT rate

Header

Data type

Designation

Description

SuggestedRetailPriceInclVat_[currency]

Dec(8,4)

Recommended retail price incl. VAT.

Recommended retail price incl. VAT.

"currency": Specification of the currency in the header in CHF or EUR.

VatRatePercentage

Dec(2,2)

VAT rate

VAT rate as a figure without % sign.

E.g.: Switzerland: 8.1, 2.6, 0.0

FILE STRUCTURE PRICE DATA MERCHANT

General notes to PriceData

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

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

The data preparation of the price data depends on the integration model. The requirements are listed separately for supplier (retail) and marketplace models!

Use the following CSV-samples

Use the following XLSX-sample

Minimal criteria: PriceData Merchant

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item.

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126

SalesPriceExclVat_[currency]

Dec(8,4)

Sales price excl. VAT

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

  • "Currency": Specification of the currency in the header in CHF or EUR.

  • EU hub Merchant without fiscal representation: transmits the EUR price

  • EU hub Merchant with fiscal representation: transmits the CHF price.

VatRatePercentage

Dec(2,2)

VAT rate

VAT rate as a figure without % sign.

  • E.g.: Switzerland: 8.1, 2.6, 0.0

  • EU hub trader without fiscal representation: no transmission of a VAT rate

  • EU hub trader with fiscal representation: transmits the CH VAT rate.

Optional criteria for future optimization of PriceData Merchant

 Expand here to show optional crietria für Merchant - SalesPriceinclVAT

The following information cannot be processed at the moment. However, we are constantly optimising our technical systems and will expand the information processing for corresponding fields in due course. Supplying the information in the data files helps us to better assess the relevance and prioritisation of future extensions.

Header

Data type

Designation

Description

SalesPriceInclVat_[currency]

Dec(8,4)

Selling price incl. VAT

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

  • "Currency": Specification of the currency in the header in CHF or EUR.

  • EU hub trader without fiscal representation: transmits the EUR price

  • EU hub trader with fiscal representation: transmits the CHF price.

FILE STRUCTURE STOCKDATA

General notes on the inventory data

  • File name: StockData_[ProviderName]. [FILE FORMAT] Ex: StockData_digitecgalaxus.csv)

  • Transmission frequency: every 12 hours (optimal: every 2 hours)

Quantities logic

  • All quantities listed here refer to retail packaging (ConsumerUnit, CU).

  • Without explicit specification of minimum order quantities and order quantity steps, all retail packaging is processed without minimum quantities. Mandatory order quantities (>1) must therefore be specified according to the fields "Supplementary criteria for optimising availability and order processing" described below.

Use the following CSV-samples

Use the following XLSX-samples

Minimal criteria: StockData

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126

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.

Negative stocks are treated as backlogs.

Supplementary criteria for optimizing availability and order processing

 Expand here to display the supplementary criteria for optimising availability and order processing → replenishment period and date, minimum order quantity, order quantity step, repackaging, warehouse of origin, control direct delivery

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

  • *Maximum value = 365 (1 year)

  • If the RestockTime is unknow, we expect an empty field, value “0” will cause an error

  • Either RestockTime OR RestockDate is possible - not both

  • RestockTime or Restockdate are considered only if the quantity on stock is equal to 0. In case of a positive stock quantity restocktime or restockdate are ignored.

RestockDate

Date

Repurchase date

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

We recommend specifying the replenishment period or the replenishment date in all cases (regardless of the stock level). This information has an impact on availability and is used for automated ordering processes.

(warning) Either RestockTime OR RestockDate is possible - not both

(warning) RestockTime or Restockdate are considered only if the quantity on stock is equal to 0. In case of a positive stock quantity restocktime or restockdate are ignored.

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,...

In principle, the MOQ > 1 should only be set for logistical reasons and always in combination with the order quantity step. E.g. if plates or glasses cannot be transported individually due to their fragility. If individual shipment is possible, the MOQ = 1 and a larger outer packaging (TU) should be specified instead.

  • Maximum value = 32'767

  • If no MOQ value is transmitted, we assume 1 piece as the default value.

  • The specification of MOQ < OQS is not valid.

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,...

In principle, the OQS > 1 should only be set for logistical reasons and always in combination with the minimum order quantity. E.g. if plates or glasses cannot be transported individually due to their fragility. If individual shipment is possible, the OQS = 1 and a larger outer packaging (TU) should be specified instead.

  • Maximum value = 32'767

  • If no OQS value is transmitted, we assume 1 piece as the default value.

  • The specification of OQS > MOQ is not valid.

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,...

When purchasing, we are guided by this value and, if possible, order the exact repackaging quantity or a multiple of it. Correctly transmitted outer packaging units (TU) therefore optimise warehouse deliveries considerably

  • Maximum value = 65’535

LogisticUnit

Ushort

Full Pallet quantity(LU)

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

  • Maximum value = 65’535

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.

  • Standard ISO 3166-2 Country code

  • For marketplace traders, we do not currently offer this specification.

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.

Permissible values: true, false / 1, 0

Optional criteria for future optimization of the StockData

 Expand here to view the optional criteria → Expected replenishment quantity, Item per sales unit, Package, Shipping method.

The following information cannot be processed at the moment. However, we are constantly optimising our technical systems and will expand the information processing for corresponding fields in due course. Supplying the information in the data files helps us to better assess the relevance and prioritisation of future extensions

Header

Data type

Designation

Description

ExpectedRestockQuantity

Int(5)

Expected repurchase quantity

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

This information is only relevant if the replacement date is available and will be used for automated ordering processes in the future.

RetailUnitQuantity

Int(4)

Item per sales unit

Number of items per retail pack.

We can currently only process this information in the specifications. We therefore ask you to consider the number of items per sales unit in the specification field in "Stage 3: Enrichment specifications".

PackagingQuantity

Int(4)

Packages per item

Number of packages per retail pack.

  • Eg: 1 table top (1 pack) + 4 table legs (1 pack): PackagingQuantity = 2

ShipmentType

Int(1)

Item shipping method

1: letter, 2: parcel, 3: bulky goods, 4: general cargo

 Additional information shipping method based on Swiss post

1: Letter → format B4 (3533 x 250 mm), 501-1000 g
2: Parcel → 100 x 60 x 60 cm, up to 30 kg
3: Bulky goods → length: 250 cm / girth: 400 cm (2x height + 2x width + longest side), up to 30 kg
4: General cargo → From 30 kg

FILE STRUCTURE PRODUCTDATA

General notes on the ProductData

  • File name: ProductData_[ProviderName]. [FILE FORMAT] (Ex: ProductData_digitecgalaxus.csv)

  • Transmission frequency: every 24 hours (optimal: every 12 hours)

The minimum criteria listed here are only relevant for the offer data creation and allocation.

We recommend that all those who wish to benefit from the automated creation of new assortments directly implement the extended data preparation of the master data in "Stage 2: Product creation".

➡ Link Stage 2

Use our CSV-samples

Use our XLSX-samples

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

Header

Data type

Designation

Description

ProviderKey

Str(50)
ASCII 32-126

Partner specific item number

Unique identification number of the partner item.

  • The item numbers must be unique. Duplicates are not permitted.

  • We expect only characters in the range ASCII 32-126

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)

  • The EAN/GTIN forms the basis for our automated allocation and product creation processes. Therefore, request GTINs for your products for a smooth data transfer: GS1 Switzerland: Request barcode, GS1 Germany: Request barcode

  • The EAN/GTINs must be unique and globally valid. Duplicates are not permitted.

  • The EAN/GTIN must be visible on the retail packaging.

  • Further information on Gtins and GS1 at: http://gtin.info or GS1 Switzerland.

⬅ Product Data overview

⬆ To top

Stage 2: product creation ➡

  • No labels