Flow: Bundle & Save Campaign

Creates a discount that rewards customers for purchasing multiple items, encouraging product discovery and cross-selling. The discount activates when the cart contains a minimum number of items, and targets categories or products where bundling makes strategic sense.

Prerequisites

• Products exist in the catalog across multiple categories (siteData.hasCatalog === true, checked at context load)
• Categories with 2+ products suitable for bundling

Required APIs

• Create Discount Rule
• Query Discount Rules

Step 1: Use pre-loaded catalog data

Catalog analytics and product data are already in conversation context — do NOT re-fetch:

• siteData.catalogAnalytics — category groups with min(price), max(price), avg(profitMargin), count(). Loaded by the eCommerce Load Context.
• siteData.productCatalogData — per-product list sorted price DESC, ordersCount DESC for BUNDLE_AND_SAVE goal. Loaded by the run-a-sale orchestrator Step 5.

Extract the following from context:

• min_price, max_price — from the "All Products" group in siteData.catalogAnalytics
• avg_profit_margin — sets the discount ceiling
• count — catalog breadth; more products = more bundling options
• Top products by price and order count — from siteData.productCatalogData

Step 2: Analyze cross-sell patterns

Evaluate the catalog for bundling opportunities:

1. Category diversity: Look for categories with multiple products at complementary price points (e.g., a $50 main item + $15 accessories).
2. Price range suitability: Wide price ranges (large gap between min_price and max_price) suggest tiered bundles. Narrow ranges suggest quantity-based bundles.
3. High-margin categories: Categories with above-average profit margin are better candidates because the discount erodes less absolute profit.
4. Popular + discoverable: Pair best-selling products (high ordersCount) with lower-visibility products to drive discovery.

Step 3: Set minimum item quantity

Determine the minItemQuantity based on catalog characteristics:

Default to minItemQuantity: 2 if data is ambiguous.

Step 4: Select discount percentage

Scale the discount to the average margin, rewarding multi-item purchases without eroding profitability:

Verify that the discount respects the global cap of 25% and the minimum margin threshold of 15% (discount <= avg_profit_margin - 15%).

Step 5: Determine discount scope

Select the scope based on bundling analysis:

• CATEGORY (preferred): When analytics show a clear category with cross-sell potential — multiple products, high margin, complementary items. Target that category.
• ITEMS: When specific complementary products are identified for bundling (max 5 productIds). Use when cross-sell pairs are specific rather than category-wide.
• SITE: When the goal is store-wide multi-buy incentive. Less targeted but simpler.

Step 6: Convert category names to GUIDs (if CATEGORY scope)

If scope is CATEGORY, call getCategoryIds to convert category names to GUIDs.

• Never use category names as scope IDs — always use the GUID.
• Exclude the "All Products" system category.
• Max 3 categoryIds per discount rule.

Step 7: Run guardrail checks

Run the pre-create guardrails in Create Discount Rule → "Guardrails" before creating the rule. Bundle discounts are especially prone to scope-overlap stacking (a customer buying 3 items in a category with both a bundle discount and a catalog-wide sale gets both) and coupon stacking — present any conflicts to the merchant and confirm.

Step 8: Create the discount rule with minItemQuantity condition

Endpoint: POST https://www.wixapis.com/ecom/v1/discount-rules

Request — Buy 2+ items from a category, get 15% off:

Response:

Request — Buy 3+ specific items, get 10% off:

Save the returned id and revision for later management.

Step 9: Verify the rule is active

1. Query discount rules to confirm the new rule exists and is active: true
2. Verify the minItemQuantity condition is correctly set
3. Report to the merchant:

   "Bundle discount is live: {discount}% off when buying {minItemQuantity}+ items from {scope description}. This encourages customers to explore more products and increases items per order."

Branching logic

Error Handling

References

• Discount Rules API