Skip to content

How to Stop Losing £4.50 on Every Remake

Every remake costs £4.50 in labour and food. These fixes cut 80% of them without slowing the pass or adding staff.

By The Berryin Team8 min read
Digital ordering system in a restaurant kitchen with a touchscreen display and a chef at work.

Why remakes happen—and why they cost more than you think

A remake is not just a second attempt at a dish. It is a chain reaction: the ticket gets rerouted, the cook restarts the prep, the pass slows, and the customer—if they’re still waiting—walks out or leaves a review. The £4.50 figure covers the food waste, the extra labour, and the lost sale if the customer leaves. But the real cost is the time: every remake adds 30 to 90 seconds to the pass, and in a busy service, that’s the difference between keeping up and falling behind.

Most remakes fall into three categories:

  • Wrong order: The ticket says ‘chicken tikka masala’ but the customer wanted ‘butter chicken’. This is a front-of-house mistake, but the kitchen pays for it.
  • Undercooked or overcooked: The dish comes out wrong, and the cook has to start again. This is a skill gap or a rushed pass.
  • Missing ingredients: The ticket is correct, but the kitchen forgot the garnish, the sauce, or the side. This is a checklist failure.

The first two are fixable with training and better workflows. The third is the easiest to stop—and it’s where most kitchens leak the most money.

The hidden cost of ‘just one more remake’

Say your kitchen does 50 remakes a day. At £4.50 each, that’s £225 lost daily—£6,750 a month. But the real damage is the domino effect: every remake delays the next ticket by at least 30 seconds. In a 3-hour rush, that’s 15 minutes of lost time per cook. If you’ve got three cooks, that’s 45 minutes of inefficiency, or roughly one extra member of staff you’re paying for but not using.

The fix isn’t to hire more people. It’s to stop the remakes before they happen.

How to cut remakes by 80% without slowing the pass

The two biggest levers are ticket accuracy and kitchen discipline. Neither requires new staff, a kitchen rebuild, or even a new system—just smarter workflows.

1. Stop wrong orders before they hit the pass

Wrong orders happen when:

  • The waiter writes it down incorrectly (or forgets to write it down at all).
  • The customer changes their mind after ordering but doesn’t tell anyone.
  • The ticket gets misread at the pass.

The solution is a double-check system that doesn’t add time but catches mistakes early:

  • Front-of-house: Train staff to read back the order before the customer leaves the table. ‘So that’s a large vegan burger with no onion, no cheese, and extra pickles—is that correct?’ This catches 60% of mistakes before they reach the kitchen.
  • At the pass: Assign one person (the expediter) to scan the ticket and the customer’s face. If the dish looks wrong, they ask for confirmation before it goes out. This stops 30% of remakes from skill gaps.

This adds zero time to the pass if done right. The expediter is already there; they’re just doing their job properly.

2. Make the kitchen a no-remake zone

The other 70% of remakes come from the kitchen itself. The fixes here are about standardisation and accountability—not more training, not more pressure, but clearer rules.

  • Prep sheets, not memory: Every dish has a checklist. ‘Chicken tikka masala’ isn’t just ‘chicken in sauce’—it’s ‘marinated for 2 hours, cooked at 180°C for 12 minutes, served with mint yoghurt and naan’. Write it down. If it’s not on the sheet, it’s not going out.
  • One person, one job: Assign ownership. If the garnish is missing, the garnish person owns it. No more ‘someone else forgot’. This cuts missing ingredients by 50%.
  • The ‘three-strike’ rule: If a dish is remade three times in a shift, the cook or prep person does an extra 15 minutes of cleanup. This isn’t punishment—it’s a motivator. People pay attention when their time is on the line.

3. Use tech to flag problems before they happen

Paper tickets are the enemy of accuracy. A digital kitchen display system (KDS) doesn’t just show orders—it tracks them and alerts when something’s wrong.

  • Colour-coded tickets: Red for ‘urgent’, yellow for ‘needs attention’, green for ‘on track’. If a ticket turns red after 5 minutes, the expediter knows to check why.
  • Automatic reminders: If a dish is supposed to have a side but doesn’t, the system flags it before it leaves the pass.
  • Real-time stats: At the end of service, the KDS shows which dishes were remade most often. That’s your training list for next week.

A KDS costs money, but the payback is immediate. If you’re doing 50 remakes a day, cutting even 20 of them saves £90 daily—enough to pay for the system in two weeks. See how a KDS works and how to switch from paper without a disastrous first week.

The trade-offs: What breaks if you fix remakes?

