1. Excise and municipal tax stacking
What CA requires: California charges a 15% state cannabis excise, administered by the California Department of Tax and Fee Administration (CDTFA). AB 564, signed September 2025, reversed a planned increase to 19% and returned the rate to 15% effective October 1, 2025, stable through 2026. On top of the state excise, cities and counties stack their own municipal cannabis taxes that vary by jurisdiction, plus local sales tax. An operator selling across several California jurisdictions calculates a different total at each one.
What SellStack does natively: SellStack calculates the 15% state excise and the applicable municipal and sales tax per jurisdiction at product configuration, so the correct total is applied at the point of sale rather than reconciled afterward. Each location is configured once.
What this means for your operations: You stop hand-reconciling tax across jurisdictions, and a statewide rate change like AB 564 is a configuration update, not a spreadsheet project.
Request a demo for California operations →
2. Distributor middle-tier coordination
What CA requires: California is one of the few adult-use states with a mandatory distributor tier. Product moving between cultivators or manufacturers and retailers has to pass through a licensed distributor, which coordinates the transfer and generates the manifest. Whether you run a Type 1 specialty cottage cultivation or a Type 5 large operation, product bound for retail goes through the distributor step, and you either hold that license yourself or coordinate with a licensed distributor for every transfer.
What SellStack does natively: SellStack builds distributor coordination into product movement. Transfers, approvals, and manifest generation run in the same ledger as the rest of the operation, whether you hold the distributor license or work with one.
What this means for your operations: The distributor step is part of your workflow, not a separate system to reconcile against, so product moves through the middle tier with its lot record intact.
Request a demo for California operations →
3. Metrc reconcile, not dependence
What CA requires: California's state track-and-trace system is Metrc. In December 2025, an Orange County Superior Court writ ruled that the DCC's current use of Metrc does not comply with California law, which triggered an active DCC rulemaking to address the system. Operators have to keep meeting Metrc requirements today while the system itself is under revision.
What SellStack does natively: SellStack treats its own ledger as the source of truth and reconciles Metrc from it, rather than building inventory logic on top of Metrc. Metrc records reconcile against the ledger you already run on, not the other way around.
What this means for your operations: When DCC changes how Metrc works, and it is changing, your inventory logic does not have to be rebuilt. You adapt the reconciliation, not your whole operation.
Request a demo for California operations →
4. Type 9 delivery operational logic
What CA requires: California's Type 9 non-storefront retailer license is delivery-only, with specific constraints: deliveries run on dedicated vehicles with directly employed drivers (no third-party delivery services), only to physical California addresses, and never to schools, youth centers, parks, daycares, or other restricted locations. No more than $5,000 of cannabis value may be in a vehicle at any one time. Storefront retailers carry their own delivery rules by local authorization.
What SellStack does natively: SellStack enforces the Type 9 rules in the delivery workflow. It assigns directly employed drivers, tracks the $5,000 per-vehicle cap, and checks delivery addresses against the restricted categories before a route is committed.
What this means for your operations: The constraints that make Type 9 easy to violate are enforced by the system on every delivery, not left to a dispatcher to remember.
Request a demo for California operations →
5. State DCC and local dual-authorization
What CA requires: Every commercial cannabis activity in California requires both a state DCC license and a separate local-jurisdiction authorization. Neither stands alone; an operator cannot legally operate without both, and the local permit is as load-bearing as the state license. The two run on separate renewal and expiry clocks.
What SellStack does natively: Operator and entity records carry both the state DCC license and the local jurisdiction authorization, with their separate statuses and expiry dates. A lapse or approaching expiry on either side triggers an alert before it becomes an operating problem.
What this means for your operations: You track both halves of your authorization in one place, so a local permit renewal does not slip while everyone is watching the state license.
Request a demo for California operations →
6. Per-municipality social equity
What CA requires: California's social equity framework is local-first. Rather than one statewide allocation, 38 jurisdictions as of 2026 each define their own equity program, with their own qualification, fee waivers, technical assistance, and reporting. A multi-jurisdiction operator may qualify for equity in one city and not another, and each program reports separately.
What SellStack does natively: Operator records carry per-municipality social equity classifications, not a single equity flag, and reporting flows per jurisdiction to match how the programs actually run.
What this means for your operations: A multi-city operator tracks each jurisdiction's equity status and reporting in one system, instead of keeping a separate file per city.
Request a demo for California operations →
7. Adapting as DCC rules change
What CA requires: California cannabis rules are in constant motion. In 2026 alone, the DCC has a pesticide-testing standard that landed October 1 (DCC-2025-03-R), a proposed group-tagging rule (DCC-2026-03-R), a proposed rule requiring all parties to approve a transfer before a manifest is generated and retailers to enter tax information and provide COAs on request (DCC-2026-02-R), and the Metrc rulemaking driven by the December 2025 court writ. Operators have to keep up with each one.
What SellStack does natively: SellStack absorbs these changes in its configuration layer rather than in operator-side code. When an action level, a transfer-approval step, or a COA-on-request rule changes, the configuration is updated and operators keep working.
What this means for your operations: A DCC rule change becomes something your platform adapts to, not a development project you fund, so the pace of rulemaking stops being an operating risk.
Request a demo for California operations →
Also in motion: federal Schedule III
Medical cannabis moved to Schedule III federally, effective April 28, 2026, and it is in effect now for California medical operations. Adult-use rescheduling is still pending; the DEA proceeding was stayed September 29, 2026 awaiting a GAO report, with a decision expected late 2026 or early 2027. For California medical operators, the practical effect is that GMP-grade records start to matter, and the records half of GMP is a byproduct of running on one lot-level ledger.