Jarir Bookstore is one of the largest retailers in Saudi Arabia and one of the best known names in the Gulf. What began as a bookshop is now a chain of large-format showrooms selling books, consumer electronics, computers, mobile devices, office supplies and school equipment, trading across Saudi Arabia and into neighbouring GCC markets.
Jarir runs Live across more than 700 screens in its store network. That is the largest single deployment named on this site, and it is a useful one to understand, because retail at that scale breaks the assumptions most digital signage software is built on.
Why 700 screens is a different problem from 70
A signage platform that works comfortably at a handful of sites tends to fail at several hundred in one of three ways, and all three are operational rather than technical.
The first is publishing. A price change or a campaign launch has to reach every screen in every store, and it has to reach them without someone opening 700 individual displays. That is what display groups and central scheduling exist for: content is targeted at a group of screens rather than at a device, and one change lands everywhere it should.
The second is scope. A store network of this size has content owners at more than one level. Category and marketing teams own the campaign that runs nationally; a store may need something local on one screen. Scoped user access is what lets a large organisation give people the ability to publish without giving everyone the ability to publish everywhere.
The third is what happens when something goes wrong at one site. A screen in one showroom drops off the network, and the estate has to keep running. The Live players cache their scheduled content and play it from local storage rather than streaming it, so a network problem at one site is a monitoring issue rather than a black screen in front of customers.
Retail screens are not one thing
The reason a bookstore-turned-electronics-retailer ends up with hundreds of displays is that a large showroom carries several completely different kinds of screen, each with its own audience and its own update rhythm.
There is pricing and promotional display, which changes when the campaign changes and has to be right, because a wrong price on a screen is a customer service problem before it is a marketing one. There is product information at the shelf, particularly in the electronics and computing departments, where the screen is doing the job a spec sheet used to do. There is the window and entrance display, which is advertising to the street. And there is wayfinding and departmental signage inside a large floorplate, which barely changes at all but has to be correct.
Those four update on entirely different cycles from the same CMS. That, rather than any single feature, is the argument for a central content management system in retail: not that each screen is difficult, but that the alternative to one system is four.
Sizing a rollout of your own
Seven hundred screens is not seventy with more of them. The publishing model, the permission model and the failure model all change at that scale, and a platform that has not been run there before tends to show it in the second year rather than the first.
If you are planning a retail rollout, put your screen count, your store count and your campaign cycle into the first conversation. The costing below the page runs on exactly those three numbers, and sales can run it against yours rather than ours. Ask for a reference call if you would rather hear it from someone operating an estate at this scale.