Print the labels your finished cases carry and export the cooking and cooling logs an auditor asks for — both straight off the production run.
On this page
Was this helpful?
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
The teriyaki bowls are cooked, packed, and stacked by the loading dock, and two
things stand between them and the truck: a label on every case with a lot number
you can trace, and the day's cooking log filed where you can hand it to an
inspector. Both come off the run itself — the labels from each batch, the logs
from the run's tabs. Open
Production runs and the
run you just finished.
Kitchen+
Print a batch label
A label prints from the
— the same screen where you weigh ingredients and record
output.
1
Open the recipe on the run
From the run's Recipes tab, select Continue on a recipe that's in
progress, or Start on one still pending. The line item opens on the batch
you're working.
2
Open the label
Print batch label — on the batch card, and on every row of the supervisor
Batch overview — prints the label for the whole batch. Label, on a
single Output entry, prints just that entry's. Either opens the label in a
new tab, headed Batch label.
3
Send it to the printer
Select Print label to hand the sticker to your browser's print dialog —
to a label printer, or to PDF.
The lot number lands after the first weighing
Open a label before anything's been weighed into the batch and the lot line
reads Pending first weighing, with no Print label button yet. Bettr
mints the lot when the first ingredient is weighed — print the label once it's
there.
What the label carries
The sticker is built to go straight on a case or tote:
The heading — a finished product's item code and name, or, for an
intermediate, its recipe name and
.
PREP — the date the batch was prepared.
LOT# — the lot the batch produced, the string you trace forward to every
shipment and back to its ingredients.
A QR code — the same lot, scannable, so the floor can pull it up later
without keying a thing.
An intermediate's label carries three lines a finished-product label leaves off:
WIP #, BEST BY, and ALLERGENS.
Export a cooking or cooling log
A recipe with a cooking or cooling
puts
a Cooking Log or Cooling Log tab on the run.
Record the readings there
batch by batch; when it's time to file them, the export lives on the same tab.
Above the consolidated table, each log carries a button per template — the format
your plant files under. Cooking offers FDA PDF and USDA Kettle PDF; cooling
offers FDA PDF and USDA IQF PDF. Recipes set up under a different authority
or cook method file under their own template, so the button set matches what's on
the run. Selecting one opens the finished record in a new tab.
Each log carries an export button per template — FDA and USDA Kettle here — above the run's Cooking Log. Selecting one opens a print-ready record in a new tab.
What the exported record contains
The export is a print-ready log, not a raw dump of numbers:
Your plant's name and address, the run's reference, and the production date
across the top.
A row per batch with its readings, the times, and initials — plus a couple of
blank rows for anything the floor logged by hand.
The critical limit spelled out in full, so the record explains its own
pass-or-fail rule.
On a USDA template, the establishment number and a Verification block for
the reviewer to sign.
The note at the top reads use your browser's print dialog to save as PDF, and
Print this log does exactly that. This is the
an
auditor asks for — produced without a day of prep.
Export one department at a time
When a run's recipes span more than one department, a Department filter sits
above the log. Pick a department and the table — and the log you export from it —
narrows to that department's recipes, so each line files its own record.
Bettr flags a run until its log is filed
Until you've generated a run's cooking or cooling PDF, the run list marks it —
Cooking Log PDF not generated, with a warning triangle — so a run doesn't
ship without its records. Generating the export clears the flag.