Grocery End-of-Day Perishable Shrink Log

This template covers end-of-day documentation for perishable shrink events such as markdowns, disposal, donation, and waste by category. It is meant to capture what happened, what was counted, and why the product left sellable inventory. The goal is to create a repeatable record that supports shrink reporting and trend analysis.

Use it once per day at close, or at the end of each operating shift if your department closes in waves. The recurrence should match the store's closing process so the log reflects the final state of perishable inventory. If your operation has multiple departments, each one should complete its own log on the same cadence.

The DRI is usually the department lead, closing supervisor, or designated associate responsible for perishable counts and waste handling. The person completing it should be able to verify markdowns, confirm disposal or donation actions, and reconcile the log against the day's inventory activity. If a manager reviews it later, the original entries should still be independently verifiable.

Yes, because it creates a consistent record of shrink decisions and disposal handling. That matters when you need to show how product was classified, where it went, and who verified the action. It also helps reduce gaps between operational waste handling and the records used for internal review or external audit.

A common pitfall is combining multiple actions into one vague entry, such as mixing markdowns and disposal without separating them by category. Another is recording totals without a verification step, which makes it hard to confirm accuracy later. Teams also sometimes skip the reason for shrink, which weakens trend analysis and makes recurring issues harder to spot.

Yes, and it should be tailored to the department's product mix and waste process. For example, produce, dairy, meat, and bakery may need different category labels, disposal reasons, or donation fields. Keep the checklist items independently verifiable so each department can answer yes, no, or N/A without ambiguity.

Ad-hoc notes are easy to start but hard to reconcile, especially when multiple people handle the same product during the day. This template gives you a structured task type with clear checklist items, so the log can be reviewed, audited, and compared over time. It also reduces blocking follow-up because missing details are easier to catch before the day is closed.

Yes, it pairs well with inventory counts, markdown workflows, and POS adjustments because the log captures the operational reason behind the numbers. Many teams use it alongside a closing checklist or a perishable department runbook so the shrink record is part of the same closeout process. If you integrate it, keep the log focused on verification and classification rather than duplicating every transaction detail.