@wix/agent-skills 1.11.0 → 1.13.0

package/skills/wix-manage/references/ecommerce/{flow-bundle-and-save.md → pricing-promotions/ecom-pricing-flow-bundle-and-save.md}

@@ -1,28 +1,16 @@
 ---
 name: "Flow: Bundle and Save"
-description: Creates a discount campaign promoting product discovery and cross-selling by requiring minimum item quantities. Targets high-margin categories with complementary products.
-layer: flow
-references:
-  - name: "Guardrail: Discount Conflicts"
-    path: ecommerce/guardrail-discount-conflicts.md
-    load: true
-  - name: "Setup: Discount Rules"
-    path: ecommerce/setup-discount-rules.md
-    load: true
+description: BUNDLE_AND_SAVE sub-flow — load [Goal: Drive Cross-Sells] FIRST (it owns classification and routing); this is a sub-step, NOT a direct entry from README.
 ---
 # Flow: Bundle & Save Campaign
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Guardrail: Discount Conflicts](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-discount-conflicts)
-> - [Setup: Discount Rules](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/setup-discount-rules)
+> **Before executing this skill**, read [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) with `ReadFullDocsArticle` — it contains the discount-rule mechanics **and** the pre-create guardrails (conflict/stacking, margin floor, %-sanity).
 
 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
 
-- Wix Stores installed on the site
-- Products exist in the catalog across multiple categories
-- Access to `getCatalogAnalytics` and `getProductCatalogData` tools
+- Products exist in the catalog across multiple categories (`siteData.hasCatalog === true`, checked at context load)
 - Categories with 2+ products suitable for bundling
 
 ## Required APIs
@@ -32,25 +20,18 @@ Creates a discount that rewards customers for purchasing multiple items, encoura
 
 ---
 
-## Step 1: Gather catalog data
+## Step 1: Use pre-loaded catalog data
 
-Call `getCatalogAnalytics` and `getProductCatalogData` concurrently to assess the catalog's bundle potential.
+Catalog analytics and product data are already in conversation context — do NOT re-fetch:
 
-**getCatalogAnalytics** call:
-```
-aggregates: min(price), max(price), avg(profitMargin), count
-```
-
-**getProductCatalogData** call:
-```
-ordered: price DESC, ordersCount DESC
-```
+- `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.
 
-Save the following values:
-- `min_price`, `max_price` — price range determines viable bundle combinations
+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 — identifies popular items for bundle anchoring
+- Top products by price and order count — from `siteData.productCatalogData`
 
 ---
 
@@ -118,29 +99,7 @@ If scope is CATEGORY, call `getCategoryIds` to convert category names to GUIDs.
 
 ## Step 7: Run guardrail checks
 
-**Run the Guardrail: Discount Conflicts checks before creating the rule.**
-
-1. Query existing active discount rules:
-
-**Endpoint**: `POST https://www.wixapis.com/ecom/v1/discount-rules/query`
-
-**Request**:
-```json
-{
-  "query": {
-    "filter": {
-      "active": true
-    },
-    "paging": {
-      "limit": 100
-    }
-  }
-}
-```
-
-2. Check for scope overlap with existing rules. Bundle discounts are especially prone to stacking — a customer buying 3 items in a category with both a bundle discount and a catalog-wide sale would get both.
-3. Check for coupon stacking risks.
-4. If conflicts found, present to merchant and get confirmation.
+**Run the pre-create guardrails in [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-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.
 
 ---
 

package/skills/wix-manage/references/ecommerce/{flow-seasonal-promotion.md → pricing-promotions/ecom-pricing-flow-seasonal-promotion.md}

@@ -1,30 +1,22 @@
 ---
 name: "Flow: Seasonal Promotion"
-description: Creates event-driven promotional campaigns tied to holidays or seasonal events. Uses country and date context to identify upcoming events, calculates optimal campaign windows, and targets relevant categories.
-layer: flow
-references:
-  - name: "Guardrail: Discount Conflicts"
-    path: ecommerce/guardrail-discount-conflicts.md
-    load: true
-  - name: "Setup: Discount Rules"
-    path: ecommerce/setup-discount-rules.md
-    load: true
+description: SEASONAL sub-flow — load [Goal: Seasonal Revenue] FIRST (it owns classification and routing); this is a sub-step, NOT a direct entry from README.
 ---
 # Flow: Seasonal Promotion
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Guardrail: Discount Conflicts](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-discount-conflicts)
-> - [Setup: Discount Rules](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/setup-discount-rules)
+> ⛔ **Routing gate — [Goal: Seasonal Revenue](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/goal-seasonal-revenue) must be loaded before this flow.**
+>
+> This flow is a sub-step, not a direct entry point. If you have not yet called `ReadFullDocsArticle` on [Goal: Seasonal Revenue](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/goal-seasonal-revenue) in this conversation, **stop and load it now**. The goal skill owns the SEASONAL classification rule, the time-window presentation requirement, and the priority rule that gates access to this flow.
+>
+> **Before executing this flow**, also read [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) with `ReadFullDocsArticle` — it contains the discount-rule mechanics **and** the pre-create guardrails (conflict/stacking, margin floor, %-sanity).
 
 Creates event-driven promotional discounts tied to holidays, shopping events, or seasonal milestones. The flow identifies upcoming events based on the site's country and current date, calculates optimal campaign start/end windows, and targets event-relevant product categories with appropriately sized discounts.
 
 ## Prerequisites
 
