Which price takes precedence?

A price row has three fields, but only one is visible externally. The order is fixed:

1. Override Price — if set, it always wins.
2. Calculated price — the result of a formula or workflow.
3. Base Price — a value entered manually.

On the Product prices tab, these correspond to Override, Calculated, and Base columns; the result appears under Final. Amounts use the group's currency; an empty cell is —, while zero is 0.00.

Step by step: remove an override and return to the formula

There is no separate “clear override” button. Clear the field instead.

1. Go to Catalog → Prices, on the Product prices tab.
2. Find the row with search, which looks for product name, SKU, and EAN. Use the price group, pricing method, and status filters to narrow the list.
3. Check the Override column. If it has a value, that value wins and no price recalculation will change it.
4. Click the Edit icon on the row.
5. In the Edit Product Price panel (the panel is in English), clear the Override Price field completely — an empty field means there is no override.
6. Click Update.
7. Recalculate the price using the Recalculate icon on the row.

Recalculate group above the table recalculates the entire group selected in the group filter — all its products, regardless of search or other filters. The button is inactive unless a group using a formula or workflow is selected. You can also find it in the group's editor, under More actions.

8. Check the Calculated and Final columns; they should now match.

An override wins even when it is zero

An override counts as set even if its value is 0.00. Here, zero is a valid price, not “no price” — deliberately, so free products can have a price of zero.

In practice, an override is permanent. Until you clear it, no formula or workflow can change that product's price. This is the most common answer to “I recalculated the formula, but the price hasn't moved.”

To return to formula-based pricing, clear the override; do not just recalculate. See the steps above.

The calculated price is a cache

The calculated price stores the last recalculated result. For a fixed price, it is deliberately cleared on every recalculation. Otherwise, the old value would outrank the newly changed Base Price and hide it.

A formula error does not remove the price

If recalculation fails — because of an invalid expression, a missing exchange rate, or division by zero — the system keeps the previous calculated price, records the error, and reports the failed recalculation. It does not silently fall back to Base Price or set the price to zero.

That is why you should check the failed count in a bulk operation, not only whether the operation finished.

Negative prices are clamped to zero

If a formula, workflow, or integration adjustment produces a negative result, the price is set to zero and a warning is recorded.

Recalculation is not scheduled

Formulas and workflows are not recalculated on a schedule. Recalculation is triggered by a specific event: a Base Price change, an import or exchange-rate change, a change to a product attribute or category (for workflows), clicking Recalculate on a row or Recalculate group, or a bulk operation. Merely opening the screen does not recalculate anything. A schedule exists only for sending ready prices to a marketplace — that is different from calculating them.