Price workflows

A price workflow is an ordered list of rules. Each rule combines a condition with a formula to apply when the condition is met. This lets you set “a different margin for a different kind of product” without writing one giant formula.

On Catalog → Prices, the tab is called Workflows: the list is on the left and the editor on the right.

Step by step

First, prepare the formulas that the rules will select (Price formulas). You cannot save a rule until a formula is available.

1. Go to Catalog → Prices, on the Workflows tab.
2. Click + above the list. An editor opens on the right with New workflow where the name will go.
3. Enter a name in the editor heading.
4. On Rules, click Add rule. Until you add one, the editor says There are no rules yet — every product keeps its base price.
5. A rule reads like a sentence: If [Field] [condition] [Value], then use formula [Formula]. Field and formula are required; without them, saving shows Select a field and formula.
6. The Active switch beside a rule decides whether it is considered at all.
7. Repeat steps 4–6 for other rules and set their order with Move up and Move down. Put narrow rules first and general ones later; the section below explains why. Remove an unnecessary rule with Delete rule.
8. On Advanced, check the Code (required, unique within the company; letters, digits, and _ only; generated from the name until you enter your own; editable after saving). Description is optional.
9. Click Save in the footer.
10. Open Price groups and assign the workflow to a group: in the group editor, select Workflow under Calculation, then choose it in Group workflow (Prices — screen and price groups). A workflow does not price anything until a group uses it. The workflow editor's Groups tab shows the groups already using it.

On save, rules are saved one row at a time: new ones are added, changed ones updated, and removed ones deleted. If one rule fails to save, the editor marks it with a message and saves the others. Correct it and click Save again.

You can test a saved workflow on a real product in the Test on product box on Rules. It shows which rule matches and the formula it selects, or No rules match — the base price is kept.

The first matching rule wins

Active rules are checked in order, and the formula from the first match is applied. The remaining rules are not checked.

Order therefore matters: put narrow rules first and general ones later. If you put “everything × 1.2” at the top, no later rule will ever run.

If nothing matches

If no rule matches, the price falls back to the base price. A calculated price left by a rule that no longer matches is cleared. This is not an error and is not reported as a failed recalculation; add a catch-all rule at the end if the base price is not a sensible result.

Condition fields

The Field list suggests: base price (in the group being tested), SKU, EAN, product name, whether the product is active, ABC class, weight in kg, height, width, and length in mm, catalog code, name, and ID. It also includes:

• Category (code or name) — matches when one of the product's active categories has that code or name.
• Attribute: … — every active company attribute. For a select attribute, enter an option's code or name (in any language). For multi-select, one matching selected option is enough.
• Custom field: … — each custom field used by at least one company product.

For categories and multi-select attributes, is not equal to and is none of mean that none of the product's values match.

You can also enter a custom path, for example, product.custom_fields.brand. A path or attribute that a product does not have never matches, even with is not equal to. Custom paths must use one of the supported forms: a product field (product.<field>), a catalog field (product.catalog.code, name, id), a custom field, a price group field (price_group.<field>), an attribute, or a category. The system rejects any other path on save.

Condition operators

A rule condition can be equals, is not equal to, is greater than, is at least, is less than, is at most, is one of, is none of, contains, or starts with.

For is one of and is none of, enter a list in square brackets, for example, ["OUTLET", "B2B"].

Numeric comparisons use decimal numbers, so a condition such as “price ≥ 99.95” behaves predictably at the boundary.

When a workflow runs

A workflow has no schedule of its own. It is evaluated when a price is recalculated: after a Base Price or exchange-rate change; after a product attribute or category changes; during manual recalculation or a bulk operation (Which price takes precedence?). A rule using a deactivated formula is skipped.

Limitation with integrations

Integration price policy configuration supports a “workflow” type, but calculating a workflow for an integration policy has not yet been implemented. For integration prices, use a formula or a simple percentage or amount adjustment.