VusionGroup vs SOLUM vs Pricer: How to Compare Enterprise ESL Platforms

Mar 06, 2026

Leave a message

Leo Chen
Leo Chen
Leo joined Legoyo's hardware team in 2018 and has been involved in bar LCD and ESL development since then, including certification work for CE, FCC, and several other markets. He writes about the technical side of display systems — mounting specs, en

Retail procurement team comparing three ESL platform architectures and pilot evidence requirements

If VusionGroup, SOLUM, and Pricer are already on your electronic shelf label shortlist, the useful question is no longer "Which company is biggest?" It is whether each platform fits your store network, retail data model, operating controls, and support requirements. Public specifications can establish important architectural differences, but they cannot determine a winner for a specific retailer without a controlled pilot and contract-level evidence.

This guide therefore compares the three vendors as enterprise ESL platforms rather than ranking them. If you are still building a long list, start with the broader ESL company comparison. If you are already deciding between VusionGroup, SOLUM, and Pricer, use the framework below to turn public information into testable procurement questions.

 

Start with architecture, not company size

Three vendors can all deliver digital shelf labels while using materially different paths between retailer data, store infrastructure, and the shelf edge. Those differences affect site surveys, integration work, network ownership, monitoring, change control, and the evidence you should request before rollout.

Vendor Current public architecture signal What a buyer should verify
VusionGroup VusionOX is built around Bluetooth Low Energy and connects into VusionCloud. Which access-point integrations, device families, software modules, and migration paths are included in the proposed scope.
SOLUM Aims SaaS connects retailer data to the SOLUM environment and operates through the Newton Gateway; SOLUM documents HTTPS and MQTT in that workflow. Exact integration method, gateway design, supported label families, monitoring, and recovery behavior for the quoted configuration.
Pricer Pricer uses near-infrared optical wireless communication and manages the ESL estate through Pricer Plaza. StoreLink placement, optical coverage validation, Plaza integration, monitoring, and the operational workflow around failed or delayed changes.

These are not interchangeable descriptions of the same radio system. They are the first reason a shortlist should be evaluated at platform level rather than by label dimensions alone.

Three ESL platform paths showing VusionOX BLE, Aims with Newton Gateway, and Pricer Plaza optical architecture

 

VusionGroup: validate the BLE ecosystem you are actually buying

VusionGroup describes VusionOX as a Bluetooth LE-based foundation that connects devices and networking infrastructure to VusionCloud. Its current ESL portfolio also presents BLE as a core element of newer connected shelf-edge products.

For procurement, the important detail is not simply "supports Bluetooth." A retailer should ask which access-point integrations are supported in the proposed country and software version, whether dedicated infrastructure is still required in any store areas, how device onboarding works, and which management functions belong to the base platform versus additional modules. The answer should refer to the exact proposal, not to an ecosystem diagram from a general product page.

Bluetooth also has an industry standard specifically for ESL control and updates. The Bluetooth ESL Profile is useful context when evaluating standards-based designs. It does not, by itself, prove that every device or platform feature from a particular vendor is interoperable with every other vendor. Qualification, supported profiles, system software, and commercial integration boundaries still need to be checked.

 

SOLUM: treat Aims, the Newton Gateway, and the integration boundary as one system

SOLUM's current Aims SaaS documentation shows retailer data flowing into Aims and ESL operations running through the Newton Gateway. The same page describes HTTPS and MQTT as part of its secure communications and presents Aims as the management layer for dashboard, layout, user, and third-party integration functions.

That makes the gateway-to-platform boundary a procurement checkpoint. Ask SOLUM to identify the source systems that will feed Aims, the method used for each interface, how product-to-label binding is represented, how failed updates are exposed, and what evidence is retained after a change. If a retailer has store-specific prices, multiple product masters, or variable-weight items, those data conditions should be included in the integration test rather than assumed to be normal.

A public software page can confirm that a capability exists in the platform family. It cannot establish that a particular connector, service level, gateway topology, or support process is included in your contract. Those items belong in the statement of work and pilot acceptance plan.

 

Pricer: optical wireless is not the same design problem as RF coverage

Pricer's optical wireless network uses a near-infrared band rather than conventional radio. A useful correction to older ESL comparisons is that Pricer explicitly states that its optical system does not require line of sight. A procurement team should therefore avoid treating "infrared" as shorthand for a simple point-to-point remote-control link.

The practical design question is how Pricer's optical access-point infrastructure will be validated in the real store. Ceiling geometry, fixtures, store changes, and any unusual areas still need to be represented in the site survey. The test should show that target labels receive changes and that the platform can identify exceptions; it should not rely on a generic claim that optical or radio is automatically better for a particular store format.

