Bundle / Multipack Price Calculator
Compute a recommended bundle price (net) from unit cost, bundle size, extra costs, fees and target contribution % — incl. per-unit comparison vs single and a signal.
Note: results are not made indexable via URL parameters. Canonical: https://tools.snapsoft.de/en/tools/bundle-preis
Who is this for?
- Marketplace/D2C teams testing bundles/multipacks without losing margin
- Pricing/ops teams that need per-unit comparisons and guardrails
- Teams that want to include bundle packaging/handling costs cleanly in pricing
Bundle pricing: per-unit advantage without killing contribution
Bundles/multipacks work when customers see a clear per-unit advantage — while you still hit your target contribution.
Enter unit cost, units per bundle, extra costs (e.g. packaging/handling), platform fee %, payment fee % and target contribution %. The calculator solves for a recommended bundle price (net) and compares per-unit price vs single including a signal.
Calculator
Max 6 inputs, clear outputs. Everything runs locally in your browser.
Inputs
Advanced options
E.g. bundle packaging, inserts, extra handling time.
Result
How it works
Bundle cost: (C_{bundle} = c_{unit} \cdot n + c_{extra}).
Fee share: (f = (platform\% + payment\%) / 100), target: (t = target\_contrib\% / 100).
Recommended price (net): (P = C / (1 - f - t)).
Single baseline (for comparison): (C_{single} = c_{unit} + c_{extra}\) ⇒ (P_{single} = C_{single} / (1 - f - t)).
Per-unit comparison: (P_{bundle}/n) vs. (P_{single}). Signal: green if bundle is cheaper per unit AND contrib% ≥ target; yellow if on target but no advantage; red if below target.
Quick conclusion
- The recommended bundle price is your guardrail — below it you’ll miss your target contribution quickly.
- If there’s no advantage: increase bundle size or reduce extra costs — or treat the bundle as an AOV/convenience play.
- Keep fees/costs up to date and document assumptions (net/gross, extra costs).
Sources & notes
Disclaimer: assumptions, fees and policies can vary and change. Always verify critical values in official sources (marketplace, supplier, payment provider).
FAQ
Why is “extra cost” used for the single baseline as well?
To keep the per-unit comparison fair, extra costs are treated as a one-time per-order block (packaging/handling). For singles it applies once per sale; for bundles it’s spread across multiple units.
Which fees should I enter?
Enter the percentage fees applied to your selling price (platform/category + payment). Keep them up to date from your fee schedule/seller center.
Net vs gross — what should I use?
The calculator uses net logic; gross price (VAT 19%) is display only. Important: don’t mix systems for fees/costs.
How do I pick the right bundle size?
Start with 2–3 units and check two things: (1) your target contribution stays achievable, (2) per-unit advantage is visible to customers. Then iterate on bundle size and extra costs.
What if the bundle isn’t cheaper per unit?
Then it’s not a “savings bundle” — it’s more convenience/AOV. Either increase bundle size, reduce extra costs, or adjust messaging (don’t claim savings).
Turn it into a repricing rule in SnapTrade
If you want to turn bundle guardrails into persistent repricing rules/price rails (not just a one-off calc): take a look at SnapTrade.