Additional Features¶
Apptus eSales Lifestyle includes several additional features that work across different parts of the system.
Custom prices¶
Supplying custom prices for variants enables displaying visitor specific prices, or showing prices within the same market in different currencies.
It can for example easily be integrated with external currency providers and is suitable for retailers supporting shipping to multiple locations, but not fully supporting different markets. Custom prices are fully compatible with price filtering and sorting, and prices will automatically be updated and rendered in both product listings and in price filters.
If a product lacks price information for a given price id, that product will be omitted from all results where that price id is specified in a request. For example, if searching for jackets with EUR as the price presentation, jackets without a custom price provided in EUR will be omitted from the search result.
For more information about custom prices in the data feed, see the Format Specification.
How to use
The applicable price identifier should be provided when initiating the script. This must match a provided price id in the data feed. If the price should be displayed using a different currency symbol, this must also be provided in the script. This is for example applicable when using custom prices to display prices in local currencies, while not necessary if used to display other prices e.g. VIP prices or the default list price.
priceId: EUR
currencySymbol: '€ '
currencyBefore: true
Keeping the state of which price identifiers that are applicable to different clients, such as selected currencies, is assumed to be stored externally.
Ratings¶
Supplying ratings as the standard rating attribute for products in the data feed enables the feature of displaying rating stars in product cards in all product listing components.
A product rating is supplied as a value from 0.0 to 5.0. Rating of actual products and score aggregation is assumed to be handled elsewhere, e.g the value to import is the current rating to display.
How to use
The parameter rating must be set to true when initiating the script to display the ratings in product cards. For alternative positioning and colouring of rating stars, adjust theming parameters for the product card accordingly.
For more information about ratings in the data feed, see the Format Specification.
Favourites¶
A personal input signal supported by eSales Lifestyle is a visitor's favourite products. Visitors can select and have their favourite products notified to eSales via either the Web Components or the Web API.
How to use
Using the Web components
Enable the Favourites and customize the look and feel as desired using the Theming API.
Note: Only a limited amount of favourite information will be stored in eSales for various use, hence external storage is needed for cross device favourite state handling. With the Web Components, state handling of selected favourites are made client side, but can be retrieved and set externally using esales.favorites, see the Library API. This can to be used upon visitor sign in, if the actual favourites should be accessible on multiple devices.
Using the Web API
When a visitor select a product as a favourite, send the Add favourite notification. When a visitor removes a favourite, send the Remove favourite notification.
Content¶
Content is a flexible and generic type of data, that can be searched for and ranked according to interest or newness. Typical entities that would be suitable to supply as content are for examples FAQs, magazine entries and inspirational articles.
Apptus eSales Lifestyle uses both user interactions and the provided content data, to determine how to rank content. Furthermore, multiple types of content can be added and used for separate purposes. For example, FAQs could be added as content to search in, while also adding the latest and greatest inspirational articles for presentation on the start page.
How to use
Supply the content items in the data feed.
Using the Web API
To create a new separate endpoint for search, e.g. a standalone FAQ search, use the Content Search Page. Content entities may also be included on the Search Page.
To retrieve content information, or list content according to newness or relevance, use either Content Information or the Landing Page. Some requests require that the content lists to include are specified in the request body through the Page configuration.
Using the Web components
Content functionality in the Web Components is currently limited to the content type link. This provides the equivalent support as Content links, but may now be provided as the new entity type. Both import formats are supported, but they must not be mixed.