Event WiFi setup for markets, festivals and pop-ups

Good event WiFi setup comes down to one thing the venue's free WiFi never does: sizing the wireless to the crowd, and keeping the people taking payments on a separate lane from the people watching videos. The number that matters isn't the size of the field, it's how many devices are on the air at once — and a single access point only carries about 30 to 50 of them before everyone slows down together. So you deploy enough access points to share the load, spread them out, and split the network into a private stallholder lane and a public one. Do that and the EFTPOS terminals keep working through the rush. Skip it — one tired router for everyone — and payments start declining at the exact moment the queue is longest. Here's how I'd build it.

Why the venue's free WiFi always dies

It dies because it was built for the building's normal Tuesday, not for a thousand people turning up at once. A hall or a showground's WiFi is usually one or two access points sized for staff and the odd guest checking email. That's a sensible build for what it was designed to do. It just has nothing to do with an event.

When the crowd lands, three things break at the same instant. The access points run out of airtime — WiFi is one conversation at a time, every device has to take turns, and a few hundred phones all waiting their turn means everyone crawls. The router's connection table, the list of who's allowed on, fills up and starts quietly dropping clients. And the single internet line behind the whole thing saturates the moment a few hundred people start using it. None of that is a fault you can reset away. It's a capacity problem, and the only honest fix is more capacity, placed properly — not crossing your fingers that the existing kit copes.

Size the network to the crowd, not the venue

This is the call most people get backwards. They look at the size of the marquee or the paddock and pick gear to "cover" it. Coverage is the easy half. The hard half is capacity — how many devices can actually use it at once — and that's set by the crowd, not the acreage.

So start by counting devices, not square metres. A modern business-grade access point comfortably carries somewhere around 30 to 50 active devices before it starts queueing them; push past that and they don't get a thinner slice of a fat pipe, they get put in a longer line, and the whole cell slows down together. Estimate how many devices will really be connected at your peak — every stallholder terminal and phone, plus however much of the public you decide to let on — and provision roughly one access point per 30 to 50 of those, with headroom. A small weekend market might need two or three. A festival offering public WiFi across the grounds needs a planned grid of access points with deliberate, overlapping coverage, all on one managed network so devices roam between them cleanly instead of clinging to the first one they found.

And get them up. An access point on a trestle table behind a stall, surrounded by bodies, is half the access point it could be. High on a pole or a truss, clear of the crowd, aimed down into the zone it's meant to serve — that placement is free and it's most of the performance.

Stallholders and the public are two different jobs

Here's the part that separates a network that copes from one that falls over by 11am: never put the people taking money and the people having fun on the same lane.

A stallholder's EFTPOS terminal needs a tiny, boring, utterly reliable trickle of data that is always there. The public, given an open network, will stream video, upload to socials and back up their photos — they'll cheerfully soak up every bit of bandwidth you hand them. Run those two on the one network and the second the public traffic spikes, the terminals start timing out. Cards decline, the line banks up, and the stallholder blames the EFTPOS provider when the real problem is a teenager four metres away watching highlights.

The fix is to split them into separate SSIDs — separate named networks — with the stallholder lane prioritised. The payments lane is private, locked down, and guaranteed its slice no matter what's happening on the public side. The public lane gets whatever's left, and you can cap it per device so one heavy user can't ruin it for the rest. Same hardware, two lanes, and suddenly the part of the network that earns the money is bulletproof. If keeping the payments side rock-solid is the whole point of the exercise for you, that lane deserves its own attention — getting EFTPOS to work reliably at a busy event comes down to prioritisation and backup.

Stop relying on fifty phone hotspots

The default at most markets is every stallholder running their terminal off their own phone hotspot or a 4G EFTPOS unit. At a single quiet stall, that's genuinely fine — leave it alone. At a busy event it's a trap, and it's worth understanding why, because it fails in a way that looks like everyone's gear breaking at once.

Every one of those hotspots, plus every customer's phone, is hammering the same handful of mobile towers in the same paddock at the same time. The cell congests. Suddenly the 4G terminals that worked perfectly on setup morning start timing out at noon — not because the terminals are bad, but because the tower is full. Fifty independent connections all fighting the same congested tower is the worst possible design for a crowd. One shared, properly backhauled connection on the ground, with the terminals on a prioritised lane, beats it comfortably. Keep mobile as a backup path by all means — just don't make it the primary for the busiest hour of your day.

The connection behind it — and a backup that takes over by itself

None of the WiFi matters if the link feeding it falls over. And event sites are exactly where that happens: many have no fixed line at all, so you're working with whatever you can bring in.

