A manifest discrepancy on a licensed Minnesota cannabis transfer is a compliance event, not a paperwork fix. METRC flags it automatically, and both the originating licensee and the transporter carry exposure under Minn. Stat. ch. 342. OCM can hold the load and pursue discipline. Your response in the first hour decides the outcome.
What a Manifest Is — and What It Must Contain
Under Minnesota's cannabis framework (Minn. Stat. § 342.35 and § 342.36), every licensed cannabis transfer must move with a manifest generated through METRC, the state's track-and-trace system. The manifest is a legal document, not a packing slip.
A compliant transfer manifest must include:
- Origin and destination license numbers — both facilities active, licensed, and of a license type permitted to conduct that category of transfer
- Package UIDs (METRC tags) — every package individually identified and matched to an active tag
- Product category and form — flower, concentrate, edible, etc., as classified in METRC
- Net weight or unit count — the exact quantity leaving the originating facility
- Estimated departure and arrival windows
- Transport vehicle and driver information — the licensed transporter's vehicle registration and the credentialed driver
OCM Rules 9810 govern transfer documentation in detail, including the requirement that the manifest stay accessible in the transport vehicle throughout transit and be presented to law enforcement or an OCM inspector on demand.
If any of those fields conflict with what is physically in the vehicle, you have a discrepancy.
The Three Types of Discrepancy — and Why It Matters
Not all discrepancies carry the same weight. OCM and METRC treat them differently, so your response should match the type.
1. Quantity Variance
The most common. The physical count or weight of a package does not match the manifested quantity. This triggers an automatic METRC reconciliation flag on the receiving end and a variance record on the transfer. Causes include harvest or post-processing measurement drift, packaging-line error, or data-entry mistakes. Small variances (within an OCM-recognized tolerance) may be resolvable through a documented adjustment — but the documentation burden falls on both the originating licensee and the transporter.
2. Product Identity Mismatch
A package in the load does not match the METRC UID on the manifest — wrong strain, wrong form, wrong batch. This is a higher-severity event, suggesting either a fulfillment error or a chain-of-custody break. OCM's concern is diversion: product that cannot be traced to a licensed origin is treated as potentially unlicensed, regardless of intent.
3. Manifest Absent or Invalid
No manifest in the vehicle, an expired manifest (departed outside the stated window), or a manifest for a different transfer. Under Minnesota law, moving a licensed cannabis load without a valid manifest is a standalone violation, separate from any underlying product issue.
What Happens When a Discrepancy Is Found
At the Destination Facility
When the receiving licensee logs receipt in METRC, any quantity variance is recorded immediately. The receiving facility is legally required to reject packages whose METRC UIDs do not match the physical tags — it cannot accept product that does not trace. That rejection creates a METRC transfer exception visible to OCM.
The receiving licensee should document the discrepancy: timestamped notes, photographs of the physical packages and tags, and a written record of the transporter's response. Do not manually override or "close out" a flagged transfer in METRC before consulting compliance counsel — that action can compound the violation.
During Transit — A Law Enforcement or OCM Stop
If a discrepancy surfaces during a stop (routine, random, or for cause), the driver presents the manifest immediately. Minnesota law enforcement and OCM inspectors have authority under Minn. Stat. ch. 342 to inspect the vehicle and its contents. A manifest that does not match the load gives an inspector grounds to detain it pending investigation.
The driver should not explain the discrepancy beyond stating that the transporter's compliance contact is being notified. Every word at roadside is a record. Get your compliance officer on the phone.
The OCM Enforcement Pathway
OCM's authority under Minn. Stat. § 342.36 includes the ability to:
- Issue a notice of violation to the originating licensee, the transporter, and the receiving licensee
- Place a hold on the affected packages pending investigation
- Initiate a formal complaint that can result in civil penalties, license conditions, or — in cases involving diversion or falsification — suspension or revocation
Both the licensed transporter and the originating licensee carry exposure. Minnesota's framework does not draw a clean firewall between shipper and carrier on manifest integrity: the originating licensee is responsible for the accuracy of what they tender, and the transporter is responsible for chain of custody and document integrity during transit.
Will This Affect My License?
For a first-time, documented, good-faith quantity variance with a clear paper trail pointing to a benign cause (a scale-calibration issue, say), the practical outcome is typically a violation notice and a corrective action plan — not a suspension. Context matters: how fast you caught it, whether you self-reported, whether your METRC records are internally consistent, and whether this fits a pattern.
For a product identity mismatch, the calculus changes. If OCM cannot reconcile the physical product to a licensed origin through the METRC record, the stakes escalate. This is the scenario that keeps compliance officers up at night.
The clearest predictor of outcome is how fast and how cleanly you respond. Operators who self-report, quarantine the affected product, and produce a complete paper trail consistently fare better in OCM proceedings than those who try to quietly correct the issue after the fact.
What It Costs You — Dock vs. Destination vs. Roadside
The price of a discrepancy depends almost entirely on where it is caught. The discrepancy is the same; the cost is not.
A quantity variance found at the loading dock, before the vehicle departs, is a five-minute METRC adjustment with both parties present and documenting. The same variance discovered at the destination is a transfer exception on OCM's radar. Discovered at a roadside stop, it is a detained load and a roadside record.
That is why dock-level verification — a documented, package-by-package check against the METRC manifest before the load moves — is the cheapest insurance in the chain. It moves the catch point to the only place where a discrepancy is still a clerical fix rather than a compliance event.
How to Act: Your First Sixty Minutes
A manifest discrepancy is a compliance event the moment it is discovered — not after OCM is notified, not after the load is received. What your staff does in the first hour decides whether it resolves as a documented variance or escalates into enforcement.
The strongest posture combines four moves: identify and quarantine the affected packages, document the discrepancy with timestamps and photographs, file a METRC adjustment with proper records, and self-report to OCM in writing before the next audit finds it. Minnesota's framework — like most mature cannabis systems — distinguishes voluntary disclosure from discovered violations. A licensee who discloses and documents stands in a materially different legal position than one who absorbs the variance silently and gets flagged later. The voluntary-disclosure mechanism is set out in OCM's compliance guidance.
If you do not have a written SOP covering those four moves — at the dock, in the cab, or in METRC — that SOP is the single most valuable document you can write this quarter.
A licensed Minnesota cannabis transporter is built around that catch point. The transport license issued under Minn. Stat. ch. 342 requires the transporter to maintain manifest procedures, driver credentialing, and chain-of-custody controls as a condition of licensure. When Emerald Enterprise & Distribution handles a transfer, manifest verification happens at the dock — package by package, against the METRC manifest — so discrepancies are resolved at origin, where they are cheapest to fix, rather than at destination or on the roadside. Choose your transporter on the strength of its documented manifest protocol, not its rate sheet.
The One Takeaway
A manifest discrepancy becomes a compliance event the instant it is discovered. Your response in the first hour determines whether it resolves as a documented operational variance or escalates into an OCM enforcement action. Verify at origin, build the SOP now, and self-report when something slips through.
FAQ
What Minnesota law governs cannabis transfer manifests?
Minn. Stat. § 342.35 and § 342.36 establish the transfer and manifest requirements for licensed cannabis businesses. OCM Rules 9810 provide the detailed operational requirements, including what a manifest must contain, when it must be accessible, and the authority of OCM inspectors to examine manifests during transit.
What happens in METRC when a receiving facility identifies a quantity variance?
METRC records the variance automatically when the receiving licensee enters the received quantities. Any difference between the manifested and received quantity creates a transfer exception visible to OCM. The receiving facility is required to reject packages whose physical METRC UIDs do not match the manifest — it cannot accept untraceable product.
Can a transporter be held liable for a manifest discrepancy they did not cause?
Yes. Under Minnesota's framework, the licensed transporter holds responsibility for chain-of-custody integrity during transit. While the originating licensee is responsible for the accuracy of what they tender, a transporter who moves a load with a known discrepancy — or fails to verify adequately at origin — carries independent exposure under their transport license.
Is a manifest discrepancy automatically a license-threatening violation?
Not automatically. A first-time, documented, good-faith quantity variance with a clear paper trail and prompt self-reporting typically resolves as a corrective action plan rather than a suspension. Product identity mismatches and manifest absence are treated more seriously. The speed, completeness, and transparency of your response is the most significant factor in how OCM proceeds.
What is the difference between a quantity variance and a product identity mismatch?
A quantity variance means the physical weight or count of a package differs from the manifested amount — often a measurement or data-entry error. A product identity mismatch means a package does not correspond to the METRC UID on the manifest — different strain, form, or batch. OCM treats identity mismatches as higher severity because they raise diversion risk: product that cannot be traced to a licensed origin is treated as potentially unlicensed, regardless of intent.
What should a driver do if a discrepancy is discovered during a roadside stop?
Present the manifest immediately and state that the transporter's compliance contact is being notified. Do not explain or characterize the discrepancy beyond that — every statement at roadside is a record. The compliance officer should be on the phone before any further discussion with the inspector. Attempting to verbally resolve a manifest issue at roadside typically makes the legal position worse, not better.
More from Emerald on Licensed Cannabis Transport in Minnesota.
