Blog posts
Every retailer evaluating in-store retail media eventually arrives at the same fork in the road. You have decided the business case is sound. You understand that your store traffic is an audience, your screens are inventory, and your first-party data is an asset that advertisers will pay to reach. The strategic question is settled.
The operational question is not. And it is the one that actually determines your timeline, your investment, and your competitive position: do you build on what you have, or do you rebuild from the ground up?
There is no universal right answer. But there is a clear framework for finding yours.
Most retailers approaching in-store retail media for the first time already have digital signage infrastructure in place. Screens are running. Content is being managed. The CMS is doing its job. The instinct is to treat retail media as an add-on — a new revenue stream layered on top of existing operations.
That instinct is partly right. But it underestimates how different the requirements are. A traditional digital signage CMS was built to answer one question: what content plays on which screen at what time? Retail media requires answers to an entirely different set of questions — who is the audience at this screen right now, which advertiser has bid for that audience, what campaign should be served, and what did it drive at the till?
These are not features you can add to a signage CMS. They are the outputs of a fundamentally different architecture — one built around audience data, campaign management, media sales, and closed-loop measurement. The question is not whether you need that architecture. You do. The question is how you get it.
The strongest argument for a purpose-built Retail Media CMS is not about any single feature. It is about what becomes possible when every capability in the platform shares the same data and works as part of the same loop.
Consider what a traditional digital signage CMS does — and does not do. It publishes content manually. It selects screens manually. It uses no audience data. It has no media sales capability. Its creatives are uploaded one by one. Its reporting is a play log. That is a content publishing tool. It has no concept of a media business at all.
Now consider what changes when the CMS is built for retail media from the ground up. Content automation means sponsored product ads are generated dynamically from SKU data — pricing, availability, imagery — without manual production for every campaign. That automated content feeds directly into audience-based campaign distribution. The media sales team books a campaign, the platform builds the creative, delivers it to the right screens, and closes the loop with sales uplift reporting. All of it connected, in a single system, with no data moving between platforms.
That tight integration between content automation, audience targeting, and media sales is the real case for the full solution. It is not just cleaner operationally — it is the difference between a retail media business that scales and one that hits a ceiling every time headcount does not grow with volume.
The trade-off is commitment. Replacing a working CMS takes time, requires migration, and disrupts operations while it happens. For retailers whose existing screen infrastructure is relatively new and performing well, that cost needs to be weighed carefully. But for those deploying a new network, or whose current CMS is aging, the integrated path is the right long-term foundation.
"The store should be the starting point — not an afterthought added to an e-commerce toolset. Strategies built for online retail media don't translate to the physical environment."
— Doohlabs, "Store in the Core" retail media strategy
For the majority of retailers with functioning screen infrastructure, the faster and lower-risk path is to leave the CMS in place and add the retail media capability on top. This is not a compromise solution. It is a deliberate architectural separation between two problems that are genuinely distinct — content management and media monetisation — and solving each one on its own terms.
The Retail Media Toolset provides everything a retailer needs to run a media business on their screens: audience creation from first-party data, a self-service portal for brands and trade partners, campaign booking and management, automated campaign delivery to existing screens, and performance reporting including sales uplift. None of it requires changing what the CMS does or how it operates.
The practical benefits are significant. Deployment is measured in months rather than years. The existing investment in screen infrastructure continues to generate returns. Operations teams are not disrupted. And retail media revenue generation can begin while the rest of the business runs as normal.
There is also a strategic argument for starting here even if a full platform migration is on the long-term roadmap. Running the Retail Media Toolset on top of an existing CMS builds the operational muscle — media sales workflows, advertiser relationships, audience data pipelines — before committing to a full infrastructure change. By the time a migration makes sense, the retail media business is already running and the case for integration is proven.
The one area where the overlay approach requires attention is data connectivity. The Retail Media Toolset needs to ingest audience data from POS and loyalty systems, and it needs to deliver campaign instructions to existing screens. This is an integration question, not an architecture problem — but it is worth assessing early to understand what your current environment requires.
The choice between the two paths comes down to a handful of honest answers about your current situation.
Most retail media technology is built for one starting point. Platforms that grew from e-commerce ad serving tend to have limited in-store CMS capability. Traditional digital signage vendors have deep screen management expertise but lack native media monetisation tools. Choosing one usually means accepting a gap somewhere.
The architecture behind Doohlabs In-Store IMPACT was designed specifically to avoid that trade-off. The platform consists of two components — a Retail Media CMS and a Retail Media Toolset — that can be deployed together as a fully integrated solution, or where the Toolset can be used independently alongside any existing CMS.
This shared foundation is what makes the upgrade path viable. A retailer running the Retail Media Toolset on top of an existing CMS is not building a parallel system that needs to be dismantled later. They are building on the same data layer, the same audience logic, and the same reporting infrastructure that the full integrated platform uses. When the time comes to migrate, the transition is a continuation — not a replacement.
Recognised by Gartner as a sample vendor for in-store retail media supply-side technologies, and operating across major retail chains in Europe and beyond, Doohlabs built In-Store IMPACT for exactly the situation most retailers are in — ready to move on retail media, working out how to get there without disrupting what is already working.
The answer, in most cases, is that you do not have to choose between speed and the right foundation. You just need a platform that supports both.
