Hi everyone — Mahmoud here, maker of BatchRoute. This started with an annoying observation: brands spend real money on third-party lab testing, and the COA ends up as one static PDF on a product page — matching exactly one production run out of the many they ship. The usual alternative, a unique QR per batch, means new artwork and new print plates every run, which most brands can't justify. BatchRoute splits those two identities apart. The QR on the packaging is permanent and belongs to the SKU. The lot code your co-packer already stamps on the bottle identifies the batch. Scan, type the lot, get that exact run. A few things we were opinionated about: - The public verification page is server-rendered with zero client JavaScript, zero cookies, and self-hosted fonts. Someone checking a bottle shouldn't be profiled for it. - Every batch has a governed lifecycle: Pending, Verified, Quarantined, Recalled, Archived. A recall requires a typed lot-code confirmation plus a consumer note, and it can't be undone. - Certificate links re-check the batch status at click-time, so a recall cuts off document access in zero seconds — even for a browser that's already open. - When a lookup fails we never say "invalid" or "counterfeit". We show people where the code sits on the pack and which characters get misread, then show the brand the grouped misses so they can fix the label print. To be clear about what this isn't: BatchRoute is not a lab or a certification body. It publishes what the brand provides, with an append-only audit trail of who did what. We're running concierge pilots right now — I set brands up on their first SKU myself. Happy to answer anything about the architecture or the day-to-day workflow.

BatchRoute

One permanent QR per SKU. Verify any batch in seconds.

One permanent QR per SKU. Verify any batch in seconds.