Documentation Gaps & Open Questions

GAP-001 — Holds System

Feature: Holds & Reserved Inventory
Code ref: src/admin/routes/passes.tsx (Stadli repo)

No dedicated Holds UI found. Code references holds as “integrated with promotions system.” How does an admin actually create and release a hold? Is it:

A promo code with no discount (reserve via code redemption)?
A seat-level blocked status set manually?
Something else entirely?

Impact: Cannot document “How to hold seats for a sponsor” without this answer.

GAP-002 — Fee Stacking & Calculation

Feature: Pricing, Checkout
Code ref: src/admin/routes/orders.tsx (Stadli repo)

How are fees calculated and stacked? No fee configuration UI found in admin settings. Are fees (platform fee, processing fee, tax) fixed at deployment? Per-team configurable? Where does an admin see the fee breakdown they’re charging fans?

Impact: Cannot accurately document “How fees work” or “Why is my total higher than face value.”

GAP-003 — Refund Policy / Window

Feature: Refunds & Cancellations
Code ref: src/admin/routes/orders.tsx (Stadli repo)

Is there a configurable refund window (e.g., no refunds within 48 hours of event)? Code allows full/partial refunds at any time by admin with no apparent deadline enforcement. Is this by design (admin always has override power), or is a policy window planned?

Impact: Teams need to know if they can set a refund cutoff or if it’s always discretionary.

GAP-004 — Ticket Transfer (Fan-to-Fan)

Feature: Ticket Transfers
Code ref: Reports dataset includes “Ticket Transfers”; no admin-facing or fan-facing transfer workflow found in admin UI

Is ticket transfer a buyer-side-only feature (fans can transfer from their account)? Can an admin initiate or reverse a transfer? The report dataset implies transfers happen — but the mechanism is unclear.

Impact: Cannot document the transfer workflow (buyer perspective or admin perspective) without this.

GAP-005 — Pre-Launch Mode (Public Gating)

Feature: Settings > Public Website > Pre-Launch Mode
Code ref: migrations/0199_settings_prelaunch_mode.sql + src/admin/routes/settings.tsx

The settings toggle exists, but no public-side gating logic found. If a team enables Pre-Launch Mode today, what actually happens to their public storefront? Does it show a “coming soon” page? Redirect? Block all pages? Currently nothing?

Impact: Documenting this feature as functional when the public gating isn’t wired could mislead teams.

GAP-006 — Comp Tickets (Canonical Workflow)

Feature: Comping seats
Code ref: No dedicated comp flow found

What is the canonical workflow for issuing a complimentary (comped) ticket? Two plausible paths:

Manual order with $0 price
Promo code with 100% discount

Which does the product intend? Is there a “comp” label or category in order data, or are comps indistinguishable from regular $0 orders in reports?

Impact: “Comp a ticket” is one of the most common box office tasks. Must be documented accurately.

GAP-007 — Seat Lock Expiry Duration

Feature: Seat selection / checkout hold
Code ref: NEXT_STEPS.md (Stadli repo) — lock countdown timer shipped 2026-03-03

What is the seat lock timeout? Is it configurable per team, per event, or fixed globally? What happens when the lock expires — seats silently released, user notified, cart cleared?

Impact: Teams need to communicate hold time to fans (“You have X minutes to complete your purchase”).

GAP-008 — Season Definition

Feature: Season Passes, Dashboard season metrics
Code ref: src/admin/routes/seasonPasses.tsx, Dashboard season card

“Season” appears in season passes and dashboard metrics, but no top-level “Season” entity or settings page was found. How does the platform know which events belong to the current season? Is a season defined by date range? By a tag? Automatically by year?

Impact: Cannot document season pass setup without explaining how a season is defined.

GAP-009 — Bundle vs. Pass vs. Season Pass (Glossary)

Feature: Passes & Packages
Code ref: src/admin/routes/passes.tsx, src/admin/routes/seasonPasses.tsx

Three overlapping concepts exist — Pass, Season Pass, and Bundle — with a separate Bundle Redemption flow. What is the precise distinction between each? Working definitions to confirm or correct:

Pass = single-event, purchasable or admin-issued, no assigned seat?
Season Pass = multi-event, seat-assigned, holder-managed?
Bundle = pre-paid multi-use credit redeemable at checkout?

Impact: Wrong glossary = wrong docs across 3+ sections.

GAP-010 — Two Promotions Systems

Feature: Promotions (ticketing) vs. Promotions (commerce)
Code ref: src/admin/routes/orders.tsx (ticket promos) + src/admin/routes/commerce.tsx (product promos)

Two separate promotions systems exist — one for ticket discount codes, one for merchandise products. Can a single promo code apply to both? Is there a unified “Promotions” admin page, or are they completely separate? How should teams think about which system to use for cross-sell scenarios (e.g., “20% off merch with every ticket purchase”)?

Impact: Documenting them as independent systems may be correct, but the cross-sell question needs an answer to avoid misleading teams.

Last updated: 2026-05-22 — generated during initial documentation discovery pass.