Metrc to Flag Irregularities: The Other Half of Track-and-Trace (Bus. & Prof. Code § 26067)

Status: this is a court judgment, not a new rule. Nothing in this post is a regulation, and nothing in it changes a licensee’s reporting obligations. It is a final judgment entered August 4, 2026 in HNHPC, Inc. v. Department of Cannabis Control (Orange County Superior Court, No. 30-2021-01221014), ordering the Department to fix the state’s own half of the system. [4][5][6] The legal duty it enforces comes from a published Court of Appeal opinion in the same case [2] and from statute [1]. No appeal has been reported as of publication, and the appeal window has not closed. The judgment document itself was not obtained; its terms are as described by plaintiff’s counsel and reported by trade press, and are framed that way throughout. [4]

For six posts, this series has read one half of California’s track-and-trace system — the half that runs against you. Tags and transfers, sampling chain of custody, locked batch states, data-entry windows, retail COA data. On August 4, 2026, an Orange County judge finished reading the other half. The Department of Cannabis Control was ordered to make the state’s track-and-trace system do something the statute has required of it since the program was written: flag irregularities for investigation. [1][4][5] The court gave the Department six months. Your reporting duties did not change. What the system does with what you report is about to.

Where It Stands Today

The statute is short and it is not ambiguous. Business and Professions Code § 26067(b)(2) reads, in full: “The electronic system shall be designed to flag irregularities for the department to investigate.” [1] That is one sentence, and it is a duty the Department owes — not one you owe. It sits inside the subdivision that builds the electronic shipping-manifest system, immediately after the list of what that system must capture.

The section was amended effective January 1, 2026 to fold industrial hemp in throughout (Stats. 2025, Ch. 592, Sec. 35.5 — SB 861). [1] The earlier version said “database” where the current version says “electronic system.” The flagging mandate itself did not change. Court opinions written before 2026 quote the older word. [2]

The duty is also ministerial, and that word is doing real work. In 2023 the Court of Appeal held in this same lawsuit that § 26067 does not leave the Department room to decide whether to build flagging in — it requires it. The Department had argued that its contracts to develop a track-and-trace system showed compliance. The court held that the Department “did not have a duty to enter into a contract but to establish an electronic database that actually flags irregularities.” [2]

What the system does today, as the court found it: Metrc captures transactions and generates reports and raw data. What it does not do is automatically identify potentially irregular activity against objective criteria. Finding an irregularity requires someone to go looking — analysts reviewing data by hand, without an established definition of what counts as irregular. [4][5][6] That gap between recording and noticing is the entire case.

What the Court Actually Ordered

This is a two-beat story, and most coverage collapses it into one.

December 9, 2025 — the merits

After a November 2025 trial, the court ruled that the Department’s use of Metrc does not comply with the flagging requirement. [4][5] That decision established the violation; it did not yet fix it.

February 6, 2026 — implementation

A status conference took up what compliance would actually have to look like. [4][5]

August 4, 2026 — final judgment

The court gave the Department six months to establish objective criteria defining an irregularity, so that the system can detect and flag suspect transactions without requiring manual review. [4][5][6] Six months from entry lands at approximately early February 2027.

Two things the judgment did not do, both of which have been reported loosely elsewhere. It did not order California to replace Metrc — the Department may configure or supplement the existing system to perform the flagging function. [4][5] And it did not touch a single licensee obligation. No new report, no new field, no new deadline for you.

Today vs. After the Clock Runs — for a California Licensee

Regulations Are Optimizers in Disguise

It is easy to read this as somebody else’s problem. The Department got ordered; you did not. That reading misses what changes underneath you.

A system that only records treats every operator identically. Your transfer reconciliations, your entry timing, your batch-state discipline — all of it has been, functionally, invisible to the state between inspections. It sat in a database that nobody queried unless something else drew attention first. Careful and careless looked the same from the outside.

A system that records treats every operator the same. A system that flags does not.

Objective criteria change that. Criteria are rules, and rules do not skim — they compare. Quantity variances that reconcile, timestamps that fall inside the window, batch states that match the physical product: those stop being your private housekeeping and start being the thing that keeps your record quiet. The operator who has been doing this well for three years has already built the asset. The operator who has been closing gaps at audit time is about to find out that the gaps were logged.

Regulation is not creating that advantage. It is making it legible.

The Standing Practice

Nothing here is a new obligation. All four are worth having in place before the criteria exist, because you cannot retrofit history.

• Assume your data will be read by a rule, not a person. Objective criteria mean thresholds and patterns — variance percentages, timing windows, transfers that do not reconcile at both ends. The small drift that survives a human skim is exactly what a rule catches.
• Reconcile at the handshake, not at audit. A transfer that both sides recorded the same way is a non-event. A transfer that only reconciles after someone fixes it later leaves a record of having been fixed later — which is why the 30-day reconciliation cycle is worth running on schedule rather than on discovery.
• Keep batch states honest in real time. State changes recorded when they happen produce a clean sequence. State changes recorded in a catch-up batch produce a pattern — and patterns are what criteria are built to find.
• Be able to explain your legitimate anomalies. Real operations produce real irregularities: moisture loss, destruction events, returns, equipment failure. A flag is an invitation to investigate, not a finding. The operator who can hand over the documentation that explains an anomaly closes it in one exchange.

What We Don’t Know (and What’s Still Moving)

There is no public comment window on a court judgment — this is not a rulemaking, and there is nothing for an operator to file. What there is, is a watch list of things that are not yet publicly known.

• Whether the Department appeals. No appeal has been reported as of publication. Plaintiff’s counsel has publicly predicted the Department may appeal and could extend the dispute by another one to two years. [4] Under California Rules of Court, rule 8.104, a notice of appeal is due 60 days after service of notice of entry, with an outer backstop of 180 days after entry — which from the August 4 judgment runs to roughly the end of January 2027. [7]
• What the criteria actually say. This is the part that touches your records. “Objective criteria defining an irregularity” is the whole story, and none of it is written yet.
• How the criteria arrive. If they come through formal rulemaking, there will be a comment period and a public record. If they come through internal system configuration, there may not be. Worth watching which path the Department takes.
• The outcome of DCC-2026-02-R. The proposed track-and-trace rulemaking that governs how operators record data closed its comment period on July 20, 2026 and has not produced a final statement of reasons. [3] The state’s half of the system is now on a court’s clock; your half is still on the Department’s.
• Approximately early February 2027. Six months from the August 4 judgment. That is the date to have on your calendar — not a compliance deadline of your own.

Last verified: August 20, 2026 — no notice of appeal reported as of this date. This post is re-checked when the record changes.