Digital retail shelf labels and price consistency

Keep shelf prices aligned with checkout. Learn how electronic shelf labels receive product data, handle automated updates and reveal failed changes.

Digital retail shelf labels are connected physical displays that receive product information and prices from a store’s systems. They keep shelf prices consistent with checkout when both use the same approved price record and staff resolve failed updates.

A price change has several destinations. Sending it to the label system doesn’t prove the label beside the product has changed, or that the till charges the same amount.

How electronic shelf labels receive a price

An approved product record reaches each electronic shelf label through label-management software and the store’s communications network. The software puts the product information into a display template, then sends it to the assigned physical label.

You’ll also hear these devices called digital shelf tags or digital price tags. A shelf-edge display can be a product label, although larger promotional screens have a different job.

The basic route is straightforward:

  1. Your product or pricing system supplies a product identifier and the approved price for a particular store.
  2. Label-management software matches that record to a label and generates its display content.
  3. A gateway or compatible access point passes the update to the label over the installed wireless network.
  4. The label displays the content and the management system records the update’s outcome, where the installation supports that reporting.

SOLUM’s gateway documentation describes gateways as wireless access points that communicate with labels and connect to the server. Its gateways are registered to stores.

That store connection matters. A correct price sent to a label in the wrong branch still produces the wrong customer-facing result.

Choose the source of product and price data

Give each field an authoritative source before connecting labels. That source is the system your team treats as correct when two systems disagree.

Your product catalogue can own the stock keeping unit (SKU), product name and pack size. Your point-of-sale (POS) or central pricing system can own the selling price and promotion rules. Record which system supplies each field, who approves changes and which downstream systems receive them.

For every price record, carry the SKU, store identifier, selling price and applicable promotion period. Include pack quantity and the unit-price basis where required. A promotion also needs an end action, so its expiry restores the intended price.

Product-to-label mapping joins the product identifier to the physical label’s identifier within the selected store. SOLUM’s label-assignment procedure includes store selection, product confirmation and a label identifier. It also requires a template suitable for the label type and resolution.

Scan the product beside the label when creating or checking this mapping. Compare the pack size as well as the name. Two similar products can have different SKUs and selling prices.

Use the store identifier throughout the price feed and label assignment. Reject a record with a missing or unknown store instead of sending it to a default branch. Where online and store prices intentionally differ, keep their channel rules explicit.

For grocery retailers covered by the ACCC’s Unit Pricing Code guidance, unit prices must be accurate, readable and close to the selling price. Keep the quantity and measurement basis with the price data, so a pack-size change also updates the unit price.

Coordinate automated pricing with checkout

Approve one price change, distribute it to each destination and reconcile the results before treating the change as complete. Choose a release window that your label, till and online systems can support.

Use this sequence for a controlled change:

  1. Approve the SKU, store, new price and promotion rules in the authoritative system. Give the change a reference your team can trace.
  2. Send the approved record to label management. Check its store mapping and the generated label content before release.
  3. Apply the same approved price at the till and online, following the agreed release window and any explicit channel differences.
  4. Inspect the label update result, scan the product at checkout and check the online price. Put every mismatch into an exception list with a named staff member.

Queued means an update is waiting to be processed. Delivered means it has reached the destination reported by that system, which could be a gateway or a label. Confirmed means the system reports the relevant label operation as successful. Define these stages for your installation instead of treating a successful file import as shelf confirmation.

SOLUM’s label-information documentation distinguishes SUCCESS, PROCESSING and TIMEOUT. It also records operation history and completion times. A preview in a processing or timeout state can show the intended image, so compare the physical label too.

If checkout and the displayed price disagree, staff need an immediate sales decision. The ACCC’s price-display guidance gives businesses two options. Charge the lowest applicable checkout, displayed or advertised price. Alternatively, stop selling the item until the error is corrected. Different regional prices and other listed exceptions have separate treatment.

Give staff a way to apply that response while the technical fault is repaired. A pending retry doesn’t settle the customer’s price dispute, and successful synchronisation alone doesn’t establish legal compliance.

Handle failed or stale shelf updates

