Bandwidth Management for SMEs: Sharing a Link Without a Meltdown

T he failure is always the same shape. The internet link is provisioned for the business: enough for the card terminal, the booking system and the back office. Then the café fills up, six people start a film on the same network, and the payment terminal stops responding. The business did not buy more bandwidth, but it has effectively lost the bandwidth it had.
The fix is not a bigger pipe. It is deciding who gets what, in advance, while the link is quiet.
One link, several speeds
A shared business connection serves traffic with very different requirements. A card terminal needs a tiny amount of bandwidth and an extremely low latency. A guest streaming video needs a lot of it and does not mind latency. A back-office user needs a stable, modest slice all day. Treating them the same is what makes the link feel broken for everyone.
The fix is per-profile bandwidth control: a minimum and a maximum for every profile you define, enforced per session rather than per device. The terminal's profile caps out low and is guaranteed a floor; the guest profile can use a lot but never more than its share; the office profile sits in between and stays predictable.
Guarantee a floor, not just a ceiling
Most people think of bandwidth limits as a maximum. The more useful half is the minimum. If a guest is streaming at full speed and an employee needs to upload a booking, the link has no concept of who should go first. A guaranteed minimum per profile means critical traffic keeps working regardless of what the guests are doing.
Let unused capacity be borrowed
The classic objection to bandwidth management is that you end up paying for capacity nobody is using at 3am. Borrowing solves it: unused bandwidth from idle profiles is made available to the profiles that want more, up to their own ceiling. The business still owns the smaller pipe, but a quiet evening means every guest gets a good experience and a busy evening means nobody breaks the connection.
Cap the session, not just the speed
Speed limits alone do not stop one guest from consuming the entire allowance over a long evening. Pair them with a data cap per session or per period and the behaviour changes: the profile can be generous per hour while the overall consumption stays bounded.
This is also where profile parameters earn their keep. Session duration, traffic per session, connection hours, account expiry and maximum devices per account are all independently configurable, so you can build a profile that means exactly “two hours, one gigabyte, up to three devices, evenings only” without writing any code.
Segment the network so the rules can differ
If staff devices, guests and building systems share one flat network, one set of rules cannot be right for all of them. Bridge mode gives you a separate guest LAN on the second network interface, so the captive portal, the traffic policy and the walled garden apply to guests, while the business network stays untouched and outside the quota system entirely.
Set it up before you need it
* Profile the real traffic first: look at the dashboard for a week and see what the business actually uses versus what guests assume they are entitled to.
* Start with the profiles that protect the business — the point of sale, the booking system, the voice handsets — and then decide what is left for guests.
* Review the result. A profile that nobody uses is a profile you can delete; a profile that is always at its ceiling is telling you to buy more bandwidth, or to reprice your guest offer.
* Put the ceilings in writing and tell guests. The complaints you get from people who knew the rules are shorter than the ones from people who did not.
None of this needs a large network or a dedicated line. It needs the decision of how to share what you have — taken once, written down, and enforced automatically from then on.

No part of this document may be reproduced without prior written permission of WifiGem.