Skip to content

E2: Match & Stadium Management

Overview

Bounded Context / Service: Match Service, Admin Portal

Goal: Enable admins to create, configure, and manage matches with stadium configurations.

Priority: High

Primary User Roles

  • Admin (Match Manager role)

Scope

In-Scope

  • Match creation wizard (basic info, sales phases, quotas)
  • HOME match stadium configuration (use templates)
  • AWAY match stadium creation and configuration
  • Sales phase management (Loyalty, General Public)
  • Price category assignment to sectors
  • Match update with notification options
  • Match cancellation with approval workflow
  • Away match non-numbered seat handling
  • Access control data export (pre-match)
  • Match closure with attendance import
  • Loyalty points calculation trigger

Out-of-Scope

  • Stadium physical layout design tools
  • Live match scoring/events
  • Broadcast integration

Features

ID Feature Size Description
E2-F1 Match CRUD API M Create, read, update, delete matches
E2-F2 Sales Phase Configuration S Loyalty and General Public phases
E2-F3 Stadium Template Management M Pre-created Croatian stadium configs
E2-F4 Match Stadium Configuration M Configure stadium for specific match
E2-F5 Away Match Stadium Creation S Create stadiums for away matches
E2-F6 Match Update Notifications S Notify vs silent update options
E2-F7 Match Cancellation Workflow M Cancel with refunds and notifications
E2-F8 Access Control Data Export S Export barcodes for gate validation
E2-F9 Match Closure with Attendance M Close match and import attendance
E2-F10 Sector Seat Map Configuration M Define rows and seats within sectors

Dependencies

  • Stadium templates must be pre-loaded
  • E-racuni integration for refunds on cancellation

Risks & Open Questions

OQ-E2-1: Stadium Zoomable View

Is a full stadium zoomable view technically feasible with the stadium map data format?

Assumption: Implement sector-only view initially; add zoomable view if data supports it.

Last Updated: January 2026