The “starter” bundle at a promotional price sells well on the web shop. Three weeks later, the stock count shows a gap: cable stock is negative, gift box stock is positive, and nobody can say what margin the bundle actually delivered. The problem is not the promotion. It is the way the ERP was configured to sell a set of products.
This guide is for CIOs, e-commerce managers and order management teams in wholesale, distribution and light manufacturing. It compares the three kit models, explains the difference between a sales BOM and a manufacturing BOM, then covers availability, pricing, VAT, returns and online channel synchronization. It ends with setup in Odoo, Business Central and SAP, and a checklist.
The problem: sell a bundle, deplete the components, invoice at the right price
A customer orders “a set”. For the salesperson, that is one quote line and one price. For the warehouse, it is several SKUs to pick. For accounting, it is products that may carry different VAT rates and different purchase costs. The ERP has to reconcile these three views from a single entry.
When it does not, workarounds multiply:
- The catch-all item: a single “XMAS-PACK” SKU created for selling, with no link to its components. Real stock never goes down, or goes down through manual adjustments that nobody reconciles.
- Double entry: the order desk adds the bundle, then removes each component by hand.
- Manually split pricing: the bundle sells at €89, but the invoice shows catalog prices with a global discount, which skews revenue by product family.
Each of these workarounds degrades stock valuation, margin by product and the reliability of the availability shown online. It is better to pick one model and configure it properly.
Three models for selling a set
Virtual kit: exploded at order time
The kit does not exist physically. It is a sales line that breaks down into components on validation. The kit’s own stock is always zero: only component stock moves. In Odoo, the Kit BoM type works this way: a single line appears on the quote and the order, but the delivery slip lists each component.
Assembled physical kit: assembly order
The kit is a stocked item, built from its components through an assembly order (sometimes called kitting), either to order or in advance. Business Central distinguishes the two cases: assemble-to-order and assemble-to-stock. The first creates an assembly order linked to the sales line; the second prepares kits ahead of time, for example for a campaign.
Fixed-price composite item
The bundle is a sales item in its own right, with its own price, and the BOM mainly drives accounting and logistics breakdown. This is the model for “all-inclusive” offers where the customer sees only one price. It often combines a virtual kit (for stock) with its own pricing rule (fixed, not the sum of components).
Comparison table
| Criterion | Virtual kit | Assembled kit | Fixed-price composite item |
|---|---|---|---|
| Kit stock | None, components only | Stocked, assembly order | Depends on implementation (often virtual) |
| Advantage | No handling, no dedicated stock, availability always consistent | Fast shipping, ready-to-ship parcel, quality control | Clear price for the customer, simple marketing |
| Limit | Longer picking time | Tied-up capital, risk of unsold kits to dismantle | Price to maintain, risk of drift from the sum of components |
| Stock impact | Components leave stock immediately at order | Components leave at assembly, then the kit at shipment | Same as the underlying model |
| Suited to | Wide catalog, changing promotions | High volume on few SKUs, gift boxes | Packaged commercial offers |
The main selection criterion is volume and storage. If the bundle sells in low volumes or its composition changes often, the virtual kit avoids transforming stock. If the same composition ships at scale and the picker saves time with a ready-made parcel, assemble-to-stock is justified. For a gift box with specific packaging, assembly is almost mandatory: the packaging is itself a component.
Sales BOM vs manufacturing BOM
Both are “lists of components”, but they do not answer the same question. The manufacturing BOM describes how an item is produced: routings, work centers, yields, scrap, sub-assemblies. The sales BOM describes what is sold together.
| Dimension | Sales BOM | Manufacturing BOM |
|---|---|---|
| Purpose | Sell and deliver a set | Produce an item |
| Operations | None (or simple assembly) | Routings, work centers, times |
| Price | Bundle selling price, possibly split | Calculated cost price |
| VAT | Each component keeps its rate | Not applicable internally |
| Stock | Explosion at order or at assembly | Consumption on production order |
| Cost | Sum of component costs, plus packaging and any labor | Materials, labor, overheads |
| Versioning | Driven by marketing (promotions) | Driven by engineering |
In SAP, this separation is explicit: a sales and distribution BOM (usage 5) drives explosion in the sales order, while the production usage drives manufacturing. Mixing both in a single structure is a classic source of errors: a marketing change to the bundle must not alter a manufacturing routing, and vice versa.
A light manufacturer selling finished goods in bundles will therefore often have both: a manufacturing BOM for each product, and a sales BOM that assembles those finished goods into a bundle.
Kit availability calculation and reservations
The rule is simple and must be applied everywhere: kit availability is the minimum, across all components, of available stock divided by the quantity required per kit, rounded down.
Example: a kit contains 1 base station, 2 batteries and 4 special screws. Available stock: 50 stations, 90 batteries, 120 screws. The calculation gives 50 for stations, 45 for batteries (90 divided by 2) and 30 for screws (120 divided by 4). The limiting component is the screw: you can sell 30 kits, not 50.
Three points call for attention:
- Available stock, not physical stock. Deduct quantities already reserved (open orders, transfers) and, where relevant, safety stock. A component shared between several kits and single-unit sales is reserved only once: the first validated order takes the stock, and later ones see availability drop.
- Shared components. If two bundles use the same battery, the availability of each must be recalculated on every movement. A figure frozen at the start of the day leads to overselling.
- Mix of assembled kits and loose components. If assembled kits are in stock, total availability is: available assembled kits, plus what free components allow you to assemble.
On the replenishment side, the supply plan must work on components, not on the virtual kit, which has no stock. For an assembled kit, components are required at the assembly date, so the requirement must be shifted by an assembly lead time. Our guide on initial inventory and cycle counting explains how to keep these quantities reliable, because a kit amplifies errors: one wrong component blocks or distorts the sale of the entire bundle.
Pricing, discounts, kit margin and revenue allocation
Three pricing policies
- Sum of components: the kit price is the sum of catalog prices. Simple, but with no promotional effect.
- Fixed kit price: the price is entered on the bundle. This is the most common, and the one that demands the most rigor in accounting.
- Discount on the sum: a percentage applied to the total of the components. Convenient in B2B, where discounts are already managed by customer.
Allocating revenue across components
When the bundle sells for €89 and the sum of catalog prices is €110, the ERP must spread the €89 across the components, generally pro rata to their catalog prices. This allocation feeds:
- revenue by product family and by analytical dimension (otherwise the “accessories” family is overstated or understated depending on promotions);
- margin by component, needed to decide whether the bundle stays profitable;
- sales commissions, often calculated by family.
In the “virtual kit” model, allocation is native in several ERPs, because the line is exploded at delivery or invoicing. In the “composite item” model without explosion, allocation must be configured explicitly, otherwise all the revenue stays on the bundle item.
Multiple VAT rates
A mixed bundle can group products with different rates, for example a book and an accessory. In that case, VAT cannot be applied at the bundle’s rate as a whole without analysis. Depending on the country and on how the transaction is characterized (a single supply or a set of distinct supplies), treatment differs. Two options are common:
- Splitting the invoice by component, each with its own rate, based on the price allocation above;
- A single rate if the transaction can be characterized as a single supply.
This characterization is a tax question, not a software option: have your accountant or tax advisor validate it before locking the configuration, then set up the ERP to apply it with no manual intervention.
Returns and after-sales: partial kit return, itemized credit note
Returns are where a poorly chosen model costs you. A customer returns just one item from a bundle. Three consequences:
- What refund? The price of the returned component is calculated from the bundle’s price allocation (pro rata), not from the catalog price, otherwise the customer is refunded more or less than they paid. A rule written into the terms of sale prevents disputes: for example, the bundle discount is forfeited if a component is returned.
- What credit note? The credit note must reproduce the itemized lines of the original invoice, with the right VAT rate per component. Hence the value of splitting the invoice.
- What stock? The returned component goes back into stock (or into quarantine) at its own cost. With an assembled kit, a partial return requires disassembling the kit, which the ERP should support through a disassembly order, or failing that a traced adjustment.
Serial numbers and lots. If a component is tracked, the exploded kit must keep the serial number or lot per component and per delivery line. Otherwise a product recall or warranty claim cannot find the customer. Check that at delivery the ERP forces entry of the component’s serial number, not just the bundle’s.
Synchronization with the online channel
This is where stock diverges most often. Web shops (Shopify, WooCommerce, PrestaShop) and marketplaces manage their own notion of pack or bundle, often with their own stock or stock derived from components, depending on the feature used. Three traps keep recurring:
- The bundle exists online as a product with its own stock, while the ERP manages a virtual kit with no stock. Result: the site shows 0 or an arbitrary value. Fix: the ERP calculates availability as the minimum across components and pushes it as the bundle’s stock, or the connector handles the composition explicitly.
- Components are also sold individually online. A component sale does not update the bundle’s availability, because the connector only recalculates the item sold. Fix: recalculate availability of every kit containing the component on each movement, or at short intervals.
- The order arrives with a bundle line but no components. The ERP must recognize the reference and explode it. If the online reference does not match the ERP’s, the order is imported as an unknown item and stock is not decremented. A controlled reference mapping is essential.
For the details of the ERP-to-shop dialogue, see our guide to ERP and e-commerce integration (Shopify, WooCommerce, PrestaShop). For stock consistency between stores and website, see our article on ERP for omnichannel retail and distribution.
Setup by ERP and implementation checklist
Odoo: Kit-type BoM
Create a Kit-type BoM on the sold item and list the components. The quote shows one line, the delivery lists the components, and the kit’s stock is driven by them (Odoo documentation). For a physical kit, use a standard manufacturing BoM and a manufacturing order. Check how kit valuation is calculated in your configuration (standard or average cost) before going live.
Strengths. Native and quick to set up: no development is needed for a virtual kit, and the same BoM mechanism covers both the virtual and the physical kit. Limits. Valuation and the way kit cost flows into margin depend on the costing method and the version, so test them on a real order. Revenue allocation across components is not always what finance expects out of the box. Target fit. SMEs and mid-market companies that want a fast rollout and sell mostly catalog bundles, with or without a web shop.
Business Central: assembly BOM
On the item card, the “Assembly” replenishment system links the item to an assembly BOM. With assemble-to-order, a sales line automatically creates an assembly order whose lines mirror the BOM; with assemble-to-stock, you prepare kits in advance (Microsoft documentation). The walkthrough on selling, assembling and shipping kits illustrates the full flow.
Strengths. Both assemble-to-order and assemble-to-stock are native, so you can choose per bundle family between a virtual-like flow and a prepared physical kit. The assembly order leaves a clear audit trail. Limits. Selling a kit creates an assembly order, which adds a step and requires someone to own assembly and its capacity. Pure virtual kits with no assembly step are less natural. Target fit. SMEs already on Business Central that pack or assemble sets in their own warehouse and want traceability of each assembly.
SAP: sales BOM
On the kit’s material master, the item category group (for example LUMF) indicates that the structure is exploded into components in the sales order, with pricing, stock and delivery at component level. The BOM must have the “sales and distribution” usage, and the explosion scope (one level or several) is set in item category determination (SAP Community explanation). The limits of this model, notably around header item pricing, should be tested at design stage.
Strengths. The sales BOM is a long-standing, robust mechanism: pricing, stock and delivery happen at component level, and it fits high-volume order processing in an existing SAP landscape. Limits. Configuration is technical (item category groups, BOM usage, explosion scope), and header-level pricing and discounts need careful design. Changes depend on specialist skills. Target fit. Large companies and mid-market groups with SAP already in place and a team able to maintain master data and item category determination.
Implementation checklist
- Choose the model (virtual, assembled, composite) per bundle family, based on volume and packaging.
- Ban “catch-all” items: every bundle has a BOM, every component has a stocked SKU.
- Separate sales BOM and manufacturing BOM.
- Define the pricing policy and the revenue allocation rule (pro rata to catalog price in general).
- Have the VAT treatment of mixed bundles validated by your accountant or tax advisor.
- Calculate availability from the limiting component, on stock net of reservations.
- Configure partial returns: refund rule, itemized credit note, disassembly.
- Enforce serial and lot entry at component level.
- Map ERP and online channel references, and test the three synchronization cases (bundle sale, component sale, return).
- Review after one month: stock variances on components, margin per bundle, rejected credit notes.
The checks in point 10 are decisive: a poorly configured kit shows up in cycle counting, first as repeated variances on the same components.
Five mistakes to avoid
- Creating one “catch-all” bundle item without a BOM. Consequence: the components are never depleted, stock drifts from the first sale and cycle counts reveal it weeks later. Countermeasure: every bundle has a BOM and every component a stocked SKU.
- Using the manufacturing BoM as the sales BOM. Consequence: a production change (substitute component, new routing) silently alters what customers receive, or blocks a sale. Countermeasure: keep two separate structures with distinct owners.
- Calculating availability on total stock instead of net stock. Consequence: you promise bundles whose components are already reserved, which means backorders and cancelled web orders. Countermeasure: take the limiting component, on stock net of reservations.
- Ignoring revenue allocation and VAT by component. Consequence: wrong margin per bundle, wrong VAT on mixed-rate bundles, and credit notes that do not match the invoice. Countermeasure: define a pro rata allocation rule and have the VAT treatment validated by your accountant or tax advisor.
- Leaving the online channel to manage its own bundle stock. Consequence: the shop shows 0 or an arbitrary value, or sells a component that a bundle already consumed. Countermeasure: push the ERP-calculated availability, recalculate every kit on each component movement, and control reference mapping.
Going further
Get our next guides on stock, order management and e-commerce integration by subscribing to the newsletter. And to scope the web shop side of your project, read our guide to ERP and e-commerce integration.