METRC tracks cannabis in transit in Minnesota by requiring the shipper, the licensed transporter, and the receiver to create, carry, and close a single transfer manifest before product moves. Every package carries a unique METRC tag; the manifest records route, driver, vehicle, and package detail; and the receiver must reconcile and accept the transfer in METRC. Any gap is a reportable discrepancy under OCM Rules chapter 9810.
What Is METRC, and Why Does Minnesota Use It?
METRC (Marijuana Enforcement Tracking Reporting and Compliance) is the state-mandated seed-to-sale tracking platform for Minnesota's cannabis program. The Office of Cannabis Management (OCM) administers it under the authority of Minn. Stat. ch. 342. Every licensed cannabis business in the state — cultivators, manufacturers, retailers, medical cannabis businesses, and licensed transporters — operates inside the same METRC environment.
That shared environment is the entire point. When product moves from one licensed premises to another, METRC builds a continuous, timestamped custody record that OCM, law enforcement, and banking-compliance reviewers can audit at any moment. The manifest is not paperwork that rides along with the load. It is the legal record the physical cannabis must match — at every handoff.
Does METRC Tracking Apply to My Transfers?
Yes — with no carve-out for volume or distance. Under Minn. Stat. §§ 342.35 and 342.36 and the implementing OCM Rules (Minn. R. ch. 9810), any movement of cannabis or cannabis products between licensed premises must travel under an active, OCM-compliant transfer manifest. Ten units or ten thousand, across town or across the state — the requirement is the same.
The manifest requirement covers:
- Cultivator-to-processor transfers — biomass, flower, trim
- Processor or manufacturer-to-retailer transfers — finished goods, concentrates, edibles
- Retailer-to-retailer transfers — permitted between co-licensees under defined conditions
- Return and waste transfers — product moving to a licensed destruction or processing facility
- Lab-sample transfers — material moving to a licensed testing laboratory
When a licensed transporter is in the chain — which Minn. Stat. § 342.36 contemplates for most third-party moves — that transporter must appear on the manifest and must carry a printed or approved-digital copy for the entire movement.
If your operation ships, hauls, or receives licensed cannabis in Minnesota, every section below applies to you.
How a METRC Transfer Manifest Actually Works
A compliant transfer moves through three controlled handoffs. Each one writes a timestamp to the state record.
Step 1 — The Shipper Creates the Transfer in METRC
Before product touches a vehicle, the originating facility creates an outgoing transfer in METRC. The entry must include:
- The receiving licensee's METRC license number
- Each package, identified by its unique METRC package tag (UID)
- Package detail: product type, weight or unit count, test batch number, and test status
- Planned departure date and estimated arrival window
- The licensed transporter and the assigned driver
- Vehicle information — make, model, plate number
METRC generates a manifest number at this step. That number is the chain-of-custody anchor for the whole move.
Step 2 — The Licensed Transporter Logs the Pickup
When the transporter arrives, the driver must have the manifest in hand — printed or on an approved digital device — and must be able to produce it on demand to any law enforcement officer or OCM inspector during transit, per OCM Rules chapter 9810. The manifest must match the packages actually loaded. No substitutions and no additions without a corrected manifest.
The transport vehicle carries only the packages listed on the active manifest. Nothing else rides along.
Step 3 — The Receiver Reconciles and Accepts
On arrival, the receiving facility checks each incoming package against the manifest — tag by tag, weight or count by count. If everything matches, they accept the transfer in METRC, and the system records the acceptance timestamp. The loop is now closed.
If something does not match — a short-weight package, a mismatched tag, a missing unit — the receiver must note the discrepancy in METRC and report it to OCM. Under OCM Rules chapter 9810, discrepancies above defined thresholds trigger a formal review, and both the shipper and the transporter carry liability exposure until the matter is resolved. Until the receiver accepts, the transfer stays open and both facilities hold compliance risk.
What the Manifest Must Contain: An Operator Checklist
Before any shipment leaves your dock, confirm your METRC transfer record carries every required field:
- [ ] Originating license number and facility address
- [ ] Receiving license number and facility address
- [ ] METRC manifest number (system-generated)
- [ ] Unique METRC UID for every package in the transfer
- [ ] Product name, category, and weight or unit count per package
- [ ] Test batch number and testing laboratory name per package
- [ ] Pass/fail test status and test date
- [ ] Transporter license number
- [ ] Driver name and state-issued ID or driver's-license number
- [ ] Vehicle make, model, and plate number
- [ ] Planned departure and estimated arrival
A missing required field is grounds for OCM to void the manifest and send the shipment back to origin. Catching it at your dock costs minutes; catching it at a roadside stop costs the load.
Chain-of-Custody Gaps That Create Real Risk
Three patterns generate most of the chain-of-custody problems field inspectors find. Each is preventable at the shipper end.
1. Tags applied after weighing. METRC tags belong on packages at harvest or production — not at the loading dock. A tag applied at the dock leaves the package's pre-transfer history blank in METRC, which reads as a red flag to auditors and banking reviewers.
2. Verbal route changes. If a driver needs an unscheduled stop at a different licensed facility, the original manifest cannot legally cover that drop. A new or amended manifest must exist in METRC before the vehicle reaches the unplanned destination. Arriving at an unlisted facility with cannabis aboard is a chain-of-custody violation.
3. Accepting without reconciling. Accepting a transfer before you physically count and weigh locks in whatever the shipper entered. Discrepancies found after acceptance are far harder to resolve under OCM Rules chapter 9810 — and the paper trail can resemble diversion even when the real cause was a packing error.
What This Means for Each Operator Role
Cultivators and processors: Your package-level accuracy — correct weights, correct test-batch linkage, tags assigned at the right process step — decides whether a transporter can legally pick up your product. A manifest built on bad package data is a non-compliant manifest before the truck even arrives.
Manufacturers: Finished-goods transfers require the test batch number and pass status from a licensed Minnesota testing laboratory on the manifest. Untested product cannot move under a sales or transfer manifest; it can only move under a lab-sample manifest.
Retailer buyers: You are the last line of reconciliation. Accepting a transfer without a physical count creates downstream liability that lands on your license. Build a receiving protocol — scale, tag scanner, METRC acceptance — into your intake SOP before your first delivery arrives.
Licensed transporters: Once your name is on the manifest, you share chain-of-custody responsibility for the duration of the move. A discrepancy discovered at delivery is not solely the shipper's problem.
The One Thing to Get Right
The METRC manifest is the legal product record, and the physical cannabis must match it at every handoff — no exceptions. Get the manifest right at the shipper end and you prevent the entire downstream chain of problems: rejected deliveries, OCM reviews, banking-compliance flags, and strained operator relationships.
If you move licensed cannabis in Minnesota and your METRC workflow shows any of the gaps above, close them before OCM or law enforcement finds them in the field. That is a decision you can make today, on your own dock.
*Emerald Enterprise & Distribution holds a Minnesota licensed cannabis transporter authorization. This article reflects our reading of publicly available Minnesota statutes and OCM rules as of the publication date and is provided for informational purposes only. Operators should consult qualified legal counsel for compliance decisions specific to their license type and operations.*
FAQ
Does every cannabis transfer in Minnesota require a METRC manifest?
Yes. Under Minn. Stat. §§ 342.35–342.36 and OCM Rules chapter 9810, every movement of cannabis or cannabis products between licensed premises must travel under an active METRC manifest, regardless of shipment size or distance.
Who creates the METRC transfer manifest — the shipper or the transporter?
The originating (shipping) facility creates the outgoing transfer in METRC before product is loaded. The licensed transporter carries the manifest during transit and confirms the pickup. The receiving facility closes the manifest by accepting it in METRC.
What happens if the manifest does not match the physical packages delivered?
The receiving facility must note the discrepancy in METRC and report it to OCM. Under OCM Rules chapter 9810, discrepancies above defined thresholds trigger a formal review. Both the shipper and the transporter carry liability exposure until the matter is resolved.
Can a driver make an unscheduled stop at a different licensed facility during transport?
Not under the original manifest. A new or amended METRC manifest must exist before the vehicle reaches any destination not on the active manifest. Arriving at an unlisted facility with cannabis aboard is a chain-of-custody violation.
What driver and vehicle information must appear on a Minnesota METRC manifest?
OCM Rules chapter 9810 require the driver's full name and state-issued ID or driver's-license number, the transporter's license number, and the vehicle's make, model, and plate number. Inspectors may request the manifest during any stop.
Does product need to pass testing before transfer to a retailer in Minnesota?
Yes. Finished products transferred to a retailer must carry a completed test batch number and a pass status from a licensed Minnesota testing laboratory in the METRC manifest. Untested product may only move under a lab-sample manifest.
More from Emerald on METRC & Chain-of-Custody Compliance.
