Labelsdesigned, approved, printed and audited in one place.
Most regulated manufacturers run a label tool (NiceLabel, Loftware, BarTender) bolted next to their QMS — versions drift, reprints aren't audited, and 211.122 / 111.130 / 820.120 findings follow. V5 puts the designer, the approval workflow, the print agent and the reprint audit trail in one place — the same place that holds the BMR.
Watch a label build itself — by the book.
Nine layers, nine citations. None of them are hand-typed. None of them can be printed against the wrong batch.
Layout is a controlled artifact — version-controlled, e-sig approved, never a Word doc.
A label isn’t artwork.It’s a regulated record.
Most label tools are design studios — they let you draw a label and push it to a printer. Part 11 doesn’t care about drawing. It cares about who approved that layout, which batch it was bound to, who actually pressed print, and whether anyone could quietly change it after the fact. V5 holds the label as a record, not a file.
Take a photo of any label.Get a signed master in seconds.
Onboarding a new SKU used to mean re-keying a label by hand from a PDF or a vendor sample. Open V5 on a phone, point it at the existing label, and the engine extracts every regulated field — identity, NDC, lot pattern, barcode symbology, allergens, address blocks — and drops them into a draft master ready for QA review.
Every captured token is matched against the regulated field dictionary, validated for format, and staged in a draft. Nothing is bindable until QA signs the master under §11.50.
Every Part 11 control, mapped to the label engine.
Eleven controls. Eleven concrete answers. Click any tile to see the regulation alongside the mechanism that satisfies it.
Seven states. Every transition is signed.
A label master moves through a state machine, not a folder. Each arrow between states is an electronic signature — meaning no rev ever appears without a name, a time, and a reason attached.
Released
Second signature releases the master. Now immutable. From here, only supersede — never edit.
Every print event links to the previous one — by hash.
Each event records its parent’s SHA-256. Change any byte in any historical record and every downstream hash breaks. An auditor with the latest hash can independently re-verify the entire history of a label — without trusting V5.
- → No silent edits. No quiet reprints.
- → Reprints carry a reason code, not just a count.
- → Voids supersede — they never erase.
- → Chain root + leaf hash exportable for offline archive.
- 2025-09-14 14:22:08PRINTsha256: c91a4f…7e2by J. Parkrev v1.0lot K228reason —
- 2025-09-14 14:22:34REPRINTsha256: b4d109…91aby J. Parkrev v1.0lot K228reason PAPER_JAM
- 2025-09-14 14:23:01REPRINTsha256: 7af602…cc8by J. Parkrev v1.0lot K228reason PAPER_JAM
- 2025-09-14 14:23:55VOIDsha256: 1e8b27…334by P. Reyesrev v1.0lot K228reason REPRINT_SUPERSEDES
- 2025-09-22 09:12:40SUPERSEDEsha256: ff20a6…aa1by QA Mgrrev v1.1lot —reason ALLERGEN_TEXT_UPDATE
NiceLabel, BarTender, Loftware — all great designers. None are record systems.
Design studios were built to make a label look right. V5 was built to prove a label was right — at 14:22 on a Tuesday, on the printer in line B, for lot K228, against rev v1.0 of an artwork two people signed off. That’s a different class of system.
Designers can be wired up to a record system — but every plumb job becomes one more validated boundary. V5 collapses the boundary by owning the master, the WO bind, the kiosk signature, and the archive in one Part 11–scoped tenant.
“Show me the label you printed at 14:22 on 14 September, for WO-2918.”
- 1. Pull the batch record binder from the archive.
- 2. Find the printer log for line B that shift.
- 3. Try to match the timestamp to a label image — there isn’t one.
- 4. Ask the operator who printed (they don’t remember).
- 5. Cross-reference the supervisor’s sign-off page.
- 6. Photocopy the saved sample label from the QC drawer.
- 7. Hand the auditor a stack of paper.
• zpl_stream.txt
• epcis_event.xml
• signature_envelope.json
Stop printing labels.Start signing records.
V5 holds your label library, your print events, and your auditor’s evidence in one Part 11–scoped system — no integrations, no bolt-ons, no quiet reprints.

