Origo Help

Products and variants

Create a reliable catalogue record first, then use variants only for sellable differences.

Last reviewed:

Key concepts and when to use them

A product is the central catalogue record. A variant is also a product, linked to one parent product. Use a parent for shared identity and shared content; use variants for choices such as size, colour, or pack size that need their own sellable record.

Permissions and preparation

Have a clear product identifier, product family, and ownership decision before creating records. Admins and editors can maintain products. Viewers can inspect products but cannot change them.

Steps

  1. Open Products and select + Create Product.
  2. Enter the product name, identifier, product family, and the facts shared by every sellable option.
  3. Create each variant as its own product. On the parent, open Variants and choose Set up variants to define the variant axes.
  4. On the child product, open Relations and use Link Parent Product to link it to the parent.
  5. Fill the axis values and review inherited content. Add a value on a variant only when that variant must differ.

Verification

Open the parent and each variant. Check that shared facts are shown consistently, every option is distinct, and a product can be found by its identifier and name.

Common mistakes and rules

  • Do not create a variant for a marketing grouping with no sellable difference.
  • Do not use categories as a substitute for a product family.
  • A variant has one parent. Keep the hierarchy to parent and variant, rather than building deeper chains.

Work through a representative example

Create one lounge chair with + Create Product and complete its shared commercial and technical information. On the parent record, open Variants and choose Set up variants to define colour as an axis. Create a blue chair as another product, then open its Relations section and use Link Parent Product to link it to the lounge-chair parent.

Use one parent only. If a child already represents a variant, do not build another level beneath it. Check the parent and child records after linking so the variant axes and shared product family remain consistent.