ERRA for Compliance

What you do in ERRA

You check that a claim on packaging is backed by evidence in the claims register, that an approved formula version's content has not drifted since its approval, and that the audit trail for a specific batch or lot holds together end to end.

When a recall question comes in, you pull the blast radius from real shipment and genealogy data instead of assembling it from spreadsheets under time pressure.

What ERRA gives you

• An append-only audit trail on every domain mutation: who, what, when, and the before-and-after state, with a viewer, record history, and export.
• Approval content binding: a formula version's approval is bound to a hash of its compliance-relevant facts, and drift after approval is named on the record, not silently absorbed.
• A claims register with substantiation evidence and a DSHEA check, connected to the formula version it describes.
• Recall blast-radius calculation drawn from real shipment and lot genealogy, plus a timed mock recall drill.
• A public per-lot verification page stating exactly what has been documented, traced, or verified about that lot.

What ERRA attests to, and what it does not

ERRA attests to the record: that the evidence exists, that the gate ran, that the signature is bound to what it approved. It does not inspect your product and does not substitute for your own regulatory judgment or counsel. The mark goes dark the moment the record it reads from breaks.

Keep reading