Menu Scheduling for Breakfast Cafes: Items That Switch Off at 11am

Breakfast menu timing for online ordering is a simple idea with an expensive failure mode: the poha and the masala omelette should stop being orderable at 11 am, and if they do not, somebody orders them at 12:15, the batter is finished, and a staff member spends five minutes on WhatsApp cancelling and apologising. Menu scheduling moves that cut-off from a person's memory into the menu itself.

This post walks a breakfast cafe through it: mapping which items switch off when, setting windows on categories and single items, using snooze for the days the idli batter runs out early, and what the customer sees at 11:05 when the breakfast menu has gone and the lunch bowls have taken its place.

The 11:05 problem

A cafe that sells breakfast until 11 and lunch after has two menus, and online customers only see one of them if the system knows what time it is. Without scheduling, the whole menu is live all day. The customer who opens the store page at noon sees the ₹140 poha next to the ₹220 lunch bowl, picks the cheaper one, pays, and the kitchen gets an order it cannot make.

The cost is not just the five minutes. It is a refund to process, a customer who now distrusts the menu, and an order that would otherwise have been a ₹220 bowl. Multiply by three or four a day and a cafe loses a few thousand rupees a month in orders that were switched or cancelled, plus the staff time. The same logic applies to the evening: a cafe that stops its sandwich grill at 7 pm should not be taking sandwich orders at 8.

Map the day before you touch the settings

Ten minutes with a pen saves an hour of clicking. List every category and write down when it can actually be made. A typical breakfast cafe ends up with something like this.

Notice two things. Coffee has no schedule at all, because it is available all day; only add a window where there is a reason. And the bakes do not have an end time, because they end when they sell out, which is a different tool.

Category windows and item windows

Set the window on the category wherever you can. Put "Breakfast plates" on 7:30 to 11:00 and every item inside inherits it. When you add a new breakfast dish next month, it gets the window automatically. If the category needs two windows in a day, such as snacks from 8 to 11 and again 4 to 7, add a second slot on the same category rather than making two categories with the same items.

Use an item-level window only when one dish differs from its category. The masala dosa might run until 11:30 because the dosa batter lasts longer than the poha; give it its own window inside the breakfast category. An item window narrows the category window and cannot widen it, so keep the category window as the outer limit and tighten single items inside it.

Keep item-level windows to a handful. Two or three special dishes with their own hours is easy to remember; twenty is a maintenance problem the next time you change your opening hours. If your menu changes by meal rather than by item, the category-first approach in rotating menus that switch automatically is the cleaner model.

Snooze is for sold out; schedule is for timing

These two get confused, and the confusion is how a dish mysteriously never comes back. A schedule answers "when is this normally sold". Snooze answers "we ran out today". The croissants are scheduled from 7:30 with no end time; on a Tuesday when they go by 9:40, snooze them for the rest of the day and they return on their own tomorrow morning. On a Saturday when the second bake arrives at 11, snooze them until 11.

Never use a schedule to handle a one-day shortage, and never use snooze to handle a daily cut-off. The first leaves you editing windows every morning; the second relies on someone remembering to un-snooze.

What this looks like on Tezzu

In the Tezzu dashboard, open the menu, select a category such as Breakfast plates, and turn on availability scheduling. Tick the weekdays and set the start and end time, 7:30 to 11:00, and save. From that moment the category and everything in it shows on the WhatsApp bot and the store page only inside that window. The weekend brunch category is set to Saturday and Sunday only, 8:00 to 13:00, and simply does not exist on a Wednesday as far as customers can tell.

Single items are scheduled from inside their category: open the masala dosa, give it 7:30 to 11:30, and it stays on for half an hour after the rest of breakfast has gone. Snooze is on the item too, with a choice of the rest of the day or a fixed time. Nothing is deleted when a window closes; the item is hidden from customers and reappears on its own when the next window opens, with its price, photo, variants and add-ons intact.

Scheduling sits apart from two other settings so they do not interfere. Store hours still decide whether the bot accepts any order at all, and scheduled orders still let a customer pick a later slot; a customer at 10:50 can order a lunch bowl for 1 pm because the lunch category is open for that time. Orders arrive in the live dashboard and staff app as usual, and the KOT prints the item the customer actually saw. The setup guide with every screen is in menu scheduling in Tezzu, and the rest of the menu tools are on the features page.

What the customer sees at 11:05

This is the part that earns the money. At 10:55 a customer opens your store page and sees breakfast plates and lunch bowls, because both windows are open for that five-minute overlap. At 11:05 the same customer sees lunch bowls, sandwiches, bakes and coffee. No "breakfast is over" message, no greyed-out items, no reply from staff. The ₹220 bowl is simply what is for sale.

Over a month, if four customers a day who would have ordered a ₹140 breakfast at noon order a ₹220 bowl instead, that is around ₹9,600 of extra revenue and zero cancellations, before counting the staff time saved. The numbers are illustrative, but the direction is reliable: a menu that matches the kitchen's clock turns cancelled orders into sold ones.

The same trick works in reverse for a cafe that wants to push breakfast. A "before 9 am" category with a ₹99 coffee and croissant deal, scheduled 7:30 to 9:00 on weekdays, gives office-goers a reason to order on the way in and vanishes before the brunch crowd arrives. How a tiffin kitchen uses the same feature to rotate a different menu every weekday is in rotating menus for tiffin services, and the wider case for a cafe taking orders on its own channel is in cafe online ordering without apps, with the setup described on Tezzu for cafes.

Frequently asked questions

How do I make breakfast items unavailable after 11 am on my online menu?

Use a menu with time-based availability. Put the breakfast category on a window such as 7:30 to 11:00 and every item in it is hidden from the bot and store page outside those hours, then returns the next morning. On Tezzu this is set on the category in the dashboard, with weekdays and start and end times, and single items can have their own narrower window.

Can I show a different menu on weekends only?

Yes. Schedule the weekend brunch category to Saturday and Sunday with its own hours, and it does not appear on weekdays at all. Customers who open the store on a Wednesday see only the weekday menu, so nobody orders pancakes on a day the brunch cook is not in.

What is the difference between snoozing an item and scheduling it?

A schedule is the regular pattern: breakfast ends at 11 every day. Snooze is for today only: the croissants sold out at 9:40, hide them until tomorrow. Snoozed items come back automatically when the snooze ends, and scheduled items come back when their next window opens. Using one for the other's job is how dishes go missing from menus.

Does menu scheduling change my cafe's opening hours?

No. Store hours still decide whether orders are accepted at all. Scheduling only decides which items are offered within those hours. A cafe open 7:30 to 19:00 can have breakfast until 11, lunch from 11, and coffee all day, all inside the same opening hours.