Back to blog
Compliance

How to Set Up One-Click Lot Recalls

November 20, 2026

To set up one-click lot recalls, you need a system that already links every lot from the receiving dock, through each batch it went into, to every shipment that left the building. When those links exist, one action on the bad lot can show every affected lot and customer, hold the stock that is still on hand, and save a record of what you did.

The click is the easy part. The work is in the records underneath it. This guide explains what has to be true before a recall can be fast, how to find every affected lot and shipment, how to hold everything at once, what goes into the notice, and what to keep for the audit trail. It is written for operations and quality leads at small manufacturers, co-packers, and food, supplement, and CPG plants.

What “one-click” really means

When a vendor says “one-click recall,” it means the system can answer three questions from one starting point: where did this lot go, what is still here, and who received it. The system can only answer those questions if someone recorded the right facts at each step, at the time the step happened.

A recall search does not create information. It follows links that already exist. If a lot number was never written down at the dock, no software can find it later. If an operator consumed “some whey” into a batch without scanning which lot, the trace stops at that batch. If a shipment record names the product but not the lot, you have to call every customer who bought that product.

So the honest answer is this: one-click recall is the payoff of a hundred small, boring steps done right. The sections below cover those steps in order.

The four records a fast recall depends on

A fast recall needs four kinds of records, and each one must connect to the next.

  • The lot at receiving. Every incoming container gets a lot number, the supplier’s lot if there is one, a quantity, an expiration date where it applies, and a location. Our guide to warehouse receiving best practices covers how to make this reliable at the dock.
  • Lots consumed into batches. Each batch record must list which input lots it used and how much of each. A batch that lists only SKUs breaks the chain.
  • Finished lots on shipments. Each finished lot gets its own lot number, and each shipment record must say which finished lots and how much of each went to which customer.
  • Current customer contacts. The trace tells you which customers got the product. It does not tell you who at that company handles quality, or whether that person still works there.

The first three records are the trace. The fourth is what turns the trace into action. Most recalls that go badly fail at one of these four points, not at the software.

Physical labels help a lot here. When every pallet or case carries its own ID that is tied to one lot, the scan at each step records the lot for you. Our explainer on what a license plate number is shows why one lot per label keeps the records clean.

Step 1: Find every affected lot and shipment

A real recall usually starts with a phone call or an email. A supplier says an ingredient lot may be contaminated. A customer reports a defect. Your own lab finds a problem in a retained sample. In each case you start from one lot and work outward.

If the bad lot is an ingredient, trace forward. Find every batch that consumed it, every finished lot those batches made, and every shipment that carried those finished lots. If the bad lot is a finished good, trace backward first to find the inputs, in case the cause is an ingredient that also went into other products. Then trace forward from that ingredient.

As you trace, sort what you find into three groups.

  • Stock still on hand, with its location and quantity.
  • Stock that is in flight: reserved for an order, staged, or waiting on a pending shipment.
  • Stock that has shipped, with the customer, the shipment, the date, and the quantity.

The in-flight group is the one teams forget. A pallet that is staged at the dock is not on the shelf, but it has not left either. If you miss it, it ships an hour after you decide to recall.

Be conservative. If a downstream lot was blended from several batches and only one of them used the bad ingredient, treat the whole downstream lot as affected until you can prove otherwise. It is better to hold too much for a day than to ship one bad case.

If you have never done this under a clock, practice first. Our guide on how to run a mock recall walks through a full practice run and how to score it.

Step 2: Hold everything at once

Once you know which lots are affected, stop them from moving. A hold should do three things.

  1. Block the lot from being shipped.
  2. Block the lot from being consumed into new batches.
  3. Show clearly, on every screen and label, that the stock is held and why.

The hold must be by lot, not by location. Affected stock is often spread across racks, staging lanes, and production areas. A hold that only covers one quarantine cage misses the pallet that is already at the line.

Speed matters here more than anywhere else. If your process is to walk the floor and tag each pallet by hand, every minute between the decision and the last tag is a minute when someone can pull the wrong pallet. A bulk hold in the system, applied to every affected lot at once, closes that window. Walk the floor afterward to tag the stock and confirm counts, but let the system hold first.

Write down the reason for the hold and who placed it. You will need both later, and you will not remember the details in three months.

Step 3: Prepare and send the notice

