Minnesota cannabis B2B transfers move on a licensed transporter under a METRC-generated manifest, within the time window that manifest documents. There is no statewide SLA — your real window is set by three things: manifest parameters, your transporter's cutoff, and the receiving licensee's acceptance hours. Align all three in writing to prevent voids, rejected loads, and OCM audit flags.
What Are Delivery Windows and SLAs in Cannabis B2B Transport?
In general freight, a delivery window is the agreed time range during which a shipment can be tendered and accepted. A cutoff is the last moment you can hand off product and still make that window. An SLA (service-level agreement) is the written commitment between shipper and transporter that defines performance, remedies, and escalation.
In licensed Minnesota cannabis logistics, those same concepts carry regulatory weight that standard freight does not. A missed window is not just a service failure — it can create a manifest discrepancy under OCM Rules 9810 and require corrective reporting. That is the core difference, and it is why transport in this lane is a licensed function, not a vendor afterthought.
Does This Apply to My Operation?
If you are a Minnesota cannabis licensee moving product between licensed facilities — cultivator to processor, processor to manufacturer, manufacturer to retailer, or any combination — you are conducting a regulated transfer under Minn. Stat. § 342.35 and § 342.36. That means:
- The transfer must be initiated and tracked in METRC before product leaves the origin facility.
- The vehicle must be operated by a licensed cannabis transporter — a separate license class under ch. 342.
- The manifest must travel with the product and accurately reflect the departure time, route, and estimated arrival.
This applies whether you are moving a full pallet of packaged flower or a single transfer of extracted oil. Volume does not create an exemption.
The Regulatory Framework That Sets Your Window
Minn. Stat. §§ 342.35 and 342.36
Section 342.35 establishes the general transfer requirements for licensed cannabis businesses, including the requirement that cannabis and cannabis products be transported by a licensed transporter. Section 342.36 addresses security during transport — secured compartments, GPS tracking, and communication protocols — all of which shape how a transporter structures route timing and driver schedules.
These provisions do not set a maximum transit time in hours, but they do require that the manifest accurately reflect the planned route. A manifest reading "estimated arrival 2:00 PM" that delivers at 6:00 PM without an amended manifest is a discrepancy.
OCM Rules 9810
The Office of Cannabis Management's administrative rules under Chapter 9810 govern record-keeping, manifest requirements, and what constitutes a compliant transfer. Key operational implications:
- Manifest accuracy is a compliance obligation, not a courtesy. The departure time, vehicle, and driver on the manifest must match reality.
- Amendments are allowed but auditable. If a route changes or timing slips, the manifest can be updated — but the amendment is logged and visible to OCM inspectors.
- Receiving facilities must reconcile. The buyer's facility must accept the transfer in METRC and note any discrepancies. A receiving window that closes before the driver arrives forces a manifest void or a refused-transfer entry — both are audit flags.
METRC Manifest and Transfer Mechanics
METRC is Minnesota's track-and-trace system. Every licensed transfer generates a manifest package in METRC, which includes:
- A transfer template (origin, destination, transporter, packages, quantities)
- A departure timestamp, set when the transporter accepts the transfer in METRC
- An estimated arrival time
- A void condition if the transfer is not completed or is rejected within the manifest window
Operationally, the METRC manifest is your SLA in documentary form. If your transporter's cutoff is 3:00 PM for same-day delivery and your transfer template is not built and approved in METRC by that cutoff, the manifest cannot be generated in time and the load does not move.
How Delivery Windows Actually Get Structured
Scheduled Route Windows
Most licensed cannabis transporters in Minnesota operate on scheduled route windows — fixed days and time blocks for each corridor (Twin Cities metro, Central MN, Southern MN). Those windows exist because:
1. A licensed driver-guard pair must staff every vehicle under § 342.36. 2. Routes are pre-planned for manifest accuracy. 3. Receiving facilities set acceptance hours that cannot always flex.
A structured metro run might be departure 8:00–10:00 AM, delivery window 10:00 AM–1:00 PM. A Southern MN corridor might run one or two days per week with longer lead times. Exact blocks vary by transporter and corridor — confirm yours in your service agreement rather than assuming.
Cutoff Times
Your order cutoff — the last time you can submit a transfer request and still make a given route — is set by your transporter and should appear in your service agreement. As a planning rule of thumb, cutoffs commonly fall well ahead of departure for multi-stop routes and tighter for dedicated same-day runs in dense corridors.
Missing the cutoff means the next available window, which for some corridors can be days out. For time-sensitive product — a tested batch with a retailer waiting on shelf space — that delay has real revenue impact.
Receiving Window Alignment
This is the step most often missed in operator SLA planning: your receiving facility must be open and staffed to accept the METRC transfer during the delivery window. A retailer's 9:00 AM–12:00 PM receiving hours do not accommodate an afternoon delivery window, no matter what the transporter can execute. Build receiving-window confirmation into your pre-transfer checklist.
Is Your SLA Structure Compliant?
A service-level agreement between a shipper and a licensed transporter does not override OCM requirements — it must be written within them. A compliant SLA structure includes:
- Cutoff times that allow manifest generation before departure. The transporter needs enough lead time to accept the transfer in METRC and attach the driver and vehicle before wheels roll.
- Defined escalation for manifest discrepancies. Who amends the manifest if there is a delay, and what is the documentation trail?
- Clear terms for refused or undeliverable transfers. What happens operationally and in METRC if the receiving facility cannot accept, and who initiates the return-transfer manifest?
- GPS and communication compliance per § 342.36. Your SLA should reference — not contradict — the security and tracking requirements the transporter already meets.
If your current transporter agreement does not address METRC manifest procedures explicitly, it is not a cannabis-compliant SLA. It is a general freight contract applied to a regulated context, and the gaps will surface at the worst possible time.
What Same-Day Delivery Actually Looks Like in MN
Same-day B2B cannabis delivery in Minnesota is operationally feasible in dense corridors — primarily the Twin Cities metro — under specific conditions:
- The transfer request is submitted and approved in METRC before the transporter's same-day cutoff.
- The origin facility has product staged, weighed, and labeled, with METRC data entry complete, before the driver arrives.
- The receiving facility has confirmed acceptance availability for the same afternoon window.
- The transporter runs a dedicated route, not a multi-stop run where timing is variable.
Outside the metro, same-day is rarely achievable given route frequency and drive times. Operators in Greater Minnesota should plan around scheduled corridor windows and build safety stock accordingly.
One Clear Takeaway
Document your transfer workflow end-to-end — from METRC template creation to receiving confirmation — and put every cutoff and window in that workflow in writing with your transporter. The manifest is the compliance record. The SLA is the operational agreement that keeps the manifest accurate. Both need to exist, and they need to align.
How to Act on This
1. Audit your current transporter agreement. Does it reference METRC manifest procedures, OCM Rules 9810, and § 342.36 security requirements? If not, request an addendum. 2. Map your corridor windows. For each route you run regularly, document the transporter's cutoff, departure window, and delivery window. Put these in your internal SOPs. 3. Align receiving facilities. Confirm in writing that your buyers' receiving hours overlap your delivery windows before you build the METRC transfer. 4. Build manifest accuracy into your pre-ship checklist. Departure time, driver, vehicle, and estimated arrival should be verified — not estimated — before the manifest is submitted. 5. Establish a discrepancy protocol. Know who amends the manifest, who notifies OCM if required, and what the return-transfer procedure is if a load cannot be accepted.
FAQ
What is the legal requirement for manifests on Minnesota cannabis B2B transfers?
Under Minn. Stat. § 342.35 and OCM Rules 9810, every licensed transfer must travel with a METRC-generated manifest that accurately reflects the origin, destination, transporter, vehicle, driver, departure time, and estimated arrival. The manifest must be created and accepted in METRC before the product leaves the origin facility.
Does Minnesota set a maximum transit time for cannabis transport?
Minnesota statutes and OCM Rules 9810 do not specify a single maximum transit time in hours. The compliance obligation is manifest accuracy: the estimated arrival time on the manifest must reflect the actual planned route, and any deviation that extends transit must be documented via a manifest amendment in METRC.
What happens if a delivery arrives outside the manifest window?
A delivery that falls outside the time parameters documented on the METRC manifest creates a manifest discrepancy. Both the transporter and the receiving licensee have reporting obligations. Repeated discrepancies are visible to OCM inspectors and can trigger compliance review. Amending the manifest before the window lapses — not after the fact — is the correct procedure.
Is same-day cannabis B2B delivery possible in Minnesota?
Same-day delivery is operationally feasible in the Twin Cities metro corridor when the METRC transfer request is submitted before the transporter's same-day cutoff, the origin facility has product staged and labeled, the receiving facility confirms same-day acceptance availability, and the transporter runs a dedicated (not multi-stop) route. Outside the metro, route frequency and drive times typically make same-day unreliable.
What should a compliant cannabis transport SLA include?
A compliant SLA should specify cutoff times that allow METRC manifest generation before departure, define escalation procedures for manifest discrepancies and delays, address refused or undeliverable transfer handling in METRC terms, and reference the GPS tracking and security requirements of Minn. Stat. § 342.36. A general freight contract that does not address these cannabis-specific elements leaves compliance gaps.
Who is responsible for accepting the METRC transfer at the receiving facility?
The receiving licensed facility is responsible for accepting the transfer in METRC and recording any package discrepancies at the time of delivery. The receiving facility must have staff available within the agreed delivery window to complete this step. A facility that is closed or unstaffed when the driver arrives forces a refused-transfer entry in METRC — an auditable event for both parties.
More from Emerald on Last-Mile & Same-Day Delivery.
