Batch lifecycle & consumer verification for supplement brands

Instant proof for the exact batch in your customer's hands.

One permanent QR code per product. The lot code printed on the bottle identifies the batch. Publish documentation, put a batch on hold, or issue a recall — without new artwork every production run.

QR codes per SKU
One
Consumer accounts
None
Reprints per batch
Zero

Public verification page

batchroute.io/p/nbn-mg4

Magnesium Glycinate

Northbay Nutrition · 120 capsules

Try:

Awaiting lot code

Enter the lot code printed on your pack. It is usually stamped near the best-before date, on the base of the pack or along the edge of the label.

BatchRoute publishes the batch information Northbay Nutrition provides. It is not a testing laboratory, a certification body, or a statement that this product meets any regulation.

Sample data · this is the page your customer sees

How a customer checks a batch

  1. 01 — Scan

    The native phone camera

    No app, no account. The QR resolves to the product, not to a single production run.

  2. 02 — Enter the lot code

    Straight off the bottle

    Exact match on a normalized code. Spacing and case don't matter to your customer.

  3. 03 — See the batch

    As it stands right now

    Status, dates, your note, and the published COA — or the notice you've issued instead.

How batch verification works, from your workspace to your customer's phone

The everyday version

“Can you send me the COA for this bottle?”

You already pay a laboratory to test the product. Then the document goes into a shared drive, an email thread, a lab portal or a spreadsheet — and someone on support has to work out which batch the customer is holding before they can answer.

The tools you'd reach for don't close the gap. A QR generator gives you a code and a COA viewer gives you a PDF, but neither knows which batch is in the customer's hand — and when a batch goes on hold, neither takes its certificate down.

Publishing a certificate of analysis for each batch

  • Documentation your customers can't reach on their own.
  • A product page showing one certificate for every production run.
  • New artwork, new plates, new QR — every time the batch changes.
  • No reliable way to tell buyers a batch status changed after it shipped.
  • No record of who published or edited what, and when.

Permanent QR architecture

Packaging identity stays still. Production identity keeps moving.

The QR belongs to the SKU and is printed once. Behind it, batches come and go, statuses change, and documents get published — all without touching the artwork.

Printing a permanent QR code on your packaging

Printed once · never changes

Batches behind this code

  • L2607-A14 Verified
  • L2605-C09 Quarantined
  • L2603-B02 Recalled
  • L2608-D21 Pending

Batch lifecycle

Five states, one source of truth

Every batch sits in exactly one state. Change it and the public page follows — no reprint, no email blast, no waiting for anyone to update a product description. Status is never carried by colour alone.

Pending

Created, not yet published. Customers see that documentation is on its way.

Verified

Published with the COA you attached and the dates you entered.

Quarantined

On hold. Your notice replaces the normal presentation while you investigate.

Recalled

Stop-use notice front and centre, with your instructions for the customer.

Archived

Kept as history. Old lot codes keep resolving instead of going dark.

Recall and quarantine, without a reprint

Change the status, confirm the action, write the notice your customer needs to read. Anyone scanning that bottle sees it on their next lookup. The action is permission-controlled and always recorded.

A recall notice here is a way to reach the person holding the product. It doesn't replace your statutory obligations.

How lot-specific recalls and holds reach customers

Recall notice

Stop using this batch

Voluntary recall of lot L2603-B02, issued 2 August 2026, for a packaging seal defect. Return the bottle to the point of purchase for a full refund.

Published by K. Osei · QA Manager

Audit trail

Who changed what, and when

Every batch action is written to a ledger with the actor, their role, the previous value and the new one. Your team can read it. Nobody on your team can rewrite it.

TimestampActorActionFrom → to
2026-08-02 09:14K. Osei · QAStatus changedQuarantined → Recalled
2026-07-28 16:02K. Osei · QAStatus changedVerified → Quarantined
2026-07-12 11:47A. Boateng · OpsCOA publishedcoa-L2607-A14.pdf
2026-07-03 08:31A. Boateng · OpsBatch createdL2607-A14

Pilot

A free pilot for independent supplement brands.

Create a workspace, set up one product and you have its permanent QR code and a live verification page to test with real lot codes — before you commit to a single packaging change. It is free while we validate the product.

  1. 01You create a workspace and add one product. Nothing waits on a call with us.
  2. 02You record recent batches by lot code, attach their COAs, and download the permanent QR as SVG and PNG.
  3. 03You review the public page and test it with real lot codes off real bottles.
  4. 04The QR goes on at your next natural artwork update — not before.

Pilot access

$0 / during validation

Free for our initial pilot cohort. No credit card, subscription, or billing. You set it up yourself, and we ask for 20 minutes of feedback after your first batch goes live.

Cohort scope

  • Independent supplement, nutraceutical, sports nutrition and pet brands
  • 1 SKU to start, set up in your own workspace
  • Recent production batches with third-party COAs
  • 20 minutes of feedback after your first batch goes live
  • Commercial terms decided after validation

What we're measuring in the pilot

Customers who find their batch
≥ 85%
Status change goes public in
< 60s
Setup time per brand
< 4h
Drop in COA support tickets
≥ 50%

These are the targets the pilot is designed to test, not results we're claiming.

The pilot: what it involves and what it tests

Where we stand

BatchRoute publishes and hosts the batch information you give it. It is verification and documentation infrastructure — not a testing laboratory, a certification body, or a statement that a product meets any regulation.

We don't test your product, review your laboratory results, certify anything or determine regulatory compliance. You remain responsible for the accuracy and lawfulness of what you publish.