On every price list import, Elbuz cleans supplier names, descriptions, and attributes: replaces words, removes clutter, cuts out text between two markers. You set a rule once.
When you need this:
- A supplier adds “(SALE!!!)” or a technical wrapper to names — “Delete text” removes it everywhere.
- Suppliers spell a brand differently — a shared rule turns “Самсунг” into “Samsung” everywhere.
- A description ends with an ad tail — a rule cuts it off from its first word.
- An attribute value isn't spelled your way — an exact-match rule fixes it.
Where to start: add a rule in the “Text replacement rules” window and import the price list again.
What text replacement rules can do
- Replace text — “Самсунг” with “Samsung” in every name where it appears.
- Remove clutter — a technical wrapper, “SALE!!!”, other companies' phone numbers in a description.
- Cut out a piece between two markers — an advertising tail of a description or an insert in brackets.
- Remove Cyrillic or special characters — from a SKU or model.
- Fill an empty field — with your own text or the value of another price list column.
- Apply to all price lists at once — shared rules are set up once.
- Remove words that get in the way of matching — without changing the price list itself.
Task route
- Add a rule: pick a field, enter the textText replacement rules
- If needed, narrow the rule by categories or an additional filterText replacement rules
- Make sure the replacement operation is in the price list's list of operationsOperation order
- Re-import the price list and check the result in the product gridList of price lists
How to create a rule
A rule starts from a field. First you tell Elbuz what you're cleaning — name, description, SKU — and only then enter the text. That's why the “Add” button opens a list of fields, not a form.
Step one: pick a field
The list has two sections: “Catalog fields” and “Product attributes”; attributes are marked “attribute”. At the top is “Recently selected” — up to five fields you worked with last.
1
Search field…2
Catalog fields3
Product attributes- Search field… — type part of a name to filter the list.
- Catalog fields — built-in product fields.
- Product attributes — attribute fields, marked «attribute».
The list is long. The demo database has 91 price list fields and 3,104 active attributes. Elbuz shows at most a hundred items and displays the hint “Not all shown. N more — refine your search”, where N is how many are left.
The “Search field…” box appears as soon as there are more than fifteen items — use it; scrolling through the whole list makes no sense.
The field label comes from the price list product grid settings, so in the list it may differ from the name you remember from another window: Elbuz labels the same field differently in different grids. Each field appears in the list exactly once. Rely on searching by name, not on the position in the list.
Step two: the “New replacement rule” dialog
After you pick a field, a small form opens. At the top is the line “Field: name of the selected field”, so you can see where the rule goes.
1
Field: Name2
Search3
Delete text4
Use a regular expression- Field: Name — a rule is always created for a chosen field.
- Search — the text to find (here ![CDATA[).
- Delete text — removes the found text; the Replace field is not used.
- Use a regular expression — treats the Search text as a regular expression.
| Form field | What to enter |
|---|---|
| Search | The text to look for in the field. Required; the cursor is placed in it right away. |
| Replace | What to replace the found text with. An empty field means “with nothing”. |
| Delete text | Checkbox: the found text is removed, and the “Replace” field isn't used. |
| Case sensitive | Checkbox: “TV” and “tv” become different texts. |
| Use a regular expression | Checkbox: “Search” is treated as a pattern, not as exact text. |
| Note | Text for yourself. It doesn't affect how the rule works. |
The buttons are “Create” and “Cancel”. The form won't accept an empty “Search”: “Enter the text to search for” appears under the field. You can't create a rule made of spaces only either.
The form keeps edge spaces, but import still trims them unless “Allow spaces in text” is on in the grid — and a new rule has it cleared. So by default “TV ” with a trailing space is searched as “TV”; how to change this — below, in the section about spaces.
The form has three checkboxes, the grid has seven, plus “Active”. The rest is set in the grid, in the rule's row — the next two sections cover this.
You can't change the field of an existing rule: the “Field” column in the grid isn't editable. Picked the wrong field — create the rule again and delete the extra one.
How to replace, remove, or cut out text
There are only a few actions, set with checkboxes in the rule's row. Which ones to select depends on what you need to do with the text.
- Action or result
- Decision: the path depends on the answer
Replace the found text inside a value
This is the default behavior, controlled by the “Partial match” checkbox. When it's on, the text is searched inside the value and every occurrence is replaced, not just the first. The rule “Самсунг” → “Samsung” fixes the name “Телевізор Самсунг, пульт Самсунг” completely.
Case is ignored by default: “самсунг”, “Самсунг”, and “САМСУНГ” are all caught by such a rule.
Fire only on an exact match
Clear “Partial match”, and the rule will require the field value to equal the “Search” text in full. This is rarely needed, and almost always for attribute values.
A typical case: an attribute cell holds a whole value — “Yes”, “Black”, “XL” — and you need to bring it to your spelling without touching names where the same word just happens to appear.
A cleared “Partial match” together with an empty “Search” gives a rule that does nothing. The condition becomes “the field equals empty text”, so the rule only touches products whose field is already empty. If you leave “Search” empty on purpose — for the cleanups described below — keep the checkbox on.
Remove the found text
The “Delete text” checkbox. The found text is cut out of the field, and the “Replace” column isn't used at all — you can leave it empty. This is the most common mode.
An example from the demo database: two rules with this checkbox — for “![CDATA[” and for “]]” — clean 95 names out of 95, every name of the source. The supplier wraps each name in technical text, and two lines of settings remove it for good.
“Delete text” ends the rule. If the same row also has “Replace” or cleanup checkboxes filled in, they won't run. Need two actions — make two rules.
Cut out a block between two markers
Two grid columns, “Block start text” and “Block end text”, work as a pair and separately from “Search”.
- Only the start is filled in. Everything from the found text to the end of the value is cut off, including the text itself. This is how you remove tails like “ARDESTO multicooker — more details on the supplier's website”.
- Both start and end are filled in. The fragment between them is cut out — together with both markers. This is how you remove inserts in brackets or technical tags in a description.
If “Search” and “Replace” are empty, the rule ends after the cut. If they're filled in, a regular replacement follows.
Marker length doesn't matter: exactly the fragment between the markers is cut out, markers included. The marker “[note” works as precisely as a single square bracket — the text before it stays untouched.
Remove Cyrillic or special characters
Two checkboxes for removing a whole class of characters rather than specific text.
- “Delete Cyrillic” — removes Cyrillic letters from the field, collapses the double spaces left behind, and trims spaces at the edges. Useful when a supplier mixes explanations in Ukrainian into the SKU or model field.
- “Delete special characters” — removes control characters and punctuation: hyphen, quotes, period, comma, slash, brackets, exclamation and question marks, and other technical characters.
Both cleanups are limited by the “Search” text: they only work on rows where that text occurs. To clean the field in all products, leave “Search” empty and keep “Partial match” on — otherwise the rule looks for products with an empty field.
Unlike “Delete text”, the “Delete special characters” checkbox doesn't end the rule: after it, the same row also replaces “Search” with “Replace”.
How to specify what to search for more precisely
Four settings refine how a rule searches for text: case sensitive, by pattern, with spaces at the edges, or with special macro words.
Case sensitive
By default, case doesn't matter. The “Case sensitive” checkbox makes the search exact: “TV” no longer finds “tv”. Together with “Delete text” this checkbox has no effect — deletion always ignores case.
In this mode, the “Search” text is matched as a plain string, character by character. So a period, hyphen, brackets, asterisk, slash, and other special characters are matched literally — “Bosch (2.5-3.0)” finds exactly this text.
A pattern instead of exact text
The “Use a regular expression” checkbox turns “Search” from exact text into a pattern: it describes a word's shape, not the word — “four digits in a row”, “everything in parentheses at the end of the line”. The syntax is PCRE, as in the “Regular expressions” window, which also tests an expression on sample text and has ready-made examples.
Two notes. The “Case sensitive” checkbox doesn't work in this mode at all — it simply isn't used. And an error in the pattern itself produces no message: the rule silently does nothing, and the price list import continues. If a pattern rule didn't work, suspect an error in the expression first.
Spaces at the edges
The “Allow spaces in text” checkbox. Off — spaces at the edges of “Search”, “Replace”, and both block markers are trimmed. On — they're kept.
You need it when you remove a word together with the space after it: the rule “TV ” → empty with the checkbox on gives “Samsung QLED”, and without it — “Samsung QLED” with a double space.
Macros
A few special words you can write instead of text. They go in curly braces and work in their own fields.
| Macro | Where to write it | What it does |
|---|---|---|
{ПРОБЕЛ} or {SPACE} | “Search”, “Replace”, both block markers | Stands for a space. Works even when “Allow spaces in text” is off — so it's a reliable way to set a space explicitly. |
{ПУСТО} or {EMPTY} | “Search” | The rule fires only where the field is empty or contains a single zero. This is how you fill empty fields with the text from “Replace”. |
{Price list: Field name} | “Replace” | Inserts the value of another price list column. For example, a rule on the “Name” field with {Price list: Supplier SKU} in “Replace” puts the SKU from the same row into the name. |
The “fill an empty field” scenario takes two fields: in “Search” you write {ПУСТО}, in “Replace” — the value that should fill the gaps in the price list. No other rule checkboxes are needed: the macro sets the selection condition itself, and the rule ends on it.
The window's reference offers this same scenario. It's a rare one: empty fields are more often fixed on the supplier's side.
What exactly the macro treats as empty: a truly empty cell and a cell containing a single zero. Neither “0 points” nor “Samsung TV” qualifies.
Text replacement or regular expressions
Elbuz also has a “Regular expressions” window, and people confuse the two all the time. The difference is not that “there you have patterns and here plain text”: there's a pattern here too, under the “Use a regular expression” checkbox.
The difference is where the result is allowed to go. Text replacement writes it only back to the same field it read from. Regular expressions also write to their own field by default, but you can change the target field: extract a SKU from the name and write it to the SKU field.
So both windows can clean one field: here by exact text or pattern, there by pattern with a preview. Only regular expressions can move a value to another field. Shared rules for all price lists, removing a block by start and end, and cleaning Cyrillic and special characters exist only here.
| Feature | Text replacement rules | Regular expressions |
|---|---|---|
| Where the result can go | only to the same field | to the same or another field — your choice |
| Main action | replace or remove the found text | extract the found text |
| Shared rules for all price lists | yes | no, one price list only |
| Simple mode without expressions | yes: substring search, exact match, character removal | no |
| Limit by manufacturer | no | yes |
| Remove a block by start and end | yes | no |
| Clean Cyrillic and special characters | yes | no |
| Case sensitivity | separate checkbox | no |
| Default value when nothing is found | no | yes |
| Check before import | no | yes, on a line of text and on price list products |
In the list of import operations these are also two separate steps, and text replacement runs first. More about the other window: Regular expressions: extract a value from price list text.
Window buttons and columns
Button bar
- “Add” — opens the list of fields that a new rule starts from.
- “Delete” — removes the selected rows. It asks for confirmation and shows what exactly is being deleted.
- “Copy” — duplicates the selected rule together with the categories chosen for it. Handy when you need the same rule for a neighboring field or with different text: copy it and adjust it in the grid.
- “Select base catalog categories” — narrows the selected rule to certain categories.
- “Additional operations” — a menu with two items: “Refresh” and “Clear filter”.
- “Help” — opens the help article on the website.
Reference at the top of the window
Under the button bar is a collapsed reference: a single path line, and the “Show more” button expands eight sections — from “How rules are processed” to “Typical scenarios” with six ready-made recipes. It's a short reference on the same settings, right there in the window.
1
Add2
Copy3
Select base catalog categories4
Partial match5
Number of items6
Show more- Add — creates a new replacement rule starting from a field.
- Copy — duplicates the selected rule.
- Select base catalog categories — limits the rule to chosen categories.
- Partial match — the search text is looked up inside the field value.
- Number of items — how many rows the rule changed during the last run.
- Show more — expands the collapsed reference text.
Grid columns
Values are edited right in the cell: a click opens the cell for editing, and leaving it saves the change. The grid has no separate “Save” button.
There's no “undo” button. To get rid of the effects of a bad rule, turn it off with the “Active” checkbox or delete it, and import the price list again.
Nine columns are the checkboxes and texts covered in the previous section: “Search”, “Replace”, “Delete text”, “Case sensitive”, “Allow spaces in text”, “Use a regular expression”, “Delete Cyrillic”, “Delete special characters”, “Partial match”. Two more are the block markers: “Block start text” and “Block end text”. The rest:
| Column | What it contains |
|---|---|
| Field | The product field the rule cleans. Set on creation and not editable. |
| Processing order | A number that decides which rule runs earlier. |
| Base catalog category | Categories the rule is narrowed to. Set with a button, not typed in. |
| Preprocessing formula | A technical column. Not needed in everyday work. |
| Note | Text for yourself. |
| Active | Clearing the checkbox turns the rule off without deleting it. |
| The rule number. | |
| Number of items | How many price list rows the rule changed. The specifics of this column are covered in a separate section below. |
Below the grid is a line that shows the categories of the selected rule.
How to limit a rule by categories or a filter
By default, a rule touches all rows of the price list. You can narrow it in two ways, and they don't interfere with each other.
Base catalog categories
Select the rule's row and click “Select base catalog categories”. The selected categories are shown below the grid, and the rule then applies only to price list products that have landed in these categories.
1
Category tree2
Save- Category tree — check the base catalog categories the rule applies to.
- Save — stores the selection (not pressed here).
“Landed” is the key word: these are categories of your catalog, not those in the supplier's file. Products are distributed across your categories in a separate import step that comes before text replacement in the list of operations. So by the time of replacement the category is known.
Deleting a catalog category removes the rule's restriction. If a rule had a single category and you deleted it, the link is gone — and the rule applies to the whole price list. It looks as if the rule “suddenly started spoiling other products”. After cleaning up the category tree, reselect categories in rules that had them.
Additional filter
Below the grid is a collapsible “Additional filter” block — a condition builder on price list fields. The order is: first select the rule's row, then set the condition, then click “Save”. The condition is saved to the selected rule, and the “Updated” toast confirms it.
1
Price list field2
Operator3
Clear All- Price list field — the field the condition checks.
- Operator — contains, doesn't contain, begins with, is empty and others.
- Clear All — removes all conditions.
For numbers and prices, the comparisons are “equal to”, “not equal to”, “less than”, “less than or equal to”, “greater than”, “greater than or equal to”, “between”. For text — “contains”, “does not contain”, “equal to”, “not equal to”, “begins with”, “does not start with”, “ends with”, “does not end with”, “empty string”, “non-empty string”. “Clear All” removes the condition.
The block is hidden while the grid has no rows, and it expands by itself when you select a rule that already has a condition.
It's a rarely used tool, but it's exactly what helps when you need to limit a rule by something that isn't among the grid columns: for example, clean the name only for products priced over a thousand.
In what order rules run
The order matters because rules are applied in a cascade: the second rule sees the result of the first, the third sees the result of the second. There's no “this row is already processed” mark — each rule goes through all price list products again.
The order is:
- first, all shared rules — the ones set for all price lists;
- then all rules of this price list;
- within each group — by the “Processing order” column, and for equal values — by rule number, older ones first.
New rules have “Processing order” set to zero, so by default rules run in the order they were created.
The grid shows rules in the reverse of their run order. By default it sorts by number, newest on top — and those are the ones that run last. If the order matters to you, enter numbers in the “Processing order” column explicitly or sort the grid by it by clicking the header.
A classic example of what the cascade does. Rule A changes “TV ” to “Television ”, rule B changes “Television” to “Smart TV”.
If A runs first, the name goes through both rules and becomes “Smart TV”. If B runs first, it finds nothing, and after A the name keeps “Television”. The same two rows give different results — and only the “Processing order” column controls this.
Shared rules and rules for one price list
There are two sets of rules, but one window that looks the same. You need to tell them apart deliberately, or the rule ends up somewhere other than you think.
| Feature | Shared rules | Rules of one price list |
|---|---|---|
| How to open | menu; header menu of the price list list → “Text replacement rules” | source row menu → “Processing rules”; source card → “Additional” section |
| Hint in the window | “The settings for all price lists are used.” | none |
| When they run | first | after the shared ones |
| What deletes them | nothing — they stay until you delete them manually | deleting the price list or the contact |
Shared rules are what you do the same way for all suppliers: remove “SALE!!!”, unify a brand's spelling, strip other companies' phone numbers from descriptions. Price list rules cover a specific file: a technical wrapper around the name, a supplier's note at the end of the description.
When a rule runs
Text replacement is one of the price list import steps. In the list of operations it's called “Apply text autocorrect rules” and comes after distributing products across catalog categories and before manufacturer lookup. You set the order of steps in the “Operation order” window.
1
Apply text autocorrect rules2
Distribute products across base catalog categories3
Auto-replacement of product values based on regular expressions- Apply text autocorrect rules — the text replacement step.
- Distribute products across base catalog categories — runs before it, because replacement relies on the category.
- Auto-replacement of product values based on regular expressions — the neighbouring function, runs after.
The position in the list is deliberate: the product category is already known, and manufacturer lookup and catalog matching see cleaned names. If the operation is removed from the list, the rules don't run at all, and there's no warning about it. More details: Order of operations during price list import.
Rules apply to all price list rows every time it's processed, not only to new ones. A special case is price lists that come from an “Article” type parser: only a few steps from the list of operations run for them, and text replacement is one of them.
Rules change price list rows, not products in your catalog. The product card gets the corrected name only when you run a .
You can't fix cards already in the catalog with this window.
In the work log, replacement leaves a technical entry that's hidden by default, and it doesn't post any message like “so many rows replaced”. The only report on the result is the “Number of items” column in the rules window.
Checking a new rule
What “Number of items” shows
It's how many price list rows the rule changed during the last import. Before applying rules, Elbuz resets their counters — so zero means exactly “found nothing this time”, not “didn't find anything at some point”. The window's reference says the same: “The “Number of items” column shows how many rows the rule changed during the last run.”
Every branch of a rule writes the number: replacement, case-sensitive replacement, deleting text, cutting a block, cleaning Cyrillic and special characters. If several branches fired in a row — say, a block was cut, then a replacement ran — the column keeps the last one's result, not the sum.
The column shows how many price list rows the rule changed. How many rows didn't match isn't shown anywhere.
How to remove words that get in the way of matching
The same window opens from one more place. Open “Product matching settings” — source row menu, “Processing rules” group, or source card, “Additional” section. Then open the matching type: the “Open global word cleanup rules” button is in the type's card, not the list. The window title will be different: “Word cleanup rules for product matching (for all price lists)”.
Don't confuse it with the “Matching types” menu item — that's a different window, a directory of types, and it has no word cleanup button.
This isn't the same set of rules but a separate one.
It's used for product matching: before comparing a name from the price list with a name in your catalog, Elbuz strips from both the words that prevent a match — “pcs”, “original”, “new model”.
How this mode differs:
- there's no “Field” column: the rule applies to whichever column is being compared at the moment;
- the “Delete text” checkbox in the creation form is on from the start — in this mode you almost always need deletion;
- only shared rules are used, and only those with a non-empty “Search”;
- the window has no reference and no “Additional filter” block;
- these rules don't change the price list: they work on temporary comparison data, and the field values themselves stay as they were.
The mode is set when the rule is created and can't be switched later: you can't move an existing rule from the regular set to the word cleanup set — you need to create a new one.
The “Copy” and “Select base catalog categories” buttons aren't on the toolbar in this mode — neither is relevant here: temporary comparison data has no categories.
Scenarios
Four typical store tasks and the rule settings each one needs.
A supplier wraps every name in technical text
What to turn on. Open the window from the source row menu: “Processing rules” group → “Text replacement rules”. Click “Add”, pick the “Name” field, enter the technical text in “Search”, and select “Delete text”. Leave “Replace” empty. Each separate piece of the wrapper is a separate rule.
What you get. On every import of this price list, all occurrences of the text are removed from the names of its rows. Price list rules run after shared ones, so they already work with the name prepared by the shared rules.
What won't happen. The rule won't touch other sources' price lists. Product cards in the catalog won't change until a base catalog update runs.
Different suppliers spell the same brand differently
What to turn on. Open the window from the menu: Directories → Processing price lists → Text replacement rules. The top should say “The settings for all price lists are used.” Add a rule on the “Name” field: “Search” — “Самсунг”, “Replace” — “Samsung”. Keep “Partial match” on, don't select “Case sensitive”.
What you get. In the price list of every source whose list of operations includes “Apply text autocorrect rules”, all occurrences of the word in any case are replaced with your spelling.
What won't happen. The rule doesn't look for word boundaries: if “Самсунг” is inside a longer word, it gets replaced there too. A price list with the replacement operation removed from its list won't be processed by the shared rule.
A supplier description ends with an advertising tail
What to turn on. Create a rule on the description field, then in the grid enter the first words of the tail in the “Block start text” column, leave “Block end text” empty, and clear “Search” — the creation form doesn't accept a rule without search text.
What you get. In rows where the marker occurs, everything from it to the end of the value is cut off together with the marker, and trailing spaces are trimmed. Rows without the marker stay as they were.
What won't happen. If you leave “Search” or “Replace” filled in, the rule won't stop after the cut: a regular replacement runs after it.
An attribute value needs your spelling
What to turn on. “Add” → the “Product attributes” section in the field list → the attribute you need. “Search” — the supplier's spelling, for example “Yes”, “Replace” — yours. In the grid, clear “Partial match”.
What you get. The rule changes only those values of this attribute in price list rows that equal the “Search” text in full.
What won't happen. A value where the same word only appears among other text won't change. A rule on an attribute doesn't touch product names or other attributes' values.
What to do when a rule didn't work
| What you see | Why | What to do |
|---|---|---|
| “Enter the text to search for” | In the new rule form, the “Search” field is empty or contains only spaces | Enter text. If you need a rule without search text — to clean Cyrillic — create any rule and clear “Search” in the grid, keeping “Partial match” on (cleanups) |
| “Select a row!” | You clicked “Delete” without selecting a row in the grid | Select the rule by clicking its row and try again |
| A browser system dialog “Status: … Error: …” | Saving the rule didn't reach the server; the cell edit is rolled back | Reload the window with “Refresh” in the menu and try again. If it keeps happening, contact support |
| Instead of the window — a placeholder image about denied access (in English) | Your group has no access to the “Text replacement rules” window | Ask the owner to grant access to the window in the group's permissions (who has access) |
| The window has no “Add” and “Copy” buttons | The group is restricted by the “Button "Add Rule"” permission block — it hides both buttons at once | Ask for this block to be opened in the group's permissions (who has access) |
| The rule is created, but “Number of items” shows zero | Zero here means “found nothing this time”. There are three reasons: the text didn't match; (“Partial match”) is off and the field doesn't equal the text in full; the replacement operation isn't in the price list's list of operations | Check the rule's checkboxes and the list of operations (what “Number of items” shows) |
| A rule with a regular expression does nothing, with no messages | An error in the expression itself: Elbuz doesn't show it, and the price list import continues | Check the expression; the syntax is PCRE (a pattern instead of exact text) |
| A rule with “Case sensitive” doesn't find the row you need | In this mode, text is matched character by character, case included: “TV” won't find “tv”, and an extra space in “Search” makes the text different | Compare the text with what's in the price list, or clear “Case sensitive” (case sensitive) |
| The rule used to work, but now applies to the whole price list | The rule had a single catalog category selected, and that category was deleted — the link disappeared with it | Select the categories again with “Select base catalog categories” (which products the rule applies to) |
| “Number of items” shows a number that can't be right anymore | The column describes the last price list import, not the current state of the grid: after it, the price list may have been imported again without this operation, or rows may have been edited manually | Import the price list again and check the number after that (what “Number of items” shows) |
| New rules are at the top of the list but run last | The grid sorts by rule number, while execution follows the “Processing order” column | Set “Processing order” explicitly or sort the grid by that column (run order) |
| Names are fixed in the price list but old in the catalog | Rules change price list rows; values get into catalog cards in a separate step | Run a base catalog update (when a rule runs) |
| Two rules on one field give an unexpected result | Rules apply in a cascade: the second sees the result of the first, and the outcome depends on the order | Set “Processing order” for both rules (run order) |
FAQ
I created a rule, but the names are the same. Why?
A rule takes effect from the next price list import. If the price list has already been re-imported, check: whether “Apply text autocorrect rules” is in the price list's list of operations, whether the rule is narrowed by categories, and whether the search text matches what's in the field.
How do I remove a word instead of replacing it?
Select the “Delete text” checkbox and leave “Replace” empty. This is the most common mode.
A rule should apply to all price lists — where do I create it?
Open the window from the menu: Directories → Processing price lists → Text replacement rules. The top should say “The settings for all price lists are used.” — that's the shared set. Shared rules run before the rules of an individual price list.
Can I move the found text to another field?
No, text replacement writes only to the same field it read from. Moving a value — for example, a SKU from the name to the SKU field — is what regular expressions do (comparison).
Can I see the result without importing the price list?
No, this window has no preview. Here's how to check: note a few products in the price list grid, create the rule, import the price list again, and look at the same products.
Can I see who changed a rule and when?
No, the window doesn't keep a change history. For notes on why a rule exists and who created it, use the “Note” column.
Where to find it and who has access
Where you open the window from decides which set of rules you see: the one shared by all price lists or the rules of a single source. The menu opens the shared set — the top of the window says “The settings for all price lists are used.”
- Menu
- Directories → Processing price lists → Text replacement rules
- Shared rules from the list
- “List of price lists” → header menu → “Text replacement rules”
- Rules of one price list
- source row menu → “Processing rules”; or source card → “Additional”
- From a matching type card
- “Open global word cleanup rules” — a separate mode
- Access right
- the “Text replacement rules” window; buttons — the “Add Rule” and “Delete rule” blocks
- Have ready
- an imported price list and the field that contains the extra text
1
Text replacement rules- Text replacement rules — the menu item that opens the rules window (Directories → Processing price lists).
The window has no desktop shortcut. The menu item is third in the “Processing price lists” group — between “Ignore rules” and “Product matching”.
The “Button "Add Rule"” permission block hides both “Add” and “Copy”; “Button "Delete rule"” hides the delete button. Nothing else in the window is restricted by permissions: a manager left with view-only access can still edit values in the grid and set filters.
Access to the menu item is a separate permission entry. The menu item can be hidden while the entry from the price list card still works. There's no separate module switch: the feature is available wherever you work with price lists.
Related topics
- If you need to move a value to another field, such as a SKU from the name — Regular expressions for price lists.
- If a rule is set up but didn't work on a single product — Order of operations during price list import.
- If an item needs to be removed from the price list entirely rather than cleaned — Price list product ignore rules.
- If names are fixed in the price list but old in product cards — Base catalog update.
