Entering attribute values — five ways
Enter values manually on a product card, use the editor on the list, update in bulk, import a file, or use AI. Each method has different validation rules.
Step by step: values on a product card
This is the basic method. Start here when you are correcting an individual product.
- Go to Catalog → Products and click a product row.
- Open the Attributes tab.
- Click any field. The entire tab switches to edit mode at once — there is no separate “edit” button or single-field editing.
- Fill in the values. Required attributes have a \* at the end of their label.
- If a select list is missing the value you need, type it in the search field. Add “your text” appears below the list; one click saves the new option and selects it immediately. The option code is generated from its label (Polish letters are converted to Latin characters: “Złoty” →
zloty). If you need a different code, click Add new value (always shown below the list), enter the required Label and Code, then click Add. You will not see a confirmation. - Click Save at the top of the tab. This button is in English and appears only after you make a change; a cross beside it discards the changes.
- The confirmation message is Attributes saved successfully. If some changes fail, you will see Saved N, failed M.
If the product shows no attributes and you expected some, check the five visibility conditions in Attribute pitfalls.
Step by step: set the same value for many products
- Select products on the product list (Bulk actions on products).
- Click Attributes in the selection bar.
- In the Product operations window, choose an attribute in the Field box.
- Under Change type, choose Set value, Append to value (text attributes only — text, long text, rich text editor), or Clear value.
- Enter a Value. Attributes with language-specific values also show a Language field.
- To change several attributes at once, click Next change and repeat steps 3–5.
- Click Preview changes.
- Review the result in the Attribute changes preview window. Back returns to the form; Cancel stops the operation.
- Confirm with Apply changes.
In grouped view, the window warns that changes will apply to all variants in the selected groups. Use the preview: bulk attribute operations cannot be undone.
The operation is all or nothing. If even one value for one product fails validation (for example, an invalid value for a numeric attribute), nothing is saved, including values that passed validation. The error message identifies the affected products and attributes.
Which method should you use?
| Method | When to use it |
|---|---|
| Product card, Attributes tab | Individual corrections |
| Editor on the product list | Quickly filling in multiple products one after another (Product list — inline editing and quick actions) |
| Bulk edit | Setting the same value for many products |
| File import | External data or large volumes |
| AI | Extracting values from descriptions |
Bulk editing has three modes
The modes are Set value, Append to value, and Clear value. You can also Preview changes before applying them.
Import: an unknown attribute is a hard error
Remember this distinction:
| Situation in the file | Result |
|---|---|
| Unknown attribute | The entire row is rejected |
| Unknown category | Warning only; the row is imported |
Attribute import is therefore stricter than category import. Before a large import, check your attribute column headers against a few rows.
Attribute columns have a prefix in the header that identifies the attribute and may also specify a language.
Validation can be unexpected
- An integer attribute accepts
5.0but rejects5.5. - A regular expression is checked whenever one is set on the attribute, regardless of the selected validation type. An invalid pattern causes every value save to fail.
- A calculated attribute is read-only and requires a valid expression.
Values by language and catalog
An attribute can have a separate value for each language or for each catalog; its configuration determines which.
Two pitfalls:
- If the attribute is not set to “value per catalog” but you provide a catalog when saving, the save is rejected. This can happen during imports and integrations.
- Turning on “per language” after the fact will orphan existing values. Values saved earlier without a language stop matching and disappear from the product card, even though they remain in the database (Attribute pitfalls).
Change these settings before filling in the catalog, not afterward.
An empty value counts as filled in
The completeness indicator checks whether a value exists, not whether it makes sense. An empty string saved as a value increases the score (Completeness indicator).
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo