Beauty Product Shoplifting Incident Report
Record a beauty product shoplifting incident in one place, including what was taken, who was involved, evidence, and police follow-up. Use it to create a clear incident record without over-collecting unnecessary PII.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Beauty Retail · Cosmetics Stores · Drugstores · Department Stores
Overview
This Beauty Product Shoplifting Incident Report template captures the core facts of a retail theft event in a structured format: when and where it happened, what items were lost, how much inventory was affected, what the suspect looked like, what evidence exists, and whether police were contacted.
Use it after a suspected or confirmed shoplifting incident in a beauty retail setting, especially when staff need a consistent record for loss prevention, store management, insurance, or law enforcement follow-up. The template is also useful when the incident is only partially observed and you need to preserve details before memories fade. The submission notice section makes it clear what happens after submit, whether the report is internal or shared, and whether anonymous submission is allowed.
Do not use this form as a general customer complaint form, a workplace injury report, or a broad security log for unrelated events. It is intentionally focused on one incident type so the fields stay relevant and the report stays usable. If no items were taken and there is no theft suspicion, a simpler store observation note may be a better fit. If the event includes a threat, injury, or a detained suspect, pair this report with the appropriate safety, HR, or legal process rather than forcing everything into one form.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the incident details, evidence, and contact information needed for follow-up.
- If the report is used in a public-facing or employee-facing interface, make the fields accessible under WCAG 2.1 AA with clear labels, validation, and keyboard-friendly controls.
- Use anonymous submission when your internal reporting policy allows it, especially for staff who may be reluctant to identify themselves in a sensitive loss-prevention case.
- Avoid collecting unnecessary PII in suspect or witness fields, and document any consent or disclosure language if personal data is retained in an audit trail.
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
Submission Notice
This section tells the reporter what happens after submit, whether the report is internal or shared, and whether anonymous submission is allowed.
-
What happens after I submit?
This report is sent to the store manager or loss prevention reviewer for audit trail and follow-up. If police are contacted, the police report number can be added later.
- Submission type
-
Submit anonymously
Use this if you need to report discreetly. Anonymous submissions may limit follow-up questions.
Incident Overview
This section anchors the timeline and location so the rest of the report can be reviewed against a clear incident record.
- Date of incident
- Approximate time of incident
- Store location
- Area where the incident occurred
-
Brief incident summary
Describe what was observed in 2-5 sentences. Include only observable facts.
Items and Loss Details
This section documents what was taken and the estimated loss so the report can support inventory and shrink follow-up.
- Items lost
- Total estimated value lost
- Inventory status
Suspect Description
This section captures only observable suspect details, which makes the report more useful without over-collecting unnecessary information.
- Number of suspects
-
Suspect description
Include observable details such as approximate age range, clothing, height, build, and distinguishing features.
- Direction of travel after incident
- Vehicle observed?
- Vehicle details
Evidence and Witnesses
This section links the report to video, images, and witness accounts so the incident can be verified later.
-
Video clip reference
Enter the camera ID, clip ID, or file reference for the relevant footage.
- Photo or image upload
- Were witnesses present?
- Witness notes
Police and Follow-Up
This section records whether police were contacted and what internal actions still need to happen after the report is submitted.
- Police report filed?
- Police report number
- Internal follow-up actions
How to use this template
- Start by setting the submission notice so reporters know whether the form creates an internal record, triggers a manager review, and allows anonymous submission.
- Enter the incident date, time, store location, incident area, and a concise summary of what happened before adding any supporting details.
- List the items lost, the total estimated value, and the inventory status so the report can be used for shrink reconciliation and follow-up.
- Describe the suspect using observable facts, then use the vehicle fields only if a vehicle was actually seen and relevant to the incident.
- Attach video clip references, photo uploads, and witness notes, then record whether a police report was filed and what internal follow-up actions are needed.
- Review the completed report for missing fields, unclear wording, or unnecessary PII before submitting it into your audit trail.
Best practices
- Record the incident as soon as practical after the event so the timeline, suspect description, and evidence references stay accurate.
- Use conditional logic to show vehicle details only when a vehicle was observed, and keep the rest of the form focused on the actual incident.
- Capture item names, quantities, and product categories in the same format your inventory system uses so reconciliation is easier later.
- Write the incident summary in plain language and stick to observable facts rather than guesses about intent or identity.
- Reference the exact camera clip, time range, or file name for video evidence so another person can retrieve it without searching through unrelated footage.
- Collect only the PII needed for the report and avoid adding unrelated customer details, especially when the incident can be documented without them.
- Add witness notes separately for each person when accounts differ, instead of merging conflicting statements into one paragraph.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this incident report be used?
Use it any time a suspected shoplifting event involves beauty products, whether the loss is confirmed on the spot or discovered during a later inventory check. It is designed for single incidents, not ongoing shrink tracking. If the event includes assault, threats, or a medical issue, add the appropriate safety or injury form alongside this report.
Who should complete the report?
A store manager, shift lead, loss prevention associate, or employee who witnessed the event can complete it. The best practice is to have the person with the clearest timeline and evidence references fill in the incident details first, then have a manager review the follow-up actions. If multiple people observed different parts of the event, use witness notes to capture each account separately.
Does this template support anonymous submission?
Yes, the submission section includes an anonymous submission option for cases where the reporter should not be identified. That can be useful for internal reporting or when staff are uncomfortable naming themselves in a sensitive incident. If your process requires contact follow-up, make that clear before the form is submitted so the reporter understands what information will be shared.
What evidence should be attached?
Attach the most relevant video clip reference, photo or image upload, and witness notes that support the incident timeline. Keep the evidence fields focused on what helps verify the event and identify the items lost, rather than collecting unrelated footage. If your store uses a camera system, include the camera location or clip time range in the reference field so the footage can be retrieved quickly.
How detailed should the suspect description be?
Capture observable details only, such as approximate height, clothing, direction of travel, and whether a vehicle was observed. Avoid assumptions about identity or protected characteristics that are not necessary for the report. The conditional fields for vehicle details help you document a plate, make, model, or color only when a vehicle was actually seen.
Should every field be required?
No. This template works best when required fields are limited to the essentials, such as incident date, location, and a short summary, while evidence and witness fields remain optional unless available. That aligns with data minimization and helps staff complete the report quickly during a busy shift. Use conditional logic so extra fields appear only when they apply.
How does this compare with a free-text incident note?
A structured template is easier to review, search, and hand off than an ad-hoc note because it separates the incident timeline, loss details, suspect description, evidence, and police follow-up. It also reduces missing information by prompting the reporter for the fields that matter most. Free-text notes can still be attached in the incident summary or witness notes if you need narrative context.
Can this template integrate with other store workflows?
Yes, the report can feed into loss prevention, inventory reconciliation, and police follow-up workflows. Many teams connect it to ticketing, email notifications, or an audit trail so managers can track internal actions after submission. If you use a separate inventory system, keep the item fields aligned with your product naming and SKU conventions.
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
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
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.
Ready to use this template?
Get started with MangoApps and use Beauty Product Shoplifting Incident Report with your team — pricing built for small business.
