Use case · Multi-location ops
One person, one phone, every screen at every site
The way you run signage today: design in Figma, send to a print shop, wait a week, ship boxes to 40 locations, coordinate a swap window with every store manager, then chase the ones who forgot. The way you run it on our stack: open the CMS on your phone, upload the new art, pick which screens, done. Every device pulls it on its next wake. Dashboard tells you which ones rendered.
This isn’t a use case defined by what the signs say — it’s defined by who has to keep them current. If you’re the single ops, marketing, facilities, or merchandising lead responsible for signage across dozens or hundreds of physical locations, this page is for you. The vertical could be retail, QSR, workplace, healthcare, warehousing, or field service. The problem shape is the same.
What we mean by ‘managed at scale’: Wi-Fi connected color e-paper displays, a cloud CMS, and a fleet model where a single operator can push a design to a subset of devices — one store, one aisle, one region, or every unit in production — and see confirmation that it landed. No app to install on the device, no on-site technician, no reprint.
The design-print-ship-swap loop, and what it actually costs
Every multi-location signage program we’ve looked at has some version of the same weekly ritual. It looks organized on paper. On the ground it burns most of a headcount.
- Design — brand or merch approves the file. Fine, this part still happens.
- Print — send to a print vendor. Days of turnaround, minimum-quantity math, waste on the leftovers.
- Kit and ship — someone packs 40 kits, labels each for a location, tapes up boxes, hands them to FedEx. Multi-day transit.
- Coordinate the swap — email the 40 store managers with a window. Half of them will do it late. A few won’t do it at all.
- Verify — you don’t. Nobody has time to audit 40 stores. So you assume it happened and hope the district manager will flag it if not.
- Revert — the campaign ends. Start the loop over for the takedown or the next promo. Recycle the printed material.
The dollar cost is easy to underestimate because it’s spread across print vendors, freight, and the labor line of people whose time isn’t billed against “signage.” The wall-clock cost is worse: two weeks minimum from decision to in-store, which means you can’t react to a competitor promo, a stock-out, a weather event, or anything that moves faster than the print calendar.
What the loop looks like on Spectra 6
Same starting point — a designer hands over artwork. From there:
- Upload the artwork in the CMS. The dither preview shows exactly what the Spectra 6 panel will render, in the same six pigments the physical panel uses.
- Pick the scope: every screen, one region, this store only, the endcaps but not the aisle headers. Groups are tags, not folders — a screen can belong to many.
- Schedule the swap. Now, tonight at close, or the first Monday of next month. Time-zone aware per device.
- Devices wake on their schedule, pull the new art over Wi-Fi, render, sleep. A weekly-refresh device goes weeks between charges doing this.
- The fleet dashboard shows every device: last-render timestamp, current image thumbnail, battery, Wi-Fi RSSI, firmware version. Filter by anything that didn’t update.
The entire chain compresses from two weeks to about two minutes of operator time, plus the sleep cycle of the slowest device on your least-refreshed schedule. Nobody drives to a store. Nobody opens a box.
Why one person can actually run hundreds of screens
The unlock isn’t just “wireless updates.” Digital signage vendors have offered that for a decade with LCD screens. The unlock is that a Spectra 6 e-paper fleet disappears into the background the way LCD screens never do:
- No power runs. Battery-powered. Magnetic-mount. A store manager sticks it to the fixture and forgets it. That kills the biggest historical blocker to per-location scale — nobody has to hire an electrician per install.
- No screen fails you notice on a Sunday. An e-paper panel with no image on it looks like blank paper, not a black rectangle. Failures degrade gracefully; nobody calls corporate at 9pm because a screen “went dark.”
- No burn-in, no schedule padding. Reflective pigments hold state with zero power. You aren’t rotating imagery to prevent burn-in. What you schedule is what shows, indefinitely.
- Weeks between charges, not hours. A weekly-refresh cadence on a rechargeable cell runs six-plus weeks between charges. A coin-cell variant on a monthly cadence runs over a year. The store staff aren’t your battery-swap technicians.
- Provisioning that a non-technical operator can do. A store manager pairs a new unit by scanning a QR code on their phone. It joins the store’s Wi-Fi and inherits every group tag for that location automatically.
The net: the operational overhead per device trends toward zero after install. A fleet of 500 units doesn’t cost 500x the effort of one. It costs about 1.1x, because the marginal management cost is the CMS filter you type to select them.
What you can push, and at what cadence
Weekly retail promos
Endcap posters, category headers, brand cards adjacent to the shelf. Push Monday morning, live in every store by mid-morning. Kill Sunday night. See the retail deep-dive for the ESL boundary.
Room and desk state
Meeting-room signs that reflect calendar state, hot-desk plates that follow booking software, wayfinding that updates with the floor plan. Cadence measured in minutes for booking events, days for wayfinding.
Kanban and work-order state
Warehouse bin labels that reflect current SKU, kanban cards that reflect MES status, work-order travelers that update as they move through the line. Cadence: as often as your ERP or MES pushes state, throttled to the panel refresh rate.
Emergency and event overrides
Push a message to every screen in a building for a fire drill. Push a takedown to every screen in a store when a product gets recalled. Push a stock-out sign to a single shelf when inventory hits zero. Same interface, different scope.
What the operator actually uses
- Mobile-first web CMS. Works in Safari on an iPhone. No app to install. Same URL a district manager gets works from a laptop.
- Groups by tag. Every device carries tags: region:west, store:1147, fixture:endcap, campaign:q3-launch. Push to any boolean combination.
- Scheduled swaps. Now, one-shot future, or recurring. Time-zone per device so a “9am Monday” push actually lands at 9am local everywhere.
- Fleet dashboard. Sortable by battery, last check-in, current image, RSSI, firmware. Bulk actions on the filtered set.
- Roles. Merch designs, ops schedules, store managers do nothing but plug the unit in. Or invert if that’s your org.
- API and webhook ingress. Your DAM, PIM, or ERP can push updates without a human in the loop. Room booking systems and MES integrations are one webhook away.
Costs you stop paying
- Print runs. Per-campaign, per-location, per-size. Includes the waste on locations that closed or reformatted since the last run.
- Freight. The kits, the takedowns, the reprints when someone spelled a promo wrong.
- Labor at the site. Store manager time on swap windows, corporate visits to audit compliance, field marketing driving between locations.
- The delay tax. The revenue you don’t capture because a promo went live four days late, or a stock-out sign didn’t go up until the next print cycle.
Rule of thumb from the customers we’ve scoped: a signage program running 200+ locations on weekly cadence pays back the hardware inside 12–18 months on print and freight alone, before you count the labor line or the delay tax.
What it costs to start
- Pilot — $20–30k NRE, 10 units on stock reference hardware in your enclosure, live cloud instance addressing your real store list. 6 weeks.
- Regional rollout — $50–100k NRE, 200–500 units, custom PCB and enclosure, white-label CMS with your SSO and DAM wired in. 10–14 weeks.
- Unit cost at 500–5k volume — $60–180 per unit depending on size and battery topology, in your logo. Fully managed cloud is a per-device-per-month add-on; self-hosted on your Vercel is included.