Ramadan operations: one hour that decides the month

Ramadan is not a busier month. It is a differently shaped month, and operations built for a normal evening service break under it.

The defining fact: a large share of the night's revenue arrives in the forty minutes around iftar. Everything below follows from that.

Four weeks out: simplify the menu

The iftar rush is not the time for a broad menu. Cut it to the dishes that:

• The kitchen can produce at volume
• Hold quality when prepared slightly ahead
• Travel well, if you deliver
• Carry acceptable contribution — check againstmenu engineering

A shorter menu means faster ordering, faster kitchen, fewer mistakes and less waste. Most restaurants that do this report it as the single change with the largest effect.

Three weeks out: set up pre-orders

The most effective tool for flattening the peak. If a portion of your iftar is pre-ordered and paid, the kitchen can prepare against a known number and the forty-minute rush becomes a delivery of prepared orders rather than an avalanche of new ones.

Set up:

• A pre-order product or booking for iftar, with a collection or delivery window
• A deadline — typically Asr — after which the kitchen is committed
• Payment upfront, which removes no-shows

Two weeks out: configure the POS

Ramadan menu as a scheduled menu. If your system supports time-based menus, set the Ramadan menu to activate for the month and the iftar menu to activate in the window. Wameed supports menu scheduling; see thefeature page.

Reconfigure the till screen for the shortened menu. Top items on the first screen, no digging.

Raise delivery prep times for the iftar window. An honest 45 minutes protects your rating better than an optimistic 20. See theaggregator guide.

Add a second till. A browser cashier on a laptop, open for the peak two hours only.

One week out: staff and rehearse

• Schedule for the shape, not the hours. Maximum staff from an hour before iftar to an hour after; a thin crew in the afternoon.
• Staff iftar comes first. Feed your team before the rush, not during it. A team eating at 19:40 while customers arrive is a team that is not working.
• Rehearse the iftar sequence once, with the team, so everyone knows their position in the first ten minutes.
• Brief on the outage procedure. Peak load is when networks fail. Seeoffline rules.

During: the iftar hour

• Take payment before the rush where possible — pre-orders, or payment on seating
• Keep the floor plan in front of the manager. Seetable management
• Do not attempt upselling during the peak. It slows everything and lands badly
• Have someone whose only job is the collection point for takeaway and delivery riders — otherwise riders come to the counter and block it

Suhoor is a second business

Late-night trade has a different menu, a different pace and a different customer. Treat it as its own service with its own par levels and its own staffing, not as an extension of the evening.

After: what to measure

Ramadan data is only useful if you keep it separate. Record:

• Revenue and covers by fifteen-minute block around iftar
• Pre-order share of iftar revenue
• Delivery orders during the iftar window, and the cancellation rate
• Waste by item — seewaste management
• Average prep time against what you promised platforms
• Suhoor revenue as its own line

Write down three things to change next year while it is fresh. Every operator intends to and most forget by Shawwal.

The comparison trap

Do not compare Ramadan to the previous month. Compare it to last Ramadan. A POS that lets you define and save a period, and compare like-for-like, saves an hour of spreadsheet work and prevents a lot of wrong conclusions.