Setting Up Batch Records and Traceability From Day One

Most small makers start batch records because someone told them they'd need them eventually, then treat the actual paperwork as an afterthought, a notebook page scribbled after the fact from memory. That works fine right up until a customer reports a reaction, or a raw material gets recalled by your supplier, and you need to answer a very specific question fast: which finished units contain the ingredient lot that's now in question. If your batch records can't answer that in five minutes, they're not doing the job.

What a batch record actually needs to do

The whole point of a batch record is traceability in both directions. From a finished unit, you should be able to work backward to every raw material lot that went into it. From a raw material lot, you should be able to work forward to every finished batch it touched. That two-way link is what lets you respond to a supplier recall by pulling exactly the affected units, instead of pulling your entire inventory out of caution.

This kind of traceability is also part of what good manufacturing practice guidance for cosmetics, laid out in standards like ISO 22716, expects as baseline documentation, even for a small operation that isn't formally certified against it.

The minimum fields worth capturing

You don't need enterprise software to do this well. A structured spreadsheet or a simple database table works, as long as it consistently captures:

• Batch number for the finished product, assigned at production, unique and never reused.
• Production date and, if relevant, the person or team who ran the batch.
• Formula version used, since formulas do get tweaked over time and you need to know which version was actually made.
• Raw material lot numbers for every ingredient in that batch, not just the ingredient name. This is the field people skip and regret skipping.
• Quantities used of each raw material, which supports both traceability and consistency checks.
• Yield, meaning how many finished units the batch actually produced, useful for reconciling inventory and catching process errors.
• QC or release notes, even something as simple as "visual check passed, pH checked at 5.2" for a lotion.
• Expiry or best-by date applied to that batch, tied back to the production date and your stability data.

A simple structure

Field	Example entry	Why it matters
Batch number	LB-2026-0142	Unique identifier tying label to record
Production date	2026-01-14	Anchors shelf life and recall windows
Formula version	v3.2	Confirms which recipe was actually used
Raw material lots	Shea butter lot #S4471, Fragrance oil lot #F1189	Enables backward and forward tracing
Quantities	Shea butter 1.2 kg, Fragrance 18 g	Supports consistency and cost checks
Yield	96 units, 2 oz jars	Reconciles against sales and inventory
QC notes	pH 5.1, visual pass	Documents release decision

Why this matters more than it feels like it should

A lot of makers treat this as busywork until the day it isn't. If a fragrance supplier issues a recall on a specific lot because of a contamination issue, and you've been tracking lot numbers per batch, you can identify exactly which of your finished batches used that fragrance lot and pull only those. Without lot-level tracking, your only honest option is pulling everything made in the affected time window, which is expensive and, frankly, embarrassing to explain to customers.

The same records matter if you ever need to file an amendment or discontinuation for a product, or if a regulator asks for documentation supporting a safety claim. Having clean, consistent batch records turns what could be a scramble into a five-minute lookup.

Getting started without overbuilding it

You don't need to buy manufacturing execution software on day one. Start with:

1. A spreadsheet template with the fields above, one row per batch.
2. A habit of writing down lot numbers the moment you open a new container of raw material, not from memory later.
3. A simple numbering convention for your own batches that encodes the date, so you're not relying on a separate lookup to know when something was made.
4. A backup of the spreadsheet somewhere that survives a laptop crash.

As your product line grows, this becomes the backbone of a lot of other compliance work too, including the ingredient percentages and formula versions you'll need on hand when it's time to file or amend a notification. Cosmetic Comply's duplicate-a-past-filing feature leans on exactly this kind of clean formula versioning, so if your batch records already track which formula version is current, filing a minor variant later is a much faster process than starting from scratch.