Start with the affected product and label, then check whether the failure also affects neighbouring labels. One incorrect product points towards mapping or data. Several unresponsive labels on one gateway point towards shared connectivity.

Shelf-label fault checks

SymptomCheckCorrective action
Product has no labelCompare its shelf position and SKU with the assigned label listReplace the missing label, assign it to the correct product and verify the displayed price
Label stops accepting updatesInspect its battery status and physical conditionReplace the battery or device using the model’s maintenance procedure, then resend and inspect the result
Several labels stop updating togetherCheck their gateway’s power, server connection and connectivity statusRestore the gateway connection, then retry affected updates and reconcile every outstanding label
Label shows another product or pack sizeScan the product barcode and compare the mapped SKU and label identifierCorrect the assignment, regenerate the content and check the label against checkout
Right product still shows an old priceCompare the approved change with the last successful operationResolve the failed feed or update, then resend the intended price and check its completion

An exhausted battery needs physical maintenance. Resending an update won’t restore power. Likewise, repeated retries won’t correct a label assigned to the wrong SKU.

After each price-change batch, compare the approved records with successful label operations and checkout results. Keep incomplete changes open until a staff member checks the visible price or applies the exception process.

Add a shelf walk for newly assigned labels and unresolved failures. Scan the product, read the visible price and compare both with the authoritative store record. Include promotion endings in this routine because an expired offer can leave an old price visible.

Evaluate labels and wider shelf signage

Choose price labels for product-level price information and promotional screens for campaigns or wider messages. Both can sit at the shelf edge, but they need different acceptance checks.

Vusion’s retail-media range includes e-paper and LCD displays for centrally managed campaigns. If a promotional screen displays a price, include that price in reconciliation alongside the product label and checkout.

What to compare before choosing a system

CriterionEvidence to request
Data compatibilityA sample import from your actual price system, preserving SKU, store and promotion fields
Update confirmationA demonstration of per-label success and failure records, including what each status proves
Store infrastructureA coverage assessment and a list of required gateways, compatible access points and network connections
MaintenanceProcedures for low batteries, broken labels, replacements and reassignment, with responsibility for each job
Total operating costA quote covering hardware, installation, integration, software charges, support and replacement work

Infrastructure differs between systems. Vusion’s electronic shelf-label range describes deployments using compatible existing access points, partly integrated infrastructure or a dedicated network. Don’t assume the Wi-Fi equipment already in your shop supports the chosen labels.

Use the same store and price-change sample for each supplier’s demonstration. Include a failed update and its recovery. A clear display is useful, but your team also needs to find every product whose price hasn’t changed.

Verify one complete price change

Test one product from approval through the physical shelf and checkout before expanding the rollout. Use a controlled pilot with staff responsible for any price discrepancy.

In this illustrative example, a 500 g bag of coffee has SKU COF500 and label identifier L104 at Store A. Its tax-inclusive selling price changes from $12 to $10 for a promotion. All channels in this example use the same price, and the applicable unit-price basis is per 100 g.

The original unit price is $2.40 per 100 g. The promotion changes it to $2.00 per 100 g, calculated as $10 divided by five 100 g units.

  1. Approve the $10 price for COF500 at Store A, including the promotion’s start and end rules. Keep Store B outside the change.
  2. Confirm that L104 is assigned to COF500 at Store A. Preview the 500 g description, $10 selling price and $2.00 per 100 g unit price.
  3. Release the change to label management and apply it at the till and online under the agreed release process.
  4. Read L104 beside the coffee, then scan that bag at the till and inspect its online listing. Each selling price must show $10 in this example.
  5. Save the approved change reference, label-operation result and checkout check. Record who inspects the physical label and whether Store B remains unchanged.
  6. Test the promotion’s end action. Confirm the label, till and online listing return to $12, with a unit price of $2.40 per 100 g where displayed.

If L104 times out while checkout changes to $10, keep it on the exception list. Apply the store’s price-discrepancy process, correct the fault and inspect the label again after retrying.

Close the exception only when the visible label and checkout match the intended store price. Use that complete record as the acceptance check for the next group of labels.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup