A kit is only as available as its scarcest part. For every component, divide its on-hand stock by the quantity that goes into one bundle and round down: floor(stock ÷ qty per kit). The maximum number of bundles you can build is the minimum of those values across all components. For example, a kit needing 1 lamp and 2 cable organisers, with 64 lamps and 300 organisers, can build min(floor(64/1)=64, floor(300/2)=150) = 64 kits — the lamp is the limiter. The Bundle / Kit SKU Builder does this automatically and highlights the limiting component so you know what to restock first.

The sum of parts is Σ (component unit price × quantity per kit) — what the customer would pay buying everything separately. Set the bundle price below that so the bundle is the better deal: ecommerce bundling research puts the effective saving in a 10–25% range (often 15–20%) — enough to feel like a deal without eroding margin. The customer saving is sum of parts minus bundle price, shown as both an amount and a percentage. The tool also computes the bundle cost (Σ cost × qty), the margin ((price − cost) ÷ price) and the profit per bundle, and warns you if the price falls below cost or the bundle actually costs more than the parts.

A bill of materials (BOM) lists every component SKU in a kit and how many of each go into one bundle. It is the recipe for the parent SKU: the bundle cost is the sum of (component cost × quantity), the sum of parts is the sum of (component price × quantity), and the bundle’s availability is derived from component stock. The Bundle / Kit SKU Builder turns the components you enter into a BOM table and lets you export it as CSV to set the kit up in your store, marketplace or inventory system.

The Bundle / Kit SKU Builder helps you plan bundle/kit SKUs, their pricing and how many you can assemble from the stock you type in. It does not manage live inventory and does not push kits or BOMs to your store or marketplace — you export the CSV and set them up there. The suggested SKU is just a suggestion, so follow your own scheme and keep it unique. All arithmetic runs client-side: your component costs, prices and stock counts — which are commercially sensitive — are never uploaded, logged or stored, and the page works offline once cached. Just enter accurate figures and remember margins ignore marketplace fees and shipping unless you include them in the unit cost.