Definition
ESL (Electronic Shelf Label, electronic price tag) is an electronic display device on retail store shelves that replaces paper price tags, allowing remote bulk updates of product prices, promotional information, QR codes, inventory status, etc. ESL usually uses e-ink screens, which are low power, easy to read, and visible in sunlight, and communicate with backend systems through 2.4GHz private protocol, LoRa, or cellular gateways.
ESL connects with POS, Merchant Data Management (MDM), and pricing management systems to achieve price synchronization, promotion linkage, and price change auditing. IoT SIM cards provide connectivity for ESL gateways, centralized multi-store management, and remote updates, especially suitable for chain stores and new stores without wired networks.
Technical Features
ESL uses a master-slave architecture: gateways connect hundreds to thousands of price tags, which use wireless wake-up and batch refresh, allowing single price changes to be completed in minutes. Some ESLs support NFC scanning and inventory sensing. Combined with RFID and visual recognition, it can support unmanned retail and smart inventory management.
Use Cases
ESL is applied in supermarkets, convenience stores, pharmacies, 3C stores, and fresh food supermarkets. Typical scenarios include bulk price updates, promotion linkage, centralized management of multiple stores, inventory and price tag linkage, price change audit, dynamic pricing, etc. SimtoLink provides IoT SIM cards, dedicated APN, and smart retail solutions for ESL scenarios.
The Price-Change Air Interface at the Label Gateway
How the gateway SIM and the label bus divide the work
In an electronic shelf-label store, the IoT SIM is almost always in the store gateway, not in each e-ink label. Labels wake and refresh over short-range radio inside the store. The SIM is the segment from the gateway to the price platform: it pulls the price-change task down, then returns the label addresses that succeeded, failed, or did not answer. The SIM is the store's exit, not the identity of a tag. When one SIM goes offline, the whole run of shelves covered by that gateway is affected, not a single label that ran out of battery.
A price-change task is usually a batch of item codes, prices, promotion copy, and an effective time. The gateway collects the task, then refreshes the store in batches. On cellular you see the task package and the receipts. On the in-store radio you see the screens flip. Mixing the two into one "label online rate" makes a healthy SIM look like proof that every price has changed. If the gateway generates a promotion code on the spot, the link issued by the platform and the code on the screen still have to match. The SIM only carries the bytes. It does not rewrite item master data.
Conditions for being attached before the promotion window
The price window is known, the gateway location is fixed, and the in-store radio and the cellular link are assessed separately. In the minutes before a large promotion, the SIM should already be registered. It should not cold-start when the task arrives. Underground supermarkets, metal shelves, and refrigerated aisles block the gateway antenna. Place it in the ceiling or on an outside wall, and measure again with the shelves full. A new store with no fixed line can use the SIM as its only uplink, but the plan has to cover the task package plus failed retries. Do not buy data by the number of labels. The traffic is at the gateway, not at the label.
When many stores share one price platform, each gateway SIM must map to a store number and a shelf zone. A SIM swap, a store closure, or a gateway sent for repair has to update the ledger, or receipts are filed against a store that has already closed. If the platform accepts traffic only from a fixed address, a public SIM whose address changes cannot pull tasks. That calls for a fixed access method, not a diagnosis of broken label hardware.
Some labels still show yesterday's price
Treating "gateway online" as "the whole store has changed price" is the common miss. Where the in-store radio has a dead spot, the receipt lists labels that did not answer, and those screens still show yesterday's price. The customer and the checkout then disagree. If the system reports one overall status only when everything succeeds, a partial failure disappears. Another error is using the gateway's local clock as the effective time. Clock drift moves the price change early or late. The SIM stays online, but the time no longer matches the checkout.
Repeating a task with no version number paints a label that was already correct back to the old task. If a night batch and a daytime spot change share one unqueued path, the small task sits behind the large one, and the counter asks for a price change while the screen does not move. At acceptance, pick a few labels known to sit in dead spots and compare the receipt id, the screen, and the checkout price. Do not stop at the gateway's signal bars.
Label battery and screen state also have to come back to the platform. Otherwise the SIM stays online while the screen is frozen months in the past. An e-ink panel that fails to refresh can keep the old image. If the gateway records only "radio sent" and does not wait for the label to answer, the platform treats the price as effective. The answer should carry at least the label address, the task version, and success or failure. Low-battery labels should be replaced before promotion day, not discovered that morning on the failure list. With several gateways in one store, one label can be woken by two of them, and the platform receives two results. Split zones by label address, and name a primary gateway for the overlap. SIMs are billed per gateway. Overlapping refresh sends the same task on two SIMs, doubles the traffic, and can still disagree. A seasonal bulk package should go out after closing. During opening hours, only a small batch may cut in, and that task needs a higher version so the night package does not paint over it the next day.