[ Use case 02 ] Pricing
Raise the price. See the volume you'd lose first.
Compare keeping your price, a small increase and a larger one: units, revenue and gross profit per version, estimated from your own price history.
| World | Value | 80% range |
|---|---|---|
| A (Winner) | 5,028 | baseline |
| B | 4,793 | 4,665 – 4,921 |
| C | 4,575 | 4,450 – 4,701 |
- A
- Keep as is
- B
- Price +5%
- C
- Price +10%
[ 01 ] Scope
What Jonbar simulates
Whose problem: Sellers who must pass on cost increases and don't know how far they can go. On a marketplace you can't show two prices for the same product to test it live.
- Price elasticity from your own price changes, blended with a published prior when your history is thin.
- A simple competitor reaction: a share of a price cut matched after a lag. For price increases no reaction is assumed.
- Substitution to your own products in the same group.
If your history has few price changes, Jonbar says so and leans on published ranges instead of guessing.
[ 02 ] Sample output
The same run, week by week.
Each line is one version of the decision, with its range. This run has no campaign window: only the price level differs between the lines.
- A
- Keep as is
- B
- Price +5%
- C
- Price +10%
ABC
[ 03 ] Limits
What it doesn't do yet.
- Competitor reaction is a single simple rule, not a model of a named competitor.
[ 04 ] Other use cases
- [ Use case 01 ] PromotionsKnow which campaign still pays after it ends.
- [ Use case 03 ] Multi-channelA campaign on one marketplace shouldn't blur the other.
- [ Use case 04 ] Bundles · Partly available"2 for x" or "x/2 each"? Same price, different week.
- [ Use case 05 ] Launches · RoadmapPick the launch price before the launch.