A cannabis recall in Minnesota is first a transport and custody problem. Every recalled unit must move from its current location back through a documented, METRC-tracked chain before remediation or destruction. If your licensed transporter lacks a compliant manifest before product leaves the dock, you have turned a quality event into a compliance violation.
What Is a Cannabis Recall in Minnesota?
Under Minnesota's cannabis framework (Minn. Stat. ch. 342), a recall is the removal of cannabis product from commerce because it poses — or may pose — a risk to public health, safety, or product integrity. The Office of Cannabis Management (OCM) holds authority under Minn. Stat. § 342.35 and § 342.36 to require a licensee to withdraw product. OCM can act on its own initiative or in response to a licensee's voluntary disclosure.
Recalls reach across the supply chain. A cultivator whose flower tests outside acceptable limits, a processor with a labeling defect on a concentrate batch, a manufacturer whose edibles were packed under compromised conditions — all are recall scenarios. Dispensary buyers holding that product in inventory are downstream recipients with their own obligations.
OCM can classify recalls by scope (lot, batch, SKU) and by urgency. The classification sets your timeline. But regardless of urgency level, the chain-of-custody requirement does not flex.
Does This Apply to My Operation?
If you hold a Minnesota cannabis license under ch. 342 and you have ever received, stored, or transferred cannabis product, a recall can reach you. That includes:
- Cultivators and processors whose own product is named in the recall notice
- Manufacturers who used a recalled input ingredient or packaging component
- Dispensary buyers who took delivery of recalled wholesale product and placed it in retail or storage inventory
- Brand owners whose product is co-manufactured or co-packed by a third party
If you are a transport licensee moving recalled product on behalf of any of the above, your exposure is procedural: the manifest must be correct, the vehicle must be compliant, and your driver must carry the right documentation at every stop.
The METRC Spine of Every Recall
Minnesota's seed-to-sale tracking system, METRC, is the record regulators use to reconstruct a product's full movement history. Every transfer between licensed facilities requires a METRC-generated manifest (a "transfer" in METRC terms). That manifest is the legal document authorizing product to be in a transport vehicle.
When a recall begins, OCM or the recalling licensee identifies the affected METRC package tags — the unique identifiers assigned to each lot or batch. From that point on, every physical movement of those packages must be reflected in METRC before transport begins.
How a Recall Transfer Works in METRC
1. The origin licensee creates a transfer in METRC designating the recalled packages, the transporter license, and the destination — typically the originating facility, a licensed destruction facility, or a licensed remediation facility. 2. The transporter accepts the transfer in METRC and generates the physical manifest. The driver must carry this manifest — printed or in an approved electronic format — at all times during transport. 3. The destination facility receives the transfer in METRC upon physical arrival and inspection. 4. No package moves without a corresponding open manifest. A recalled package in a vehicle without a current manifest is an unmanifested transfer — a separate violation under OCM Rules 9810.
This is not a formality. Law enforcement and OCM inspectors can and do conduct roadside inspections of cannabis transport vehicles. An unmanifested load — even one being returned for legitimate recall purposes — can result in administrative action against both the transporter license and the shipper's license.
Is Your Current Process Actually Compliant?
Most recall failures at the logistics level trace to one of three gaps.
Gap 1: Moving product before METRC is updated. An operator gets a recall notice and physically pulls product off the shelf before creating the METRC transfer. The product is now in a staging area — or already loaded — with no manifest covering its location. The fix: METRC transfer creation is step one, before any physical movement.
Gap 2: Using the wrong transfer type. A return-to-vendor transfer carries different METRC type designations than a transfer to a destruction facility. Using the wrong type creates audit-trail discrepancies that regulators flag on review. Your transporter should be fluent in which transfer type applies to each recall scenario.
Gap 3: Destination is not licensed to receive. Recalled product can only go to a facility holding a license that authorizes it to receive cannabis. A cultivation facility cannot receive product for destruction unless it holds the appropriate endorsement. Confirm the destination license type before you build the METRC transfer.
What Does a Recall Actually Cost an Operator?
There is no standard recall cost — scope varies. A single-SKU lot recall at a small manufacturer is a very different exercise than a multi-facility recall involving dozens of wholesale recipients. What operators consistently underestimate is the transport cost multiplier.
In a normal wholesale transfer, product moves once. In a recall it may move two or three times: dispensary back to distributor, distributor back to manufacturer, manufacturer to a licensed destruction or remediation facility. Each leg requires a licensed transporter, a new METRC manifest, and the associated handling and labor. If your wholesale network distributed to multiple facilities across Minnesota, you are coordinating parallel return legs at once.
Additional cost categories to budget:
- Transporter fees per leg (variable by distance and volume)
- METRC time: staff hours to create, manage, and close transfers
- Destruction or remediation facility fees
- Potential OCM administrative penalty if any leg is mishandled
- Lost product value (destruction is permanent; remediation may recover value depending on the defect)
Being organized at the logistics layer — clear contacts, established transporter relationships, facility licenses verified in advance — compresses this cost.
How to Act: The Recall Response Sequence
When you receive a recall notice from OCM, or initiate one yourself, execute in this order.
Step 1: Quarantine first, move nothing
Physically segregate all affected packages and mark them quarantined. Do not initiate any sales, transfers, or use of recalled product. Update your internal inventory system to flag the METRC package tags.
Step 2: Notify your licensed transporter immediately
Do not wait for the full picture. A qualified cannabis transporter can begin route planning, manifest preparation, and destination coordination while you confirm scope. OCM recall notices carry response timelines — time matters.
Step 3: Confirm destination license status in METRC
Log into the METRC licensee portal and verify your intended return or destruction destination is currently licensed and active. License lapses happen; discovering one mid-recall adds delay you cannot afford.
Step 4: Build METRC transfers before product moves
Work with your transporter to create the METRC transfer for each leg. The transporter's license number, vehicle, and driver must be entered accurately. Do not load the vehicle until METRC shows an open, accepted transfer covering those packages.
Step 5: Document everything outside METRC too
METRC is the regulatory record, not a substitute for your own documentation. Keep copies of the OCM notice, your quarantine log, internal communications, and any third-party lab reports tied to the recall. If OCM requests a compliance review, this parallel record shows you managed the event — not just the system entries.
Step 6: Confirm receipt at destination and close the loop
Once the destination facility accepts the transfer in METRC, verify on your end that all packages are closed out. Dangling open transfers are a common audit finding.
The One Takeaway
A recall is a logistics event before it is anything else. Every other response — remediation decisions, regulatory communication, financial recovery — depends on product being where METRC says it is, moved by a licensed transporter carrying a valid manifest. Get that layer right first, and the rest of the recall becomes manageable.
FAQ
Who is legally required to initiate a cannabis recall in Minnesota?
Either OCM under Minn. Stat. § 342.35/342.36, or the licensee itself through a voluntary recall. Licensees who discover a defect or safety issue are expected to self-report to OCM promptly; waiting for OCM to act first typically produces a worse compliance outcome.
Can a dispensary return recalled product without a licensed transporter?
No. Under Minnesota's cannabis framework and OCM Rules 9810, any physical transfer of cannabis between licensed facilities — including a recall return — requires a licensed cannabis transporter and a METRC-generated manifest. A dispensary cannot self-transport recalled product back to a supplier.
What METRC transfer type applies to a recall return versus a destruction transfer?
These are different transfer types in METRC. A return to the originating licensee uses a return-type transfer; a transfer to a licensed destruction facility uses a transfer-to-destroy type. Using the wrong type creates an audit discrepancy. Confirm the correct type with your transporter or METRC support before creating the transfer.
Does recalled product have to be destroyed, or can it be remediated?
It depends on the reason for the recall. Some defects — such as failed contaminant tests — require destruction. Others, such as labeling errors or certain potency variances, may qualify for remediation under OCM rules if the product itself is not unsafe. OCM's recall notice specifies the required disposition. Do not assume remediation is available; confirm with OCM in writing.
How quickly does OCM expect a licensee to respond to a recall notice?
OCM recall notices specify response timelines that vary by urgency classification. Treat any OCM recall notice as requiring immediate quarantine (same business day) and prompt transporter engagement. Minn. Stat. ch. 342 gives OCM authority to take administrative action against licensees who do not respond within the stated timeframe.
What happens if a transport vehicle is stopped with recalled product that lacks a valid METRC manifest?
This constitutes an unmanifested transfer under OCM Rules 9810, regardless of intent. Both the transporter and the originating licensee may face administrative action. The manifest must be created and accepted in METRC before the product is loaded — not after.
More from Emerald on METRC & Chain-of-Custody Compliance.
