All skills
wix avatar

/wix-manage

@4895cc9 official
by Wix.comwix/skills33 stars
33

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, payments, CMS, and more. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API, never write Wix dashboard URL from memory. Routes to: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, ricos rich-content, sites, blog, calendar, domains, events, site-properties, ecommerce, marketing, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-manage

This session only. Nothing lands on disk.

referencesecommercepricing-promotionsecom-pricing-goal-drive-cross-sells.md

≈1.8k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Goal: Drive Cross-Sells and Product Discovery

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 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.


Business Goal

Goal ID: BUNDLE_AND_SAVE

The merchant wants customers to explore more of the catalog and purchase multiple items per order. This is achieved through minimum item quantity conditions that incentivize buyers to add more products, particularly in categories with natural cross-sell relationships.


KPIs

KPI Definition How to measure
Items per order Average number of line items per completed order Order data: total items / total orders
Cross-sell rate Percentage of orders containing items from 2+ categories Analyze order composition across categories
Category diversity per order Number of distinct categories represented per order Track unique categories per order before and after
Bundle discount redemption Orders meeting the minItemQuantity condition / total orders Count qualifying orders vs total

Triggers

Activate this goal when the merchant expresses any of the following intents:

  • "bundle"
  • "cross-sell"
  • "buy together"
  • "product discovery"
  • "multi-buy"
  • "encourage people to buy more items"
  • "sell accessories with main products"
  • "increase items per order"
  • "mix and match"
  • Any request about getting customers to explore more of the catalog

Recommended Actions

Primary: Flow: Bundle & Save Campaign

The sole action for this goal. Creates a percentage discount with a minItemQuantity condition that activates when the customer adds enough items to their cart.

When to use: Whenever the merchant wants to incentivize multi-item purchases, cross-category exploration, or product discovery.

Key mechanics:

  • minItemQuantity condition (typically 2-3 items based on catalog profile)
  • Scope determines which products count toward the bundle:
    • CATEGORY — items from a specific category (best for focused cross-sell)
    • ITEMS — specific complementary products (best for curated bundles)
    • SITE — any items in the store (broadest reach)
  • Discount percentage scaled to margin (10-20%)
  • Higher item thresholds for lower-priced catalogs, lower thresholds for premium catalogs

Catalog profile matching:

Catalog Type minItemQuantity Scope Example
Accessories + main products 2 CATEGORY (accessories) "Buy 2+ accessories, save 15%"
Wide catalog, many categories 3 SITE "Buy any 3 items, save 10%"
Curated complementary items 2 ITEMS (specific products) "Buy these together, save 15%"
Low-price items (avg < price_p25) 3-4 CATEGORY or SITE "Buy 4+, save 20%"
High-price items (avg > price_p75) 2 CATEGORY "Buy 2 premium items, save 10%"

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

  1. Record baseline items per order
  2. Record baseline category distribution per order
  3. Identify current cross-sell rate (orders with 2+ categories)

During campaign (weekly check-ins)

  1. Track items per order vs baseline
  2. Monitor bundle redemption rate
  3. Check margin impact — multi-item discounts compound with quantity
  4. Verify the minItemQuantity threshold is appropriate:
    • Redemption rate > 70% — threshold may be too low
    • Redemption rate < 5% — threshold may be too high or scope too narrow

After campaign (30-day assessment)

  1. Calculate items-per-order lift: (new_items_per_order - baseline) / baseline * 100
  2. Measure new category penetration — did customers discover categories they had not purchased from before?
  3. Assess AOV impact — bundling often increases AOV as a side effect
  4. Evaluate whether specific product combinations drove the most bundle completions
  5. Target benchmarks:
    • Items per order increase > 15% = strong result
    • Cross-sell rate increase > 10% = successful discovery

Decision Matrix

Scenario Approach Rationale
Store has clear accessory categories CATEGORY scope on accessories, minItemQuantity: 2 Natural cross-sell with main products
Broad catalog, no clear bundles SITE scope, minItemQuantity: 3 Encourages exploration across the entire catalog
Merchant names specific products ITEMS scope with those products Curated bundle matching merchant's intent
Low average price catalog Higher minItemQuantity (3-4) Lower price per item makes larger bundles feasible
High average price catalog Lower minItemQuantity (2) Customers less likely to buy 3+ expensive items
Merchant specifies quantities or discounts Honor merchant input User overrides always take priority

Source: SKILL.md on GitHub

1 warning1d4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The wix-manage skill is an extensive collection of management recipes for Wix sites, covering business solutions such as eCommerce, Bookings, SEO, and site provisioning. It utilizes official Wix REST endpoints and incorporates robust safety patterns, including mandatory user confirmation for sensitive operations and careful validation of site data before mutation.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4895cc9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
compatibility
Requires Wix REST API access (API key or OAuth).
  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

REST API operations for configuring Wix business solutions including stores, bookings, CMS, contacts, domains, and ecommerce. Routes to site setup, entity management (products, services, staff), bulk administrative operations, and server-to-server integrations across Wix's business app ecosystem.

Generated from the current SKILL.md.

Do I need API credentials to use these recipes?
Yes. The skill requires Wix REST API access via either an API key or OAuth token to execute any management operations.
Can I use these recipes to display data on my site frontend?
No. These recipes are for backend REST API operations only — site configuration, entity management, and administrative tasks. They do not cover frontend development or displaying data to users.
What business domains do these recipes cover?
The skill covers stores, bookings, payments, CMS, contacts, forms, media, apps, pricing plans, restaurants, rich content, sites, blogs, calendars, domains, and site properties.
Do these recipes handle OAuth authentication with external services like Google Calendar?
Yes. The external calendar integration recipe covers OAuth-based setup with Google Calendar, Microsoft Outlook, and Apple Calendar for bidirectional event sync.

Generated from the current SKILL.md. These answers refresh after source changes.