-- Wix Stores installed on the site
-- Products exist in the catalog
-- Access to `getCatalogAnalytics`, `getProductCatalogData`, and `getSiteData` tools
+- Products exist in the catalog (`siteData.hasCatalog === true`, checked at context load)
 - `current_date` available for event scheduling
-- Site `country` known for region-specific event mapping
+- Site `country` known for region-specific event mapping (`siteData.country`, loaded by eCommerce Load Context)
 
 ## Required APIs
 
@@ -82,27 +74,18 @@ For Black Friday + Cyber Monday, use a single extended window: start the precedi
 
 ---
 
-## Step 3: Gather catalog data
+## Step 3: Use pre-loaded catalog data
 
-Call `getCatalogAnalytics` and `getProductCatalogData` concurrently.
+Catalog analytics and product data are already in conversation context — do NOT re-fetch:
 
-**getCatalogAnalytics** call:
-```
-aggregates: sum(ordersCount), quantiles([0.5, 0.9], price), avg(profitMargin)
-```
-
-**getProductCatalogData** call:
-```
-ordered: ordersCount DESC
-```
-
-This sort order surfaces the best-selling products first — seasonal campaigns should lead with proven sellers to maximize revenue.
+- `siteData.catalogAnalytics` — category groups with `sum(ordersCount)`, `quantiles([0.5,0.9], price)`, `avg(profitMargin)`. Loaded by the eCommerce Load Context.
+- `siteData.productCatalogData` — per-product list sorted `ordersCount DESC` for SEASONAL goal. Loaded by the run-a-sale orchestrator Step 5.
 
-Save the following values:
-- `total_orders` — overall sales volume
-- `price_p50`, `price_p90` — price distribution for discount sizing
+Extract from context:
+- `total_orders` — `sum(ordersCount)` from the "All Products" group in `siteData.catalogAnalytics`
+- `price_p50`, `price_p90` — from quantiles in `siteData.catalogAnalytics`
 - `avg_profit_margin` — sets discount ceiling
-- Top products by sales volume
+- Top products by sales volume — from `siteData.productCatalogData`
 
 ---
 
@@ -160,30 +143,7 @@ If scope is CATEGORY, call `getCategoryIds` to convert category names to GUIDs.
 
 ## Step 8: Run guardrail checks
 
