World Cup Ticketing: Technically Correct, Practically Broken
A ticketing system can satisfy its functional requirements and still create outcomes users perceive as failures. It may scale under load, maintain consistent inventory, process payments, and enforce pricing rules, yet still expose buyers to prices, queues, or checkout flows that feel opaque or unfair to them.
The 2026 FIFA World Cup ticketing controversy provides a useful lens for this problem. Public reports and customer feedback highlighted concerns about pricing, dynamic pricing mechanisms, resale processes, affordability, and unclear expectations during the purchasing experience.
Technical correctness means the system behaves according to its specification. Product correctness means the specification includes acceptable output boundaries alongside the operations that must succeed. In pricing, allocation, and access systems, that distinction matters because the rules can execute exactly as written while still producing outcomes users experience as failure.
Design note: A specification that defines only successful operations leaves output boundaries unspecified. That gap is where product failures emerge in otherwise correct systems.
This newsletter examines that gap through high-demand ticketing, starting with dynamic pricing as a feedback loop, then covering optimization objectives, guardrails, external actors, and transparency. The central question is whether the system’s outputs stay within the boundaries defined by the design.
Dynamic pricing as a feedback loop#
In high-demand ticketing systems, dynamic pricing functions as a feedback loop. Demand signals influence pricing decisions, and buyer behavior feeds back into later pricing updates.
Those signals may include queue depth, conversion rate, sell-through rate, remaining inventory, match popularity, time to event, regional demand, and resale activity, where available.
Each signal has a different latency and trust level. Queue depth may update in near real time, while match popularity moves slowly, and resale activity can be noisy or incomplete.
Queue depth requires careful interpretation. It can reflect real buyer demand, but it can also be inflated by bot traffic, repeated sessions, speculative cart holds, or users who abandon checkout at the current price. When the platform throttles ingress, queue depth may represent users waiting, but it does not necessarily measure willingness to pay.
Risk: Delayed or low-quality feedback signals can cause price oscillation or overcorrection. A stale conversion signal may cause prices to move on outdated demand, then adjust again when newer data arrives.
A dynamic pricing loop should separate raw demand signals from trusted inputs used to change prices. High-confidence real-time signals may support short-term reactions, while lower-confidence signals should be filtered to reduce noise or smoothed to dampen high-frequency fluctuation. Slower signals may be better reserved for longer-horizon pricing strategies.
