Prices that change centrally
One publish, every store you selected.
Product catalogue
The whole range,
on one wall.
A shop cannot hold every variant, and a printed catalogue is out of date on arrival. A published catalogue shows the range, the price and the specification — and changes the morning any of them do.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
Product artwork in folders
One folder per range, reused by every store rather than rebuilt.
-
Laid out in Composition
A grid of products is a composition — the same machinery as a menu board.
-
Published per store
Stores that stock a range get it; stores that do not, do not.
-
Scan codes as artwork
A code on the panel carries someone to the full product page.
What you get
Six things it does today.
Scan for detail
Specifications and stock live on your own site; the screen carries the code.
Ranges in folders
The library stays navigable past a season's worth of artwork.
Range by store
Publish targets facilities, so a small store is not showing a range it cannot sell.
Product in use
Silent loops beside the price they belong to.
Every change on record
Audits records who changed a price panel and when.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can it read our product catalogue automatically?
No catalogue or PIM integration has been observed in the console. Panels are published as media.
Can stock levels show on screen?
Not from a live feed. Anything on the screen is published content.
Can each store show its own range?
Yes. Publish targets the facilities you choose.
What runs on the screens?
An Android player app on displays you own.