Kitting & Product Bundling in Ecommerce | Pipe17
Kitting and Product Bundling in Ecommerce
Product bundling and kitting describe 2 sides of the same sale. Bundling defines the offer a customer buys. Kitting defines how a warehouse or 3PL prepares its components for fulfillment. Both sides depend on the same component list, from available-to-sell inventory through pick instructions and fulfillment updates.
How kitting and product bundling fit together
Merchandising owns bundling and decides what the customer buys together. Fulfillment owns kitting and decides how the component products become an order-ready set.
What is product bundling?
Ecommerce product bundling is the practice of selling 2 or more products together as a single offer. The customer sees the set and its price. The seller still counts each component because the same product may also be sold alone or used in another bundle.
What is kitting?
In ecommerce, kitting means grouping or staging component products so a fulfillment team can ship them as an order-ready set. The warehouse can assemble repeatable kits before orders arrive or keep the products separate until a customer places an order.
Kit vs bundle
The useful kit vs bundle distinction is process versus offer. Kitting is how a warehouse prepares the components. A bundle is what a seller merchandises.
| Product bundling | Kitting | |
|---|---|---|
| Primary decision | Which products should the customer buy together? | How should the warehouse prepare those products? |
| Owner | Merchandising or ecommerce team | Warehouse, 3PL, or fulfillment team |
| Timing | During offer and catalog setup, before the customer buys | Before orders arrive or after an order is placed |
| Inventory question | How many complete bundles can the available components support? | Are components stocked separately or committed to finished kits? |
| Operational output | A sellable offer tied to a component list | Pick, assembly, packing, and labeling instructions |
Sellers and platforms use different names for bundles and kits. Warehouses and 3PLs do too. The handoff needs each component SKU and quantity. It also needs assembly and packing steps, label requirements, and exception rules.
Product bundling examples and a pre-launch checklist
A product bundling strategy starts with a clear reason for the customer to choose the set.
Complementary set. Products that solve one job together, such as a device with the accessories needed to use it.
Starter set. A core product plus the first supplies or refills a new customer needs.
Quantity pack. Several units of the same product sold as one offer.
Seasonal or gift set. A temporary selection packaged for a holiday or another gift occasion.
Customer reason Give the set one clear job so the buyer understands why the products belong together.
Component readiness Confirm that every required product is available in the quantity the bundle needs.
Warehouse work Include the assembly labor and extra materials the finished set requires. Add storage when kits are built in advance.
Return path Decide whether the customer returns the whole set or individual products, then give the warehouse the matching inspection instructions.
How product bundling pricing works
Product bundling pricing starts with the combined price of the products sold separately. That total is a reference point, not the automatic amount to charge. For a bundle intended to protect contribution margin, the final price also needs to cover the direct cost of assembling and fulfilling the set.
reference price = sum of individual item prices
amount left after direct bundle costs = bundle price โ component cost โ kitting and packaging cost
Test the price against 4 checks:
Customer value. Ask what time or effort the set saves compared with finding and ordering each product separately.
Margin floor. Include component cost plus the labor and materials required to assemble the set. Add storage and return handling where they apply.
Promotion goal. Decide whether the bundle should introduce a product or increase units per order. For replenishment sets, test whether the offer makes a repeat purchase easier.
Standalone demand. Compare the incentive with actual order and return data. A discount loses margin when buyers would have purchased the same products at full price.
Kitting in warehousing: pre-kit or assemble to order
Ecommerce bundle programs can use 2 warehouse kitting models. A fulfillment team pre-kits repeatable sets before orders arrive or assembles each set after an order is placed. The order-time model is also called on-demand kitting or kit-to-order.
Fulfillment kitting tradeoffs
| Pre-kitting | On-demand kitting | |
|---|---|---|
| Best fit | Repeatable sets with predictable demand | Sets that vary or sell at lower volume |
| Pick work | The finished kit is ready to pick | Components must be picked and grouped for the order |
| Inventory tradeoff | Components move into finished kits earlier | Components remain available to other bundles longer |
| Operational pressure | Forecasting and storage for assembled kits | Assembly labor inside the order cutoff |
Finished-kit inventory. Pre-kitting moves component units into a finished set before the sale. Once the warehouse records that set as its own inventory, the storefront must stop treating the same units as loose components. Otherwise the finished kit and its components appear available at once.
Component-derived inventory. When the finished set remains tied to component availability, the warehouse's consumption report must reduce the same component counts the storefront uses.
What kitting services should handle
Kitting services turn a seller's bundle definition into repeatable warehouse work. The seller defines the offer. The kitting partner turns its components into a job the warehouse can repeat.
Seller's bundle program.
One customer-facing offer that sets the price and promised contents under a bundle identifier.
Warehouse kitting work.
A component-level job with component SKUs, quantities, and assembly timing. The warehouse also needs packing materials, label instructions, and a record of what it used or could not complete.
Before the first order arrives, the seller and kitting partner should assign responsibility for:
- Receive and count each component The seller needs to know what remains sellable alone and inside every bundle.
- Follow the assembly timing Specify which sets are pre-kitted and which stay separate until an order arrives.
- Pack and label the finished set Give the warehouse the materials and instructions required for a consistent result.
- Report consumption and exceptions Record which products were used, then flag a shortage before an incomplete set reaches packing.
- Return usable inventory Define whether returns stay assembled or are inspected by component before sellable products go back into inventory.
- Exchange usable order data Confirm whether the warehouse accepts a parent bundle SKU, component lines, or both.
When Pipe17 connects a brand with the 3PL performing its kitting, the handoff works in both directions. Orders and component instructions go to the warehouse. Inventory changes and exceptions return with fulfillment status and tracking.
How bundle inventory works
When sellable bundle counts come from component inventory, the product that runs out first sets the limit. Divide each component's available quantity by the units required per bundle, then round down. The lowest result is the number of complete bundles the seller can offer.
bundle availability = minimum of floor(available component quantity รท units required)
Suppose a bundle uses the component recipe below.
| Component | Available | Required per set | Sets supported |
|---|---|---|---|
| Bottle | 12,000 | 1 | 12,000 |
| Refill | 15,000 | 2 | 7,500 |
| Case | 9,500 | 1 | 9,500 |
Refills are the limiting component, so the travel set has 7,500 units available.
One shared component changes several bundle counts
Inventory events. For component-derived bundles, a sale reduces the count of each product in the component list. A replenishment receipt adds units back. Returns and manual corrections create inventory adjustments too. Each change requires a new available-to-sell quantity for every bundle that uses the component.
Eligible inventory. Start the formula with inventory that is eligible to sell after location rules are applied and reservations or buffers are deducted. Pipe17's Inventory Visibility applies those rules to the component count before calculating bundle availability.
Shopify product bundling still has a warehouse side
Shopify product bundling starts with the storefront offer. For Shopify kitting to reach fulfillment correctly, the component list must also drive inventory availability and warehouse pick work. In the Pipe17 workflow, the Shopify integration connects the channel side of that handoff.
Storefront. Record which products and quantities make up the bundle the customer buys.
Availability. Calculate how many bundles remain sellable from the shared component inventory.
Warehouse. Send either a parent bundle SKU the warehouse recognizes or the component lines it needs to pick.
Writeback. Return fulfillment status and tracking in the bundle-level representation Shopify expects.
For Shopify bundles tied to shared components, a sale reduces those product quantities. Every bundle that uses them needs a new sellable count.
The warehouse needs the correct component list. Shopify receives status and tracking tied to the bundle it sold. If one step describes a different set, the warehouse may pick the wrong products or the selling channel may reject the fulfillment update.
How Pipe17 keeps product bundling and warehouse kitting aligned
In configured bundle-decomposition workflows, Pipe17 turns the bundle sold in a channel into the component lines the warehouse picks. After fulfillment, Pipe17 returns status and tracking in the bundle-level update the channel expects.
Define the bundle.
Product Sync records the component products and quantities behind the bundle SKU.
Calculate available-to-sell.
Inventory Visibility calculates how many bundles remain sellable from eligible component inventory. For bundles tied to shared products, a sale reduces their available quantity and a replenishment receipt adds units back. Pipe17 records each inventory adjustment, then recalculates available-to-sell for every bundle that uses the product.
Translate the bundle into pick lines.
In workflows configured to decompose bundles for fulfillment, Pipe17 sends the component lines a warehouse or 3PL recognizes.
Return the bundle-level update.
In the same configured workflow, Pipe17 recomposes the resulting status and tracking data into the bundle-level update the selling channel expects.
The warehouse picks the component SKUs it recognizes. The selling channel receives the bundle status it expects. Pipe17 carries the translation, so the operations team does not have to rebuild order and tracking updates by hand.
Kitting and product bundling FAQ
Do product bundles need their own SKUs?
A product bundle does not need a new SKU in every platform, but each selling and fulfillment system must be able to match the offer to its component products. A selling channel may represent the set as a grouped offer. In Pipe17, Product Sync links the bundle SKU to its components and quantities so the warehouse receives the intended work.
What happens when bundles share the same component?
When a bundle's available-to-sell count remains tied to a shared component, that product limits every affected bundle. Sales and replenishment receipts change the component count. Returns and manual corrections do too. Inventory Visibility uses each adjustment to recalculate the affected bundled products.
Is pre-kitting better than on-demand kitting?
Neither pre-kitting nor on-demand kitting is better for every operation. Pre-kitting suits predictable, repeatable demand when faster picking justifies the storage and early component commitment. On-demand kitting keeps shared products available to other bundles longer, but puts more assembly work inside the order cutoff.
What bundle data should a 3PL receive?
A 3PL performing the kitting should receive a recognized bundle SKU, executable component lines, or both, based on the fulfillment workflow. Component-level work needs the SKU and quantity for each product, plus assembly and packing instructions that include the finished-set label. The 3PL should return what it consumed or could not complete.