-**Run the Guardrail: Discount Conflicts checks before creating the rule.**
-
-1. Query existing active discount rules:
-
-**Endpoint**: `POST https://www.wixapis.com/ecom/v1/discount-rules/query`
-
-**Request**:
-```json
-{
-  "query": {
-    "filter": {
-      "active": true
-    },
-    "paging": {
-      "limit": 100
-    }
-  }
-}
-```
-
-2. Check for time overlap — seasonal promotions have defined windows, so check that no existing rule covers the same period on the same scope.
-3. Check for scope overlap — a seasonal category discount stacking with an existing catalog-wide discount could create unexpectedly deep combined discounts.
-4. Check for coupon stacking — seasonal events often have high coupon usage.
-5. If conflicts found, present to merchant and get confirmation.
+**Run the pre-create guardrails in [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) → "Guardrails" before creating the rule.** For seasonal campaigns the most relevant are **time overlap** (defined windows — ensure no existing rule covers the same period/scope), **scope overlap** (a category discount stacking with a catalog-wide one), and **coupon stacking** (seasonal events drive high coupon usage). Present any conflicts to the merchant and get confirmation.
 
 ---
 

package/skills/wix-manage/references/ecommerce/{flow-stock-mover.md → pricing-promotions/ecom-pricing-flow-stock-mover.md}

@@ -1,32 +1,18 @@
 ---
 name: "Flow: Stock Mover"
-description: Creates discount campaigns to clear slow-moving inventory by targeting products with high stock levels and low sales velocity. Uses deeper discounts proportional to inventory urgency.
-layer: flow
-references:
-  - name: "Guardrail: Discount Conflicts"
-    path: ecommerce/guardrail-discount-conflicts.md
-    load: true
-  - name: "Guardrail: Margin Protection"
-    path: ecommerce/guardrail-margin-protection.md
-    load: true
-  - name: "Setup: Discount Rules"
-    path: ecommerce/setup-discount-rules.md
-    load: true
+description: Stock-mover clearance sub-flow — load [Goal: Clear Inventory] FIRST (it owns the routing); this is a sub-step.
 ---
 # Flow: Stock Mover Clearance
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Guardrail: Discount Conflicts](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-discount-conflicts)
-> - [Guardrail: Margin Protection](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-margin-protection)
-> - [Setup: Discount Rules](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/setup-discount-rules)
+> **Routing rule (READ FIRST).** This recipe is a sub-step of [Goal: Clear Inventory](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/goal-clear-inventory). If you arrived here directly from the WixREADME index, load the goal recipe NOW before executing — it owns the velocity scoring, classification cues, and the per-recommendation presentation rules (including the **margin-floor guardrail** surfacing requirement).
+>
+> **Then** read [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) with `ReadFullDocsArticle` — it contains the discount-rule mechanics **and** the pre-create guardrails (conflict/stacking, margin floor, %-sanity).
 
 Creates a discount targeting slow-moving inventory — products with high stock levels and low sales velocity. The discount depth is proportional to how overstocked the product is, with deeper discounts for the most stagnant items. Margin protection guardrails are especially important here since clearance discounts tend to push closer to cost.
 
 ## Prerequisites
 
-- Wix Stores installed on the site
-- Products exist in the catalog with inventory (quantity) data
-- Access to `getCatalogAnalytics` and `getProductCatalogData` tools
+- Products exist in the catalog with inventory (quantity) data (`siteData.hasCatalog === true`, checked at context load)
 - Inventory tracking enabled for target products
 
 ## Required APIs
@@ -36,27 +22,18 @@ Creates a discount targeting slow-moving inventory — products with high stock
 
 ---
 
-## Step 1: Gather inventory and sales data
+## Step 1: Use pre-loaded catalog data
 
-Call `getCatalogAnalytics` and `getProductCatalogData` concurrently to assess stock levels and sales velocity.
+Catalog analytics and product data are already in conversation context — do NOT re-fetch:
 
-**getCatalogAnalytics** call:
-```
-aggregates: sum(quantity), sum(ordersCount), avg(profitMargin)
-```
+- `siteData.catalogAnalytics` — category groups with `sum(quantity)`, `sum(ordersCount)`, `avg(profitMargin)`. Loaded by the eCommerce Load Context.
+- `siteData.productCatalogData` — per-product list sorted `quantity DESC, ordersCount ASC` for STOCK_MOVER goal. Loaded by the run-a-sale orchestrator Step 5.
 
