How to Handle a Dinner Rush: Managing High-Volume Orders Smoothly

1. 01

   Step 1: Set realistic prep times before the rush starts

   

   Log into your shop dashboard at golumo.app (or open the Seller mode in the Lumo app) and check your menu. Each item should have a prep time that reflects tonight's reality – if your fryer is slow or you're short a line cook, add five minutes. Customers see this estimate at checkout, and the app adds a buffer, but starting honest keeps you from drowning.

   Between 4 and 5 PM, prep your stations: portioned proteins, sliced vegetables, sauces in squirt bottles, bags and boxes stacked within arm's reach. Write the evening's 86 list on a whiteboard where everyone can see it. If you're out of something, remove it from your Lumo shop or mark it out of stock so new orders don't include it. Nothing kills momentum like discovering mid-rush that you're out of chicken.

2. 02

   Step 2: Assign one person to manage incoming orders

   

   When the first wave hits, designate someone – manager, owner, or a calm front-of-house staffer – as the order captain. Their job is to monitor the tablet or phone for new Lumo orders, call out ticket times to the kitchen, and update prep times if things slow down. They also handle the in-app messages: a customer asking to swap a side, someone arriving early, a driver asking for the door code.

   The order captain doesn't cook. They watch the screen, the clock, and the rail. If orders are coming every two minutes and your kitchen can handle one every four, the captain pauses new orders in the app (you can toggle your shop on or off in Settings) until you catch up. Better to stop taking orders for 15 minutes than to blow past your promised times and rack up complaints.

3. 03

   Step 3: Batch orders by pickup time, not arrival time

   

   Print or display tickets in pickup-time order, not the sequence they arrived. If three orders are due at 6:40 and two at 6:50, start the 6:40 batch first even if a 6:50 order came in earlier. Use a marker or colored stickers to group tickets by ten-minute windows: everything from 6:30 to 6:40 gets a blue dot, 6:40 to 6:50 gets red.

   This prevents the mistake of finishing orders too early – food sitting under a heat lamp for 20 minutes tastes worse than food that comes out right on time. It also keeps your counter clear; you're not juggling 15 bags when only three customers are walking in. When a pickup customer or delivery driver arrives, the app sends you an alert and they can message in-app if they can't find you.

4. 04

   Step 4: Use a runner to stage completed orders

   

   Once a meal is plated or bagged, it goes to a staging shelf – not the counter where customers wait. Label each bag clearly: order name (from the Lumo ticket), pickup time, and any special notes ('extra napkins', 'utensils', 'nut allergy'). For delivery orders, the driver's name appears on the ticket; write it on the bag so your front staff can hand off fast.

   The runner's only job during peak is moving finished orders from the kitchen to staging and from staging to customers or drivers. If you don't have a dedicated runner, rotate a prep cook or dishwasher into the role for the rush. This frees your order captain to focus on timing and your kitchen to focus on cooking. When the driver arrives and opens the app, they'll take a photo of the bag at pickup (Lumo requires this), so make sure everything is sealed and labeled.

5. 05

   Step 5: Communicate delays immediately

   

   If you realize an order will be more than five minutes late, message the customer through the Lumo app right away. Tap the order, hit the message button, and type something simple: 'Running 10 minutes behind due to volume – your food will be fresh and hot, thanks for your patience.' Most customers are fine with a delay if you tell them; they're furious if they show up and wait without warning.

   For delivery orders, the customer can already track the driver on a map once pickup happens, so they'll know if things are slow on your end. If you're swamped and need to stop taking orders, pause your shop in the app. You can unpause when you've cleared half the board. The 5% service fee Lumo charges only applies to completed sales, so there's no penalty for pausing – it's built in as a relief valve.

6. 06

   Step 6: Check quality before every bag leaves

   

   Right before a bag goes out, open it. Check that the order matches the ticket: right entrées, correct sides, no missing items. Feel the container – is it still hot? If something sat too long, remake it. This takes 15 seconds and prevents the dreaded 'wrong order' message an hour later.

   After delivery or pickup, customers rate the order in the app. A string of four-star reviews because food arrived cold or incomplete will hurt your shop's visibility. Lumo shows ratings and reviews on your storefront, and customers sort by rating when they're deciding where to order. One bad rush can cost you a week of new orders. If you do get a low rating, respond to the review politely and fix the issue – most customers appreciate the follow-up and some will revise their rating.

7. 07

   Step 7: Debrief after the rush ends

   

   Once the last order goes out, gather your team for five minutes. What backed up? Which menu items took longer than expected? Did you run out of anything you didn't anticipate? Write down two or three changes for tomorrow: 'Prep double the sauce,' 'Add five minutes to burger cook time,' 'Move the bagging station closer to the fryer.'

   Check your Lumo earnings in the app's wallet – you'll see each completed order and the 5% service fee deducted. If you did $800 in Lumo orders tonight, you keep $760. Tomorrow, adjust your menu prices or prep times based on tonight's reality. Restaurants that do this debrief consistently handle rushes better every week. The goal isn't perfection on day one; it's a system that improves every shift.

Photos are illustrative. Service prices are typical ranges and vary by city. How we write our guides.