...
The required and recommended data attributes and the name conventions for the data fields, which can come from several data sources are:
Attribute Name | Required | Recommended | Remarks | Visible in Recommendation | ||
---|---|---|---|---|---|---|
id | X | - | Unique ID for a single product
| - | ||
name | (X) | X | Name of the product
| |||
image | (X) | X | Product image URL, e.g. a URL to the product image on your website
| |||
price | - | X | Product price (decimal number) | |||
manufacturer | - | X | Manufacturer or brand name | |||
detailUrl | - | X | URL to the product details page | |||
purchaseUrl | - | (X) | URL to shopping basket. We recommend including it since the product recommendation can then directly perform a "add to basket" action without the user needing to visit the product details page first. However, this depends on the desired customer journey throughout your shop / website.
| |||
variantId | - | - | Master variant ID of a product. Useful if your product assortment contains e.g. color or size variants. excentos can collect them to make sure only the master product is displayed in the product result list. | - | ||
description | - | X | Product description text | |||
currency unit | (X) | Not strictly necessary, but cleaner. The currency can be directly included in the price attribute, too. | ||||
status / available / online etc | (X) | If you can not restrict your product feed to products actually available, please provide a suitable filter attribute to excentos | ||||
category | (X) | Having a category indicator for the product is often helpful. Please try to include the tree of parent categories (in a separate attribute if possible) | ||||
Push factors / merchandising information | (X) | If you have information available that helps excentos to optimize the product listing for your business (such as margin, stock levels), include them. |
...
If prices, product names and descriptions differ, we recommend providing separate data feeds for each market (although it would be technically possible to contain all markets in one feed).
Mime Type Detection
...
During the upload process the Workbench is analyzing the data file type. Only if the file is a valid CSV the file can be uploaded. The corresponding mime type (internal format) for CSV files is 'text/csv'. Unfortunately, there are 600+ words, word phrases or hexadecimal values (mostly at the start of the file) that can affect the mime type. That means that a word like 'Article' at the beginning of a CSV file results in the mime type 'message/news'. With that resulting type, it is not possible to upload the CSV anymore although the file is completely valid. Because of the huge amount of words and word phrases, excentos is not able to prevent these errors during the upload process. Nevertheless, the mayor part of these words/phrases are not relevant for a CSV file use case, like detecting python or image files.
If you have any problems regarding this issue do not hesitate to contact us. Some "bad words" examples are listed below:
Bad words | Mime Type |
---|---|
Article | message/news |
Path: | message/news |
[version] | application/inf |
StartFontMetrics | application/x-font-adobe-metric |
Rar! | application/x-rar-compressed |
Spreadsheet | application/x-sc |
FWS | application/x-shockwave-flash |
CWS | application/x-shockwave-flash |
PSID | audio/prs.sid |
BEGMF | image/cgm |
icns | image/icns |
AGD2 | image/x-freehand |
FreeHand10 | image/x-freehand |
MATLAB | application/x-matlab-data |
#!/bin/perl | text/x-perl |
#!/bin/python | text/x-python |
FLV | video/x-flv |
MOVI | video/x-sgi-movie |
\037\213 | application/gzip |
Read about the Template Data File and Example Data File to get started building your own Data File
...