Event Ordering
Fans scan a QR at their seat and get food without missing the match.
Problem
At stadiums and events, fans had to choose between queuing for food and watching the event. Stadium operators were losing food revenue because fans simply skipped ordering.
What I built
A complete event ordering system built on top of Foodhub.
Fans scan a QR code at their seat. They see upcoming events with name, date, and time. They select their event, choose their box or table, pick a time slot, Now, Half Time, or Full Time, and place their order. Food is routed to their seat.
I owned this end to end, user stories, configuration design in BOB CRM, consumer flows, kitchen routing, email notifications including event name replacing takeaway name and table number replacing address, and post-launch iteration.
Complex edge cases I owned: pre-order slot configuration with agent-controlled labels that carry through to basket and receipt, ASAP vs pre-order logic switching automatically based on event date, multi-event menu management preventing conflicts, and ordering before or after event time if slots are still configured.
Key decisions
Keep event ordering on a completely separate URL from dine-in so neither breaks the other. Carry slot text labels like Half Time end to end rather than just timestamps.
Outcome
Fans order from their seat without missing the match. Agents configure events, slots, and menus independently through BOB CRM without engineering. Stadium operators gained a new revenue channel.