[ Use case 03 ] Multi-channel
A campaign on one marketplace shouldn't blur the other.
Run the decision for the channel where it happens. Your other channel's history stays a clean baseline.
| World | Value | 80% range |
|---|---|---|
| A | 3,823 | baseline |
| B | 3,463 | 3,293 – 3,632 |
| C (Winner) | 4,242 | 4,051 – 4,396 |
- A
- Keep as is
- B
- Price +6%
- C
- 10% off, weeks 3-4
[ 01 ] Scope
What Jonbar simulates
Whose problem: Sellers on two marketplaces plus their own site. If channels are summed, a campaign on one leaks into the other's baseline.
- The decision on a chosen channel, estimated from that channel's own history.
- A warning when uploaded data has channels summed together.
[ 02 ] Sample output
The same run, week by week.
Each line is one version of the decision, with its range. The shaded weeks are the campaign window; the weeks after show what it cost or kept.
- A
- Keep as is
- B
- Price +6%
- C
- 10% off, weeks 3-4
ABC
[ 03 ] Limits
What it doesn't do yet.
- v0 does not model shoppers switching between channels because of your decision. It works per channel.
[ 04 ] Other use cases
- [ Use case 01 ] PromotionsKnow which campaign still pays after it ends.
- [ Use case 02 ] PricingRaise the price. See the volume you'd lose first.
- [ 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.