...
| Type / Field | Specification | ||
|---|---|---|---|
| File type | CSV file (preferred encoded is UTF-8) | ||
| Field separator | Needs to be one of the following: ',' (comma), ';' (semi-colon), ':' (colon), '|' (pipe), tab or whitespace character. | ||
| Text delimiter | Text cells have to be surrounded by " " (double quote) or ' ' (single quote). One of them at the beginning of a cell; one at the end of a cell. This is especially important if the text contains a specified field separator. | ||
| Escape character | The escape character that is used within the text cells. Normally this is a '\' (backslash), to escape a single double quote, another single double quote can also be used. | ||
| Decimal separator | Default is a '.' (dot), e.g. '799.99'. For comma separated decimals (e.g. '799,99') you need to set the number format in the Workbench. | ||
| Multiple values separator | If some attributes contain cells with more than one value in a cell (e.g. the attribute color with the values black and blue), these values need to be separated by a separator (e.g. with a comma such as "black,blue"). Otherwise these two values will be interpreted as one value and cannot be split by using the "Multi Value" switch button in the data attribute table (see Upload your Product Data File, Multi Values).
| ||
| Units | Such as kilogram, currencies etc. should be in a separate field if the data field is required to be interpreted as a number. (we've marked this as this is a suggestion only because the unit is only required if it shall be displayed in the Product Guide . The unit is not technically required, except if prices are displayed in the result list because we then need to know the currency) |
| Info | ||
|---|---|---|
| ||
The field separator and text delimiter as well as the file type encoding and the escape character can be set during the update process of your product data file. |
...
- The "Required" attributes in the table below are the minimal set of data that every Product Guide needs to work properly.
- The "Recommended" attributesare technically optional, but we recommend you using it is recommended you use them in order to display certain information like the product name or price in the product recommendation card.
...
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 needingto | visitthe product details page | first. However, this depends on the desired customer journey throughout your shop / website.note|||||||
This feature has to be supported by your website and furthermore implemented for your individual requirements. | | |||||||||||||||
| 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. |
| Info | ||
|---|---|---|
| ||
This means that the name 'price' and 'Price' will be recognized as two different attributes (with lowercase and uppercase 'p'). Please make sure all attributes are written correctly to match the required/recommended attributes above. Otherwise make sure your own attribute names are mapped correctly. Else the corresponding information cannot be displayed or executed properly. |
...
| Info |
|---|
This part of the documentation describes different Product Data sources. The The Product Data can consist consists of several data sources and can also be connected by different connector types (HTTP, FTP, SFTP). excentos can help to preprocess these Product Data sources to use them for your Product Guide. You can contact Contact excentos support if you have any questions regarding your Product Data sources. |
...
Category-Specific Attributes describe the product itself, such as technical data, possible use-cases and everything that distinguishes one product from the other. For every Product Guide , we need all the category specific attributes are needed, like e.g. the screen resolution of a notebook computer, the shoe size of a mountaineering boot, the range of height adjustment of an office desk etc. The more data we havethere is, the more powerful and detailed the Product Guide can be.
The category-specific attributes can have the same data structure (mostly the case with CSV files) or a separate data structure / different attributes per category (mostly the case with XML data structures).
Category-Specific Attributes are not required for the data sourcing option „third-party licensed data“.
...
This is how the CSV file needs to look like if you open it in e.g. Excel if you have correctly set the text delimiters (in the example above we used a comma is used):
Data Feed for international rollouts
...
If prices, product names and descriptions differ, we recommend providing it is recommended to provide separate data feeds for each market (although it would be technically possible to contain all markets in one feed).
...