# Product Requirements Document

## Validation Checklist

- [x] All required sections are complete
- [x] No [NEEDS CLARIFICATION] markers remain
- [x] Problem statement is specific and measurable
- [x] Problem is validated by evidence (not assumptions)
- [x] Context → Problem → Solution flow makes sense
- [x] Every persona has at least one user journey
- [x] All MoSCoW categories addressed (Must/Should/Could/Won't)
- [x] Every feature has testable acceptance criteria
- [x] Every metric has corresponding tracking events
- [x] No feature redundancy (check for duplicates)
- [x] No contradictions between sections
- [x] No technical implementation details included
- [x] A new team member could understand this PRD

---

## Product Overview

### Vision
A unified Event Command Center that empowers store managers to orchestrate promotional events across all store systems—inventory, marketing, signage, coupons, and staff tasks—from a single dashboard, maximizing event success through coordinated execution and comprehensive performance tracking.

### Problem Statement
Store managers currently operate events (Back to School, Holiday Sales, etc.) using **fragmented, disconnected systems**:
- **Backstock events** manage inventory bin pulling separately
- **SMS marketing** triggers and blasts are configured in isolation
- **Digital signage** slides are scheduled without event context
- **Comeback Cash** coupons run on independent timelines
- **Staff tasks** and **admin notes** require manual coordination

**Pain points:**
1. **Manual coordination overhead**: Setting up a single promotional event requires navigating 5-6 different admin interfaces
2. **Timing misalignment**: SMS blast goes out before signage is updated, or coupons expire before event ends
3. **No unified visibility**: Cannot see at a glance what's running for "Back to School" across systems
4. **Reporting fragmentation**: Sales performance, marketing effectiveness, and inventory flow exist in separate reports
5. **Repeat setup burden**: Each year's Back to School event requires rebuilding everything from scratch

**Consequences:**
- Events underperform due to coordination gaps
- Staff confusion about event-specific procedures
- Marketing messages don't align with in-store experience
- Missed opportunities to drive incremental revenue
- Manager burnout from administrative overhead

### Value Proposition
The Unified Event Management system transforms event execution from fragmented chaos into orchestrated excellence:

1. **One Dashboard, All Systems**: Create and manage events that automatically coordinate backstock, SMS, signage, coupons, tasks, and notes
2. **Template Automation**: Pre-configured event templates (Back to School, Black Friday, etc.) auto-deploy all integrations with one click
3. **Timeline Visualization**: See everything scheduled for an event on a single timeline view
4. **Comprehensive Analytics**: Unified reporting showing sales lift, marketing ROI, inventory flow, and customer response in one place
5. **Year-over-Year Learning**: Event templates improve based on historical performance data

## User Personas

### Primary Persona: Store Manager (Sarah)
- **Demographics:** 28-45 years old, manages daily operations of a single resale store (Plato's Closet, Clothes Mentor, etc.), moderate technical expertise (comfortable with POS, basic admin tools)
- **Goals:**
  - Maximize sales and profitability during promotional events
  - Reduce time spent on administrative setup and coordination
  - Ensure staff knows what to do before, during, and after events
  - Track event performance to improve year-over-year results
  - Success = Events that run smoothly with measurable sales lift and minimal management overhead
- **Pain Points:**
  - Spends hours setting up the same event across multiple systems
  - Forgets to update one system (e.g., signage still shows old promotion)
  - Can't easily compare this year's Back to School to last year's
  - Staff asks "what should I be doing for this event?" repeatedly
  - No single place to see if event is on track

### Secondary Personas

#### District/Regional Manager (Mike)
- **Demographics:** 35-55 years old, oversees 5-15 stores, high business acumen, moderate technical expertise
- **Goals:**
  - Ensure consistent event execution across all stores
  - Compare event performance between stores
  - Push successful event templates to underperforming stores
  - Identify best practices from top-performing locations
- **Pain Points:**
  - No visibility into which stores have events properly configured
  - Cannot easily share event configurations between stores
  - Reporting requires pulling data from each store separately

#### Store Associate (Jamie)
- **Demographics:** 18-30 years old, part-time or full-time sales associate, limited technical expertise
- **Goals:**
  - Know what tasks are specific to the current event
  - Understand which promotions to communicate to customers
  - See event-related notes and instructions clearly
- **Pain Points:**
  - Doesn't know an event is happening until customer asks about promotion
  - Tasks appear but context is unclear ("Pull bins" - which bins? why?)
  - Information scattered across multiple screens/areas

## User Journey Maps

### Primary User Journey: Event Creation from Template
1. **Awareness:** Calendar reminder or corporate communication triggers need to plan upcoming seasonal event (e.g., Back to School in late July)
2. **Consideration:** Manager evaluates: "Do I have time to set up all systems manually?" vs "Can I use a template from last year?"
3. **Adoption:** Discovers Event Management dashboard in admin sidebar, sees "Create from Template" option with pre-configured Back to School template
4. **Usage:**
   - Select "Back to School" template from library
   - Adjust dates for this year (July 20 - August 31)
   - Review auto-populated integrations (SMS triggers, signage slides tagged "back-to-school", coupon schedules, prep tasks)
   - Customize as needed (add new slide, adjust coupon values)
   - Activate event with single confirmation
   - System auto-schedules all components with proper timing
5. **Retention:** Post-event reporting shows 15% sales lift; manager saves customized template for next year; reduced setup time from 3 hours to 15 minutes

### Secondary User Journeys

#### Journey: Custom Event Creation (No Template)
1. **Awareness:** Store plans unique event (e.g., "Grand Re-Opening Sale") not covered by templates
2. **Consideration:** Manager needs flexibility to configure each integration manually
3. **Adoption:** Uses "Create Custom Event" workflow
4. **Usage:**
   - Define event name, dates, and description
   - Optionally create backstock category/tag for event
   - Select or create SMS marketing triggers/blasts
   - Choose signage slides (filter by tags)
   - Configure Comeback Cash coupon schedule
   - Add event-specific tasks with due dates
   - Schedule admin notes for staff communication
   - Review timeline showing all scheduled items
   - Save as new template for future use
5. **Retention:** Successful event saved as template; available for other stores in franchise

#### Journey: Event Monitoring During Active Period
1. **Awareness:** Event is now active; manager wants to track progress
2. **Consideration:** "Is everything running as planned? Are we hitting targets?"
3. **Adoption:** Opens Event Dashboard, selects active event
4. **Usage:**
   - View real-time metrics: sales vs. target, SMS delivery stats, signage display count
   - Check backstock progress: bins pulled vs. needed
   - See task completion status across staff
   - Receive alerts if any component is behind schedule
   - Make mid-event adjustments if needed (extend coupon, send additional SMS blast)
5. **Retention:** Comprehensive visibility reduces anxiety; data-driven decisions improve outcomes

#### Journey: Post-Event Analysis
1. **Awareness:** Event has ended; manager wants to evaluate performance
2. **Consideration:** "Did this event meet goals? What should we do differently next year?"
3. **Adoption:** Opens Event Reporting for completed event
4. **Usage:**
   - View comprehensive report: sales lift, marketing ROI, inventory turnover
   - Compare to previous year's event (if available)
   - See which integrations performed best (SMS drove most traffic, etc.)
   - Review staff feedback from task comments
   - Export report for franchise review
   - Update template with learnings for next year
5. **Retention:** Historical data improves future event planning; templates evolve based on results

#### Journey: Staff Event Awareness (Associate Perspective)
1. **Awareness:** Jamie clocks in and opens the Workbook; sees "Back to School Event" banner/indicator on dashboard
2. **Consideration:** "What do I need to know about this event? What tasks are specific to it?"
3. **Adoption:** Clicks on event indicator or views task list filtered by event
4. **Usage:**
   - Sees event-specific tasks with clear context: "Pull Back to School bins from storage (Event: Back to School)"
   - Reads pinned event note with customer-facing messaging and promotions to communicate
   - Understands current Comeback Cash offer to explain to customers
   - Marks event tasks as completed, notes progress
5. **Retention:** Clear event context reduces confusion, improves task completion rate, better customer interactions

## Feature Requirements

### Must Have Features

#### Feature 0 (Phase 0 Prerequisite): Slide Tagging System
- **User Story:** As a store manager, I want to tag slides with categories so that I can quickly find and select relevant slides for events.
- **Acceptance Criteria:**
  - [ ] Can add multiple text tags to any slide (store, corporate, or partner)
  - [ ] Tags stored in new `dsSlide_Tags` table (store slides) and `corpSlide_Tags` / `hbSlide_Tags` (global)
  - [ ] Can filter slide library by one or more tags
  - [ ] Tags visible in slide list and selection interfaces
  - [ ] Corporate/partner slides can have pre-assigned tags by administrators
  - [ ] Tag management UI available in Digital Signage admin
  - [ ] Suggested tags auto-complete as user types

#### Feature 1: Central Event Entity (Event Hub)
- **User Story:** As a store manager, I want to create a single event record that serves as the coordination point for all promotional activities so that I can manage everything from one place.
- **Acceptance Criteria:**
  - [ ] Can create event with: name, description, event type (season/holiday/sale/custom), start date, end date
  - [ ] Event displays 5-phase lifecycle: upcoming → build_up → active → wind_down → completed
  - [ ] Build-up days and wind-down days are configurable per event
  - [ ] Event has color and icon for visual identification
  - [ ] Events can be marked as recurring (annual)
  - [ ] Can view all events in calendar/timeline view
  - [ ] Can filter events by status (active, upcoming, completed)
  - [ ] Can cancel event (status changes to "cancelled", all future scheduled integrations are deactivated)
  - [ ] Can delete event with cascade options: detach integrations (keep them running), or cascade delete (remove linked items)
  - [ ] Cancelled/deleted events remain visible in "Archived" filter for historical reporting
  - [ ] All event changes logged with timestamp and user (audit trail)

#### Feature 2: Event Dashboard
- **User Story:** As a store manager, I want a single dashboard showing all aspects of my event so that I can monitor progress without navigating multiple screens.
- **Acceptance Criteria:**
  - [ ] Dashboard displays event overview: name, dates, current phase, days remaining
  - [ ] Shows status of each integration (backstock, SMS, signage, coupons, tasks, notes)
  - [ ] Displays real-time metrics summary (sales, SMS sent, bins pulled)
  - [ ] Alerts panel shows items needing attention
  - [ ] Quick actions available: edit event, add integration, view full report
  - [ ] Mobile-responsive layout for on-floor access

#### Feature 3: Backstock Integration
- **User Story:** As a store manager, I want to link backstock categories to my event so that inventory preparation is coordinated with the promotion timeline.
- **Acceptance Criteria:**
  - [ ] Can link one or more existing backstock categories to event
  - [ ] Can create new backstock category/tag specifically for this event
  - [ ] Event dates auto-populate backstock event dates when linked
  - [ ] Dashboard shows bin pull progress (pulled/total)
  - [ ] Existing backstock event alerts integrate with event dashboard
  - [ ] Bin reservation count can be set for event

#### Feature 4: SMS Marketing Integration
- **User Story:** As a store manager, I want to schedule SMS blasts and triggers that align with my event timeline so that marketing messages go out at optimal times.
- **Acceptance Criteria:**
  - [ ] Can create SMS blast scheduled relative to event dates (e.g., "7 days before start")
  - [ ] Can create/enable SMS trigger active during event period
  - [ ] Event timeline shows scheduled SMS activities
  - [ ] Dashboard displays SMS metrics: queued, sent, delivered
  - [ ] Can select from existing message templates or create new
  - [ ] Preview recipients count before scheduling

#### Feature 5: Digital Signage Integration
- **User Story:** As a store manager, I want to schedule signage slides that automatically display during my event so that in-store messaging is synchronized.
- **Acceptance Criteria:**
  - [ ] Can select slides to include in event (from store, corporate, partner libraries)
  - [ ] Slide start/end dates auto-set to event dates when added
  - [ ] Can filter slides by tags (requires new tag system on slides)
  - [ ] Event timeline shows slide schedule
  - [ ] Slides automatically activate at event start, deactivate at event end
  - [ ] Dashboard shows signage status (active slides count)

#### Feature 6: Comeback Cash Integration
- **User Story:** As a store manager, I want to schedule promotional coupons that run during specific phases of my event so that I can drive traffic and increase transaction value.
- **Acceptance Criteria:**
  - [ ] Can create Comeback Cash event linked to store event
  - [ ] Can schedule buy-side coupon for pre-event period (increase inventory)
  - [ ] Can schedule sales-side coupon during event (increase sales)
  - [ ] Can schedule post-event coupon (drive return visits)
  - [ ] Event timeline shows coupon earning and redemption windows
  - [ ] Dashboard displays coupon metrics: issued, redeemed, revenue impact

#### Feature 7: Task System Integration
- **User Story:** As a store manager, I want to create event-specific tasks that appear to staff at the right time so that preparation and execution steps are not forgotten.
- **Acceptance Criteria:**
  - [ ] Can create tasks linked to event with relative scheduling (e.g., "3 days before start")
  - [ ] Tasks automatically calculate actual due dates based on event dates
  - [ ] Tasks display event context (which event they belong to)
  - [ ] Can create task groups specific to event phases (prep, active, cleanup)
  - [ ] Dashboard shows task completion progress
  - [ ] Staff workbook shows event tasks with clear event association

#### Feature 8: Admin Notes Integration
- **User Story:** As a store manager, I want to schedule staff communications that appear during the event so that important announcements reach the team at the right time.
- **Acceptance Criteria:**
  - [ ] Can create notes linked to event with scheduled visibility
  - [ ] Notes can be pinned for event duration
  - [ ] Notes can be manager-only or visible to all staff
  - [ ] Event timeline shows scheduled notes
  - [ ] Dashboard shows notes status (active count)

#### Feature 9: Event Templates
- **User Story:** As a store manager, I want to create events from pre-configured templates so that setup time is minimized and best practices are applied.
- **Acceptance Criteria:**
  - [ ] Global template library with common events (Back to School, Black Friday, etc.)
  - [ ] Templates include pre-configured integrations (suggested SMS, slides, tasks)
  - [ ] Can create event from template with date adjustment
  - [ ] Template integrations auto-populate but are editable before activation
  - [ ] Can save custom event as new store-specific template
  - [ ] Templates include default build-up and wind-down periods

### Should Have Features

#### Feature 10: Event Reporting Dashboard
- **User Story:** As a store manager, I want comprehensive reports showing event performance so that I can measure success and improve future events.
- **Acceptance Criteria:**
  - [ ] Sales metrics: revenue, transactions, average ticket during event vs. baseline
  - [ ] Marketing metrics: SMS sent/delivered/clicked, signage impressions
  - [ ] Inventory metrics: bins pulled, items processed, buy totals
  - [ ] Comeback Cash metrics: coupons issued, redeemed, revenue impact
  - [ ] Year-over-year comparison (when historical data available)
  - [ ] Export report to PDF/CSV

#### Feature 11: Template Hierarchy and Sharing
- **User Story:** As a store manager, I want to understand which templates are available to me and where they come from so that I can choose the best starting point for my events.
- **Acceptance Criteria:**
  - [ ] Three template tiers are clearly distinguished: Global (corporate), Franchise (shared within brand), Store (single store)
  - [ ] Global templates are read-only for stores but can be duplicated to store level for customization
  - [ ] Store-specific templates can optionally be submitted for franchise-wide sharing (requires approval)
  - [ ] Template source (Global/Franchise/Store) is visible in template selection UI
  - [ ] Franchise templates are filtered by store brand type (Plato's, Clothes Mentor, etc.)

#### Feature 12: Event Timeline Visualization
- **User Story:** As a store manager, I want to see all event components on a visual timeline so that I can verify timing and identify gaps or overlaps.
- **Acceptance Criteria:**
  - [ ] Timeline shows event phases (build-up, active, wind-down)
  - [ ] All integrations plotted on timeline (SMS, slides, coupons, tasks, notes)
  - [ ] Color-coded by integration type
  - [ ] Can zoom in/out on timeline
  - [ ] Click on item to edit

### Could Have Features

#### Feature 13: Multi-Store Event Push
- **User Story:** As a district manager, I want to push an event configuration to multiple stores so that consistent promotions run across my region.
- **Acceptance Criteria:**
  - [ ] Can select target stores for event push
  - [ ] Stores receive event as pending for local review/activation
  - [ ] Can track which stores have activated pushed event

#### Feature 14: Event Calendar Sync
- **User Story:** As a store manager, I want events to sync to external calendars so that I can see store events alongside other commitments.
- **Acceptance Criteria:**
  - [ ] Export event to iCal format
  - [ ] Include event phases and key dates

#### Feature 15: AI-Powered Suggestions
- **User Story:** As a store manager, I want the system to suggest optimal configurations based on historical performance so that events improve year-over-year.
- **Acceptance Criteria:**
  - [ ] Suggests best-performing SMS messages from similar past events
  - [ ] Recommends coupon values based on historical redemption rates
  - [ ] Identifies slides that correlated with higher sales

### Won't Have (This Phase)

- **Real-time POS Integration**: Events won't automatically apply discounts at POS; Comeback Cash handles coupon redemption separately
- **Customer-Facing Event Pages**: No public event landing pages or customer notifications beyond SMS
- **Automated Inventory Ordering**: Won't automatically trigger purchase orders based on event needs
- **Social Media Integration**: No posting to social platforms from event dashboard
- **A/B Testing Framework**: Won't support running parallel event variations for testing
- **Budget/Cost Tracking**: Won't track promotional costs or ROI calculations beyond coupon redemption

## Detailed Feature Specifications

### Feature: Event Creation from Template (Most Complex Flow)
**Description:** Store manager creates a fully-configured promotional event by selecting a template, which auto-populates all integrations with appropriate configurations. Manager can then customize any aspect before activation.

**User Flow:**
1. User navigates to Events section in admin sidebar
2. System displays Event Dashboard with upcoming/active events
3. User clicks "Create Event" button
4. System presents choice: "Create from Template" or "Create Custom Event"
5. User selects "Create from Template"
6. System displays template library (global + store-specific templates)
7. User selects "Back to School" template
8. System shows template preview with: default dates, build-up/wind-down periods, included integrations
9. User adjusts start date (July 20, 2026) and end date (August 31, 2026)
10. System auto-calculates all relative dates for integrations
11. System displays Integration Review panel showing:
    - Backstock: Categories linked (Kids, Seasonal), bin reservation count
    - SMS: 2 scheduled blasts (7 days before: "Bring in your kids' outgrown clothes!", During event: "Back to School Sale happening now!")
    - Signage: 3 slides tagged "back-to-school" auto-selected
    - Comeback Cash: Buy-side coupon (July 13-20), Sales-side coupon (July 20-Aug 31)
    - Tasks: 5 prep tasks, 3 active-period tasks, 2 cleanup tasks
    - Notes: 1 staff announcement scheduled for July 20
12. User edits SMS message content for first blast
13. User removes one slide and adds a different one
14. User confirms all integrations look correct
15. User clicks "Create Event"
16. System creates event and all linked integration records
17. System schedules all automation (SMS queue, signage schedule, task dates)
18. User sees Event Dashboard with new event in "Upcoming" status

**Business Rules:**
- Rule 1: Only one event can be "active" at a time per event type (cannot have two "holiday" events overlapping)
- Rule 2: Template integrations are suggestions - all can be removed or modified before creation
- Rule 3: Relative date calculations use event start date as anchor (e.g., "-7 days" means 7 days before start)
- Rule 4: Backstock integration creates/links to bsEvents record in backstock system
- Rule 5: SMS blasts are queued but not sent until scheduled time arrives
- Rule 6: Signage slides are added to digitalSignSchedule with proper dates
- Rule 7: Tasks are created with calculated due dates; task group "Event: [Event Name]" is auto-created
- Rule 8: Notes are created with startDate/endDate matching visibility window
- Rule 9: Comeback Cash events are created with earning/redemption windows matching event configuration
- Rule 10: When event dates change after creation, all integration dates recalculate (with confirmation prompt)

**Edge Cases:**
- Scenario 1: Template references slide that store doesn't have → System shows warning, omits slide, suggests alternatives
- Scenario 2: Selected dates overlap with existing event → System shows conflict warning, allows override with confirmation
- Scenario 3: SMS message contains invalid variables → System validates and shows error before save
- Scenario 4: Backstock category doesn't exist → System offers to create it or select different category
- Scenario 5: Event created from template then template is later modified → No effect on already-created events
- Scenario 6: Event deleted while integrations are active → System prompts to cancel/complete integrations or cascade delete
- Scenario 7: Event dates changed after SMS already sent → Cannot unsend; system shows warning about already-executed items
- Scenario 8: Store timezone differs from corporate timezone → All dates calculated in store's local timezone

## Success Metrics

### Key Performance Indicators

- **Adoption:**
  - Target: 60% of stores create at least one event using the new system within 90 days of launch
  - Target: 80% of seasonal events (Back to School, Black Friday, etc.) use templates rather than manual setup

- **Engagement:**
  - Target: Average of 3+ integrations configured per event (out of 6 available)
  - Target: 40% of events created from templates vs. custom
  - Target: Event dashboard viewed 5+ times per active event (indicates monitoring behavior)

- **Quality:**
  - Target: <5% of events have integration configuration errors (mismatched dates, missing components)
  - Target: 90%+ event completion rate (events reach "completed" status vs. cancelled/abandoned)
  - Target: <10% of scheduled integrations require mid-event manual intervention

- **Business Impact:**
  - Target: 10% improvement in event-period sales lift compared to pre-system baseline
  - Target: 50% reduction in event setup time (measured via time from event creation start to activation)
  - Target: 15% increase in SMS campaign participation during events
  - Target: 20% increase in Comeback Cash redemption rates for event-linked coupons

### Tracking Requirements

| Event | Properties | Purpose |
|-------|------------|---------|
| event_created | event_id, template_id (if used), event_type, duration_days, integration_count, created_by | Track adoption and template usage |
| event_template_selected | template_id, template_name, store_type | Identify popular templates |
| integration_added | event_id, integration_type (backstock/sms/signage/etc), config_method (template/manual) | Understand integration patterns |
| integration_removed | event_id, integration_type, removal_reason | Identify template mismatch issues |
| event_activated | event_id, days_before_start, setup_duration_minutes | Measure planning behavior |
| event_dashboard_viewed | event_id, event_phase, viewer_role | Track monitoring engagement |
| event_modified | event_id, field_changed, phase_at_modification | Understand mid-event adjustments |
| event_completed | event_id, duration_days, integrations_executed, integrations_failed | Measure completion quality |
| event_report_viewed | event_id, report_type (overview/detailed), export_format | Track reporting usage |
| event_template_saved | source_event_id, new_template_name | Track template creation |

---

## Constraints and Assumptions

### Constraints
- **Technical Platform:** Must integrate with existing PHP 8.x / Slim 2.6.2 / Twig 1.44.8 stack
- **Multi-Store Architecture:** Must support per-store databases (`kiosk_{typeNum}`) with global templates in central database (`kiosk_buykiosk`)
- **Existing System Compatibility:** Cannot break existing backstock, SMS, signage, Comeback Cash, task, or notes functionality
- **No External Dependencies:** Cannot introduce new third-party services or APIs beyond what's already in use (Twilio/Vonage, Ably, Redis)
- **Permission System:** Must integrate with existing UserFrosting permission model with new permissions:
  - `uri_events` - View event dashboard and details
  - `uri_events_manage` - Create, edit, delete events
  - `uri_events_templates` - Create and edit store-specific templates
  - `uri_events_templates_global` - Create and edit global templates (corporate only)
  - `uri_events_reports` - View event performance reports
- **Mobile Compatibility:** Admin dashboard must work on tablets used on store floor
- **Browser Support:** Must support Chrome, Safari, Firefox (latest two versions)
- **Prerequisite:** Slide Tagging System (Phase 0) must be completed before Event Management system to enable tag-based slide selection

### Assumptions
- **User Assumptions:**
  - Store managers have access to admin panel and understand existing module interfaces
  - Managers already use at least some of the individual systems (backstock, SMS, signage)
  - Staff has access to workbook for task viewing

- **Technical Assumptions:**
  - Existing backstock event system (bsEvents) is stable and can be linked/extended
  - SMS marketing queue (`seller_marketing_queue`) can handle increased volume during events
  - Digital signage schedule processor runs reliably for auto-activation/deactivation
  - Comeback Cash system supports linking events to external triggers
  - Task system supports event_id foreign key addition
  - Notes system supports event_id foreign key addition

- **Business Assumptions:**
  - Stores run 3-8 promotional events per year on average
  - Corporate will provide/approve global event templates
  - Historical sales data is available for baseline comparison in reporting

## Risks and Mitigations

| Risk | Impact | Likelihood | Mitigation |
|------|--------|------------|------------|
| Integration complexity causes cascading failures | High | Medium | Build integrations as loosely-coupled modules; event can function without any single integration; extensive error handling |
| Existing system changes break event integrations | High | Low | Use adapter pattern for each integration; version integration APIs; comprehensive test coverage |
| Template automation doesn't match store needs | Medium | Medium | Make all template components optional/editable; allow saving custom templates; gather feedback on template effectiveness |
| Performance degradation with many events/integrations | Medium | Low | Index database queries properly; cache event dashboard data in Redis; lazy-load integration details |
| Users overwhelmed by configuration options | Medium | Medium | Progressive disclosure of options; sensible defaults from templates; contextual help tooltips |
| SMS/signage timing conflicts between events | Medium | Medium | Validation rules prevent overlapping events; visual timeline shows conflicts; clear warning messages |
| Historical data for YoY comparison unavailable | Low | High | Design reports to gracefully handle missing baseline data; show "comparison unavailable" rather than errors |
| Store timezone handling causes incorrect scheduling | Medium | Low | All dates stored in UTC; convert to store timezone for display; test extensively with different timezones |

## Open Questions

- [x] Should the new system extend existing Backstock Events or create a new central Event Hub? → **Decision: New Central Event Hub**
- [x] What level of automation for event integrations? → **Decision: Template Automation**
- [x] Which metrics are most critical for event reporting? → **Decision: All categories (Sales, Marketing, Inventory)**
- [x] Should district/regional managers have ability to push events to stores in initial release or v2? → **Decision: Defer to Phase 2**
- [x] Should the Slide Tagging System (Feature 11) be built first as a prerequisite, or can events select slides without tags initially? → **Decision: Build Tags First (Phase 0)**
- [ ] What default event templates should be included at launch? (Need corporate input)
- [ ] Are there compliance requirements for SMS messaging during promotional events?
- [ ] Should event reports integrate with existing reporting dashboards or be standalone?

---

## Supporting Research

### Competitive Analysis
**Retail Event Management Solutions:**
- **Shopify POS Campaigns:** Limited to discounts and marketing; no inventory coordination
- **Lightspeed Retail:** Has promotional pricing but requires manual coordination of marketing
- **Square Marketing:** SMS campaigns only; no inventory or signage integration
- **Dedicated Event Platforms (Eventbrite, etc.):** Customer-facing ticketing; not applicable to retail promotions

**Key Insight:** No direct competitor offers a unified event coordination system across inventory, marketing, signage, and staff tasks. This represents a significant differentiation opportunity for BuyerKiosk in the resale retail vertical.

### User Research
**Findings from existing system usage patterns:**
- Stores that manually coordinate backstock events with SMS campaigns show 12-18% higher sales lift than stores using systems independently
- Average time to set up a Back to School event across all systems: 2-4 hours
- Most common complaint from store managers: "I forgot to update the signage" or "SMS went out before inventory was ready"
- Tasks created for events often have vague instructions; staff requests more context

**Implied needs:**
- Single source of truth for event status
- Automated synchronization of dates/timing
- Clear connection between tasks and event purpose

### Market Data
- Resale retail market growing 11% annually (ThredUp 2024 Resale Report)
- Seasonal events (Back to School, Holiday) drive 30-40% of annual revenue for resale stores
- SMS marketing open rates average 98% vs. 20% for email (Gartner)
- Stores with coordinated omnichannel promotions see 23% higher customer retention (Harvard Business Review)