Why a Stuck Label Costs More Than It Looks
One mispriced item is rarely the headline. The aggregate is. The National Retail Federation's 2023 National Retail Security Survey put U.S. retail shrink at $112.1 billion in 2022 - a category that includes pricing errors and missed markdowns alongside theft. McKinsey's Beating the Shrink on Grocery Shelves work added a useful nuance: operational breakdowns at the shelf, not theft, drive a growing share of that loss in food categories.
When a Saturday-morning promo freezes for two hours, the store pays the spread between displayed and POS prices on every transaction, eats time at the customer service desk, and - in jurisdictions like Quebec, Massachusetts, and parts of California with shelf-price laws - takes on real audit exposure. We treat ESL update failures the same way we treat refrigeration alarms: time-sensitive operational events, not minor IT tickets.
1. The Battery Is Depleted or Near End-of-Life
Battery depletion is the single most common cause we see in support tickets, and it almost never happens overnight. E-paper labels typically run five to seven years on a single coin cell at one to two updates per day, and some specs stretch longer. Aggressive promotional cycles, frequent graphic refreshes, or cold-aisle deployments shorten that window meaningfully - labels installed in a freezer case at −20°C will trend two to three years shorter than the same SKU on a dry-goods aisle.
The display tells you the story: a frozen mid-refresh, a partial ghost image, or a blank screen while the tags around it update normally. Open your management dashboard, filter for battery voltage below the manufacturer's threshold (typically 2.5V to 2.7V for the most common chemistries), replace the affected unit, and reinitialize it to the gateway. If batches of failures cluster in the same aisle within weeks of one another, that is a deployment-age signal - the entire batch is hitting end-of-life and you should plan a rolling replacement rather than treating each failure as a one-off. The physics behind the e-paper battery curve is covered in our breakdown of why ePaper price tags can run for years on a coin cell, and the size-by-size battery specs are listed on each product page - for example, the 4.2-inch electronic price tag we ship most often into grocery deployments.
2. The Gateway Has Lost Power, Network, or Both
If multiple labels in the same physical zone freeze at the same moment, the labels are not the problem - the gateway is. Walk to the access point. Most gateways carry two indicators: a power LED and a traffic LED. Solid green on the power side and fast-blinking green on the traffic side means a healthy gateway. Anything else is your starting point.
A red or off power LED points to a tripped outlet, a damaged PoE injector, or a failed cable. A solid power LED with no traffic activity points to a network path failure between the gateway and the management cloud. In the system-wide outages we triage, the resolution is almost always boring: someone unplugged a gateway to vacuum, or an IT change pushed a firewall rule that blocked outbound traffic to the cloud platform. Confirm the outlet has power, the Ethernet cable is seated at both ends, and the gateway's IP is reachable from the store network. If you want a benchmark for the realistic delivery times you should expect from a healthy gateway before flagging anything as slow, our piece on ESL refresh rates and display performance covers the numbers.
3. RF Signal Interference Is Starving the Labels
A healthy gateway can still let labels at the edge of its coverage receive partial packets, which the firmware refuses to commit. ESL networks run on dedicated 2.4 GHz protocols today, and the industry is moving toward the Bluetooth 5.4 PAwR and EAD profiles that the Bluetooth SIG ratified in February 2023 specifically to handle thousands of low-power tags from a single access point. Either way, that frequency band shares space with Wi-Fi, microwave ovens, walkie-talkies, and metal-heavy fixtures.
Coverage problems cluster geographically. If every stuck label sits in the freezer aisle, behind a metal end-cap, or near the back-of-house break room, you are looking at a coverage gap, not a tag defect. Most modern dashboards surface a per-label RSSI value - anything weaker than around −75 dBm is marginal and worth investigating. Add or relocate a gateway, lower it from a high ceiling, or move it past metal obstructions. A typical industrial gateway covers roughly 25 to 30 meters in retail layouts, which is why dense fixture areas need overlapping coverage rather than a single unit per zone. For more on the protocol side and how it shapes hardware choice, see our overview of electronic shelf label technology.
4. The CMS Is Not Syncing With Your POS or ERP
When every label in your store still shows last week's prices but battery and gateway diagnostics come back clean, the problem is upstream. Your ESL management platform pulls price changes from a pricing master - usually an ERP, a pricing engine, or POS directly. If that sync breaks, the labels happily display whatever stale data the CMS last received, and there is no error visible at the shelf.
Open the integration log inside your CMS. Most platforms record the last successful sync timestamp, the last failed call, and the HTTP response code returned upstream. A 401 or 403 means a credential expired. A 500 or 502 means the upstream system is failing. A clean 200 response with zero records returned means the export job on your POS side is broken - the most common scenario we see immediately after an ERP upgrade. The fix lives outside the ESL stack but the signal lives inside it. The full picture of how price data should flow from POS to shelf is covered in our walkthrough of how electronic shelf labels streamline retail operations.
5. The Label Is Mapped to the Wrong SKU
This one fools store teams because the label is technically updating - it is just updating with the wrong product's data. A new associate scans a tag against the wrong barcode during a planogram reset. A clearance pull leaves an orphan label still bound to a discontinued SKU. The shopper sees the right format, the right currency, the right promo template - just the wrong number on the screen.
Run a binding audit from your CMS. Most platforms can flag tags whose bound SKU has not registered POS movement in 30 or more days, which is a strong proxy for an orphaned binding. Re-bind any flagged tags by NFC scan or barcode pairing. Building this audit into your monthly cadence catches the problem before customers do, and it is one of the lowest-cost preventive habits we see at the operators running retail electronic shelf labels at scale.
6. A Firmware or Scheduling Conflict on the Server Side
The least common but most disruptive cause is server-side. A failed firmware push. A job stuck in the update queue. A maintenance window someone forgot about. Symptoms vary - sometimes new prices queue successfully but never dispatch, sometimes labels show "updating" for hours, sometimes the dashboard itself becomes unresponsive.
Check the platform's status page first. If your vendor publishes one, that single page resolves more tickets than any other diagnostic step. If the platform is healthy but jobs are stuck, look for a firmware update flagged in-progress on any of the affected gateways - firmware pushes often pause normal traffic until they complete. The fix is rarely store-side. Document the affected store and label IDs and open a ticket. End-to-end visibility into this layer is one of the criteria you should evaluate before buying, which is why we built it into our framework on how to choose a retail ESL solution.
Special Case: First-Time Deployment Failures
If the labels never updated at all - meaning you just installed them and the prices have never reflected your CMS - the problem is almost always one of three things, and none of them are tag defects. The tag was not initialized to the gateway after pairing. The gateway was added to the management platform but not assigned to a store. Or the CMS template the labels are pulling was created but never published. Walk through your installation checklist again. Each step in our step-by-step ESL installation guide has a verification action attached for exactly this reason.
New deployments also tend to surface temperature-related issues that show up later. Labels installed in freezer cases without specifying the cold-chain SKU may behave fine during warehouse staging at room temperature and then go blank - sometimes literally - once they hit the cooler shelf. If that happens, you are not troubleshooting a software bug. You are looking at a procurement specification gap, and the fix is replacement with the correct cold-rated variant.
The 60-Second Diagnostic Checklist
Before you escalate anything to your ESL vendor, run these six checks in order. Most store teams resolve the issue at step two or three:
- Confirm whether the stuck labels share a physical zone (gateway or coverage problem) or scatter across the store (battery or software).
- Walk to the nearest gateway and verify both the power LED and the traffic LED are healthy.
- Pull the battery voltage report from your management dashboard for the affected labels.
- Check the integration log for the last successful POS-to-CMS sync timestamp and HTTP code.
- Spot-check three suspect labels for correct SKU binding via NFC or barcode pairing.
- Open your vendor's status page to rule out a platform-level incident.
In our experience handling field tickets, this six-step pass closes most cases without a vendor escalation. Document each step's result so the cases that do escalate arrive with the diagnostic information already attached.
When to Fix It In-Store, When to Call Your IT Team, When to Escalate to Your Vendor
Three boxes worth drawing for your store team before anything goes wrong.
Fix in-store. Anything battery, gateway-power, or SKU-binding related is yours to handle. These are operations cases - waiting on a vendor adds days to problems that close in minutes.
Hand to IT. Anything that points upstream of the CMS - a 500 from your ERP, a corrupted import file, a stalled price-sync job - belongs to your IT or ERP team, not the ESL vendor.
Escalate to your vendor. Anything firmware-, server-, or platform-level - sustained outage, dashboard unresponsive, a scheduled push that locks up traffic - is your vendor's problem from the moment you confirm it. If you don't have a clear escalation path, that is a buying-stage gap to fix; our ESL solutions overview describes the support model we offer customers.
Frequently Asked Questions
How long should an electronic shelf label take to update after a price change?
Most modern ESL networks deliver an update to a single label within 1 to 5 minutes once the change is committed in the CMS. Bulk updates across thousands of labels typically complete within 15 to 30 minutes, depending on gateway density and protocol. Beyond an hour, treat it as an incident.
Can I update an electronic shelf label manually if the wireless network fails?
Yes - labels with NFC support can be refreshed locally with a handheld NFC controller. Useful for emergency price corrections during a network outage. Keep the controller in the store manager's kit; it is a failsafe, not a replacement for the wireless system.
How often should ESL batteries be replaced?
For e-paper labels under typical retail load, plan on five to seven years. Cold-storage deployments and labels updated several times a day will run closer to three to five. Once you pass a few hundred tags, centralized battery monitoring inside the CMS is the only realistic way to track this.
Do electronic shelf labels run on store Wi-Fi?
No. Most professional ESL systems use a dedicated 2.4 GHz radio or Bluetooth 5.4 PAwR through purpose-built gateways. They do not consume store Wi-Fi bandwidth, which is one reason large grocery operators can deploy tens of thousands of tags without affecting customer-facing networks. The retailers profiled in our breakdown of which grocery stores have electronic shelf labels all operate this way, including chains with stores well over 100,000 square feet.
What kind of solution does an ESL system actually include?
At minimum: digital labels, communication gateways, management software, mounting hardware, and integration with your pricing data source. The way these layers fit together, and where most failure modes originate, is laid out in our explainer on what an electronic shelf label solution is.
When should I replace the entire ESL system instead of troubleshooting?
If you are still running a first-generation deployment from before 2018, see end-of-life battery clusters across multiple aisles within the same year, or rely on a discontinued gateway protocol your vendor no longer supports, the math typically favors a phased replacement over ongoing repair. The cost case for migrating is laid out in our piece on why retailers are switching to electronic shelf labels.
