Elbuz fills a product field by a rule you set once: calculates the price, builds the name, copies a value into an attribute — catalog-wide or for a filtered part.
When you need this:
- Products arrive without your SKU — a counter gives each new one the next number.
- A site filter needs an attribute — a formula fills it from a card field.
- The price must not exceed the RRP — a formula fixes it in every price list update.
- A formula got broken — the change history restores its previous text.
Where to start: “Products” → toolbar menu → “Set up formulas for fields” → “Add formula”.
What catalog field formulas can do
- One formula — one target field: price, name, SKU, barcode or attribute.
- They run on their own in updates from price lists, when a card is saved and a product is added, or manually with a button.
- They take values from product fields, its attributes and matched price list rows.
- A counter and a barcode generator issue new numbers and EAN-13 codes.
- An apply condition limits a formula to a category, a manufacturer or an empty field.
- The change history brings back a previous version of a formula and deleted formulas.
The app has two different sets of formulas, and mixing them up is costly. Price list formulas work with the supplier's price list rows — with what the contact sent. Catalog formulas, covered in this article, work with your product cards: with what's already in the base catalog and will go to the site.
How to build a formula in the window
The window is split in two. On the left is the list of formulas, one row each. On the right is the editor for the selected one: clicking a row redraws the right panel. While nothing is selected, the editor shows three hint steps — what to click to create your first formula.
Above both panels is a row of buttons: “Add formula” (opens a search across catalog fields, where you can also create a new field), “Apply formulas”, the AI assistant's magic wand, a trash can for the selected row, the formula change history button, list refresh and the “Help” link.
The list on the left
The list holds what you search formulas by and what you manage in bulk:
| List column | What it sets |
|---|---|
| “Field name” | the target field: where the result is written. It also serves as the formula's name |
| “Note” | a note for yourself: what this formula is for. Six months from now you'll thank yourself |
| “Sort order” | sequence: a formula with a lower number runs earlier |
| “Active” | a disabled formula doesn't run at all |
| “Read-only” | the full caption is longer: “do not replace value when parsing”. A field filled by a formula won't be overwritten by what comes from the supplier's site |
| “Apply when importing the catalog from external sources” | also run the formula when the catalog comes from outside — through a marketplace or a tunnel |
| “Language” | the language the rule is written for; next to it is a button to change it |
Edit values in these columns by double-clicking the row. Drag the strip between the panels to resize the list; the columns scroll, so a narrow window shows only “Field name” and “Note”. The expression itself isn't in the list: the formula lives on the right.
The editor on the right
At the top: the selected field's name and the “Active” switch, same as in the list. Then the “Fields for formulas”, “Apply this formula” and “Change history” buttons and the expression field with syntax highlighting. Below it: two switches (“Read-only” and “Apply when importing the catalog from external sources”), “Note” and the collapsed “Apply condition (optional)” block.
There's no “Save” button here, and you don't need one: changes go to the database on their own, and “Saved” with the time flashes next to the title.
Don't type fields into a formula by hand — a macro typed from memory is the most common cause of errors.
“Fields for formulas” opens a searchable list (“Field”, “Group”, “Macro”, “Code”): a click shows the field description, a double-click inserts the macro at the cursor. Ctrl+Space in the editor does the same. The hint under the field: “Double-click a field in the right panel to insert its macro at the cursor; Ctrl+Space for autocomplete.”
Three groups of sources are available: catalog fields ({Product: …}), price list fields ({Price list: …}) and contact fields. So a catalog formula can reach into a price list — but only for matched products, just as in the other direction.
The formula takes the {Price list: …} value from the price list row the product is currently linked to. If that row is no longer in the price lists, the field's old value is not kept: the formula still writes the result, only an empty one. A numeric field becomes 0, a text field becomes empty.
For example, {Price list: Price} * 1.2 in the “Price” field gives zero for every product that dropped out of the price list. To keep the previous value in that case, wrap the expression in IFNULL: IFNULL({Price list: Price} * 1.2, {Product: Price}).
When a formula runs
There are several run points, and the difference between them is the main thing to learn.
- Manually. The “Apply formulas” button above the list runs all active formulas. The “Apply this formula” button in the editor does the same for the one selected formula — that's how you test a new formula without touching the rest.
- During the batch update from price lists. If “Apply formulas” is checked on the “Settings” tab, they run in the same pass that updates the catalog from suppliers.
- When the catalog is imported from outside. Only for formulas with the “Apply when importing the catalog from external sources” checkbox.
- When a product card is saved. If “Apply formulas when editing” is turned on in the catalog settings, formulas are recalculated for that product every time you save the card. If “Formulas for attributes only” is turned on next to it, only attribute formulas run, and other fields aren't touched.
- When a product is added. When a product is added to the catalog (for example, through the API), formulas run for it right away.
Before each run, the app silently checks the formula and doesn't run a broken one: the others still run, and for skipped ones you get the “Formula errors” window listing fields and rule IDs. Its “Ask the AI assistant” button sends the expressions to the assistant to explain what's wrong.
A formula overwrites the field rather than adding to it. If the target had a value typed in by hand, it will be gone after the run.
Formulas have no “apply once” protection: the expression {Product: Price} * 1.1 written to the “Price” field raises the price by ten percent on every run. Run a formula that reads and writes the same field once and check the result — don't press the button “just in case”.
The order within a run is set by the “Sort order” column. This matters when one formula uses the result of another: for a built name to reach the formula that calculates something further from it, the first formula needs a lower order.
What happens after “Apply formulas”
The button sends one request and waits for the response: the recalculation isn't queued in the background. Meanwhile “Apply formulas” is disabled, a spinner turns next to it and “Recalculating...” stays at the bottom. The code has no product limit: the formula runs for all products that pass its apply condition.
The app takes the active formulas one by one by the “Sort order” column and makes one database write for each — for all filtered products at once. After all formulas, it updates the product fields the catalog grid reads from and clears the saved copies of the cards.
- Start or end
- Action or result
- Decision: the path depends on the answer
How to make sure the recalculation happened
- If all formulas ran, the “Formulas applied” message appears. The app doesn't show how many products were recalculated, and a manual run from the formulas window isn't written to the operation log.
- If some formulas have errors, the “Formula errors” window opens instead of that message. The other formulas have already been written by then.
- An open base catalog grid refreshes on its own. Look at the target field and at the “Exported” column: for every product the formula reached, this flag is cleared — even if the new value matches the old one. For products the formula didn't touch, the flag stays as it was.
- If the request failed with a server error or the response couldn't be read, a red “Formulas were not applied: the server did not respond or returned an error” message appears. Click the button again; if the message repeats, check the operation log.
When the new values reach the site
A formula changes only base catalog cards and sends nothing to the site or marketplace: new values go out with the next export. The cleared “Exported” flag marks products for an export with “Only export new data” — it takes only products without this flag. With the option off, the export takes its whole filtered set, recalculated or not.
If the recalculation was interrupted
Formulas are written one at a time: the next one starts once the previous one is written. An interruption midway leaves the formulas earlier in the “Sort order” done and the rest not done.
Clicking “Apply formulas” again runs all active formulas from the start. A formula that takes values from other fields is safe: same result. A formula that reads and writes the same field applies a second time. If one like that ran before the interruption, skip it and run the rest one by one with “Apply this formula”.
Bulk changes: what happens if a run is interrupted and how to undo it
Products change in bulk in three ways: “Updating base catalog” from price lists, “Set value in bulk” and “Find and replace” in the catalog grid, and the “Apply formulas” button. None is all-or-nothing: each writes changes in parts, and an interruption leaves exactly what was already written. Undo differs for each, so they are covered separately below.
Which products the operation affects
- “Set value in bulk”: if products in the catalog grid are selected with checkboxes, the value is written to all selected products, not only to those visible on the current page. If nothing is selected, only the row under the cursor changes.
- Your selection is kept until you clear it. A product you selected earlier and then hid with a filter or left on another page is still affected by the operation. The “select all” button selects everything in the grid's current filtered set: the category, column filters and the search box, and it clears the previous selection.
- “Find and replace”: if nothing is selected, the replacement runs across the whole selected category with its subcategories, and if the tree root is selected, across the whole catalog. Column filters and grid search do not narrow this scope. So if search or a filter is active in the grid and no rows are selected, the replace dialog does not open. Instead, a red message appears: “A search or filter is active in the grid but no rows are selected: the replacement would apply to the whole category, not to the visible products. Select the rows you need (“Select all” respects the filter) and try again.” Without search or filters, the program asks you to confirm a category-wide replacement with a separate checkbox.
- “Updating base catalog” ignores selections in the price list grid. It processes the whole selected price list or all price lists at once. You can narrow it only with conditions on the “Additional” tab of the update settings.
The program has no limit on the number of products in one operation.
How to undo a bulk change in the catalog grid
After “Set value in bulk” and “Find and replace”, a “N products changed” message with an “Undo” button appears at the bottom for 15 seconds. You can also do this later: the clock button in the catalog window opens the “Recent actions” list, and you can undo any operation from it.
- If someone has already changed the field in a product after your operation, undo leaves that product alone. The message shows how many such products were skipped: “(N skipped — changed since)”.
- If the operation changed nothing (all products already had that value), there is nothing to undo, and no button appears.
- The program keeps only your last five bulk operations, and none older than one day. A sixth operation pushes out the oldest undo, and operations older than 24 hours disappear from the list.
- No undo is recorded when “Set value in bulk” changes only the row under the cursor (nothing selected), when a price is set as a markup rather than a number, or when the “Images” column is cleared. Clearing images deletes product photos together with their files, and they cannot be restored.
Updating base catalog: interruption and rerun
The update runs in stages: prices and product fields, adding new products, stock and status, profit, photos and others. Each stage is written to the catalog right away, separately from the next ones. There is no single undo for the whole run.
- If you click “Stop”, the run stops at the nearest point between stages, not in the middle of one: a stage that has already started runs to the end. The log shows “Import interrupted by the user!”. What earlier stages managed to write stays in the catalog.
- If the run breaks off on its own (server failure, error), what was written before that also stays. There is no completion message in the log then: the last line is the stage where everything stopped.
- If you start an update while the previous one is still running, the second start is rejected with the message “Batch processing is already running in another process — this run was rejected”. While a run is in progress, it refreshes its lock between stages, so a second start cannot take it over. When a run finishes, including a crash on an error, the lock is released at once, and you can start a new run without waiting. Only if the process on the server was killed or the server restarted does the lock remain. New starts are then rejected until two hours have passed since the interrupted run started or since the last stage it completed.
- If a scheduled price list import is in progress, a manual update start is rejected with the message “Scheduled price list import is in progress — catalog update start was rejected”.
- A rerun recalculates products from price list data with the same settings. It does not restore what the interrupted run already erased. If a field in the update settings has “Clear catalog field before updating” checked, that field is erased at the prices and product fields stage, right before new values from the price list are written, and only when “Update products” is on. It is erased only in products matched to the price list being updated (all catalog products when updating from all price lists), subject to the conditions on the “Additional” tab. Products marked “Do not update” are not cleared, and products with “Fixed Price” keep their price fields. The field stays empty in every product the run does not write a new value to after clearing. This happens if the run breaks off between clearing and writing, if a product is in none of the price lists when updating from all of them, if the price list row fails the write conditions for that field (empty cell, logical condition), or if the field mapping row itself is disabled but its clear checkbox is left on.
If “Days a product stays current; after that it is deleted” is filled in the update settings, products missing from price lists for that many days are permanently deleted from the catalog. There is no undo for this, and the change log will not bring them back either.
Applying formulas
The “Apply formulas” button recalculates fields using all active formulas, each one separately. If a formula has an error, the program skips it, runs the rest, and then shows a list of formulas that failed. This operation has no undo button: to restore values, fix the formula and apply it again.
What the log shows and how to find what changed
- “Operation log” shows the update's progress by stage: how many products were updated, how many were added, when the operation was interrupted. It does not list product names. Log lines are kept for 14 days, and operation summary cards for 90 days.
- To see which products changed and what value they had before, use the “Operation history” tab, but only if the “Value change history” setting is on. If it is off, the catalog update records no details at all.
- For a catalog update, history is recorded only when the run reaches the end. A run stopped with the “Stop” button or broken off by a failure does not appear in history.
- In “Operation history”, previous field values are restored one product at a time, with the button in the row. There is no bulk restore there. History records are kept for 7 days.
How to insert a product, attribute or price list field into a formula
A formula expression is written in , not Excel. The functions, conditions and limits are the same as in price list field formulas: what you can write in a formula, “if … then …” conditions and ready-made formulas for price and text.
Specific to the catalog are macros. A field is the group name and field name in curly braces, exactly as in the “Fields for formulas” list. {Product: Name} works, as does the same macro in another interface language (e.g. Russian), but {Product: Title} doesn't: there's no such field, and the formula lands in the “Formula errors” window.
| Macro group | Example | Where the value comes from |
|---|---|---|
| Product | {Product: Cost price} | a product card field |
| Catalog attribute | {Catalog attribute: Color} | the product's attribute value in the language the formula runs for; after the colon — the exact attribute name from the reference list |
| Price list | {Price list: Price} | the price list row the product is currently supplied from |
| Blocks in double brackets | [[FromGroupContractor_2 MIN({Price list: Price})]] | values from other contacts' price lists, warehouses, the main product, a set |
Attribute macros usually aren't in the “Fields for formulas” list. Type the remaining {Catalog attribute: …} macros by hand, copying the attribute name from the attribute reference list. Field suggestions in the editor — Ctrl+Space.
Language matters
A formula is tied to a language. Text fields — name, descriptions, meta tags — are separate for each language, so each needs its own formula. Write a rule for Ukrainian, and the English version of the field stays as it was.
Numeric fields — prices, dimensions, quantity — don't depend on the language, so for them it doesn't matter.
Ready-made catalog formulas
Here are tasks that only catalog formulas can solve. General recipes for price, text and conditions are in the formula library.
Internal SKU as a counter
You need this when products arrive without their own code but you need your own running number. There's a separate block for this that doesn't look like other expressions:
[[max_add_1{Product: SKU (internal)}]]
The app finds the largest number across the whole catalog in the given field and gives each product the next one. Non-digit characters are ignored when finding the maximum, so prefixes like ART- don't throw the counter off. The block also has two synonyms, Russian and Ukrainian; write any of them.
Limit this formula with an apply condition “field is empty”. Otherwise every run renumbers the whole catalog, and the SKUs you've already sent to marketplaces will change.
EAN-13 barcode
The {GENERATOR_EAN13} macro produces a valid EAN-13 barcode with a check digit. Use it the same way as the counter: in the barcode field, with the “empty” condition, so you don't overwrite what's already there.
To print the resulting barcode on a label or price tag, see printing barcode labels.
Copying between a field and an attribute
Attributes are available to formulas too — you refer to them by their code. This covers two mirror tasks: putting an attribute value into a regular field (so it goes into a feed that has no attributes) and the reverse — filling an attribute from a regular field.
You pick the target field with the “Add formula” button: that list includes all attributes. The source in the expression is written as the {Catalog attribute: name} macro — it usually isn't in the “Fields for formulas” list, so copy the name from the attribute reference list.
Move the value of one attribute into another. “Add formula”, pick the target attribute in the list, and the source attribute in the expression:
{Catalog attribute: Color}
Add the apply condition “target field is empty” if filled values must not be overwritten. For products that don't have the target attribute yet, the app creates it; a product with no value in the source attribute won't get the target.
A text label by condition: “New” or “Sale”
The target is an attribute or text field that should hold the label:
CASE WHEN {Product: On sale} = 1 THEN 'Sale' WHEN {Product: Date added} >= CURDATE() - INTERVAL 30 DAY THEN 'New' ELSE '' END
Conditions are checked top to bottom, and the first one that's true gives the result. A sale product added a week ago gets “Sale”. The “New” label disappears on its own once the product is 30 days old, but only after the formula's next recalculation.
Markup by cost price ranges
The target is “Price”. The more expensive the product, the lower the percentage:
CASE WHEN {Product: Cost price} <= 0 THEN {Product: Price} WHEN {Product: Cost price} < 500 THEN {Product: Cost price} * 1.30 WHEN {Product: Cost price} < 2000 THEN {Product: Cost price} * 1.20 ELSE {Product: Cost price} * 1.12 END
The first branch keeps the price as is where the cost price isn't filled in — without it, such products would get a zero price. Running it again doesn't inflate the price: the formula calculates from the cost price, not from the price itself.
Lowest price among a group of suppliers
The FromGroupContractor_N block (it also has a Russian synonym) collects the price list rows of all contacts in group N that are matched to the product. MIN, MAX and SUM are allowed inside the block:
[[FromGroupContractor_2 MIN(IF({Price list: Price} = 0, NULL, {Price list: Price}))]]
This is the lowest non-zero price among group 2 suppliers. IF(… = 0, NULL, …) drops zero-price rows, or the minimum would be zero. Only active price lists count. In “Fields for formulas” the block is “Take the value from a contact group”. The “Contact groups” window doesn't show the group number — if unsure, ask support.
Competitor prices are available too, but not as a separate “competitor field”. In Elbuz a competitor is a contact with its own price list: its price reaches the product through matching, and the formula reads it from price list fields. Same steps as for a supplier: upload the price list, match the products, and only then write the formula.
How to limit a formula to some of the products
The “Apply condition (optional)” block at the bottom of the editor filters the products the formula will reach at all. Without a condition, the rule applies to the whole catalog.
You build the condition with buttons, not text. “Add” adds a “field — operator — value” row, “Add group” a nested group with its own “and / or”. “Save” saves it, “Reset” clears it. Below the builder, the app restates it in plain words: read this before running on the whole catalog — it shows what you actually filtered.
You almost always need a condition, not for speed but for safety. Three typical examples: run only for one category, only for products of one manufacturer, only where the target field is still empty. The last option protects against double application better than any amount of caution.
There's one more filter that works outside your condition: formulas don't touch products with the “Do not update” flag at all. It's the same flag that protects a card from being overwritten by a price list, and it applies to formulas in the same way.
How to restore a previous version of a formula
The app keeps previous versions of each formula's text. Open the “Formulas” tab, select the formula in the list and click “Change history” above the editor (the same clock button is in the window's toolbar, with the tooltip “Formula change history: previous versions, comparison with the current one, restore”).
- On the “Versions” tab, click the version you need — the app shows the difference from the current one: green appears after restoring, struck-through disappears.
- Click “Restore” and confirm. The current version also goes into the history, so you can undo a restore the same way.
- Look for a deleted formula on the “Deleted” tab: restoring returns it to the list with all its settings. If no formula is selected, the history opens straight on this tab.
1
Versions tab2
Saved version3
Comparison with current formula4
Restore button- Versions tab — saved versions of the selected formula; the Deleted tab holds removed formulas.
- A version in the list — click it to compare with the current formula.
- Comparison — green text will be added, struck-through text will disappear.
- Restore — returns the formula to this version (not pressed while shooting).
A version stores the formula expression and the apply condition. Each formula keeps its last 50 versions; one person's edits within 10 minutes merge into one, so in-between typing states aren't there. Versions marked “Changed by the system” are made by the app itself before bulk changes: renaming or deleting an attribute, merging duplicate attributes.
The history restores only the formula text. Values the formula has already written to products stay as they were after the run: to fix them, apply the restored formula again.
Scenarios
Four store tasks: which settings to turn on and what you get.
Price no higher than the RRP after every price list update
Task: the supplier changes prices, and you can't sell above the recommended price.
What to set up: on the “Formulas” tab — “Add formula”, the “Price” field, the expression from the “Don't sell above the recommended price” recipe. On the “Settings” tab, check “Apply formulas”.
What you get: the formula runs in the pass that updates the catalog from the price list, only for products linked to its rows — and if “Additional” tab filters narrow the pass, only for that filtered set. The result follows the price rounding settings. A formula with an error is skipped and logged in the operation log.
What won't happen: the price of products with “Fixed Price” or “Do not update” won't change. The formula doesn't touch products that aren't in this price list in this pass — for them, click “Apply this formula” on the tab.
Price slightly below the competitor, but not below the purchase price
Task: set the price 1% below the cheapest competitor and don't sell for less than the purchase price plus 5%.
What to set up:
- Add the competitor as a contact in the “Competitor” group and connect its price list or a parser for its site. Don't set markups on this price list: the competitor's price is taken from the “Price” field of its price list, and a markup would end up in the comparison.
- Match the products in the competitor's price list to the catalog. Without matching, the competitor's price won't reach the formula.
- In the “Updating base catalog” window, in the “Price selection by contact group” block, “Supplier” must be checked and “Competitor” not. That's the default. Check “Competitor” and the catalog takes the competitor's price as your own; check nothing and the price is taken from all groups, competitors included.
- Add a formula on the “Price” field:
CASE WHEN [[RowFromCompetitor_1{Price list: Price}]] > 0 THEN [[RowFromCompetitor_1{Price list: Price}]] * 0.99 ELSE {Product: Price} ENDRowFromCompetitor_1is the competitor's lowest price for this product,_2the second lowest. If there's no competitor price, the current price stays. - On the “Settings” tab, check “Apply formulas”.
- In Account → System settings → “Catalog update” → “Prices and markups”, turn on “Do not set the price below purchase price + N %” and enter 5. A value of 0 means not below the purchase price itself.
1
Switch2
Percent N- Switch — turns the price floor on.
- Percent N — the margin above purchase cost, in percent.
What you get: on every catalog update from price lists, the price is calculated from the competitor, and then the floor raises any prices that ended up lower to “cost price × 1.05”, rounded up to the cent. The floor applies after formulas and markups, so it also catches a regular markup.
Demo examples, UAH: competitor 6,559, purchase price 6,042 — price 6,494, 1% below the competitor; purchase price 27,450 — price at least 28,822.50. Where the floor raised the price, “Product markup history” shows the step “Floor “not below purchase price” — Price raised to purchase price + 5 %”.
1
Floor step2
Final price- The floor step: the price was raised to purchase price + 5%.
- The final price after the floor was applied: 430.50 EUR.
What won't happen: the price of products with “Fixed Price” or “Do not update” won't change, either by the formula or by the floor. The “Apply this formula” button outside a catalog update doesn't apply the floor — it works only during an update from price lists.
Your own SKU for new products only
Task: products from suppliers arrive without your code, and numbers already issued must stay as they are.
What to set up: a formula in the “SKU (internal)” field with the expression [[max_add_1{Product: SKU (internal)}]]. In the “Apply condition (optional)” block — “Add”, the “SKU (internal)” field, the “empty string” operator, then “Save”.
What you get: products with an empty SKU get numbers that continue the largest number in this field across the whole catalog. To find the largest, only the digits of each SKU are used.
What won't happen: filled SKUs aren't overwritten — the condition doesn't let them through. No prefix is added to the new number: the formula writes just the number. Products with “Do not update” won't get a number.
1
Condition row “is empty”2
Plain-words summary of the condition- The condition row: the formula reaches only products whose SKU (internal) is empty.
- The summary under the buttons restates the condition in plain words.
An attribute for a filter from a product field
Task: the site filter needs an attribute, but the value is in a regular card field.
What to set up: “Add formula” — the field list includes attributes; pick yours. Insert the source field through “Fields for formulas”. In the “Language” column, set the language; without it, the formula runs in the app's main language, and in a price list pass — in that price list's language, if set.
What you get: for products that don't have this attribute yet, the app creates it and fills it with the result. In a new attribute formula, “Read-only” turns on by itself so the value isn't overwritten during parsing.
What won't happen: a product that didn't have this attribute and for which the formula returned an empty value won't get the attribute: such empty rows are deleted after the run. This attribute in other languages stays as it was.
What to do when a formula didn't work
| What you see | Why | What to do |
|---|---|---|
| The formula fails the syntax check and is in the “Formula errors” window | most often — a semicolon instead of a comma in IF, an = sign at the start, curly or angle quotes instead of ', or a field name in a macro that isn't in the list ({Product: Title} instead of {Product: Name}) | fix the listed formulas by rule ID: check the expression against the syntax rules and insert the macro from “Fields for formulas”; the “Ask the AI assistant” button sends the expressions to the assistant |
| I clicked the button — nothing changed | the formula is disabled or the apply condition didn't let a single product through | check the “Active” switch and the condition summary under the builder |
| The formula ended up in the “Formula errors” window although its syntax is correct | the expression has a forbidden word outside quotes: SELECT, UPDATE, INSERT, UNION, DELETE FROM and so on. It's skipped like a broken one; in the batch update and external catalog imports, the operation log also gets a line starting with “Formula skipped: field “…”, rule ID …” | remove the word from the expression; if it's text, put it in quotes |
| The price formula didn't work for some products | they have “Fixed Price” turned on: formulas for “price” type fields skip such products | clear “Fixed Price” in the products whose price the formula should calculate |
| It didn't run for all products | the skipped ones have the “Do not update” flag | clear the flag in the cards the formula should touch |
| The price went up a second time after another run | the formula reads and writes the same field, and there's no protection against repeated application | add an apply condition or calculate the price from a source field, not from itself |
| A value typed by hand disappeared | the formula overwrites the whole field | turn on “Read-only” or add the “field is empty” condition |
| It only ran for Ukrainian | the formula is tied to a language | create the same one for the other language |
| SKUs were renumbered from scratch | the counter ran without an apply condition | add the “field is empty” condition — and never run it without one again |
| A formula with a price list field returned an empty value | the product isn't matched to a price list row | first match the products, then run the formulas |
If a formula was skipped during a catalog update or price list upload, the “Formulas skipped during update” hint appears in the consultant chat in the products or price lists window. The consultant names which formulas were skipped and why, and suggests a fixed formula as a separate block — you paste it in yourself.
It doesn't show formulas of deleted rules or of fields your permissions hide from you. The hint is visible to those who have access to the catalog field formulas window.
FAQ
How do catalog formulas differ from price list formulas?
In what they write to. Price list formulas change the supplier's price list rows, catalog formulas change your product cards. The syntax and set of functions are the same, the windows are different.
How do I roll a formula back to an earlier version?
Select the formula, click “Change history”, click the version you need and then “Restore”. The formula text and condition come back, not the values in products (how to restore a version).
The formula fails the syntax check — what's wrong?
Most often — a semicolon instead of a comma in IF, an “=” sign at the start, or a field name in a macro that isn't in the “Fields for formulas” list. Insert fields from the list instead of typing them (troubleshooting).
How do I make a formula run only once?
There's no separate checkbox for this. The working approach is the apply condition “target field is empty”: such a formula simply has nothing to calculate the second time.
Can a formula calculate a sum or average across several products?
Not with a regular expression: a formula runs for each product separately. Totals come only from contact group blocks (over matched price list rows) and product set blocks: [[FromProductSet SUM({Product: Price})]].
I checked “Update product uniqueness key” on the “Model” field formula — and nothing changes. Why?
This column exists only in price list formulas, and it works only on the “Name” field formula (price list formulas).
How do I make a formula that multiplies the “Price” field by 1.18 on every import?
Calculate from the cost price, not from the price itself: {Product: Price} * 1.18 inflates the price on every run. See the example in markup from cost price; on the “Settings” tab, check “Apply formulas”.
What happens to a product on the site if the supplier removed it from the price list?
The product stays in the catalog and on the site, but out of stock. To have such products disabled, use the deactivation settings on the “Additional” tab in “Updating base catalog” (updating the base catalog).
Where to find it and who has access
- Menu
- Directories → Base product catalog → Products → menu → “Set up formulas for fields”
- Other ways in
- List of price lists → menu → “Updating base catalog” → “Formulas” tab
- Access right
- the base catalog field formulas window in “Group permissions”
- Prepare
- for price list fields — matched products
Catalog formulas live not in the product card but next to the batch update — where the catalog is updated from price lists: formulas almost always polish what has just arrived from the supplier. The “Apply formulas” checkbox on the “Settings” tab of the same window turns them on in the batch update.
1
Formula list2
Formula editor3
Active switch- Formula list — one row is one formula; the row name is the field that receives the result.
- Formula editor — the expression of the selected formula; insert fields with “Fields for formulas” or Ctrl+Space.
- Active switch — a formula that is switched off is not calculated.
The checkbox and the tab are different things. On the tab you build formulas and can apply them manually with a button. The “Apply formulas” checkbox decides whether to run them during the batch catalog update from price lists.
A formula can be active while the checkbox is cleared — then the batch update won't run it, but it will work from the button or when a product card is saved (see “When a formula runs”).
Related topics
- If the value needs to be calculated already in the supplier's price list rows — price list formulas.
- If formulas should run on every update from price lists — updating the base catalog.
- If it's easier to set the price with a markup by supplier or category — pricing rules.
- If the value needs to be entered once rather than calculated — bulk changes in the catalog.
