A failed cannabis delivery in Minnesota is a live compliance event, not a rescheduling problem. The driver secures the load and the METRC transfer stays open until it is accepted, rejected, or voided. Re-attempting to a different receiver, or returning to origin, requires a new or corrected manifest under OCM Rules 9810 before the vehicle moves again.
What Counts as a Failed Delivery in MN Cannabis Transport?
A delivery fails the moment a transfer cannot be completed as described on the active METRC manifest. In practice, that covers a short list of real-world scenarios:
- Receiver unavailable or facility locked — the destination dispensary, processor, or manufacturer cannot accept the product at the scheduled time.
- Load rejected at the dock — the receiving licensee refuses all or part of the transfer (wrong product, quantity mismatch, failed COA, packaging noncompliance).
- Documentation discrepancy — manifest quantities, package tags, or vehicle/driver credentials do not match what is presented.
- Driver safety or vehicle incident — a breakdown, accident, or law-enforcement stop that prevents completion.
Each scenario has a different resolution path, but every one starts with the same action: the driver secures the product and contacts dispatch. No disposition decision is made at the roadside.
Does This Apply to Your Operation?
If your operation moves cannabis product between licensed facilities in Minnesota — cultivator to processor, processor to manufacturer, manufacturer to dispensary, or any combination — that product travels under a licensed transporter's manifest. Under Minn. Stat. § 342.35, cannabis transport between licensees must be conducted by a licensed cannabis transporter or by a licensee operating under its own transport authority.
That means failed-delivery protocols are not a transporter-only concern. When a run fails, the originating licensee and the receiving licensee both carry METRC obligations alongside the transporter. It is a shared compliance event that touches every operator whose product is on that truck.
The Governing Framework: OCM Rules 9810 and METRC Mechanics
Minnesota's Office of Cannabis Management has codified transport requirements under OCM Rules 9810 (the cannabis transporter rules), adopted under the authority of Minn. Stat. ch. 342. Three obligations directly govern failure scenarios:
Transport documentation (OCM Rules 9810). Every load must travel with a complete manifest identifying the originating licensee, the receiving licensee, the vehicle, estimated departure and arrival times, and an itemized package list with METRC package tags. The manifest is not optional paperwork — it is the legal chain of custody.
Transporter responsibilities (Minn. Stat. § 342.36). The licensed transporter is responsible for maintaining product security from departure to acceptance. If a transfer is not accepted, the product must return to the originating licensee unless an alternate disposition is otherwise authorized.
METRC transfer mechanics. In METRC, a transport transfer is created by the originating licensee and accepted by the receiving licensee. If a delivery fails, the transfer remains open and unaccepted — a live audit flag. It cannot be abandoned. It must be accepted, rejected by the receiver, or voided, depending on the cause.
What Happens Step by Step When a Run Fails
Step 1 — Secure the load and contact dispatch
The vehicle stays locked and the product stays secured. The driver makes no disposition decision independently. Dispatch logs the failure event with a timestamp — that entry becomes part of your audit trail.
Step 2 — Identify the failure type
- Receiver-side issue (closed, no staff, short-notice refusal): the load is a failed delivery pending re-attempt. The METRC transfer stays open. Transporter and originating licensee coordinate on whether a same-day re-attempt is possible or the load returns to origin.
- Full load rejection: the receiving licensee formally rejects the METRC transfer, which returns the packages to the originating licensee's inventory. The originating licensee reconciles inventory immediately.
- Partial rejection: the receiving licensee accepts some packages and rejects others. The rejected packages are physically separated, clearly identified, and tracked on a separate return transfer.
- Documentation discrepancy: no product moves until it is resolved. If the manifest cannot be corrected in the field, the load returns to origin and a corrected manifest is issued.
Step 3 — Return or re-attempt: which requires a new manifest
This is where operators most often slip.
A same-day re-attempt to the same receiver can proceed on the existing manifest if the METRC transfer has not been voided and the route and timing deviation stay within a reasonable window. The transporter documents the delay and updates dispatch. If the manifest's estimated arrival time has passed by a significant margin, follow your transporter's OCM contact protocol — do not assume a time window creates automatic authorization.
A re-attempt to any alternate receiver requires a new manifest. The original transfer is voided, and the originating licensee creates a new METRC transfer to the alternate destination. The vehicle does not move toward the new destination until that transfer is finalized and in the driver's possession.
A return to origin requires return documentation — a separate METRC transfer from the failed destination back to origin, or a documented internal transfer acknowledgment if the product never left transporter custody. Your transporter should have a return-manifest template ready to issue within minutes of the failure call.
Step 4 — Reconcile in METRC the same business day
Every open transfer that ends in failure must be resolved in METRC before end of business. Transfers left open overnight create a compliance gap that surfaces in an OCM audit. The originating licensee, the receiving licensee, and the transporter each carry METRC obligations — align before anyone closes out for the day.
What a Failed Delivery Costs You Beyond Compliance
OCM Rules do not publish a fine schedule specific to failed-delivery incidents — but that does not mean the cost is zero. Consider:
- Driver time and fuel for a return run or re-attempt add unplanned mileage to a licensed vehicle operating under an approved route. Route deviations require documentation.
- Inventory hold — product sitting on a truck that has not been accepted is unavailable for any other transfer. For time-sensitive loads, hours matter.
- Receiving-side shelf gaps — a buyer counting on that transfer to stock a promotion or meet a volume day takes a downstream hit. Your reliability record is your B2B reputation.
- Re-manifest labor — creating a corrected METRC transfer, issuing a new manifest, notifying OCM if required, and reconciling both parties' inventories takes staff time on both ends.
The clearest way to cut this cost is to eliminate preventable failures at booking: confirm receiver availability and dock hours before dispatch, verify package tags and COA status before the vehicle loads, and confirm driver credentials against the manifest before departure.
The One Thing to Take Away
Build a failed-delivery SOP that lives in your driver's cab and your dispatch software before you need it. It should answer four questions in under 30 seconds: Where does the product go? Who gets called? What gets logged? What METRC action is required? A transporter who can execute that SOP without escalating to a manager on every failure is a transporter worth contracting with — because the manifest, not the schedule, decides what is legal the moment a run goes sideways.
FAQ
Can a cannabis transport driver in Minnesota deliver to an unlicensed location if the original receiver is unavailable?
No. Under Minn. Stat. § 342.35 and OCM Rules 9810, cannabis product in transit may only be delivered to a licensed receiving location. If the original receiver cannot accept, the product returns to the originating licensee or goes to a pre-approved alternate licensed location on a new manifest.
Does a failed delivery have to be reported to OCM?
A routine failed delivery resolved by same-day return or re-attempt does not automatically trigger a mandatory OCM incident report. However, any event involving a security breach, lost product, or law-enforcement contact must be reported. Check your specific license conditions — some transport authorizations carry their own reporting thresholds.
How long can a METRC transfer stay open if a delivery fails?
OCM Rules 9810 set no explicit hour-count, but open unaccepted transfers that age past the original estimated arrival time become a visible audit flag. Best practice is to resolve — via acceptance, rejection, or void — within the same business day.
If a receiving dispensary rejects part of a load, does the transporter need a new manifest for the rejected packages?
Yes. Rejected packages physically returning to the originating licensee require a separate return transfer in METRC and corresponding return manifest documentation. They cannot ride back on the original outbound manifest.
What should a transport manifest include to minimize failed-delivery risk?
At minimum: originating and receiving licensee names and license numbers, vehicle identification and driver license number, the complete METRC package tag list, a route description, and estimated departure and arrival windows. Confirm the current requirements against OCM Rules 9810 for your license class.
Does Emerald Enterprise handle re-manifest and METRC reconciliation on failed runs?
Yes. Emerald's dispatch protocol covers same-day re-manifest issuance, METRC transfer coordination with both the originating and receiving licensees, and driver return-to-origin authorization — so your compliance exposure is contained from the moment the failure call comes in.
More from Emerald on Last-Mile & Same-Day Delivery.
