Direct answer: Every cannabis run in Minnesota must carry a METRC-generated transfer manifest naming the origin licensee, destination licensee, product quantities by weight or count, the vehicle, and the licensed driver. It must stay in the vehicle the entire run and be produced on demand to OCM or law enforcement. No manifest, no lawful move.
What Is a Cannabis Transport Manifest?
A cannabis transport manifest is the legal chain-of-custody document that travels with every cannabis shipment inside Minnesota. It is not a paper receipt or a generic bill of lading. It is a state-tracked electronic record generated inside METRC — Minnesota's seed-to-sale tracking system — before the vehicle leaves the originating facility.
Under Minn. Stat. § 342.35 and § 342.36, every cannabis transfer between licensed entities must be documented and traceable. The Office of Cannabis Management (OCM), through its administrative rules at Minn. R. ch. 9810, specifies exactly what that document must contain and how it must travel. If you are moving flower, extract, edibles, concentrate, or any other cannabis product between two licensed premises in Minnesota, this requirement governs the move.
The manifest is what separates a lawful transfer from unregistered cannabis in a vehicle.
Does This Apply to Your Operation?
If you are any of the following, the manifest requirement governs every product movement you make:
- Cultivator shipping harvested flower to a manufacturer or processor
- Manufacturer or processor delivering finished goods to a retailer or another manufacturer
- Retailer receiving inbound transfers from any licensed source
- Brand owner or white-label manufacturer transferring packaged product to a distribution partner
- Wholesale buyer or seller executing a B2B transfer between licensed premises
The requirement applies regardless of distance. A five-mile run from a cultivation facility to a processing lab in the same industrial park requires the same compliant manifest as a delivery from the Twin Cities to Duluth. Mileage is not a factor — crossing a property line with product is.
What Must the Manifest Contain?
Required fields under OCM Rules 9810
OCM rules require the manifest to include, at minimum:
1. Origin licensee name and OCM license number — the facility releasing the product 2. Destination licensee name and OCM license number — the facility receiving the product 3. METRC Transfer ID — the unique identifier generated when the transfer is created 4. Product description for each package — cannabis type (flower, concentrate, edible, etc.), the METRC package tag number, and net weight or unit count 5. Estimated departure time and estimated arrival time — both logged in METRC when the manifest is created 6. Vehicle make, model, and license plate number — tied to the specific vehicle running the load 7. Driver name and OCM transporter credential — the person behind the wheel must be an authorized employee under an active OCM-licensed transport business
What METRC generates vs. what you must verify
METRC auto-populates the Transfer ID and timestamps when you create the transfer. Your job as the originating licensee is to verify that every product quantity, package tag, and destination detail is accurate before you finalize the manifest. Once the transfer reaches in-transit status, corrections require OCM coordination. Errors discovered mid-run create compliance exposure for both the origin and destination licenses — so the verification has to happen before the wheels turn.
Is Your Current Process Actually Compliant?
The manifest failures we see across the Minnesota supply chain are not exotic edge cases. They are procedural, and all three are preventable.
1. Departure time logged after actual departure. The manifest must reflect the real departure window. If the driver rolls out at 8:10 a.m. but the METRC transfer reads 9:00 a.m., that gap is a chain-of-custody break an OCM inspector can act on.
2. Vehicle or driver substitution without a manifest update. If the scheduled driver calls in sick and a backup takes the run, the manifest must be updated to the new driver and confirmed against their OCM authorization before departure. A manifest listing Driver A while Driver B is at the wheel is a violation regardless of the reason for the switch.
3. Quantity discrepancy between manifest and physical package. Package weights must match the METRC manifest at both origin and destination. Shrinkage, re-packaging, or a missed packing error creates a reconciliation problem that can trigger an audit. A destination licensee who signs off without weighing or counting is accepting liability for that discrepancy.
What Happens If You Move Product Without a Compliant Manifest?
Under Minn. Stat. § 342.35, OCM has authority to issue compliance orders, suspend licenses, and refer violations for civil penalties. Moving cannabis without a compliant manifest — including a manifest with material errors — can constitute an unlicensed transfer even when both parties hold valid OCM licenses. Law enforcement that encounters a vehicle carrying cannabis without a current, vehicle-specific METRC manifest has grounds to treat the load as unregistered cannabis.
The cost is rarely just the fine. It is the audit that follows, the inventory hold on the receiving side, and the disruption that cascades from one non-compliant run. The good news: every one of these failure points is closed by getting the document right before departure.
How METRC Manifest Mechanics Actually Work
For operators newer to the system, here is the sequence every compliant transfer follows:
1. Origin licensee creates the transfer in METRC — selecting destination license, packages, vehicle, driver, and the departure/arrival window. 2. METRC generates a Transfer ID and a printable manifest — this is the document that travels in the vehicle. 3. Driver departs within the logged window — carrying the manifest and OCM employee authorization. 4. Destination licensee receives the transfer in METRC — scanning or entering package tags to confirm receipt. 5. Both parties' records update and the chain of custody closes — any quantity discrepancy between what was sent and what was received must be reported to OCM within the timeframe in OCM Rules 9810.
Any gap in this sequence shows up as a visible anomaly in METRC's audit log — OCM can pull transfer histories, flag delayed receipts, and identify vehicles that departed outside their logged window. That is exactly why a clean manifest process protects you rather than burdens you.
The One Thing to Take Away
A cannabis transport manifest is not back-office paperwork — it is the legal instrument that makes your product movement lawful in Minnesota. Whether you are the shipper, the carrier, or the receiver, you hold a role in keeping that document accurate, and each role carries its own exposure if the document fails.
Act on it two ways. If you manage inbound transfers, build manifest verification into your receiving SOP before the truck backs up to the dock. If you manage outbound transfers, finalize the manifest in METRC before the driver keys the ignition.
If transport is not your core competency, putting the road on a licensed carrier is the cleaner path. Emerald Enterprise & Distribution holds the OCM transport license, maintains documented manifest SOPs, and runs a two-check verification on every load — one at pack-out, one at vehicle load — before a driver clears the gate. That keeps the compliance accountability where it belongs: on the party whose license covers the road.
FAQ
What statute governs cannabis transport manifests in Minnesota?
Minn. Stat. § 342.35 and § 342.36 establish the transfer documentation requirements for licensed cannabis businesses. OCM's administrative rules under Minn. R. ch. 9810 specify the manifest content and METRC mechanics that implement those statutes.
Does every cannabis transfer need a manifest, even short local runs?
Yes. Distance is not a factor under Minnesota law. Any movement of cannabis product between two licensed premises — regardless of mileage — requires a compliant METRC-generated manifest accompanying the vehicle.
Who is responsible if a manifest has an error — the shipper or the receiver?
Both, within their roles. The origin licensee owns manifest accuracy at departure; the destination licensee owns verifying received quantities against the manifest at receipt. Discrepancies must be reconciled and, if material, reported to OCM.
Can a driver use a printed manifest or does it have to be digital?
OCM accepts either the METRC-generated manifest in print or a digital version accessible on a device in the vehicle, provided it reflects the active, current transfer record for that specific run.
What happens if a driver is pulled over without the manifest?
Law enforcement encountering cannabis in a vehicle without a current, vehicle-specific METRC manifest has grounds to treat the product as unlicensed cannabis. That is a significant enforcement risk independent of any OCM licensing action that may follow.
Does Emerald Enterprise & Distribution handle manifest creation for shippers?
Emerald manages manifest creation within METRC as part of its carrier service for B2B transport clients. The originating licensee authorizes the transfer, and Emerald's operations team coordinates the METRC workflow, driver documentation, and receiving confirmation to close the chain of custody on every run.
More from Emerald on Licensed Cannabis Transport in Minnesota.
