Network setup
The lanes, the back office, and what connects them
The network is the part of a POS installation nobody wants to own, and the part every other vendor points at when something goes wrong. It is scoped as named work with an owner, because otherwise it becomes an argument at the worst moment.
Named work with an owner, not an assumption.
What network does a POS system need?
Enough that every lane reaches the back office reliably, and a decision about what happens when the outside connection drops. That means knowing where the registers physically are, how they connect, where the router and the back-office machine live, and whether payments run over the same path. None of it is exotic; almost all of it is assumed rather than checked, which is why it is a common cause of installation-day surprises.
The other half is ownership. If the network is nobody’s job, a lane dropping becomes a conversation between a POS vendor, a payment processor and an internet provider, none of whom can see the other two.
- Every lane has to reach the back officeThat path is what the system actually runs on.
- The outside connection is a separate questionPayments and updates depend on it; ringing sales may not.
- Physical placement mattersCable runs and power decide what is possible before anything else does.
- Somebody has to own itOtherwise an outage becomes three vendors pointing at each other.
We do not claim a network configuration makes a store immune to outages. What it does is make the failure understandable and bounded, and the plan for it agreed in advance rather than improvised at the till.
What gets scoped
The four things worth settling before installation day
Each has caught somebody out on a go-live.
Where the registers are
Build a POS systemCable runs, power, and what is physically possible at each counter.
How they connect
To each other and to the back office, reliably enough to trade on.
What happens when the line drops
Payment outage planningDecided before it happens rather than during.
Who owns it afterwards
SupportSo a dropped lane has somebody to call rather than three somebodies.
Who does what
Who sets up the network, in Tampa Bay and everywhere else
The scope is the same wherever the store is. What changes is who is in the building for the physical part.
Scoping, for every store
Where the registers sit, how they connect, where the back office is and whether payments share the path, worked out before installation day.
Onsite across Tampa Bay
Showroom and local supportThe site can be looked at in person, and setup and go-live can be attended at the counter.
Remote everywhere else
Installation and trainingConfiguration, testing and go-live are handled remotely. The physical cabling is local work, for the store’s own electrician or cabling contractor.
After go-live
SupportA dropped lane goes to support. Standard support hours are weekdays 9–5.
Where networks cause POS problems
-
The network was assumed to be fine
Installation day becomes a cabling job nobody quoted.
It is scoped with the rest of the system: onsite in Tampa Bay, remotely everywhere else.
Installation and training -
A lane drops intermittently
The hardest kind of fault: it works whenever anyone looks.
The path from lane to back office is known, so it can be tested rather than guessed at.
-
Payments and the POS share an unexamined path
One outage takes out both, and nobody knows which failed.
The payment path is part of the design, not a later addition.
Merchant processing -
Nobody owns the network
Three vendors, no resolution, and a store not trading.
Ownership is agreed while the system is being specified.
Support
Network questions
Do you do the cabling?
We scope what is needed and coordinate it. In Tampa Bay, whether we run it or your electrician does depends on the site, and it is agreed rather than assumed. Outside Tampa Bay it is run locally, by your electrician or cabling contractor, to the scope we agree.
Can the registers work if the internet drops?
That depends on the configuration and it is one of the questions worth settling when the system is specified. We will tell you what applies to your setup rather than a general claim.
Do I need a separate network for payments?
Not necessarily, but whether payments share the path is a decision rather than an accident, and it changes what an outage takes out.
What about wireless?
It has its place and it has failure modes a cable does not. Which is right depends on the building, which is why the building is part of scoping.
Tell us where the registers go
How many lanes, where they sit, and where the back office is. That is enough to scope the network with the system rather than after it.