Scala Is Separate Now

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.

The publicly established sequence is simply:

• STRATACACHE acquired control of Scala in August 2016.

• STRATACACHE completed full ownership in February 2018.

• Scala remained in the group for roughly a decade from initial control, or a little over eight years from full ownership.

• Vertiseit agreed to acquire Scala on May 20, 2026 and completed the purchase June 1, 2026.

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.

Good read on DX Pro

Not a fan of 22Miles? Then look at AcquireDigital and Nanonation!

Addendum – What Happened With Stratacache

This is a personal take look at Stratacache. At one point I was pursuing them and trying to get my foot in the door.  Several companies I have worked with were approached to be purchased. SC seemed moving toward titan stage.

I believe my thesis is plausible in its overall direction, and recent industry reporting now supports several of its most important observations: STRATACACHE was acquisition-led, expanded aggressively beyond QSR, made a substantial U.S. manufacturing bet, suffered a real 2026 retrenchment, and has begun selling assets—including Scala. But the strongest version of the argument is that this was an interlocking strategic, operational, and financing problem, not yet a provable “the banks pulled the plug” story. Dayton

Personal perspective on STRATACACHE

None of this is especially surprising. STRATACACHE appeared interested in acquiring a wide range of adjacent companies; Acrelec was reportedly among the targets, and the broader pattern suggested an acquisition-led effort to assemble scale across digital signage, QSR technology, retail technology, software, and hardware.

What follows is my personal interpretation, not a statement of verified fact. I do not have access to STRATACACHE’s internal financials, lender discussions, acquisition terms, or board-level decisions.

A shift away from QSR

Element of our theory	Match with public evidence	Plausibility
STRATACACHE pursued an aggressive acquisition strategy	Strongly supported. The company says it evaluated more than 400 deals annually and completed 14 acquisitions over 18 years; Scala, Walkbase, PRN, RDM, X2O, and other assets reflect that strategy.	High
STRATACACHE shifted toward retail and broader in-store experience	Supported. Its own market positioning includes retail, grocery, finance, retail media, analytics, displays, and shopper engagement alongside QSR.	High
QSR became less secure, especially McDonald’s	Supported in the important sense that McDonald’s named Coates its single global DMB CMS provider in 2022; Coates was also one of two approved hardware providers. That is a material strategic displacement of STRATACACHE’s U.S. incumbent role.	High
Retail diversification did not offset QSR weakness	Reasonable, but not publicly quantifiable. The logic is sound; there is no public segment revenue disclosure sufficient to prove retail underperformed QSR or to validate a 15% figure.	Medium-high
Large fixed-cost manufacturing/real-estate investments hurt the business	Strongly plausible. The Oregon MicroLED project, Dayton/Trotwood industrial investment, and capital intensity of display manufacturing are well documented.	High
Display reliability/service economics created customer friction	Plausible but weakly documented in public sources. Treat Taco Bell burnout/filter claims as market intelligence or anecdotal evidence unless supported by contracts, service bulletins, failure-rate data, or customer testimony.	Medium
Layoffs were a response to serious financial distress	Supported. STRATACACHE confirmed layoffs; multiple industry reports subsequently described liquidation of subsidiaries and asset sales.	High
Lenders/investors withdrew support or forced restructuring	A credible inference, but unproven. Public reporting shows distress and monetization, not the internal lender covenants, debt stack, or bank decisions required to state this as fact.	Medium-high as a hypothesis

My view is that STRATACACHE gradually shifted attention away from its original QSR strength and toward broader retail. By then, it had already secured major restaurant brands, notably McDonald’s and Restaurant Brands International, while also acquiring Scala after Scala had won the Taco Bell digital-signage opportunity.

The strategic logic was understandable: once a company has won many of the largest QSR opportunities, retail represents a much larger potential addressable market. The shift was visible externally as well. At industry trade shows, STRATACACHE’s presence appeared to feature progressively less restaurant-specific content and more retail-oriented messaging, merchandising, and in-store experience technology.

However, retail is fundamentally harder to standardize than QSR. A restaurant chain can often deploy a repeatable product model across stores: menu boards, drive-thru, order status, promotional display, kitchen communications, and related workflows. Once a supplier has built a credible solution for one large chain, much of that architecture can be adapted for another.

Retail is different. Two retailers may both use displays, but their requirements can be radically unlike one another: product categories, store formats, promotional calendars, merchandising rules, inventory integrations, customer journeys, screen placement, content ownership, and store labor models vary enormously. The “common denominator” is much smaller.

Acrelec’s experience is illustrative. Despite a significant QSR footprint, what it described as diversification beyond its core restaurant business remained a comparatively limited share of global revenue—roughly 15 percent by this account. That suggests how difficult it is to convert an established QSR technology position into a scalable retail platform.

Execution and customer experience

