Locked Batches: Why a Batch Stays Bound to Its Test Result (Proposed DCC Track-and-Trace Rules, 4 CCR §§ 15306–15307)
Status: Part of the DCC’s proposed track-and-trace overhaul, DCC-2026-02-R (noticed June 5, 2026). These are proposed amendments to the compliance-testing-results and quality-assurance-review sections (§§ 15306–15307) and are not yet adopted law. Public comment is open through July 20, 2026; hearing scheduled for July 21. [1]
Of the six changes in the proposed track-and-trace overhaul, this is the one that decides whether a result—passing or failing—stays attached to the batch that earned it. For California cannabis distributors, and the manufacturers and cultivators who ship to them, DCC-2026-02-R closes a gap that has historically allowed a batch to be quietly re-created in the track-and-trace system to shed an unfavorable result.
Where Track-and-Trace Stands Today
The lock already exists on one stage. Under current § 15306(b), once a batch has passed regulatory compliance testing, it may not be repackaged into a new production batch in the track-and-trace system, nor assigned a new batch number. That is existing law, and it is not changing. [3]
What today’s rules leave open are the other two stages of a batch’s life. The current section says nothing about a batch that is still in testing, and nothing that stops a distributor from electronically creating a new production batch from a batch that has failed.
Around those open ends, the ordinary mechanics run as they do now: a distributor stores the batch on its premises until it passes or fails. By the Department’s own account, these open ends get used. A distributor who is unhappy with a result—or who has been told by a laboratory that a sample will not pass or will read lower in potency than desired—can electronically repackage the tested batch into a “production batch.” Doing so disassociates the prior test results, flagging the batch as “Not Submitted” for testing. The distributor can then arrange for the “new” batch to be re-sampled and re-tested by a different laboratory. [2]
What the Proposed DCC Rule Changes
The draft extends the lock to the two stages it previously did not cover, anchoring the batch at three specific points. [1]
In testing (§ 15306, new subsection (b)). A licensed distributor may not physically or electronically repackage a batch that has been submitted for or is undergoing regulatory compliance testing. This core provision stops a batch from being severed from its result before the result is even final. [1]
After a failure (§ 15306, amended — today’s (d), relettered to (e)). A licensed distributor may not electronically create a new production batch in the track-and-trace system from a batch that has failed testing. A manufacturer may still repackage a failed batch into a production batch as part of a Department-approved § 17305 remediation plan; that path is fully preserved. [2]
Numbers must match at QA review (§ 15307, new subsection (a)(2)). During quality-assurance review, if a manufactured product carries a production batch number in the track-and-trace system, the distributor must confirm it matches the number on the product’s COA and the number printed on its label. This closes the drift that lets the system record and the paperwork diverge—a mismatch that today causes transfer bottlenecks and slows Department investigations. [2]
The passed-stage lock has been law since 2022. What is new is that a batch is now bound to its result across its entire lifecycle: while it is in testing, once it has passed, and after it has failed. [3]
Comparing the Lifecycle Locks
| Batch stage / element | Current law | Proposed DCC-2026-02-R |
|---|---|---|
| Batch in testing | Not addressed — can be repackaged into a “production batch,” disassociating prior results. | May not be physically or electronically repackaged while submitted for or undergoing testing (§ 15306(b)). |
| Passed batch | Already locked: no new production batch, no new batch number (§ 15306(b)). | Unchanged — same lock, relettered to (c). |
| Failed batch | May be electronically re-created as a new production batch. | May not create a new production batch from a failed batch (§ 15306(e)); § 17305 remediation path preserved. |
| QA batch-number check | COA must carry the label’s production batch number (§ 15726), but the CCTT number can drift. | QA reviewer must confirm the CCTT number matches the COA and the label (§ 15307(a)(2)). |
| COA distribution | Provided to all receiving distributors and the producer (§ 15306). | Unchanged. |
Regulations Are Optimizers in Disguise
A regulation is a forcing function. The old story is that locking a batch to its result removes flexibility. The Freed Up frame is that the lock protects the one thing the whole supply chain is pricing on: that a COA means exactly what it says.
When a result can be shed by re-batching, every COA downstream carries a quiet asterisk. When it cannot, a passing result is worth what the market pays for it, and a failing result cannot be laundered back into inventory to undercut the operators who test honestly.
A result you can re-batch around is a result no one downstream can trust.
For the operator, a batch cleanly bound to its record is fundamentally cheaper than the re-tests, reconciliation, and disputes that a severed link invites. Fixing the audit risk and fixing the unit economics are the same project. The work of compliance—done well—is the work of becoming a better business.
The Standing Practice for Locked Batches
The operators who will barely feel this proposed shift are the ones who already treat a batch number as permanent.
The standing practice is straightforward: assign a batch its identity once, keep the batch record intact from production through disposition, never build a financial plan around re-creating a batch to escape a result, and when a batch fails, run it strictly through the § 17305 remediation path. An operation already keeping clean batch production records and maintaining an inspection-ready standing file has most of this muscle memory already built.
Weighing In on the Public Record
Because this is still a proposed rule, the final framework is not yet set. We do not know what the final adopted text will look like. If the ban on repackaging a batch that is in testing collides with a legitimate operational step your product genuinely requires between sampling and result, that is precisely the operating reality the public record is built to capture. Written comment is open through July 20, 2026, with a hearing on July 21. [1]