A trade show entrance can be quiet for hours and then fill up in minutes. Choosing kiosk numbers from total attendance alone can leave visitors waiting at the busiest moment.

There is no universal number of event kiosks. It depends on simultaneous arrivals, the task and the time each transaction takes. Printing a badge after scanning a QR code is different from registering, paying and printing.

Start with peak demand, test the real journey and allow for exceptions. If you do not have all the figures yet, contact us on WhatsApp or email us and we can help scope the solution.

1. Define the kiosk journey

Decide whether visitors will scan a code, find a registration, correct details, pay or print a badge. Consider languages and separate badge collection from ticket sales when their workflows differ.

2. Estimate arrivals at the busiest time

Estimate arrivals during the peak hour and the share likely to use a kiosk. Consider groups, exhibitors and staff. If there is no historical data, model several scenarios with the organiser.

3. Calculate an initial capacity

Use kiosks = peak arrivals × kiosk usage share × seconds per transaction ÷ available seconds, rounded up. This is a workload estimate, not a waiting-time guarantee.

For example, 600 arrivals in one hour, 60% kiosk use and 45 seconds per transaction give 360 × 45 ÷ 3,600 = 4.5, or at least 5 kiosks under ideal conditions. Paper replenishment, uneven arrivals and exceptions require further capacity assessment.

4. Test and plan for exceptions

Time the complete journey with users unfamiliar with the interface. Check the space, signage, power, connection and supplies. Set aside a support point for incorrect data, unreadable codes and reprints, and agree a contingency procedure.

Choose the right delivery model

Woolando offers sale, rental, provision and complete projects across Spain, with on-site support when needed. We can develop the software and connect kiosks with ticketing and QR validation to suit the project. At the Fira del Vi in Cambrils, our work included self-service, online sales and validation; the published outcomes are team observations, not capacity measurements for other events.

Tell us the event type, city, approximate date and what you need to solve. Peak arrivals and expected transaction time help us prepare an estimate when available.