Attributes

Attributes (Colour, Size, Material, Fit…) are your catalogue's vocabulary. You define them once for the whole shop in Products › Attributes, and their values work everywhere: as catalogue filters, as specifications in the product page's table, and as variants with their own stock and price.

What it is

An attribute has:

• A name (translated per shop language) and a type - "Text" (chips, e.g. Size, Material) or "Colour" (swatches).
• Values - the attribute's dictionary (S, M, L… or Denim, Cotton…). A value is created once and reused by every product.
• "Generates variants" - whether picked values create sellable combinations (see below).
• "Show as filter" - whether the attribute may appear as a catalogue filter.

The shop palette

All colour attributes share one palette: a colour like "Black" exists once (with its swatch) and is reused everywhere. That's how "Dark grey" stops appearing in five spellings across categories.

Role: variants or specification

• "Generates variants" (e.g. Size): the values you pick on a product create combinations in the Variants card - each with its own stock, price, SKU and barcode.
• Specification (e.g. Material, Care): the values describe the product. They show in the product page's Specifications table and work as filters without creating variants.

The attribute's switch sets the default role - each product remembers its own. So switching "Generates variants" off doesn't take the variants away from products that already have them: they keep their role. When a product still uses the attribute as a specification while the registry now says "Generates variants", a "Move to variants" button appears in its Specifications card - one click moves the attribute to the variants side, keeping its picked values.

Creating and editing

• Click New attribute, name it and pick the type. Then open its row (the pencil) and add the values.
• Next to each value you can see how many products use it. Removing a value removes it from products too - their variants lose that dimension. A product left with no variant in its table becomes a single item at its own price, and its variants' stock moves onto it (just as when you remove the last value in the product's Variants card). If such a product has no price of its own, or its variants hold batches ("By batch"), nothing is saved and the editor names every product in the way - both those with no price and those with batches.
• Drag the rows to order the attributes - that's also their order as filters.
• Renaming is safe: filter URLs use stable identifiers (slugs), so saved links and ads pointing at filtered pages keep working after a rename. A new attribute or value gets a Latin-letter identifier - «Възраст» becomes vazrast, «6-8 г.» becomes 6-8-g - so a filtered page's address stays readable (?vazrast=6-8-g). Identifiers you already have do not change.
• Deleting a whole attribute removes its product usages, variants lose that dimension, and filters stop offering it (if it was picked for the quick buttons above the products, that row goes too). A product that sold only through this attribute becomes a single item - the same rule as removing a value. It can't be undone - the editor asks you to confirm.

Merging duplicate values

When two values are effectively the same ("Dark grey" and "Darkgrey"), the editor highlights them and offers Merge: every variant and filter is repointed to the more-used spelling and the duplicate is deleted.

When adding a value from the product editor, the system also asks "Did you mean…?" before minting a new one - so duplicates never appear in the first place. For colour attributes you also pick the new value's swatch there, not just its name.

Merging duplicate attributes

Sometimes whole attributes repeat - most often after a migration from another platform, where each product carries its own copy of the same question. You then see several rows with the same name (for example "Избери Модел:" three times).

A note with a Merge button appears above the list. It keeps one attribute holding all the values; identical ones are merged rather than duplicated.

• Every product keeps exactly the values it already uses. A Huawei case still offers only Huawei models even when the vocabulary also holds Xiaomi and iPhone ones - picks are stored per product.
• The category filter likewise shows only the models the products in that category actually have.
• Products, variants and personalisations are all repointed. It can't be undone - you're asked to confirm.
• Attributes of different types (a text "Цвят" and a colour "Цвят") are never merged - the colour one uses the shop's shared palette, and merging would lose the swatches.

Relation to categories

Categories no longer define attributes. Which attributes show as filters is set shop-wide - from the attribute's own "Show as filter" switch, not per category. A new attribute is included automatically, and each category shows only the values its products actually have; empty values are never shown to customers. That's why moving a product to another category can never break its variants.

Tips

• Keep incompatible scales as separate attributes: "Waist size" (29-40) and "Size S-XXL" - not one shared "Size".
• Turn off "Show as filter" for purely descriptive attributes (e.g. "Care") that aren't useful for narrowing.
• After a migration, an attribute no product uses arrives with the filter already off - otherwise it would sit on every category and match nothing. Its vocabulary is kept: turn it on and it appears as soon as real products carry it.

Next step

Pick each product's values in its editor's Selling tab - the specifications and the variants. See Variants & stock.