Bilingual store targeting
Target store groups by language, including English and French groups, as an operational part of the request. Check the reach before you submit.
For retail teams
Retail screen changes, scoped before they reach stores
One campaign can touch a few screens or a whole store group. Docket makes the reach visible before anyone approves it, then keeps the record from request through deployment.
Know exactly which stores a change reaches
Choose a predefined group or individual screens. Docket shows a live count of exactly how many screens the selection reaches, and lets you expand it to see the exact list.
That matters when “this playlist” and “these stores” are not the same thing. The approver sees the scope before the work starts.
All stores — EN
All stores — FR
Pick screens…
Reaches 214 screens
Make the request match the network
Video-wall rows
For a 1×3 video wall, a request needs complete rows of three. Docket keeps the request aligned with the physical layout instead of leaving the operator to infer what was meant.
Device classification and inventory
Use the screen and device information mirrored from MagicINFO to make a request against the network that is actually in place.
Give head office and the signage team the same record
Head office can describe the campaign, pick the screens, upload or select the content, and set the dates. The signage team can review the complete request, deploy it in MagicINFO, and record the result as Deployed.
No one has to rebuild the scope from emails and spreadsheets. The paper trail keeps who asked, who approved, who deployed, and what happened together.
See the full workflowPlan campaigns around the work
Set go-up and optional come-down dates during business hours on weekdays. The calendar makes upcoming campaign work visible, and email notifications follow per-tenant routing rules.
If a campaign needs to run again, clone the finished request into a fresh Draft and set the new dates. Finished requests stay intact.
Keep the CMS out of the approval path
Docket reads from Samsung MagicINFO but cannot write back to it. The system cannot deploy content or change live screens. The human operator keeps that responsibility in MagicINFO.
See the MagicINFO integrationRead the security design