-**getProductCatalogData** call:
-```
-ordered: quantity DESC, ordersCount ASC
-```
-
-This sort order surfaces products with the most stock and the fewest sales first — the primary candidates for clearance.
-
-Save the following values:
-- `total_quantity` — total stock across catalog
-- `total_orders` — total sales across catalog
-- `avg_profit_margin` — average profit margin (sets discount ceiling)
-- Per-product: `quantity`, `ordersCount`, `price`, `name`, `id`, `categoryId`
+Extract from context:
+- `total_quantity` — `sum(quantity)` from the "All Products" group in `siteData.catalogAnalytics`
+- `total_orders` — `sum(ordersCount)` from the "All Products" group
+- `avg_profit_margin` — sets the discount ceiling
+- Per-product: `quantity`, `ordersCount`, `price`, `name`, `id`, `categoryId` — from `siteData.productCatalogData`
 
 ---
 
@@ -122,38 +99,7 @@ If scope is CATEGORY, call `getCategoryIds` to convert category names to GUIDs.
 
 ## Step 6: Run guardrail checks
 
-**IMPORTANT: Run both guardrail checks before creating the discount rule. Clearance discounts are the most likely to trigger margin warnings.**
-
-### 6a: Discount Conflicts
-
-1. Query existing active discount rules:
-
-**Endpoint**: `POST https://www.wixapis.com/ecom/v1/discount-rules/query`
-
-**Request**:
-```json
-{
-  "query": {
-    "filter": {
-      "active": true
-    },
-    "paging": {
-      "limit": 100
-    }
-  }
-}
-```
-
-2. Check for scope overlap. Clearance items that already have an active discount would stack — warn the merchant about combined discount depth.
-3. Check for coupon stacking risks. A customer combining a clearance discount with a coupon code could get an unexpectedly deep total discount.
-
-### 6b: Margin Protection
-
-This check is especially critical for clearance:
-
-- Verify `discount_percentage <= avg_profit_margin - 15%` for each candidate product.
-- If the discount would push effective margin below 15%, warn the merchant: "This clearance discount of {discount}% on {product_name} would reduce the effective margin to {remaining_margin}%. The minimum margin threshold is 15%. Proceed?"
-- If margin data is unavailable, apply extra caution — cap at 15% unless the merchant explicitly overrides.
+**Run the pre-create guardrails in [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) → "Guardrails" before creating the rule** (conflict/stacking, %-sanity, margin floor). Clearance is the **most margin-sensitive** case: discounts push closest to cost, so the margin-floor check (effective margin ≥ 15% unless the merchant overrides) is the one most likely to fire here — verify it per candidate product.
 
 ---
 
@@ -278,7 +224,19 @@ Save the returned `id` and `revision` for later management.
 1. Query discount rules to confirm the new rule exists and is `active: true`
 2. Verify the correct products or category are targeted
 3. Report to the merchant:
-   > "Clearance discount is live: {discount}% off {number_of_products} slow-moving items. These products had a velocity ratio of {avg_velocity}, indicating high stock relative to sales. Monitor inventory levels — once stock clears, consider deactivating the rule."
+   > "Clearance discount is live: {discount}% off {number_of_products} slow-moving items. These products had a velocity ratio of {avg_velocity}, indicating high stock relative to sales. **Margin floor enforced — effective margin stays ≥ 15% on every targeted SKU.** Monitor inventory levels — once stock clears, consider deactivating the rule."
+
+---
+
+## Presentation requirement — margin guardrail line is mandatory
+
+When generating recommendations for the merchant (whether persisted as PROPOSED via the tracking API or returned inline), **every clearance recommendation MUST include explicit margin-floor language in its `reasoning` / `why` field.** Examples:
+
+- "Discount keeps effective margin ≥ 15% (minMarginPct floor)."
+- "Pre-discount margin {X}%, post-discount {Y}% — above 15% breakeven floor."
+- "Margin protected: 20% off does NOT push `{product}` below the 15% floor."
+
+Urgency labels, stock level, capital tied up, and the "Why {N}%" velocity rationale are NOT substitutes — the merchant must see a per-item margin protection statement on every clearance line. If you cannot meet the floor at the velocity-tier discount, either reduce the discount or drop the item; never silently breach the floor.
 
 ---
 

