Product data modelling
The product data modelling in Litium is easy but also flexible. You can assign an infinite number of attributes, files, images and relationships to your products. You can group your attributes in a logical and understandable way that makes sense to administrators and site visitors.
Product, base product and variant
Any sellable product in Litium is always made up of two levels. One is the base product and the other is the variant. The base product stores the information common to all product variants, while the variant stores the information that differs between the variants of the product. The base product is connected to a tax class in order to be able to calculate the correct price with and without VAT.
Products that only have one variant - like a pair of one size, one color sunglasses - is still made up of the two levels base product and variant. The attributes for a product are defined as fields in a field template, and the field template for a product is always divided into two levels, one for base product and the other for variant.
The sellable item always includes the variant level. While a product can technically exist with data only on the base product level, any sellable product has to include the variant level. The variant level stores information about price and stock balance.
Price list
The price list entity holds information about the unit price and has connections to country and currency. It also has a property to determine if the prices in the price list are with or without VAT. The price calculator uses this property together with the tax class and country information to find and calculate the correct price for the customer.
Set up fields and field templates for products
The field templates for products are divided into the levels base product and variant. There are a number of predefined system fields. The system fields are always available, but if they are to be shown in the back office administration, they need to be added to field templates. These are the most important when modelling products:
Article number
|
| The article number always exists on both the base product and variant level, and it is not part of any field template. Article number is mandatory both on the base product and variant level. Once the value is set, the user cannot edit it. |
Name
|
| Can be set to both levels, or either one of them can be used. |
Description
|
| Both levels, or either one of them can be used. |
Images
|
| Always exists on both levels, and is not part of the field templates. |
URL
|
|
The URL is set on either on the base product or the variant level. The URL is set on the variant level if the variant itself should be browsable, that is it has its own URL. In the case when all variants are shown as a list on one page, it is better to place the URL on the base product level. It is the display template specified in the field template that defines whether the URL of the base product or the variant is to be used.
The URL settings from the display template is also used when the product is indexed. If the URL setting is Variant, all the variants will be added to the search index as individual items. If the URL setting is Product the search index will only add the base product with all the variants as one item.
|
Product types
There are usually several types of products in any merchant's assortment. Let's examine a couple of common product types and see how they can be modelled in Litium.
Sunglasses - one size, one color
The perhaps simplest product type is a product that is sold in only one make. It does not come in variations, like different sizes or colors.
T-shirt - variants for different sizes and colors
The classic example of a product that is sold as different variants.
Office chair - variants with alternative presentation
This kind of product is sold as different variants, but the way it is displayed on the web site differs from the t-shirt example, which also makes the modelling slightly different.
