Die Bosveld Ticketing

[ qr ]    [ nfc ]
    └───┬────┘
    ( gate )
       │ scan
       ▼
( history ) ─▶ ✓ admit

Context

Die Bosveld is a working events and leisure venue in Doornpoort, Pretoria — day visitors, ticketed events, fishing spots, venue hire. I spent three years there on both sides of the gate: as an access controller checking people in, and as the person turning what I saw into software. That double view — feeling every queue and every dispute at the gate, then encoding the fix — is what this project taught me best.

A deliberate no-code decision

We built the system on Bubble, together with Gerhard van Staden, who knows the platform deeply. That was a considered call, not a shortcut: the venue needed working software in weeks, the requirements were still moving as we learned from each event day, and no-code let us iterate at the speed the gate demanded. Languages and platforms are tools — this problem, at this stage, with this team, wanted Bubble.

My side of the build was the product thinking: the data model of passes, events and bookings; the validation rules; the flows for the gate, the till and the customer's phone. Gerhard's was making the platform sing.

Requirements you only learn at the gate

• One ticket, two phones. Die Bosveld runs one gate, but on busy days several marshals work it, each with their own phone — so a ticket gets presented on two phones within seconds. Sometimes fraud, mostly a family splitting up in the queue. Every scan had to be recorded with a verdict against the order's history, so a second scan of a used ticket bounces no matter whose phone catches it.
• Families don't arrive as a unit. A day pass covers, say, four adults and six children — and dad walks in with two kids while mom parks the car. The gate logic tracks what remains on the pass per visitor type and admits partial groups across multiple taps. Software that forces a family to enter all at once is software the marshals will bypass with a wave-through — and then your records are fiction.
• Check-in without scanner hardware. QR codes and NFC tags read straight from a phone at the gate; customers can program their own NFC tag or bracelet from their ticket page, with a copy-the-link fallback for unsupported phones. Any phone becomes a checkpoint; the venue never bought a scanner.
• Payments must reconcile themselves. Online sales settle through Payfast with tickets delivered by email and WhatsApp — because the person selling at the till on a Saturday cannot also be chasing payment mismatches on a Monday.
• Exceptions can't wait for the admin. The old setup routed every fix — a wrong booking, a missing ticket, a payment query — through one admin, who is most often unavailable exactly when the gate is busiest: weekends and holidays. The new system puts those powers in the workers' hands. A marshal at the gate — or the worker at the trailhead just past it, catching whoever slips through — can look up and fix bookings, sell tickets, take payments and settle disputes from the scan history, on the spot.

Outcome

The venue went from scattered systems — each covering a slice of the operation, none of them talking to each other — and manual reconciliation to one integrated system: digital sales, WhatsApp delivery and phone-based check-in across every product it sells — passes, events, fishing spots and venue hire.

Check-in itself got drastically faster. The gate runs with fewer people now, and the ones on it don't route problems anywhere — they sort out bookings, payments and disputes on the spot instead of stalling behind an admin who's off on the venue's busiest days.

What it left me with

Knowing exactly how the gate behaves on a chaotic Saturday is the best spec I'll ever get — it shapes how I design software still. The gate stories, long-form: The venue gate is a distributed system.