Which product boundaries should be set for fixed, promotions, and merchandising rules?
Plan fixed, configurable, or build-your-own bundles with component inventory, pricing, promotions, substitutions, fulfillment, returns, and merchandising rules. Treat fixed, configurable, and promotions as one operated product boundary. A credible first release makes merchandising rules observable and defines how exceptions involving returns are recovered.
Best for: Teams planning Bundle and Kit Ecommerce that need to agree on fixed, promotions, and merchandising rules before detailed scope.
The first release should connect fixed to merchandising rules and expose a clear recovery path for exceptions involving returns.
Good fit / poor fit
Test whether fixed and promotions require an operated product
This topic is specific enough when fixed has durable state, promotions changes that state, and the team can own exceptions around returns while observing merchandising rules.
Good fit when
Bundle and Kit Ecommerce needs a durable workflow connecting fixed, promotions, and observable evidence for merchandising rules.
People in the shopper role need a repeatable path from build-your-own bundles with component inventory through promotions.
The commerce team must govern configurable and intervene when exceptions involve returns.
Progress can be observed through merchandising rules, not merely visits or screen activity.
Choose a narrower model when
An existing tool or simple information surface can already handle fixed without owning its lifecycle.
configurable does not need separate permissions, history, or accountable state.
No operated workflow must connect build-your-own bundles with component inventory to promotions.
The team cannot yet name who resolves exceptions around returns or what evidence is needed for merchandising rules.
End-to-end workflow
Trace fixed through promotions and evidence for merchandising rules
Use one representative Bundle and Kit Ecommerce journey. Keep configurable, exceptions around returns, and manual operator work visible so the release boundary reflects the real product rather than an idealized happy path.
1
Frame Build-your-own bundles...
Shopper
A person in the shopper role enters with build-your-own bundles with component inventory and enough context to begin working with fixed.
Commerce team
The commerce team function defines eligibility, ownership, and the initial state for fixed.
Boundary question
Who may begin with build-your-own bundles with component inventory, and what makes fixed ready?
2
Establish Configurable
Shopper
A person in the shopper role creates, selects, or confirms configurable before progressing.
Commerce team
The commerce team function validates permissions, quality, and lifecycle rules around configurable.
Boundary question
Which version of configurable is authoritative, and which changes need history or review?
3
Operate Promotions
Shopper
A person in the shopper role moves through promotions with visible state, next actions, and feedback.
Commerce team
The commerce team function observes substitutions, stalled work, and interventions that cannot be safely automated.
Boundary question
Which state changes prove progress through promotions, and where does substitutions branch?
4
Handle Returns exceptions
Shopper
A person in the shopper role receives a clear recovery path when an exception involving returns interrupts the expected journey.
Commerce team
The commerce team function resolves the exception, records the result, and captures evidence for merchandising rules.
Boundary question
Who owns exceptions around returns, and what evidence is needed for merchandising rules?
First-release boundary
Scope the smallest release that makes merchandising rules observable
The first release of Bundle and Kit Ecommerce should connect build-your-own bundles with component inventory to merchandising rules before expanding every variant of fulfillment, integration, automation, or reporting need.
Prove in the first release
Name one primary shopper segment and the exact role of fixed in its journey.
Model the minimum state and permissions needed for configurable and build-your-own bundles with component inventory.
Implement one complete path through promotions, including the essential branch around substitutions.
Give the commerce team a practical way to detect, inspect, and recover exceptions involving returns.
Capture evidence of merchandising rules so the team can continue, narrow, or revise the product boundary.
Hold until evidence justifies it
Additional audiences, variants, and advanced permissions around fixed and configurable.
Automation, integrations, and optimization for fulfillment before the core workflow is reliable.
Sophisticated reporting or personalization beyond the evidence needed to verify merchandising rules.
Decisions that materially change effort
The number of roles and permission boundaries controlling fixed and configurable.
Lifecycle branches, approvals, reversals, and recovery paths across promotions and substitutions.
Operational exposure when exceptions involving returns occur repeatedly or at scale.
External systems that create, change, or depend on build-your-own bundles with component inventory or fulfillment.
Audit, accessibility, availability, localization, and support expectations attached to merchandising rules.
Trust, exceptions, and operations
Assign ownership for promotions, exceptions around returns, and merchandising rules
The interface for Bundle and Kit Ecommerce is only the visible layer. The operating model must also govern fixed, keep configurable trustworthy, and make recovery from exceptions involving returns practical.
Ownership of Fixed
The commerce team function needs explicit rules for creating, changing, and retiring fixed while keeping configurable consistent.
Who creates or approves fixed, and which roles may change it?
What happens when fixed and configurable disagree?
Which changes need history, notification, approval, export, or deletion controls?
Control of Promotions
Every important transition through promotions needs a visible owner, especially where substitutions changes the normal path.
Which states make progress through promotions visible to each role?
Where can substitutions be automated safely, and where is review required?
How is duplicated, abandoned, or contradictory work returned to a valid state?
Recovery for Returns exceptions
A credible release makes exceptions involving returns visible, gives the commerce team a workable response, and preserves evidence for merchandising rules.
What can the shopper do when an exception involving returns occurs without contacting support?
Which evidence does the operator need to investigate and resolve exceptions around returns?
Which signal demonstrates merchandising rules without relying on vanity metrics?
Useful next steps
Turn the planning boundary into an evidence-backed first release
For Bundle and Kit Ecommerce, use the WebShop guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.
Scope packaged services sold through ecommerce with eligibility, inclusions, add-ons, payment, redemption, booking, expiry, cancellation, and delivery evidence.
Plan configurable orders that enter production after purchase, including choices, validation, quotes, lead time, approvals, change windows, milestones, and delivery.
Planning basis and review
A complete catalog brief with room for deeper research
This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.
This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.