Choose the event that determines availability
If breakfast ends at 11, decide whether an order must be started, submitted, accepted, or paid before that time. Those events are not interchangeable. A customer can open a cart before the cutoff and submit it afterward, while a cashier may have an unfinished order on screen. Give staff a single approved rule and a clear explanation for guests rather than asking each employee to interpret the clock differently.
Map every supported channel separately: counter, drive-through, kiosk, phone, and online ordering where applicable. The same menu name does not prove identical scheduling behavior. Note the location, time zone, effective days, and any exceptional opening hours. Keep those details in one approved operating record. This checklist does not assume a universal breakfast schedule or claim that your customers want all-day service.
Test the boundary, not just the menu editor
Set up demonstration orders just before and after the cutoff. Include a saved cart, an unpaid counter order, a paid order awaiting preparation, and an item that changes to a lunch equivalent. Document the expected outcome for each. An already accepted breakfast order needs a responsible preparation decision even if the breakfast button disappears from new orders. Do not silently substitute another dish or change an agreed price without following your guest-resolution process.
Illustrative example: at 10:58 a guest starts a breakfast combo, then submits at 11:02. The shop’s policy might reject new submissions after 11 or allow an approved exception; the important point is that the policy, system response, and kitchen instructions agree. Ask whether the guest sees a clear message and can revise the order. Avoid accepting payment for something the kitchen has already stopped making.
Give the kitchen a separate readiness check
A digital schedule is not a physical kitchen changeover. Assign someone to confirm remaining ingredients, equipment readiness, and who handles accepted breakfast tickets during the transition. Use your trained food-safety procedures for food handling; a menu schedule is not a holding-time control. If both menus briefly overlap, define which items can actually be prepared together and how staff will communicate an unexpected shortage.
Use the sold-out menu guide for stock-driven availability. A planned cutover is different: the change happens because of an operating schedule, not because an item ran out. Keep the two controls distinguishable during testing. Confirm what happens when a manager temporarily extends breakfast, and check that the extension does not unintentionally change every location or reopen an item that is unavailable.
Write a short cutover runbook
The runbook should name the decision time, acceptance event, channel checks, kitchen owner, guest explanation, and exception approver. Include the person authorized to reverse a mistaken schedule. Review the first transition in person before relying on an unattended daily switch. Staff should know how to report a mismatch without changing multiple menus independently and creating a different configuration for the following morning.
After the shift, review accepted orders that needed intervention rather than judging success solely by whether lunch buttons appeared. Keep a clear record of manual overrides and recurring confusion. Use the Quick Service solution page to discuss your actual daypart boundary cases. Confirm current scheduling and integration support, including saved carts and already-paid orders, before presenting automated cutovers as an available Freedom POS capability.

