The Last Mile: Nine Retail Fields, One Customer COA (Proposed DCC Track-and-Trace, 4 CCR §§ 15049.4 & 15404.1)
Status: Part of the DCC’s proposed track-and-trace overhaul, DCC-2026-02-R (noticed June 5, 2026). This introduces two new sections governing what a retailer records at the point of sale (§ 15049.4) and hands a customer on request (§ 15404.1). Not yet adopted law. Public comment is open through July 20, 2026; hearing July 21. [1]
This is the sixth and final change in the proposed overhaul, and the only one that lands entirely after your product leaves your hands. You are not a retailer, and neither section is addressed to you. Both are written for the licensed retailers and microbusinesses that sell what you make and move. Read this as a map of what your retail accounts are about to be required to record and show — and what that new visibility means looking back up the chain to you.
Where the Retail Record Stands Today
The nine “tax” fields your accounts would record already exist in the track-and-trace system. The California Department of Tax and Fee Administration (CDTFA) built them in mid-2022 and uses them to check a retailer’s recorded sales against the gross receipts on their tax returns. [5]
The catch is that recording them has been voluntary. Per the Department, only a handful of retailers use the fields, and the data is often wrong. CDTFA reports gross receipts sometimes diverge from the track-and-trace figures by as much as 30%, which triggers a full audit. Today, the sell-through record on goods you produced is patchy and unreliable. [2]
On the Certificate of Analysis (COA) side, your retail accounts already have every product’s testing data available to them in the system. Nothing in current law requires them to hand a customer a copy. Many do not — which means the test data on your product usually stops at the counter.
What the Proposed DCC Rule Changes
The proposal adds two new sections. Neither adds a task to your license; both add visibility around your goods. [1]
Nine retail sales fields become mandatory, defined, and enforceable (§ 15049.4). For every retail sale, the licensee must enter nine fields into track and trace: the invoice number, the retail price before discounts and taxes, the state excise tax, the local business tax collected by the city, the same for the county, the same for the municipality, any discount, the subtotal, and the sales tax. The fields are not new. What changes is that recording all nine becomes mandatory for every sale, each field is defined in regulation, and the Department gains a mechanism to enforce it. [2]
A customer can ask for your product’s COA (§ 15404.1). On request from a customer, a retailer or microbusiness must provide a copy of the COA for any cannabis goods offered for sale. The COA carries the complete test results — every analyte and the specific cannabinoid potency the laboratory reported. [1]
What It Means for Your Operation
You never touch these nine fields, but they change what the state can see about how your goods actually sell. Once every retail sale carries a defined, mandatory price-and-tax record, the sell-through data on your products stops being patchy and becomes auditable. It ties back through the distributor transfer to the batch you entered. A discrepancy that used to die at the register now has a paper trail that runs up the chain. The entry discipline you have built finally has a matching record at the far end.
And the COA on your product becomes a document a stranger can ask to see. When a customer at the counter requests it, your test results go into their hand. A COA used to be a compliance artifact; this rule makes it part of the buying decision. The operators who benefit are the ones whose COA is clean, current, and worth showing.
Comparing the Retail-End Rules
| Element | Current law | Proposed DCC-2026-02-R |
|---|---|---|
| Retail sales fields | The nine tax fields exist, but recording is voluntary and often inaccurate. | All nine mandatory for every retail sale, each defined by regulation (§ 15049.4). |
| The nine fields | No regulatory definition or user guidance. | Invoice #, price before tax/discount, state excise, city tax, county tax, municipal tax, discount, subtotal, sales tax. |
| Enforcement | None — a handful of retailers record voluntarily. | Department can enforce the recording mandate (§ 15049.4(a)). |
| Customer access to COA | Retailer holds the COA; no duty to share it. | Must provide a COA copy on customer request (§ 15404.1). |
| Who records / acts | Your retail accounts, downstream of you. | No change — still your accounts, not you. |
Regulations Are Optimizers in Disguise
Rules reveal what the business was already missing. The last two records in the chain were the loosest. Clean entry, a two-sided transfer, one lab and one sample, a batch you can’t re-shop — these built a chain of custody that ran hard right up to the register, then went quiet. These two sections close that gap.
For you, mandatory retail data means the story of how your goods sell finally becomes legible, and a COA a customer can pull is a standing reason to make yours worth pulling. The upstream operator who comes out ahead is not the one who does more work at the counter. It is the one whose data and COA are already clean when they arrive there.
A chain of custody that goes dark at the register was never a full chain.
The Standing Practice
Make the batch and package data you hand your distributor accurate enough to survive a field-level retail record. Treat every COA as a document a customer might read, not a form a lab files. Know which of your retail accounts already record and share; an account that keeps a clean counter is one that will not generate the discrepancy that traces back to you.
Closing the Series
This is the last of six changes in DCC-2026-02-R, and the discipline underneath all of them is a single thing. Clean entry at your bench, an honest two-sided transfer to your distributor, one lab and one sample, a batch you can’t re-shop, accurate data at every hand-off, and now a retail record and a COA that hold up at the counter — it is one chain, and it is only ever as strong as the record you start. Every post in this series has traced the same line from a different link.
Six sections, one discipline — from the batch you enter to the page a customer holds.
What We Don’t Know
Because this is still a proposed rule, the text is not final. We do not know if public comment will alter the nine mandatory fields, adjust the enforcement mechanisms, or change the COA access requirements before the rules are formally adopted.
Two Ways to Weigh In
The public record. If the retail-recording mandate or the COA-on-request rule intersects your operation, that is exactly the operating reality the public record exists to capture. Written comment is open through July 20, 2026, with a hearing on July 21. Submit yours by email to publiccomment@cannabis.ca.gov and reference the rulemaking number, DCC-2026-02-R. The comments that carry weight are specific: name the field or the COA requirement, and describe how it lands on a real batch-to-retail data trail — yours. [1]
The Blueprint conversation. No. 09 closes the six-post arc, and we want to hear what actually changed for your operation across it. Add your read in the comments on our LinkedIn, or tag #FreedUpBlueprint with the one section from the series that hit your operation hardest. The best operator questions become the next thing we write.