When you make products in small runs, every batch has a story. Which ingredients went into Saturday's granola? When was that lavender soap poured? Which glaze did you use on the mugs collected from the studio last week? Most of the time, the answer feels obvious—until a customer asks three weeks later, a supplier announces a recall, or one batch behaves differently from the others.
A batch tracking system connects what you bought, what you made, and what you sold. It does not need to be enterprise software or a shelf full of binders. For many home-based sellers and local makers, a batch code, one consistent production record, and a way to connect orders back to that code are enough to make problems smaller and decisions better.
This is useful for bakers, jam makers, candle pourers, soap and skincare businesses, ceramicists, dyers, coffee roasters, meal-prep sellers, and anyone whose products are made together under similar conditions. The exact records you are legally required to keep depend on your product and location, so check the rules that apply to you. The practical system below is a starting point for traceability, not a substitute for safety, labeling, tax, or regulatory advice.
Start with the question your records must answer
Good tracking lets you move in both directions.
If a supplier tells you that one lot of an ingredient or material has a problem, you should be able to identify which finished batches used it and where those products went. If a customer reports an issue with a finished product, you should be able to find the production date, inputs, process notes, and other orders from the same batch.
That means your system should answer five questions without relying on memory:
1. What did you make? 2. When and where did you make it? 3. Which materials or ingredients did you use? 4. How many sellable units did the batch produce? 5. Which listings, markets, pickups, or customers received those units?
Do not collect information merely because it looks official. Every field should help you trace a product, improve consistency, calculate yield, or respond to a real question.
Create a batch code you can read at a glance
A batch code should be unique, short, and easy to write on a label. A simple structure is:
Product code + production date + run number
For example, a baker's first focaccia batch on September 1, 2026 might be FOC-260901-01. A candle maker's second amber-and-cedar pour that day might be AC-260901-02.
Use the date the product was made, not the market date. Give each meaningfully different run its own code. If you change a key ingredient lot, recipe, fragrance load, glaze combination, machine setting, or production condition, start a new batch rather than squeezing the difference into a note nobody will notice later.
Keep codes boring. Avoid customer initials, changing abbreviations, or numbers that reset each month without a date. Write a one-page key for product abbreviations so a helper uses the same codes you do.
Build one batch record you will actually complete
Your record can live in a spreadsheet, notebook, or printed form. The best format is the one you can fill out during production with clean hands and without hunting through five apps.
Include these core fields:
- Batch code and product name
- Production date, start time, and maker
- Recipe, formula, design, or process version
- Ingredient or material names and supplier lot numbers when available
- Quantities used
- Important process readings or conditions
- Units produced, damaged, sampled, and released for sale
- Packaging or label version
- Best-by, cure-ready, or review date where relevant
- Storage location
- Notes about substitutions, delays, unusual results, or rework
- Final check and release decision
Record the measurements that affect your product rather than copying another business's form. A baker may need bake time and temperature. A candle maker may track wax temperature, fragrance percentage, wick, and cure date. A ceramicist may record clay body, glaze lot, kiln, firing schedule, and shelf position. A natural dyer may record fiber weight, mordant, dye material, water conditions, and timing.
Use a version number for recipes or production instructions. “Chocolate cookie v3” is much more useful than “usual recipe” after you change the flour ratio six months from now.
Connect incoming materials to finished products
When supplies arrive, record enough detail to identify them later. Save the supplier, item, received date, lot or batch number, and use-by date when applicable. The lot number is often printed near a barcode, seal, or best-by date.
You do not have to catalog every shipping box. Focus on inputs that affect safety, quality, claims, or product performance. For a food seller, that usually includes ingredients and packaging that touches food. For a skincare maker, it may include oils, preservatives, fragrances, containers, and labels. For a ceramicist, it may include clay and glaze lots.
Assign a simple internal code if a supplier does not provide one, then keep the invoice or delivery record with it. Use older suitable stock first, and do not combine identical-looking supplies from different lots in one unlabeled container. Once two lots are mixed, tracing them separately becomes difficult.
Here is a practical example: you receive two cases of oats, lot O778, on August 27. Your September 1 granola batch record shows that lot O778 was used in batch GRA-260901-01. If the supplier later flags O778, you can identify the exact finished batch instead of treating every bag of granola you have ever sold as affected.
Put the code where it survives the sale
The batch code is useful only if it stays connected to the product. Print or write it on the product label, packaging, hang tag, care card, or a removable sticker on the outer box. Choose a location customers can find if they contact you.
For products sold as a set, decide whether the set receives one assembly code, the individual items keep their original codes, or both. If three jars from three batches go into a gift box, recording only the gift-box date loses important detail.
At markets, do not rely on remembering which stock came from which tote. Separate batches in labeled bins and finish one batch before replenishing from the next when possible. If you mix batches on the display, keep a start-and-end note for each one sold.
For preorders and local pickup, add the relevant batch code to your packing or fulfillment record. A Tiny Store weekly menu or custom listing can keep the customer-facing offer clear, while your internal order list connects the pickup order to the batch. If one listing spans multiple production runs, record the code beside each fulfilled order instead of assuming the listing identifies the batch.
Make market and pickup traceability practical
Local sales often happen through several channels in one weekend: Friday porch pickup, Saturday farmers market, and Sunday coffee-shop meetup. Track the quantity assigned to each destination before products leave your workspace.
A distribution log can be simple:
| Batch | Destination | Quantity out | Quantity returned | Date | | --- | --- | ---: | ---: | --- | | GRA-260901-01 | Friday home pickup | 18 | 0 | Sept. 4 | | GRA-260901-01 | River Market | 30 | 6 | Sept. 5 | | GRA-260901-01 | Oak Street meetup | 12 | 1 | Sept. 6 |
For paid preorders, connect the order name or number to the batch. For anonymous market sales, record the selling window and destination even when you cannot identify every shopper. The goal is to know the smallest reasonable group affected if you need to provide an update.
Tiny Store can reduce the number of loose ends: use a dedicated listing for a dated preorder release, set the correct local pickup or meetup spot, and share that direct storefront link or QR code. Export or retain the order information you need under your applicable recordkeeping and privacy rules. Avoid placing sensitive customer details in a general production sheet.
Add a ten-minute end-of-batch routine
Incomplete records are usually a workflow problem, not a discipline problem. Finish the record before cleaning up or opening sales.
At the end of each run:
1. Count sellable, sample, damaged, and held units. 2. Compare actual yield with expected yield. 3. Photograph the finished batch and its label if visual consistency matters. 4. Record deviations while they are fresh. 5. Mark where the batch is stored. 6. Sign or initial the final check. 7. Create the quantities assigned to listings, pickups, and markets.
If you need to hold products until a cure time, temperature check, or quality review is complete, label them HOLD and keep them physically separate from released stock. A checkbox in a spreadsheet will not prevent the wrong box from reaching the market table.
Use batch data to improve the business
Traceability is the safety net, but the same records can make production more profitable. Review them monthly for patterns.
Track:
- Expected yield versus actual sellable yield
- Waste, breakage, rework, and samples by batch
- Production minutes per unit
- Ingredient or material variance
- Customer complaints, refunds, or remakes by batch
- Sell-through by market, pickup spot, and release
- Returns or leftovers by batch
- Recipe or process version performance
Suppose one candle batch produces 48 jars but six develop rough tops, while the next produces 48 with no defects after a temperature adjustment. Your records turn “this pour seemed better” into a repeatable improvement. Or perhaps a jam batch sells out through preorders but returns eight jars from a distant market. The recipe may be fine; the better decision could be moving more inventory to click and collect next time.
Look at rates, not just totals. Two damaged items in a 20-unit batch is a different signal from two in a 200-unit batch.
Practice a mock trace before you need a real one
Once a quarter, choose one finished product at random. Set a timer and try to find its batch record, inputs, quantities, selling destinations, and connected preorder customers. Then choose one ingredient or material lot and trace forward to every finished batch that used it.
Write down what slowed you down. Maybe the supplier lot was missing, market returns were added to the wrong bin, or an order list did not show which Saturday release it belonged to. Fix the system while the exercise is calm.
If a real quality or safety concern occurs, pause sales and isolate related stock. Preserve records, document what you know, and follow the reporting, notification, withdrawal, or recall requirements that apply to your product and location. Do not guess publicly or quietly relabel questionable goods. Contact the appropriate regulator, insurer, supplier, or qualified professional when the situation requires it.
Common batch tracking mistakes
The first is using the market date as the batch code even though products were made on several different days.
The second is recording ingredient names but not supplier lot numbers. “Flour” cannot be traced to a specific delivery.
The third is making the form so detailed that nobody completes it. Start with fields tied to traceability, consistency, and yield.
The fourth is changing a recipe without assigning a new version. Later results become impossible to compare.
The fifth is putting a code on a production sheet but not on the product or fulfillment record.
The sixth is mixing returned market stock into a newer batch without preserving its identity.
The seventh is storing all customer information in an open batch spreadsheet. Keep operational records useful and access appropriately limited.
The eighth is collecting data forever but never reviewing yield, waste, complaints, or sell-through.
Your batch tracking starter checklist
Set up the system:
1. List the products that need batch tracking and the process details that matter for each. 2. Choose one readable batch-code format. 3. Create a short production record and recipe-version convention. 4. Start an incoming materials log with supplier lots. 5. Decide where the code will appear on each product or package. 6. Create a distribution log for markets, preorders, pickups, and meetup spots.
For every batch:
1. Assign the code before production begins. 2. Record inputs and process details as you work. 3. Count sellable, held, sample, and damaged units. 4. Complete the final check before releasing products. 5. Connect quantities and fulfilled orders to selling destinations. 6. Keep batches physically identifiable through storage and transport.
Each month:
1. Review yield, waste, production time, issues, and sell-through. 2. Investigate repeated differences instead of explaining them from memory. 3. Update the recipe or process version when you make a controlled change. 4. Test one backward and forward trace. 5. Retain records for the period required by the rules, risks, and shelf life relevant to your products.
Batch tracking is not paperwork for paperwork's sake. It is how a small maker can answer a difficult question quickly, protect customers, learn from production, and keep one uncertain jar, candle, loaf, or mug from becoming an uncertain business. Start with one code and one honest record. Consistency will do the rest.
Tiny goodbye
May every batch have a name, every mystery have a paper trail, and your best experiments always be repeatable.
