California recall trend
Eight out of ten cannabis recalls in California are paperwork failures.
All numbers on this page are sourced from the California Department of Cannabis Control's public recall portal. The methodology is at the bottom. Refresh date appears on every figure.
The headline statistics
What this regulator phrase means
'Inaccurate Labeling (Cannabinoid inflation),' in plain English.
Cannabinoid percentage gets inflated through a data pipeline, not through a single decision. The lab tests the product, hands a result to the brand or distributor, the result is recorded in an ERP, the ERP feeds a label generator, the label generator hands a payload to a printer, and the printer renders text onto the package. Somewhere along that chain, the number on the package becomes higher than the number the lab actually measured.
The DCC's verbatim citation phrase is "Inaccurate Labeling (Cannabinoid inflation)." It does not specify which step in the pipeline failed. From the regulator's view, the label is the artifact and the artifact is wrong. The investigation falls on the licensee whose name is on it.
- Lab issues result.
- Result lands in ERP, sometimes as an attachment, sometimes as a structured field, often both.
- Label generator (BarTender, Loftware, custom) reads the ERP record through a field map.
- Field map renders payload to printer-ready format (PDF, ZPL, EPL).
- Printer renders payload to package.
- Metrc records the cannabinoid value of the package as part of the state's authoritative record.
If any of those handoffs is stale, mismapped, or out of order, the label and the lab no longer agree. The label is what the regulator photographs. That is what counts.
Why no vendor solves this
Each vendor in your stack is responsible for their own product surface. Your lab vendor is responsible for the test result they hand you. Your ERP vendor is responsible for the records you put in their system. Your label vendor is responsible for rendering the payload they receive. Your printer vendor is responsible for putting ink on substrate. Your Metrc integrator is responsible for syncing what your system tells it to sync.
None of them are responsible for the gaps between their products. None of them have commercial incentive to be. A vendor who fixes the cross-vendor gap is a vendor who has expanded their support burden into systems they don't control. So the gaps stay open, and operators absorb the cost when something falls through.
The fix requires an independent operator with cross-vendor visibility and no surface to defend. That is the work I do.
Methodology
Data harvested from recalls.cannabis.ca.gov. Verbatim regulator language is preserved where cited. Counts include voluntary and mandatory recalls in the date range above. Reason categories are mapped 1:1 against the DCC's published reason fields; the "label / cannabinoid-pipeline" bucket aggregates reasons coded as Inaccurate Labeling, Cannabinoid inflation, and Misbranded.
Data refreshed quarterly. Last refresh: 2026-04-30. Methodology questions: brandon@phenominal.io.
If your distribution sits on this data flow, the conversation is free.
Thirty minutes. No slides. If an engagement does not make sense, I will tell you on the call.