Menu Board and Digital Price Sync Verification

This template verifies that the digital menu board is showing the same prices as the current POS price file after a corporate price push. It also checks that the file loaded correctly, that unresolved pricing exceptions are cleared, and that current LTOs display the right prices and dates. The close-out section captures any mismatch so it can be escalated instead of left unresolved.

Use it after the corporate price push propagation window has passed and the store has had time to receive and load the update. It is especially useful on the day of a price change, before peak meal periods, and after any menu content refresh. If the board is still syncing or the POS file is not finalized, the inspection should be delayed until the correct version is active.

A shift manager, assistant manager, or trained store leader is usually the right person to complete it because they can confirm the POS file status and escalate mismatches quickly. In some operations, a field support lead or district manager may review exceptions after the store completes the walk-through. The key is that the inspector can access both the menu board and the current POS release information.

This template is built around a sample of at least 20 items, which gives a practical cross-check across core menu categories and price points. The sample should include high-volume items, items with recent price changes, and any items tied to modifiers or combo pricing if those appear on the board. If your menu is small, you can still use the full sample list and mark any items not applicable.

No. This template is focused on price synchronization, not on photography, branding, nutrition panels, or menu layout review. It is meant to catch pricing mismatches, stale LTOs, and failed file loads after a corporate push. If you also need content accuracy, add a separate menu content or brand compliance inspection.

The most common issues are a board still showing the prior price file, a partial load that leaves some items unchanged, and LTOs that remain visible after expiration. Teams also miss date ranges on promotions, especially when the board updates but the POS file does not. Another frequent problem is documenting the inspection before the propagation window has fully elapsed.

Any mismatch should be documented with the item name, board location, displayed price, expected POS price, and time observed. The issue should then be escalated through the store's pricing or IT support process so the board can be corrected or the POS file reloaded. If the mismatch affects guest-facing pricing, treat it as a priority non-conformance until resolved.

Yes. You can adapt the sample list to match your menu architecture, add sections for drive-thru boards or kiosk screens, and include fields for the POS version or content management system used. If your operation uses multiple digital displays, you can duplicate the sample section by board location so each screen is verified separately.