Electronic Shelf Label Companies: How the Main Vendor Platforms Differ

Dec 26, 2025

Leave a message

Anna Xie
Anna Xie
Anna covers accounts in the Middle East and Eastern Europe and has been part of retail display projects across a pretty wide range of store formats. She writes from a buyer's perspective: total cost of ownership, common spec mismatches between what v

Comparing electronic shelf label companies is harder than comparing label sizes or display colors. The major suppliers do not all sell the same kind of system. Some position ESLs as one layer of a broader connected-store platform. Some are strongly centered on shelf-edge infrastructure and retail operations. Others emphasize cloud management, managed services, digital signage, or a wider intelligent-store stack.

That difference matters before a retailer creates a shortlist. Two vendors can both offer e-paper labels and still require different store infrastructure, software ownership, integration work, operating responsibilities, and support models. A useful company comparison therefore should not start with a "best brand" ranking. It should start with the architecture and operating model the retailer will actually have to own.

This guide maps six established ESL platform companies by their current public product direction and gives buyers a common set of questions to verify. It does not score a winner. For a deeper architecture comparison of Vusion, SOLUM, and Pricer, use the three-platform ESL manufacturer comparison. For a broader product-selection process, use the ESL solution selection guide.

Retail team comparing different electronic shelf label vendor platform architectures rather than ranking brands

 

First, decide what you mean by an "ESL company"

The phrase can describe several different roles in the electronic shelf label ecosystem. Treating all of them as interchangeable creates a misleading vendor list.

Company role What the buyer is actually evaluating Typical evidence to request
End-to-end ESL platform vendor Labels, store communications, management software, integrations, deployment and support as one operating system Architecture diagram, exact product/configuration, software scope, interface documentation, support boundary
Shelf-edge specialist ESL infrastructure and retail workflows closely tied to the shelf edge Store infrastructure design, management platform, workflow support, monitoring and lifecycle process
Broader digital-store platform provider ESL plus signage, sensing, store intelligence or additional connected-store functions Which modules are in scope, how components share data, integration ownership and licensing boundaries
Cloud-first ESL provider Central cloud management, APIs and device connectivity with reduced local software footprint Cloud architecture, gateway model, API/SDK documentation, tenant/security model and outage behavior
Managed-service provider The supplier takes a larger role in hosting, monitoring or operating the ESL estate Service boundary, monitoring scope, escalation model, data ownership, transition/exit plan
Display-component supplier The e-paper display technology inside a finished label rather than the complete retail ESL system Component technology documentation; the finished ESL vendor still owns system architecture and support

This distinction explains why an upstream e-paper company can appear in an "ESL market" report without being a direct substitute for a retail platform supplier. E Ink describes electronic shelf labels as an application of its display technology. The finished label, communications layer, management software, integration, mounting, deployment, and support still come from the ESL system vendor or its partners.

ESL ecosystem roles separating finished platform vendors, managed services and upstream display component suppliers

 

Use one comparison lens across every company

Brand-by-brand feature lists become difficult to compare because each vendor describes its platform differently. A better first pass uses the same six questions for everyone:

  1. Platform scope: Is the offer centered on ESLs, or does it extend into a broader connected-store stack?
  2. Store infrastructure: What communications equipment and local infrastructure are required, and who owns it?
  3. Management layer: What software manages devices, pricing workflows, templates, monitoring, and store operations?
  4. Integration boundary: Which interfaces are standard, which are project-specific, and who implements and supports them?
  5. Operating model: What work remains with retailer IT and store operations, and what can the supplier or service partner operate?
  6. Proof: Which claims can be supported by current product documentation, architecture, interface material, compliance evidence, and a representative pilot?

Those questions are more durable than a league table. Product families change, software evolves, and a retailer's own constraints often matter more than a generic brand ranking.

Six-dimension framework for comparing ESL companies by platform, infrastructure, management, integration, operations and proof

 

Company landscape at a glance

Company Current public platform emphasis Distinctive architecture question Buyer should verify
Vusion ESLs within a broader connected-store and IoT cloud platform How much of the proposed architecture depends on the wider Vusion platform and infrastructure? Exact device stack, cloud modules, store connectivity, interfaces, support and project scope
Pricer Shelf-edge ESL system plus the Pricer Plaza cloud retail-operations platform How will the proposed store infrastructure connect to Plaza, and which workflows are managed centrally? Infrastructure design, Plaza scope, integration responsibilities, monitoring and migration assumptions
SOLUM Newton ESL platform with a broader direction toward integrated shelf and in-store digital communication Which ESL, management and signage components are included in this specific project? Exact Newton configuration, management platform, integration scope, signage dependencies and pilot evidence
Hanshow Broad ESL families combined with IoT cloud and intelligent-store solutions Is the project an ESL deployment only, or part of a wider digital-store architecture? Exact label family, controller/network design, cloud modules, interfaces and operating responsibilities
Displaydata Enterprise ESL system with centralized management and an explicit managed-service option Which responsibilities stay with the retailer and which are operated by Displaydata? Hosting, monitoring, communicator design, service levels, escalation and transition/exit terms
ZKONG Cloud-oriented ESL platform with APIs, SDK options and Bluetooth-device management How does the cloud/gateway design fit the retailer's security, integration and support model? API/SDK documentation, gateway architecture, account/security model, integration ownership and support