package/skills/wix-manage/references/ecommerce/{flow-upsell-boost.md → pricing-promotions/ecom-pricing-flow-upsell-boost.md}

@@ -1,33 +1,17 @@
 ---
 name: "Flow: Upsell Boost"
-description: Creates a discount campaign to increase average order value by setting minimum subtotal conditions above current AOV. Uses margin-based discount tiers and targets high-margin categories.
-layer: flow
-references:
-  - name: "Guardrail: Discount Conflicts"
-    path: ecommerce/guardrail-discount-conflicts.md
-    load: true
-  - name: "Guardrail: Margin Protection"
-    path: ecommerce/guardrail-margin-protection.md
-    load: true
-  - name: "Setup: Discount Rules"
-    path: ecommerce/setup-discount-rules.md
-    load: true
+description: UPSELL_BOOST sub-flow — load [Goal: Increase AOV] FIRST (it owns classification and routing); this is a sub-step, NOT a direct entry from README.
 ---
 # Flow: Upsell Boost Campaign
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Guardrail: Discount Conflicts](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-discount-conflicts)
-> - [Guardrail: Margin Protection](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-margin-protection)
-> - [Setup: Discount Rules](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/setup-discount-rules)
+> **Before executing this skill**, read [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) with `ReadFullDocsArticle` — it contains the discount-rule mechanics **and** the pre-create guardrails (conflict/stacking, margin floor, %-sanity).
 
 Creates a discount that incentivizes customers to spend more per order by setting a minimum subtotal threshold above the store's current AOV. The discount percentage is scaled to the store's average profit margin, and the scope targets high-margin categories or products.
 
 ## Prerequisites
 
-- Wix Stores installed on the site
-- Products exist in the catalog with price data
-- Access to `getCatalogAnalytics` and `getProductCatalogData` tools
-- AOV data available from site metrics (revenue / ordersCount)
+- Products exist in the catalog with price data (`siteData.hasCatalog === true`, checked at context load)
+- AOV data available from site metrics (`siteData.aov`, loaded by eCommerce Load Context)
 
 ## Required APIs
 
@@ -36,27 +20,19 @@ Creates a discount that incentivizes customers to spend more per order by settin
 
 ---
 
-## Step 1: Gather catalog data and site metrics
+## Step 1: Use pre-loaded catalog data
 
-Call `getCatalogAnalytics` and `getProductCatalogData` concurrently to collect pricing, margin, and product data.
+Catalog analytics and product data are already in conversation context — do NOT re-fetch:
 
-**getCatalogAnalytics** call:
-```
-aggregates: count, quantiles([0.5, 0.75, 0.9], price), avg(profitMargin)
-```
-
-**getProductCatalogData** call:
-```
-ordered: price DESC, ordersCount DESC
-```
+- `siteData.catalogAnalytics` — category groups with `count()`, `quantiles([0.5,0.75,0.9], price)`, `avg(profitMargin)`. Loaded by the eCommerce Load Context.
+- `siteData.productCatalogData` — per-product list sorted `price DESC, ordersCount DESC` for UPSELL_BOOST goal. Loaded by the run-a-sale orchestrator Step 5.
+- `siteData.aov` — site-level AOV (revenue / ordersCount). Loaded by eCommerce Load Context.
 
-Also retrieve site-level AOV from `getSiteData` (AOV = revenue / ordersCount). Run the AOV sanity check: if AOV < price_p25, override with price_p50 as the effective AOV.
-
-Save the following values:
-- `effective_aov` — the validated average order value
-- `avg_profit_margin` — average profit margin across the catalog
-- `price_p50`, `price_p75`, `price_p90` — pricing quantiles
-- Top products by price and order volume
+Extract from context:
+- `effective_aov` — use `siteData.aov`; run AOV sanity check: if AOV < price_p25, override with price_p50 as effective AOV
+- `avg_profit_margin` — from the "All Products" group in `siteData.catalogAnalytics`
+- `price_p50`, `price_p75`, `price_p90` — from quantiles in `siteData.catalogAnalytics`
+- Top products by price and order volume — from `siteData.productCatalogData`
 
 ---
 
