Card reader offline
Usually a network path or a terminal that lost its configuration. We monitor terminals so we know before the line forms.
Retail
A point-of-sale outage on a Saturday is lost revenue you never get back. We keep POS, payment terminals and inventory systems online, segment card traffic away from everything else, and make sure your busiest month is the one you planned for.
Overview
Retail IT has exactly two jobs: keep the sale from failing, and keep card data out of places it does not need to be.
Point-of-sale outages are rarely caused by the point-of-sale software. They are caused by an internet circuit that dropped, a switch that lost power, a payment terminal that fell off the network, a receipt printer with a changed IP, or a workstation that installed an update mid-shift. We build redundancy into the parts that fail: a secondary internet path with automatic failover, uninterruptible power on the register stack and the network closet, standardized register hardware with a spare on the shelf, and controlled patching so nothing installs itself at 2pm on a Saturday.
PCI DSS is the second job, and the practical strategy is to shrink your scope rather than secure a sprawling one. Modern EMV terminals with point-to-point encryption mean the raw card number never lands on your network in readable form, which removes a large amount of risk and a large amount of questionnaire. From there, payment devices go on their own VLAN with tightly written firewall rules, remote access into the POS environment requires multi-factor authentication, default credentials are removed from every device, and card data is not stored anywhere it does not belong. Your acquirer determines which self-assessment questionnaire applies. We build the network to support it and we document what was done.
Customer Wi-Fi is where a lot of stores quietly create risk. A single flat network with one password shared between staff, shoppers and the register is common and it is exactly what an attacker hopes to find. We put guest access on a separate SSID and VLAN with client isolation and bandwidth limits, keep staff devices on their own network, and put cameras and back-office systems somewhere else again. That work is part of our network administration and wireless services.
Inventory and back office are the third layer. Whether you run Lightspeed, Shopify POS, Clover, Square, Heartland or a vertical-specific platform, the systems behind them, purchasing, receiving, e-commerce sync, loyalty, scheduling and payroll, all depend on the same infrastructure. We monitor integrations so a broken e-commerce sync raises an alert before oversold inventory turns into canceled orders, and we keep back-office data in real backup rather than trusting a vendor’s default retention.
Seasonal peaks make everything sharper. From November the store runs longer hours, more temporary staff and far more transactions per hour. We stage extra registers and scanners ahead of time, create scoped seasonal accounts that expire, freeze non-essential changes during the peak, and stay available for a season where a two-hour outage is a very expensive afternoon. More at our retail IT microsite.
The cheapest way to pass a card audit is to hold less card data.Orca IT, Gilbert AZ
What We Handle
The things that keep a store selling on its busiest day.
Register hardware, receipt and label printers, cash drawers, scanners and EMV terminals kept standardized with spares configured and ready.
Card devices on their own VLAN with explicit firewall rules, MFA on any remote access, and default credentials removed everywhere.
Separate SSID and VLAN with client isolation and bandwidth shaping, so shoppers never share a network with your registers.
Automatic failover to a secondary circuit and uninterruptible power on the register stack and network closet.
Monitored sync between POS, online store and purchasing, so oversold stock is caught by an alert rather than by a customer.
Scoped temporary accounts that expire, extra hardware staged in advance, and non-essential changes held until the peak passes.
Common Calls
The register is down is the headline. These are the actual causes.
Usually a network path or a terminal that lost its configuration. We monitor terminals so we know before the line forms.
One provider, no backup, no sales. Automatic failover keeps you selling while the carrier works the ticket.
A DHCP change or a driver update. Static reservations and a spare printer end this category of call.
One overloaded access point serving everyone. We separate and size the wireless for both audiences.
Often an old vendor account with a weak password. We audit, remove and require MFA on what remains.
A silent integration failure. Monitoring the sync turns a week of oversells into a same-day fix.
We implement the technical controls PCI DSS asks for and we help reduce your scope, but validation is between you, your acquirer and, where required, a qualified assessor. Practically, using EMV terminals with point-to-point encryption, segmenting payment traffic and locking down remote access removes most of the risk and simplifies the questionnaire you have to complete.
Two ways. First, a firewall with automatic failover to a second circuit, usually cable or cellular, so the switch happens in seconds without staff involvement. Second, understanding your POS platform's offline mode. Some systems can store and forward transactions; some cannot process at all. We document exactly what your staff should do in each case before it happens.
Yes, when it is built correctly. Guest access belongs on its own SSID and VLAN with client isolation so devices cannot see each other, bandwidth limits so streaming does not affect operations, and no route whatsoever to your registers, back office or cameras. A single shared network with one password is where this goes wrong.
We support the environment those platforms run on and we manage the vendor escalation. That means registers, peripherals, network, internet redundancy, printing and integrations. For issues inside the application itself we open and drive the case with the vendor so your manager is not the one sitting on hold during business hours.
It depends on square footage, construction materials, shelving height and how many devices are in use. A small boutique may need one properly placed unit; a large store with metal fixtures, handheld scanners and heavy customer traffic may need several with a tuned channel plan. We survey rather than guess, because too many access points fighting each other performs worse than too few.
Create them scoped and time-bound. Each temporary employee gets a named account with an expiry date, limited to the POS functions and systems their role needs, and no shared manager credentials. When the season ends, access closes on schedule. Shared logins make theft investigations nearly impossible and are the most common bad habit in retail.
Yes. Cabling to register positions, back office and camera locations, network closet design, wireless coverage, internet circuit ordering with lead time, POS staging and testing, and a go-live day where someone from your pod is physically in the store. We coordinate with your general contractor and your POS vendor directly.
Yes. Depending on your needs that could be site-to-site VPN, an SD-WAN approach, or simply centralized cloud systems with strong identity and no store-to-store traffic at all. The right answer depends on where your inventory and reporting live. We usually recommend the simplest design that meets the requirement, because complexity in retail networks tends to become downtime.
Free store review covering POS resilience, segmentation and peak readiness.
Talk to Your Pod
We will review POS resilience, network segmentation, wireless and internet failover, then give you a written plan and a realistic timeline.
(602) 677-0779Family owned in Gilbert, AZ since 2015 · onsite across the Phoenix metro · remote support nationwide · never outsourced
A few details and your pod gets right back to you, usually the same business day.