On every import, Elbuz runs price list products through a chain of operations: sorting into categories, dropping extras, cleaning up names, finding the brand, catalog matching and pricing. New price lists get them in the right order.
When you need this:
- A markup or ignore rule silently didn’t work — often its operation runs before the one that prepares the data.
- Quantity is calculated by a formula — move formulas above availability detection.
- The supplier mixes Latin and Cyrillic — homoglyph cleanup fixes letters before matching.
- All price lists need one order — “Set for all” copies it.
Where to start: source card → “Additional” → “Order of operations”.
What the operations window does
- Give a new price list the default order — twelve operations are already arranged the way they should run.
- Explain each operation — what it does, where it’s configured, what happens without it.
- Move an operation — drag it with the mouse when your processing logic is different.
- Add or remove an operation — “enabled” here means “in the list”.
- Configure manufacturer search — the window’s only parameter, the minimum word length.
- Copy the order to all price lists — with the “Set for all” button.
The default order is already right. In the vast majority of cases you don’t need to touch this list at all. You change the order not “just in case”, but for a specific task, when your processing logic requires something different.
Why a rule silently didn’t work: the order of operations
Operations are a pipeline. Price list products go through it from start to finish once per import, and each step sees the results of the previous steps, but not the next ones. Operations run strictly one after another, in the order you see in the “Order of operations” window.
An ignore rule “skip the Car care section” won’t work if removal by the ignore list comes before category detection: there are no categories yet, so there’s nothing to filter by.
That’s why a wrong order doesn’t look like an error but like “nothing happened”. Say a markup rule is tied to a manufacturer. The manufacturer is filled in by the “Search for a product manufacturer” operation. If repricing comes before it, the “Manufacturer” field is still empty at that point, the rule’s condition isn’t met, and no markup is applied.
The program doesn’t complain: the rule is valid, the operation ran, it’s just that no product matched it.
Looking for the cause in the rule itself when the problem is the order. If a markup, ignore or replacement rule is set up correctly but didn’t apply to a single product, check whether the operation that fills the field the rule filters products by comes earlier in the operations list.
What ran is written to the import run log, but at the “debug” level — such entries are hidden in the log by default, so to see the operations you need to turn on this level in the log filter.
Why a manual edit disappears after import
During import, products from the file don’t go straight into the catalog but into a temporary copy — this price list’s draft. The whole chain of operations works on it.
Only after the pipeline has finished do the price list’s stop rules decide whether to pass the result on: if a stop rule blocked the run, the draft is discarded along with everything the operations did, and the catalog stays as it was.
That’s why you can experiment with the order of operations: a bad order spoils the result of one import, not your catalog for good. Check a change with a run — just import this price list again and look at the products.
Manual edits to price list products don’t survive the next import. If you fixed a name, price or another cell right in the price list product grid, the edit is saved to this price list’s current product list.
The next import deletes all products of the price list, builds the list again from the file and runs it through the operations. The value you fixed by hand is replaced with what came in the file and came out of the operations.
The previous list, with your edits, stays only if the new import didn’t replace it:
- if a stop rule of the price list blocked the run;
- if not a single product could be read from the file: the log then shows “No data received, previous product list will be displayed”;
- if “Process the price list only if the file has changed” is turned on in the price list card and the file hasn’t changed: when all price lists are imported or on a schedule, the price list is skipped with the message “Price list data has not changed, skipping import”.
- Action or result
- Decision: the path depends on the answer
To make a value stick, set it with a rule rather than a cell edit: in the “Text replacement rules”, “Regular expressions” or “Field formulas” windows. Operations apply the rules on every import, so the result is reproduced every time.
The only thing stored apart from the product list is manual matching — a link between a price list product and a catalog record that you set by hand. During import, it is restored by the “Search for manually matched products” matching type inside the “Matching products from the price list with the products of the base catalog” operation, if that type is enabled in the price list.
If you clear the found-product checkbox in the price list product grid, the manual match is deleted, and the next import won’t restore it.
Default order
There are fourteen operations in the program. A new price list gets twelve of them — in exactly this order:
- Action or result
- Decision: the path depends on the answer
| # | Operation | What appears in the data after it |
|---|---|---|
| 1 | Determine product categories | the supplier category and its full path |
| 2 | Remove products that are on the ignore list | unwanted items disappear from the price list |
| 3 | Distribute products across base catalog categories | your catalog category |
| 4 | Apply text autocorrect rules | cleaned-up names and other text fields |
| 5 | Search for a product manufacturer | a filled-in “Manufacturer” field |
| 6 | Auto-replacement of product values based on regular expressions | values extracted or reworked by a pattern |
| 7 | Create main products for option products | new parent products and the “product — option” link |
| 8 | Determine product availability | a stock status instead of the “stock” value from the file |
| 9 | Matching products from the price list with the products of the base catalog | a link between the price list row and the catalog record |
| 10 | Repricing | the selling price and the saved cost price |
| 11 | Applying formulas to fields | calculated field values |
| 12 | Saving values from fields to attributes | product specifications from the file’s columns |
Two operations aren’t in this set. “Clean up homoglyphs” is added by hand by those who need it. “Matching products from the linked price list with the products of the main price list” is added automatically to a stock price list when you create it and isn’t needed in a regular price list.
What each operation does
The operations are described in the order of the operations directory: the twelve default ones and the two added separately, each in its place. For each operation: what it does, where its rules are configured, what happens if you remove it from the list, and what its position depends on.
Determine product categories
Parses the supplier’s categories: collects them from a file column or from sections of the export, builds them into a tree and assigns each product its category along with its full path.
For files and API sources, a separate branch runs that can build the hierarchy automatically; for other formats, categories are detected by the chosen price list structure type, and for an Excel workbook — separately for each sheet, if the price list is set up that way.
One of the structure types is meant for when the supplier didn’t send categories at all: the category is then detected by keywords in the product name.
Where it’s configured: the “Category detection” window, where you also choose the type of category structure in the file.
Position in the list: first. The supplier category is input for ignore rules, distribution rules, some markup rules and matching types with a “by category” condition. Move this operation lower, and all of them will work on an empty category.
If it’s not in the list: categories from the file aren’t unpacked, and products come in without a category. Everything that reads the category breaks: ignore rules, distribution rules, markup by category, matching with a “by category” condition.
And if the “Show products in Trash that are not assigned to catalog categories” checkbox is cleared in the price list card, such products are also deleted at the end of the import — and nothing is left of the price list.
Remove products that are on the ignore list
Drops from the price list what you don’t sell: individual products, whole supplier categories, items by text in a field. It runs in three passes — first the rules shared by all price lists, then the rules for individual Excel sheets, then the rules of this price list.
The number of removed items is written to the import log and to the run history. If the ignore log is turned on for the price list, each removal is recorded separately, and the previous record is cleared before the run.
Where it’s configured: the “Ignore rules” window.
Position in the list: after category detection, because rules can filter products by supplier category. Move the operation higher, and such rules stop working. Move it lower, and the junk will go through text replacement, manufacturer search and repricing, so the program does extra work, though the junk is removed in the end anyway.
If it’s not in the list: all of the supplier’s items reach the catalog, including sections you don’t sell. The ignore list stays configured — nobody applies it.
Clean up homoglyphs (Latin ↔ Cyrillic look-alikes) in name, SKU and manufacturer
In supplier price lists, letters such as A, B, C, E, O and P are often typed in Latin in one place and in Cyrillic in another. They look the same, but to the program they are different characters: the SKU «EBS-501Р» with a Cyrillic “P” won’t match the same SKU in Latin, and the product is duplicated in the catalog. The operation fixes such substitutions in the name, SKU and manufacturer.
Where it’s configured: nowhere. It has no rules or parameters — it’s either in the list or it isn’t.
It is deliberately left out of the default set. Here’s why.
Not every supplier needs it — many price lists have no substitutions at all. It changes product names, which can break matches you’ve already made. And it appeared later, when many users already had their price lists set up, so it wasn’t forced on existing imports. The user chooses when to apply it — it’s a choice with consequences, not a forgotten switch.
Position in the list: above manufacturer search and above catalog matching. The fixed letters are needed exactly at matching time; after it, cleanup can’t save anything — pairs weren’t found, duplicates were created.
Rearranging operations by hand, then adding homoglyph cleanup and not checking its position.
“Add an operation” puts the cleanup not at the end but in its default place — right after the operations that come earlier in the default order, that is, above manufacturer search and matching.
But if you moved matching to the top, the cleanup may end up below it. Then drag it above “Matching products from the price list with the products of the base catalog” — placed lower, it fixes the letters after matching has already failed to find a pair.
If it’s not in the list: products with substituted letters won’t match the catalog and will create duplicates, and brand filters and search will work only partly.
Distribute products across base catalog categories
Maps supplier categories to yours: the “Small appliances / Kettles” section becomes the “Kettles” category of your catalog. It runs twice — this price list’s rules and the rules shared by all price lists. This is the operation that assigns the catalog category to a product.
Where it’s configured: the “Distribution rules” window.
Position in the list: after category detection, because the rules read the supplier category, and before the steps that filter products by catalog category — above all, repricing and matching with a “by category” condition.
If it’s not in the list: products keep the supplier category but get no catalog category, and markup rules and “by category” matching won’t find anything to attach to. And if the “Show products in Trash that are not assigned to catalog categories” checkbox is cleared in the price list card, undistributed products are deleted at the end of the import.
Apply text autocorrect rules
Runs product text fields through your replacement rules: remove “SALE!!!” from names, replace “used” with “discounted”, strip the supplier’s phone number from descriptions, bring different spellings of a brand to one. Rules shared by all price lists are applied first, then this price list’s rules.
Where it’s configured: the “Text replacement rules” window.
Position in the list: before manufacturer search. If a rule changes «Самсунг» to “Samsung”, manufacturer search after it finds the brand in the name; move the replacement lower, and the brand won’t be detected, while the fixed name won’t help anyone in this run. Replacement affects catalog matching the same way: it compares the value that’s in the field at matching time.
If it’s not in the list: names go to the catalog as they are. It’s not just how the record looks — manufacturer search and catalog matching work on these same fields.
Search for a product manufacturer
Fills in the “Manufacturer” field. First it fills an empty field from product attributes named “Brand”, “Manufacturer” or “Vendor”, or their Ukrainian and Russian equivalents («Бренд», «Виробник», «Марка», «Торгова марка», «Производитель», «Торговая марка»; case doesn’t matter), if such attributes are already loaded.
Then it sets the manufacturer by an exact name match with your manufacturer directory, then looks for brands in the words of the name and by synonyms, and passes the found brand up to parent products.
Only active manufacturers take part in the search: if a brand is disabled in the directory, price list products with that name are left without a manufacturer.
If the general setting for adding new manufacturers is on, unknown brands from the current import get into the directory on their own, and price list products are linked to them right away.
Its own parameters. This is the only operation that has its own setting in this window — the “Min. characters” field in the right panel. It sets the length of words that are checked for similarity to a brand at all. The default is 3; if you enter zero, the program still uses 3.
1
Min. characters2
Operation guide- Min. characters — words shorter than this length are ignored when searching for a brand in the name.
- Operation guide — the description changes when another operation is selected.
Position in the list: above repricing if you have markup rules for specific brands, and above catalog matching if a matching type has a “by manufacturer” condition: with an empty field, such a condition finds nothing. The flip side is worth knowing too — catalog matching itself fills in the manufacturer from the found product, but only for products where the field is empty.
If it’s not in the list: the brand is no longer picked out of the name, and for most price lists that’s the main way to get it.
Products whose manufacturer came in a separate file column stay filled in: at the end of the import, the program goes through products without a manufacturer once more and matches the whole field value with the manufacturer directory and its synonyms.
Catalog matching will also fill in the brand for some products. For the rest, the field stays empty, and with it markup rules by brand, regular expression rules with a manufacturer filter, “by manufacturer” matching types, store brand filters and exports to marketplaces that require a brand all stop working.
Auto-replacement of product values based on regular expressions
The same as text replacement, but by pattern — for cases a simple “find and replace” can’t describe: remove all sizes in brackets from names, extract the volume into a separate field, build an SKU from part of a string.
The price list’s rules are applied in order, one after another. In a rule you can set a default value for when the result is empty, replace only empty fields, and limit the rule to a manufacturer or category.
Where it’s configured: the “Regular expressions” window.
Position in the list: after manufacturer search, because a rule can be limited to a manufacturer, and after category detection if it’s limited to a category. Move it higher, and the filters in the rules stop selecting products, so the rule either doesn’t work or works in the wrong place.
If it’s not in the list: fields stay as they are in the file. Rules from the “Text replacement rules” window don’t replace this — they use a different mechanism and have their own operation.
Create main products for option products
Needed when the supplier sends each variant as a separate row: a T-shirt in S, M, L is three items. The operation splits rows by the value separator, marks the variants as options, creates a shared parent product for them and links them to it. The customer sees one product page with a size choice, not three identical products.
Where it’s configured: the value separator is set in the price list column addresses; there too, in the price list settings, you turn on adding the option name and value to the product name and copying attributes between the main product and its options.
Position in the list: this operation creates new product rows. Everything after it sees both parents and options; everything before it sees only the original file rows. That’s why it comes before availability detection, matching and repricing: otherwise the created parent products would be left with no stock status, no catalog link and no selling price.
If it’s not in the list: each variant stays a separate product, and no parent records are created.
Determine product availability
Turns the “stock” values from the supplier’s file into your stock statuses: “>10” or “plenty” becomes “In stock”, “0” becomes “Out of stock”, “expected” becomes “Pre-order”.
Where it’s configured: the “Availability” section in the price list card.
Position in the list: after creating option products, so parent products get a status too. If your quantity is calculated by a formula, availability must come after the formulas — and by default formulas come after it, so this is the case where you have to change the order by hand.
If it’s not in the list: stock values from the file aren’t turned into statuses. The product isn’t left with no status at all, though: at the end of the import, every product without a status gets “In stock”. So a removed operation results not in an empty field but in a store that takes orders for things it doesn’t have.
Matching products from the price list with the products of the base catalog
Looks for each price list product in your catalog and links the pairs it finds. Thanks to the link, the next import updates the price and availability of the existing record instead of creating a new one.
Inside, the operation runs the matching types set up for this price list — one after another, in their own order. The order of matching types is a separate queue inside one operation, configured in the “Product matching settings” window; matching types themselves are a separate topic. The operations pipeline only decides when this queue starts.
What it writes to the price list product: the link to the catalog product and a mark of which matching type found the pair. Two more things, conditionally: the catalog category, if the product didn’t have one and automatic category detection from the found product is on, and the manufacturer, if the field was empty.
Position in the list: after all the operations that put the fields in order. Matching type conditions read the fields that earlier operations fill in: “by manufacturer” reads the “Manufacturer” field, “by category” the catalog category, “by contact” and “by warehouse” the corresponding product fields.
An empty field means such a condition finds nothing. That’s why, by default, categories, junk removal, text replacement, manufacturer search, regular expressions, option products and availability all finish before matching.
Removing this operation from the list is the costliest decision in this window. Without it, price list products won’t link to the catalog, and each update will create new records instead of updating existing ones. You’ll then have to clean up the duplicates by hand.
Repricing
Calculates selling prices from cost prices by your markup rules: “cost up to UAH 1,000 — 30% markup, from UAH 1,000 to 5,000 — 20%”. Rules are selected by product category — including subcategories, if the rule says so — and by manufacturer. A separate price list setting decides whether to take into account rules shared by all price lists.
Before calculating, the operation saves the supplier’s original prices and records the product’s cost price. For parsers that don’t delete products, markup is applied only to new items — items repriced earlier stay as they are.
Where it’s configured: the “Markup types” window.
Position in the list: after categories, manufacturer search and matching — otherwise “markup for category X” or “for brand Y” rules won’t find anything to attach to. Relative to formulas, the order matters both ways, and there’s no right answer: formulas before markup change the input price it’s calculated from, formulas after markup override the calculated price. By default, markup comes first.
If it’s not in the list: products keep the supplier’s prices. A less obvious consequence: the cost price isn’t filled in either — it’s set inside this operation and then carried over to the catalog product.
Applying formulas to fields
Calculates field values by your formulas: recommended price = cost × 1.4, a name built from brand, model and volume, conversion of units of measure. It runs in several passes — this price list’s formulas, formulas per Excel sheet if the price list is set up by sheets, and formulas shared by all price lists.
Where it’s configured: the “Field formulas” window.
Position in the list: a formula can write to any field, so its position determines who sees the result. A formula that builds a name from brand and model works after manufacturer search but not before it: the brand is still empty. A formula that calculates a price is marked up by repricing if it runs before it, and overrides it if it runs after.
If it’s not in the list: calculated fields stay empty or keep the original values from the file. This is most noticeable where the needed value isn’t in the file at all.
Matching products from the linked price list with the products of the main price list
An operation for a pair of “main price list + a separate stock or price file” from the same supplier. It finds the same products in both files, links them and carries values from the linked file over to the main price list products.
Before carrying values over, it removes previous links, and if needed, after carrying them over it sets “Out of stock” for main price list products that weren’t in the stock file.
It does this only if at least one product found a pair: when the stock file is empty or broken, the main price list’s availability stays as it was. If the stock price list card has the “Only keep items found in the main price list in the secondary price list” checkbox selected, rows without a pair are deleted from it.
Where it’s configured: which values to carry over to the main price list is set by the “Copy value to main price list” checkbox in the stock price list column addresses; the rest of the behavior — by checkboxes in the card of the same price list.
Position in the list: in a stock price list — after “Determine product availability” and “Repricing”, so your status and the repriced price go to the main price list. By then the main price list is already imported and doesn’t recalculate the carried-over values, so stock price lists are imported after the main ones.
If it’s not in the list of a stock price list: the file is imported, but its data goes nowhere, and the main price list keeps old prices and availability. In a regular price list without a linked file, the operation does nothing — it finishes right away.
Saving values from fields to attributes
Carries values from file columns over to product specifications: the “Color”, “Volume” and “Material” columns become record attributes and get into store filters. The operation creates attributes, then matches them with your directory in four passes — by name with the main synonym, by name, by code with the synonym, by code.
Where it’s configured: which columns to carry over is set by the “Product attribute” and “Product option” checkboxes in the price list column addresses. The operation itself has no parameters.
Position in the list: last by default. If the brand comes in a column marked “Product attribute” and the column is named, say, “Brand” or “Manufacturer”, move the operation above “Search for a product manufacturer”: the attribute appears earlier, and manufacturer search moves the brand into the “Manufacturer” field of products where it’s empty.
If the brand is a separate column in the price list, assign that column to the “Manufacturer” field in the column mapping wizard — then it gets into the product right away, without operations.
If it’s not in the list: specifications from file columns won’t become product attributes and won’t get into store filters. Three more things that live in this same operation, though they have nothing to do with attributes, stop working too: linking options to the parent product, copying attributes between the main product and its options, and adding the option value to the name.
When and how to change the order
You change the order when your processing logic differs from the default one. Here are the cases when a rearrangement is really needed.
- The brand is in a separate column, not in the name. Move “Saving values from fields to attributes” above “Search for a product manufacturer” — then the manufacturer is taken from the attribute.
- Product quantity is calculated by a formula. Move “Applying formulas to fields” above “Determine product availability”, otherwise availability is calculated from the original value in the file.
- The price is set by a formula, not by markup. Then formulas must come after “Repricing” to override its result. If, on the contrary, markup should be calculated from the computed price, put formulas higher. There’s no right answer here: it depends on what counts as the input price for you.
- You added homoglyph cleanup after rearranging by hand. It takes its default place relative to the operations already in the list, but if you moved catalog matching higher, check that the cleanup is above it and drag it if needed.
To change the order, drag a row up or down with the mouse — the new sequence is saved right away. There’s no “apply” button here, and no button to reset to the default order either, so remember what the list looked like before rearranging.
The order isn’t checked for sense: the program lets you put repricing first and category detection last, and silently runs them that way.
Check a change by importing the price list: the order is taken from the list when the import starts.
Before you change the order
How to copy the order to all price lists
This button copies the order of operations from the current price list to all other price lists. Its tooltip says exactly that: “Set this order of applying operations for all price lists”.
What to know before you click:
- the button affects all price lists of all suppliers in your database, not just the price lists of the current contact;
- before the change, it shows how many price lists will be affected and asks for confirmation; once you agree, the order changes right away, and the message “Updated” appears on screen;
- it can’t be undone in one step: the previous order isn’t saved anywhere.
The button doesn’t change what’s in the lists. It copies only the order: operations that another price list doesn’t have won’t appear there, and extra ones won’t disappear. So it makes sense to click it when you changed the order for a rule common to all suppliers — and doesn’t when you set up a specific price list for a specific supplier.
Special cases
Stock price list. When you create a stock price list for an existing source, it gets a different set of operations: matching with the linked price list is added, while catalog matching and category detection are removed. A stock file has no assortment of its own; it only passes its data to the main price list.
“Repricing” stays in a stock price list, before “Matching products from the linked price list with the products of the main price list”: the main price list doesn’t reprice the carried-over price, so only the stock price list’s own repricing applies the column’s exchange rate and markup. Stock price lists created before October 31, 2026 lack this operation — if the stock file has prices, add it before linked matching, with markup types (stock price list). If the file has only availability, repricing can be removed.
for articles. For sources that collect articles rather than products, the program runs only five operations: removal by the ignore list, text replacement, regular expressions, formulas and category detection. The rest are ignored, and their order doesn’t matter.
Empty price list. If the file has no products, the pipeline doesn’t start at all — there’s nothing to run it on.
Stopping an import. If you stop an import by hand, the pipeline is interrupted at the nearest boundary between operations: the program checks the stop flag before each operation, so what has already run stays in the draft, and the remaining operations don’t run.
Steps outside the list. After the pipeline, the import runs steps that aren’t in the list and can’t be rearranged:
- linking stores and warehouses, updating units of measure;
- setting the manufacturer by its name once more;
- deleting products outside the set price range;
- deleting products not distributed across catalog categories, if the “Show products in Trash that are not assigned to catalog categories” checkbox is cleared in the price list card;
- carrying over values from the stock price list, the “In stock” status for products without a status;
- counting products in categories and checking threshold deviations, after which stop rules decide the fate of the whole run.
Price list copy. When you copy a source, the operations list is copied with it — along with your order.
Attributes and manufacturers in directories. The “Saving values from fields to attributes” operation doesn’t add new attributes to the directory: it only links price list product specifications to attributes already in the directory, by name or code.
New attributes appear in the directory during a base catalog update, when specifications are carried over to product records. The program adds a manufacturer to the directory right away if you type a name that isn’t in the directory in the price list product grid.
You can delete such entries from directories, but the consequences go beyond the directory. Deleting a manufacturer clears the “Manufacturer” field in all catalog records with that manufacturer, removes the link to it in price list products, and deletes its synonyms, markup rules tied to it and its page URL on the website.
Deleting an attribute erases its values in all catalog products and removes rows tied to it from price list column addresses.
Large price lists. There’s no limit on the number of rows in the pipeline: operations process the whole price list. The log shows how long an import took: it ends with the line “Data loading completed!” with the number of products and the “Time spent”.
When all price lists are imported in turn, the program waits for each file source for no more than 2 hours. If it doesn’t get a response in time, it writes “The source did not respond within 2 h — its import was aborted, the run continues with the next source” to the log and moves on to the next source.
This limit doesn’t apply to parsers. You can’t start an import of the same price list a second time while the first is still running: the program replies “This source is already being imported (started at …)”.
Scenarios
A separate markup for one brand
Task: sell one brand’s products with a different markup than the rest of the price list.
What to set up: in the “Markup types” window — a rule with the manufacturer selected, in a markup type that takes manufacturers into account. In the operations list, “Search for a product manufacturer” must be above “Repricing”; in the default order it is.
What you get: the rule selects products by manufacturer, so the markup applies to the products that manufacturer search assigned a brand from your directory.
Products whose brand wasn’t found, or whose name isn’t in the manufacturer directory, won’t fall under this rule. If you move repricing above manufacturer search, products that don’t have a brand at that point won’t fall under the rule, and the program won’t tell you.
The supplier mixes Latin and Cyrillic letters
Task: in the price list, SKUs and names are typed in Latin letters in some places and Cyrillic in others, and products don’t find a pair in the catalog.
What to set up: the “Add an operation” button → “Clean up homoglyphs (Latin ↔ Cyrillic look-alikes) in name, SKU and manufacturer”; it takes its place above “Matching products from the price list with the products of the base catalog” on its own. You only need to drag it if you moved matching higher earlier.
What you get: before catalog matching, substituted letters are fixed in three fields — name, SKU and manufacturer. The operation doesn’t touch other product fields, and units of measure such as «2400Вт» or «12В» stay as they are. The operation has no rules or parameters: it works while it’s in the list.
Availability is derived by a formula
Task: the supplier doesn’t provide a separate availability column, and the status has to be derived from other file columns.
What to set up: in the “Field formulas” window — a formula that fills the availability field. In the operations list, drag “Applying formulas to fields” above “Determine product availability”, and set the conversion rules in the “Availability” section of the price list card.
What you get: availability detection sees the value the formula wrote and turns it into your status. If you leave the formulas lower, while the column addresses have no availability column and the availability rules don’t take the value from another field, availability detection gives all products a status marked “in stock” before the formula calculates anything. This fallback doesn’t apply to XML price lists.
Fixes that don’t disappear after an update
Task: the supplier always sends a name or another field not in the form you need.
What to set up: a rule in the “Text replacement rules”, “Regular expressions” or “Field formulas” window — and the matching operation in the price list’s operations list.
What you get: the rule is applied on every import, so the fixed value comes back after every update. A cell edit in the price list product grid doesn’t work that way: the next import builds the product list again from the file, and the edit disappears — except in the three cases from the diagram in “Why a manual edit disappears after import”.
FAQ
How do I disable an operation?
There’s no switch: in this window, “enabled” means “in the list”. To stop an operation from running, select it and click “Delete”. To bring it back, use “Add an operation”.
When does a changed order take effect?
From the next import of this price list: the order is taken from the list when the import starts. There’s no “run operations now” button in the window.
Should formulas go before or after markup?
There’s no right answer; it depends on the task. A formula before markup changes the input price the markup is calculated from; a formula after markup overrides the calculated price. By default, repricing comes before formulas.
Does “Set for all” change the set of operations in other price lists?
No, it copies only the order: operations another price list doesn’t have aren’t added, and extra ones aren’t deleted. But the button affects all price lists of all suppliers in the database — before applying, it tells you how many and asks for confirmation.
I added an operation, but nothing changed. Why?
Check where it is in the list. An operation placed before the one that prepares its data runs idle and doesn’t tell you: there’s no error, and the log reports that it ran.
Can I add the same operation twice?
No. Each operation can appear in a price list at most once, so the “Add an operation” menu doesn’t show the ones already added.
Does each price list have its own order, or is there one for all?
Each has its own: the window configures the price list you opened it from. There’s no shared template — only the “Set for all” button, which copies the current order to other price lists.
Where to find it and who has access
This window has no menu item: it opens from the price list card or from the list of price lists and configures the price list you opened it from.
- From the source card
- “Additional” section → “Order of operations” button
- From the list of price lists
- header menu → “Processing rules” group → “Order of operations”
- Access right
- the “Order of operations” window in group permissions
- You need
- a price list source that is already set up
1
Order of operations- Order of operations — opens the list of operations for this particular source.
There is no shared operations list for all price lists: each source has its own.
1
Processing rules2
Order of operations- Processing rules — the group that collects the windows with price processing rules.
- Order of operations — the second way to open the same window.
Below the buttons is a hint line: “List of applied operations: To change the order in which an operation is applied, drag it up or down with the mouse.”
Below that, the window is split in two. On the left are the operations that run for this price list, top to bottom in the order they run.
On the right is “Operation guide”: select a row on the left, and the description of that operation appears here. Until you select one, the panel shows “Select an operation in the list on the left — its description and parameters will appear here.”
1
Operation list2
Operation guide3
Add an operation4
Set for all5
Delete6
Drag hint- Operations run top to bottom in this order; rows can be dragged with the mouse.
- The panel on the right describes the selected operation.
- Adds an operation that is not yet in the list.
- Applies this order to every price list — the only action of the window that goes beyond this price list.
- Removes the operation from the list, which switches it off.
- The hint icon: to change the order, drag an operation up or down with the mouse.
The header has the “Add an operation” button (a menu of operations this price list doesn’t have yet), the “Set for all” button and the “Delete” icon button, which removes the selected operation from the list. To their right is the “Help” icon: it opens this article.
1
Missing operations2
Homoglyph cleanup- Only operations that are not in the list yet are offered here.
- Clean up homoglyphs (Latin and Cyrillic look-alikes) in name, SKU and manufacturer — the operation added by hand most often.
In this window, “enabled” means “in the list”. There is no on/off switch here, and none is planned: to make an operation run, add it; to stop it, delete it. Deleting from the list doesn’t touch your rules: the ignore list, formulas and markup types stay in place — nobody applies them during import.
Related topics
- If supplier names need cleaning up or a brand needs a single spelling — Text replacement rules.
- If a value needs to be extracted from the name into a separate field — Regular expressions for a price list.
- If an import stopped and the draft was discarded — How to keep supplier price list errors off your website.
- If the price list doesn’t import yet — How to upload a supplier price list to Elbuz.
- If you’re deciding whether to hand price lists over to the program — what it gives your store.
