Elbuz finds pairs of cards for one product in your base catalog — by barcode, part number and name words, in any order — and lets you merge each pair into a single card.
When you need this:
- One product came from two price lists, named differently — Elbuz pairs and scores the cards.
- Many variants differ by one suffix — the AI check keeps variants apart from duplicates.
- One card already has orders — merging moves orders and documents to the card that stays.
- A product was added three times — searching again after merging finds the third card.
Where to start: the first run across the whole catalog.
What duplicate search can do
- Finding pairs — Elbuz compares the selected products and shows pairs with a similarity score from 0 to 100.
- AI check — the model looks at each pair and tells a duplicate from a different variant.
- Reviewing pairs — “Confirm” or “Not a duplicate” in the row or with checkboxes; exact matches are confirmed automatically.
- Merging — one pair by comparing the cards, or all confirmed pairs with the “Apply” button.
- Search settings — the fields used to find pairs and the similarity thresholds.
How Elbuz decides two cards are duplicates
A duplicate is a pair of cards, not one “extra” card. Elbuz never says “this product is the extra one”: it shows two cards side by side and a score for how similar they are.
For two cards to end up in a pair at all, at least one key must match. There are six keys:
- barcode and UPC barcode — only the digits are used; anything shorter than 8 digits is ignored: that’s not a barcode but a truncated entry;
- Manufacturer part number () and Model — lowercase, letters and digits only; anything shorter than 3 characters is ignored;
- Name — the words of the name are normalized and sorted alphabetically, so “Laptop Lenovo IdeaPad 3” and “Lenovo IdeaPad 3 laptop” give the same key;
- Rare words of the name — the 2–3 rarest words in the product name. For a tablet that’s “Y336”, for a chair “Barsky”, for coffee “Lavazza”. Rarity is counted across the whole catalog, not the filtered set: otherwise, within a single category, the word “laptop” would turn out rare and link half the category.
During normalization, every Cyrillic letter that looks like a Latin one is replaced with the Latin letter — such a look-alike is called a . Thanks to this, “Samsung” with a Cyrillic “a” stops being a separate product. A “+” inside a word, on the other hand, is kept: “Redmi A2+” and “Redmi A2” are different models.
- Action or result
- Decision: the path depends on the answer
Next, every pair found gets a score from 0 to 100. Elbuz calculates it itself, offline, from the words of the names. Three rules behind this score explain almost everything you’ll see in the list.
Different variants are not duplicates. If the numbers in the names differ on both sides (“128” vs “256”, 24 inches vs 27), the pair scores zero and never makes it into the list. This is deliberate: different memory, a different size, a different color — that’s a different product.
The order of numbers matters. “Blackview Active 6 8/128GB tablet” and “Blackview Active 8 6/128GB tablet” contain the same numbers in swapped places — and they are different tablets. Such pairs also score zero.
Only an exact match of words in the same order scores 100. Reordered words score 95 at most. The reason is simple: “HDMI to VGA adapter” and “VGA to HDMI adapter” use the same words, yet the products are opposites. Such a pair scores 95, stays in the list — and a person makes the call on it, not automation.
A barcode match raises the score sharply but doesn’t make the pair a duplicate automatically. A real catalog had “Vintage Camera Kodak Retina” and “Aparat analogowy Zenit 122” with the same EAN — the field was filled with junk. Such a pair scores 73 and goes to review, not to confirmed.
How to configure duplicate search
The slider icon in the window header opens “Duplicate search settings”. They apply to the whole account, not to a single run.
The top block is “Fields that count as a match”. On by default: “EAN barcode”, “UPC barcode”, “Name”, “Rare words of the name”. Off: “Manufacturer part number (MPN)” and “Model” — they may hold a supplier’s internal code or a shared series code, so a match proves nothing. Check what’s stored in yours before turning them on.
Three numbers next to them:
| Field | Default | What it does |
|---|---|---|
| “Duplicate threshold, %” | 85 | the boundary of the “Very similar” tile in the mode without AI |
| “Doubtful zone threshold, %” | 60 | the lower bound for getting into the list: pairs with a lower score are discarded and not shown |
| “Maximum cards per single key” | 20 | above this, the group is treated as junk in the field and left out of the search; the same number limits how common a word can be and still count as “rare” |
This threshold is the key number if Elbuz seems to miss something. A live catalog example: “Крісло офісне Barsky Soft Grey” and “Крісло офісне Barsky Soft, сіре” are the same office chair, but the color is a word in another language, so the score is 46. With the threshold at 60, this pair never reaches you.
Lower the threshold to 40 and it shows up, along with a certain amount of noise.
The AI check looks at every unreviewed pair in the list, whatever its score — the doubtful zone threshold only decides which pairs get into the list at all. The hint under the fields says the same.
Below the numbers are two more checkboxes: “Require the same manufacturer” (on; an empty manufacturer on either side of the pair is still allowed) and “Check doubtful pairs with AI” — the same setting as the mode switch in the header. At the bottom, the “Confirm automatically” block has two auto-confirmation thresholds (which pairs are confirmed automatically).
1
Manufacturer part number (MPN)2
Rare words of the name3
Doubtful zone threshold, %4
Maximum cards per single key5
Require the same manufacturer- Manufacturer part number (MPN) is off by default because it may hold a supplier internal code.
- Rare words of the name finds pairs by the 2-3 rarest words of the product name.
- Doubtful zone threshold (60) decides which pairs reach the report at all.
- Maximum cards per single key — a group larger than this is treated as junk and skipped.
- Require the same manufacturer compares only cards of one brand.
The eraser icon next to the settings clears the list of found pairs. It asks for confirmation and removes everything except the records of merges already done: “Products stay where they are: only the list is deleted.”
Scenarios
The first run across the whole catalog
Do the first run without filters: then later checks of individual categories will also see duplicates that sit elsewhere (why).
Steps
The “Manufacturer SKU” field holds the real manufacturer part number
What to do. In “Search settings”, turn on “Manufacturer part number (MPN)”. Leave “Maximum cards per single key” at 20 and save. Then click “Find duplicates”.
What you get. Cards with the same part number end up in a pair even if their names differ. Case, spaces and hyphens in the part number don’t matter. A part number match raises the pair’s score, but the names set the ceiling: a pair with very different names may still fall short of “Doubtful zone threshold, %”.
What won’t happen. A value found on more than 20 cards is left out of the search. The window shows it in the “Some products could not be checked” block with the number of cards. A part number match alone won’t confirm a pair: only an exact match of the name words in the same order scores 100.
What to do when the search finds no pairs
| What you see | Why | What to do |
|---|---|---|
| “No field selected for comparison — turn on at least one in the search settings.” | All six field checkboxes are cleared in the settings | Open “Search settings” and turn on at least “Name” or “Rare words of the name” (settings) |
| “No duplicates found” | The filtered set has no pair scoring at or above the doubtful zone threshold | Widen the filtered set, turn on “Rare words of the name”, lower “Doubtful zone threshold, %” (settings) |
| “Some products could not be checked” and lines like “Manufacturer part number “12345” — the same on 300 products” | The same value sits in an identifier field on more than 20 cards (the “Maximum cards per single key” threshold): such a value can’t tell whether it’s one product or several, so the group is left out of the check. This is neither an import error nor duplicates | If the value was set by mistake, fix or clear it in the catalog with a bulk edit; if it’s meant to be that way, turn this field off in “Search settings” or raise the threshold (search settings) |
FAQ
Why didn’t Elbuz find a duplicate I can see with my own eyes?
Most often the cards share no key — barcode, part number or rare words of the name — or the score came out below “Doubtful zone threshold, %”. Another reason: the numbers in the names differ on both sides, and Elbuz treats them as different variants (how the score works).
It says “Some products could not be checked”, the same value on 300 products. What should I do?
This isn’t an import error: one value sits on more cards than “Maximum cards per single key” allows, and those cards weren’t checked. Fix the field with a bulk edit in the catalog or turn it off in the search settings (settings).
How is a “different variant” different from a duplicate?
A variant is the same model line but with different memory, color, size or package contents. Such cards must exist separately, so Elbuz never confirms them automatically, however confident the AI answer is.
Will Elbuz warn me that a product already exists when I create it?
No. There’s no “this product already exists” check when you enter a name, either in the card or in the add windows. Duplicates are reviewed only in the “Catalog duplicates” window, once both cards already exist.
Can Elbuz find identical products by photo?
No. Pairs are found by barcode, part number, model and the words of the name. Elbuz won’t link two identical items with completely different names and no shared identifiers.
A product comes from several suppliers — are those duplicates too?
No, if the price list rows are matched to one catalog card: then there’s only one card. A duplicate appears when a new card is created from a price list instead of matching. How to match: matching supplier products to the catalog.
Where to find it and who has access
- Menu
- no menu item
- From the base catalog
- Directories → Base product catalog → Products → toolbar menu → “Catalog duplicates”
- Access right
- the “Catalog duplicates” window: anyone who can open it can both search and merge cards
- Prepare
- the filtered set of products in the grid; what is stored in the “Manufacturer SKU” and “Model” fields
The only way into the window is the : there is no menu item for it. This is deliberate — the window checks the filtered set currently shown in the grid, and opening it from the menu would mean no filter, that is, the whole catalog.
The window opens maximized to the full desktop: the table has two name columns, and on half the screen there’s no room to compare them.
1
Catalog duplicates2
Burger button- Catalog duplicates — the only entry to the window; it is not in the main menu.
- The burger button at the right end of the grid toolbar opens this menu.
Related topics
- If you need to find pairs and review them — How to find duplicates in your catalog and review pairs.
- If the pairs are confirmed and it’s time to merge — How to merge two product cards into one.
- If duplicates appear because a supplier product isn’t matched to a card — How to match price list products to the catalog.
- If you need to narrow the filtered set of products before searching — Searching and filtering products in the catalog.
