Update to Ecommerce Skills

{
  "description": "Use when pricing or promoting tickets, classes, workshops, bookings, or any event with dates and limited seats — e.g. \"how should I price the workshop\", \"early-bird discount or something else\", \"should I show sold-out dates\", \"only 12 seats left banner\", \"what goes on the ticket page\", \"how do I sell out this cohort\".",
  "included_files": [
    {
      "relative_path": "reference.md",
      "size_in_bytes": 1724
    }
  ],
  "name": "event-pricing",
  "skill_md_contents": "---\nname: event-pricing\ndescription: Use when pricing or promoting tickets, classes, workshops, bookings, or any event with dates and limited seats — e.g. \"how should I price the workshop\", \"early-bird discount or something else\", \"should I show sold-out dates\", \"only 12 seats left banner\", \"what goes on the ticket page\", \"how do I sell out this cohort\".\n---\n\n# Event pricing\n\nEvents are experiences: buyers decide on feelings, sold-out dates signal quality, and the wrong kind of scarcity turns the people who miss out against you. This skill is the delta versus `pricing`, `promotions`, `discounts`, and `product-page`. Ticket *price digits* still follow `pricing`; the payment form follows `checkout-ux`.\n\n## When to use\n\n- Setting a ticket, class, or booking price\n- Designing pre-sales, early-bird offers, and how dates or seats are shown\n\n## When not to use\n\n- Shared digit, gift, deadline, and depth rules in isolation → `pricing`, `promotions`, `discounts`\n- Product-page media and price position in isolation → `product-page`, `product-visuals`\n- Finding the price level people will pay → `price-research`\n- Checkout/payment fields for the ticket sale → `checkout-ux`\n\n## Inputs\n\nCollect, or state your assumption: the event, ticket price, and date(s); how far away the first date is; how many dates or slots and how many are sold out; any complementary item you can give; whether it is bought for enjoyment or for a functional outcome.\n\nMost events — workshops, concerts, retreats, cooking classes — are hedonic. Training bought for a functional result (exam prep, compliance) is the utilitarian exception.\n\n## Procedure\n\nOnly the rules that change for dated, capacity-limited events.\n\n1. **Rounded ticket price.** Experiences are bought on feelings, so $150 beats $149. Just-below only for a promotion price. Depth: `pricing`.\n2. **Show sold-out dates — up to 30% of them.** Mark them instead of hiding them; beyond ~30% people abandon. This is the event form of the sold-out-variant rule. Depth: `product-page`.\n3. **Deadline, not a seat-count, as the promotional lever.** \"Early pricing ends 30 Sept, 23:59 CET\" is fine. \"Only 12 seats left!\" as a marketing hook is not: people who miss a quantity-capped *offer* get angry and switch. Showing *accurate* remaining capacity as inventory (a seat picker, \"2 dates left\" in a list) is fine. Depth: `discounts`.\n4. **Pre-sales: gift, not early-bird discount, when the event is 3+ weeks out.** A bonus session, materials, or the recording at no cost. Within about a week, either works. Hedonic events tolerate long windows; functional ones should keep them short. Depth: `promotions`.\n5. **Human-labeled recommendations** for experiences (\"others also booked\"). Depth: `store-audit`.\n\nShared, unchanged: discount ≤ 40% and amount-vs-% by the 100 threshold; invented relevant special days; video and gaze-away on the ticket page; price below the image. Depth: `discounts`, `promotions`, `product-visuals`, `product-page`.\n\n## Worked example\n\nPottery studio, 8-week wheel class, plan: $149, 25% early-bird, \"Only 12 seats left\", sold-out Saturday hidden, algorithm \"recommended\" row.\n\n- **$150**, rounded.\n- Early-bird 8 weeks out → **glazing-masterclass recording at no cost**, dated deadline, no seat-count banner.\n- Show the sold-out Saturday, marked, if sold-out dates stay in the 10–30% band.\n- **\"Others also booked\"** instead of the algorithm label.\n\n## Output\n\n| Item | Value |\n|---|---|\n| Ticket price | $150 (rounded; hedonic) |\n| Dates shown | All 8; 2 marked sold out (25%) |\n| Pre-sale (8 weeks out) | Recording at no cost by a dated deadline |\n| Urgency copy | Deadline + reason + timezone; no seat-count promo |\n| Rejected | 25% early-bird, \"Only 12 seats left\", hidden sold-out dates |\n| Why | one line per choice |\n\n## Common mistakes\n\n- Keeping the early-bird discount because it \"gives a real reason to book now\" — 3+ weeks out, a gift converts better.\n- Dropping \"12 seats left\" only because it might be inaccurate — accurate or not, unit caps as a promo anger the people who miss out. Use a deadline. Accurate inventory in a picker is a different thing.\n- Hiding sold-out dates — they are the strongest quality signal on the page; show them, up to 30%.\n- Pricing at $149 to look cheaper — it signals a bargain, not an experience.\n\n## Quick reference\n\n| Situation | Do | Depth |\n|---|---|---|\n| Ticket price | Rounded | `pricing` |\n| Sold-out dates | Show, marked; 10–30% | `product-page` |\n| Promo urgency | Deadline, never a seat-count hook | `discounts` |\n| Pre-sale, 3+ weeks out | Gift, not early-bird | `promotions` |\n| Recommendations | Human label | `store-audit` |\n\nEvidence and effect sizes: see [reference.md](reference.md).\n"
}