On every price list import, Elbuz matches rows to your catalog by matching types and restores pairs you confirmed earlier. A new price list gets three working types.
When you need this:
- The SKU is in the name, not a separate column — add a type that finds the catalog SKU in the name.
- The supplier only gives its own code — “Search by supplier SKU” with a supplier check.
- Wrong products assigned — move precise types up, narrow the loose rule.
- Products renamed, manual pairs lost — the manual pairs type restores them by SKU.
Where to start: source → “More” → “Processing rules” → “Product matching settings”.
What automatic matching does
- Runs on every import — on price list values that are already corrected; progress is shown in the work log.
- A queue of types — the first type that succeeds takes the row; you set the order by dragging.
- Three types out of the box and six more in the add menu — SKU in the name, supplier code, link, name from other price lists.
- Restoring manual pairs — from the directory, including by SKU after a product is renamed.
- Your own rule — any pair of fields, a comparison condition and value cleanup.
- Restart — rebuilds the price list's links after you change the rules, without losing manual pairs.
Whatever the rules don't link is left for manual review or AI matching.
When matching runs and what you see during a run
Matching is a price list import operation at position 110, called “Matching products from the price list with the products of the base catalog”. There's no “don't match” switch: to turn it off, remove the operation from this price list's operations — see the article on the order of operations.
Before it, these have already run: categories, deleting products from the ignore list, text auto-replacement, manufacturer detection, regular expressions, option products and availability. This matters: matching works on corrected values, not on what was in the supplier's file. After it come repricing, field formulas and saving attributes.
You can follow the run in the “Work log” — it appears as the “Price list import” operation. Each applied type writes a line “Matching type: …”, followed by “Total items found: N”. The same lines appear live in the price list import progress panel, not just at the end.
The log doesn't show how many rows were left without a pair or which product each row got. Check that in the price list product grid: the “Product found” and “Catalog product ID” fields, and the “Match type” column shows which type found the pair. Not visible? Add these columns in the grid settings.
A pair is only made between products in the same condition. Before matching, the program determines each row's condition — new, discounted, used or refurbished — and all automatic types link a row only to a card in the same condition. A “… (Discounted)” row won't be paired with a new card, even if the SKU matches. More: Product condition.
Why the order of types matters
Types run from top to bottom, in the order they appear in the list. Each next type only touches rows that don't have a pair yet: the first type that succeeds takes the row, and the remaining types no longer look at it. So put precise types above approximate ones — SKU above name, and name last.
You change the order by dragging with the mouse in the left list of the settings window. It is saved immediately, with no separate button.
If several catalog products fit a rule's condition, the program doesn't choose the best one and doesn't warn you — it takes an arbitrary one. The row is marked as matched, but the product behind it is someone else's, and you'll only notice it in prices or on an order.
Narrow the rule until exactly one product fits it: add a second row to the rule, turn on “Consider manufacturer” or “Consider category”, raise the minimum length. “Too few pairs” is a state you can see and fix. “Lots of random pairs” goes unnoticed.
The only exception is the i~ and i~~ conditions, which work through the search index: there the program takes the most relevant match. But “best” doesn't mean “correct”: it is always taken, even when the similarity is weak.
Which types work out of the box
A new price list gets three matching types, in exactly this order.
| Type | What it compares | Condition | Min. length |
|---|---|---|---|
| Search for manually matched products | brings back previously confirmed pairs from the directory | — | — |
| Search by MPN | manufacturer SKU in the catalog — manufacturer SKU in the price list | exact match | 5 |
| Search by product name | name in the catalog — name in the price list | exact match | 6 |
Search by MPN works when the supplier provides the actual manufacturer SKU and the “Manufacturer SKU” field is filled in your catalog cards. If the supplier gives its own internal SKU, you need a different type — “Search by supplier SKU”. If the SKU is empty in the catalog, those products simply drop out of the comparison.
It makes false pairs too: SKUs like 1000, A-100, PRO occur across brands, and the only safeguard is the minimum length of 5. “Consider manufacturer” is cleared by default, so the brand isn't checked. Special characters aren't removed by default, so AB-123 and AB123 differ for the program. “Remove special characters” fixes this, but then AB-123 and A-B123 become identical.
Search by product name takes the catalog name in the storefront language, not the admin language. And it has two cleanup checkboxes turned on by default — read about them carefully.
Out of the box, “Search by product name” has the “Remove cyrillic” and “Remove special characters” checkboxes turned on — that's how they're labeled in the rule row (in the matching types directory the same settings appear as “Remove Cyrillic” and “Remove special characters”).
This is by design: «Смартфон Samsung Galaxy A12 чорний» becomes samsunggalaxya12, so the comparison is effectively by brand and model, not by how each side translated the word «смартфон» (“smartphone”). For a catalog with Latin-script brands, this works well.
Two consequences you need to know.
- «Чохол iPhone 13» (case) and «Скло iPhone 13» (screen glass) are identical after cleanup —
iphone13, and the program can easily match one with the other. The product type lived in the Cyrillic part, which the type threw away, and the minimum length of 6 doesn't help. - a fully Cyrillic name turns into an empty string. «Килимок для миші чорний» (black mouse pad) is nothing after cleanup, such a row drops out of the comparison, and the type silently finds nothing.
There are three fixes: the “Clean words” list (remove words like «чохол», «скло», «оригінал»), the “Consider category” or “Consider manufacturer” checkbox, or clearing “Remove cyrillic” — then full names are compared; there will be fewer pairs, but they'll be more accurate.
How manual pairs come back
This type works differently from the rest: it doesn't look for new pairs, it brings back the ones you once confirmed manually. Instead of a field table, it has five checkboxes under “Restore manual matches by fields:” — “Manufacturer”, “Manufacturer SKU”, “Supplier SKU”, “Name” and “Supplier”.
They're for the case when the supplier has changed a product's name: then the pair is looked up by the other fields. Separately there is the “Search for previously added products from price lists in the base catalog” checkbox — it finds the pair if the product originally got into the catalog from a price list.
1
Restore manual matches by fields2
Five field checkboxes3
Search for previously added products4
Apply to all price lists- The heading explains the form: manual matches are restored by the selected fields.
- Five checkboxes: the pair is found by these fields if the supplier changed the name.
- Checkbox for searching previously added price list products in the base catalog.
- Apply to all price lists — the only action of the window that goes beyond the current price list.
Two things about these checkboxes that aren't visible in the interface.
“Manufacturer” and “Supplier” don't turn anything on by themselves — they only narrow the search. For the search by fields to happen at all, at least one of three must be checked: “Manufacturer SKU”, “Supplier SKU” or “Name”. If only “Manufacturer” and “Supplier” are checked, this part of the type won't run.
The directory of confirmed pairs is shared across the whole database, not separate for each price list. With the “Supplier” checkbox cleared, a pair you confirmed for one supplier will also be applied to a row from another supplier's price list. The riskiest option is leaving only “Name”: identical names at different suppliers will produce someone else's pair.
Word cleanup, minimum length and the “Consider …” checkboxes don't apply to this type — it has a different settings form with no field rows.
Inside the type, the search methods run one after another, and each next one only takes rows that don't have a pair yet. The last method — by unique fields — works only when “Field uniqueness key” is turned on in “System settings”, section “Price lists”, group “Product matching”, and unique fields are marked in the price list column settings.
- Action or result
- Decision: the path depends on the answer
The form saves itself; there's no “Save” button. “Apply to all price lists” copies these settings to all other price lists — the only action in the window that goes beyond the current price list. The program asks “Apply current manual matching settings to all price lists?” and then tells you how many price lists were updated.
Which other types you can add
The “Add matching type” button shows the types this price list doesn't have yet. Besides the three out-of-the-box ones, you'll find the following.
- Search by supplier SKU. Supplier SKU in the catalog — supplier SKU in the price list, exact match, minimum length 5. The SKU gets into the catalog when a product is added from a price list. The trap: such an SKU is unique only within one supplier, so supplier X's
A-15will match a product with supplier Y'sA-15. Turn it on together with the “Consider supplier” checkbox. - Search for the base catalog MPN in the price list product name. For suppliers who only send a long name string: “Grundfos UPS 25-40 180 96281375 pump”. The SKU is searched as a separate word, not as any substring, and the price list row's manufacturer must match the catalog product's manufacturer — this is built into the program. If the row has no manufacturer, the type searches among catalog products without a manufacturer too, and a short SKU is easily found in someone else's name.
- Search for the price list SKU in the base catalog product name. The mirror case: catalog names contain the SKU, and the price list gives a bare SKU. There's no minimum length here at all, so SKU
10will match any name with a separate word “10” — but only among products of the same manufacturer: the manufacturer match is built into the program here too. - Search by external product link. The link from the price list equals the external link in the card. Works only if the catalog products were created by a parser from this same supplier's site. Almost never makes false pairs, but silently fails on any detail: a different protocol, a trailing slash, an added
?utm_…. - Search for found products by name in other price lists. Takes the pair from a row in another price list with exactly the same name: match a product in one supplier's price list, and a second supplier with the same name gets it automatically. The name is compared raw, without cleanup and without considering supplier, manufacturer or category, so this type is risky.
- Individual matching type. An empty template where you build the rule yourself: How to build a custom product matching rule.
Field settings only work for four types: individual, “Search by MPN”, “Search by supplier SKU” and “Search by product name”. The others have their conditions built into the program. In some of them the right panel still shows a field table, but the run doesn't read it — there's nothing to edit there.
What happens to a pair when an item disappears from the price list
Matching only records which catalog product a price list row corresponds to; prices and availability are carried over by “Updating base catalog”. When it runs: When the price from the price list appears in the product card.
If the item is no longer in the supplier's file, its row simply won't be in the price list after the next import: before writing the fresh file, the program deletes the old price list rows, and the link disappears together with the row.
The product itself stays in the catalog. When “Updating base catalog” runs across all price lists with availability update turned on, a product that isn't in any price list gets the out-of-stock status. An update for one selected price list doesn't touch such a product.
The manual pair in the directory isn't deleted, though. If the item comes back to the file and the program recognizes it as the same one, the “Search for manually matched products” type will link it to the same product again.
It recognizes the row by its fingerprint: by default, the manufacturer SKU together with the name, or the unique fields if they're marked in the price list column settings. If the supplier changed the SKU or the name, the pair no longer fits by fingerprint, and only the “Restore manual matches by fields:” checkboxes can find it.
How to change type defaults for all price lists
This is a different window, and it behaves differently. It opens from the “Directories” → “Processing price lists” → “Matching types” menu or from the “Matching types” item in the “Menu” in the header of the left sources panel — a different menu from the one that opens the per-price-list window.
It looks like an ordinary directory. But editing a row in it changes the settings in all price lists at once.
The window itself warns you about this: “Below are the default settings for new price lists. Warning: changing them also affects price lists that already exist. The exception is “Order”: it only sets the position of the type in a new price list — the order inside existing price lists is changed by dragging within the price list itself.”
You edit the grid by double-clicking a cell. Columns: “Active”, “Matching type name”, “Order”, “Remove Cyrillic”, “Remove special characters”, four “Consider …” columns and “Min. characters” — the last one is shown but can't be edited.
1
Warning about changes2
Active column3
Remove Cyrillic / special characters4
Additional operations- Warning: changes here affect all price lists at once.
- Active column.
- Remove Cyrillic and Remove special characters — defaults for a new price list.
- Burger menu — matching can be started for all price lists from here.
There are no “add” or “delete” buttons here: the list of types is fixed, and you can't create your own type in the directory. Your own rule is made as an individual type in a specific price list.
The “Order” column in the directory sets the order for new price lists. It doesn't change the order in price lists that already exist: there you change it by dragging in the per-price-list window.
How a stock price list is matched
If you open the matching settings for a stock price list, you'll see a different set of types and an empty right panel — that's expected. A stock price list isn't checked against the base catalog: it's checked against the same supplier's main price list, to carry over availability, quantity and prices from there.
That's why it has its own types — search by barcode, by supplier SKU, by manufacturer SKU with name, by name and by manufacturer SKU (these five work out of the box), plus four substring-match types.
Their fields, conditions and order are built into the program; word cleanup and minimum length don't apply, and dragging the list doesn't affect the order. There's nothing to configure there.
What to check when a supplier matches poorly
Check in this order
Scenarios
Three typical shop tasks and which types and checkboxes each one needs. How to change the rules and check them without losing good pairs — see the article on restarting matching.
The supplier writes the manufacturer SKU only inside the name
What to turn on: in the “Product matching settings” window, “Add matching type” → “Search for the base catalog MPN in the price list product name”. Drag the type above “Search by product name”.
What you get: a price list row gets the catalog product whose “Manufacturer SKU” appears in the row name as a separate word — at the start, at the end or between spaces — and the row's manufacturer matches the product's manufacturer.
What you won't get: catalog products with an empty manufacturer SKU don't take part in the search. An SKU joined to another word without a space won't be found. Word cleanup, minimum length and the “Consider …” checkboxes don't apply to this type.
The supplier only gives its own internal product code
What to turn on: “Add matching type” → “Search by supplier SKU”. In this type's rule row, check “Consider supplier”.
What you get: a pair is made when the supplier SKU in the price list exactly matches the supplier SKU in the product card and the card's supplier is the same supplier.
What you won't get: a product whose card lists a different supplier won't be matched, even if the code matches. Codes shorter than 5 characters are dropped from the comparison — that's the minimum length the type is added with.
Names are in Cyrillic, and “Search by product name” finds nothing
What to turn on: select the “Search by product name” type and clear “Remove cyrillic” in its rule row.
What you get: names are compared in full — lowercase, without spaces, and while “Remove special characters” is on, without punctuation too. The catalog name is taken in the storefront language.
What you won't get: names that differ by even one word won't match: the = condition requires an exact match. To remove the words that differ between your names and the supplier's, fill in “Clean words” for the same row.
FAQ
Why did the program assign a completely wrong product?
Several catalog products fit the rule, and the program took an arbitrary one without warning. Narrow the rule: a second row, “Consider manufacturer” or “Consider category”, a larger minimum length (order of types).
The supplier changed names, and manual links were lost. What should I do?
In the “Search for manually matched products” type, check “Manufacturer SKU” or “Supplier SKU” and “Supplier”, and leave “Name” unchecked. The pairs come back on the next price list import (manual pairs).
How do I turn off automatic matching for a price list?
There's no separate switch: remove the matching operation from this price list's operations (order of operations).
Does editing the “Matching types” directory change existing price lists?
Yes, all of them at once, except the “Order” column: it only sets the type's position in new price lists (types directory).
How do I find out how many rows were left without a pair?
The work log doesn't record this. Look at the price list product grid: the “Product found” and “Catalog product ID” fields, and the “Match type” column for the type that found the pair (run progress).
/section>Where to find it and who has access
- Other ways in
- “List of price lists” → source → “More” → “Processing rules” → “Product matching settings”
- From the source card
- the section with the list of settings → “Product matching settings”
- Defaults for all price lists
- Directories → Processing price lists → Matching types
- Access right
- the “Product matching types” window; the directory — “Matching types”
Everything you do in the “Product matching settings” window applies to one price list only — adding a type, deleting it, the order, the rule fields. There is one exception: the “Apply to all price lists” button in the manual pairs type.
The “List of price lists” has two different menus, and it's easy to mix them up. “More” is in the header of the selected source and holds that source's settings. “Menu” is in the header of the left panel with the list of sources and holds shared directories and actions for all price lists at once.
On the left is “List of product matching types:”, on the right — “Matching type settings” for the type you selected in the list. Until you select something, the right panel asks you to pick an item on the left. Some types have nothing to configure, and the panel stays empty.
In the window header: “Add matching type” (a menu with types this price list doesn't have yet), “Start product matching” (drops all links of the price list — how to restart safely), the “Delete” trash icon for the selected type, and “?” for help.
1
List of matching types2
Add matching type3
Start product matching4
Delete5
Settings of the selected type- The list of matching types — the order is the order of application; rows can be dragged.
- Add matching type — offers only the types this price list does not have yet.
- Start product matching — drops all links of the price list and rebuilds them.
- Delete — removes the selected type from this price list.
- The right panel holds the settings of the type selected on the left.
Related topics
- If none of the standard types fits your supplier — How to build a custom product matching rule.
- If you've changed the types and need to rebuild the price list's pairs — How to restart price list matching without losing manual pairs.
- If some rows are still without a pair after the rules — How to manually match price list products with the catalog.
- If price list values need fixing before matching — Order of operations during price list import.
- If you're deciding whether to hand price lists over to the program — what it gives your shop.
