Modeling concepts¶
Markets¶
A market typically refers to a specific geographical region where the collective user behavior is relevant, and the retailer offers a similar assortment of products or services. In Elevate, this concept is represented by a unique market identifier, which is required for nearly all types of requests. Product data, content, and behavioral statistics are all linked to one or more markets. A market supports one or more locales.
Market identifier conventions
- Market identifiers must be consistent across all integration points
- Markets identifiers are case-sensitive
- All product data and content keys belonging to a market must be unique
- All product data and content keys must be consistent across all markets, e.g. a product with the same key on different markets are assumed to be the same for all intents and purposes.
Locales¶
A locale is a language and country combination, that enables correct handling and analysis of text content. The following locales are currently supported:
bg-BG
, cs-CZ
, da-DK
, de-AT
, de-CH
, de-DE
, el-GR
, en-001
, en-150
, en-AU
, en-CA
, en-GB
, en-IE
, en-IN
, en-PH
, en-HK
, en-TW
, en-MO
, en-US
, es-ES
, es-MX
, et-EE
, fi-FI
, fr-BE
, fr-CA
, fr-CH
, fr-FR
, he-IL
, hr-HR
, hu-HU
, is-IS
, it-CH
, it-IT
, ja-JP
, ko-KR
, lt-LT
, lv-LV
, nb-NO
, nn-NO
, no-NO
, nl-BE
, nl-NL
, pl-PL
, pt-BR
, pt-PT
, ro-RO
, ru-RU
, sk-SK
, sr-RS
, sv-FI
, sv-SE
, tr-TR
, vi-VN
, zh-CN
, zh-HK
, zh-TW
and zh-MO
.
Product data¶
The data feed is mainly composed of product data. How Elevate handles the data feed depends on the feed operations included in the file that is imported.
An online retailer often sells articles in different colors or styles, and in different sizes or configurations. To describe an article and its properties, Voyado Elevate utilizes a model with three levels.
The first level is the product group (the overall article), the second level is the product (the style or color), and the third level is the variant (the SKU/size/configuration). The product is what is shown in a search result. Consider the image below where the different type of ladies tops are product groups, the colors of the different types are the products, and the sizes of the products are the variants.
The properties of the articles, i.e. the product attributes, are also segmented. Overarching properties such as brand and department are at the product group level, while attributes such as images and material are at the product level. Attributes as size, price, cost, and availability are at the variant level.
Images¶
Images exist on the product level. Each image object defines a single image which may have URLs with different resolutions of the same image. Multiple resolutions are used for saving bandwidth and are especially useful for thumbnails.
More on images
An image element must have at least one URL and URLs must be unique within a product. If relative image resolutions are known, the image URLs should be ordered by ascending width, i.e. smallest first, otherwise it can lead to inconsistencies before it is analyzed automatically. There can be a maximum of 25 images on a product.
Additional attributes regarding image tags
, widths
, and types
can be set in the import. These attributes are mainly for use before the automatic image analysis is complete. There is also support for custom image attributes and the alt
and caption
attributes.
Sizes¶
Each variant has a single physical size, but the size can be expressed in several formats. For example, a shirt can be considered both a size S and sizes 34 and 36 simultaneously. If multiple formats are known, all should be provided.
Multiple variants with the same format and value are allowed, as long as there is one format with a unique single value for each variant. For example, having one variant of size S in SML format and 36 in EU format, and another variant of size M in SML format and 36 in EU format, is okay because the SML format has different values.
Translations¶
This replaces Attribute names seen in the xml format.
Translations is a separate entity imported within a catalog feed and can be applied to category
, series
, and custom attributes. A translation maps a property id to a localised value and is used to localise the presentational information while ensuring stable filters and product selections.
Content¶
Content items enable visitors to search for content on the site, such as FAQs, shipping and contact information.