Batch and lot release management: from formula to physical lot

A formula describes a product in principle; a batch is one physical run of it — a specific lot, made on a specific date, in a specific quantity, that has to be tested and released before it can ship. Managing batches — their lot numbers, their test results, their release status, and the manufacturing record behind each — is where the formula meets the real world of production and quality. Here is how software handles batches and lot release.

A batch is a physical run of a formula

Where a formula is the recipe, a batch is one actual making of it: a lot number, a quantity produced, a manufacturing date, an expiry or best-before date, and a status. Each batch is tied to the formula version it was made from — so you always know exactly which recipe produced which lot. This link is the foundation of traceability: a lot in the market traces back to a precise formula.

Batches come in types — a lab or pilot batch during R&D, a production batch for sale — but the structure is the same: a physical run, recorded, traceable to its formula.

The batch carries its record and results

A batch is more than a number. It carries its manufacturing record — what was made, from which formula — and its linked test results, the QC tests run on that specific lot. So everything about a lot lives together: the formula it came from, the quantity, the dates, and the evidence it was tested. When you need to know everything about lot number such-and-such, it is one place.

This is exactly what traceability and audits demand: the full story of a physical lot, connected and findable, rather than scattered across production logs and lab reports.

Release status: the gate before shipping

A batch should not ship until it is released — confirmed to have passed its tests and met its specification. The release status is the gate: a batch is held until its QC results come back pass, then released. Managing this status in the system means you always know which lots are released and shippable and which are still pending or failed — so an unreleased or failed lot is not shipped by mistake.

This ties directly to testing: the batch's linked test results drive whether it can be released, connecting QC to the release decision.

The batch manufacturing record, generated

A batch needs a manufacturing record — the document capturing what was made, from which formula snapshot, in what quantity, with which lot number. Because the batch is tied to its formula version, this record is generated from the data: the formula snapshot plus the lot details, produced as a document rather than assembled by hand. The record that proves how a lot was made comes straight from the system.

Lab, pilot, and production batches

The same batch structure serves R&D and production. A lab or pilot batch during development records a trial run — useful for scaling up and for the development story. A production batch is the real thing for sale, with full release discipline. Handling both in one system connects development to production: the pilot batches that proved the formula and the production batches that ship it share the same lineage.

Because batch record, lot, and release requirements differ by market and your quality system, confirm the requirements that apply to your specific operation rather than relying on a general summary.

Where Lemoniq fits

Lemoniq manages batches as physical runs of a formula: each batch carries its lot number, quantity, dates, and status, tied to the exact formula version it was made from. Linked test results drive the release status, so only passed lots are released; lab, pilot, and production batches share one structure; and the batch manufacturing record is generated from the formula snapshot and lot details. The formula meets production with full traceability and a clear release gate.

The takeaway

A batch is one physical run of a formula — lot number, quantity, dates, test results, release status — and managing batches connects the formula to the real world of production and quality, with traceability from a market lot back to its exact recipe. Software that ties each batch to its formula, links its test results to a release gate, and generates the manufacturing record makes lot release controlled and traceable. From formula to released lot, the chain is unbroken.

Lemoniq manages batches and lot release — each lot tied to its formula, gated by test results, with the manufacturing record generated. We solve this exact problem. See how it works