How many payment devices does a large show need?

A show does not need a device for every visitor. It needs enough working devices in the right places when the gates, food courts, bars, rides and showbag halls are all busy at once.

That sounds obvious. It is still where most fleet plans go wrong. Annual attendance is easy to find, so it becomes the planning number. The queue outside a single top-up point at 1pm on peak Saturday is the number that matters.

Start with trading locations, not attendance

Count every place where money or value moves at the same time. Include vendor tills, top-up points, self-service kiosks, entry scanners, refund desks, roaming staff and the devices held back for replacements.

Then map the busiest operating window for each area. A gate fleet peaks before the food court. A beverage bar peaks around a headline act. A showbag hall can stay busy for hours. One venue-wide average hides all three.

The useful question is: how many people must transact in this area during its busiest fifteen minutes, and how quickly can the team replace a failed device without closing a lane?

What 500+ devices proves

At Sydney Royal Easter Show, Ludo supported 900K+ attendance, 125K+ daily visitors at peak, 3M+ transactions and 500+ devices across the show.

The 500+ figure proves fleet scale. It is not a universal formula. The fleet included different device jobs, and the transaction load was not spread evenly. A kiosk, a gate scanner and a vendor terminal solve different pressure points.

Dividing 900K by 500 produces a neat number and a poor deployment plan. Start from concurrent jobs, then use attendance and transaction forecasts to test whether the plan has enough headroom.

Plan the spare path before the show

A spare device only helps if it is charged, configured, assigned and close enough to reach the failed lane. Keep replacements by operating zone. Give the support team a clear handover record so the replacement carries the right vendor, location and payment configuration.

The same rule applies to mounts, scanners, printers, cables and charging points. A working terminal with a missing mount can still close a till.

Keep the fleet visible while it trades

Fleet sizing is not finished when the order is placed. Operators need live device status, battery, connectivity and trading-location context during the event. That lets the team move a spare before a queue becomes a complaint.

After each trading day, compare the plan with actual transaction pressure and device incidents. Move devices before the next peak. Large shows are too dynamic for a fleet map that stays fixed for twelve days.

Five questions for the device plan

Which locations trade at the same time? Which fifteen-minute windows carry the most pressure? Which roles need dedicated hardware? How quickly can a configured spare reach each zone? What live signal tells the control room to act?

Answer those five questions and the fleet number becomes an operating decision, not a guess based on annual attendance.