[ Use case ] Restaurant chains
Rehearse the menu price before 40 branches ship it.
Jonbar runs 3-5 versions of a menu price or platform campaign on your own order history. Showing what each one leaves per order, and measuring the result branch by branch in waves, is what we're building with the first chains.
Planning a price rise or a campaign?
Decision-time checkSample scenario · assumed commission and courier
Platform campaign: 20% off · one menu item
- Menu priceTRY 400
- Discount−TRY 80
- Commission (assumed 25%)−TRY 80
- Courier (assumed)−TRY 45
- Food and packaging−TRY 150
- Left per orderContribution marginTRY 45
Without campaign: TRY 105
[ 01 ] What Jonbar simulates
The same engine, applied to your menu.
Restaurant chains use the same engine as marketplace sellers: price and campaign decisions, run side by side in one market.
- Menu price changes: orders and revenue per version, from your own order history.In pilot
- Platform campaigns: percent off and the share the platform funds.In pilot
- What's left per order after commission, delivery share and food cost.Building
- The decision-moment check: when a platform proposes a campaign, what it leaves you and how many extra orders it needs.Building
Without the campaign, TRY 105 stays with you per order. With it, TRY 45. To earn the same, the campaign needs 2.3× the orders.
- Chains
- 40+ branches, or prices set centrally
- Channels
- Food delivery platforms, several at once
- Decisions
- Menu price, platform campaign, branch differences
- Stage
- Private pilot
[ 02 ] Sample run
One menu item, three prices, twelve weeks.
A sample engine run for one menu item across a chain on one delivery platform. World A keeps the price at TRY 400; B and C raise it.
- A
- TRY 400 (as is)
- B
- TRY 420 (+5%)
- C
- TRY 440 (+10%)
Sample scenario · Not yet backtested
| World | Total | vs. A | Result |
|---|---|---|---|
| A | 4,195,201 | base | |
| B | 4,235,468 | +1% | |
| C | 4,262,932 | +1.6% | Ahead, not clear |
| World | Total | vs. A | Result |
|---|---|---|---|
| A | 16,781 | base | Winner |
| B | 15,687 | -6.5% | |
| C | 14,700 | -12.4% |
| World | Total | vs. A | Result |
|---|---|---|---|
| A | 6,712,322 | base | Winner |
| B | 6,588,506 | -1.8% | |
| C | 6,467,897 | -3.6% |
In this sample, a 10% menu price rise loses about one order in eight; gross profit before commission barely moves and has no clear winner.
[ 03 ] Learn
Measured in waves, branch by branch.
A chain applies one decision to many branches. The first wave gets the change, the rest wait; comparing the two groups over the following weeks shows whether the result came from the decision or from the season. The forecast is locked before the first wave starts. We're building this measurement with the first chains.
Illustration: 40 branches split into three waves of 14, 13 and 13, a week apart; each wave switches to the new price one week after the previous one.
[ 04 ] Honest limits
What to know first.
- Built for chains with 40+ branches or central pricing; franchise-set prices are not a fit yet.
- What's left per order after commission and delivery is being built; the engine reports gross profit today.
- No accuracy figure until the backtest is published.
- Jonbar recommends; you decide and change prices on the platforms.