The realistic options are a business 4G/5G connection on a proper external antenna mounted up high and aimed at the best tower, fixed wireless if the site has it, or Starlink where there's a clear view of the sky. The good news is you don't need much raw speed — card payments and basic browsing sip data; it's the number of connections that's the load, not the bandwidth. What you actually need is for the link to stay up. So run it into a router that can hold a second connection as automatic failover — say a primary 4G link with Starlink behind it — so the moment the primary drops or congests, every terminal shifts across without anyone touching a thing. The one time your connection will drop is the busiest hour of the day. Design for that, the same way you'd never run a serious site on a single link, and a tower outage becomes a blip instead of a dead till.

What "done properly" actually looks like on the day

Put it together and it's not exotic, it's just planned. A reliable connection brought onto the site with a backup link behind it. A router that fails over by itself. Enough access points to carry the crowd you're actually expecting, mounted high and spread out as one roaming network. Stallholders and their EFTPOS on a private, prioritised lane that's guaranteed to work; the public, if you offer them anything, on a separate capped lane that can't touch the payments. Set up like that, the busiest hour of the event is the same as the quietest as far as the network's concerned — the tills just keep going, and "the WiFi's dropped out again" stops being a sentence anyone says.

That's the whole idea: stop treating the venue's free WiFi as the plan, and build something sized for the crowd that's about to walk in. If part of your event runs on knowing how many people are where, people counting for events works off the same network you've already put in.

Frequently asked questions

What is the right way to set up event WiFi for a market or festival?

Size the wireless to the number of people, not the size of the field. Work out how many devices will be on the air at peak, deploy enough access points to share that load — a single AP comfortably handles roughly 30 to 50 active devices, so a busy market needs several, not one — and put them up high and spread out so each covers a zone instead of fighting the others. Then split the network into two lanes: a private one for stallholders taking payments, and a separate public one for punters, so customers streaming video can't choke the EFTPOS terminals. The venue's free WiFi fails because it does none of this — one tired router trying to cover everyone.

Why does the venue's free WiFi always die at events?

Because it was built for the building's normal day, not for a thousand people arriving at once. A venue's WiFi is usually one or two access points sized for staff and the occasional guest. Drop a crowd on top and three things break together: the access points run out of airtime as hundreds of devices take turns talking, the connection table fills up and starts dropping clients, and the single internet line behind it saturates. It's not that the WiFi is bad — it's that it was never sized for an event. You fix it by adding properly placed access points and a backhaul link built for the crowd, not by hoping the existing kit copes.

How many access points do I need for an event?

Count devices, then divide. A single business-grade access point comfortably carries about 30 to 50 active devices before it starts queueing; cram more on and everyone slows down together. Estimate how many devices will actually be connected at peak — stallholder terminals and phones, plus however many of the public you let on — and provision one access point per 30 to 50 of those, with a bit of headroom. A small market might need two or three; a festival with public WiFi across the grounds needs a planned grid of them with overlapping coverage. The number is driven by the crowd, not the acreage.

Should stallholders and the public be on the same WiFi network?

No — keep them on separate lanes, every time. Stallholders taking card payments need a small, reliable amount of bandwidth that's always there; the public, given WiFi, will happily stream video and burn everything you give them. Put the two on separate SSIDs with the stallholder lane prioritised, and the EFTPOS terminals keep working through the busiest part of the day while the public traffic gets what's left. Mixing them is the single most common reason payments start declining right when the queue is longest.

Can stallholders just use their phone hotspots or 4G EFTPOS instead?

They can, and at a small quiet stall it's fine. It falls apart at a busy event because every stallholder and every customer is hammering the same few mobile towers at once, so the cell congests and the 4G terminals start timing out exactly at peak trade. A single shared, properly backhauled connection on the ground — with the terminals on a prioritised lane — is far more reliable than fifty separate hotspots all fighting the same congested tower. Mobile is a reasonable backup; it's a poor primary for a crowd.

What internet connection do I need behind event WiFi?

Whatever you can get that's reliable, with a backup. Many event sites have no fixed line, so the realistic options are a business 4G/5G connection with a proper external antenna, fixed wireless, or Starlink where there's a clear sky. The important part isn't raw speed — payments and basic browsing need very little — it's that the link stays up and has a second path to fall back to. Run the connection into a router that can fail over to a backup link automatically, because the one time it drops will be the busiest hour of the day.

Do I need WiFi at a pop-up just to take card payments?

You need a reliable connection; it doesn't have to be WiFi specifically, but at anything beyond a single stall, planned WiFi on a prioritised lane beats every terminal running on its own mobile data. A pop-up with two or three points of sale is already enough for mobile congestion to start causing declined transactions at peak. A small, correctly set up network — one connection, one router, a couple of access points, EFTPOS on its own lane — costs little and turns payments from a gamble into something you stop thinking about.

Running a market, festival or pop-up and tired of the WiFi falling over right when the crowd's biggest and the tills are busiest? That's exactly what we set up — a connection sized to your crowd, EFTPOS on its own protected lane, and a backup that takes over by itself if the main link drops. No lock-in, no selling you gear you don't need. Tell us about your event and we'll work out what'll actually hold up on the day.