Cosmetics Tester Damage and Breakage Write-Off Log
This Cosmetics Tester Damage and Breakage Write-Off Log records damaged tester units by SKU, cause, and disposition so stores can adjust inventory and support vendor credit claims.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Beauty Retail · Cosmetics Stores · Department Stores · Pharmacy Retail
Overview
This Cosmetics Tester Damage and Breakage Write-Off Log is a workplace form for recording damaged cosmetic tester units in a consistent, auditable way. It captures when the issue was discovered, who reported it, where it happened, which brand and SKU were affected, what kind of damage occurred, and how the item was handled afterward.
Use this template when a tester is cracked, contaminated, missing parts, leaking, or otherwise no longer suitable for customer use. It is especially useful when the store needs to adjust inventory, document a write-off value, or submit a vendor credit claim. The disposition fields make it clear whether the tester was returned to the vendor, destroyed, or handled another way, and the review section creates a supervisor approval trail.
Do not use this form as a general incident report for customer injuries, employee accidents, or theft investigations. It is also not the right tool for full product recalls or quality complaints that affect sellable inventory across many locations. For best results, keep the fields focused on the minimum necessary information: product identity, damage details, photos, and the action taken. That keeps the log useful for operations while avoiding unnecessary collection of PII or unrelated narrative.
Standards & compliance context
- The form supports GDPR Article 5 data minimization by limiting collection to the fields needed for inventory control, vendor claims, and approval.
- If employee_id or reported_by identifies a person, include a clear notice about how the information will be used and who can access it.
- Keep any photo upload or attachment field focused on the damaged tester and avoid capturing unnecessary customer or employee PII in the background.
- Use an audit trail for edits, approvals, and disposition changes so the write-off record remains traceable.
- If your organization treats tester handling as part of a regulated quality or loss-control process, retain supporting_documents according to your internal retention policy.
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
Log Entry Details
This section captures when the issue was found, who reported it, and where it occurred so the record can be traced back to a specific store and shift.
-
Date of Report
Date this log entry is being created.
-
Date Damage Was Discovered
Date the damaged or broken tester was first identified. May differ from report date.
- Reported By (Employee Name)
-
Employee ID
Optional — include if required by your store's loss prevention policy.
- Store / Location
- Department / Section
Product Identification
This section identifies the exact tester unit so inventory, pricing, and vendor claim records can be matched without guesswork.
- Brand Name
- Product Name
-
Shade / Variant
Include shade name or number if applicable.
-
SKU / UPC
Scan barcode or enter manually. Required for inventory adjustment and vendor credit.
- Tester Unit Type
-
Quantity Damaged / Broken
Number of individual tester units affected.
-
Retail Unit Value (USD)
Retail price per unit. Used to calculate total write-off value.
-
Total Write-Off Value (USD)
Auto-calculated: Retail Unit Value × Quantity Damaged.
Damage Assessment
This section documents what happened to the tester and why, which is the core evidence for write-off decisions and vendor follow-up.
-
Type of Damage
Select all that apply.
- Probable Cause of Damage
- Describe Other Cause
- Damage Description
- Was this tester damaged upon arrival from the vendor?
-
Damage Photos
Attach one or more photos of the damaged tester. Strongly recommended for vendor credit claims.
Disposition and Vendor Claim
This section records the action taken after the damage was confirmed, including return, destruction, and any vendor credit claim details.
-
Disposition Action
Select the approved handling method for this damaged tester.
- Describe Other Disposition
- Has a vendor credit claim been initiated?
-
Vendor Claim / RMA Number
Enter the vendor-issued return merchandise authorization or claim reference number if available.
- Vendor Representative Contact Name
-
Scheduled Return / Shipment Date
Date the damaged unit is scheduled to be returned to the vendor or DC.
- Has the inventory system been updated to reflect this write-off?
Review and Authorization
This section creates the approval trail that shows the write-off was reviewed, documented, and authorized before the inventory change was finalized.
- Additional Notes
-
Supporting Documents
Attach any related documents such as vendor invoices, delivery receipts, or incident reports.
- Approving Supervisor Name
-
Supervisor Signature
Supervisor signature confirms the damage assessment, disposition decision, and inventory adjustment are accurate and authorized.
- Approval Date
How to use this template
- 1. Set up the form with your store locations, department sections, and approved disposition options so reporters can choose from controlled fields instead of free text.
- 2. Enter the discovery details immediately, including report_date, discovery_date, reported_by, employee_id, store_location, and department_section.
- 3. Record the product information exactly as it appears in your inventory system, including brand_name, product_name, shade_variant, sku_upc, tester_unit_type, quantity_damaged, and retail_unit_value.
- 4. Document the damage with a specific damage_type, a clear damage_cause, a short damage_description, and photos if your process allows image upload.
- 5. Select the disposition_action, note any vendor claim details, and confirm inventory_adjustment_completed after the write-off or return is processed.
- 6. Route the entry to a supervisor for review, attach supporting_documents, and capture the supervisor_signature and approval date before closing the log.
Best practices
- Use a date picker for report_date and discovery_date so the log stays consistent and easy to audit.
- Keep quantity_damaged as a numeric field and require the total_write_off_value to match the unit value multiplied by the damaged quantity.
- Use progressive disclosure for damage_cause_other and disposition_other_detail so extra text only appears when the selected option needs it.
- Attach photos at the time of discovery, not after the item has been moved or discarded.
- Mark arrived_damaged separately from in-store breakage so vendor responsibility is easier to determine.
- Limit the form to the minimum necessary fields and avoid collecting unrelated PII beyond what is needed for accountability.
- Require supervisor approval before inventory_adjustment_completed is checked off to prevent premature write-offs.
- Standardize damage_type and disposition_action values across stores so reporting and vendor claims stay comparable.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this log used for?
Use this log to record broken, damaged, or unsellable cosmetic tester units and document what happened to them. It captures the product details, damage cause, photos, and whether the item was returned to the vendor or destroyed. That makes inventory adjustments and credit requests easier to reconcile later.
Who should complete the form?
The person who discovers the damage should usually start the entry, and a supervisor should review and authorize it. In many stores, a floor associate, beauty advisor, stockroom lead, or manager may report the issue, but the final approval should come from the role responsible for inventory control. Keep the reported_by and employee_id fields consistent with your internal process.
How often should this be filled out?
Complete it as soon as the damage is discovered, not at the end of the week. Immediate entry helps preserve the condition details, supports accurate inventory counts, and makes it easier to attach photos and vendor documentation. If multiple testers are damaged in one incident, record each SKU or unit line clearly.
Does this template support vendor credit claims?
Yes. The disposition and vendor claim section is designed to capture whether a claim was initiated, the claim number, vendor contact, and return shipment date. That gives accounting or operations a clean audit trail when requesting credit or replacement from the vendor. If your vendor requires extra documentation, add it in supporting_documents.
What should I do if the tester arrived damaged?
Mark arrived_damaged and document the issue separately from in-store breakage. That distinction matters because it may affect whether the vendor, carrier, or store is responsible. Include photos, the receiving date if relevant, and any packaging notes so the claim is easier to validate.
Can this be customized for different store formats?
Yes. You can rename department_section, add fields for counter, gondola, or backroom location, or adjust disposition options to match your workflow. If your stores use different tester types, keep tester_unit_type as a controlled field so reporting stays consistent across locations.
What integrations work well with this log?
This log pairs well with inventory systems, vendor claim trackers, and document storage for photos and receipts. If your workflow supports automation, you can route supervisor approval to a task queue and trigger an inventory adjustment after review. Keep the form fields aligned with the identifiers used in your POS or ERP system.
What are the most common mistakes when using it?
Common mistakes include leaving out the SKU/UPC, using vague damage descriptions, and skipping photos or disposition details. Another frequent issue is recording the write-off before the supervisor reviews it, which can create inventory mismatches. Make sure the total_write_off_value matches the quantity and unit value entered.
How does this compare to ad-hoc email reporting?
A structured log is easier to search, audit, and reconcile than scattered emails or chat messages. It standardizes the fields needed for inventory adjustment, vendor follow-up, and approval, which reduces back-and-forth when someone needs proof of the loss. It also helps different stores report damage in the same format.
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 —...
-
Manual HR data entry costs $4.78 per entry and introduces bias into pay decisions. Learn how automating performance data creates fairer, more accurate...
-
MangoApps refreshes its brand and logo to power AI-first frontline work with a unified workforce platform that keeps teams aligned daily
-
See how the Kansas City Chiefs unified communication for 600+ event staff with a branded app, achieving 90% adoption and reaching every employee on game day.
-
Discover how continuous feedback, dynamic goal-setting, and psychological safety replace annual review dread with a no-surprise performance culture that...
Ready to use this template?
Get started with MangoApps and use Cosmetics Tester Damage and Breakage Write-Off Log with your team — pricing built for small business.
