Known-Loss Markdown Tracking Form
Track damaged, expired, or unsellable goods in one form so known loss is separated from unknown shrink and inventory records stay clean.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Retail · Grocery · Pharmacy · Wholesale Distribution
Overview
The Known-Loss Markdown Tracking Form records inventory that is no longer sellable because it was damaged, expired, recalled, returned, or otherwise removed from sale. It gives teams one place to capture the item description, SKU/UPC, quantity, condition, loss reason, valuation, and the action taken, such as markdown, donation, disposal, or expected vendor credit.
Use this template when you need a clean audit trail for known loss and want those items separated from unknown shrink in inventory reconciliation and loss-prevention reporting. It is especially useful in stores, warehouses, pharmacies, and departments that handle perishable, seasonal, or high-turnover goods. The manager review section helps confirm the disposition decision before the record is finalized.
Do not use this form as a catch-all for unrelated incidents. If the event is a workplace injury, customer complaint, theft investigation, or safety hazard with no inventory disposition, a different form is a better fit. It is also not the right place to collect unnecessary PII or extra narrative that will never be used. Keep the fields tied to the business purpose: document the loss, support the valuation, and show what happened after the item was identified.
Standards & compliance context
- If the form is public-facing or used by employees with accessibility needs, design labels, validation, and error states to meet WCAG 2.1 AA expectations.
- Apply GDPR data minimization by collecting only the fields needed to document the loss, approve the disposition, and reconcile inventory.
- If the form includes any health-related products or pharmacy items, follow the minimum-necessary principle and avoid collecting patient-specific information.
- If the workflow includes employee or customer notes, avoid unnecessary PII and add a clear disclosure about how the information will be used and retained.
- If loss prevention review creates a case record, keep the audit trail consistent so the form supports internal controls and later review.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Record Details
This section anchors the event in time, place, and ownership so the loss can be traced back to the correct store and department.
-
Date of Markdown / Disposal
The calendar date on which the markdown or disposal action was taken.
-
Time of Markdown / Disposal
Approximate time the action was completed.
- Store / Location Number
- Department
- If 'Other', specify department
-
Recorded By (Name / Employee ID)
Person completing this form. This field is part of the audit trail and will not be anonymized.
Item Information
These fields identify exactly what was lost, which is essential for matching the record to inventory and item master data.
- Item / Product Description
-
SKU / UPC / PLU
Scan the barcode if available. Leave blank only if the item has no scannable code.
- Brand or Supplier
- Unit of Measure
-
Quantity Affected
Number of units, cases, or pounds being marked down or disposed of.
-
Expiration / Best-By Date (if applicable)
Required for perishables, pharmaceuticals, or any date-coded product.
Loss Reason and Condition
This section explains why the item is unsellable and provides the evidence needed to support the disposition decision.
- Primary Reason for Markdown / Disposal
- If 'Other', describe the reason
-
Condition Description
Be specific and observable. Vague entries such as ‘bad’ or ‘damaged’ will be returned for clarification.
-
Recall / Advisory Number (if applicable)
Required when loss reason is ‘Recalled Product’. Reference the FDA, USDA, or internal recall number.
-
Photo Evidence
Attach one or more photos of the damaged or unsaleable item. Strongly recommended for damage claims and recalls.
Valuation
These fields document the financial impact and the action taken so markdowns, donations, and credits can be reconciled cleanly.
-
Retail Price per Unit ($)
Full retail selling price per unit at the time of markdown.
-
Total Retail Value ($)
Auto-calculated: Quantity × Retail Price per Unit.
- Markdown / Disposal Action Taken
-
Markdown Sale Price per Unit ($)
Required if action is ‘Marked Down for Quick Sale’. Enter the reduced selling price.
-
Donation Recipient Organization
Required if action is ‘Donated’. Retain the donation receipt for tax and audit purposes.
-
Vendor Credit Expected?
Indicate whether a vendor allowance or credit memo is anticipated for this loss.
Manager Review and Authorization
This section creates the approval trail and escalation path that turns a draft record into an auditable business document.
- Authorizing Manager Name
- Manager Employee ID
- Date of Manager Review
- Manager Decision
- Manager Notes / Correction Details
-
Manager Signature
Digital signature confirms the manager has physically inspected or verified the reported loss and authorizes the accounting entry.
-
Loss Prevention Notified?
Notify Loss Prevention for any single event exceeding your store’s threshold (check your LP policy for the dollar amount).
-
LP Case / Incident Number
Enter the Loss Prevention case number if one was opened.
How to use this template
- 1. Set up the form with your store locations, department list, loss reason options, and disposition choices so users can select from controlled values instead of free text.
- 2. Enter the record details as soon as the known-loss item is identified, including date, time, location, department, and the person submitting the form.
- 3. Complete the item information with the exact description, SKU or UPC, unit of measure, quantity, and expiration date if the item is date-sensitive.
- 4. Select the loss reason, add condition details, attach photos, and include any recall number so the record explains why the item is unsellable.
- 5. Record the valuation and disposition fields, then route the form to a manager for review, approval, and any loss-prevention notification or case number.
- 6. After approval, use the completed record to update inventory, support markdown or disposal actions, and retain the form as part of the audit trail.
Best practices
- Use conditional logic so department_other, loss_reason_other, and similar fields only appear when the selected option requires them.
- Mark required versus optional fields clearly and keep the form to the minimum necessary data needed for reconciliation and reporting.
- Use a date picker for expiration_date and numeric inputs for quantity and prices so validation is consistent and data exports are clean.
- Attach photos at the time of discovery, not after the item has been moved or discarded, so the condition record remains credible.
- Separate markdown, donation, disposal, and vendor-credit outcomes into distinct actions so the inventory adjustment is easy to trace.
- Require manager review before final submission when the disposition affects financial reporting or loss-prevention follow-up.
- Keep submitted_by and manager fields tied to role-based accountability rather than collecting unnecessary personal details.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this form used for?
This form records known loss events such as markdowns, disposals, donations, and vendor-credit cases for goods that cannot be sold at full value. It captures the item, reason for loss, condition, valuation, and manager approval in one place. That makes it easier to reconcile inventory and keep known loss separate from unexplained shrink.
When should a team use this instead of a general incident form?
Use this form when the issue is specifically tied to product loss, damage, expiration, recall, or unsellable condition. A general incident form is better for safety events, customer complaints, or employee issues that do not affect inventory disposition. If the outcome is a markdown, disposal, donation, or credit request, this template fits.
Who should complete and approve the form?
Store associates, department leads, or inventory staff can enter the initial record, depending on your workflow. A manager should review the valuation, disposition choice, and supporting evidence before the record is finalized. If loss prevention needs to investigate, the form also gives them a clear handoff point.
How often should this be used?
It should be completed each time a known-loss item is identified, not batched loosely at the end of the month. Some teams review these records daily during receiving or closeout, while others submit them as events occur and reconcile them during scheduled inventory checks. The key is consistency so the audit trail stays reliable.
What fields should be customized for our operation?
Common customizations include department lists, loss reason options, markdown actions, and approval routing. You may also want to add fields for lot number, vendor return status, disposal method, or store-specific cost center codes. Keep the form focused on data you will actually use for reconciliation and reporting.
Can this form be integrated with inventory or ERP systems?
Yes. The item, quantity, valuation, and approval fields map well to inventory, POS, and ERP workflows, and the record can be used as a source document for downstream adjustments. If you integrate it, keep field names aligned with your system's item master and transaction types so exports are easy to reconcile.
What are the most common mistakes when teams use this form?
The biggest issues are vague loss reasons, missing photos, inconsistent valuation, and skipping manager review. Teams also sometimes mix known loss with unknown shrink, which makes reporting less useful. Another common problem is collecting too much detail without a clear disposition path, which slows completion and reduces compliance with internal controls.
How does this help compared with ad hoc notes or email threads?
Ad hoc notes are hard to search, hard to audit, and easy to lose when a question comes up later. This template creates a consistent record with required fields, validation-friendly data entry, and a clear approval trail. That makes it easier to explain why inventory changed and what action was taken.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
MangoApps NoCode Workflow Apps let teams build, customize, and deploy employee apps without IT—automating workflows and boosting operational efficiency fast.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
MangoApps refreshes its brand and logo to power AI-first frontline work with a unified workforce platform that keeps teams aligned daily
-
HR compliance software that keeps records audit-ready every day with real-time reporting, tracking, and documentation.
Ready to use this template?
Get started with MangoApps and use Known-Loss Markdown Tracking Form with your team — pricing built for small business.
