The data feed is one of the main parts of the eSales Lifestyle integration. The quality will impact the available features, as well as the quality and performance of eSales Lifestyle. This page targets both retailers and integrators and contains best practices and guidelines regarding the data feed, as well as how they are leveraged in eSales Lifestyle.
Implementing every guideline is not needed to build a great solution, but the more implemented practices, the better the end user experience will be. Follow the listed best practices as closely as possible, and for those outside of reach, don't worry. Apptus eSales Lifestyle does a lot of automatic data processing to make the best of it!
Integration time savings
Some guidelines relates to data normalisation and asset handling which needs to be addressed by retailers if to be implemented. Have guidelines and data accessibility assessed by retailers when needed.
Many content related best practices can be implemented iteratively, enabling going live as fast as possible with room for additional improvements.
Use the Data feed checklist when building the data feed.
Natural key mapping¶
The keys of the product groups, products, and variants should have a natural mapping to something comprehensible on the retailer side. Ideally something like an article number, SKU number, or codes that are both used internally and externally as identifiers for the different entities. The keys provided in the feed must match the keys provided in the order notifications.
If a visitor search exactly matches a key the visitor will be directed to the corresponding product page.
The release date of a product indicates how new a product is considered to be. The release date should correspond to when the product is made available for purchase. Release dates are highly recommended to be provided in the feed when possible.
- Newness of a product is considered when ranking products.
NEWproduct badge can be used when a release date is provided.
- Products can be sorted by newness.
- Dynamic product selections can be created based on newness.
Supplying the cost of products allows eSales to optimize on profit as well as present profit metrics in statistics interfaces. The cost can be supplied either as an attribute on variants in the data feed, or it can be notified at time of purchase in the order notification. A retailer should select the approach that is easiest for them to supply cost information to eSales.
- Profit optimization as business objective, optimizing all product listings towards profit.
- Profit as an included aspect in various statistics
The recommendations listed below regards image management and image creation. These can favourably be considered when taking new pictures of products as well.
If an image is missing, do not provide an actual image of something indicating a missing image, e.g. let the provided image url point to a 404. Images that are missing will be handled by the image analysis, and custom images for indication of missing images should be handled through theming.
Products with broken imagery are automatically demoted.
Multiple product images¶
Supply all available images for each product and differentiate images by supplying image tags. Image tags will facilitate merchandisers to differentiate between image types such as primary, full, front, back, side, and detail images.
Providing multiple images enables product card features in the Experience app such as alternate images on hover and showing image galleries.
Providing multiple enables automatic image fallback for broken or missing images.
Multiple image resolutions¶
Supply all relevant resolutions of each image. It is highly recommended to supply images in resolutions suitable for thumbnails, mobile listings, as well as for desktop listings. Ensure to supply imagery in size order and if widths are known. This information can favourably be added in the data feed.
It is recommended to always supply at least one product image in a high resolution as images of products with patterns in lower resolutions with lossy compression may result in incorrect colour analysis.
Providing multiple image resolutions will improve page load speed and allow visitors to have a good experience with regard to image quality, with minimal bandwidth usage. The most suitable resolution of an image will automatically be chosen by the Web Components.
Image type separation¶
For retailers with highly structured image assets, advanced image imports including image type information (especially for cutouts) is recommended. A cutout image is an isolated image of solely the product, typically with a single colour background.
Performance gains with a faster colour analysis of new collections as cutout images can be analysed significantly faster than other image types.
Cutout images refers to images where only the product is represented, e.g. without a model or other additional products. If there are multiple cutout images for each product to choose from, select the ones that best adheres to the recommendations below.
- Portraits the entire product as accurately as possible.
- Avoid sharp edges in the background.
- Avoid shadows on the products.
- Homogeneous background colours for all products. Images are however not required to all have the same background colour.
Product colours are automatically extracted and allows eSales to retrieve a very complex view of the colours, with detailed nuances as well as the colour distribution. This in turn enables a very powerful colour search, colour filtering, and precise colour swatches.
Cutout imagery provides the fastest and often the most accurate colour distributions.
Consistent image ratio¶
All images provided should ideally have the exact same ratio. The height of the rendered product cards will be the same to avoid alignment issues, meaning that inconsistent image ratios will lead to clipping.
Keep the images clean and separate from functionality and information that belongs elsewhere. Avoid overlays, badges, padding, etc. built into the images.
Providing metallic colours¶
Provide metallic properties in
color_default for products that are
Silver. Metallic properties cannot be found through colour analysis and must be tagged manually.
Correct presentation of products with metallic properties.
Providing regular colours¶
For retailers with extremely high product turnover, providing colours manually can be beneficial to ensure products are provided with a colour prior to the colour analysis is completed. Colours can also be manually set if the automatic colour analysis should happen to be unsatisfactory for specific products.
Colours must be provided as exactly
Silver, or a valid RGB hex code. When used, always strive to provide as detailed nuances as possible. Multiple colours can be provided and will be considered to be an evenly distributed colour representation.
Performance gains with initial colour values supporting colour search, colour filtering, and colour swatches available before the automatic colour analysis is completed. Will be replaced with more accurate representations by the automatic colour analysis unless using
color_override, which is not replaced by the colour analysis.
Do not include the brand (or other redundant information) in the product title. Brands can be presented and styled separately in product cards. Product titles should ideally be kept short as long titles may be clipped for mobile visitors.
Displaying the colour of a product in the product title is often not necessary as it is displayed in the image. One exception where it is useful is if the retailer has a set of specialized custom colours that are well known among the visitors. In this case, place the colour name at the end of the title. Placing the colour in another position will result in that the title flickers when the visitor hovers over the different colours.
Clara T-shirt - spirit green
Clara T-shirt - dreamy pink
Clara T-shirt - real teal
Custom attributes are used to enhance search, to provide facet and filter options for both search and navigation, and as a basis for creating product selections.
- Provide any non-standard data that is useful for search, facets, filters, or product selections as custom attributes. Standard attributes include department, price, size, colour, and brand. Examples of useful custom attributes include
- Send as structured data when possible. "A short summer party dress" can be used in more ways when provided as separate attributes rather than single description, e.g.
- Include attributes that represents the current categorisation of the site.
- Provide as high granularity as possible of available values. Supply both
Leggingsas opposed to only
- Normalise values. Avoid having "Long dress", "long dress", and "Long dresses" in different products, when describing the same property.
- Use custom attribute values that are not often changed for product selections.
- Supply display names in the data feed for custom attribute values where identifiers are not human friendly. The following illustrates the syntax of the category
Jacketswith an external id
Product selections and stable values¶
A product selection is a defined set of products. Product selections are used in promotions, demotions, and navigation items and are often rule-based. The rules consists of including or excluding products where an attribute has a specific value. The attribute values are treated as identifiers, meaning that only products with those attribute values are included in the selection. If the attribute values on the products change, the products will no longer be part of the selection.
Keep track of changes
It is important to keep in mind what fields are used in a product selection and when/if they are changed. It is important that these values are stable and not changed often.
Make sure department values in products are stable and not changed often. Common department values for fashion are
Kids. For a single department retailer, all products should have the same department value.
Product recommendations are restricted to products within the same product department.
Provide content items and/or links for vital pages of high client interest. Typical pages recommended to include are: Returns, Shipping, Delivery, Contact, and Stores. Use the Search phrase report in the Experience app to keep track of popular search phrases.
Data feed checklist¶
The following checklist should be used when creating the data feed.
Items marked as are dependent on retailer data that in some cases are difficult to access. These can be seen as guidelines for future retailer data curation projects, when not possible to implement right away.
- Natural key mapping of product groups, products, and variants.
- Release dates for products are provided.
- No actual image is used for indicating a missing image.
- All relevant product images for each product are provided.
- Each image is provided in a suitable thumbnail, mobile and desktop resolution.
- The metallic colours
Silverare provided as colours in the feed.
- All attributes usable for search, filters and facets are provided as custom attributes.
- Custom attributes used for product selections are structured and stable.
- A custom attribute representing the current categorisation of the site is provided.
- Department values are stable and does not change often.
- Content links for popular pages are provided.
- Cost is provided in the data feed or to be supplied in order notifications.
- Images are clean and separate from additional information.
- Image widths are provided for known resolutions.
- Consistent image ratios are used for all images.
- Cutout images are separated though their provided type.
- Product titles are kept short and does not include the brand name.
- Default colours are provided for retailers with high product turnover.