Attribute requirements and completeness weight

An attribute is assigned to catalogs, and each assignment can override the attribute's global settings. That is why the same attribute may be required in a retail catalog and optional in a wholesale catalog.

Step by step: set the requirement and weight for a specific catalog

1. Go to Catalog → Attributes, on the Attributes and groups tab.
2. Click an attribute in the list to open its editor beside it.
3. Open the Catalogs tab. The number of assigned catalogs appears beside the tab name.
4. If the catalog is not yet in the table, click its plus button below the table (the search field above the table also filters catalogs you can add). Each catalog has one row with the Required, Position, Weight, and On card columns.
5. In Required, click until it shows Inherit, Yes, or No.
6. Position shows Auto (the attribute appears according to its global order) or a number set for this catalog. Click to open the ordering window, described below.
7. Set Weight (1–10), used in completeness.
8. On card switches between Visible and Hidden — whether the attribute appears on the product card in this catalog.
9. Click Save at the bottom of the editor. Assignments are saved together with the whole attribute, not separately. The ordering window is the exception; it saves immediately.

Removing a catalog from this list deletes the entire assignment, including its overrides, weight, and position.

The three requirement states

For an attribute assigned to a catalog, Required has three values:

A catalog override always takes precedence; Inherit delegates the decision to the attribute.

Attribute order in the product form

This ordering applies to attributes, not catalogs. It determines where the attribute appears in the product form for a given catalog. The same attribute can be third in one catalog and tenth in another.

The easiest way to set it is in the Attribute order window:

• From the catalog list, click ⇅ in the catalog row.
• Or from the attribute editor, on the Catalogs tab click the position number (or Auto) in the catalog row. This works only for an assignment that has already been saved; save a new one first.
• Or from the group editor, on the Catalogs tab click Auto or the number in the catalog row.

Attributes are grouped as they are in the product form. Drag a row by its handle or use the ↑↓ arrows, then click Save order. Saving assigns numbers in increments of 10 (10, 20, 30…), so you can later insert an attribute between existing ones without rearranging the whole catalog. An attribute without its own number (Auto) follows the global position.

You can reorder groups the same way: drag the handle beside the group name or use its ↑↓ arrows. Group order is saved for this catalog only. Groups that are not assigned to the catalog appear at the bottom with the label Outside the product form. The form does not show them, so they cannot be moved. Saving changes only what you reordered: groups or attributes.

Bulk changes do not remove overrides

The bulk action Toggle required (attribute list → select rows → Bulk actions) changes only the global setting. An attribute with an explicit Required or Optional override in a catalog keeps that override, so nothing changes in that catalog.

Despite its name, this action does not actually “toggle” anything: it opens the Bulk update attributes window. In Set value, choose Enable or Disable, then click Apply. All selected attributes receive that same value.

This explains the common surprise: “I set the requirement in bulk, but completeness has not changed.” Check whether the attribute has an override in the catalog covered by the report.

Completeness weight

Each assignment of an attribute to a catalog has a Weight (the form hint says 1–10; the default is 1). Weight has exactly one purpose: it affects the product completeness percentage. Required attributes account for 60% of the result, and each attribute's share of that 60% is proportional to its weight.

In other words, weight changes nothing about validation or listing. It changes only how much the absence of the attribute lowers the score — and therefore the order in which it is worth filling in missing data.

There is no strict range validation: a value outside 1–10 supplied through an import or API is accepted and simply carries a correspondingly greater weight. The 1–10 hint is a convention and a limit in the form field, not server-side validation. Follow it so weights remain comparable.

The first assignment sets the language

The first catalog to which you assign an attribute sets its default language and creates its first translation, derived from the code. Later assignments do not change this. If an attribute name looks like a technical code with underscores replaced by spaces, that is the automatically generated name; edit it in the translations window.