What makes retail telecom uniquely hard to manage
Retail telecom looks simpler than it is from the outside. Most stores need internet, a POS connection, and maybe a phone line. But multiply that across 30, 80, or 200 locations — with different lease dates, different incumbent carriers in each market, different equipment vintages, and a constant stream of remodels, store openings, and closures — and you have a carrier management problem that can easily consume a full-time IT resource.
The retailers we work with most commonly inherited their carrier situation through growth. A chain that expanded from Portland into the Willamette Valley and then into Washington ends up with Comcast Business in some markets, Ziply Fiber or Astound in others, CenturyLink (now Lumen) in rural areas, and maybe a handful of Verizon or AT&T wireless backup circuits thrown in for good measure. Each carrier bills separately, renews on a different date, and has a different process for moves and adds. Nobody has a master view of what's installed where and when everything expires.
ITG Group has been working with Pacific Northwest retailers since 2001. Our longest-running retail client is Bi-Mart, where we've managed carrier relationships across their Oregon and Washington store footprint for over a decade. We know the carrier landscape in small-market retail — Roseburg, Klamath Falls, Eastern Oregon — as well as Portland and Seattle metro, and we know which carriers actually deliver on their rural SLAs and which ones make promises they can't keep.
SD-WAN, POS segmentation, and the carrier mix
The most significant shift in retail networking over the past five years is the move from dedicated MPLS circuits to SD-WAN with broadband underlays. For a 50-store chain, replacing MPLS with a managed SD-WAN overlay using dual broadband circuits — one primary, one secondary — typically cuts connectivity spend by 25–40% while improving resilience. The key is that SD-WAN gives you application-aware routing: POS traffic stays on the primary circuit with failover to secondary in under a second; general browsing and back-office apps can use whatever path is available.
POS segmentation is a critical security and compliance requirement that SD-WAN handles more elegantly than traditional hardware. PCI DSS requires that payment card data be isolated on its own network segment, separate from general store traffic and guest WiFi. With legacy hardware, this typically means a separate VLAN and a dedicated circuit or strict firewall rules that are easy to misconfigure. Managed SD-WAN with centralized policy enforcement makes PCI segmentation far more consistent across a large store footprint.
In the Pacific Northwest, the dominant retail carriers are Comcast Business in metro and suburban markets, Ziply Fiber in mid-sized Washington and Oregon cities, Astound Broadband in specific Oregon coastal and valley markets, and Lumen in rural and Eastern Oregon/Washington markets. CenturyLink legacy circuits still appear in rural areas. We know which markets have genuine competition — which drives better pricing — and which are effectively single-carrier markets where the negotiation strategy has to be different.
What ITG handles for retail IT teams
Retail engagements typically cover: carrier audit across the full store portfolio — inventory reconciliation, billing error recovery, contract expiration mapping; competitive RFP for internet and voice at scale, negotiated as a portfolio rather than store-by-store; SD-WAN design and carrier sourcing for stores transitioning off MPLS; POS connectivity review and redundancy planning to meet uptime and PCI requirements; UCaaS for corporate and regional offices; loss prevention camera bandwidth planning as IP surveillance systems replace legacy analog; seasonal bandwidth right-sizing for high-volume periods like Black Friday and back-to-school; and lifecycle management — we track every circuit, every contract, every renewal date, so your team doesn't have to.
The recurring problems we find in retail telecom
- Store-by-store contracts with no portfolio leverage: Retailers that grew organically often negotiated each store's connectivity individually, usually with whoever the local carrier rep was at the time. The result is a patchwork of contracts at varying rates — sometimes 40–60% higher than what's achievable through a portfolio-level RFP.
- Circuits for closed or remodeled stores: Store closures and remodels are a constant in retail, and carrier disconnects don't always happen cleanly. We regularly find active billing for circuits at locations that have been closed for months, or legacy MPLS circuits that were supposed to be replaced by SD-WAN but were never formally disconnected.
- Inadequate POS failover: Most stores have a primary circuit, but secondary failover — especially in smaller markets — is often a 4G LTE backup that hasn't been tested in 18 months. When the primary goes down on a Friday afternoon, the backup either doesn't work or can't sustain POS transaction volume. Structured redundancy planning changes this.
- Bandwidth that hasn't kept pace with the technology stack: A store circuit provisioned in 2018 was sized for POS, basic email, and a security camera or two. By 2025 that same store might be running cloud-based inventory management, IP surveillance with 4K cameras, digital signage, a loyalty app with real-time sync, and mobile POS devices. The circuit hasn't grown; the application load has.
- Carrier turnover on dedicated account teams: The carrier rep who negotiated your last contract is almost certainly gone. Their replacement has no institutional knowledge of your account, your locations, or your prior pricing. Without a broker maintaining continuity, you're starting from scratch every renewal cycle.
Regional sporting goods chain, Oregon and Washington — 34 stores
A Pacific Northwest sporting goods retailer came to us with 34 stores spread across Oregon and Washington, most of them on legacy cable modem or DSL circuits that had never been consolidated or renegotiated at the portfolio level. Several stores had no formal secondary failover at all. Black Friday weekend had produced two store outages the prior year that the IT director estimated cost roughly $30,000 in lost transactions and staff overtime.
We ran a full inventory audit first and found six circuits billing for a store format that had been rebranded and physically rebuilt two years earlier — the old circuits were never disconnected. That recovery alone offset the first three months of our ongoing engagement.
For the network redesign, we ran an RFP across Comcast Business, Ziply Fiber, and Astound, segmented by market where the carriers actually had footprint. We negotiated a master service agreement covering all 34 stores, with SD-WAN hardware from a single vendor to enable centralized management, and LTE failover from T-Mobile for stores where the secondary wireline option was marginal. Total annual savings: 27% over prior run rate. Zero store outages during the following Black Friday period.
Frequently Asked Questions
- How do you handle stores in markets where only one carrier has fiber?
- Rural and small-market retail is a real constraint. When there's only one wireline carrier with adequate bandwidth at a location, we negotiate as hard as possible on SLA terms, pricing, and contract flexibility rather than pretending we can create competition that doesn't exist. We also look harder at LTE/5G fixed wireless as a genuine primary option in markets where wireless coverage is strong — it's no longer a fallback technology in many Pacific Northwest markets.
- Can you manage the carrier relationship for store openings and remodels?
- Yes, that's a core part of what we do. New store installs, circuit upgrades for remodels, and disconnects for closures all go through us. We handle the carrier ordering, track installation commitments, escalate when installs run late, and make sure disconnects actually complete so you're not paying for circuits at closed locations.
- We already have an SD-WAN vendor — can you still help with the carrier side?
- Absolutely. SD-WAN vendor and carrier are independent decisions, and we work with whatever SD-WAN platform is already in place — Meraki, VeloCloud, Fortinet, Cato, others. The carrier underlay is a separate contract, and that's where our leverage sits. We can also advise on whether the current underlay circuits are properly matched to the SD-WAN platform's performance requirements.
- How does PCI DSS factor into carrier selection?
- PCI DSS compliance is a network architecture question more than a carrier question — the segmentation requirements are met by your SD-WAN or firewall configuration, not by the carrier. Where carriers do matter is in the QSA audit process: some auditors want to see documentation that the carrier network is isolated from your CDE (cardholder data environment) at the circuit level. We make sure the carrier contracts and network diagrams support that documentation requirement.
Let ITG Look at Your Bill
Send us a recent carrier invoice and we'll do a no-obligation first look. You'll hear back within two business days with a quick read on whether there's meaningful savings to find.
Start a Conversation