Store Operations · Grocery

Fresh Waste Prevention

Perishables trending to spoilage. Proposes markdown or pull timing.

Target KPI Waste %
Executes in ≤ 4 hours
System of record Relex · POS
Trigger condition

Remaining shelf life on a fresh batch falls below the sell-through the current velocity can clear, with enough time left for a markdown to work.

Write-back

Markdown scheduled in the POS price rules for the batch; waste projection updated in Relex.

Every write is gated on an approver role you name. Nothing runs unattended.

Procedure
  1. Project sell-through to expiry per batch from current velocity, remaining life, and the day of week.
  2. Model the markdown ladder that clears it: how deep, how early, and what it costs against full write-off.
  3. Check the donation and staff-sale routes where the margin maths says the markdown will not clear it either.
  4. Push the recommended action to the department task list with a time on it, since a fresh markdown decided late is worthless.
  5. Close when the batch clears or is recorded as waste, and the decision is scored against what actually happened.
Outcome metric

Recovered revenue per batch against the full write-off value, over a 30-day rolling window of decisions.

The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.

Run Fresh Waste Prevention on your data.

Pick three playbooks from the catalog. We wire them against your system of record for the pilot.

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3
What are your goals?
Step 2 of 3
About your operation
Step 3 of 3
Your contact info