A compliant Minnesota cannabis transfer takes three steps, in order: every package gets a METRC tag before it leaves your facility, gross weight is recorded against that tag at origin, and the receiving licensee verifies receipt in METRC within 24 hours. Miss any step and the manifest breaks — OCM reads that as untracked product in transit.
What a "Transfer" Actually Means Under Minnesota Law
In Minnesota cannabis logistics, a transfer is not a sale confirmation or a delivery receipt. It is a state-tracked custody event — the moment a licensed package moves from one licensed premise to another under the authority of a cannabis manifest.
Minnesota Statutes chapter 342 governs all cannabis business licensing and operation. Section 342.35 establishes the general operational requirements for cannabis businesses, and section 342.36 addresses record-keeping obligations including real-time inventory tracking. The Office of Cannabis Management (OCM) operationalizes these requirements through Minnesota Rules chapter 9810, which sets the specific METRC reporting timelines and manifest standards carriers and licensees must follow.
Every cultivator, processor, manufacturer, and retailer in the state is a node in the same chain. The transport licensee — the carrier physically moving product between those nodes — is the link that has to hold all of them together.
Does This Apply to Your Operation?
If any of the following describes you, METRC manifest compliance is your direct obligation:
- You cultivate, process, or manufacture cannabis and transfer finished or intermediate product to another licensed facility
- You are a dispensary buyer receiving product from a brand or distributor
- You are a brand owner or co-manufacturer shipping to a fulfillment or retail partner
- You are a licensed cannabis transporter moving product on behalf of any of the above
There is no threshold below which METRC tracking is optional. A single unit, a single gram, a single cartridge leaving your licensed premises requires a manifest. OCM does not distinguish between small operators and large ones here. The standard is uniform.
The Three-Step Transfer Sequence
Step 1 — Tag
Every package must carry a METRC-assigned UID tag before it is loaded onto a transport vehicle. The tag is not a label you print and apply at will — it is a state-issued identifier tied to a specific plant batch or production run in the METRC system. You request tags from METRC, associate them with inventory at the package level, and that association is permanent. You cannot re-tag a package mid-chain.
What this means practically: if you are a processor building a transfer order for a dispensary, your inventory must already be packaged, tagged, and reconciled in METRC before the carrier arrives at your loading dock. The carrier's job is to verify the tags on the physical packages match the manifest line items — not to fix discrepancies at the door.
Tag integrity failures are among the most common compliance breakdowns in the state. They are also among the easiest to prevent with a defined pre-transfer checklist.
Step 2 — Weigh
Minnesota's METRC implementation requires that package weights be recorded at origin and matched at destination. Weight is recorded in grams for plant material and processed cannabis; unit count is recorded for manufactured products. OCM Rules 9810 establish the tolerance bands for acceptable variance between origin and destination weights.
The weighing obligation sits with the originating licensee, not the carrier. The carrier's obligation is to transport the package intact and present it for destination verification at the weight reflected on the manifest. Any variance outside tolerance at destination triggers a discrepancy report — which becomes part of the chain-of-custody record and is visible to OCM.
Practical implication: use calibrated, NIST-traceable scales and document the calibration date. If a scale has not been calibrated recently, that gap will surface in an audit even if the actual weights were accurate. The documentation is the compliance event, not just the measurement.
Step 3 — Verify
The receiving licensee must accept or reject the transfer in METRC within 24 hours of physical receipt. This is not a courtesy confirmation — it is a required custody handoff that closes the manifest loop. An open manifest (product transferred out, not yet received in METRC) represents untracked inventory from OCM's perspective.
For transport operators, the 24-hour clock is particularly important. If a delivery is made and the receiving licensee does not complete their METRC acceptance, the manifest stays open — and that open manifest is associated with the transporter's license. Standard practice is to document the physical delivery with a signed delivery receipt and follow up directly with the receiving licensee's compliance contact if acceptance is not recorded within a reasonable window.
Rejection at delivery — when a receiving licensee refuses a package due to tag mismatch, weight variance, or damaged goods — requires the carrier to return the product to origin under a return manifest. There is no informal disposition option under Minnesota law. Product that is refused goes back on record to origin.
What a Complete, Compliant Manifest Looks Like
A valid METRC manifest for a Minnesota cannabis transfer includes:
- Originating licensee name, license number, and licensed premise address
- Receiving licensee name, license number, and licensed premise address
- Departure date and estimated arrival window
- Transporter's cannabis business license number and vehicle registration
- Driver's employee license number (OCM-issued)
- Each package's METRC UID, product category, strain or product name (where applicable), quantity, and unit of measure
- Route description (not required to be turn-by-turn, but must identify the origin-to-destination path)
All of this is generated inside METRC before departure. The manifest travels with the product — physically in the vehicle, accessible to law enforcement on request at any point during transit under Minnesota Statutes section 342.35.
Common Compliance Failures and How They Happen
Tag-package mismatch at loading. The most frequent breakdown. A package gets re-sorted, a label falls off, or a last-minute order change creates a tag that never got associated with a physical package. Build a tag-scan confirmation step at the loading dock — every tag on the manifest gets scanned against the physical package before the door closes.
Scale not calibrated. Origin weight is recorded, destination weight is measured, and they differ by more than tolerance — but there is no calibration record to explain the variance. OCM will flag the discrepancy. A calibration log is cheap insurance.
Open manifests. The delivery is made, the driver leaves, and the receiving licensee's staff does not complete METRC acceptance until the next business day. The manifest sits open. For a high-volume transporter, open manifests accumulate quickly and create an inventory picture that does not match reality. Build a next-day acceptance confirmation into your delivery workflow.
Driver license status unverified. OCM-issued employee licenses have expiration dates. A driver whose license lapsed last month is operating outside compliance even if every other document is clean. Carriers should maintain a recurring calendar check on driver license expiration dates — this is not a detail to catch at an audit.
What Compliant Transfer Operations Actually Cost You
There is no fee per manifest in Minnesota — METRC access is provided to licensees as part of OCM's regulatory infrastructure. The cost of compliance is operational: time to tag, weigh, and document correctly; calibrated equipment; staff trained on METRC workflows; and a carrier who can receive and present compliant manifests without creating discrepancies on their end.
The cost of non-compliance is materially higher. OCM enforcement actions under chapter 342 range from corrective action plans to license suspension. Untracked product in transit is one of the fastest paths to a serious violation. The math is straightforward.
The One Takeaway
Get the manifest right before the truck moves. Everything downstream — weight verification, acceptance, chain-of-custody record — depends on the quality of what you built in METRC at origin. A clean manifest takes ten minutes to audit before departure. A failed manifest takes weeks to remediate.
If you are a Minnesota cannabis operator who transfers product — in any direction, at any volume — and your pre-departure METRC checklist is not a written, repeatable procedure, that is the single thing to fix first.
*Emerald Enterprise & Distribution holds a Minnesota cannabis transporter license and operates in the B2B logistics lane. This article is informational and does not constitute legal advice. Operators should consult qualified cannabis compliance counsel for guidance specific to their license type and situation.*
FAQ
What Minnesota statutes govern cannabis transfer manifests?
Minnesota Statutes chapter 342 is the primary authority, with section 342.35 covering operational requirements and section 342.36 covering record-keeping and inventory tracking. OCM Rules chapter 9810 sets the specific METRC reporting timelines and manifest standards that apply to individual transfers.
How long does a receiving licensee have to accept a transfer in METRC?
Under OCM's METRC requirements, the receiving licensee must accept or reject the transfer in METRC within 24 hours of physical receipt. An open manifest beyond that window represents untracked inventory and is a compliance exposure for both the transporter and the receiving licensee.
What happens if a receiving licensee rejects a delivery?
A rejected delivery must be returned to the originating licensee under a return manifest generated in METRC. There is no informal disposition option under Minnesota law — product that is refused cannot be left at the delivery location or transferred to a third party without a new, properly documented manifest.
Does every package need its own METRC tag, or can a shipment share one tag?
Every individual package requires its own METRC-assigned UID tag. A single manifest can cover multiple packages and multiple tags, but there is no provision for a single tag to cover a multi-package shipment. Tags are assigned at the package level in METRC before the manifest is generated.
Who is responsible for recording the origin weight on a cannabis manifest?
The originating licensee — the cultivator, processor, or manufacturer releasing the product — is responsible for recording package weights at origin. The transporter's obligation is to deliver the package intact so the destination weight can be verified against the manifest record. Weight discrepancies outside OCM's tolerance bands must be reported as a discrepancy in METRC.
Is a cannabis transporter in Minnesota required to carry a separate license from the origin or destination licensee?
Yes. Minnesota Statutes chapter 342 requires a dedicated cannabis transporter license for the entity physically moving product between licensed premises. The manifest must reflect the transporter's cannabis business license number and the driver's OCM-issued employee license number, both of which are separate from the originating or receiving licensee's credentials.
More from Emerald on METRC & Chain-of-Custody Compliance.
