Elbuz uses AI to bring attribute values to one style by your rules, showing each edit as “Before → After”. Products change only after “Apply”; the same spellings in new price lists are then fixed automatically.
When you need this:
- The filter lists “available”, “+”, “present”, “Yes” separately — they become “Yes”.
- A supplier writes “no data” and “n/a” — Elbuz suggests deleting them.
- Values start lowercase or end with a full stop — fixed by your rules; numbers and codes stay.
- Each price list brings the same spellings — a replacement rule fixes them.
Where to start: select a category in “Attributes” and open “AI tools” → “Check values”.
What the value check can do
- Value rules — you describe in your own words how values should look; a ready-made default set of eight rules is included.
- “Apply value standard” — AI checks every value against the rules, and Elbuz suggests deleting placeholders such as “n/a”.
- “Find duplicates” — AI looks for values that mean the same but are written differently.
- “Before → After” review — you see how many products will change; you can correct an edit, remove part of it or reject it.
- Replacement rules — after “Apply”, the same spellings from new price lists and parsers are fixed automatically.
How to set value rules
The rules are plain text in step 1, “Value rules”. AI reads it before every check and brings values to exactly that form. Until you change anything, the “Default standard” applies:
- Yes/no — one spelling: “+”, “1”, “present”, “available” become “Yes”; “absent”, “-”, “0” become “No”.
- Capital first letter; brands, models, codes and units as usual (iPhone, mAh, USB-C).
- Decimal point: 2.5 kg. Versions and standards stay unchanged: USB 3.0, PCIe 4.0, M.2 2280.
- A space between the number and the unit: 220 V, 256 GB.
- If the unit is already in the attribute name (“Weight, g”), the value is the number only.
- Dimensions with “ × ”: 27 × 34.8 × 44.6 cm.
- Lists separated by a comma and a space, no full stop at the end.
- No extra words around the value: “Color: black” becomes “Black”.
The default standard is written in the main catalog language, not the interface language: an English catalog gets “Yes” and “No” (the list above), a Ukrainian or Russian catalog gets the same rules in its own language. This way AI doesn't translate values when it rewrites them by the rules.
- Rewrite the text in your own words, for example “Yes/no — as + and −”, and click “Save”. The step heading will show “Your rules”.
- The “Default standard” button restores the eight rules and saves them right away.
- The rules are shared by the whole catalog: they apply the same way to any category and attribute.
1
Step 1 header2
Rules text3
Default standard- Click the step header to expand the rules; the label shows the default standard is in use.
- The rules are plain-language instructions that AI follows when checking values.
- The button restores the default standard for the whole catalog.
What AI won't change, whatever the rules say
The safeguard is built into Elbuz itself, not into the rules text. An AI edit that breaks it is discarded before it reaches the table, so you never see it.
In “Find duplicates”, AI only groups spellings that already exist in the catalog: only one of them can become the primary value, and spellings with different numbers (“1000 mm” and “1 m”) never end up in one group. Still, double-check which spelling becomes the primary one yourself.
| What is checked | Passes | Rejected |
|---|---|---|
| digits stay the same | 2,9 GHz → 2.9 GHz | 256 MB → 0.25 GB; 1000 mm → 1 m |
| versions and standards don't change | usb 3.0 → USB 3.0 | USB 3.0 → USB 3,0; PCIe 4.0 → PCI 4.0 |
| Latin-script names, brands and codes don't disappear and aren't translated | intel graphics → Intel Graphics | Black → Noir; Silver → Argent |
| AI adds nothing of its own | 256 mb → 256 MB | Bluetooth 5.3 → Bluetooth 5.3, BLE |
- A Latin-script unit is the only Latin word that may change or disappear: “234 g” in the “Weight, g” attribute becomes “234”.
- The values 0, 1, + and − can be replaced with a word without digits: “+” becomes “Yes”.
- A value that has become twice as long (and longer than 60 characters) is rejected as AI's own addition.
- AI can't delete a value — only the placeholder cleanup suggests “remove the value”.
How to check values
Step 2, “Check”, has two buttons, each looking for something different. Both take values from the whole catalog, from every product that has the attribute filled in: the category only decides which attributes to check.
| “Apply value standard” | “Find duplicates” | |
|---|---|---|
| What it looks for | values that don't follow the value rules | different spellings of one value: “Wi-Fi”, “WiFi”, “Wi Fi” |
| How many values it takes | all unchecked ones, in batches of 150, most frequent first | up to 1,000 different values per attribute; attributes with one value are skipped |
| Remembers checked values | yes: a value AI has already seen isn't checked again | no: every run checks everything again |
| “Why” in the edits table | “By the value rules” | AI's explanation for the group |
Only the main catalog language is checked; values in other languages are neither seen nor changed.
“Apply value standard”: what happens to a value
Before AI, Elbuz cleans the value itself: extra and non-breaking spaces, leftover HTML markup, and a comma, semicolon or colon at the start or end are removed.
A value that is only a placeholder — “no data”, “n/a”, “not specified”, “unknown”, “brak danych”, “keine Angabe”, “?”, “...” and the same words in Ukrainian and Russian — becomes a “remove the value” suggestion. Letter case doesn't matter, but “no data.” with a full stop isn't a placeholder.
A dash “-” isn't a placeholder: in yes/no fields it means “No”.
- Start or end
- Action or result
- Decision: the path depends on the answer
- Key step
The check runs in batches. The server works about 40 seconds per request, and the window starts the next one itself until the values run out. Progress shows in the “Values checked: …, new suggestions: …” line under the buttons. With tens of thousands of values, it takes minutes, not seconds.
- You can close the window mid-check. Suggestions found so far are saved and checked values are marked; the next “Apply value standard” continues with the rest.
- AI didn't respond — the check stops with “AI did not return a response”. That batch isn't marked as checked, so the next click picks it up again.
- A new value from a price list or parser isn't checked yet: the next run takes only such new values.
When to tick “Re-check already checked values”
After you change the rules. Without it, AI sees only new values, and old ones stay checked against the old rules. With it, for the attributes in scope Elbuz:
- clears the “checked” marks, and all values go to AI again;
- deletes unreviewed “By the value rules” suggestions found earlier with the same category and attribute selection — new ones replace them;
- leaves suggestions from “Find duplicates” alone.
The checkbox clears itself after the run. On a large category, checking from scratch takes as long as the first time; try new rules on one attribute first.
“Find duplicates”
AI gets all the different values of each attribute and returns groups: a primary value plus spellings that mean the same. Only a spelling already in the catalog can become primary, and values with different numbers stay out of groups. AI may still add a word with another meaning, so read the groups and remove extras with the cross.
- Each run deletes unreviewed duplicate groups found with the same category and attribute selection and searches again.
- A rejected group can come back on the next “Find duplicates” — this check has no memory.
- There are no batches: all attributes of the category go in one server request. For a large category, run it one attribute at a time.
How to review and apply edits
Findings go into the table in step 3, “Review and apply”. Nothing in your products has changed yet: the table is a list of suggestions. If several attributes were checked, rows are grouped under their names.
| Column | What it shows |
|---|---|
| Before | old spellings crossed out, each with the number of products that have it |
| After | the new value; you can correct it right in the row |
| Products | how many products will change if you apply the row |
| Why | “By the value rules” or AI's explanation for duplicates |
- Review the rows. Correct the new value in the “After” field — it's saved as soon as you leave the field or press Enter. An empty field means “remove the value” from products.
- Remove an old spelling that shouldn't change with the cross next to it (“Keep this value unchanged”). If no spellings are left in a row, the row disappears.
- Tick the rows you agree with. A bar appears at the bottom: “Edits selected: 1 · products will change: 1” — how many rows are ticked and how many products they will change.
- Click “Apply” and confirm: “Apply 1 edits? Values will change in 1 products…”.
Reject a row you disagree with: use the cross at the end of the row or the “Reject” button for all ticked rows. A rejected rule-based edit isn't suggested again because the value is already marked as checked. You can bring it back only with a check that has “Re-check already checked values” ticked.
1
Selected edits panel2
Apply button- The panel shows how many edits are ticked and how many products will change (1 edit, 30 products).
- Apply makes only the ticked edits; unticked rows stay untouched.
What happens after “Apply”
- The old spelling is replaced with the new one in all products in the catalog where it appears in this attribute, not just in the category you opened the window from.
- Only the main catalog language changes.
- A replacement rule for this attribute is created for each old spelling (see below).
- The list of values and the filters update right away, without waiting for the next import.
- Applied rows leave the table, and Elbuz shows “Done: 1 products changed. New incoming values will be fixed automatically.”
There's no undo. The old spelling isn't stored in products, so you can't restore it with a button. Before “Apply”, reread rows with a large number in the “Products” column: “Size” or “Type” can mean different things in different parts of the catalog.
What about other catalog languages
The edit itself doesn't change translations: the Ukrainian or English version of the product keeps the old value until the next translation. The next attribute translation notices that the main-language value has changed and translates it again (bulk translation, attribute translation). Changing only the letter case doesn't trigger a new translation.
Fix one spelling by hand, without AI
When there are only a few spellings and you can see them yourself — “8gb”, “8 GB”, “8Gb” — you don't need AI:
- In the “Attributes” window, open the “Values” tab and select the attribute on the left — all its values appear on the right with a “Products” column.
- Double-click the wrong value, type the correct spelling and press Enter — the value is rewritten in all products at once.
- If a category is selected in the tree on the left, the edit affects only products whose main category it is. To fix it across the whole catalog, clear the category selection.
- Only the value in the language shown in the row's “Language” column changes.
- A manual edit doesn't create replacement rules: if “8Gb” arrives again from a price list, it goes into the product card as is. To normalize future incoming values too, use the value check or create a replacement rule yourself.
How new incoming values get fixed
Every “Apply” leaves replacement rules behind: “no” → “No”, “non-ECC.” → “Non-ECC”. A rule covers the attribute in all categories, in the main catalog language. It runs without AI in price list processing, parsing, value edits in the product card's attributes and catalog field formulas. A manual edit on the “Values” tab doesn't run the rules.
Where: “Attributes” → “Maintenance” → “Configure attribute value replacement rules”.
- Rules from the check sit in the same list as the ones created by hand. For a “remove the value” edit, the row has “Delete text” ticked.
- If a rule turns out to be unnecessary, disable or delete it in this window. Values already replaced in products won't revert.
1
Search column- Each rule lists the attribute, the value to search for and the value it is replaced with, such as «no» → «No».
What happens if you disable a replacement rule
- If you clear the “Active” checkbox, the rule stops working in price lists, parsing, the product card and formulas: “USB Type C” from a new price list goes into product cards as is again.
- Values that were already replaced keep the primary spelling. Disabling the rule doesn't bring the old ones back: the old spelling wasn't stored in the cards.
- If you enable the rule again, it applies to future incoming values. Values that got into product cards while the rule was disabled are fixed in one go by the “Run attribute value replacement” button in the same window: it runs all active rules over the attributes of catalog products.
Scenarios
Category filters show “available”, “+”, “present” and “Yes”
Select the category in the tree of the “Attributes” window, open “AI tools” → “Check values” and click “Apply value standard”. Tick the rows with “Yes” and “No” and click “Apply”.
- All spellings in all catalog products become “Yes” and “No” — one item each in the filter.
- The next price list with “available” or “+” lands in the product card as “Yes”.
- Values AI has already checked won't be checked on the next run — only new ones.
A supplier fills in attributes with “no data” and “n/a”
Select the attribute where you see this and click “Apply value standard”. These values come back as rows with an empty “After” field. Tick them and click “Apply”.
- The placeholders are erased from products, and the “no data” item disappears from the filter.
- A replacement rule with “Delete text” ticked will remove the same text from future price lists.
You need “+” and “−” instead of “Yes” and “No”
In step 1, add “Yes/no — as + and −” to the rules and click “Save”. Select one attribute, tick “Re-check already checked values” and click “Apply value standard”.
- AI suggests “Yes” → “+” and “No” → “−”; values checked earlier under the old rules are checked again.
- After “Apply”, replacement rules bring new incoming values to “+” and “−”. Check the rule list for older rules that lead to “Yes”: it's worth disabling them.
- When you're happy with the result, run it the same way for the whole category.
One color is written five different ways
Select the “Color” attribute and click “Find duplicates”. Check the groups: you can correct the primary value in the “After” field and remove an extra spelling with the cross. Tick the groups and click “Apply”.
- The different spellings are reduced to the primary one in all products, and a replacement rule is created for each of them.
- Values with different numbers don't get into one group, but AI may merge words with different meanings — reread the groups before “Apply”.
What to do when the check gives no result
| What you see | Why | What to do |
|---|---|---|
| “No category or attribute selected” | the window was opened without a selected category or attribute | close the window, select a category in the tree or an attribute, and open it again |
| “No suggestions” after “Apply value standard” | the values were checked earlier or already follow the rules | after changing the rules, run it with “Re-check already checked values” |
| You ran a check, but no suggestions show in the window | suggestions are tied to what was selected when the window opened: those found for a category show when the window is opened from the same category | open the window with the same selection or with just the attribute — then you see all its suggestions |
| “AI did not return a response” | AI didn't answer the request; the batch isn't marked as checked | click “Apply value standard” again — the check continues from the same place |
| The rules say to convert megabytes to gigabytes, but there are no suggestions | Elbuz discards edits that change numbers | fix such values by hand on the “Values” tab (how) |
| A rejected duplicate group came back | “Find duplicates” checks all values again every time | reject it again, or remove the extra spelling with the cross and apply the rest |
| The value stayed old in another language | the edit changes only the main catalog language | run attribute translation: it translates the changed values again |
FAQ
Can AI change values in my products without me?
No. Both check buttons only build suggestions; products change only after “Apply” in step 3 (reviewing edits).
I write “Yes/no — as 1 and 0” in the rules, but there are no edits. Why?
The safeguard blocks any edit that introduces digits that weren't there. “Yes” → “+” passes, “Yes” → “1” doesn't (what AI won't change).
Will values change in other categories?
Yes. Values are taken and replaced across the whole catalog; the category only determines which attributes to check (what happens after “Apply”).
I applied a wrong edit. How do I undo it?
Not with a button: the old spelling isn't stored. Fix the value by hand on the “Values” tab and disable the replacement rule that was created (replacement rules).
A new price list brought the same messy values. Do I run the check again?
No. Spellings you already replaced are fixed by the replacement rule. New spellings AI hasn't seen yet will be checked by the next “Apply value standard” — it skips values that were already checked.
How long does checking a large category take?
Minutes: values go in batches of 150, and the server works for about 40 seconds per request. You can close the window — the next run continues from where it stopped (how the check runs).
Where to find it and who has access
- Menu
- Directories → Base product catalog → Attributes → “AI tools” → “Check values”
- Other entry points
- the “Values” tab of the same window — the “Check values” button
- Access right
- the “Attributes” window in group permissions
- Prepare
- a category in the tree on the left or an attribute in the list
Whatever is selected when you open the window is what gets checked. With a category selected, all attributes linked to it are checked; with an attribute selected as well, only that attribute.
The scope is shown at the top of the window: “Attributes to check: 90” or “Attribute: Embedded video”. With nothing selected, the window says “No category or attribute selected”. Check this line before you start: if an attribute from a previous step is still highlighted in the list, only that attribute will be checked.
1
Attribute being checked2
Step 1: value rules (collapsed)3
Check buttons- The window header names the attribute whose values are checked.
- Step 1 holds the value rules and is collapsed.
- Apply value standard and Find duplicates start the AI check.
Related topics
- If you need to merge the attribute names rather than their values — How to merge duplicate attributes into one.
- If the category has no attributes yet — How to create and clean up product attributes with AI.
- If messy values come from supplier websites — attributes from the parser.
- If the value translation is outdated after an edit — How to translate product attributes into other languages.
