A checkout line fails in seconds when the uplink hiccups. The fix is not another consumer modem or a 5G dongle. It is a clean, dual-entrance fiber design with verified path diversity, fast failover, and enough headroom for POS, cameras, loyalty apps, and nightly uploads. Use the guide below to spec it right, price it fast, and accept it with evidence.
Executive snapshot
Objective
Keep POS, scanners, loyalty, and price checks online during cuts and peaks.
Targets
Jitter p95 under 8 ms, packet loss under 0.1 percent, failover under 300 ms.
Design
Two curb entrances to different rooms and different first-handholes. Photo-verified.
5G or cable is fine as a tertiary path. It does not replace a second fiber entrance. Treat wireless as grace, not as diversity.
1️⃣ What actually breaks POS
Retail timeouts are rarely the card reader. They are almost always uplink conditions or DNS and path changes at the wrong second.
Common causes
- Microbursts push uplink to 100 percent during shift changes and price updates
- Jitter spikes above 10 ms on shared DIA paths during busy hours
- Packet loss above 0.3 percent forces retransmits that stall authorizations
- Failover that takes seconds, not milliseconds, due to BGP or VRRP tuning
- Both circuits in the same lateral or bridge crossing get cut together
Simple fixes
- Reserve QoS for POS, gift, and returns queues until you upgrade
- Move DNS to resilient anycast with short TTLs for faster resolution
- Use SD-WAN or dynamic routing that detects loss and jitter, not just link down
- Buy the second entrance and prove it with photos and first-handhole IDs
2️⃣ Dual-entrance fiber that actually survives a cut
Diversity is physical, not just a different logo on the bill. Two entrances, two routes, two handholes, and no shared choke points.
| Element | Acceptable | Not acceptable |
|---|---|---|
| Building entrances | Two curb points on different sides | Two conduits at the same curb box |
| First handhole | Different handholes with IDs and photos | Same handhole feeding both |
| Path overlaps | Less than 10 percent overlap inside 100 m | Shared trench or bridge crossing |
| Carrier mix | Two carriers or two independently owned segments | Resale on the same physical ring |
| Room separation | Separate IDF/MDF rooms | Same rack and same riser |
Diversity score estimator
Score (0 to 100)
—
Assessment
—
Hint
—
Use the score to screen options. Always require entrance photos and first-handhole IDs before award.
3️⃣ Capacity planning for lanes, scanners, cameras, and apps
Right-size uplink so peak hours never slam to 100 percent. Include cameras, loyalty, price updates, and nightly uploads.
Quick capacity helper
POS burst requirement
—
Total peak estimate
—
Suggested symmetric tier
—
Assumes 1.5 protocol overhead factor and 70 percent comfort peak. Choose the next tier up for growth.
4️⃣ Failover that feels invisible to the cashier
Aim for sub-second stateful failover. Use SD-WAN or routing that measures loss and jitter and moves flows before the customer notices.
Practical design
- Two underlays that never share the same first handhole
- Health checks for packet loss and jitter, not just link down
- Per-application steering: POS and returns get the cleanest path
Turn-up test
- Run a live transaction while pulling one entrance
- Record downtime in milliseconds with a continuous ping
- Repeat in both directions and keep the screenshots in the as-built
Failover target check
Result
—
Guidance
—
Reminder
Test during real peak hours
5️⃣ What downtime costs in a retail month
Small hiccups add up. Price the risk so a second entrance is easy to approve.
Downtime cost calculator
Lost gross margin / month
—
Soft costs / month
—
Total monthly impact
—
Use conservative inputs. Show both CFO and store ops so the budget and the pain match.
6️⃣ Acceptance checklist before you pay the NRC
Close the loop with evidence. If it is not in the as-built, it does not exist.
Proof pack
- Entrance photos from curb to building room for both paths
- First-handhole IDs, GPS, and photos for both paths
- Route map with distances and all bridge, rail, river crossings
- OTDR traces and light levels at turn-up
- Failover screenshots showing sub-second results
Service settings
- Jitter p95 and loss thresholds logged for 14 days
- QoS policy that protects POS, gift, returns, and price files
- DNS anycast with short TTLs and two independent resolvers
7️⃣ Vendor question pack you can paste into your RFP
8️⃣ Red flags that mean fake diversity
- Both fibers emerge from the same curb box or handhole
- A “ring” that returns to the same bridge crossing
- Aerial pairs on the same pole line for miles
- Resale on the same physical sheath sold under two brands
- MMR sharing that forces both paths through a single rack
- No photos or first-handhole IDs offered before signature
9️⃣ Quick glossary for your team
| Term | Plain meaning |
|---|---|
| Entrance | Where a path enters the building at the curb or wall |
| First handhole | The first access vault outside the building that your path uses |
| Diversity | Two paths that do not share the same physical choke point |
| Failover | How fast traffic moves to the other path when conditions degrade |
If your stores feel choppy during busy hours, assume path risk first. Prove two entrances, prove two first-handholes, and record a sub-second failover with screenshots. Once the physical design is right, right-size the symmetric tier and lock in QoS so authorizations, returns, and price updates never fight each other.
