4. Product Data
Product data includes not just products, but categories, versions,
options and attributes too. The relationship between these will be covered
in this section, as well as the process for setting them up.
4.1. Relationships
Before you start entering product data, it is important to understand the way this data is structured in Kartris.
There are three basic required elements of product data structure:
- categories
- products
- versions
A product must have at least one version, and feature in at least one category – so in this respect, all three elements of data structure are required for every product item you have.
4.1.1. Unlimited category levels
Categories can be nested within other categories. Kartris is
designed to allow unlimited category levels, though in order to manage
even the biggest sites, five levels is probably more than
enough.
4.1.2. Multiple parent categories
Each category can have any number of parent categories, and you
do not have to have the same number of category levels throughout the
store. For example, below we see a product whose category can be
reached via three navigation routes. One of them has two levels, one
three and the other four. A product can also have multiple parent
categories.
4.1.3. Mix products and subcategories
A category can at the same time be a parent both to other
categories, and products. This provides more flexibility as you can
nest general interest products in a category, while still subdividing
other items into further subcategories.
4.1.4. Product types
There are several different types of products that can be
created within Kartris.
4.1.4.1. Single product
This is the simplest form of product; it has a single version
and for display purposes the two are merged into a single
unit.
4.1.4.2. Multiple version product
This is suitable for items that tend to have only one degree
of variation. For example, ketchup that might come in several
different bottle sizes (each with its own SKU / item code), or a
book that comes in hardback, paperback and audiobook. Each version
can have its own image, as well as the product having images
too.
4.1.4.3. Options product
This has a single base version and unlimited options can be
applied to it. This is suitable for products with multiple types of
variation such as size, style and colour. You can have as many
options as required, and these can display as dropdown menus, radio
buttons or a checkbox. It is therefore ideal for items such as
computers that might be highly configurable, with a choice of
hard-disks, processors, operating systems, RAM, and so
on.
You can control whether a selection is required for a particular option. So for example, when configuring a computer, the RAM and processor selections would be required (because a computer must have both) but the secondary hard-disk size selection might be optional (if the component was not necessary required).
You can control whether a selection is required for a particular option. So for example, when configuring a computer, the RAM and processor selections would be required (because a computer must have both) but the secondary hard-disk size selection might be optional (if the component was not necessary required).
4.1.4.4. Combinations product
This is similar to an options product, and is created in the
same way. But you can choose to create 'combinations'. The system
will then create a unique record for each permutation of the
options. This allows you to record stock level for each permutation
separately, and have a different SKU / item code for each
permutation.
The number of permutations will be limited to a few hundred for performance reasons. Remember that you only need to create a combinations product if you are stock tracking or need a unique SKU for each permutation - otherwise use an options product.
The number of permutations will be limited to a few hundred for performance reasons. Remember that you only need to create a combinations product if you are stock tracking or need a unique SKU for each permutation - otherwise use an options product.