Skip to content

Canning Log: A Batch Record for the Jars You Sell

A canning log for small producers: what to record for every batch of pickles, salsa or sauce, what 21 CFR 114.100 asks of acidified foods, and an Excel file.

By Koa Sterling. Product specialist at TaroStack and small business owner. Yes, I am a real human, and I actually sit in front of a computer and write these articles. Reviewed November 19, 2026 · 6 min read

A canning log has one row for each batch: the date, the product, a lot code that's also on the jars, how many jars, the process they got, and whether the seals held. If you sell acidified foods, such as pickles, salsa or most hot sauces, federal rule 21 CFR 114.100 adds to that list: the pH and other critical factors for each batch, with the product code, date and container size; a separate record of every departure from your scheduled process and what you did about it; and where each lot was first shipped. Those records are kept three years. Below is a log that covers both, a week of batches with one that failed, and the file.

The short version

  • One row a batch, written the day it's made.
  • The lot code on the row is the code on the jar.
  • Record the pH you measured and the limit it had to meet, side by side.
  • A batch that misses is held, and what happened next is written down.
  • Keep where each lot went, and keep it all three years.
  • TaroStack gives every batch its lot code and remembers which customers got it. More below.

What to record

Column Why
Date, product, lot code Ties a jar on a shelf to this row
Container size and count A recall is counted in jars
Scheduled process Which written process this batch followed
Equilibrium pH, and the highest allowed The control that keeps the food safe
Fill temperature, and the lowest allowed The other critical factor in a hot-fill process
Process or hold time As the scheduled process states
Seals checked A jar that didn't seal isn't shelf-stable
pH meter calibrated A reading is only as good as the meter
Who Somebody saw it

The limits come from your own scheduled process, the written process for that product from a process authority. This article is about the records, not about setting the process.

What the rule asks of acidified foods

21 CFR 114.100 In plain words
(a) Records of examinations of raw materials, packaging and finished products, and suppliers' guarantees
(b) Production records showing each batch followed the scheduled process: pH and other critical factors, with product code, date, container size and product
(c) Every departure from the scheduled process noted, the affected product identified, kept in a separate file with the action taken and what became of the product
(d) Records identifying initial distribution, so specific lots can be found
(e) (b), (c) and (d) kept 3 years from the date of manufacture

Section 114.80 sets the number underneath all of it: a finished equilibrium pH of 4.6 or lower. When the finished pH is above 4.0, it has to be measured with a pH meter, not paper strips. How to take the reading is in pH testing for acidified foods, and whether your product counts as acidified in acid food vs acidified food.

A week of batches

A made-up maker of salsa, pickles and hot sauce. Each product's limits are its own.

Date Product Lot Jars pH Allowed pH check Fill temp Lowest Temp check
Nov 9 Roasted tomato salsa, 16 oz RS-1109 288 3.9 4.2 OK 186°F 180°F OK
Nov 10 Bread and butter pickles, 16 oz BP-1110 240 3.6 4.0 OK 182°F 180°F OK
Nov 11 Hot sauce, 5 oz HS-1111 600 3.4 4.0 OK 190°F 180°F OK
Nov 12 Roasted tomato salsa, 16 oz RS-1112 276 4.3 4.2 HOLD 184°F 180°F OK

Thursday's salsa read 4.3 against a limit of 4.2. It's under 4.6, and it still failed, because the scheduled process is the standard the batch has to meet.

The departure

Number, date, lot D-014, Nov 12, RS-1112
What departed Equilibrium pH 4.3; the scheduled process allows 4.2 at most
Product affected All 276 jars
Action taken Held apart and tagged. Process authority called Nov 13
What became of it Destroyed Nov 14 on the process authority's advice
Cause Tomatoes weighed over; vinegar not adjusted

That's a complete departure record: what, how much, what was done, and where the product ended up. It goes on its own sheet so the departures can be read together.

State rules differ on who may sell canned goods and from what kitchen: see can you sell salsa from home. This is general information, not legal advice.

Get the log

Download the canning log. A batch sheet where the two checks say OK or HOLD, a departures sheet, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. The steps the log sits beside are in salsa production process and pickle production process.

Where this stops working

The log proves each batch was made right. It doesn't say where the jars went. Paragraph (d) asks for that, and it lives in a different place: invoices, a market cash box, a delivery notebook. When RS-1109 has to be found, someone matches two sets of paper by date and hopes the dates line up.

How TaroStack does it

TaroStack keeps the batch and where it went in one record.

Each batch gets a lot. Record a batch and the jars go into stock under their lot code, with a best-by date. Lot labels print with both.

Your checks are fields on the batch. pH, fill temperature, seal check, calibration and initials go on the batch-record form, with sign-off.

The ingredients' lots are noted automatically. Which tomatoes, which vinegar, which lids.

A held batch stays held. Put a batch on hold and it's out of what you can sell until someone releases it.

Orders record the lot shipped. So the recall report lists which customers got RS-1109 and how many jars are still on your own shelves.

The job Log and invoices In TaroStack
Lot code on the jar Hand-written or stamped On the lot and its label
pH and temperature The log sheet Fields on the batch record
A failed batch Tagged on a shelf On hold
Where a lot went Match invoices by date The recall report

TaroStack doesn't write your scheduled process or judge a pH reading. 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.

Questions people also ask

What should a canning log include?

The date, product, lot code, container size and count, the process used, the pH and temperature readings with their limits, a seal check, and who made the batch.

How long do acidified food records have to be kept?

Three years from the date of manufacture, under 21 CFR 114.100(e).

What pH do canned acidified foods need?

A finished equilibrium pH of 4.6 or lower under 21 CFR 114.80. Your scheduled process may set a lower limit, and that's the one your batch has to meet.

Sources

  1. 21 CFR 114.100: acidified foods, records (pH and other critical factors with product code, date, container size and product; departures in a separate file; initial distribution; kept 3 years) · read November 19, 2026
  2. 21 CFR 114.80(a): acidified foods, processes and controls (finished equilibrium pH 4.6 or lower; a potentiometric method when the pH is above 4.0) · read November 19, 2026

We use AI to help with the research for these articles. Every one is read, checked against its sources and edited by Koa before it's published. Spot a mistake? Tell us and we'll fix it and say so. How we write these.

Let’s get your stack in order.

Get TaroStack

Sign up now for your free 14 day trial. No credit card required.