Allocating Bundle Discount Depth Across Component SKUs
A bundle discount is one line on the receipt but lands unevenly across components. Here's how to allocate it — by price, margin, or role — without accidentally killing your best SKU.
Quick answer
Default to proportional-by-standalone-price allocation — it matches how the customer perceives value and keeps SKU-level margin comparable across bundled and standalone sales. Switch to margin-weighted when component margins differ by more than ~15 points, and to strategic-role (protect the anchor, absorb on the filler) when you're using bundles to move slow inventory.
Allocating Bundle Discount Depth Across Component SKUs
The practice of splitting a bundle-level discount across its component SKUs so each product carries a fair share of the markdown in reporting.
When you sell three shampoos as a €30 bundle instead of €39, the €9 discount is one number on the order. But your P&L, your merchandising dashboard, and your reorder logic all run at the SKU level — so that €9 has to land somewhere. The allocation method you pick decides which SKU looks profitable and which looks like a drag, even though the bundle margin as a whole hasn't changed. Get it wrong and you'll delist a hero SKU that's actually pulling the bundle, or double down on a filler that's silently eroding blended margin.
This is the operational sibling of Attributing Bundle Margin Back To Component SKUs. Margin attribution asks how much profit each SKU earned in the bundle; discount allocation asks how much of the markdown each SKU absorbed. You need both — and they have to agree — or your SKU-level reporting drifts against your bundle-level P&L.
Why the same bundle produces different SKU-level numbers
Consider a hair-care bundle: shampoo €18, conditioner €14, mask €12. Standalone total €44, bundle price €35, discount €9. The bundle margin is fine. But if you allocate that €9 equally (€3 per SKU), the mask absorbs 25% off its list price while the shampoo absorbs 17% — so the mask now shows a razor-thin per-unit margin in your reports.
A merchandiser scanning the SKU dashboard sees the mask underperforming and pushes to reformulate or discontinue it. Except the mask is doing exactly what a bundle component should do. The allocation rule invented a loser.
The fake-loser pattern
Any component with a below-average standalone price gets over-penalised by an equal-split allocation. If your bundle contains a cheap filler and a premium anchor, equal-split makes the filler look profitable and the anchor look weak — the exact opposite of the truth. This is the single most common reporting artifact in bundle merchandising.
The three allocation methods worth knowing
Method one: proportional to standalone price. Each SKU absorbs a share of the discount equal to its share of the pre-bundle total. In the hair-care example the shampoo absorbs €18/€44 × €9 = €3.68, the conditioner €2.86, the mask €2.45. Every SKU ends up discounted at the same percentage (20.5%), so margin percentages stay comparable to standalone sales. This is the default and it's the right default about 70% of the time.
Method two: proportional to margin dollars. Each SKU absorbs discount in proportion to its contribution margin. A high-margin SKU absorbs more absolute discount but its margin percentage takes a smaller hit. Use this when component margins vary widely — say, a €40 accessory at 65% margin bundled with a €40 core product at 25% margin. Equal or price-based allocation would push the low-margin SKU into a loss on paper. Margin-weighted keeps both SKUs solvent in the report.
Same €9 discount, three allocation methods — the hair-care bundle example
| SKU | Standalone price | Equal split | Proportional to price | Proportional to margin |
|---|---|---|---|---|
| Shampoo (anchor) | €18.00 | €3.00 (17%) | €3.68 (20.5%) | €4.10 (23%) |
| Conditioner | €14.00 | €3.00 (21%) | €2.86 (20.5%) | €3.20 (23%) |
| Mask (filler) | €12.00 | €3.00 (25%) | €2.45 (20.5%) | €1.70 (14%) |
| Bundle total | €44.00 | €9.00 (20.5%) | €9.00 (20.5%) | €9.00 (20.5%) |
Method three: strategic-role allocation. You manually assign a role to each SKU — anchor, complement, filler, clearance — and absorb the discount asymmetrically. Anchors get protected (small discount share); fillers absorb the depth. This is how experienced merchandisers actually think, and it's what most ERPs can't do out of the box. See Shapley vs Proportional Allocation For Bundle SKU Margin for the mathematically principled version of the same idea.
Effective discount percentage per SKU by allocation method
Shampoo (anchor)
Conditioner
Mask (filler)
How to pick the right method for your catalogue
Start with proportional-to-standalone-price. It's transparent, matches perceived value, and preserves comparable margin percentages across bundled and standalone sales. If your finance team ever audits SKU margin trends, this is the method that survives the audit without a footnote.
Switch to margin-weighted when the spread between your highest- and lowest-margin components exceeds 15 percentage points. Apparel bundles pairing a hero garment with an accessory, or beauty bundles pairing a premium serum with a low-margin applicator, both fit this pattern. Price-based allocation would flatten those margin differences unfairly.
Reach for strategic-role allocation when the bundle exists to solve a merchandising problem — moving overstock, protecting an anchor's advertised price, launching a new SKU alongside a proven one. In those cases the allocation is a business decision, not an accounting formula, and it needs to be documented so downstream reports can be read correctly.
Keep the method consistent per bundle, not per SKU
The rule lives on the bundle SKU, not on its components. A single component might appear in three bundles under three different allocation rules — that's fine, and it's exactly what strategic-role allocation is for. What you cannot do is change the method mid-quarter without restating history: your SKU-level margin trend will look like a step change that isn't real.
Test the allocation choice before you commit
Two experiments worth running before you lock a method in. First, re-run the last 90 days of bundle sales under each of the three methods and compare per-SKU margin rankings. If the top-five and bottom-five SKUs shuffle meaningfully, the method choice is materially changing merchandising decisions — and you need to consciously pick, not default.
Second, look at reorder velocity for the SKUs that changed rank. If a SKU that looks like a loser under equal-split is being under-ordered, you have direct financial evidence that the allocation method is costing you stockouts on a product customers actually want. That's the moment to change the rule.
Frequently asked questions
Discount allocation splits the markdown across components — deciding which SKU absorbs which slice of the €9 off. Margin attribution splits the resulting profit. They're paired: once you allocate the discount, per-SKU margin falls out mechanically. See the parent topic on attributing bundle margin back to component SKUs for the full picture.
Shopify's native bundle apps generally allocate proportionally to line-item price, which is the same as proportional-to-standalone-price when components aren't already discounted. That's a sensible default, but it means margin-weighted and strategic-role allocation require a custom reporting layer downstream — Shopify itself won't produce those views.
Discount allocation changes the revenue side of the SKU margin calculation; COGS stays fixed per unit. So the same COGS assumption produces different margin percentages under different allocation rules. Always name the allocation method in your margin reports — 'SKU margin' alone is ambiguous when bundles are involved.
Rarely. It's defensible only when all components have near-identical standalone prices and near-identical margin percentages — a bundle of three variants of the same product, essentially. In every other case equal-split creates the fake-loser artifact and misleads whoever reads the SKU dashboard.
A free item is a 100% discount on that component, which means proportional methods break (division by the free item's discounted price becomes meaningless). Use strategic-role allocation: assign the full discount amount to the gift SKU and record it as a marketing cost against the anchor. Otherwise your gift SKU looks catastrophically unprofitable.
Yes — the refund must reverse the exact same per-SKU discount that was allocated at purchase. Otherwise partial returns of a bundle create phantom margin: the customer returns the anchor and keeps the filler, but if your return logic uses equal-split while your original sale used price-proportional, the retained SKU's margin will be wrong.
If you're measuring whether a bundle promotion lifted a specific SKU, the allocation method dictates what 'lift' even means for that SKU. Under margin-weighted allocation a high-margin SKU absorbs more discount and shows less unit-margin lift; under strategic-role it might show none at all. Compare like-for-like methods across periods.
Technically yes and some large retailers do — finance uses proportional-to-price for GAAP-friendly reporting, merchandising uses strategic-role for buying decisions. But you need a reconciliation view that shows the delta, or the two teams will argue past each other about which SKUs are actually performing.
Then there's no discount to allocate — you have a bundle premium, usually because the bundle includes a service or exclusive variant. Allocate the premium the same way in reverse: proportional-to-price adds a small uplift to each SKU's effective revenue. Rare in DTC but common in electronics with warranties bundled in.
Shapley allocation is a mathematically fair version of strategic-role allocation: it computes each component's marginal contribution to bundle attractiveness across every possible sub-bundle. It's the theoretically correct answer when components genuinely differ in pulling power, but it's overkill for most catalogues. The related Shapley vs Proportional Allocation For Bundle SKU Margin page walks through when the extra rigour pays off.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.