A working compliance checklist for California Type 11 distributors.

A Type 11 license is California’s commercial cannabis distribution license, issued by the Department of Cannabis Control (DCC). It authorizes a licensee to take possession of cannabis goods from cultivators, manufacturers, and other distributors, and to move those goods through the regulated supply chain to retailers.

Three things every Type 11 distributor is responsible for, regardless of size or business model:

• Track-and-trace. Every package that enters or leaves a Type 11 licensee’s possession must be recorded in Metrc, California’s seed-to-sale tracking system. Package state, transfer manifests, and inventory adjustments all live in Metrc.
• Quality assurance and label review. A Type 11 distributor takes possession of finished goods before they reach retail. The distributor coordinates the regulatory QA testing (the lab does the testing and submits it to Metrc; the distributor arranges sampling and tracks the result). Many distributors also run their own internal QC testing in parallel — for pre-screening, supplier monitoring, and operational signal — but only the regulatory lab’s submission to Metrc is the regulator-valid number. The distributor verifies products are properly labeled and accompanied by valid lab paperwork before release.
• Transport. Type 11 includes the right to physically move cannabis goods between licensees on permitted routes, in compliant vehicles.

The license sits at the choke point of the supply chain. Almost every regulated cannabis product in California passes through a Type 11 licensee at least once before reaching a consumer. That position is why the recall-prevention surface is so concentrated here.

Metrc is the system of record. If Metrc and reality disagree, Metrc is what the regulator sees. Reality has to come into alignment, not the other way around.

Every Metrc tag is a unique URL, and that URL is supposed to appear as a unique QR code on every individual product label. No duplicates, no batch-shared QRs across thousands of units. A regulator scanning the QR at retail expects to land on the public Metrc traceability page for that specific unit. If two products carry the same QR, or a QR that doesn’t resolve to the matching package, the chain of custody is structurally broken — every downstream document is suspect. That uniqueness is the backbone of California cannabis traceability, and label-pipeline failures that produce duplicate or mismatched QRs are recall-worthy in the same way as a wrong THC number.

Three places Metrc reconciliation goes wrong, in order of frequency:

1. Package state drift. A package’s status in Metrc — active, in-transit, finished, destroyed — should match its physical and operational state. When the floor moves a package and the system doesn’t catch up, every downstream report carries that drift forward.
2. Transfer manifest mismatches. The package quantities and weights on a manifest should agree with the package records they reference, and the package records should agree with the COA and the physical inventory. Split shipments, mid-route adjustments, and re-weighs all create opportunities for the manifest, the package record, and the goods to diverge.
3. Tag-to-label binding errors. Each Metrc tag binds to a specific package. The label generator has to pull the right tag URL into the right unit’s QR. A field-map drift, an ERP-side intake error, or a batch-level QR that gets reused across units are all variants of the same failure: the unit’s identity in Metrc and on the label diverge.
4. Late entries. Metrc has timing expectations. Adjustments and transfers entered hours or days after the operational event become harder to defend if a regulator asks why the digital record lagged the physical one.

The fix isn’t usually new software — it’s tightening the loop between what happens on the floor and what gets entered in Metrc, and verifying that the unique tag a package was issued is the unique tag that ends up on its label. The failure-modes page has worked examples of where the loop breaks.

Forty-two percent of California cannabis recalls in the last twenty-eight months cite a label or cannabinoid-pipeline failure. The full data, with sources, is here.

For a Type 11 distributor, the label pipeline is the failure surface that costs the most when it breaks. The label is what the regulator photographs. The label is what the consumer reads. The label is what shows up in the recall notice.

Four things to verify about the label pipeline that most Type 11 operators have not formally documented:

1. The field-map between the COA and the label. Every field on the printed label that pulls a value from the COA — cannabinoid percentages, lab name, batch ID, expiration date — should have a documented source. “The integration handles it” is not a documented source.
2. The configuration of the label generator. Most label-design tools (BarTender, Loftware, NiceLabel, custom systems) have configurable per-field calculations. Get the configuration in writing. Confirm it matches the field-map.
3. The printer fleet’s firmware and stored-format state. Stored-format mismatches between printers in a fleet produce labels that look correct on one machine and wrong on another. Fleet-wide config diffs should be a quarterly check, not an incident-driven one.
4. The pre-print preview as a compliance control. Before a run goes to the printer, somebody should be able to see what the label will look like — not just confirm that the print job started. A preview is a compliance control, not a UX nicety.

None of this is glamorous work. All of it is the difference between a clean compliance posture and a recall.

An unannounced DCC inspection is not the time to reconstruct your records.

Audit-readiness for a Type 11 distributor isn’t a one-time project — it’s a posture. The simplest test of whether you’re ready: pick a random package from Metrc that left your warehouse last quarter, and try to assemble its full paper trail in fifteen minutes. The COA. The intake record. The label that was printed. The transfer manifest. The destination acknowledgement.

If that takes more than fifteen minutes, the gap is documentation discipline, not regulation. Closing the gap is operational work, not legal work.

Pre-inspection audits — walking your floor and your data the way an inspector would — are one of the most common engagements I take. How an engagement works.