The trace gives you a list of customers. The notice is how you reach them. A good recall notice is short and specific.

  • The product name and SKU, as the customer knows it.
  • The affected lot numbers, and how to find them on the label.
  • The quantity you shipped to that customer, with the shipment dates.
  • What you want the customer to do: stop using it, hold it, return it, or destroy it.
  • Who to contact with questions, with a direct phone number and email.

Draft a template before you ever need one, and have your quality lead and anyone who handles legal questions approve it in advance. During a recall, you should only be filling in blanks.

Then check the contact list. For each customer on the trace, confirm you have a current name, phone number, and email for the person who handles recalls or quality. Send the notice, record when each one went out, and record when each customer confirmed receipt. Follow up with anyone who does not answer within the time you set.

If you handle foods on FDA’s Food Traceability List, a recall may also come with a records request. Our FSMA 204 traceability page explains the records involved and how a sortable spreadsheet fits in.

Step 4: Keep an audit record

When the event is over, you need to show what you did and when. Customers, auditors, and regulators may ask. Your own team will want to learn from it.

A useful recall record includes:

  • The source lot and how the problem was found.
  • Every affected lot, with the quantity on hand at the time of the hold.
  • Every shipment and customer, with quantities.
  • When each hold was placed, by whom, and for what reason.
  • When each notice was sent and when each customer confirmed.
  • What happened to the held stock: released, reworked, returned, or destroyed.

The best audit record is one the system writes for you as you work, rather than one someone reconstructs from emails a week later. Keep it with your other quality records, next to your certificates of analysis and batch records for the affected lots.

How this works in Swift WMS

Swift WMS has a Recall Impact tool on the Core plan. It is part of the Quality features, along with Lot Trace and Batch Genealogy. Here is what it does, and where its limits are.

You open Recall Impact from one lot. It is on the Quality page, in the lot details, and in the license plate actions. It walks forward from that lot and shows three lists: the downstream lots, with what is still on hand; the in-flight work, such as open orders and pending shipments that use those lots; and the shipped destinations, with the customer, the document number, the lot, the license plate, the quantity, and the date. It also shows a count of customers, documents, and total quantity shipped.

Downstream lots include every license plate on those lots, so a lot that was blended from other batches is still listed. That is conservative on purpose. If the trace is very deep, the tool warns you that it stopped at its depth limit, so you know to check further.

From the same screen, you choose which lots to hold, pick a hold reason, add notes, and hold them all at once. Every affected lot is selected by default. A lot hold blocks shipping and consumption of that lot, and the tool tells you which open orders and pending shipments the hold now stops. Holds must be turned on in your company settings, and the user needs permission to place lot holds.

When you place the holds, Swift saves a recall audit record. It stores the source lot, the reason, the notes, who ran it, and the result for each lot. You can download a recall CSV with the shipped and in-flight rows, and use it as the customer list for your notice. For lots marked as Food Traceability List items, Recall Impact also offers a sortable FDA spreadsheet, which supports FSMA 204 recordkeeping.

Two related tools fill in the rest. Lot Trace shows the license plates a lot went into and where they shipped, with a CSV export. Batch Genealogy follows a batch from receiving through ingredients, work in progress, finished goods, and shipment, and exports it as a PDF report.

Here is what Swift does not do. It does not write or send the recall notice for you, and it does not keep a separate recall contact list for your customers. You use the shipped list to send notices through your own email and phone process. And like any system, it can only trace what was recorded. If lots were not captured at receiving, or a batch was made without recording which lots it consumed, Recall Impact cannot fill that gap. The one click works because the receiving, production, and shipping steps captured the lot every time.

The takeaway

A one-click recall is real, but the click is the last step, not the first. Set it up in this order.

  • Capture the lot on every container at receiving.
  • Record which lots each batch consumed, and give every finished lot its own number.
  • Record finished lots on every shipment.
  • Keep customer recall contacts current, and check them on a schedule.
  • Use a bulk hold by lot, not a walk with a roll of tags.
  • Draft the notice template now, and save an audit record of every recall.
  • Practice with a mock recall, and fix what it finds.

To see how Lot Trace, Batch Genealogy, holds, and Recall Impact fit together, visit the lot traceability and recall impact page.

How Swift WMS does itLot traceability and recall impact