The METRC transfer loop closes the moment your receiving operator accepts or rejects the manifest in the system — not when the truck pulls away. Under Minn. Stat. § 342.35 and OCM Rules chapter 9810, every licensed cannabis transfer in Minnesota requires a manifest-tracked chain of custody between licensees. Until you record acceptance in METRC, the transfer stays open and both facilities carry compliance exposure.
What "Closing the Loop" Actually Means
In METRC, a transfer is not complete when it is created. It is not complete when the vehicle departs. It is complete only when the receiving licensee logs into METRC and formally accepts the incoming transfer — package by package, quantity by quantity — against the manifest the transporter carried to your dock.
That handoff is a regulatory event, not an administrative formality.
Minnesota's Office of Cannabis Management (OCM) built its seed-to-sale tracking framework around exactly this moment. Under Minn. Stat. § 342.35, transfers of cannabis and cannabis products between licensees must be recorded in the state's traceability system. OCM Rules chapter 9810 further require the transporter to carry a transport manifest and both the originating and receiving parties to maintain records of each transfer.
When dock confirmation does not happen — or happens late, or happens with unresolved discrepancies — the METRC record stops matching physical reality. That gap is where audits find problems.
Does This Apply to Your Operation?
If your facility receives cannabis flower, concentrate, cannabis products, or hemp-derived products from another licensed Minnesota facility, this applies to every inbound transfer you take in.
That includes:
- Cultivators receiving clones or seeds from another cultivator or nursery
- Processors and manufacturers receiving raw flower or trim from a cultivation operation
- Cannabis retailers accepting packaged products from a manufacturer or distributor
- Wholesalers and distributors moving product between tiers in the supply chain
Under chapter 342, transport between licensees requires a licensed cannabis transporter. Emerald Enterprise & Distribution holds the Minnesota cannabis transport license for the movements we run, carries the manifest, and documents the chain of custody on the road. Your dock, your METRC login, your acceptance action are the other half of that transaction. We control the road leg; you control the close.
What the Manifest Requires at Acceptance
The three-way match
When a driver arrives at your receiving dock, you are performing what logistics calls a three-way match: the physical product, the METRC manifest, and your own purchase order or intake record all have to align.
OCM's manifest requirements under Rules chapter 9810 mean the transport manifest carries:
- The METRC transfer ID
- Originating licensee name and license number
- Destination licensee name and license number
- Package-level detail: METRC package tag(s), item description, quantity, and unit of measure
- Driver identification and vehicle information
- Departure time and expected arrival window
Your receiving staff verify each field against the physical packages before signing anything and before accepting in METRC.
What to do when quantities don't match
Discrepancies happen. A package that left the originating facility at 5 lbs of flower may register 4.95 lbs at your scale. A manifest may list 12 units; the tote holds 11. Here is the governing logic:
1. Do not accept a discrepancy in METRC as if it were correct. Accepting the manifest quantity when the physical quantity is different creates a false record — a traceability violation. 2. Document the discrepancy at the dock, in writing, before the driver leaves. Note the METRC package tag, the manifest quantity, the received quantity, and the receiving staff member's name. 3. Contact the originating licensee. Under the traceability framework, the originating licensee initiates a correction or adjustment in METRC. You cannot unilaterally alter the transfer record. 4. Accept only what you received. METRC allows receiving operators to accept partial quantities. Use that function. 5. Retain the discrepancy documentation. Minn. Stat. § 342.36 requires licensees to maintain records sufficient to demonstrate compliance with traceability requirements. A discrepancy note is a compliance record.
If the discrepancy is significant — missing packages, broken seals, product that does not match the manifest description — do not accept the transfer at all until the matter is resolved with the originating licensee and, if warranted, reported to OCM.
Is Your Current Process Compliant?
Here are the questions your operations team should be able to answer yes to:
- Does every inbound transfer get a METRC acceptance action the same day product arrives?
- Does receiving include a physical count against the manifest before METRC acceptance?
- Do you have a written discrepancy protocol your dock staff are trained on?
- Are your METRC credentials current and assigned to staff physically present at receiving?
- Do you retain transport manifests as records separate from your METRC log?
If any answer is no, that is a process gap — not necessarily a violation yet, but a gap that can become one during an OCM inspection or traceability audit.
What It Costs to Get This Wrong
We are not going to invent numbers. What the framework establishes is straightforward. Under chapter 342, OCM has authority to impose civil penalties, require corrective action, and suspend or revoke licenses for traceability violations. An open METRC transfer — one never properly closed — is a documented, timestamped gap in your chain of custody. It does not take a field inspector to find it. The system surfaces it.
The same visibility cuts in your favor: because the gap lives in the record, a clean dock process erases it at the moment of receipt, before it can ever become a finding.
The operational cost is just as real. An open transfer means METRC inventory that does not match your physical shelves — breaking your own reconciliation, your downstream manifest creation if you also ship, and your financial records if product cost is tied to receipt.
Closing the loop cleanly, at the dock, at the time of delivery, is not administrative overhead. It is your inventory integrity.
How to Act: The Dock Confirmation Checklist
When an Emerald driver arrives at your facility, this is the sequence:
1. Verify driver ID and vehicle against the manifest. They must match the driver and vehicle present. Verifying this is your responsibility as the receiver under OCM Rules chapter 9810. 2. Receive the paper or electronic manifest, and retain it. 3. Count and inspect each package against the manifest, line by line. Check METRC tags, item descriptions, quantities, and unit of measure. 4. Record any discrepancy immediately — before the driver leaves. Do not accept the delivery and note it later. 5. Accept the transfer in METRC by package, with actual received quantities. Do not accept the manifest quantity if it differs from what you physically received. 6. Confirm acceptance with the driver. On the Emerald side, we do not consider a run closed until your receiving confirmation is in the system. 7. File the manifest per your facility's retention policy. Minn. Stat. § 342.36 requires records retention.
The One Thing to Take Away
The dock confirmation is the compliance event. Everything before it — manifest creation, transport, the driver log — is preparation for this moment. Build a receiving process that treats METRC acceptance as a regulatory act, not a paperwork step, and your traceability record stays clean.
Emerald Enterprise & Distribution runs licensed cannabis transport across Minnesota. We carry the manifest and document the chain of custody on the road. The loop closes at your dock — we are here to make that handoff as clean as the statute requires.
FAQ
What is the deadline for a receiving licensee to accept a METRC transfer in Minnesota?
OCM has not published a specific hourly deadline for transfer acceptance, but the traceability requirement under Minn. Stat. § 342.35 is that records must reflect the actual state of inventory. Same-day acceptance at the time of physical receipt is the standard a compliant receiving process should meet.
Can a receiving operator reject a partial shipment and accept the rest?
Yes. METRC allows per-package acceptance and rejection within a single transfer. You can accept the packages that arrived correctly and reject or flag the packages with discrepancies, then work with the originating licensee to resolve the rejected packages.
Who is responsible for creating the METRC transfer — the sender or the transporter?
The originating licensee creates the outbound transfer in METRC. The licensed transporter carries the manifest. The receiving licensee accepts the transfer. All three parties have obligations under OCM Rules chapter 9810 and Minn. Stat. chapter 342.
What happens if a METRC transfer stays open — never accepted or rejected?
The inventory tied to that transfer stays in a pending state in METRC and does not appear in the receiving licensee's on-hand inventory. This creates a traceability gap visible to OCM during any audit or inspection of either facility's records.
Does Emerald provide documentation of the transport leg separate from the METRC manifest?
Yes. Emerald maintains vehicle logs, driver logs, and chain-of-custody records for every transport run as required under OCM Rules chapter 9810. These records are available to the receiving licensee and to OCM upon request.
What statute governs cannabis transport manifests in Minnesota?
The primary authority is Minn. Stat. § 342.35 (transfer requirements) and § 342.36 (record-keeping requirements), implemented through OCM Rules chapter 9810. These govern what must be on a manifest, who must carry it, and how long records must be retained.
More from Emerald on Last-Mile & Same-Day Delivery.
