A set is not always just another product row. If its components can also be sold separately, the store needs a clear rule for availability and fulfilment.
Compare platforms using the way your sets actually work. A fixed packaged set, a choose-your-own bundle and a set assembled from shared stock can require different arrangements.
Classify the bundle
Write what the customer receives and whether they choose any components. State whether the set is prepacked or assembled after ordering.
Then identify whether components are also available individually. This determines whether stock is independent or shared.
Do not assume that a platform's bundle label covers every structure. Ask for the exact behaviour you need.
Use a scarce-component example
Suppose a gift set contains one mug and two coasters. If there are five mugs and eight coasters reserved for this arrangement, at most four complete sets can be assembled.
That is an illustrative capacity calculation, not a claim about a particular builder. Ask the provider to show how its setup represents the limiting component.
If components are also sold separately, test the effect of one separate sale before accepting another set order.
Inspect customer choices
For a configurable set, check whether the buyer can select only valid combinations. The resulting record should identify each chosen component.
Avoid a generic notes field when it leaves staff guessing which items were selected or whether the requested combination is permitted.
If the bundle needs manual approval, communicate that before payment or acceptance according to your actual process.
Verify the price presentation
Show the complete set price and what it includes. If you display a saving against individual purchase, use a genuine, current comparison with matching contents.
Do not combine unrelated component prices to manufacture a discount claim.
Check whether optional additions change the total clearly and whether the merchant record preserves those additions.
Read the packing output
Ask another person to pack the fictional order from the record alone. They should know component names, quantities and any selected options.
A set title may be memorable but insufficient. “Celebration box” does not tell a packer which version or contents were agreed.
Check exports and printed views if those are used in daily work. The dashboard alone may not be the fulfilment surface.
Test unavailable components
Make one required component unavailable in a safe environment. Determine whether the set becomes unavailable, offers an approved alternative or moves into an enquiry process.
Silent substitution is not a valid stock solution. The customer needs to agree to a changed product.
Record any manual stock step and its owner. A small range can use a manual process, but it must prevent conflicting promises.
Consider changes to the set
If you replace a component for future sales, preserve the meaning of existing orders. Staff should not fulfil an older order using today's revised contents by accident.
Use versioned descriptions or another supported record method appropriate to the system.
Do not assume a current product page is a sufficient historical specification.
Compare standard and additional tools
Ask whether the required behaviour is native, needs an app or requires custom work. Include the setup, maintenance and support responsibility.
A visually appealing bundle page does not prove shared-stock handling. Conversely, a plain page may be operationally correct and only need design refinement.
Check the returned-item record
Ask how the business records an issue with one component without losing the identity of the whole set. The applicable return decision remains yours, but the record should make the affected piece and quantity clear. A bundle name alone may be insufficient for customer support.
Choose on the hardest ordinary case
Run a safe example that combines the actual choices, scarce component and packing output. Record the buyer result and the merchant action.
Choose the arrangement that keeps the promise, availability and component identity consistent. If no standard setup does so, consider a clearly limited manual process or a separately scoped implementation.
The goal is not merely to sell a set. It is to know exactly which pieces were promised and whether you can fulfil them together.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store