ESL in retail: more than digital price tags

At first glance, ESLs look like price tags – just digital. The first benefit is obvious: less printing, less sticking labels, and less chaos on promotion days. But by the time you’re running a pilot, it becomes clear that ESLs change more than just the label. Once prices and shelf information are delivered as data, price labeling becomes a question of systems, data quality, and operations. The “label” on the shelf is no longer a standalone display – it’s the visible endpoint of an entire process chain.

And once you’re deep in day-to-day project work, it’s clear that ESLs in retail are less about the hardware than about integration, price governance, and running them reliably across a store network. In this context, price governance means the rules and responsibilities that determine how prices, promotions, and shelf content are published at the shelf.

Behind a small digital price label sits an entire cycle of data and decisions. Item and price data come from the inventory management system and pricing, while promotions come from campaign and offer planning. The POS has to stay in sync – otherwise the “right” price on the shelf isn’t worth much. The ESL management layer translates that data into templates, pushes updates, and monitors whether they’ve arrived correctly.

Depending on the setup, content from product or content systems may be added as well – for example icons, labels, QR codes, or promotional markers. That means data quality affects both the price and how it’s displayed. ESLs make existing logic visible – and with it any gray areas that show up immediately at the shelf as incorrect prices or missing information.

Across a store network, ESLs only work with clearly defined roles. Often, pricing owns the price and promotion logic, IT runs the platform, and operations executes in-store – including defined paths for handling exceptions.

Most ESL installations rely on low-power displays – often e-paper – because they’re practical at store scale. Color displays become interesting when you want promotions or additional information to be more visually guided. The trade-off shows up in daily operations: power demand, battery life, and update frequency directly affect maintenance effort and monitoring.

In projects, three questions tend to take center stage: How often will prices be updated? How “quiet” does the label stay despite added information? And how do you present promotions in a way that’s instantly clear at a glance? A useful rule of thumb is this: shelf space is a scarce information environment. ESLs can do more than what’s actually sensible to show on a label.

One of the most important project questions is: what counts as the binding source of truth for the shelf price in our organization? In many retailers, multiple pricing logics exist side by side – base prices from the ERP system or price lists, rule-based prices from pricing, promotional prices from promotion planning, local adjustments in the store, or differences by channel.

With ESLs, those priorities have to be unambiguous. Otherwise you end up with conflicts that can make a rollout expensive.

Typical conflicts include:

• Promotion vs. pricing: The promotion starts at 8:00 a.m., and right before that a new pricing rule kicks in. What applies at the shelf?
• POS vs. shelf: The POS has already been updated, but the shelf labels are lagging behind – or the other way around.
• Master data vs. display: Unit price, unit of measure, or deposit values are maintained inconsistently and become immediately obvious on the label.

A simple principle helps: the shelf price matches the POS price, is calculated according to defined rules, and is published from one clearly named system. It sounds obvious, but in implementation it saves a lot of time – and a lot of debate.

In everyday ESL use, templates determine whether the system is truly robust. A template doesn’t just define the layout – it also encodes rules. It specifies which required information must always be visible, what happens when data is missing, how promotions are displayed, and how readability is maintained.

Typical decisions include:

• required fields such as price, unit, unit price, and – where applicable – deposit information
• fallbacks for missing data instead of leaving fields blank
• clear promotion treatments without visual overload
• category-specific variants
• defined font sizes, contrast rules, and icon usage

A practical example: unit price. If products come in g, kg, ml, and l, you need clear rules for which unit applies and how values are rounded.

The ESL system has to run reliably in everyday operations, which makes monitoring essential – especially during rollout, when you can’t support every store one by one anymore. In a store network, the wireless and network layer quickly becomes an underestimated success factor. Promotion launches, in particular, reveal whether updates flow through cleanly or whether parts of the store fall behind.

These points should be clarified early:

• per-label status (online/offline, last update timestamp, battery level)
• exception processes for defects, dead batteries, or incorrect assignment
• update logic: batching, prioritization, and verification
• clear responsibilities between the store, IT, and service partners

A typical pitfall: pilot stores run under intense attention. That isn’t scalable in rollout. Without defined processes, ESL can flip from an efficiency gain into a constant operational headache.

If ESLs are meant to do more than just show the price, the guiding question is straightforward: which information actually helps customers make a decision? The best add-ons are usually the ones that improve orientation or prevent common follow-up questions. Here, too, clear information logic and strong data quality are prerequisites.

Typical high-value fields include:

• deposit notes and pack sizes
• origin or quality markers
• variants and compatibility information in non-food
• availability indicators or suggested alternatives
• multilingual support and accessibility through consistent icons

QR codes can act as a “door” – the additional details and multimedia content live behind the scan.

Digital means flexible – but not arbitrary. From the customer’s perspective, the ESL price is the “official” price. Errors at the shelf can undermine trust fast. That’s why retailers need to get three things especially right: unambiguous assignment of price to item, complete and highly readable required information, and clear rules for how promotions are displayed. Trust is built through consistency.

Four typical in-store situations that put ESL processes to the test.

• Promotion launches in the morning: Late updates create contradictions. Prioritization and verification are what count here.
• Refrigerated and fresh departments: Operationally demanding – often best tackled after standard shelving is stable.
• Non-food with variants: Variant logic stress-tests both master data and templates.
• Clearance and expiry-date pricing: Technically feasible, but operationally a governance question.

Electronic shelf labels aren’t just a digitization project – they’re a stress test for pricing logic, data quality, and organizational setup. Retailers that implement ESLs successfully don’t just gain speed; they gain transparency – into processes, responsibilities, and decision paths. That’s the real impact: ESL force you to make rules explicit instead of letting them remain informal, store-by-store habits.

For retailers, the investment pays off when ESL aren’t treated as an isolated tool, but as a binding communication channel at the shelf. If you build integration, governance, and operations the right way from the start, you create a solid foundation for scaling, trust, and future use cases. In that sense, ESL are less an end in themselves than a lever for making price labeling reliably manageable – and future-proof.

Sources: GS1 Digital Link, Price indication directive (European Commission), ABI Research, ALDI Nord, Preisangabenverordnung (PAngV)