The challenge
Every price revision meant a designer re-exporting slides, a WhatsApp group of outlet managers, and a USB stick in the back of each TV. Boards drifted out of date, sold-out items stayed on screen through the lunch rush, and head office had no way to confirm which of the 34 outlets had actually updated. Daypart changes, breakfast to lunch to dinner, depended on someone at each counter remembering to switch.
What we deployed
DigiMenu connected to the chain's Petpooja POS over a push webhook, so menu and price changes flow from the POS to every published board without re-design. Items the POS marks out of stock are excluded automatically, and veg/non-veg markers and Half/Full size-price columns come straight from POS data. Boards were designed once in Studio, menu zones plus an offers ticker, and published through the Digisigns CMS to nested screen groups organised by city and outlet. Breakfast, lunch and dinner playlists switch on a daily schedule, updates reach screens by instant push, and proof-of-play logs confirm each board played the new content.
Why the sync direction matters
Most menu screens are updated by a person. These are updated by the POS. Petpooja pushes every change over a webhook, DigiMenu merges it without touching the chain’s manual edits, and items marked out of stock drop off the board before the queue can order them. The Digisigns CMS handles the rest: daypart playlists on a daily schedule, nested screen groups per city and outlet, and playback logs per board. See how the pieces fit on the restaurants page, the DigiMenu product page, or the full feature list.
“We stopped calling outlets to ask if the new prices were up. The proof-of-play report answers before we ask.”
A representative deployment story based on typical Digisigns rollouts. Details are anonymized and consolidated; metrics reflect ranges observed across comparable deployments.