/wix-manage

Goal: Capitalize on Seasonal Events

Routing rule (READ FIRST). Any merchant query that mentions a holiday, cultural event, season, or specific date tied to a discount MUST load this recipe before any flow-* recipe. Do NOT route directly to Flow: Seasonal Promotion from the WixREADME index — this goal owns the priority rule ("holiday/event/date beats all other signals — even 'maximize revenue' / 'boost sales' must classify as SEASONAL when a date is named"), the event calendar, and the per-recommendation time-window presentation rules. 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-seasonal-promotion")

Do NOT skip this or defer it — the flow defines the event calendar, campaign window calculation, and discount-sizing logic required to produce correct seasonal recommendations.

Capitalize on holidays, cultural events, and seasonal moments to drive revenue spikes through time-limited promotional campaigns.

Business Goal

Goal ID: SEASONAL

The merchant wants to take advantage of a specific event or season to boost sales. This is achieved through time-bound discount campaigns that create urgency and align with customer purchasing behavior during peak shopping periods.

KPIs

Triggers

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

• "Black Friday"
• "Christmas sale"
• "seasonal"
• "holiday discount"
• "New Year sale"
• "Valentine's Day"
• "summer sale"
• "back to school"
• "end of season"
• Any date-related promotion request
• Any mention of a specific holiday or cultural event tied to a discount

Proactive Detection

If current_date is within 30 days of a major shopping holiday, auto-suggest a seasonal campaign:

When proactively suggesting, frame it as an opportunity rather than a requirement:

"Black Friday is {N} days away. Would you like to set up a promotional campaign to capitalize on the increased shopping traffic?"

Recommended Actions

Primary: Flow: Seasonal Promotion

For planned, scheduled events where the merchant has lead time. Creates a discount with defined start and end dates aligned to the event window.

When to use:

• The event is more than 48 hours away
• The merchant wants a structured campaign with specific dates
• The promotion should run for multiple days (e.g., a week-long sale)

Key mechanics:

• Time-bounded discount with explicit start/end dates
• Scope can be CATEGORY (seasonal products), ITEMS (featured products), or SITE (store-wide event)
• Discount percentage calibrated to margin and event significance

Secondary: Flow: Run Flash Sale

For quick, high-urgency promotions with short windows (24-72 hours). Creates immediate impact with deeper discounts and tighter time constraints.

When to use:

• The event is imminent (within 48 hours)
• The merchant wants a short burst of urgency-driven sales
• Flash sale format (limited time, deeper discount) suits the event
• Last-minute seasonal opportunity

Key mechanics:

• Short duration (typically 24-48 hours)
• Can use deeper discounts than standard campaigns due to limited exposure
• Urgency messaging: "24-hour flash sale" or "ends midnight"

Presentation requirement — every recommendation MUST carry a time window

Every seasonal recommendation presented to the merchant MUST include an explicit campaign window in its reasoning / why field — either startDate + endDate in the rule params, or a duration phrase in the human-readable reasoning. The merchant must be able to see, per recommendation, when it activates and when it expires.

Acceptable phrasings:

• "Runs Nov 25 – Dec 1 (Black Friday weekend)."
• "Campaign window: 7 days starting Dec 18; ends Christmas Eve."
• "Active from event launch through Cyber Monday (Nov 28)."

A seasonal recommendation with no time window is NOT acceptable — even if everything else is correct, the absence of a window means the discount runs indefinitely and defeats the seasonal framing. If you cannot determine a window for an item, drop it; never present a windowless seasonal recommendation.

Measurement Plan

Before campaign launch

1. Record baseline revenue for the same period (prior week or prior year if available)
2. Record baseline conversion rate and traffic
3. Note the campaign window (start date, end date)

During campaign

1. Monitor revenue daily against the campaign target
2. Track conversion rate vs baseline
3. Check inventory levels for promoted products — adjust if selling out too fast
4. Monitor discount stacking risks if other active promotions exist

After campaign (within 7 days of end)

1. Calculate campaign revenue lift: (campaign_revenue - baseline_revenue) / baseline_revenue * 100
2. Compare conversion rate during campaign vs baseline
3. Assess whether the event-specific timing maximized impact
4. Calculate ROI: incremental revenue vs margin cost of discounts
5. Document learnings for next seasonal event:
   • Was the discount depth appropriate?
   • Was the campaign window too long or too short?
   • Which product scope performed best?

Decision Matrix