Menulab
Get started
Menulab Blog

Weekly Perishables-Turn Dashboard: Spreadsheet Template and Thresholds to Cut Spoilage Costs

By MenulabSeptember 20, 2026

Manager reviewing a weekly perishables dashboard spreadsheet with fresh produce in background

Why a weekly perishables-turn dashboard matters

Perishable inventory is where restaurants and cafes lose margin fastest. A compact weekly dashboard gives managers a single view that highlights items moving below target, flags excess ordering, and creates predictable actions before food becomes waste. This guide explains the spreadsheet columns, numeric thresholds, and weekly workflows you can implement in a single 10-minute review.

Core outcomes to expect

When you run the dashboard each week you should be able to: identify the top 10 slow movers, reduce emergency markdowns, cut peak overordering, and adjust par levels so purchases match real demand.

Spreadsheet setup and essential columns

Build a one-sheet dashboard with live links to your PO and EPOS data. Keep columns simple so the line cooks and inventory clerk can update it in under five minutes.

  • SKU / Item name
  • Category (leafy, fruit, dairy, protein)
  • Unit of measure and pack size
  • On-hand quantity
  • Avg weekly usage (last 4 weeks)

From those fields calculate: turns per week, weeks on hand, and % variance vs forecast. Use these quick formulas in Excel or Google Sheets:

Turns per week = Avg weekly usage / Average inventory. Weeks on hand = On-hand / Avg weekly usage. Variance = (On-hand - Avg weekly usage) / Avg weekly usage.

Sample cell formulas

Assume columns: A Item, D On-hand, E Avg weekly usage, F Average inventory (if tracked), G Turns.

G2 formula example: =IF(E2=0,0,E2/IF(F2=0,MAX(1,D2),F2)). For weeks on hand use: =IF(E2=0,999,D2/E2).

Simple numeric thresholds to act on

Use consistent thresholds so every staff member makes the same decision when the report flags an item.

  • Turn targets by category: high-risk leafy greens 4+ turns/week, herbs 6+ turns/week, berries and tender fruit 8+ turns/week, dairy and protein 2-3 turns/week.
  • Reorder cap: do not order more than 1.5 times avg weekly usage for high-risk items; cap at 2 times for medium-risk items only with manager approval.
  • Markdown trigger: apply a planned discount or special when weeks on hand > 1.5 for high-risk items or > 3 for medium-risk.
  • Exception flag: any variance > 50% must have an owner and corrective action logged.

How to interpret turns and weeks on hand

If turns decline week over week by 20 percent, check menu placement, prep yields, and portion sizes. If weeks on hand grows above the threshold, reduce next order by the difference. Use the dashboard to create one-line notes for buyers explaining why an order was reduced.

Weekly workflow for operators

Run the dashboard at the same time each week, ideally after the slowest service day when counts are stable. The weekly review should take 8 to 12 minutes and follow a fixed agenda: update counts, review flagged items, decide reorder caps, and log markdowns or promos.

Immediate corrective actions when an item is flagged:

  • Pull a quick usage check with the chef for menu mix changes.
  • Apply a short-term promo or cross-utilize in specials.
  • Reduce next PO quantity to match the reorder cap or zero it for one cycle.
  • Change par levels or switch supplier pack size if overpack is causing waste.
  • Record the decision and owner in the sheet for accountability.

Operational examples

Example 1: Arugula shows 0.6 turns and 2.8 weeks on hand. Threshold for leafy greens is 4 turns and 1.5 weeks. Action: reduce next order to zero, promote arugula salad special two nights that week, and re-evaluate portion sizes.

Example 2: Blueberries have 5 turns but seasonal spike is expected next week. Action: keep reorder cap at 1.5x weekly usage and coordinate extra prep for baked goods rather than fresh garnish.

Maintaining the dashboard and next steps

Automate data pulls where possible. If you cannot, assign a single person to update the sheet and timebox the task. Review historical dashboard snapshots monthly to refine thresholds for your concept, not someone else s averages.

Ready-to-use template and implementation support are available. If you want the proven spreadsheet with formulas and a short training checklist for staff, download the template and run your first week s audit. Small, consistent changes to turns will show measurable P L improvements within 30 days.

Frequently Asked Questions

How often should we update the dashboard data?

Update counts and weekly usage once per week, after your slowest service day, so numbers reflect stable on-hand inventory and recent sales.

What if average weekly usage is zero for a new item?

Use a temporary placeholder usage based on expected weekly demand or recent menu tests, cap orders at one pack, and treat the item as high-risk until three weeks of real data exists.

Can this dashboard work for single-location independents?

Yes. Keep the sheet simple, focus on the top 30 SKUs by cost and spoilage, and enforce the weekly review to see rapid gains with little overhead.

Who should own corrective actions when an item is flagged?

Assign ownership to either the kitchen manager or the purchasing lead. Log the decision in the sheet with the owner s name and due date for follow-up.

Menulab