@@ -114,36 +90,7 @@ Max 3 categoryIds per discount rule.
 
 ## Step 6: Run guardrail checks
 
-**IMPORTANT: Run both guardrail checks before creating the discount rule.**
-
-### 6a: Discount Conflicts
-
-1. Query existing active discount rules:
-
-**Endpoint**: `POST https://www.wixapis.com/ecom/v1/discount-rules/query`
-
-**Request**:
-```json
-{
-  "query": {
-    "filter": {
-      "active": true
-    },
-    "paging": {
-      "limit": 100
-    }
-  }
-}
-```
-
-2. Check for scope overlap, time overlap, and coupon stacking risks with the planned upsell discount.
-3. If conflicts found, present to merchant and get confirmation before proceeding.
-
-### 6b: Margin Protection
-
-Verify that `discount_percentage <= avg_profit_margin - 15%` (minMarginPct). If the discount would push effective margin below 15%, warn the merchant.
-
-The global discount cap is 25%. Do not exceed this unless the merchant explicitly overrides it.
+**Run the pre-create guardrails in [Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) → "Guardrails" before creating the rule** — conflict/stacking (scope, time, coupon cross-stacking), the 25% cap, the 15% margin floor, and %-sanity. Present any warnings to the merchant and get confirmation before proceeding.
 
 ---
 

package/skills/wix-manage/references/ecommerce/{goal-clear-inventory.md → pricing-promotions/ecom-pricing-goal-clear-inventory.md}

@@ -1,22 +1,16 @@
 ---
 name: "Goal: Clear Inventory"
-description: Maps the STOCK_MOVER business goal to inventory turnover KPIs and clearance discount flows.
-layer: goal
-references:
-  - name: "Flow: Stock Mover"
-    path: ecommerce/flow-stock-mover.md
-    load: true
-  - name: "Guardrail: Margin Protection"
-    path: ecommerce/guardrail-margin-protection.md
-    load: false
+description: STOCK_MOVER clearance goal — always load BEFORE recommending any clearance / overstock / slow-stock / dead-inventory action.
 ---
 # Goal: Clear Slow-Moving Inventory
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Flow: Stock Mover](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-stock-mover)
+> **Routing rule (READ FIRST).** Any merchant query about clearing slow / overstocked / dead / stagnant inventory MUST load this recipe before any other clearance recipe. Do NOT route directly to [Flow: Stock Mover](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-stock-mover) from the WixREADME index — this goal owns the velocity scoring, discount tiers, **margin-floor guardrail**, and the per-recommendation presentation rules. The flow is a sub-step.
 >
-> **Related skills** (read with `ReadFullDocsArticle` if needed):
-> - [Guardrail: Margin Protection](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/guardrail-margin-protection)
+> ⛔ **MANDATORY — call this NOW before any API call or recommendation generation:**
+> ```
+> ReadFullDocsArticle("https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-stock-mover")
+> ```
+> The guardrail is also enforced in [Pricing: Create Discount Rule](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/pricing-create-discount-rule) → "Guardrails".
 
 Automate clearance discounts for products with high stock levels and low sales velocity, converting stagnant inventory into revenue before it becomes a carrying cost liability.
 
@@ -79,6 +73,21 @@ The sole action for this goal. Identifies slow-moving products using the velocit
 
 ---
 
