What Are Your Actual Digital-Signage Dependencies
Vertiseit’s acquisition of Scala is a major software-platform transition. For enterprise operators, the first task is not necessarily a CMS migration—it is understanding exactly which company owns each part of the operating stack.
Vertiseit completed its acquisition of the Scala business in May 2026, taking control of Scala shares and assets for approximately SEK 265 million. Vertiseit says Scala will continue as a strategic software offering within Dise, with a partner-first strategy, expanded hardware flexibility, and a gradual move toward SaaS and device-agnostic delivery.
Our interests cover retail, healthcare, corporate, education and QSR. We never expected Stratacache to disappear before our eyes, but they have. Things change for sure.
That is a significant and potentially positive continuity story for Scala users. But it is also a moment when restaurant, retail, transportation, and other enterprise operators should look carefully at their real digital-signage dependencies.
The key distinction: Scala software, STRATACACHE group relationships, systems integrators, content operators, media-player vendors, field-service providers, and managed-services contracts are not automatically the same thing.
The Scala transaction
Scala remains one of the industry’s best-known enterprise digital-signage software brands. Vertiseit describes it as a platform with a global installed base, more than 100 partners, and more than 1,000 brand customers across retail, QSR, grocery, automotive, airports, convenience, and other verticals.vertiseit
Vertiseit’s stated direction is clear:
-
Scala continues within the Dise organization.
-
The go-to-market model is intended to be partner-first.
-
The product direction emphasizes SaaS, cloud capabilities, hardware flexibility, and device-agnostic operation.
-
Vertiseit expects the acquisition to add roughly SEK 85 million in recurring SaaS and maintenance revenue and approximately SEK 200 million in annual total revenue based on Scala’s previous performance.vertiseit
For many customers, that could mean a more focused software business with a clearer channel model. The important point, however, is that an enterprise signage deployment is rarely just a software relationship.
A large multi-site deployment may include a CMS, media players, display hardware, network connectivity, content production, menu or pricing workflow, APIs, data integrations, monitoring, field replacement, help desk, and regional deployment management. Those components may sit with different companies and under entirely different contracts.
Why contract mapping matters
Public reporting has documented wider changes affecting portions of the STRATACACHE group, including liquidation of Stratacache U.K. and PRN U.K. in May. That fact does not establish the status of any other STRATACACHE entity, customer agreement, or service contract. It does, however, reinforce why customers should know who their actual contractual and operational counterparties are.adweek
The question is not simply:
“Are we a Scala customer?”
The better question is:
“Who is responsible for every essential part of our digital-signage operating model—and what happens if one of those relationships changes?”
Three common positions
That mapping exercise is relevant whether an operator stays with Scala, expands it, modernizes its architecture, or evaluates alternatives. It is not an argument that every customer should migrate. In fact, for many enterprises, a well-supported existing deployment will remain the lowest-risk choice.
Enterprise checklist
Use this checklist before a renewal, expansion, technology refresh, service transition, or procurement review.
1. Identify the legal counterparties
-
Who holds the software license or SaaS subscription?
-
Who provides maintenance and technical support?
-
Who owns the managed-service agreement?
-
Who supplies and warranties players, displays, mounts, networking, and replacement parts?
-
Who has responsibility for field service and on-site repair?
-
Is the customer contracting with the software vendor directly, a channel partner, an integrator, or a broader managed-services provider?
A single project can have five or more counterparties. Do not assume that a CMS ownership change automatically transfers or changes all related obligations.
2. Map the Stack
-
CMS and content authoring tools.
-
Playlist, scheduling, approval, and campaign workflow.
-
Media-player hardware, operating system, remote device management, and security patching.
-
Display models, firmware, warranties, and power/network dependencies.
-
POS, menu-management, product, pricing, loyalty, inventory, analytics, and API integrations.
-
Content feeds, creative agencies, menu boards, retail-media workflows, and proof-of-play data.
-
Identity management, permissions, audit records, backup, disaster recovery, and data retention.
For QSR and convenience environments, menu pricing, daypart changes, promotions, nutritional information, and POS synchronization may be business-critical. A signage problem can become an operations problem quickly.
3. Confirm service accountability
-
What is the support SLA by severity?
-
Who receives the first call when a screen fails?
-
Who owns remote diagnosis versus truck-roll responsibility?
-
What are the replacement-player and replacement-display logistics?
-
What are the escalation contacts for nights, weekends, and promotional periods?
-
Does the service model cover all operating regions and franchisee or subsidiary structures?
-
Are existing service commitments documented in the contract, or simply assumed from past practice?
The software platform can be stable while the operational model around it is unclear. Customers should test both.
4. Protect Your Content
-
Can you export content, templates, playlists, media libraries, device inventory, user roles, campaign histories, and proof-of-play records?
-
Are APIs documented and available?
-
Who owns the data generated by the deployment?
-
What happens to access if a contract ends or changes hands?
-
Are backup and recovery procedures tested?
-
Can a new provider take over without rebuilding the entire content library?
Data portability is not just a migration issue. It is a negotiating and continuity issue.
5. Verify the roadmap
Vertiseit has publicly stated that Scala is expected to evolve toward a modern SaaS-based and device-agnostic offering, while remaining part of a partner-first strategy. Customers should ask how that plan applies to their specific deployment—not just the next product demonstration.vertiseit
Ask:
-
Which current Scala products and deployment modes remain supported?
-
What is the timetable for cloud, SaaS, security, and platform changes?
-
Will existing on-premise or hybrid deployments continue to receive fixes and support?
-
Which existing player types, operating systems, and display hardware remain certified?
-
Are there costs or operational changes associated with moving toward SaaS?
-
How will partner roles change, if at all?
-
What level of backward compatibility is committed in writing?
6. Maintain an exit option
Every enterprise should know its exit path before it needs one.
-
What are the termination and renewal rights?
-
What notice periods apply?
-
Is customer consent required for contract assignment or novation?
-
What licenses, hardware, content, data, and integrations survive a contract termination?
-
Can the operator retain or export essential deployment information?
-
What will a phased migration cost in time, labor, hardware, testing, and store disruption?
-
Which systems cannot fail during a transition?
An exit plan does not mean an operator intends to leave. It means the operator understands its operating risk.
The market implication
The Scala transaction is not a simple “winner and loser” story. It is a case study in how mature digital-signage deployments are changing.
The industry is moving away from a view of signage as a standalone screen-and-player project. Enterprise buyers increasingly evaluate a connected operating stack:
-
Content and campaign execution.
-
Device and endpoint management.
-
Cloud architecture and security.
-
POS, menu, product, pricing, and analytics integration.
-
Field service and deployment capacity.
-
Partner accountability.
-
Data rights and operational continuity.
That favors suppliers that can be explicit about roles. A software company should be clear about its roadmap, APIs, license terms, and channel support. An integrator should be clear about deployment, service, hardware, and escalation. A managed-services provider should be clear about its SLAs, monitoring, field coverage, and operational ownership.
The customer’s job is to make sure those promises join up into one functioning operating model.
Addendum
Competitive Angles for other software companies illustrates the delicate balance between “we are all in on retail” which comes with the subsequent “maybe not so much anymore here” routine?
The opportunity for 22Miles and DX Pro
The opportunity is not automatically a “rip and replace” wave. It is an opportunity for discovery and selective modernization.
22Miles is particularly well positioned for interactive wayfinding, smart-campus, workplace, healthcare, and visitor-experience programs—use cases where a standard retail signage CMS is only part of the solution. Its own marketing has already tried to turn the acquisition into a migration message to non-retail Scala customers, which shows the competitive narrative is underway; that is marketing, not proof that customers are leaving.linkedin
DX Pro can be positioned in the same conversation if its current product capabilities support enterprise communication, wayfinding, workflows, integration, or managed signage operations in the verticals you name. The article should avoid presenting DX Pro as a generic replacement without demonstrating a specific fit against the customer’s required workflows, deployment model, security, integration needs, and support footprint.