Products
Setting up your catalogue
Item types, categories, ranges and suppliers — what each is for and the order to build them in.
Last updated September 2, 2026
Build the structure before you add products. Retrofitting it to a catalogue of five hundred items is painful.
| What it is for | |
|---|---|
| Item Types | The template — which extra fields a product of this kind has, and which content a tribe may override. |
| Categories | Your main taxonomy, and where pricing markups are carried. Can be nested. |
| Ranges | A second, flatter grouping that sits under categories. |
| Suppliers | Where products come from, with their own markup settings. |
| Customisation Methods | Named decoration methods — embroidery, print — reused across products. |
Item types do the most work
An item type defines the custom fields products of that kind carry — text, numbers, currency, lists, images, rich text and more. It also has a Tribe-editable Core Content list deciding which standard fields a tribe may reword for itself.
Categories carry pricing
As well as grouping products, a category holds markup settings and a minimum-order surcharge. That is why the category tree is worth thinking about — it is not only navigation.
Suppliers and imported categories
A supplier has a name, a code and an Automatic Sync switch. Opening one gives you its own categories and items, where you map each supplier category to your main category and range. Products imported into a mapped supplier category are then filed into your own tree automatically.