Ramadan operations checklist for restaurants in Jordan

What should you check before the first Ramadan service?

Work backwards from the day's local iftar time, rather than copying last year's clock times. Use the current prayer timetable for your location in Jordan. Separate customer collection promises from kitchen preparation times: a bag marked ready still needs checking and handing over.

Run a rehearsal before accepting a full load of Ramadan bookings. Follow each test order from acceptance to the packed bag. Nexara brings phone, website, app, table QR, Talabat and Careem orders into one live queue per branch, but someone still needs to own the handover.

Write the person's name beside the responsibility. In a small restaurant, one person may cover several jobs. What matters is that nobody assumes the other shift checked the printer or confirmed the booking.

How should you switch the menu for Ramadan?

Start with dishes your kitchen can repeat under pressure. For each iftar meal, specify exactly what is included and which choices the customer must make. A family meal with unclear portions creates phone calls at the point when your team has the least time to answer.

1. Review the Ramadan menu separately from the regular menu. Remove items you cannot prepare reliably alongside the iftar workload.
2. Check each meal's modifiers. Make included sides and paid extras distinguishable on the kitchen ticket.
3. Set the intended menu channels and check availability for each branch. Check stock locally before marking an item available.
4. Inspect the customer-facing menu on each connected channel, then place a test order and inspect its printed ticket.

Nexara supports menu lists, modifier groups, channel-specific menus and per-branch availability. It also supports catalogue pushes to Talabat and Careem. Assign someone to make the Ramadan menu change and verify it before the branch begins accepting orders.

The one menu across ordering channels guide explains how the shared catalogue connects to your ordering channels. For Ramadan menu operations, finish by checking what the customer can actually order on each one.

How many iftar pre-orders should you accept?

Set limits by preparation and packing capacity within each promised window, not by your daily order total. A restaurant can have enough ingredients for the evening and still accept more simultaneous collections than its packing bench can handle.

Suppose a branch handles 180 orders a day at an average ticket of 7 JOD. It has accepted 48 pre-orders for collection in the final 30 minutes before iftar. Those pre-orders alone require 1.6 completed bags per minute, before any walk-in or newly arriving orders.

If a rehearsal shows that the packing bench completes one checked bag per minute, that window can handle 30 bags under those test conditions. The 48 bookings exceed that by 18. Move some collections earlier with the customer's agreement, reduce what you accept, or change the packing setup and retest it. Do not count an untested extra pair of hands as proven capacity.

Keep a controlled pre-order sheet with the customer contact, promised collection or delivery window, meal quantities, payment status and person who accepted the booking. Match it against the actual order queue so a booking does not become a second order when another employee reads the sheet.

For scheduled pre-orders, Nexara supports Careem orders and printing when they become due. Confirm the intended channel's booking and printing workflow before advertising timed collections. The Pro call-center screen retrieves saved addresses and past orders by phone number; the call-center order-taking guide covers that process.

Can your printers handle iftar rush orders?

Test a burst of representative orders, not one short receipt. Include Arabic modifiers and meals that route to different stations. Watch where tickets arrive, whether cooks can read them and whether packing receives the information needed to assemble the whole order.

Nexara prints on standard ESC/POS thermal printers connected by USB or network. Arabic item names and modifiers print correctly on supported thermal printers. Printer-category controls determine which items print at each station.

Follow the rehearsal order through this path and check that the packed bag matches the ticket before handover.

• Load fresh paper and put spare rolls where the shift can reach them.
• Check each station's category routing, including Ramadan-only items.
• Test the configured backup printer. Nexara supports automatic printer failover where a backup is configured, or category rerouting from the dashboard.
• Agree who may request a manual reprint and how the kitchen will identify it before cooking the order again.

If the branch connection drops, orders keep arriving in the cloud queue and printing catches up after reconnection. Keep a tested phone hotspot beside the printer PC. Use the printing and connection FAQ when checking your fallback procedure.

Who owns the checks before and during iftar?

Separate shift coverage from task ownership. A roster says who is present. A task says who must finish a specific check and by when. NexaraFlow supports recurring timed tasks with branch assignments and role-scoped task lists. It is a Pro feature.

Build tasks around observable results: the inventory count is completed, unavailable items are checked on customer menus, or a test ticket has reached the correct printer. 'Prepare for iftar' is too vague to close honestly.

Use the NexaraFlow timed-task guide to structure recurring checks. Overdue tasks can escalate. Urgent service failures need a direct handover to the named shift lead: if a printer stops during service, tell them immediately.

Plan staff breaks and meal coverage explicitly. During handover, the outgoing employee should identify outstanding commitments, including bookings that have been accepted but have not yet reached packing.

What should you review after each Ramadan service?

Record the first point where work backed up. Was food waiting for bags, were packed orders waiting for drivers, or were customers arriving before their agreed window? These require different changes. Adding kitchen staff will not fix a collection desk that cannot identify orders.

Nexara has report tabs for orders, channels, failed orders and complaints. Its inventory tools support counts and waste records. Combine those records with the shift lead's notes to identify where delays started.

Before the next service, change the acceptance limit or preparation plan where the evidence supports it. Brief the order-taking team on the revised promise before they accept more bookings.