An ecommerce product bundle brief defines exactly what a customer receives when buying a kit, set or combined offer. For a Kenyan online store, an attractive bundle picture is only part of the work. The business must specify component quantities, permitted choices, stock behaviour and what happens when a customer changes their mind or one item becomes unavailable.
Discuss these rules with your ecommerce website development team in Kenya before approving the product page. A bundle should be a dependable offer that staff can fulfil, not a label applied to several unrelated products. The examples below are illustrative planning scenarios and do not claim any particular sales improvement.
This guide concerns the relationship between a bundle and its component products. Our product spreadsheet preparation guide covers the separate task of preparing a clean catalogue for import.
Identify which kind of combined offer you sell
Describe the offer in ordinary business terms. A fixed starter kit contains a defined set of items. A customer-built selection allows choices within agreed limits. A suggested combination may simply add several independent products to a basket. These can look similar in a design mockup while requiring different implementation and fulfilment rules.
Choose one representative offer for the initial discussion. For an illustrative stationery kit, list the notebook, pen and folder rather than saying “office bundle”. Record whether the customer may change the pen colour, add another notebook or remove the folder. Every allowed choice needs a clear result in the order.
Decide whether the bundle has its own identity. It may need a public name, internal reference and packing instructions even when stock is tracked through its components. Ask the developer how those records will appear to customers, administrators and any connected fulfilment system.
Prepare a component worksheet
Use one row for each component and allowed variant. Include its existing product identifier, required quantity, whether it is compulsory and any permitted replacement. Record the sale unit carefully. One pack containing several items is different from several individual units, especially when staff prepare an order from a packing list.
State the minimum and maximum selections where customers can build their own set. Explain whether choices can repeat and what happens when the same product is already in the basket separately. Do not rely on a product photograph to communicate these limits. The controls and final order summary should make them explicit.
Keep the worksheet connected to the catalogue owner. If a component is renamed, discontinued or replaced, somebody must review the bundle. Otherwise the website can continue selling a set whose description, product links and warehouse instructions no longer agree.
Define stock behaviour for the whole offer
Ask whether the components share stock with their individual product listings. If a notebook can be sold alone and inside a kit, decide how both uses affect availability. A separate quantity field on the bundle does not necessarily solve the problem of promising the same component to several buyers.
WooCommerce's Product Bundles owner guide describes component-level inventory behaviour, including reductions in the contents' stock when a bundle sells. Treat this as a capability to verify in the chosen configuration, not a guarantee that every similarly named plugin behaves identically. Ask for a demonstration using your actual component relationships.
Decide what happens when a required item is unavailable. The business might stop selling the kit, offer a clearly approved replacement or allow a backorder under stated conditions. Do not let the website silently remove the missing item while keeping an unchanged photograph and description of a complete kit.
Write the pricing rules before styling the offer
Choose whether the bundle has a fixed approved price or derives its price from component selections. State which optional additions change the total and whether a particular variant has a supplement. Keep the working specification free from guessed prices; the person responsible for the offer should approve the actual amounts.
Explain how discounts interact. If a customer applies a coupon or changes a quantity, decide which rules take precedence. The browser's displayed total should agree with the server-validated order total. Ask the developer to demonstrate both the customer screen and the saved order rather than approving only a visual price label.
Avoid unsupported saving claims. If the page says a kit costs less than buying separately, verify the comparison against the current eligible products and quantities. When individual prices change, assign someone to review that statement instead of allowing an old promotional calculation to remain indefinitely.
Make choices understandable on a phone
Show the included items and permitted selections in the order the customer needs them. A long set of dropdowns can become confusing when option names are similar. Use meaningful labels and make it clear which choices are required before the product can be added to the basket.
Review image behaviour for variants. If a customer selects a different colour or size, decide whether the main picture changes, whether the summary lists that choice and what happens when no matching picture exists. Do not show an unqualified picture of one option while quietly accepting an order for another.
Check error messages with realistic combinations. A customer who has selected too few items should be told what remains to choose. A customer whose selection becomes unavailable should understand how to continue without losing every earlier choice. These are acceptance requirements, not just optional visual refinements.
Keep the basket and packing record consistent
Agree how the bundle appears after it is added to the basket. The customer should be able to confirm the set name, component quantities and selected variants. If components appear as separate lines, the relationship to the parent offer should remain understandable rather than looking like accidental duplicate purchases.
Show the same representative order to the person who packs it. Can they identify the items and quantities without referring to the original website picture? If the system exports orders, check the exported fields too. A clear storefront does not prove that a downstream packing sheet preserves all selected options.
Specify edits after ordering. If staff can replace a component or amend a quantity, define who approves the change and how the customer is informed. Keep an accurate record of the accepted offer rather than allowing a later catalogue edit to rewrite what an earlier customer ordered.
Plan cancellations, returns and substitutions
Decide whether a return concerns the whole kit or an approved part of it. Have the responsible business team define its terms and explain how the operational and financial records should reflect the decision. Do not copy another store's policy or assume that an extension setting settles the business question.
For partial adjustments, ask how the system identifies the returned component and any allocated value. The original order, approved refund and stock movement should remain distinguishable. Our refund workflow brief covers that separate approval and verification process.
Add a substitution scenario to the specification if substitutions are allowed. Record what makes a replacement acceptable, who confirms it and what happens when the customer declines. A note saying “equivalent item may be supplied” is not enough guidance for a developer to invent the correct operational workflow.
Test a complete kit before launching the range
Prepare a small acceptance set with fixed components, selectable variants, an unavailable item and a mixed basket containing an individual component as well as a bundle. Include quantity changes and an applicable discount. Write the expected stock and price result before the demonstration so reviewers are checking the same behaviour.
Use sandbox payments or approved mocks in a controlled environment. Do not create misleading live sales or trigger fulfilment and advertising events simply to test the kit. Confirm the saved order and component counts as well as what appears on the customer's screen.
For a proposal, send the component worksheet, approved pricing rules, example pictures and fulfilment requirements. Request an ecommerce quotation with bundle configuration, stock checks and staff handover included. Start with a clearly defined offer and expand only when the team can maintain its catalogue and operational rules reliably.
Frequently asked questions
Is a bundle the same as a product variation?
Not necessarily. A variation usually identifies an option of one product, while a bundle can combine several products. Describe the business relationship before choosing the platform feature that represents it.
Can the same item sell alone and in several kits?
It can be a valid requirement, but shared inventory behaviour must be specified and demonstrated. Check the final component stock after representative orders and quantity changes.
Must every bundle have a discount?
No. A set can be useful because it provides a clear combination or easier ordering. Publish a saving only when the comparison is accurate and maintained.
What is the most useful starting document?
A component worksheet with quantities, variants, selection limits, pricing rules and stock relationships. It gives developers and fulfilment staff a shared description of the offer.
