Validate bundle demand by recording the exact products, variants, quantities, all-or-partial preference, acceptable substitutions, target total, and expiry. Cluster compatible requests, evaluate allocation and economics, then offer only feasible combinations.
- A bundle request needs line-level evidence, not a free-text note.
- All-or-partial preference changes inventory allocation.
- Allocate discounts exactly across lines for audit and refunds.
- Recheck every component before checkout.
Capture the proposed basket precisely
Record each product, variant, quantity, and any allowed substitute. Ask whether partial fulfillment is acceptable and whether price applies to a line, item subtotal, or the full bundle. This prevents different requests from being grouped merely because they mention similar products.
Cluster only compatible requests
A useful cluster shares the relevant product set, timing, market, and commercial constraint. The merchant can use it to design a controlled campaign or supplier brief while preserving each shopper's individual request and consent history.
Keep checkout and refunds exact
When a total discount spans multiple lines, allocate integer minor units deterministically so the displayed subtotal, Shopify line values, attribution, and later refund corrections reconcile. Every component still needs live product and inventory validation.
Frequently asked questions
Can a shopper accept only part of a requested bundle?
Yes, if the original request permits partial fulfillment and the merchant's counter states the exact accepted lines, quantities, price, and expiry.
Should bundle demand automatically create products?
No. It should inform a merchant decision. Creating products, inventory commitments, or public promotions requires an explicit approved workflow.