01 · Package
Package-level variance report
Every open package reconciled against physical inventory; variance flagged by magnitude.
Package-to-package variance analysis, transfer-manifest review, loss-and-destruction log audit, and physical-to-digital inventory reconciliation.
METRC reconciliation is never a tag count. It's a forensic reconstruction across four evidence streams — the physical inventory on the floor, the METRC package ledger, the transfer-manifest log, and the CCR 15048 waste-and-destruction record — under a single timeline. Where they disagree, the variance has a root cause, and the root cause has a name. We take ownership of all of it.
Owning the work means four concrete things. We walk the floor with a scanner and a printed package list, reconciling every open METRC tag against physical presence, weight, and product form. We audit every inbound and outbound transfer manifest against METRC records and the CCR 15307 chain-of-custody requirements, flagging mis-keyed weights, late departures, and missing driver sign-offs. We reconcile the CCR 15048 waste log against destruction events in METRC so the trash-bin reality matches the ledger reality. And we trace every variance back to a named root cause — SOP drift, equipment miscalibration, training gap, POS-to-METRC integration failure, or intent — with a remediation owner and a date.
What you keep: inventory management decisions, sales cadence, POS and ERP selection, and any HR action arising from a finding. Where counsel is needed — variance material enough to require a voluntary-disclosure path, any CDTFA excise reconciliation exposure, any finding that rises to theft or diversion — we work under counsel's direction or introduce one from our retained network.
Figures from the DCC Feb 5 2025 enforcement recap, CCR Title 4 Division 19 (§§ 15046 track-and-trace, § 15307 transfers, § 15048 waste), and operator-side benchmarks on quarterly reconciliation.
Every figure below is sourced to the DCC, the CCR, or operator-side reconciliation benchmarks. Drift compounds silently; the four patterns below are where unprepared operators cross the 2% variance threshold before they know it.
Staff round weights to whole grams, trust the POS auto-deduct, or skip the pre-transfer re-weigh that catches moisture loss on dried flower. Individually noise; collectively a CCR 15046 track-and-trace finding. (CCR 15046)
Inbound tags accepted without a weight reconciliation, outbound manifests departed before the driver signature, rejected transfers never reversed in METRC. The single most common cause of distributor-side variance. (CCR 15307)
Destruction events batched weekly or monthly instead of recorded at the event. METRC and the physical waste bin tell different stories on audit day — the exact gap auditors hunt for. (CCR 15048)
Above 2% aggregate variance, DCC pulls the full package ledger, manifests, and destruction log for the year. With no forensic record to explain drift, variance becomes willful noncompliance at renewal review. (DCC Disciplinary Guidelines)
Our job is to never put you above the 2% threshold. Physical walk first, METRC ledger second, manifest log third, CCR 15048 waste record fourth. Every variance traced to a named root cause with a remediation owner. Under 1% filed; 1–2% remediated; over 2% briefed to you verbally first so the disclosure path is your call, coordinated with counsel.
Every open package reconciled against physical inventory; variance flagged by magnitude.
Inbound and outbound manifests audited against METRC records; gaps flagged.
CCR 15048 waste records reconciled against destruction events in METRC.
On-site inventory walk matched against METRC tags; any untagged product identified.
Where variance traces to SOP drift, the specific SOP step is called out.
Floor team retraining on the specific procedures that caused variance.
Integration adjustments between POS/ERP and METRC where the variance is technical.
If variance is large: a formal CAPA documented and filed internally.
Monthly check-in on variance trend; quarterly deeper audit.
A one-page board-ready variance report for each audit cycle.
Beyond the variance report itself, operators leave each cycle with a cleaner ledger, a trained floor, and a forensic archive that pays dividends at the next DCC inspection, the next CDTFA review, and the next diligence event. Here’s the practical shape of that.
When DCC field staff questions a destruction timestamp, we cite the section. When CDTFA reviews the excise-tax reconciliation against the METRC transfer log, they see CCR references embedded in every variance memo. When counsel evaluates whether a finding rises to a voluntary-disclosure event, the regulatory chain — tag → package → manifest → destruction → retention — is documented in full.
California track-and-trace sits at the intersection of BPC Division 10 (MAUCRSA, with BPC 26067 establishing the mandatory program and BPC 26031 framing self-disclosure), CCR Title 4 Division 19 (CCR 15036 designating METRC as the system of record, CCR 15046 for user obligations, CCR 15048 for waste and destruction, CCR 15307 for transfer manifests, CCR 15311 for distributor hub operations, CCR 15037 for records retention), the DCC forms layer (DCC-LIC-019 SOPs, DCC-LIC-017 CAPAs, DCC-LIC-027 modifications), and the METRC v2 REST API itself. Each layer has its own document convention and its own audit consequence. We track all four simultaneously.
Well-run operations stay under 1% aggregate variance. The 1–2% band is worth investigating but is not yet a crisis. Above 2%, DCC typically pulls the package ledger, transfer manifests, and the CCR 15048 destruction log for the year under CCR 15036 track-and-trace authority. Our post-remediation engagements typically close below 0.5%, and the trend matters as much as the absolute number — a stable 1.2% with an explained driver beats a fluctuating 0.6% with no documented cause.
We audit across every major cannabis POS and seed-to-sale ERP. Where variance traces to the integration layer — Franwell API field mismatches, sync-cadence drift on GET /packages/v2/active, sales-receipt batch failures against the 24-hour reporting requirement, or POS auto-deduct misfires — we specify the exact field, endpoint, and sync window that needs to change. Implementation is run by your IT team or ERP vendor; we hand over a written specification with citations to METRC v2 endpoints (e.g., POST /sales/v2/receipts, PUT /packages/v2/adjust) and a named responsible party in your stack. We do not write integration code.
We brief you verbally before anything is written. Material variance can rise to voluntary-disclosure territory under DCC’s September 2021 Disciplinary Guidelines, where the per-violation, per-day ceiling is $5,000 for licensees and the regulator weighs self-reported remediation as a mitigating factor under BPC 26031. The disclosure decision is yours in coordination with retained counsel; we produce the underlying record — the package-level variance export, the CCR 15307 manifest defects, the CCR 15048 destruction discrepancies — that supports whatever path you and counsel choose. Where the variance pattern looks like diversion rather than drift, we hold the written report until counsel is engaged.
Yes — retrospective manifest audit going back to your METRC activation date. CCR 15037 requires seven-year retention of all commercial-cannabis records, so manifest data is available through the METRC GET /transfers/v2/incoming, /outgoing, and /rejected endpoints regardless of how far back the engagement scope reaches. Standard engagements cover the prior four quarters; remediation-driven engagements (post-DCC notice, pre-diligence, post-CDTFA inquiry) cover whatever window the triggering event requires. Distributors with hub operations get hub-leg-by-hub-leg reconstruction across the arrive, check-in, check-out, and depart events under CCR 15311.
Quarterly for most operators — the 90-day cadence catches drift inside a remediable window rather than a 365-day annual review. Monthly for high-volume distribution and Type 7 volatile-solvent manufacturing where conversion ratios compound variance fast. On-demand for any triggering event: a DCC notice of inspection, an observed shift-change discrepancy, pre-diligence on an M&A transaction, or a CDTFA excise-reconciliation inquiry. Retail-only operations with consistently sub-0.5% variance can run semi-annually, with the cycle aligned to the renewal-window due-diligence pass 60 days before annual expiration under CCR 15014.