Glossary¶
Action¶
The terminal node of a workflow, where price changes are written for the products that reach it. Actions can include guardrails (e.g. a margin floor).
Attribute¶
A data field on a product: unit cost, competitor price, MSRP, brand, or any field you define. Attributes power cost-pegged rules, workflow logic, and grid columns.
Attribution¶
The audit record behind every price change: its source (a workflow, Manual, or External sync), the person, the action, and when it took effect.
Baseline¶
The estimate of what a cohort would have done had a run's prices never gone live, blended from comparison groups fitted on the thirteen weeks before go-live. What measuring results compares against. Known in causal-inference terms as a counterfactual.
Cohort¶
The product × location combinations a published workflow run priced — the population measuring results follows. A combination is measured only while the run's price still stands: once a later publish or a manual change takes it over, it leaves the cohort from that day.
Customer segment¶
A customer tier with its own prices (called a price list in data files and the API). Customers are assigned to segments; every rule targets one.
Decision¶
A workflow node that routes products down different branches toward different treatment.
Decision path¶
The recorded route a product took through a workflow — which decisions it passed and which action priced it. Shown in the Review grid.
Default segment¶
The protected customer segment serving customers not assigned to any segment. It cannot be deleted.
Elasticity¶
A product's price sensitivity: how strongly its sales volume answers a price change. Workflow evaluation predicts with each product's estimated elasticity; measuring results needs none — it compares actual sales with a baseline.
External sync¶
The source label for a price change that arrived from your ERP via reconciliation rather than being made in Resolve.
Family head¶
The product whose price a product family follows. Marked with a crown.
Family member¶
A product locked to its family head's price. Marked with a lock.
Fixed addition¶
A rule type: price = cost + a set amount. Cost-pegged.
Fixed price¶
A rule type: price is exactly the stated number, unaffected by cost changes.
Hierarchy¶
The level structure organising products (e.g. Category → Line → Product). Rules on a level inherit to everything beneath it.
Impact assessment¶
The measurement of a scenario's changes against the last twelve months of actual sales, before publish.
Inheritance¶
The cascade by which a rule on a hierarchy level prices all products beneath it, unless a more specific rule overrides.
Live¶
The book of record: the current real prices. Read-only; changes reach it only by publishing a scenario (or by ERP reconciliation).
Local R²¶
A decision node's split score in workflow evaluation: the share of the price-sensitivity spread among the products reaching that node that its question separates into the TRUE and FALSE branches. 0% sorts nothing; 100% splits the mix perfectly. Local because each node is measured against its own mix — scores do not add up across the tree. A decision's drawer shows the tree's median split — the middle score across the tree's decisions — as a yardstick.
Markup¶
A rule type: price = cost × a coefficient. Cost-pegged.
Not offered¶
A rule marking a product as not for sale in a scope, blocking inherited coverage there.
Price compliance¶
The share of a run's cohort still selling at its published price, counted by prices or by revenue. Decays as manual changes, ERP syncs, or later runs overwrite prices.
Price CSV¶
The export of specific prices for your POS or ERP, produced by Export prices.
Price Display Preference¶
The global setting choosing whether the app presents prices, margins, or markups. Presentation only.
Product family¶
A group of products that must carry the same price within each location, across all segments. See family head / member.
Publish¶
The atomic step copying a scenario's changes onto Live. Adds and overwrites; never clears untouched Live rules.
Publish history¶
The Automate tab that measures each published run after the fact: realised impact versus the baseline and price compliance.
Right direction¶
The table on an action node's Evaluation tab. The direction of a product is the sign of its predicted change — a product predicted to gain revenue is "right" for revenue, one predicted to gain profit is "right" for profit — whether its elasticity was measured or imputed from similar products. The by product column is the share of priced products predicted to move the right way; by money is the share of today's revenue (or profit) those products carry. One row each for Revenue and Profit, the profit money share taken over products with positive profit today. Products whose price did not move are excluded, as a zero move has no direction, and the shares are withheld on a run with no elasticity estimates, where every product would agree by construction.
Reconciliation¶
The inbound convergence of Resolve's Live rules on an ERP-exported price book, within the territory the file asserts.
Rule¶
The unit of pricing: markup, fixed addition, or fixed price (or not offered), scoped to a product or hierarchy group × location × segment, effective from a stated time.
Scenario¶
A draft workspace for pricing changes, isolated from Live until published.
Scheduled price¶
A rule with a future valid-from date, visible in advance and effective automatically at its time.
Trigger¶
The first node of a workflow, defining which product × location rows are in scope for the run.
Valid from¶
The moment a rule takes effect. Minute precision.
Workflow¶
A decision tree (Trigger → Decisions → Actions) that prices a population of products in a repeatable, audited run.