My impression is that the strategic shift may also have affected execution in the core QSR business. There were reports and customer complaints around the speed of campaign setup, with some customers allegedly facing four- to six-week turnaround times for new marketing campaigns. In an environment where QSR operators increasingly expect quick promotions, daypart changes, price updates, limited-time offers, and localized content, that kind of lead time is a competitive weakness.

There were also visible competitive changes in the market. McDonald’s decision to move to Coates as its single global DMB CMS provider was a major strategic loss of position for STRATACACHE, even if the precise U.S. migration timetable and residual STRATACACHE footprint are not publicly disclosed. I would not attribute that transition to any one issue—large enterprise technology transitions almost never have a single cause—but it is consistent with a broader picture of pressure on STRATACACHE’s historical QSR position.

The concern is not simply that a customer is lost. It is that the QSR base historically provided the recurring revenue, brand credibility, deployment scale, and customer reference base needed to support ambitious expansion into other verticals. If that base begins to weaken while retail growth is slower than anticipated, the economics become much more difficult.

STRATACACHE still publicly marketed a major QSR position in early 2026, claiming digital menu board work for eight of the top 10 QSR brands in the United States and more than 650,000 digital menu boards globally. That is company marketing rather than independently audited revenue data, but it shows QSR remained a key claimed vertical rather than a business it had abandoned entirely.

Acquisition-led expansion

STRATACACHE did not grow organically in a narrow software-only way. It built a group through acquisitions across signage software, retail media, analytics, display hardware, integration, and service. Its own company page states that it has made 14 acquisitions over 18 years and reviews more than 400 possible deals a year. stratacache

The Scala transaction is central to the argument. STRATACACHE acquired super-majority control of Scala in 2016, but the original transaction terms were not publicly disclosed. Therefore, “roughly $100 million” should be presented as an industry estimate rather than a confirmed price. Contemporary coverage said no deal terms were released and suggested Scala’s annual revenue had been around $25 million, making a large acquisition price possible but not demonstrable from public evidence. qsrmagazine+2

The more revealing data point is the exit: Vertiseit announced in May 2026 that it was acquiring Scala from STRATACACHE for about SEK 265 million—approximately €24 million—through shares and assets. invidis+2

That does not establish a loss on Scala, because the original price, intervening cash flow, investments, asset mix, and deal structure are unknown. But selling one of the group’s most recognizable software assets during a broader period of retrenchment is consistent with a need to simplify, raise liquidity, or reduce financial pressure.

Acquisition, leverage, and manufacturing

The more important issue, in my view, may have been the financial model behind the expansion.

STRATACACHE acquired a substantial number of companies. Scala alone was reportedly acquired for approximately $100 million in 2016, although the precise transaction value and financing structure are not public. An acquisition program of that scale commonly depends on some mixture of debt, lender confidence, projected synergies, growth assumptions, and future cash flow.

The highest-risk strategic decision may have been the decision to manufacture displays in the United States. STRATACACHE made a major commitment to domestic display manufacturing, including the acquisition of a display-manufacturing operation in Oregon. The company argued publicly that Asian manufacturing regions—including Korea, Taiwan, and China—benefited from government support that U.S. manufacturers did not receive.

That does not mean the U.S.-manufacturing thesis was irrational. It may have offered supply-chain control, differentiation, domestic-production credibility, intellectual-property value, and a potential long-term MicroLED upside. But those advantages take time and volume to realize, while fixed costs, financing costs, labor, yield problems, warranty exposure, and working-capital needs arrive immediately.

That argument may have had merit. But it does not eliminate the underlying commercial challenge: display manufacturing is capital-intensive, extremely competitive, operationally unforgiving, and dominated by global suppliers with enormous scale. Meanwhile, many STRATACACHE customers were already standardized on Samsung and LG displays, brands with established supply chains, pricing, warranties, service networks, and product confidence.

For a vertically integrated display strategy to work, STRATACACHE would have needed to achieve enough unit volume to support the manufacturing operation while also convincing customers that its own display products were equal or superior on reliability, price, lifecycle management, field service, and total cost of ownership.

Unverified industry anecdote — There were also field-reliability concerns associated with some deployments. Taco Bell’s rollout is often cited as an example: STRATACACHE displays reportedly experienced early failures or overheating/burnout issues, and the proposed maintenance model—including periodic filter replacement or service visits—was difficult for the customer to accept. Whether every detail of that account is correct or not, the broader lesson is clear: digital menu boards are not simply screens. They are a deployed infrastructure product, and restaurant operators have little tolerance for a maintenance requirement that adds recurring truck rolls, store disruption, and unbudgeted cost.

Industry feedback I have heard suggested that some customers experienced campaign-activation lead times that were incompatible with fast promotional cadence. I have not independently verified the duration across accounts.

