Restaurant chains · Roadmap
A menu price is 40 decisions, not one.
The plan: rehearse a central price change per order, after platform commission, and roll it out in waves.
Not built yet. The numbers on this page are illustrative.
One order, before and after an 8% menu price rise
The price moves 8%, what is left per order moves more.
Today: 240 TL · Platform commission 58 TL, Food cost 74 TL, Courier and packaging share 14 TL, Contribution margin 94 TL | After: 259 TL · Platform commission 62 TL, Food cost 74 TL, Courier and packaging share 14 TL, Contribution margin 109 TL
Why per order
The commission is taken on every order, so the decision lives there.
A chain's economics are decided one order at a time, and Jonbar reports at that level.
- Commission rises with the menu price
- A campaign is a discount plus commission
- Extra orders must cover both
- Branches react differently to one price
The rollout
Switch 12 branches, keep 12 back, then measure.
Three waves a week apart; the comparison group never switches.
Example rollout · illustrative numbers
Branches switched: 0Comparison group: 12
- Switched branches
- 94TL per order
- Comparison group
- 94TL per order
- Orders
- 0%against the comparison group
- Weekly gross profit
- 0%against the comparison group
Every branch on the old price; the forecast is written down.
Example: 48 branches, three weekly waves of 12, 12 held back. Gross profit per order 94 TL to about 109 TL; orders about 6% below the comparison group, weekly gross profit about 1.6% above.
Without the comparison group, a cold week looks like a price mistake.
How we keep ourselves honest
The forecast is written down before wave one, then scored against the comparison group.
Without a held-back group, the season explains every result. Jonbar compares switched and unswitched branches week by week.
The rest of the engine
Same engine, other decisions.
Details: the example, inputs, outputs and limits
The example chain
48 branches, prices set centrally, food cost up and a platform offering a two-week campaign it partly funds.
Next month's turnover cannot separate a price change from the weather or a holiday.
What comes back
- What is left per order, per version.
- Orders gained or lost, as a range.
- Extra orders a campaign needs to break even.
- The wave plan and how long to measure.
What the engine needs
- Twelve months of order lines per branch and platform.
- Commission, courier share, packaging and monthly fees.
- Food cost per menu item or item group.
- Which branches share a price list.
- Past campaign weeks and platform campaign days.
- Branch opening dates and closures.
Honest limits
- None of this is built yet, and it is untested on restaurant data.
- For 40+ branches or a central price list.
- Rent, staff and marketing are not included.
- Platform ranking is not modelled yet.
- No accuracy figure until the backtest is published.