The table describes current public platform positioning, not a quality ranking. A vendor's website can show what it offers, but a procurement decision still requires project-specific documentation for the exact configuration being proposed.

 

Vusion: ESLs as part of a broader connected-store platform

Vusion's current ESL materials place electronic labels inside a larger connected-store architecture rather than presenting them as isolated price tags. Its ESL technology page connects shelf labels with cloud management and wider store operations, while its IoT Cloud platform is positioned as a central device-management layer for connected store technology.

For a buyer, the important question is not whether the broader platform has many capabilities. It is which of those capabilities are actually part of the proposed ESL project. A retailer should ask for a diagram that identifies the labels, store communications layer, cloud services, APIs or connectors, identity and access model, and the operational tools that will be used after rollout.

That boundary becomes especially important when the project may later include capabilities beyond pricing. A broad platform can create a coherent roadmap, but it can also make commercial and technical scope harder to see if every module is discussed as though it were part of the base ESL deployment.

Evidence to request: the exact proposed label and communications architecture, named cloud modules, interface documentation for the retailer's systems, responsibility for configuration and monitoring, and the pilot evidence that will prove the required workflows.

 

Pricer: shelf-edge infrastructure managed through Pricer Plaza

Pricer combines its ESL product family with Pricer Plaza, which the company describes as a cloud platform for managing an ESL ecosystem, pricing, promotions, task automation, monitoring, and in-store operations. Pricer's current product portfolio also shows dedicated store infrastructure that connects the shelf-edge system to the management platform.

The buyer-side distinction is architectural. A retailer should understand what remains in each store, how that infrastructure connects to Plaza, and what happens when the cloud path or an in-store component is unavailable. The same review should identify whether the retailer is migrating an existing Pricer estate or building a new one, because migration assumptions can change the project boundary.

Do not reduce the comparison to update speed or battery claims. Those values depend on the exact label, infrastructure and operating conditions and should be validated at model level. For an enterprise comparison that goes deeper into Pricer, Vusion and SOLUM architecture, see the site's manufacturer architecture comparison.

Evidence to request: the store infrastructure design, Plaza modules and hosting scope, interface responsibilities, monitoring workflow, migration assumptions if applicable, and a representative store validation plan.

 

SOLUM: Newton ESLs within a wider in-store communication stack

SOLUM's current direction connects its Newton ESL family with a broader digital-store stack. In 2026 the company described integrations that connect ESLs, large-format e-paper and digital signage with core store systems, illustrating a platform direction that extends beyond shelf pricing alone.

That can matter for retailers planning both shelf-edge automation and in-aisle digital communication, but the project must still be decomposed into explicit components. "Integrated" should not be treated as proof that every device, workflow or connector is included in the base proposal.

Ask the supplier to show which Newton labels and store communication components are proposed, which management software controls them, how product and price data enter the platform, whether digital-signage functions are part of the same project, and which integrations require additional engineering.

Evidence to request: exact hardware/configuration, management-platform scope, interface documentation, any dependency between ESL and signage components, and a pilot that proves the retailer's real source-to-shelf workflow.

 

Hanshow: ESL families plus IoT cloud and intelligent-store modules

Hanshow's current electronic shelf label portfolio spans multiple label families and a controller layer, while its broader site positions ESLs alongside IoT cloud and intelligent-store solutions. That makes the company relevant to buyers who may be considering a wider store-digitalization architecture as well as a conventional ESL rollout.

The procurement risk is scope ambiguity. A broad product ecosystem can look like one integrated offer even when different modules, network components or services have separate commercial and technical boundaries. The buyer should identify which label family is proposed for each store environment and which cloud or intelligent-store functions are mandatory, optional or out of scope.

Claims about lifecycle, positioning, communication performance or store coverage should be tied to the exact proposed product and architecture rather than generalized across the company portfolio.

Evidence to request: model-level documentation, controller/network architecture, cloud-module list, API or interface material, ownership of deployment and support tasks, and proof for any location or intelligent-store capability included in the business case.

 

Displaydata: centralized ESL management with a managed-service path

Displaydata is useful to compare because its current public offer includes a clear managed-service model in addition to enterprise ESL technology. The company describes centralized management, remote monitoring, and an option for the supplier to take a larger operating role.

For retailers with limited internal resources, that operating model may be as important as the label hardware. It changes the questions procurement should ask. Who hosts the service? Who monitors store communications? Who responds to faults? What data and logs remain available to the retailer? What service levels apply? Can the retailer later take over hosting or operations, and what would that transition require?

