Electronic shelf labels in Australian retail: ESL systems must align product, price and checkout records to avoid mismatches.; The ACCC enforces the mandatory Unit Pricing Code under the Competition and Consumer Act 2010.; Staff must verify shelf displays match approved prices and resolve discrepancies on the spot.
Image: Retail Technology Guide

Self-service Devices

Electronic shelf labels

Understand how electronic shelf labels fit price approval, checkout, shelf placement and exception handling in an Australian store.

Desk Store Systems · · 3 min read

Electronic shelf labels (ESLs) change shelf information through a managed system rather than replacing paper tickets one by one. They work when the product, displayed price and checkout price stay aligned. Faster updates cannot correct a wrong product record or an unapproved promotion.

What an ESL system needs

An ESL project usually links product and price records, label-management software, store communications equipment and the labels beside products. Equipment and connections vary by supplier. The retailer must still decide who approves changes, when they take effect and what staff do when a label fails to update.

Start with what shoppers must read: the selling price, any offer conditions, and enough product detail to distinguish similar variants. Check the label at its installed height under store lighting. An electronic display is not automatically legible.

Unit pricing can be a compliance attribute where required. Check current ACCC guidance and the approved product record rather than assuming a generic label layout is enough.

Some ESL management systems are cloud-based, letting retailers control and update connected labels through a central system. During assessment, check how staff monitor whether information has reached the labels. A sent update is not proof of a correct shelf display.

If using QR codes, decide what information they open and who maintains it.

Follow a price change to the shelf

A price change has several separate events:

  1. An authorised person approves the price, product, store and effective period.
  2. The approved record reaches checkout and the label system.
  3. The correct physical label is associated with the correct product.
  4. The label displays the intended price.
  5. Staff identify and resolve any customer-facing mismatch.

Ask a supplier what evidence its system provides for each event. A message sent to store equipment differs from seeing the intended price on the correct shelf label. An update can succeed while the label is attached to the wrong product.

Check promotions at their start and end, including the checkout price during each transition. Establish what happens when a store loses connectivity and how staff recognise a label still showing an old price.

Central management may reduce paper use.

Decide whether ESLs fit the store

Compare the proposed system with current ticket work: how often prices change, time spent replacing and checking tickets, and errors staff resolve. Request a proposal that identifies label hardware, fixings, communications equipment, integration, subscriptions, replacements and support. These are cost categories, not an estimate of savings.

Use the store's awkward cases in a demonstration: similar pack sizes, an expiring promotion, a moved product and an unresponsive label. Check who can pause a release and correct the governing price record. A general integration claim does not establish how the retailer's configuration will behave.

Confirm labels fit the fixtures, remain beside the intended products and can be read from normal shopping positions. Check proposed equipment before use in refrigerated areas or other unusual conditions. Give staff a procedure for missing, damaged or unresponsive labels.

ESLs are used in settings including grocery and department stores, electronics retailers, DIY and home-improvement stores, appliance stores, convenience stores, and liquor and beverage stores. The range of uses suggests assessing the proposed label against the information shoppers need in that particular store. A format suited to one retail environment may not suit another.

A rollout can be modular, with deployment incremental or at scale according to business priorities. Consider whether the system can accommodate the store formats and regions in scope. Confirm how label accuracy and consistency will be checked across the rollout.

Resolve a price mismatch

When shelf and checkout prices differ, staff should check both against the approved price record, explain the discrepancy to the shopper and follow the store's customer-resolution process. For a conditional offer, check that the shelf display states the relevant conditions and that the approved promotion record matches them.

Before expanding an ESL installation, check a defined range against the approved record, checkout and actual shelf display. Record mismatches and their causes.

The Unit Pricing Code is a mandatory industry code under the Competition and Consumer Act 2010. The ACCC enforces it and provides guidance materials about code obligations.

For price-display issues, the ACCC accepts reports and can investigate alleged breaches; it does not give legal advice to businesses about how they display prices or resolve individual disputes. A store response process therefore needs to resolve the shopper's immediate issue without relying on the ACCC to settle it.

In this guide

  1. Comparing shelf-label systems by update workflowCompare Vusion, Pricer and SOLUM on the documented route from an approved price to a shelf label, with limits to verify in your store.
  2. Connecting shelf prices to approved product dataMap product identity, approved selling prices, promotions and unit prices before publishing information to electronic shelf labels.
  3. Testing price consistency between shelf and checkoutUse a defined store sample to compare actual shelf prices with checkout, trace mismatches and check promotion changeovers.

More from Self-service Devices