Skip to content

Batch Numbering System SOP: A Template You Can Adopt

A batch numbering SOP template for a small maker: the code format, who assigns it, where it goes, rework and repacks, mistakes, and a batch register.

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 · 5 min read

A batch numbering SOP is a one-page procedure that answers six questions so nobody has to improvise: what the code looks like, who assigns it and when, where it's written, when a new code is needed, what happens with rework and repacks, and what to do when a code is wrong. The reason to write it down is the second person. One maker's habit becomes two people's guesses, and two batches end up under one code. Below is a complete SOP for a small food business that you can adopt with your own format, and a batch register to assign codes from.

The short version

  • Pick a format that says the product and the day, plus a run number.
  • Assign the code before anything is weighed, from a register, so no code is used twice.
  • Put it on the batch record, every unit, every case and every shipping record.
  • New code for a new product, day or line, or after a real stop.
  • TaroStack assigns a lot to every batch and prints it on labels. More below.

The SOP

Purpose. Every batch we make gets one code that identifies it and nothing else, so any unit can be traced to the day, the line and the ingredients it was made from.

Applies to. Every product made for sale, every sub-batch made ahead (doughs, sauces, blends), and every repack.

The format. PPP-MMDD-N: a product code of two to four letters, the month and day made, and a run number for that day. GB-1009-1 is the first granola bar batch made on October 9. The year is on the batch record and in the best-by date.

Who assigns it. The person who starts the batch, from the next free code in the batch register, before any ingredient is weighed.

Where it goes. On the batch record, on every unit (printed or stamped with the best-by date), on every case, and on the shipping record for each order.

One batch, one code. A new code when the product, the day or the line changes, or when production stops for more than a break and starts again. Two batches are never packed under one code.

Rework and repacks. Rework added to a batch is recorded on that batch's record with the code it came from. A repack keeps the original code and adds R, as GB-1009-1R.

Mistakes. A wrong code found before shipping: relabel, and note it on the batch record. Found after shipping: tell the recall coordinator the same day.

Records. The batch register and batch records are kept two years, or longer if a customer or a rule asks.

Review. Read through once a year and at every mock recall. Signed and dated by the owner.

Choosing your format

Format Example Good for Watch out for
Product, date, run GB-1009-1 Readable by anyone Needs the year from somewhere else
Year and day of year (Julian) 26282-1 Compact, sorts in order Staff and customers can't read it without a chart
Best-by date as the code BB 04/09/27 A One print on the pack Two batches on a day need a letter
Running number 004417 Simplest to assign Says nothing by itself

My advice is the first, unless a customer requires another. A code a new hire can read on day one gets written correctly. Julian dates are explained in Julian date code format, and more formats in how to create lot numbers.

Whatever you choose, decide what "a batch" is. For most small makers it's one product, made in one continuous run, from one set of ingredient lots. If you open a new bag of flour halfway through, you can either record both flour lots on the one batch or start a new code. Both work. Pick one and write it in the SOP.

The batch register

Batch code Product Date made Started by Units made Best by
GB-1009-1 Granola bars, 12-pack Oct 9, 2026 TA 480 Apr 9, 2027
TM-1104-1 Trail mix, 6 oz Nov 4, 2026 TA 564 May 4, 2027

The register is why codes don't collide. It lives where batches start, not in the office.

Get the template

Download the batch numbering SOP. Two sheets and a read-me: the SOP, section by section, and a batch register. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Printing the code on packs is covered in lot code printer.

Where this stops working

An SOP depends on people following it at 5 a.m. The register gets skipped, a code is reused, a repack goes out with no R. And a perfectly coded pack is still only half the system: the code has to be written on each order too, by hand, or it can't tell you who got it.

How TaroStack does it

TaroStack is the register, and it can't assign a code twice.

Every batch gets a lot. Record a batch and it gets a lot code, with its production and best-by dates. Sub-batches made ahead get their own.

The record fills itself. The batch record notes which ingredient lots were consumed, automatically.

Labels carry it. Print lot labels with the code and date, as GS1-128 barcodes when the item has a GTIN.

Orders take it. Each order records the lots it shipped, first-expired-first-out by default, so the code on the pack leads to a customer list.

Repacks and returns stay tied. A return goes back into the lot it left in.

The SOP says By hand In TaroStack
Assign from the register Remember to A lot with every batch
Code on every unit and case A stamp Printed lot labels
Code on every shipping record Written, if remembered Recorded with the order
Rework recorded with its code A note The lot consumed, on the record

Lots and batches 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

How do you assign batch numbers?

From a register, in a fixed format, before the batch starts, one code for one batch.

What should a batch number include?

Enough to identify the product and when it was made, plus a run number if you make more than one batch a day.

Is a batch number the same as a lot number?

For most small makers, yes. The difference, where there is one, is in batch number vs lot number.

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.