Bakery daily wastage tracking — SKU-level template + how to act on the data

About this piece. A bakery is a forecasting business disguised as a baking business. You produce in the morning what you think you'll sell by evening; whatever doesn't sell either gets binned, marked-down, or staff-meal'd. A bakery without a daily wastage log is a bakery flying blind on its single biggest controllable cost. This piece gives you the SKU-level wastage template, the four categories every entry must fall into, and the weekly review that converts log entries into production-plan changes.

Why bakeries need a wastage log more than any other restaurant format

Three reasons:

1. No second life for unsold product. A QSR's unsold dosa batter becomes tomorrow's batter. A bakery's unsold croissant becomes tomorrow's bin liner. Once produced, the clock is real.
2. Production decisions are made 6–12 hours before sales happen. You can't course-correct mid-shift. The only feedback loop is the daily wastage log → tomorrow's production sheet.
3. High labour content. A ₹120 sourdough has ₹18 ingredient cost and ₹40 labour cost embedded. Throwing it away wastes the labour, not just the flour. Wastage % at a bakery is more painful than at a kitchen.

Public benchmark: well-run Indian artisanal bakeries operate at 4–7% production wastage. Bakeries without a daily log routinely run 14–22%. The 10-point gap is recoverable only through the data → production-plan loop, not through "telling the team to be careful".

The four wastage categories

Every wastage entry must fall into one of these four buckets — no "miscellaneous":

Markdown that did sell is not wastage — it's revenue at lower margin. Track it separately as "discount sales".

The daily wastage log — what's in it

Per SKU per day:

Column 6 must reconcile: Produced = Sold + Marked-down sold + Wasted + Carried forward (rare; only for shelf-stable items). If it doesn't, something is unrecorded — likely a staff meal not logged or a comp.

The closing ritual — 8:30pm to 9:00pm

The photograph is the part most owners skip. It's worth 10 minutes a week of review time. Patterns the spreadsheet won't show — "the wastage is always croissants on Wednesdays" — show in 8 weeks of photos quickly.

Weekly review — Sunday evening, 30 minutes

This is where the log becomes action. Open the log for the past 7 days; do four things:

1. Top 5 SKUs by absolute wastage value

Ranked by ₹, not units. The croissant at ₹35 cost wasted 8/day is the same problem as 1 cake at ₹280 cost wasted 1/day — but the chart will tell you which is recurring vs which is a single bad day.

2. Wastage % per SKU vs target

Set a target wastage % per SKU type:

SKU running 2× target for 2 weeks straight = production cut next week. SKU running below target consistently = potential under-production (lost sales) — increase 10%, watch.

3. Wastage by category mix

If 70% of wastage is "production over-run" → forecast issue, fix the production sheet. If 30%+ is "quality reject" → process audit (proofing temperature, ingredient consistency). If display damage > 5% → handling training.

4. Action list for next week

Three production-sheet changes max. Don't try to fix everything in one week. Pick the biggest absolute-₹ leak and address it.

Sample weekly action list:
1. Croissant production: reduce from 30 to 24 (last 14 days avg sold = 22)
2. Chocolate cake: try Tuesday batch only; current 3-day production has 40% wastage
3. Quality reject investigation: under-proofed sourdough 2x this week — check proofer thermostat

The production sheet — the other half of the loop

The wastage log is feedback; the production sheet is the lever. A production sheet has:

• SKU + planned production qty
• Trigger time (e.g. dough mix at 4am, oven at 6am)
• Responsible baker
• Carry-over note from previous day's wastage log

The discipline is: Sunday's review changes Monday's production sheet, not next month's. Same-week feedback is the entire point of daily logging.

Three mistakes bakeries make with wastage logs

1. Logging without acting

Most bakeries that log don't review. The log becomes a guilt diary. Schedule the Sunday review on the calendar; treat it like a meeting.

2. Treating staff meals as "free"

Staff meals are a real cost. If a bakery gives away ₹400/day in staff meals, that's ₹12,000/month — material on a small bakery's P&L. Either budget it as staff welfare (capped, e.g. ₹150/staff/day) or count it as wastage. Don't pretend it's neither.

3. Pricing markdown wrong

A 50% markdown sticker at 8:30pm is too late if sale window is until 9pm. Markdown timing should be tested — 7:30pm 30%, 8:30pm 50%. The right window is the one where the marked-down item actually sells in a meaningful proportion. Track it as a separate POS code.

Composite Bandra bakery — owner started logging July 2025. Week-1 wastage = 19% (₹2,800/day at cost). Week-12 wastage = 6.5% (₹950/day). Net annualised saving: ~₹6.7L. The change was almost entirely production-sheet trims; ingredient cost % barely moved. The log was the lever; the Sunday review was the act.

What to do this week

Print the wastage log template (linked below — free, no email). Pin it to the production board. The closing baker fills it for 7 days. Sunday evening, sit with the head baker for 30 minutes and update next week's production sheet against the data. That single loop, repeated, is the entire system.

Related on Restaurant Daily

• Cafe daily ops checklist (India) — 30-seater opening/mid-day/closing
• Petty cash voucher format India — free Excel template
• 5 gaps that show up by Friday of week one — month one as a new operator