There is public confirmation that Taco Bell used STRATACACHE-related technology in its digital-menu-board environment, including a Taco Bell digital-menu-board portal identified as powered by ActiVia Networks, a STRATACACHE company. STRATACACHE also describes its own ability to manage hardware failures, screen repairs, proactive monitoring, and on-site service.

My theory

My personal theory is that the restructuring was not caused solely by retail underperformance or by loss of QSR business. Those problems alone may not have been sufficient to explain the scale of the financial pressure.

The sequence of layoffs, subsidiary liquidations, asset sales, and real-estate monetization is consistent with severe liquidity or financing pressure. Public reporting does not establish whether lenders, investors, or a specific debt event directly forced the restructuring.

Instead, I suspect the more decisive factor was lender or investor confidence.

If STRATACACHE financed an aggressive acquisition program through debt while simultaneously funding a capital-intensive domestic display-manufacturing strategy, the organization would have needed strong, predictable cash flow and a convincing growth trajectory. A slowdown in QSR momentum, weaker-than-expected retail diversification, customer friction over campaign turnaround times, display reliability or service costs, and the burden of integrating many acquisitions could collectively undermine that case.

My view is that, at some point, its financial backers may have concluded that the projected returns and repayment capacity no longer justified continued support. In that scenario, the layoffs—reportedly including roughly 200 roles in the retail division—would be a symptom of a broader financing and restructuring problem rather than the primary event.

That is only a theory. But it is the explanation that best fits the pattern: an ambitious consolidation strategy, a difficult expansion from QSR into retail, heavy vertical-integration bets, substantial fixed costs, and an apparent loss of confidence from the capital providers behind the company.

Final Conclusion

STRATACACHE’s difficulties appear most plausibly to reflect a collision of strategic ambition and capital intensity. The company expanded through acquisitions, sought to broaden from repeatable QSR deployments into the more fragmented retail market, and simultaneously pursued vertical integration through U.S. display and MicroLED manufacturing. That strategy required dependable cash flow, high execution quality, and sustained customer confidence in its legacy QSR business.

The public record supports the view that those conditions weakened: McDonald’s moved its global DMB CMS role to Coates; STRATACACHE announced layoffs; its UK entities entered liquidation; Scala was sold; and major real-estate assets were monetized. None of this proves a lender-led failure. But it makes a liquidity, leverage, or capital-provider-confidence problem substantially more plausible than a simple explanation based only on a weak retail division or a single lost customer.
daytondailynews+4

STRATACACHE’s retrenchment looks like the end result of an acquisition-heavy, capital-intensive expansion model encountering QSR competitive pressure, the difficulty of scaling retail, and weakening access to—or confidence in—the capital required to carry that model forward.

Practical conclusion

STRATACACHE appears to be dismantling much of the diversified portfolio it assembled over the past two decades, while retaining an uncertain smaller core. It is not yet publicly proven that the entire parent company is shutting down.

For customers, suppliers, channel partners, or competitors, the appropriate operating assumption is:

• Do not assume continuity solely because STRATACACHE’s website or some U.S. operations remain active.

• Treat the company as being in an active restructuring/divestiture process.

• Request written confirmation of contract ownership, service levels, escalation contacts, software-support commitments, warranty responsibility, spare-parts availability, data-hosting arrangements, and source-code/transition rights.

• For large deployments, obtain an exit plan: export rights for content and configuration data, a replacement CMS path, documented player/display inventory, and a funded maintenance or contingency arrangement.

The key difference is between “shutting down” and “shrinking to a much smaller core.” The evidence strongly supports the second. The first remains possible, but it has not yet been publicly confirmed.

The sale of Scala and PRN is especially telling because these were not minor subsidiaries:

• Scala was STRATACACHE’s internationally recognized enterprise digital-signage CMS platform.

• PRN was one of North America’s more recognizable in-store retail-media businesses.

• STRATACACHE UK and PRN UK were put into a process intended to sell assets and pay creditors.

• August 31 — Stratacache has sold its PRN division to an Israeli company, Perion Network. https://finance.yahoo.com/media-advertising/articles/dayton-based-stratacache-sells-store-183100612.html

• Reports say Real Digital Media and X2O were also shut down.

Post Notes

• Markets — The real unit growth of the global QSR brands is now happening in Europe — CEE in particular — M4B
• One final perspective: whatever the strategic missteps may have been, Chris made a genuinely ambitious bet with his own capital—without private-equity backing or a corporate parent to absorb the risk. That distinction deserves recognition. Many observers can critique the outcome from the sidelines, but far fewer have personally assumed that level of financial and professional risk.
• The strongest version of this story is not a takedown. It is an analysis of a bold, independent wager that ultimately did not pay off as intended—one that still offers useful lessons about ambition, execution, timing, and the realities of building something substantial.