Info |
---|
As mentioned on the page Prepare the Product Data page, this part of the documentation describes the requirementsthat your product data feed needs to fulfill in order to build Product Guides entirely yourself with the excentos Workbench. If you have more complex feeds (e.g. web services or XML feed), please return to the Prepare the Product Data section or contact excentos support if you have any questions regarding your data - we'll help you cover any data feed requirements. |
...
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 to include 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. |
...
For more information on possible data attributes and which data might help to even improve the Product Guide, please also check https://www.excentos.com/en/documentation/data-feed-requirements.
Anchor | ||||
---|---|---|---|---|
|
Info |
---|
This part of the documentation describes different Product Data sources. The Product Data can consist 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 excentos support if you have any questions regarding your Product Data sources. |
Possible Product Data sources
Source | Description | Recommended | Optional |
---|---|---|---|
PIM | product information like part numbers, variant id, descriptions etc. | x | |
technical attributes | characteristics of a product; can be contained in master PIM or in another database | x | |
availability feed | defines product availability per region | x | |
country-specific product definitions | e.g. different certificates per product; can be contained in master PIM or in other database | x |
Category-specific Product Data
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 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 have, the more powerful and detailed the Product Guide can be.
The categorrycategory-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“.
...
If prices, product names and descriptions differ, we recommend to provide providing separate data feeds for each market (although it would be technically possible to contain all markets in one feed).
...