Build your own matching rule for a supplier: which catalog field to compare with which price list field, and how. Each import then links those rows for you.
When you need this:
- SKU buried in a long name —
~finds the catalog SKU inside the price list name. - Random pairs — a second rule row adds an “and”, e.g. “and the brand is the same”.
- Names differ by filler words — “Clean words” removes them from both sides first.
- Short values match anything — minimum length discards “1”, “pcs” and “-”.
Where to start: the price list's “Product matching settings” → “Add matching type” → “Individual matching type”.
What a custom rule can do
The standard matching types are covered in the article on automatic matching; a custom rule isn't built from them but as a separate, individual type.
- Any pair of fields — a catalog field, a price list field and one of five comparison conditions.
- Up to ten rows joined by “and” — a pair is set only when all of them match, plus the “Consider manufacturer”, “… category”, “… supplier” and “… store” checkboxes.
- Value cleanup — Cyrillic, special characters, a word list and a minimum length, separately for each row.
- Index search — the
i~andi~~conditions take the best full-text search match. - As many rules per price list as you like — each with its own name and place in the queue of types.
How to add an individual type
You need an individual type when no standard type fits your supplier, or when a pair has to be found by two fields at once. Unlike the other types, you can add it to a price list as many times as you like — each with its own name and its own rule.
Here is an example we'll follow throughout. The supplier “Kabel-Opt” sends two columns: “Name” with the value Cable USB-C Baseus CAKW-01 1m and “Manufacturer” with the value Baseus. There is no separate SKU column. In the catalog, the manufacturer SKU sits in its own field — CAKW-01, and the brand is the same.
Step 1. Add the type
“Add matching type” → “Individual matching type”. The program asks for a name: the “New matching type” dialog, field “Matching type name”. An empty name is rejected with “You must enter a matching type name!”. The name is up to you; in the example, call it “SKU in name + manufacturer”.
1
Individual matching type2
Other available types- Individual matching type — an empty template that can be added to a price list any number of times.
- The other items are types this price list does not have yet; types already added are not listed.
Once added, you'll see the “Added” toast, and the type appears in the list on the left. Drag it to set its place: this type is more precise than name search, so it should sit above it.
How to pick fields for a rule row
Step 2. Add a rule row
On the right, a table opens with the columns “Base catalog field”, “Logical condition for comparison”, “Field from the price list”, then the cleanup and “Consider” checkboxes, “Minimum length”, “Order” and “Active”. A new type has no rows — you build the rule from scratch.
The “+” button above the table opens the list of base catalog fields; double-click a row to move that field into the rule. Remove an unneeded row with the trash icon. A new row gets the = condition, a minimum length of 6 and “Active” turned on; its price list field is still empty.
1
Add field button2
Minimum length3
Active- The plus button above the table opens the list of base catalog fields; a field is moved into the rule by double click.
- Minimum length — values shorter than this are dropped from comparison on both sides.
- Active — a switched-off row does not take part in the run.
The catalog field list holds every field of the product card plus every active attribute of your products, so there are thousands of rows (over three thousand in our database): use the filter.
The list columns are field name, description and code. Names repeat — “Name” appears several times, “Manufacturer SKU” twice — so go by the “Code” column rather than the name: it identifies the field unambiguously.
Four fields in the list can't be used — product_selected, progressbar_product_scoring_filling_card, progressbar_total_attribute_empty and “Length” (code product_length): they exist only in the catalog grid, have no data behind them, and the comparison won't work.
1
Name column2
Filter row3
Double-click hint- Name column — names can repeat, so the name alone does not identify a field.
- Filter row — the list is very long and is narrowed by typing here.
- Hint — a field is moved into the rule by double click.
You pick the price list field with the chevron button in the “Field from the price list” column. A small window opens with one drop-down list: type to find the field, names filter as you type. The list has about fifty fields.
1
Dropdown field2
List of values- The dropdown is the only element of the dialog; the value is found by typing.
- The list contains only field names, with no codes and no notes on where a file column goes.
The list is the same for every price list: it shows the fields a price list can have, not the ones filled in for your source. It doesn't mark empty fields or show which file column loads into a field. Pick an empty field and the rule silently finds nothing: rows with an empty value drop out of the comparison.
Before choosing, look at this price list's product grid and make sure the column is actually filled in.
In the example, the first rule row is: catalog field “Manufacturer SKU”, price list field “Name”.
Which comparison condition to choose
Step 3. Choose the condition
The “Logical condition for comparison” column has exactly five values. Here is what each one gives on our data: CAKW-01 in the catalog, Cable USB-C Baseus CAKW-01 1m in the price list.
| Condition | What it does | Match in the example | When to use |
|---|---|---|---|
= | both values match exactly | no — the strings differ | SKUs, barcodes, links: where the value is complete and identical on both sides |
~ | the catalog value is searched for inside the price list value | yes | a long string in the price list, a short one in the catalog: the SKU inside the name |
~~ | the price list value is searched for inside the catalog value | no | the mirror case: a long name in the catalog, a short SKU in the price list |
i~ | same as ~, but through the price list search index | depends on the index | only with the index turned on (search index) |
i~~ | same as ~~, but through the catalog search index | depends on the index | only with the index turned on |
Before comparing, the program strips all spaces from both values — always, whatever the checkboxes. So “Cable USB-C 1 m” and “Cable USB-C 1m” are the same to it, and by the time of comparison our price list row looks like cableusb-cbaseuscakw-011m. It contains the SKU cakw-01, so the ~ condition fires.
The table has no “Save” button. A row is edited as a whole and saved when you click outside it — on another row or on empty space. Adding and deleting a row are saved immediately.
How to narrow a rule: minimum length and a second row
Step 4. Minimum length
Minimum length is measured after all cleanup — Cyrillic, special characters, listed words and spaces. It doesn't let a row “skip” the check; it removes a short value from the comparison on both sides, catalog and price list. This cuts off junk like “1”, “pcs” or “-” that would otherwise match anything. 0 turns the check off.
In our example cakw-01 is seven characters, so it passes with a value of 6.
A trap for later: if your second rule row is “Manufacturer = Manufacturer” with the same minimum length of 6, the brand Baseus (exactly six) passes, but LG (two) doesn't, and all products of that brand drop out of the comparison. The rule won't work for them at all. For short values, set 0.
Minimum length, the cleanup checkboxes and the “Consider …” checkboxes belong to an individual rule row, not to the whole type. Each row has its own.
Step 5. A second row and how rows combine
Rule rows combine with “and”: a pair counts only if all rows match. This is the only way to build a compound condition — “SKU and manufacturer”, “name and volume”.
Add a second row: catalog field “Manufacturer ID”, condition =, price list field “Manufacturer”, minimum length 0. The names differ on purpose: the catalog list labels the brand “Manufacturer ID”, and the comparison uses the brand name instead of the ID. Now the SKU must be in the name and the brand must match: far fewer random pairs.
The one cost: a catalog product without a brand gets an empty value. It will no longer match price list rows that have a manufacturer, but it can match a row whose manufacturer is also empty. If the rule “stopped finding half” after you added the second row, check the manufacturer in the product cards first.
Limits and silent spots to keep in mind:
- a run uses at most ten rule rows, in the order of the “Order” column. The eleventh and later rows aren't applied;
- only rows with “Active” turned on and both fields and the condition filled in count. A row with an empty price list field drops out of the rule silently, with no warning;
- if no usable row is left in the rule, the type is simply skipped during the run.
The four checkboxes “Consider manufacturer”, “Consider category”, “Consider supplier” and “Consider store” add one more condition to the same “and” — not on the chosen field, but on the row's links: the price list row's manufacturer must match the catalog product's manufacturer, category must match category, supplier must match supplier, store must match store. All four are cleared by default.
A caveat about the first two. A price list row's manufacturer and category are filled in by earlier import operations. If the manufacturer isn't determined, “manufacturer = manufacturer” matches every product without a manufacturer: the checkbox glues unnamed products together instead of filtering. Before relying on the manufacturer, make sure the price list determines it.
How to remove extra words before comparing
Below the field table is the “Clean words” field with the placeholder “list of words, each on a new line”. That's the format: one word per line.
The list belongs to the rule row selected in the table, not to the whole type. A two-row rule has two word lists, and you see the list of the row that's currently highlighted. Click another row and the field refills with that row's list.
So select the row you need first, and only then fill in the list. Otherwise it's easy to add words to one row and believe they apply to the whole rule.
The list is applied the same way to both sides of the comparison — the catalog value and the price list value.
Words are removed by plain substring replacement, case-insensitive — word boundaries are ignored. So “pro” also cuts into “profile”, and “new” breaks “renewal”. Use longer, more precise words, and test doubtful ones on a few names.
Where cleanup sits in the chain matters too: words are removed after Cyrillic and special characters, but before minimum length is measured. So length is measured on the cleaned value, and a too-generous word list can shorten a value enough to drop it from the comparison.
- Action or result
- Decision: the path depends on the answer
The “Create a list of words” button builds a vocabulary from this price list's unmatched products: very short words are dropped, at most a thousand words, longest first. They appear below the button and aren't moved into “Clean words” automatically. Go through this raw material and copy what gets in the way into the field, which saves without a button.
1
Clean words field2
Create a list of words3
Global cleanup rules4
Collected words- Clean words — one word per line; the words are cut from both compared sides, and each rule row has its own list.
- Create a list of words — collects candidates from this price list's unmatched products.
- The button under the field opens the global word cleanup rules shared by all price lists.
- The collected words are shown under the button and are copied into the field by hand.
Words to clean in all price lists at once live in a separate window, “Word cleanup rules for product matching (for all price lists)” — open it with the “Open global word cleanup rules” button right below “Clean words” (the same action is also an icon in the form's additional operations menu).
When the i~ and i~~ conditions work
These two conditions don't use plain string comparison but a search index, and each needs its own index: i~ requires “Price list search index” turned on, i~~ requires “Catalog search index”.
Both switches are in the “System settings” window, “Search” section. These are dangerous settings: the program asks “This setting affects the whole system. Apply the change?”.
Turning on “Price list search index” creates the index and turning it off deletes it, so turning it back on means a full, slow reindex. “Catalog search index” only turns use of the index on or off; it doesn't create or delete it. Underneath, the platform needs a running search server — an installation requirement, not an account setting.
When the index is on and the rule has a row with i~ or i~~, the whole type switches to the index branch: no plain comparison runs. A full-text morphological search runs instead, and the single best result is taken, even if it's weak. Cleanup, minimum length and the “Consider …” checkboxes don't apply in this branch at all.
The two search indexes are turned on separately and are off by default: until the index is on, the i~~ condition doesn't work.
If neither index is on, a rule row with such a condition is silently skipped — no error, the rule just works without it. But if one index is on and the row needs the other, the whole type is silently skipped: the rule's other rows won't fire either. So don't mix index and plain conditions in one rule.
How to check a rule
The window has no rule preview or trial run. The working routine is: change the rule — run matching — check the log and the price list's product grid.
- How many products each type found is shown in the operation log as “Total items found: N”.
- Which pairs were set is visible in the price list's product grid: the “Product found” and “Catalog product ID” fields and the “Match type” column.
- The program doesn't check field compatibility: a numeric catalog field and a text price list field can be chosen side by side with no warning.
- The field list doesn't show whether a price list field is filled in for your source — check the price list's product grid.
Running matching removes all of the price list's links. How not to lose manual pairs — How to restart price list matching.
Scenarios
SKU in the name, brand in a separate column
What to do. Add an individual type. First row: “Manufacturer SKU” ~ “Name”. Second row: “Manufacturer ID” = “Manufacturer”, minimum length 0. Drag the type above “Search by product name”.
What you get. A pair is set when the catalog SKU is found in the row's name and the brand matches: CAKW-01 in “Cable USB-C Baseus CAKW-01 1m” from Baseus.
What you won't get. Catalog products without a brand won't match rows that have a manufacturer. A rule row with an empty price list field drops out of the rule silently.
Names in the price list and catalog differ by filler words
What to do. Select the rule row, click “Create a list of words” and move the extra words into the “Clean words” field — one word per line.
What you get. The words are removed from both sides of the comparison before minimum length is measured, and names that differed only by them now match.
What you won't get. A word is cut out as a substring: “pro” breaks “profile”. The list applies only to the rule row that was selected.
The rule links products at random
What to do. Add a second rule row or turn on “Consider manufacturer” or “Consider category” in the row; raise the minimum length.
What you get. A pair is set only when all rows and checkbox conditions match, and short values drop out of the comparison.
What you won't get. If several catalog products still fit the rule, the program takes an arbitrary one without warning. A manufacturer not determined in the price list row matches every product without a manufacturer.
FAQ
How many rule rows are taken into account?
Up to ten, in the order of the “Order” column; the eleventh and later aren't applied. Only active rows with both fields and the condition filled in count (rule rows).
I added a rule row, but it doesn't work. Why?
Most often the row's price list field is empty or not filled in for your supplier: such a row drops out silently. Other causes are “Active” turned off or a minimum length that discards short values (minimum length).
Why do the i~ and i~~ conditions give nothing?
They need a search index turned on: i~ — the price list index, i~~ — the catalog index. With no index at all, the row is silently skipped; with the wrong one on, the whole type is skipped (search index).
How do I check a rule without running matching?
You can't: there is no trial run. You see the result after a run — in the operation log for each type and in the price list's product grid (checking a rule).
Can I create a custom type for all price lists at once?
No. An individual type is added to a specific price list, and the “Matching types” directory doesn't accept new types (types directory).
Why does the catalog field list have several “Name” fields?
The list contains every card field and active attribute, and names in it repeat. Go by the field code column: it identifies the field unambiguously.
Where it is and who has access
- Other ways in
- “List of price lists” → source → “More” → “Processing rules” → “Product matching settings”
- Access right
- the “Product matching types” window in “Group permissions”
- Prepare
- a price list in which the column you need is actually filled in
The window has no menu item. A rule works only in the price list where it was created.
Related topics
- For the big picture of which types already work and in what order — How to set up automatic product matching.
- If you changed a rule and need to rebuild the price list's pairs — How to restart price list matching without losing manual pairs.
- If price list values need fixing before matching — Order of operations during price list import.
- If some rows are left without a pair after the rules — How to manually match price list products with the catalog.