Pricer's current Pricer Plaza page positions the cloud platform as the management layer for ESLs, stores, infrastructure, SKUs, pricing, promotions, and store tasks. For a buyer, the useful follow-up is to verify which Plaza functions are part of the proposed subscription and how they integrate with the retailer's systems.

 

Do not turn public specifications into a "best vendor" table

Public pages are useful for architecture discovery, but several high-impact purchasing variables are conditional. Battery life depends on device, display, update pattern, temperature, radio behavior, LED use, and other operating assumptions. Coverage depends on the store and the proposed infrastructure. Integration effort depends on the retailer's source systems and data quality. Support quality depends on region, contract, partners, and escalation terms.

For those reasons, a serious comparison should avoid universal claims such as "Vendor A is best for metal shelving," "Vendor B always costs less," or "Vendor C lasts twice as long." Replace those statements with evidence requests tied to the proposed deployment.

 

Use the same five procurement tests for all three vendors

1. Trace one price change end to end

Select a controlled SKU and store. Record the authoritative source value, effective time, product-to-label binding, rendered content, delivery event, endpoint status, and exception record. The vendor should be able to show where each stage is visible and who owns a failure. This is more useful than comparing dashboard screenshots.

2. Validate the store network under representative conditions

Test the actual infrastructure design in representative aisles, refrigerated areas, endcaps, dense fixtures, and any locations where the mounting or building geometry differs from the main sales floor. The acceptance evidence should use the vendor's proposed access points, gateways, or optical infrastructure rather than a temporary lab setup. For a deeper look at protocol trade-offs, see the site's ESL wireless protocol comparison, but do not transfer generic protocol conclusions directly to a vendor-specific design.

3. Force a recoverable failure

A successful demo proves the happy path. A useful pilot also creates a controlled exception: an unreachable label, a temporarily unavailable network segment, an intentionally incorrect binding, or another safe test condition agreed with the vendor. The team should observe how the platform reports the condition, whether retries are distinguishable from success, and what action is required to close the exception.

4. Separate device lifecycle from marketing lifetime

Request the assumptions behind battery and service-life statements for the exact label models being quoted. Then ask how battery status, replacements, damaged labels, spares, firmware, obsolete models, and migration are managed over the contract term. The acceptance criterion is not a universal number; it is a documented lifecycle model whose assumptions match your intended use.

5. Review change control and support before scale

Document who can change templates, integrations, store settings, firmware, user permissions, and rollout schedules. Confirm how updates are tested before production, how incidents are escalated, what logs or reports are retained, and which responsibilities remain with the retailer or systems integrator. A platform that works technically can still create operational risk if ownership is unclear.

Enterprise ESL pilot testing source data, product mapping, store communications and shelf outcome

 

A pilot scorecard should measure evidence, not impressions

Decision area Evidence to collect Pass condition to define before the test
Data integration Source record, interface event, mapped SKU and label The approved source value reaches the intended label without duplicate manual entry.
Store communications Representative site test and exception log The proposed infrastructure covers the agreed test locations and exposes failures.
Display outcome Visual shelf check plus platform status The correct content appears on the correct physical label and the system records the resulting state.
Recovery Controlled failure and recovery record The team can detect, diagnose, retry or escalate the exception through a documented process.
Operations User roles, audit trail, support and change-control records Ownership is explicit for normal changes, incidents, and platform administration.
Lifecycle Model-specific assumptions, spares and replacement process The lifecycle plan matches the proposed hardware, environment and service terms.

Do not copy generic thresholds from another retailer. Set acceptance criteria before the pilot using your store risk, pricing process, service model, and proposed architecture. That keeps the test from becoming a post-hoc justification for whichever demo looked most polished.

ESL vendor pilot evidence framework covering data, communications, display, recovery, operations and lifecycle

 

When this three-vendor comparison is the wrong starting point

If your organization has not yet established requirements, store constraints, integration ownership, or a realistic pilot scope, vendor-by-vendor comparison is premature. Start with the ESL solution framework and define the operating problem first. Buyers evaluating available hardware can also review the electronic shelf label category without assuming that one public product page represents an entire enterprise platform.

If VusionGroup, SOLUM, and Pricer are already the final shortlist, however, the decision can be made more disciplined: compare the exact architecture you will deploy, require the same evidence from all three, and make the pilot prove data correctness, store communications, exception handling, and operational ownership. That is a more defensible basis for procurement than market-share claims, company histories, or a universal "best vendor" label.

Send Inquiry