+## Presentation requirement — surface the margin guardrail
+
+**Every clearance recommendation presented to the merchant MUST explicitly reference the margin-floor guardrail in its `reasoning` / `why` field.** Clearance discounts push closest to cost, so the merchant needs to see — per item — that the discount stays above the floor.
+
+Acceptable phrasings:
+- "Discount keeps effective margin ≥ 15% (minMarginPct floor)."
+- "Stays above breakeven — current margin {X}%, post-discount {Y}%, floor 15%."
+- "Margin protected: this discount does NOT push below the 15% floor on `{product}`."
+
+If a candidate item would violate the floor at the velocity-tier discount, **either** lower the discount to stay above the floor and say so, **or** drop the item and note "skipped — would breach margin floor."
+
+Do NOT present a clearance recommendation that omits margin language. Urgency / stock level / "why this %" are not substitutes — the guardrail line is required.
+
+---
+
 ## Measurement Plan
 
 ### Before campaign launch

package/skills/wix-manage/references/ecommerce/{goal-drive-cross-sells.md → pricing-promotions/ecom-pricing-goal-drive-cross-sells.md}

@@ -1,16 +1,16 @@
 ---
 name: "Goal: Drive Cross-Sells"
-description: Maps the BUNDLE_AND_SAVE business goal to multi-item purchase KPIs and bundling flows.
-layer: goal
-references:
-  - name: "Flow: Bundle and Save"
-    path: ecommerce/flow-bundle-and-save.md
-    load: true
+description: BUNDLE_AND_SAVE goal — always load BEFORE recommending bundling / cross-sell / multi-item / "buy together" actions.
 ---
 # Goal: Drive Cross-Sells and Product Discovery
 
-> **Before executing this skill**, read these referenced skills with `ReadFullDocsArticle`:
-> - [Flow: Bundle and Save](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-bundle-and-save)
+> **Routing rule (READ FIRST).** Any merchant query about cross-sells, bundling, "buy together", multi-item purchases, or items-per-order MUST load this recipe before any flow-* recipe. Do NOT route directly to [Flow: Bundle and Save](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-bundle-and-save) from the WixREADME index — this goal owns the catalog-profile→bundle-shape matrix and the **per-recommendation multi-item-structure requirement** (every recommendation MUST use `minItemQuantity` or an equivalent multi-item condition — plain single-item percent-off recommendations FAIL this goal). The flow is a sub-step.
+>
+> ⛔ **MANDATORY — call this NOW before any API call or recommendation generation:**
+> ```
+> ReadFullDocsArticle("https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/skills/flow-bundle-and-save")
+> ```
+> The flow defines the required discount-rule mechanics (minItemQuantity condition, catalog data steps, guardrails). Without it, your recommendations will lack the correct structure.
 
 Promote product discovery and multi-item purchases by creating bundle-based discounts that reward customers for buying across categories or adding complementary items to their cart.
 
@@ -81,6 +81,24 @@ The sole action for this goal. Creates a percentage discount with a `minItemQuan
 
 ---
 
+## Presentation requirement — every recommendation MUST carry a multi-item condition
+
+**Every cross-sell recommendation presented to the merchant MUST use a `minItemQuantity` (or equivalent multi-item) condition** — plain single-item percentage discounts FAIL this goal's intent. The merchant must be able to see, per recommendation, the quantity threshold that triggers the discount and the scope it applies to.
+
+Acceptable shapes:
+- `apply_discount` with `conditions.minItemQuantity: 2` (or 3, 4) scoped to a category or specific products
+- "Buy 2+ accessories, save 15%" — minItemQuantity 2 on the accessories category
+- "Buy any 3 items, save 10%" — minItemQuantity 3 site-wide
+- "Buy these 2 together, save 15%" — minItemQuantity 2 on ITEMS scope with specific productIds
+
+NOT acceptable for this goal:
+- "20% off accessories" — no quantity threshold, defeats the cross-sell mechanic
+- "Site-wide 10% off" — no multi-item incentive
+
+State the quantity threshold and scope per recommendation in the `reasoning` / `why` field (e.g., "Buy 3+ items → 10% off site-wide; targets the multi-category catalog profile"). If you cannot construct a multi-item condition for a candidate, drop it; never present a plain percent-off as a cross-sell recommendation.
+
+---
+
 ## Measurement Plan
 
 ### Before campaign launch