Most operators worry that tighter controls will slow the kitchen or make staff resentful. But the data says otherwise:

  • Speed vs. accuracy: A well-run kitchen with a KDS and checklists is faster than a chaotic one. The time lost on remakes is worse than the time saved by rushing.
  • Staff morale: The ‘three-strike’ rule might sound harsh, but it’s fair. People hate being blamed for mistakes they didn’t cause. Clear rules reduce frustration.
  • Customer experience: Fewer remakes mean fewer delays, fewer complaints, and more repeat business. The cost of a remake isn’t just £4.50—it’s the lost review, the lost tip, and the lost customer.

What does break?

  • Flexibility: If you’re used to improvising, standardisation feels restrictive. But the goal isn’t rigidity—it’s consistency. A dish should taste the same every time, not ‘whatever the cook feels like today’.
  • Short-term training costs: You’ll need to spend 30 minutes a week reviewing remake stats and adjusting prep sheets. But this pays for itself in one shift.

How to implement this without a kitchen meltdown

You can’t roll this out in a day. Here’s how to do it in three weeks without losing control:

Week 1: Audit and train

  • Count your remakes: For one shift, track every remake and why it happened. Use a whiteboard or a spreadsheet.
  • Train the front of house: Run a 15-minute session on reading back orders. No theory—just practice with real orders.
  • Introduce prep sheets: Start with one station (e.g., the grill). Write down every step for every dish they handle.

Week 2: Enforce the rules

  • Double-check at the pass: Assign the expediter to scan tickets against the customer’s face. No exceptions.
  • Flag missing ingredients: If a dish is missing a side, the expediter stops it before it leaves the pass.
  • Start the three-strike rule: Pick one cook to test it with. If they remake a dish three times, they do 15 minutes of extra cleanup.

Week 3: Add tech (if needed)

  • Pilot a KDS: If you’re still using paper, try a digital system for one station. See how to switch without a disastrous first week.
  • Review the stats: At the end of the third week, look at your remake numbers. If they’ve dropped by 30%, you’re on the right track.

The numbers: How much you’ll save

Let’s say you’re doing 50 remakes a day at £4.50 each. That’s:

Remakes cut Daily saving Monthly saving Annual saving
20 (40%) £90 £2,700 £32,400
30 (60%) £135 £4,050 £48,600
40 (80%) £180 £5,400 £64,800

Even cutting 40% of remakes (20 a day) pays for a Pro plan in under a month. See pricing and plans here.

What if you’re a cloud kitchen?

Cloud kitchens have a different problem: speed over accuracy. If you’re taking orders from multiple brands, remakes aren’t just costly—they’re visible to customers who might never come back.

The fixes are the same, but the priority shifts:

  • Brand consistency: Every dish must match the menu description, or the customer (and the marketplace) will complain.
  • Ticket routing: If you’re cooking for three brands at once, misrouted tickets cause chaos. A KDS with colour-coded stations stops this.
  • Prep ahead: Since you’re not seeing the customer, prep everything in advance. No improvising—just execution.

See how Berryin helps cloud kitchens run multiple brands out of one kitchen without accuracy slipping.

Do I need a new system to cut remakes?

Not necessarily. If you’re already using a KDS, focus on prep sheets and double-checking. If you’re on paper, a digital system will help—but the biggest wins come from training and discipline, not tech alone. Start with the three-strike rule and prep checklists before investing in new hardware.

Will this slow down my kitchen?

No—if done right, it speeds it up. Remakes add 30-90 seconds to every ticket. Cutting them frees up time. The key is standardisation, not micromanagement. Prep sheets and clear rules make the pass faster and more predictable.

How do I handle staff who resist the changes?

Frame it as protecting their time. ‘We’re cutting remakes so you’re not doing extra work for no reason.’ Involve them in writing prep sheets—they’ll own the process if they helped build it. And if someone hits three remakes, make it a team issue, not a personal one: ‘Let’s figure out why this keeps happening.’

What if my cooks say they don’t have time to fill out prep sheets?

They don’t. You write the sheets during quiet periods, and they follow them. Think of it like a recipe card—it’s not extra work, it’s the right way to do the job. If a cook complains, ask: ‘Would you rather spend 2 minutes writing this down now, or 10 minutes fixing it later?’

How do I know if my KDS is actually helping?

Track remake rates before and after. If you’re doing 50 remakes a day and drop to 20, the system is working. Also check ticket times: if orders are moving faster, the KDS is cutting waste. If not, you’re not using it right—maybe you need better training or different workflows.

Start with the three-strike rule and prep sheets. Those two changes will cut 50% of your remakes in a week. Then layer in tech and training. The money you save will pay for itself in days—not months.

See how Berryin’s KDS and kitchen tools fit into your workflow.

#kitchen-operations#order-accuracy#cost-control#kitchen-display-systems#remakes

Want to see this working on your own menu?

Book a free demo and we will set Berryin up with a slice of your real menu — ordering, POS, kitchen and reports, end to end.

Ready to run your restaurant smarter?

Book a free demo and see Berryin working with your own menu.

Chat on WhatsApp
Chat with us on WhatsApp