Product Recall Plan for a Shopify Brand: Run It as an SOP

A product recall plan only holds up if it is a live SOP tied to the lot and batch records in your actual stack. Write it as numbered steps. Give each step an owner by role. Then re-check it every quarter against the screens your team really uses.

The binder version fails for a plain reason. Apps change, the 3PL changes, and staff change. Nobody opens a recall document until the day a customer gets hurt. By then the screenshots show an admin that no longer exists, and the person named on page one left in March.

What is a product recall plan, and what makes one work?

A product recall plan is the written procedure a company follows to find, stop and correct a product it has already sold.

Two things have to exist before any of that works. You need a lot code that identifies each batch, and distribution records that show where it went. Both are data problems, not writing problems.

So the useful test of a recall plan is not whether it reads well. It is whether someone who has never run a recall can open it, follow step one, and find the data step one asks for. That is an SOP standard, not a policy standard.

FDA's recall guidance in 21 CFR 7.59 suggests that firms "prepare and maintain a current written contingency plan". The word "current" is where most plans quietly fail. Current means re-checked against the live screens, not re-read in a meeting.

What has to be in the plan before you can scope a recall by lot?

Name the exact place, screen and field where the lot code lives, and write it into the plan. Shopify has no lot or batch field of its own. It does record every inventory adjustment, so you can see who changed a quantity and when. That is not the same as knowing which batch a unit came from.

So the lot code usually lives somewhere else. It might sit in your 3PL's warehouse system, in an inventory app, or in a product metafield you fill in at receiving. Pick one, and write its name into the plan.

The CPSC Recall Handbook asks for production records that hold the lot numbers and product codes for each run. It also asks for distribution records showing quantity shipped or sold, delivery dates and destinations.

If the inbound step does not capture the code, nothing downstream can scope the recall. That capture step belongs in your receiving procedure, next to the inspection photos in the product quality control checklist.

Which steps go in the plan, and who owns each one?

Six steps, each with one owner and one piece of evidence. The order is ours, built from what 21 CFR Part 7 and the CPSC handbook ask for. Neither source sets a fixed sequence, and the owner and evidence columns are our judgement calls too.

Write roles, not names. That is the same rule that makes a business continuity plan for a small Shopify store survive a resignation. Add a stand-in for any row where one person holds the only login.

How fast must you report, and who gets told first?

Fast, and the agency hears first. The CPSC handbook says a company must report to CPSC within 24 hours of getting reportable information. Its staff's standing advice is "When in doubt, report." For FDA-regulated products, a firm that pulls a product it believes breaks the rules is asked to notify FDA immediately, under 21 CFR 7.46.

Which agency covers you depends on the product. CPSC covers consumer products such as toys, clothing and home goods. Its handbook says it does not have jurisdiction over foods, drugs, cosmetics or medical devices, among others. Those sit with FDA, which matters for supplement, skincare and food brands.

The two agencies differ on who speaks to the public. Under CPSC, staff must approve every notice to media, customers and consumers. CPSC should issue the approved message first, and the company follows with its own approved version.

Under FDA, the firm notifies its own direct accounts promptly. A public warning is kept for urgent cases, and FDA ordinarily issues it in consultation with the firm. A firm that wants to issue its own warning is asked to send it to FDA for review first. FDA also lists every recall in its weekly Enforcement Report.

Write the right agency, deadline and notice order into the plan now. It is not something to work out while a defective product is still shipping.

How do you stop the recalled item from selling again?

Zeroing the inventory is not a block by itself. Shopify's setup guide says the default is "Stop selling when out of stock", where "customers can't add it to their cart". But with "Continue selling when out of stock" you "allow customers to purchase products even after the inventory reaches zero". So unpublish the product too, and remove it from any automated collection that could bring it back.

The CPSC handbook asks for controls that go past the storefront. SKUs should be blocked permanently, so employees cannot override the block. Online sales should be blocked and listings removed. Recalled stock needs a set quarantine space with a log of units in and out, plus procedures that stop returned units being restocked. The handbook also says plainly that donating recalled products is illegal, and that staff should be told so.

Then check the block from the outside. Open the product's direct link in a private browser window and try to add it to the cart. Check every sales channel the product was on, including POS and any marketplace app. A block that holds on the online store but not on one channel is not a block.

One more line for the returns desk: a recalled unit that comes back goes to quarantine, never to the shelf.

How do you prove the recall reached people?

With counted contacts and dated replies, not with a sent email. FDA's recall rules in 21 CFR Part 7 set how many consignees the checks have to reach. Level A means 100 percent of consignees are contacted. Level B is more than 10 percent and less than 100 percent, set case by case. Level C is 10 percent, Level D is 2 percent, and Level E means no checks.

Those levels are FDA's. Consumer products sit under CPSC, so check which agency covers your catalog before you borrow them.

Status reports run on the same idea. FDA asks for periodic recall status reports, generally every 2 to 4 weeks. They cover how many consignees were notified, how many responded, how much stock they held, and how many units came back or were corrected. CPSC asks for monthly progress reports through its own reporting portal.

For a Shopify brand selling direct to consumers, the reply log can be the helpdesk thread that tracks who replied and when. Give every step in the plan one visible result, written against its row with a date and the owner's name. That is the same proof standard used in this site's knowledge transfer plan template for Shopify teams.

Why does a recall plan drift, and how do you catch it each quarter?

Because every part of it points at something outside your control. The admin UI moves, the 3PL changes contacts, the helpdesk macro gets renamed, and the person who owned the quarantine log leaves. A recall plan drifts like any other SOP. It is written once and forgotten, and you notice last because you never run it.

Each quarter, do three things. First, re-record the two screens the plan depends on most: the SKU block and the lot lookup. Second, line the new recording up next to the existing SOP rather than swapping it in, and note which steps are different. Keeping both versions is what SOP version control without the overwrite is for. Third, fix only what changed.

Test the communication path too. The CPSC handbook suggests simulating a recall announcement to each facility, then asking each one to confirm receipt and its next steps. For a Shopify brand, that is one email to the 3PL and one to the support lead.

Where does this plan fail?

Four ways it fails.

First, the lot code was never captured at receiving. Then the recall cannot be scoped to a run, and you are pulling the whole SKU across every channel. That is a receiving fix, not a document fix.

Second, one person holds every login the plan depends on. If the store owner is the only admin on Shopify, the 3PL portal and the helpdesk, the plan stalls while that person is on a plane.

Third, the wrong agency is assumed. A skincare or supplement brand that writes a CPSC plan has the wrong deadlines, the wrong notice order and the wrong reports. Decide which agency covers each product line before you write step three.

Fourth, the plan is treated as legal cover. It is an operating procedure. Reporting duties, notice wording and remedies are settled with the right agency and your own counsel.

Next step

Open the plan you have and check one thing: can anyone on the team find the lot code for an order placed last month? If not, that is step one, and it belongs in the receiving procedure rather than the recall document.

Then build the six-row table. One step per row, a role in the owner column, and one piece of dated evidence each. Half a page beats a binder.

ReccordSOP is an AI SOP tool built for Shopify DTC brands. Record the screens a procedure depends on, and it turns that recording into numbered steps with a screenshot for each one. Re-record the same task later, and it lines the new recording up against the existing SOP and shows which steps changed, instead of overwriting the old version. It documents a process; it does not run the process, watch your store settings, or make decisions for you.