Skip to content

Pricing

Owners and pricing managers see six weeks of demand ahead, what the engine would change this week and why, and how their prices and promotions sit against the competitor menus they name. Every product has a role, from traffic driver to clearance, and the engine aims each one at its own goal inside your margin floor. Before an event is pushed, each line shows what it is expected to earn, and Let the engine choose picks the raises and cuts the demand model stands behind. Before a promotion runs, Plan a promotion says how deep, how long and when, and says to test it when the forecast can't tell. Four weeks after a push, each move is measured against the products held back from it. Nothing reaches the shelf until a person pushes it.

Included in Growth. See plans
Price event
Price event. A manager reads what each line is expected to earn, lets the engine choose the moves it stands behind, clears the guards and pushes. Four weeks later the same page shows what happened against the forecast frozen at the push.

Merit gaps

A manager picks products whose merit and price disagree and adds them to a price event.

Pricing roles

A manager accepts or changes the role proposed for each product from its baskets, with the reason beside it.

Plan a promotion
Plan a promotion. A manager picks a family, format or brand and gets one answer: run it at this depth on these dates, don't discount, or test it first, with the gross profit to expect.
Competitor prices
Competitor prices. A pricing manager sees every listing in stock at each competitor, size by size, on one price axis with your own shelf, specials beside the list prices they undercut.
Compare promotions
Compare promotions. A pricing manager sees how much of each competitor's menu is on deal this week and next, how deep by size, and which brands you stock are on deal there while full price here.
Assortment gaps
Assortment gaps. A buyer sees the brands, price tiers and sizes most competitors carry and you don't, and what adding a brand there has earned this store before.
A product's price history
A product's price history. List price, the price it sold at, cost and the margin floor over time, units a day under it, and what it sold at each price.
Results
Results. An owner reads each event's gross profit against the range forecast at its push, which move sizes the engine now trusts, and how often its forecasts held.

What it reads

Sales, prices, costs, discounts and lab potency from your POS, and the prices, specials and stock on the online menus of the competitor stores you name, on the schedule you set.

What runs by itself

Weekly: the demand forecast six weeks ahead, the demand model refitted from every measured move, a proposed role for every product, a Monday draft event that waits for a person, and a draft test wherever the forecast can't tell yet. Nightly: a word on every product's price. When an event's window closes: its measurement. No schedule ever pushes a price.

What it writes back

Prices go to your POS only when a person with permission pushes a price event. A rollback is a new push. Promotions are created in your POS by a person; BudLogix says what to create.

How it thinks

The same articles operators read inside BudLogix, published as they read them.

Deciding a price

Forecast and proof

Competitors