A promotion can be correct in the pricing system and still be wrong at a particular checkout or shelf. The useful solution is a reconciliation that checks three things separately: the approved price, the active checkout price, and what a shopper can see at the right shelf position. An electronic shelf label (ESL) gateway helps deliver and track label changes. Store staff still need a way to verify displays and resolve exceptions.
This guide is for grocery and big-box pricing teams, store operations leads, and the integrators who support their checkout and label systems. Start with one promotion and one store. Expand once staff can explain and resolve every exception in the pilot.
Connect the price to the right item and location
Use the approved pricing or promotion system as the source of the intended offer. Store the store ID, SKU and scannable item code, qualifying size or unit, effective time and time zone, price version, and any applicable loyalty or quantity rules. Compare checkout under the same terms a shopper would use. Check active lane data or use an approved test transaction when the pricing system alone cannot tell you what the lane will charge.
Maintain a mapping from store and shelf position to tag identity and item. At installation or relocation, scan the item and the tag together, then verify the physical position. Include endcaps and secondary displays. The same item may have several tags, and a tag can respond correctly while sitting below the wrong product. Flag duplicate or stale mappings for store staff before releasing the affected change.
Work through a promotion with incomplete updates
Suppose a supermarket schedules 80 tag positions to change at 09:00. At 09:05, 74 tags report the expected display or image state, three report an older state, and three have no response. Report 74 of 80 positions with the expected state and six unresolved. A gateway entry that says all 80 commands were sent is a separate measure. Test scans confirm the expected offer on the sampled lanes and items, so the first follow-up is at the six shelf positions. This example is a pilot exercise with invented numbers.
The price lead retries the three outdated tags once and checks whether the others share a dead zone or battery problem. A physical spot check also finds one of the 74 responding tags clipped under the wrong pack size. Staff correct the placement, confirm the display and checkout under the same offer, then record the correction. Track this placement error separately from the six device exceptions. You cannot infer a storewide shelf accuracy rate from the device response count or from a convenience sample.
Agree in advance when the price lead can pause further rollout, apply the store’s signage or checkout exception procedure, or request an authorized reversal. Treat a reversal as a new approved price version. Verify both checkout and affected tags after the change. A delayed response to an earlier version must not close a newer exception. NIST’s price verification guidance explains why displayed and charged prices are compared directly.
Choose how the gateway talks to the labels
Start with the installed label inventory. Record the manufacturer, model, firmware, band, available vendor integration, and which responses it exposes. A supported vendor access point and API are often the fastest route to a reconciliation. Evaluate a custom gateway when you need store-owned event history or have an integration requirement the existing platform cannot support.
- Bluetooth electronic shelf labels. Confirm support for the Bluetooth ESL Profile on the access point and the exact tag firmware. Periodic Advertising with Responses (PAwR) lets compatible tags listen on a schedule and reply in assigned slots. The application still needs onboarding, keys, image transfer and display commands, retries, and usable status. Test image transfer and display-state confirmation separately. A Bluetooth version number alone cannot establish either interoperability or capacity.
- ESP32 gateway candidate. An ESP32-P4 can run wired application logic, maintain the local version queue, and connect to an external Ethernet PHY over RMII. A PoE installation also needs suitable powered-device hardware. An ESP32-C6 can be evaluated as the separate Bluetooth LE radio processor. Espressif provides an ESL Profile component and a C6 PAwR example. Its C6 feature table lists PAwR as experimental. Pin the tested firmware versions and prove end-to-end behavior before specifying this combination for a store rollout. Where the custom radio is unnecessary, keep the vendor access point and integrate at its supported boundary.
- Mixed label fleets. Bluetooth LE uses 2.4 GHz. A proprietary 2.4 GHz or sub-GHz fleet needs its own compatible radio and vendor-supported protocol path. A separate SPI transceiver is only useful if your team can support the required protocol, antenna, enclosure and authorized radio configuration. Bring both fleet types into a common price exception view while retaining what each device response actually means.
Record the timestamp and meaning of each response. A tag’s radio reply, reported image index, and a staff check of the rendered price are different observations. Where tags expose supported battery data, record the field and its age and use it to plan service. Where LEDs support pick-to-light, time a separate picking trial with flash timeout, wrong-item rate, and the same basket mix. Keep LED traffic from delaying price work.
Set a pilot that exposes failures before a wider rollout
- Measure a baseline. Time a current promotion, count affected shelf positions and how many require a second visit, and identify who owns pricing, checkout and floor checks.
- Stage representative changes. Include a quantity offer, a promotion expiry, the same item in two locations, and tags near metal fixtures or cooler doors. Check end-of-aisle coverage and a realistic busy wireless period. Repeat with tags that have weaker batteries or missed prior updates.
- Exercise disruptions. Disconnect the gateway uplink, reboot it with updates queued, remove a tag, and simulate a delayed response from an older price version. An e-paper tag can still show its last image while it is unreachable. Check that the gateway resumes without repeating stale prices and that a silent label stays unresolved. Give the price lead a visible record of each exception and its owner.
- Report outcomes with denominators. Measure checkout agreement in a documented sample, expected tag state by the agreed deadline out of all affected positions, and elapsed time to close exceptions. Report the median and slowest tail of update times alongside the unresolved count. Test burst load with the intended firmware, image size and RF environment before assigning a tags-per-gateway capacity.
A useful pilot leaves the team with a repeatable release check and a short exception list for the pricing lead, floor staff and IT. Compare that result with the existing process before paying for more gateways or promising a faster promotion window.