Why this list exists
We’ve seen enough single-store ESL pilots — both ones that scaled to chain rollout and ones that died at the pilot — to identify a small number of recurring failure modes. The technology almost never fails. What fails is one of these seven operational patterns.
If you’re scoping a pilot, run through this list before committing.
1. POS feed mismatch — silent
The pilot launches, labels show prices that look right, you celebrate. Then a customer at the register sees a different price than the shelf. Investigation reveals the ESL is pulling from a stale data view that doesn’t include this morning’s promotional updates.
Mitigation: run the pilot in “shadow” mode for 1-2 weeks before committing. Compare ESL price against POS price for every SKU daily. Catch data-mapping gaps before they hit checkout.
2. Gateway coverage hole in one section
Most labels update fine, but the produce cooler or the back-aisle freezer never updates reliably. The gateway signal isn’t reaching that area. Stocker reports labels showing yesterday’s price.
Mitigation: include a site survey before deployment. Don’t trust generic “one gateway covers 10K labels” rules — actual coverage depends heavily on metal racking, cold-storage walls, and store geometry. Order one extra gateway as backup; it’s cheap insurance.
3. Wrong label size for the shelf
The 2.9″ labels you ordered look great on the standard gondola but won’t fit on the narrower endcap rails or the cooler-door fixtures. Now you have ESLs you can’t mount.
Mitigation: use the free print-and-cut PDF templates to test paper cutouts of every label size on every shelf type before ordering hardware. Pilot with at least three sizes if your store has varied fixtures.
4. Store staff don’t know the new workflow
The labels update automatically. But when an ESL falls off, who replaces it? Who pairs new SKUs to new labels when product moves? Who reports a label that’s blank or showing a ghost image? If staff don’t have answers, the pilot decays over weeks as labels become orphaned.
Mitigation: 30-minute training session before launch covering: how to use the smartphone app for re-pairing, how to flag a problem label, who to escalate to. Print a one-page reference card and laminate it for the back-of-house break room.
5. Promotion logic in the cloud platform set up wrong
Regular price displays correctly. Then the weekend promo kicks in, and labels show “WAS $X / NOW $Y” as expected — but the WAS price is wrong because the platform pulled the wrong field from the POS. Or the promo doesn’t expire on Sunday night because the end-date logic was set up with the wrong timezone.
Mitigation: run a promo simulation on day 3 of the pilot. Walk a manager through enabling, observing, and ending a fake promotion. Confirm price reverts cleanly when promo ends.
6. Battery low-warnings ignored
Some ESLs ship with batteries that started their shelf-life clock months before you got them. A small percentage of pilot labels will hit battery-low warnings within months instead of years. If nobody is checking the platform’s battery dashboard, those labels go silent.
Mitigation: someone at the store needs to check the cloud dashboard’s battery status weekly during the pilot. Set up email alerts for “X labels approaching low battery.” Replace the few that age out early; this is normal.
7. The pilot was scoped too small to learn anything
500 labels in one section of one store. Six months in, you don’t have enough data to make a chain-wide decision because the pilot is too narrow. Costs not measured against representative SKU mix. Operational learnings don’t generalize because the section was atypical.
Mitigation: pilot at least 5,000 labels covering at least 3 representative sections (high-velocity grocery + low-velocity dry goods + at least one promo-heavy section like beverages). Cover an entire SKU lifecycle including at least one chain-wide promotional cycle.
The single-page pilot checklist
| Phase | Action | Done? |
|---|---|---|
| Pre-launch | Site survey for gateway coverage | ☐ |
| Pre-launch | Print-cut sizing test on every shelf type | ☐ |
| Pre-launch | POS feed validation in “shadow” mode (1-2 weeks) | ☐ |
| Launch | 30-min staff training on app + escalation paths | ☐ |
| Day 3 | Run end-to-end promotional cycle test | ☐ |
| Weekly | Check battery dashboard, replace early-life labels | ☐ |
| Monthly | Compare measured savings against pre-pilot baseline | ☐ |
Need help scoping a pilot that won’t fail?
30-minute call to size your pilot, identify which sections to include, and avoid the seven traps above. No commitment.