In Minnesota, every cannabis transfer requires a METRC-generated manifest before the vehicle moves. It must list the transferring and receiving licensees, the licensed transporter number, driver and vehicle details, package tags, quantities, and route. OCM auditors cross-reference that record against physical tags and the driver's copy. Any gap is a documentable violation under Minn. Stat. 342.35 and OCM Rules 9810.
What "Chain of Custody" Actually Means in Minnesota Cannabis
Chain of custody is not a filing-cabinet concept. It is a live, time-stamped record that proves cannabis moved from Point A to Point B under license, under supervision, and without unexplained variance.
Under Minnesota Statutes chapter 342 — specifically §§ 342.35 and 342.36 — every licensed cannabis business must account for cannabis at every stage of transfer. That obligation does not pause when product leaves your facility. It extends through transport and does not close until the receiving licensee accepts the transfer in METRC and the manifest is finalized on both ends.
OCM Rules 9810 governs the operational mechanics: manifest creation, driver credentialing, vehicle approval, and what happens when a transfer cannot be completed as planned. Whether you are a cultivator sending trim to a processor, a processor sending distillate to a manufacturer, or a brand sending finished product to a retailer, this framework applies. Every leg of that route is a custody event.
Does This Apply to My Operation?
If your license falls under any of the following categories in Minnesota's chapter 342 framework, you are subject to manifest and chain-of-custody requirements on every inter-facility transfer:
- Cannabis cultivator (microbusiness or standard)
- Cannabis manufacturer or processor
- Cannabis retailer receiving wholesale shipments
- Lower-potency hemp edible manufacturer
- Medical cannabis manufacturer (additional METRC obligations remain from the legacy program)
There is no size exemption. A microbusiness moving product between its own co-located cultivation and retail operation inside the same building may have reduced transport requirements, but any transfer that crosses a facility boundary onto a public roadway requires a manifest and a licensed transporter.
What an OCM Auditor Is Actually Looking For
The METRC Manifest — Field by Field
OCM auditors do not skim manifests. They match fields. When an inspector pulls your transfer record, here is what gets verified against the physical reality in front of them:
- Transferring facility license number — must match the originating licensee, not a parent company or DBA
- Receiving facility license number — must be active and licensed for the product type being transferred
- Transporter license number — this is the licensed cannabis transporter, not a general freight carrier; Emerald holds this lane; using an unlicensed carrier voids the manifest
- Driver name and state-issued ID number — the driver on the manifest must be the driver in the vehicle
- Vehicle make, model, year, and plate — deviations require a METRC route amendment before departure or a documented emergency deviation on record
- Package tags — every tag on the manifest must physically match a tag on a package in the vehicle; no extra packages, no missing packages
- Product name, form, and net weight or unit count — weight variances beyond tolerance trigger a discrepancy-report obligation under OCM Rules 9810
- Planned departure time and planned arrival window — late arrivals without a logged explanation are a red flag
A manifest is not complete when it is printed. It is complete when the receiving licensee accepts the transfer in METRC and both sides reflect the same quantities. Until that happens, you hold custody and you hold liability.
Where Operators Actually Fail Audits
The violations OCM most commonly documents in transfer-related audits are not dramatic. They are administrative. These are the categories that show up repeatedly.
1. Manifest Created After Departure
METRC requires the manifest to be created and the transfer initiated before the vehicle departs. Creating it retroactively — even by minutes — is a violation. The timestamp is in the system. Auditors check it.
2. Driver Substitution Without Amendment
A driver gets sick. A substitute takes the route. Nobody updates the manifest. The name on the manifest does not match the driver who arrives. That is a chain-of-custody break. The fix is a METRC route amendment logged before or at the point of substitution, with documentation of the reason.
3. Weight Variance Without a Discrepancy Report
Cannabis loses moisture. Packages shift. A small variance between manifest weight and received weight is sometimes unavoidable. What is not acceptable is absorbing that variance silently. OCM Rules 9810 requires variances beyond tolerance to be reported. The threshold matters less than the habit: document it, report it, close it.
4. Incomplete Receiving
The sending side finalizes the manifest. The receiving licensee never completes acceptance in METRC, or completes it days later. The transfer record sits open. In an audit, an open transfer looks like unaccounted product. Receiving must be completed in METRC on the day the shipment physically arrives.
5. Unlicensed Transporter
This is the highest-severity failure. Using a carrier that does not hold a Minnesota cannabis transporter license — regardless of how reliable that carrier is for other freight — invalidates the manifest and can trigger a license action against both the sender and the receiver. Minnesota does not have a general freight carve-out for cannabis.
What Compliant Documentation Looks Like in Practice
A transfer that survives an audit has these artifacts in order.
Before departure:
- METRC manifest generated, transfer initiated, package tags scanned and matched
- Driver and vehicle confirmed against the manifest record
- Planned route logged
In transit:
- Driver carries a printed or accessible copy of the manifest (OCM Rules 9810 requirement)
- Any route deviation documented with timestamp and reason before or at the time of deviation
At delivery:
- Receiving licensee physically verifies package tags and weights against the manifest
- Receiving licensee completes the METRC acceptance the same day
- Any discrepancies logged in METRC and reported per OCM Rules 9810 before the manifest is closed
Retention:
- Transfer records retained for a minimum of five years per chapter 342 retention requirements
- Physical manifests retained at both the sending and receiving facility
What Getting It Wrong Actually Costs
OCM enforcement under chapter 342 scales with the nature and pattern of violations. A first-instance documentation gap may result in a corrective action plan. A pattern of manifest violations, or a single instance involving an unlicensed transporter, can move into license suspension or revocation proceedings. There is no published fine schedule that turns a violation into a budgeted line item — the exposure is your license.
Beyond the regulatory risk, a chain-of-custody failure at the transport layer creates downstream liability. If product cannot be traced through a clean custody record and a recall or diversion allegation arises, the party who cannot produce documentation holds the burden.
The One Thing to Take Away
Every manifest violation that shows up in an OCM audit was preventable at the point of transfer initiation. The requirement is not ambiguous — it is specific, timestamped, and cross-referenced in METRC. Build the pre-departure checklist into your standard operating procedure, confirm your transporter is licensed, and close every transfer in METRC the day it arrives. That discipline is what separates a clean audit from a corrective action.
*Emerald Enterprise & Distribution holds a Minnesota cannabis transporter license and operates within the OCM-licensed transport lane. Nothing in this article constitutes legal advice. Consult a Minnesota cannabis attorney or compliance professional for guidance specific to your license type and operational circumstances.*
FAQ
What is required on a Minnesota METRC cannabis transfer manifest?
A valid Minnesota METRC manifest must include the transferring and receiving facility license numbers, the licensed transporter's license number, the driver's name and state-issued ID, vehicle make/model/year and plate, all package tags with product name and weight or unit count, and the planned departure time and arrival window. All fields must be completed before the vehicle departs.
Can I use a regular freight carrier to move cannabis between my Minnesota facilities?
No. Minnesota Statutes chapter 342 requires cannabis transported between licensed facilities to be handled by a licensed cannabis transporter. General freight carriers do not qualify, regardless of their reliability for other cargo. Using an unlicensed carrier invalidates the manifest and creates license exposure for both the sending and receiving licensee.
What happens if the driver listed on the manifest has to be substituted?
Driver substitutions must be documented in METRC as a route amendment before or at the time of the substitution. The amended manifest must reflect the substitute driver's name and state-issued ID. Arriving at the receiving facility with a driver whose name does not match the manifest is a chain-of-custody break that OCM auditors will flag.
When does a weight discrepancy have to be reported to OCM?
OCM Rules 9810 requires variances between manifest weight and received weight beyond tolerance to be reported. The receiving licensee should document the discrepancy in METRC and file the required report before closing the transfer. Absorbing variances silently — even small ones — is itself a violation of the transfer documentation requirements.
How long do I have to retain cannabis transfer records in Minnesota?
Minnesota Statutes chapter 342 requires licensed cannabis businesses to retain transfer records, including manifests, for a minimum of five years. Both the sending and receiving facility must retain copies. METRC records satisfy the digital retention requirement, but physical manifest copies should also be kept at each facility.
Does a microbusiness need a licensed transporter for internal transfers?
A Minnesota microbusiness moving product between operations co-located within the same building and not crossing a public roadway may have reduced transport requirements. However, any transfer that places cannabis on a public roadway — even a short distance between adjacent facilities — requires a METRC manifest and a licensed transporter under the chapter 342 framework. When in doubt, treat any public-road movement as a full transfer event.
More from Emerald on METRC & Chain-of-Custody Compliance.
