A cosmetics recall plan is a page or two that says who decides, what triggers a review, how a batch code leads to the people who bought it, how you stop sales, how you tell customers and stockists, and what you do with what comes back. Since the Modernization of Cosmetics Regulation Act, FDA can order a cosmetics recall: if it finds a reasonable probability that a cosmetic is adulterated or misbranded and that using it will cause serious adverse health consequences or death, it gives the responsible person the chance to stop distribution and recall voluntarily, and can order it if they don't. A small maker's plan is about never getting to that second step. Here's a template with eight parts.
The short version
- Put a batch code on every unit. Without one, a recall means everything you've ever sold.
- Keep, for each batch, what went in (ingredient lots) and who received it.
- Decide now who can stop sales, and who calls stockists.
- Write the customer notice before you need it.
- TaroStack links each batch to its ingredient lots and its customers, and runs the notices. More below.
The eight parts
| Part | What it says | Example: a small skincare maker |
|---|---|---|
| Who decides | Who can start a recall, and a backup | The owner; backup, the production lead |
| What starts one | Findings that trigger a review | Two or more similar reactions to one batch; mold or separation in retained samples; a supplier notice naming a lot you used |
| Finding the product | How a code leads to ingredients and buyers | Batch code on every jar. The batch record lists ingredient lots; orders and invoices list the batch shipped |
| Stopping it | Hold stock, take listings down, tell stockists | Jars to a quarantine shelf marked HOLD; product page set to unavailable; stockists phoned |
| Telling people | Customers, stockists, the public if needed | Email to everyone who bought the batch, with what to do; a letter to stockists; a notice on the site |
| FDA | Reports and orders | The responsible person reports serious adverse events as the law requires and keeps records of all reports |
| Getting it back | Returns, refunds, disposal | Prepaid return or a photo of the destroyed jar; refund either way; returns counted and destroyed |
| Closing it | Count, cause, change | A one-page report: units made, sold, returned; the cause; what changed |
What triggers a review
Most cosmetics problems show up one of three ways.
Complaints that rhyme. One customer with a rash is a note in the file. Two with the same reaction to the same batch is a reason to pull a retained sample and look.
The product changes. Separation, a new smell, visible growth. Water-based products without a working preservative are the usual suspects, which is why each batch's pH and preservative lot belong on its record: see lotion making log sheet.
A supplier calls. An ingredient lot is contaminated or mislabeled, and you have to say which of your batches used it.
Keep a jar from every batch until its shelf life has passed. It's the only way to check a complaint against the batch itself.
The notice
FDA's guidance on recall communications is written for all the products it regulates, and it's a good checklist for a customer email: be brief; identify the product, size and lot or batch code clearly; explain the reason and the hazard; say exactly what to do with the product; and give an easy way to reply. No promotion, nothing that distracts. Follow up with anyone who doesn't answer.
This is general information, not legal advice. What MoCRA asks of small businesses, including which are exempt from some of its requirements, is in MoCRA for small businesses.
Get the template
Download the cosmetics recall plan. Two sheets and a read-me: the plan, with a place for your answers beside the example, and a contact list for stockists and suppliers. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. A batch record to go with it is in cosmetic batch record template.
Where this stops working
The plan says "the batch record lists each ingredient lot, and orders list the batch shipped." For a maker selling through a website, two markets and five stockists, that second half is the weak one. Online orders say "1 × body butter", not which batch was on the shelf that day.
How TaroStack does it
TaroStack records the batch on the way in and on the way out.
Batches note their lots. Record a batch and the ingredients come off stock; the batch record notes which lot of each was used, automatically, with your own fields for pH and checks.
Orders take a lot. Each sale or wholesale order records the lot it shipped, oldest first by default.
One recall, one click. Starting a recall holds every affected lot in stock and gives the recall a number. Each customer gets a notice of their own from your mailbox, naming what they received, and the recall keeps who answered.
The report. It names your two recall contacts, lists each customer and supplier with where to find them, and downloads as one CSV.
Selling online. Connect your Shopify store, and we set it up with you.
| The plan needs | By hand | In TaroStack |
|---|---|---|
| Ingredient lots for a batch | Written on the batch sheet | Recorded with the batch |
| Who bought the batch | Guess from dates | The lot on each order |
| Stock stopped | A sign on the shelf | Held when the recall starts |
| Customers told | A mail merge | A notice each, tracked |
Lots, batches and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
