Use a fixed employee gift kit when the complete set is the gift. Use a build-your-own bundle when choosing the components is an important part of the benefit—and your ordering and fulfillment process can enforce the rules. A useful middle ground is a kit with one interchangeable slot. Do not promise “choose any three” until you have checked every allowed combination, not just the attractive example on the landing page.
This decision comes after deciding to offer multiple items. A fixed kit might let someone choose a sweatshirt size without letting them replace the sweatshirt with a bag. A configurable bundle changes the contents themselves. Those two experiences can look similar in a sales demonstration while requiring different budgets, stock controls and packing instructions.
Brand Sauce publishes this guide and provides company-store services. The framework below is our editorial recommendation, not a claim that Brand Sauce or every store platform supports every configuration. Confirm exact products, destination coverage, implementation and quote-needed costs in a scoped proposal. Official documentation was checked October 24, 2026.
Choose the smallest amount of customization that solves the need
| Model | What employees choose | Best reason to use it | Main approval burden |
|---|---|---|---|
| Fixed kit | Only necessary variants, such as garment size | The items work together as a deliberate set | Approve the complete kit and variant coverage |
| Fixed core plus one choice | One item from an approved slot | One component creates most preference differences | Check each alternative with the shared core |
| Category-based bundle | One item from each named group | Preserve the kit's purpose while offering meaningful alternatives | Validate cross-category combinations |
| Open build-your-own bundle | Any permitted combination within explicit limits | Recipients have substantially different needs | Enforce count, cost, duplicates, availability and packing rules |
Start by identifying the objection you are trying to remove. If employees already own enough drinkware, replacing the mug may solve the problem without making every component configurable. If the set includes three unrelated objects, unrestricted selection may be more defensible—but ask whether a bundle is necessary at all.
For the earlier budget-allocation decision, see one premium employee gift versus a bundle. This guide addresses a different question: once you have chosen a multi-item benefit, who controls its composition and how do you deliver the selected set?
Write the selection rule before choosing the software
“Build your own welcome kit” is marketing copy, not an order specification. A provider needs a rule precise enough to reject an invalid order and explain why. Write it in ordinary language first, then check whether the proposed store can implement it without a manual workaround at every checkout.
An illustrative rule could be: “Choose one carry item and one desk item. Select size or color where shown. Each category is required; duplicate products are not allowed. The employer covers the approved combination and delivery to eligible addresses. This selection can be submitted once.” That is a different promise from “Choose any two items up to a spending limit.”
- Count: exactly two items, up to two, or one from each category?
- Duplicates: can someone choose two identical notebooks or two colors of one style?
- Variants: which sizes and colors are eligible within each component?
- Omissions: may someone decline one component without losing the rest?
- Payment: are upgrades allowed, and is an employee contribution ever required?
- Completion: must the entire selection happen in one order?
If omission is allowed, explain whether it creates any remaining entitlement. Do not let a “skip this item” choice accidentally imply cash value or a future order. Keep the rule visible during selection and in the final summary, rather than revealing it after someone has built a combination.
Verify bundle capability, not just a bundle-shaped page
A photograph of a box does not establish that a platform manages its components. Nor does a page with dropdowns establish that employees can swap products. Ask for a demonstration using your actual rule and representative variants.
For a concrete platform example, Shopify's bundle documentation distinguishes fixed bundles from mix-and-match bundles and states that its Shopify Bundles app does not support mix-and-match. That distinction is a reason to verify the specific implementation—not a reason to assume all Shopify stores lack configurable bundles.
Request the order record and fulfillment output from the demonstration. The person packing the gift should be able to identify the chosen components, quantities and variants without interpreting a screenshot or an employee's free-text note. Also test what happens when someone edits the cart after making a valid selection. A correct starting page is not enough if removing one component breaks the benefit at checkout.
Budget the combinations, not the average-looking kit
For a category-based bundle, calculate the cost of every permitted combination or apply a conservative bound that includes all relevant charges. Separate item and decoration costs from assembly, packaging and destination-dependent delivery. Use actual quotes; list unresolved costs as quote-needed rather than assigning convenient estimates.
Illustrative arithmetic, not a supplier quote: suppose a carry slot has two options costing $24 and $36, while a desk slot has three options costing $8, $12 and $18. The six merchandise combinations range from $32 to $54. With an assumed $6 assembly-and-packaging charge, the range becomes $38 to $60 before delivery and any applicable taxes or other charges. A $50 merchandise-and-packing allowance would not cover every allowed choice.
There are several honest fixes: fund the highest permitted cost, remove an incompatible combination, change the component list, or clearly offer an optional paid upgrade. A hidden restriction discovered at checkout is not a fix. If shipping depends on the selected components, destination or number of parcels, a single average shipping figure cannot prove that every combination stays within budget.
Recheck the economics when a component changes. Shopify's Bundles app documentation, for example, says that changing a component product's price does not automatically change the bundle price. It also documents component-level order SKUs. These are useful prompts for a provider demonstration; other implementations may behave differently.
Treat every required component as a possible bottleneck
A kit is only deliverable when its required parts are deliverable. Build a component register that records the exact variant, approved decoration, supply route, destination restrictions and replacement owner. Do not mark an entire category available because one product in it is in stock.
Illustrative capacity example: if every fixed kit requires one pouch and two notebooks, 40 available pouches and 65 available notebooks support at most 32 complete kits, assuming those units are usable, uncommitted and available to the same fulfillment route. That is not a forecast or an on-demand stock promise. It is a simple check that component quantities—not the number of gift boxes—constrain a finished set.
For configurable kits, shared components can compete across several options. Approving each bundle separately may allocate the same notebook inventory more than once. Ask how the system updates available combinations after other orders consume shared stock, and how it handles a component that becomes unavailable while a recipient is selecting.
Agree on a recipient-facing response: remove the unavailable option, offer a documented alternative, or pause submission pending assistance. Do not silently insert a different gift. A substitute must still satisfy the selection rule, budget and intended use of the other components.
Test physical compatibility as well as digital eligibility
Two individually approved gifts do not automatically make an approved kit. The largest permitted combination may need a different box. A mug can require protection that changes the packing layout. A folded garment can vary in packed volume across sizes. Review representative extremes rather than only the sample photographed for launch.
Use a small packing matrix: smallest combination, largest combination, most fragile combination, and any combination with a different fulfillment route. For each, record the package, protective materials, assembly steps and whether the intended presentation survives transit. These are review categories, not claims that every program needs a formal laboratory test.
Keep selection and shipping promises separate. A build-your-own bundle can be one benefit even when its components arrive separately; a fixed kit can also require consolidation before dispatch. If the recipient-facing promise is one box, obtain confirmation that every allowed combination can actually be assembled that way. Our one-box versus separate-shipment guide covers that downstream decision.
Make the chooser understandable without visual guesswork
Give each category a clear instruction, show progress through the required selections, and keep the selected set available for review. Distinguish choosing a product from choosing its size or color. Do not prefill a garment size simply to make the form appear complete.
The W3C Web Accessibility Initiative's guidance on grouping controls recommends grouping related form controls visually and in code, with clear group labels. Applied to a bundle chooser, a “Choose one carry item” group should remain understandable when navigated by keyboard or assistive technology, not only when viewed as a row of product cards.
Ask pilot reviewers to assemble a valid set, change one choice, identify an incomplete group and explain the final contents without assistance. Record where the interface is unclear. A progress indicator that says “two selected” is insufficient if both selections came from the same category and one required group remains empty.
Run a release test with deliberate invalid combinations
| Test case | Acceptance condition |
|---|---|
| One required category left empty | Submission stops with a clear explanation identifying the missing selection |
| Duplicate or excess item added | The published rule is enforced without silently changing the gift |
| Highest-cost permitted combination | Employer coverage and any optional contribution match the approved policy |
| Component becomes unavailable | The recipient sees an accurate next step before production release |
| Cart edited after building the kit | The resulting order is still valid or requires correction |
| Order reaches fulfillment | Each component, quantity, variant and packing instruction remains identifiable |
| One component needs replacement | Support can resolve that component without duplicating the whole benefit |
Keep the test order identifiers and outputs with the approved selection rule. The program owner approves the promise, the store operator verifies enforcement, and the fulfillment owner confirms the packing record. Do not treat three separate verbal assurances as an end-to-end test.
Choose bulk, on-demand or hybrid after defining the kit
Bulk preparation can be sensible for a known event quantity and a fixed, approved set. It can simplify assembly and make a consistent presentation easier to inspect before distribution. The tradeoff is committing to quantities and components before every recipient has chosen.
On-demand production can suit ongoing selection and variable apparel needs, but does not eliminate blank-stock limits, production time or the need for consolidation. A hybrid model can hold common components while producing selected apparel later. That adds responsibility for synchronizing the two flows and deciding how long an incomplete kit may wait.
Ask providers to quote the same allowed combinations and delivery promise across models. Compare total obligations, including assembly and exception handling—not an inexpensive component from one model against a fully delivered kit from another. Fewer configurable slots may be a better operational choice than an elaborate builder whose service requirements exceed the program's needs.
Frequently asked questions
Does a fixed kit mean everyone gets the same garment size?
No. The product set can be fixed while necessary variants remain selectable. Confirm that the full intended size range is included and that each chosen variant reaches fulfillment correctly.
Should employees be able to choose fewer items?
That can be a useful option when someone does not need every component. Define whether omission is final for that selection and whether it affects any remaining benefit. Do not invent a leftover balance the program cannot honor.
Is a build-your-own bundle cheaper?
Not inherently. Component mix, implementation, packing, delivery and support all matter. Compare scoped quotes and permitted combinations; customization alone proves neither savings nor higher recipient satisfaction.
What should we bring to Brand Sauce?
Bring the selection rule, component shortlist, destinations, delivery deadline and all-in budget boundary. Ask which combinations and fulfillment arrangements can be supported and which costs require a quote. For a simpler alternative, start with employee choice between complete gifts before committing to component-level customization.
