Electronic shelf labels (ESLs) have quietly moved from pilot to mainstream. Walmart announced in 2024 that it would bring VusionGroup digital shelf labels to 2,300 U.S. stores by 2026, and grocers across Europe have been running large estates for years. Yet in 2026 the same small e-paper tags became a political flashpoint. Lawmakers in several U.S. states now treat ESLs as possible infrastructure for “surveillance pricing,” and at least two states have passed laws that touch the topic directly. For retail and IT leaders, the question is no longer whether ESLs work. It is how to deploy them so that the operational upside is captured and the trust risk is designed out from day one.
This playbook walks through what is changing, how a modern ESL system is put together, how to build an honest business case, and the governance controls that will matter as pricing regulation tightens.
Why ESLs Are Back on the Agenda in 2026
Three forces pushed ESLs up the priority list this year. The first is labor. Shelf-edge price changes are a hidden, recurring cost. According to Retail Dive’s coverage of the Walmart announcement, a Walmart associate described price updates falling from about two days to a few minutes once tags were digital, in stores that carry more than 120,000 items and change prices on thousands of products each week. When labor is scarce and wages rise, removing that manual work is attractive.
The second force is omnichannel consistency. Shoppers routinely compare the shelf price with the app price while standing in the aisle. Any mismatch generates complaints, price-match claims and, in some jurisdictions, regulatory exposure for inaccurate pricing. A centrally controlled label estate makes it far easier to keep store, web and app aligned.
The third force is that the tag has become a platform. Modern labels include LEDs, NFC, and in some product lines rails that carry sensors or small displays. Walmart has said publicly that lights on its tags will flag shelves needing restocking and guide associates during online order picking. That turns the shelf edge into an operational endpoint rather than a price sticker.
The Regulatory Turn: Surveillance Pricing Laws and ESL Scrutiny
The policy debate centers on a fear that digital tags plus customer data could let stores raise prices for specific people or moments. The reality of what has passed is narrower, but it is moving fast, and every ESL program should be designed with it in mind.
- Maryland. As reported by Modern Retail, Maryland’s Protection From Predatory Pricing Act takes effect on October 1, 2026. It bars retailers of at least 15,000 square feet that sell tax-exempt food, plus third-party delivery services, from using personal data to set higher individualized grocery prices. Promotions and loyalty discounts remain allowed, and an early push to ban ESLs outright did not survive the legislature.
- New Jersey. The Fair Price Protection Act, signed in July 2026, prohibits charging different shoppers different prices for groceries and household essentials based on browsing behavior, location or past purchases. It also pauses new ESL installations for one year while the state studies the technology, though existing units can be operated, repaired and replaced.
- Other states and federal proposals. New York, Washington, Minnesota and others have debated bills ranging from disclosure rules to outright ESL restrictions, and federal bills targeting surveillance pricing in grocery have been introduced. The landscape will keep shifting through 2027.
The common thread is not the hardware. It is the use of personal data to set individualized prices, and the speed of price changes without transparency. Retailers that can prove what their tags do, and what they never do, will be in a stronger position with regulators, unions and shoppers alike.
ESLs are not the risk; opaque pricing logic is. Build the audit trail and the guardrails into the architecture before the first tag goes on the shelf.
How a Modern ESL System Fits Together
An ESL program is an IoT system with a retail brain. Understanding the layers helps teams avoid the most common integration surprises.
Edge devices
Tags are typically e-paper displays in several sizes, running on coin cells designed to last years. Product lines vary in refresh speed, color support (black, white, red, yellow), LED flash patterns and NFC for linking a phone to a product page or an associate task. Chilled and frozen zones need variants rated for low temperatures and condensation.
Radio infrastructure
Ceiling-mounted access points or base stations communicate with tags using proprietary low-power radio protocols. Coverage planning matters: metal shelving, freezers and dense displays all affect reliability. Plan for a radio survey per store format and for redundancy in high-change areas such as fresh and promotions.
Management platform
The vendor’s cloud or on-premises platform holds the tag inventory, templates, bindings between tag and product, and the queue of updates. It reports battery status, failed updates and orphaned tags.
Retail system integration
The ESL platform should never be the source of truth for price. Price must flow from the pricing engine or ERP, through the same event pipeline that feeds point of sale, e-commerce and apps. That single pipeline is what guarantees shelf and till agree, and it is also the place to enforce governance rules.
Security and resilience
A label estate is a fleet of tens of thousands of networked devices per region, so it deserves the same security review as any other operational technology. Ask vendors how tag updates are authenticated, how base stations are patched, how the cloud tenant is isolated, and what happens to store pricing if the WAN link drops. A good design caches the latest approved prices locally, keeps displaying them during an outage, and reconciles automatically when the connection returns. Role-based access with approval workflows for manual price overrides closes another common gap, since a single compromised admin account should never be able to reprice a whole chain.
Building an Honest Business Case
Vendor ROI calculators tend to assume everything goes right. A credible case breaks value into categories you can measure in a pilot and avoids counting benefits twice.
- Price-change labor. Measure current hours per week spent printing, sorting and hanging labels, including weekend promotion resets and audit rework. Use your own time studies rather than generic percentages.
- Pricing accuracy. Baseline shelf-to-till mismatch rates from audits and customer complaints. Include the cost of refunds, price-match concessions and regulatory fines where they apply.
- Markdown and waste. For fresh categories, model the effect of timely, rules-based markdowns on near-dated stock. This is often the most valuable lever in grocery and it is a price reduction, which is less contentious.
- Fulfillment productivity. If associates pick online orders in store, test LED-guided picking against current pick rates and error rates.
- On-shelf availability. Where tags or rails integrate with shelf sensors or computer vision, quantify lost sales recovered through faster gap detection, but only after you have proven the detection accuracy.
- Paper and consumables. Small individually, meaningful across a large estate, and easy to verify.
On the cost side, include tags, access points, installation, store downtime, platform licenses, integration work, battery replacement cycles, spares, and a realistic allowance for tags that are damaged by carts and shoppers. Also price the governance work described below; it is not optional anymore.
Governance Controls That Keep Shopper Trust
The best way to answer the surveillance pricing question is with controls that are technical, documented and auditable. The following set works for most grocery and mass retail operators.
- Data separation by design. The shelf price pipeline should accept product, store and zone inputs only. Customer identifiers, loyalty profiles and device data should be architecturally unable to reach it. Personalized offers, where used, belong in the app or at checkout as discounts, never on the shared shelf.
- Change-frequency limits. Define a policy for how often a shelf price can change in a given window and which categories are eligible for intraday change. Enforce it in the pricing service, not in a slide.
- Direction rules. Many retailers commit to intraday changes that only lower prices, for example end-of-day markdowns on perishables, while price increases follow a scheduled cadence.
- Emergency locks. Freeze price increases automatically on designated essentials when a declared emergency or weather event triggers local price-gouging rules.
- Immutable audit log. Record every shelf price, the time it was displayed, the rule or user that set it, and the matching POS price. Keep the log long enough to answer a regulator or a class action.
- Public pricing policy. Publish a plain-language statement of what your tags do and do not do. Several industry groups have argued that ESLs contain no cameras and cannot identify shoppers; make that claim verifiable for your own estate.
If your tags or rails carry cameras for shelf monitoring, treat that as a separate privacy assessment. Point cameras at products, not people, process frames at the edge, and discard imagery once stock status has been extracted.
A Step-by-Step Rollout Plan
- Discovery (4–6 weeks). Map the price data flow end to end, list every system that consumes price, collect labor and accuracy baselines, and check the regulatory position in each state or country where you operate.
- Architecture and vendor selection. Evaluate two or three vendors on radio performance in your actual store formats, API quality, template flexibility, cold-zone tags, security posture and total cost over seven to ten years.
- Integration build. Publish price events once from the pricing engine to POS, e-commerce and the ESL platform. Add the governance rules and audit log in this shared layer.
- Pilot (2–3 stores, 8–12 weeks). Choose formats that differ in size and category mix. Measure the same metrics you baselined, plus tag failure and update latency.
- Operational readiness. Train associates on tag binding, replacement and exception handling. Define who owns failed updates overnight.
- Wave rollout. Roll out by region with a repeatable installation runbook, a store go-live checklist and a hypercare period for each wave.
- Continuous improvement. Review markdown performance, accuracy and governance logs monthly. Add use cases such as LED picking or shelf sensing only once the core pricing flow is stable.
Worked Example: A Regional Grocer Plans Its First Wave
Consider a hypothetical regional grocer with 120 stores across three U.S. states, one of which has passed a grocery surveillance pricing law. The grocer’s motivation is labor: weekly promotion changes consume many associate hours per store, and audit findings show recurring shelf-to-till mismatches in fresh and frozen.
In discovery, the team finds that prices reach POS from the ERP but reach the e-commerce site from a separate feed, which explains some online-versus-shelf complaints. The architecture decision is to build a single price event service that feeds POS, web, app and the ESL platform. That service enforces three rules: no customer data inputs, intraday changes allowed only as reductions on perishables, and a full audit log retained for several years.
The pilot runs in three stores: a large suburban format, a small urban format and a store with an extensive frozen section. After ten weeks, the team compares measured labor savings and mismatch rates against baselines and confirms that tags in freezer aisles meet update latency targets. It also tests LED-assisted picking for online orders in one store but defers that use case because associate adoption needs more training.
Before wave one, legal reviews the published pricing policy, and the grocer briefs its union representatives on the data separation design. Rollout then proceeds by region, starting with the two states where no pause on new ESL installation applies, while the third state’s rules are monitored.
Pitfalls to avoid
- Letting the ESL platform become a second pricing system with its own overrides.
- Skipping radio surveys and discovering dead zones in freezer aisles after installation.
- Underestimating tag damage and the spares and replacement workflow that it requires.
- Treating dynamic pricing as the headline benefit. In grocery, markdowns, accuracy and labor deliver value with far less trust risk.
- Ignoring state-level legislation that can pause installations or restrict data use mid-rollout.
- Failing to involve store teams and labor representatives early, which turns a productivity project into a dispute.
Outlook: From Price Tag to Shelf Intelligence
Over the next two years, the shelf edge will continue to absorb functions. Vendors are combining labels with rails, cameras and sensors to detect gaps and planogram compliance, and retail media teams want small shelf displays for sponsored messages. At the same time, GS1’s Sunrise 2027 push toward 2D barcodes will bring richer product data, including batch and expiry, into store systems, enabling more precise markdowns on near-dated items.
Regulation will keep evolving, and it will likely distinguish sharply between price changes driven by product and market conditions and those driven by personal data. Retailers that already separate those flows technically, and can prove it with logs, will be able to adopt new shelf capabilities without reopening the trust debate each time.
Conclusion
Electronic shelf labels are a mature technology entering a period of heightened scrutiny. The winners in 2026 and beyond will treat an ESL program as a pricing governance project with an IoT component, not as a hardware swap. Integrate price once, separate customer data from shelf pricing, cap and log changes, start with markdowns and accuracy, and expand to picking and shelf sensing once the foundation is stable. Done this way, ESLs cut labor and errors while giving shoppers and regulators a clear answer to the question of how your prices are set.
How Hanoi Technology Can Help
Hanoi Technology helps retailers integrate ESL platforms with pricing, POS and e-commerce systems and build the audit and governance layer that keeps shelf pricing transparent.
Further Reading
- Walmart to bring electronic shelf labels to 2,300 stores – Retail Dive
- What Maryland’s dynamic pricing ban says about the ESL debate – Modern Retail
- New Jersey bans surveillance pricing on groceries, pauses new ESLs – Shopifreaks
- Electronic Shelf Labels in Global Retail (2026) – International Supermarket News