A managed service should not be scored simply as "more support." It is a different responsibility allocation. The buyer needs an explicit service boundary so that the commercial comparison includes the work another vendor might leave with internal IT.

Evidence to request: service description, hosting and monitoring boundary, communications architecture, support hours and escalation process, data ownership, incident records available to the retailer, and transition/exit provisions.

 

ZKONG: a cloud-oriented ESL platform with API and SDK options

ZKONG's current ESL product page describes a cloud platform for Bluetooth-device management and explicitly references API, SDK and firmware integration options. That makes integration design a central part of evaluating the platform rather than a later implementation detail.

A retailer should confirm what "cloud" removes from the store and what still remains. Gateways, network access, credentials, device binding, local failure modes, security review and support ownership still need to be defined. API availability also does not prove that a complete ERP, POS or pricing workflow is already implemented.

The right comparison is therefore not "has an API: yes/no." It is whether the supplier can document the required business events, authentication, data objects, acknowledgements, retries, logging and responsibility boundaries for the retailer's exact integration.

Evidence to request: gateway and cloud architecture, API/SDK documentation, authentication/security model, supported integration responsibilities, failure and retry behavior, and the support process for custom integration work.

 

E Ink is an important ESL technology supplier, but it is not the same kind of vendor

E Ink is frequently mentioned in ESL industry discussions because e-paper is a core display technology used in many electronic shelf labels. That does not put E Ink in the same procurement category as Vusion, Pricer, SOLUM, Hanshow, Displaydata or ZKONG.

The distinction is practical. E Ink's ESL application material describes the display technology used for shelf labels and retail signage. A retailer buying an operational ESL system still needs a finished label design, communications architecture, management platform, integration, mounting, deployment process and support model from a system supplier.

This is one reason generic "top ESL companies" lists can be confusing: a display-component supplier, an end-to-end retail platform company and an integrator may all appear in the same market landscape while performing different jobs.

 

Bluetooth standardization is changing one layer of the market, not eliminating vendor differences

The Bluetooth SIG has adopted an Electronic Shelf Label Profile 1.0.1. The specification defines how a Bluetooth GATT client can control and update ESLs.

That standard matters because it creates a common technical profile for Bluetooth-based ESL communication. It does not prove that every commercial ESL platform implements the profile, that products from different suppliers are interchangeable, or that software, cloud, gateway, security and integration layers are standardized.

When interoperability is a procurement requirement, ask the supplier to state which Bluetooth ESL specifications the exact products implement, what has been qualified or tested, what remains proprietary, and which cross-vendor combinations are actually supported. Do not infer interoperability from the presence of Bluetooth alone.

 

What every ESL company should prove before it enters a serious shortlist

A company comparison becomes useful when marketing descriptions are converted into comparable evidence. Before scoring suppliers, ask each one to provide the same evidence package.

Evidence area What to request Why it matters
System architecture Current diagram showing labels, store communications, network boundary, cloud/on-premises components and management services Exposes infrastructure and ownership differences hidden by similar feature lists
Exact proposed products Model/configuration schedule by use case, plus current model-level documentation Prevents family-level claims from being applied to the wrong label or environment
Integration API/interface documentation, supported data flows, authentication, acknowledgement/error behavior and implementation responsibility Separates "API available" from a complete supported business workflow
Store validation Site-survey method or design assumptions for representative store layouts and environments Prevents one generic coverage or infrastructure claim from being applied to every store
Security Architecture, access model, patch/update process, relevant test or certification evidence for the proposed service Allows security review to evaluate the actual system rather than a generic "secure" statement
Lifecycle Warranty scope, replacement process, firmware/software support policy, end-of-life process and model-specific operating assumptions Shows what happens after initial deployment and when products change
Support Support hours, escalation path, service levels, monitoring responsibilities and exclusions Makes different retailer-versus-vendor operating models commercially comparable
Pilot acceptance Proposed test conditions, evidence capture, prerequisites, responsibilities and defect-closure method Turns broad capability claims into project-specific proof

If a supplier cannot provide an answer yet, mark it as an open item rather than filling the gap with an industry assumption. The purpose of the first company comparison is to identify which operating models deserve deeper evaluation, not to declare a winner before the architecture is understood.

ESL vendor evaluation flow from company landscape through architecture and evidence to a validated shortlist

 

Use the company landscape to build the right next comparison

After this first pass, the next page should depend on the decision you are making. If the shortlist centers on Vusion, SOLUM and Pricer and you need a deeper architecture review, use the enterprise manufacturer comparison. If you want a six-brand view organized around retail use cases, use the six-brand retail comparison.

If the company shortlist is not yet stable, step back and use the ESL solution selection guide to define requirements first. Buyers who need the site's commercial product context can review the electronic shelf label category and the broader electronic shelf label solution framework.

The useful outcome is not a universal "top company." It is a shortlist in which each vendor is being judged against the same project boundary, with enough evidence to understand what the retailer will own, what the supplier will provide, and what must still be proven before rollout.

Send Inquiry