Between December 2024 and July 2025, the California Department of Cannabis Control posted eight recall entries against a single Sacramento Type-11 distributor's license. Three different brands appear on the recalled packages. The licensee is the same on every one.
Every recall referenced in this article is publicly visible on the DCC recall portal at recalls.cannabis.ca.gov. Anyone can verify the verbatim language, the dates, and the licensee fields by searching the portal directly. This article does not name the licensee. Naming is not the point. The pattern is.
The eight recalls, in order
| # | Date | Reason (verbatim DCC language) | Type |
|---|---|---|---|
| 1 | 2024-12-16 | Adulterated and Misbranded: Microbial Contamination (Aspergillus spp.); Inaccurate Labeling (Cannabinoid inflation) | Voluntary |
| 2 | 2025-01-03 | Adulterated and Misbranded: Microbial Contamination (Aspergillus spp.); Inaccurate Labeling (Cannabinoid inflation) | Voluntary |
| 3 | 2025-02-28 | Adulterated: Microbial Contamination (Aspergillus spp.); Inaccurate Labeling (Cannabinoid inflation) | Voluntary |
| 4 | 2025-03-28 | Adulterated: Microbial Contamination (Aspergillus spp.) | Mandatory |
| 5 | 2025-04-15 | Adulterated: Microbial Contamination (Aspergillus spp.) | Mandatory |
| 6 | 2025-04-15 | Adulterated: Microbial Contamination (Aspergillus spp.) | Mandatory |
| 7 | 2025-06-26 | Adulterated: Microbial Contamination (Aspergillus spp.) | Mandatory |
| 8 | 2025-07-17 | Adulterated: Microbial Contamination (Aspergillus flavus); Microbial Contamination (Aspergillus niger) | Mandatory |
Three things to read before the failure modes:
1. The brand on the package changes. The license number doesn't. Three different brand-and-cultivator relationships appear across the eight recalls. The licensee field on every recall page lists the same Type-11 distributor. That is a structural signal about which step in the pipeline is failing, not a brand-quality story.
2. The reason language splits cleanly into two phases. Recalls 1 through 3 (December 2024 through February 2025) are both microbial and "Inaccurate Labeling (Cannabinoid inflation)." Recalls 4 through 8 (March through July 2025) are pure Aspergillus. Something in the labeling pipeline either got fixed, got quieter, or stopped being a regulator focus around late March. The mold story didn't.
3. The classification flips at recall 4. The first three recalls were voluntary. Beginning 2025-03-28, every subsequent recall is mandatory. That transition from licensee-initiated to regulator-ordered is its own enforcement event, and it has procedural consequences that are now playing out in California Superior Court.
What "Inaccurate Labeling (Cannabinoid inflation)" actually means
The verbatim phrase "Inaccurate Labeling (Cannabinoid inflation)" appears on three of these recall pages. That phrase is regulator-coined. It does not appear in 4 CCR. DCC made it up to describe what they were seeing.
What it means in practice: the cannabinoid number printed on the package was higher than the lab's certificate of analysis supported. That can happen in three places:
- At the lab. The COA itself is wrong (rare; labs are licensed and audited).
- In the data layer between lab and label. The wrong field from the COA was pulled into the print job. The most common version of this is Total Cannabinoids being substituted for Total THC, or vice versa. They are different numbers. They live next to each other on every COA. Operators conflate them because the chemistry is non-obvious unless you've been forced to learn it.
- At the printer. The print template references the wrong column, or a hardcoded value got stale across batches.
None of these is a "the operator is lying" story. They are integration bugs. Each one happens at a hand-off: lab to ERP, ERP to label generator, label generator to printer. The DCC doesn't care which hand-off broke; the recall lands on the distributor of record either way, because Type-11s own QA at the packaging step.
The reason recalls of this kind fall on the distributor and not on the cultivator or lab: under the post-2021 consolidated DCC framework, the distributor performs the regulated QA step. Whoever runs the label is the entity holding the bag.
The microbial story is older and harder
Aspergillus appears on every single one of the eight recalls. Microbial contamination is upstream of the distributor. It's a cultivation, drying, and curing problem. But it surfaces at the distributor's QA-and-release step. Two questions a distributor's compliance team has to answer when this pattern appears:
- Is the batch being released against the correct, in-date COA? Aspergillus is on the Category III microbial panel; a batch can pass once and get re-tested later if storage conditions change. Releasing against a stale COA is a self-inflicted recall.
- Is the Metrc package tag genuinely tied to the tested lot? The unbroken chain from tested-batch to Metrc tag to ERP record to label is the entire compliance argument. Any drift between those four states is what enforcement actions look for.
The 2025-07-17 recall is unusual because it names Aspergillus flavus and Aspergillus niger by species. DCC almost never specifies species in recall language. They normally say "Aspergillus spp." That kind of specificity normally means the lab re-test came back fast and the regulator wanted the record to be unambiguous. Read it as a tell about how closely a license is being watched once a pattern is established.
The follow-on citation
In late 2025, the DCC's public compliance-action records page added a Citation and Fine against this same licensee for six code violations. The sections cited:
- 4 CCR § 15042. Premises Access Requirements, Unescorted Non-Employees
- 4 CCR § 15048.5. Use of Harvest Batch Name and Package Tags
- 4 CCR § 15305. Testing Sample, Licensee Presence During Sample Collection
- 4 CCR § 15305. Testing Sample, Video Recordings
- 4 CCR § 15305. Testing Sample, Licensee Shall Not Assist Laboratory Employee
- 4 CCR § 15314. Shipping Manifests
Read those six together. They are not a paperwork mistake. They describe a regulator's allegation that the chain of custody from sampling through release through shipping was not correctly documented or supervised. Three separate § 15305 counts on testing-sample protocol is a regulator saying we believe the integrity of how product was sampled for testing was compromised. That is the same surface area as the recalls.
The compliance-action page lists the citation as on appeal. Whatever the resolution, the public record now contains a regulator's structured allegation about exactly the pipeline that was producing recalls.
What an operator should take from this
Three structural lessons:
1. Recall liability concentrates at the distributor, regardless of where the failure originates. A cultivator can have mold. A lab can issue a stale COA. An ERP can pull the wrong column. The recall page names the packaged-by entity. If you are a Type-11, the failure modes of every upstream and downstream partner show up on your license number.
2. The label pipeline has more failure points than most distributors model it as. Lab to Metrc tags to ERP to label generator to printer is five hand-offs. Each hand-off is a transformation, and a transformation is a place a wrong number can be substituted. The "Inaccurate Labeling (Cannabinoid inflation)" cluster of December 2024 through March 2025 is what that failure mode looks like at scale, on regulator letterhead.
3. The signal worth tracking is not recall count. It's the verbatim language. "Adulterated" alone is a chemistry/biology problem. "Misbranded" is a labeling/data problem. "Inaccurate Labeling (Cannabinoid inflation)" is a specific regulator-coined phrase pointing at a specific data-pipeline failure. When that language appears in your sub-segment, the pipeline issue is becoming an enforcement priority. It tends to be followed by procedural citations on the same license, as this case shows.
The eight-recall pattern, taken with the citation that followed, is the public-record example of how DCC enforcement progresses against a single license once a failure mode is established. Any California distributor reviewing their own QA-and-release stack should read it as a map of where regulator attention concentrates after the first recall lands.
Sources used in this article are public DCC pages: the recalls portal at recalls.cannabis.ca.gov and the compliance-action records page at cannabis.ca.gov/cannabis-laws/compliance-action-records/. Verbatim DCC language is reproduced as it appears on those portals as of 2026-05-09.