Why the Playbook Determines Rollout Success More Than the Hardware
Electronic shelf labels rarely fail because the hardware was wrong. Rollouts stall because the operating model around the hardware was never designed. A label fleet touches pricing, merchandising, store labor, IT infrastructure and customer communication at the same moment, and each of those functions arrives with its own definition of “done.” An operations playbook is the document that settles those disagreements before the first store goes live, and it is usually the difference between a rollout that finishes on schedule and one that spends eighteen months in a permanent pilot phase.
A credible playbook is not a vendor manual. It is a chain-specific set of decisions written in plain language: who owns the price file, how often it may change, which store roles can override a display, what happens when a label loses contact with its access point, and who has the authority to declare a store officially cut over. Without written answers, pilot stores quietly invent their own workarounds. Those workarounds then become the de facto standard once the rollout scales, and the chain discovers it has forty different operating models instead of one.
The playbook should also document the physical and digital dependencies that determine whether an installation day runs smoothly. Shelf-edge rail compatibility, the condition of existing fixtures, wireless coverage in cold rooms and back aisles, mounting method, and integration points with the point-of-sale, ERP and product information systems all belong in a readiness checklist. Converting these into pass or fail gates is a practical discipline: a store should not be scheduled for installation until the prerequisites are verified, because retrofitting infrastructure after labels are mounted costs far more than a pre-installation survey.
Finally, the playbook should quantify the labor involved. Someone has to map SKUs to labels, mount and verify hardware, resolve exceptions during price changes, and monitor device health month after month. Estimating that work in hours per store, per wave and per week lets operations compare the rollout against a realistic baseline rather than an optimistic one. It also makes the case for store-level ownership credible, because the workload is visible rather than assumed.
Phase One — Pilot Design, Site Readiness and Data Foundations
Pilot store selection is where many rollouts quietly go wrong. The convenient store — the flagship near the head office, with strong connectivity and an engaged manager — will almost always succeed, and will teach the project team almost nothing about the stores that will be hardest to convert. A stronger approach is to choose a small set of stores that reflect the real estate portfolio: a large-format supermarket, a compact urban store and, ideally, one site with difficult conditions such as low ceilings, dense shelving or weak coverage.
Data is the second foundation. Before labels are mounted, the chain needs a single, authoritative SKU-to-label mapping and a clear answer on which system holds the price of record. Ambiguity here produces the worst possible outcome: a chain that has invested in electronic self labels and still runs manual price checks because no one trusts the feed. Integration testing should confirm that price changes flow from the source system to the labels, that failed updates surface as visible exceptions, and that a rollback path exists if a feed behaves unexpectedly.
Success criteria deserve the same discipline. Rather than agreeing that the pilot “went well,” define what must be true before scaling: price accuracy sustained over consecutive weeks, completed installation per store within an agreed window, exception volumes trending down, and store staff able to run daily routines without vendor support. Teams that are still shaping the internal business case often find it useful to review how digital price display supermarkets connect pricing, replenishment and in-store marketing, because it clarifies which workflows the pilot should actually be measuring.
The pilot should also produce artefacts, not just results. Every task performed during the pilot should generate a reusable template: a site survey form, a mounting checklist, a training outline, an escalation matrix, a communications script for shoppers. These become the building blocks of the playbook and reduce the cost of each subsequent wave.
Phase Two — Scaling, Training and Daily Operating Discipline
Scaling is a logistics problem wrapped around a change-management problem. Wave planning should group stores by format, region and infrastructure readiness rather than by district politics, and each wave needs a defined freeze period during which planogram changes are held so that mounting and verification are not chasing a moving target. A template library — label layouts, screen designs, promotional frames and shelf-edge signage conventions — keeps the estate visually consistent without requiring every store to make design decisions.
Training works best as a train-the-trainer model. A small group of store champions learns the full workflow, then supports colleagues in their own stores during and after installation. Frontline training should be practical and short: how to read the device health dashboard, how to confirm a price change has landed, how to replace or reposition a label, and who to call when a shelf edge stops responding. Vendor-written manuals rarely survive contact with a busy Saturday shift, so the playbook should include a one-page quick reference written by the people who actually use it.
Daily operating discipline is what protects the investment over time. A named owner per store, a weekly review of exception queues, a routine for verifying high-velocity and high-value items, and a simple device health routine will catch most issues before customers do. Price-change cadence should be agreed centrally with clear rules on promotional windows, markdowns and end-of-day cut-offs, so store teams know what to expect rather than reacting to surprises.
Customer-facing communication belongs in the playbook too. Shoppers notice new shelf-edge technology, and a short, consistent explanation of what the displays do — accurate pricing, faster updates, clearer product information — prevents confusion and reduces questions at the service desk. Documenting the message centrally, and refreshing it as capabilities expand into in-store marketing and customer engagement, keeps every store telling the same story.
Lagos-born, Berlin-educated electrical engineer who blogs about AI fairness, Bundesliga tactics, and jollof-rice chemistry with the same infectious enthusiasm. Felix moonlights as a spoken-word performer and volunteers at a local makerspace teaching kids to solder recycled electronics into art.