Spice and seasoning recalls are more common than most home cooks realize, and their consequences can be serious. The global spice supply chain — spanning dozens of countries, multiple processing steps, and complex blending operations — creates numerous points where contamination can occur. Salmonella in spices is a persistent problem worldwide, and heavy metal contamination has been found in several widely used spices at levels of concern.
Because spices are used in small quantities and stored for long periods, contaminated spice products may be in millions of households long after a recall is issued. Checking your spice cabinet against current recall notices is a simple but worthwhile step.
Step 1: Identify the product.
Note the brand name, spice name or blend name, and net weight (in ounces or grams). Many spice recalls are specific to certain sizes within a product line — for example, a 2-oz jar may be recalled while a 10-oz canister is not, or vice versa.
Step 2: Find the lot code and best-by date.
For spice jars, the lot code is typically stamped or printed on the bottom of the jar or on the lid. For packets and pouches, check the back panel or side seam. Best-by dates are usually clearly printed on the bottom or label.
Step 3: Find the UPC.
The UPC barcode on your spice container or packet is the most precise identifier for cross-referencing against specific recall notices.
Step 4: Search Recall Tracker.
Go to Recall Tracker and search by brand and spice name. Compare your lot code, best-by date, and UPC against any recall notices returned.
Step 5: Use the barcode scanner.
The barcode scanner at /scan lets you scan the UPC directly to check your specific product against the current recall database.
Step 6: Set up brand alerts.
On the brands page, follow the spice brands you use regularly to receive automatic notifications of any future recalls.
The FDA (Food and Drug Administration) has jurisdiction over spices, herbs, and seasoning blends. All commercially sold spices fall under the FDA's authority as food products. See the FDA agency page for more on FDA recall processes and enforcement authority.
The USDA may be involved if a seasoning blend contains meat or poultry as a significant ingredient, but standalone spices and herb blends are FDA-regulated.
Salmonella is by far the leading cause of spice recalls. The FDA has identified spices as one of the food categories most frequently associated with salmonella contamination — a 2013 FDA study found that approximately 7% of imported spice shipments tested positive for salmonella.
Spice contamination occurs at multiple points: in agricultural fields during harvesting and drying, during storage and transport, and during processing. Heat treatments used to reduce pathogens in spices (steam treatment, ethylene oxide treatment, irradiation) do not always achieve complete elimination, and cross-contamination can occur during blending and packaging operations.
Because spices are used in small quantities, it can be difficult to trace a salmonella outbreak back to a contaminated spice — the food vehicle is often identified only through detailed outbreak investigation. This means contaminated spice lots may be in distribution for some time before a recall is issued.
Several spices have been found to contain heavy metals — particularly lead, arsenic, and chromium — at levels that exceed safety thresholds. Lead contamination has been documented in ground cumin, chili powder, turmeric, paprika, and mixed seasoning blends. Lead can enter spices through soil contamination in agricultural regions, through intentional adulteration to increase weight, and through processing with lead-containing equipment.
The health risks of lead exposure are dose-dependent and cumulative. For children and pregnant women, there is no safe level of lead exposure — even small ongoing exposure from contaminated spices used daily in cooking can contribute meaningfully to total lead burden. The FDA and consumer advocacy organizations have flagged lead in spices as an underappreciated ongoing risk.
Spice blends, seasoning mixes, rubs, and marinades often contain multiple ingredients including milk solids, wheat flour, soy, and tree nuts. Recalls have occurred when these allergen-containing ingredients were present but not declared on the label — due to formulation changes, packaging errors, or incorrect label application.
Even "pure" single-ingredient spices may be processed on shared equipment with allergen-containing products. Recalls for undeclared allergens in spices address both labeling failures and cross-contact scenarios.
Some spice recalls have involved economically motivated adulteration — the deliberate addition of cheaper materials to bulk up weight or enhance appearance. Lead chromate has been used to intensify the yellow color of turmeric. Sudan dyes (industrial colorants that are potential carcinogens) have been found in paprika and chili powder. These adulterants are added intentionally but are harmful, and their discovery triggers recalls and import alerts.
Physical contaminants in spices — including insect fragments, rodent filth, and manufacturing debris — have resulted in recalls. Agricultural commodities like whole or ground spices are susceptible to pest contamination during storage, and FDA inspection of spice shipments has found filth contamination in a notable percentage of imported product.
Remove the recalled product from your kitchen. Take it out of your spice rack or cabinet and set it aside. Do not use the remaining quantity.
Check multiple containers. If you have purchased the same spice multiple times, check each container individually against the specific lot codes in the recall notice. Only containers with affected lot codes are recalled.
Request a refund. Keep the container with lot code, best-by date, and UPC visible. Contact the manufacturer using the recall notice contact information. Most spice recalls offer a full refund.
Monitor for symptoms if a bacterial contamination recall. Salmonella symptoms typically appear within 12–72 hours of consuming contaminated food: diarrhea, fever, abdominal cramps, nausea. Because spices are used in small amounts and combined with other foods, tracing illness to a spice can be difficult. If you develop symptoms after eating food prepared with a recalled spice, contact a healthcare provider.
For heavy metal recalls involving regular use: If you have been using a recalled spice heavily and regularly — particularly if cooking for children — consider mentioning this to a healthcare provider. Blood lead testing may be warranted for children in households where a lead-contaminated spice was used frequently over an extended period.
On most spice jars, the lot code is printed or embossed on the bottom of the jar or stamped on the lid. It may also appear on the label near the best-by date. The code can be faint or hard to read on glass jars — try tilting the jar under direct light. On spice packets and pouches, check the back panel or side seam near the bottom.
Yes. Organic certification addresses pesticide use, not bacterial contamination, heavy metals, or physical contaminants. Organic spice brands have been included in salmonella-related recalls. The recall status of a spice product is independent of its organic certification.
For salmonella recalls, past exposure to contaminated spice in cooked food (where the spice was added during cooking and the food was fully heated) carries lower risk than raw consumption, because cooking temperatures kill salmonella. For heavy metal recalls — particularly lead — past regular use is more concerning because lead exposure is cumulative. If you have been using a recalled lead-contaminated spice heavily over months or years, particularly when cooking for young children, consider discussing blood lead testing with a healthcare provider.
Bulk bin spices from grocery stores are subject to the same recall system as packaged spices, but identifying whether bulk product was sourced from a recalled lot is more difficult. The store's receiving records should identify the supplier and lot. If a recall is issued for a spice brand you know your store carries in bulk, ask the store's grocery manager whether their current stock is from an affected lot.
Search all spice and seasoning recalls to check your specific brand, and browse brands to follow your spice manufacturers for automatic alerts. See recall statistics by category for historical trends in food safety enforcement.
Yes. Spices, dried herbs, and seasoning blends are recalled every year for problems like Salmonella contamination, undeclared allergens, elevated lead levels, and other contamination issues. If you want to check a specific product fast, use RecallTracker’s barcode scanner at /scan or search a manufacturer directly at /brands.
The biggest triggers are Salmonella, undeclared allergens such as sesame, milk, or wheat, and contamination from heavy metals or foreign material. Some recalls also involve mislabeling or adulteration in imported spice products. RecallTracker’s /statistics page helps you spot which hazards show up most often across food recalls, including spice-related trends.
Start by checking the brand name, product name, package size, lot code, and best-by date against the official recall notice. A recall usually applies only to specific lots, not every product from that brand. You can speed that up by scanning the barcode at /scan or browsing the manufacturer at /brands.
Follow the recall notice exactly, but most recalled spices should not be used, even if they look and smell normal. Many notices tell consumers to discard the product or return it to the store for a refund. If you track multiple pantry products and want faster alerts and monitoring tools, RecallTracker Premium at /pricing is built for that use case.
Not necessarily. Organic, imported, specialty, and small-batch spices can all be recalled because the main risks come from sourcing, drying, handling, blending, and labeling, not just brand size. Checking /statistics can give you a better sense of recall patterns, and /brands lets you look up both major national labels and smaller specialty companies.