A spice blender grinds, mixes and packs. Nothing in that kills bacteria, and spices are dried in fields and yards, so Salmonella can arrive in the sack and stay alive in a dry jar for a year. The customer then shakes it onto food that's already cooked. That makes a spice blender's plan a plan about suppliers. Under FDA's preventive controls rule, a hazard that your supplier controls for you is managed by a supply-chain program: approved suppliers, a check on every lot, and verification that the checks mean something. Around that sit a sieve and magnet, dry cleaning, and allergens in the blends. Below are the hazards, the points, a week's log, and a worksheet.
The short version
- You have no kill step. Buy spices that have had one, and get it in writing.
- A certificate of analysis for every lot, matched to the lot on the sack.
- Verify: test some lots yourself, and review your supplier's records or audit.
- Sieve and magnet every lot. Clean dry: water in a spice room feeds what you're keeping out.
- Sesame, mustard, wheat and soy turn up in blends. A major allergen is declared by name.
- TaroStack records which supplier lot went into which blend. More below.
The hazards
| Hazard | Where it comes from | Why the blender has to deal with it |
|---|---|---|
| Salmonella and other pathogens | Field drying, handling, storage at origin | They survive for months in dry spice, and the spice often isn't cooked again |
| Stones, wire, glass, insects | Harvest, drying yards, sacks | Grinding makes them small, not gone |
| Undeclared allergens | Sesame, mustard, wheat flour or soy in blends; shared grinders | Many similar jars, one line |
| Mold and its toxins | Spice dried slowly or stored damp | Only the supplier's handling and testing can show it |
| Lead and illegal dyes | Adulteration at origin in some spices | Only supplier control and testing can show it |
The supply-chain program
FDA's rule lists what the program includes. In a spice room it looks like this.
| The rule asks for | What the blender does |
|---|---|
| Approved suppliers | A list. Nothing is bought from anyone who isn't on it. Each supplier's file says who applies the pathogen treatment |
| Verification activities, chosen for the risk | A certificate for every lot; your own lab test on a share of lots; the supplier's audit report or food safety records reviewed each year |
| Documentation | The certificates, your test results and the reviews, filed by lot and supplier |
| Prompt action | A supplier whose lot fails is stopped until the cause is known |
Treatment. Spices are made safe by steam, by ethylene oxide or by irradiation, and each leaves the spice a little different. Ask every supplier which treatment each spice has had, and whether the certificate's Salmonella result is from after it. "Untreated" spice needs a treatment before you pack it, by you or by a service that does it for you. A written program is in supplier approval program template.
Your own testing. A certificate is the supplier's word. FDA's rule expects product testing, where you use it, to follow a written procedure: which organism, how samples are taken and how many, which method, which laboratory, and what happens on a positive. Testing one lot in ten at an outside lab is one place to start. Keeping the paperwork straight is in certificate of analysis tracking.
The control points
A made-up blender packing single spices and blends. Its limits are its own.
| CCP | Limit | Checked | If it's missed |
|---|---|---|---|
| 1 Supplier and receiving | Approved supplier; certificate for the lot showing treatment and a negative Salmonella result | Certificate matched to the sack's lot, each lot | Held; never opened |
| 2 Sieve and magnet | Every lot sieved and passed over the magnet | In place and intact, each lot; finds written down | Everything since the last check goes through again |
| 3 Allergen changeover | Blends with an allergen run last; grinder and filler dry-cleaned and inspected after | Each changeover, signed | Next product held until the clean is redone |
| 4 Label | Each jar carries its own blend's label, allergens declared | First and last jar of each run | Held and relabeled |
Clean dry. Vacuum, brush and wipe. Water left in a grinder or a floor crack gives Salmonella what the dry spice denied it. Where wet cleaning can't be avoided, dry the equipment completely before it runs.
A week's log
| Day | What | Check | Result | OK? |
|---|---|---|---|---|
| Mon | Paprika, lot PK-4471 | Certificate on file | Yes: steam treated, Salmonella negative | Yes |
| Mon | Cumin, lot CU-2290 | Certificate on file | No certificate with the delivery | NO: act |
| Tue | Paprika PK-4471 | Sieve and magnet | Intact; two wire fragments on the magnet | Yes |
| Wed | Everything bagel blend (sesame) | Changeover clean after the run | Signed | Yes |
| Fri | Black pepper, lot BP-0915 | Outside lab, Salmonella | Negative | Yes |
Monday's cumin came without its certificate. The sacks went on hold, unopened. The certificate arrived on Wednesday, showed the lot and a negative result after steam treatment, and the cumin was released. The wire on Tuesday's magnet was written in the finds log and reported to the paprika supplier.
This is general information, not legal advice. A blender of dried herbs and tea faces the same problem: see HACCP plan for tea. Allergens are in allergen control plan template, and stock in spice inventory list.
Get the worksheet
Download the spice HACCP worksheet. Three sheets and a read-me: the hazard analysis from approving suppliers to labeling, the plan with its four control points, and a monitoring log. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A supplier recalls paprika lot PK-4471 for Salmonella. Paprika is in eleven of the blender's forty blends. Which jars got that lot and which got the lot before it? If the blend sheets say "paprika, 3 kg", all eleven blends, every jar, every store, come back.
How TaroStack does it
TaroStack records the lot, not just the spice.
Receiving records the supplier's lot for each sack. A lot waiting for its certificate can sit on hold, kept out of what you can use or sell.
Each blend is a batch. It notes which lots it consumed, automatically: PK-4471 is on the records of the blends that used it and no others.
Your checks are fields on the batch record: sieved, magnet clean, changeover signed, label checked.
Allergens on Growth. With allergen tracking on, a batch can't start if its label leaves out an allergen its ingredients contain.
One report for a recall: which blends used the lot, which stores got those jars, and what's still on your shelf. Starting a recall holds the rest.
| The recall | Blend sheets | In TaroStack |
|---|---|---|
| Which blends used PK-4471 | All eleven, to be safe | The ones that did |
| Which jars | Every jar of eleven blends | Those batches' lots |
| Which stores | Invoices | One report |
| A sack with no certificate | Easy to open by mistake | On hold |
TaroStack doesn't test for Salmonella or approve suppliers. Recipes, batches, lots and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes, with allergen tracking). 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.
