Minnesota law requires every licensed cannabis business to keep all records tied to a cannabis transfer — manifests, invoices, transport documents, and METRC logs — for at least three years from the transfer date. The duty applies to every party in the chain. Failing to produce records on demand is itself a violation, separate from any transfer error.
What Is the Three-Year Retention Requirement?
Minnesota's cannabis recordkeeping rules sit in Minn. Stat. ch. 342 and the Office of Cannabis Management's implementing rules under Minn. Rules ch. 9810. The retention clock starts on the date of the transfer event — not when a product was manufactured, not when it was sold to a consumer, and not when a license was issued.
Minn. Stat. § 342.35 sets the general operational recordkeeping duties for cannabis businesses. Minn. Stat. § 342.36 covers the OCM's inspection and audit authority, including the right to demand records during unannounced inspections. Together, these sections make records more than paperwork — they are the legal proof that a transfer was lawful.
OCM Rules ch. 9810 turns the statute into operational specifics: which records to keep, in what format, for how long, and what must be produced on request. Three years is the floor, not a target.
Does This Apply to My Operation?
If your license involves cannabis moving between facilities or between legal entities, the answer is yes.
The rule reaches every tier that touches a transfer:
- Cultivators transferring biomass or flower to a processor or manufacturer
- Manufacturers and processors transferring finished product to a distributor or dispensary
- Transporters — the licensed entity that physically moves product between licensees
- Retailers and medical dispensaries receiving inbound shipments
- Microbusinesses and mezzobusinesses operating across multiple license tiers under one roof
The duty does not depend on whether a transfer was flagged, audited, or disputed. Every completed transfer creates a retention obligation, and a clean transfer history does not shorten the window.
What Exactly Must You Retain?
METRC Transfer Manifests
METRC is Minnesota's seed-to-sale tracking system, and every transfer between licensees must be opened and closed inside the platform. The METRC transfer manifest is the official chain-of-custody document for each shipment. Retain:
- The outbound transfer manifest created at origin
- The inbound transfer manifest accepted at destination
- Any manifest amendments made in transit (route changes, rejected packages, quantity adjustments)
- The reconciled close-out record confirming all packages were received or returned
Keeping the data inside METRC alone is not enough. OCM can require licensees to produce printed or exported records during inspections, so maintain your own local or cloud-archived copies.
Transport Documentation
For every shipment, the transporter operating the vehicle generates its own records, each subject to the three-year rule:
- Vehicle manifest issued for each transfer leg
- Driver assignment records linking a credentialed driver to a specific manifest
- Vehicle inspection logs for the transport date
- GPS or route logs where required by the transporter's license conditions
- Proof of insurance and vehicle registration current at the time of transport
Emerald runs under a Minnesota cannabis transporter license, and every shipment produces a complete, timestamped document package — one copy to the receiving operator, one retained by us. Each copy is subject to the three-year rule independently, which is the point: the receiving licensee cannot rely on the transporter's archive to satisfy its own duty.
Commercial Transaction Records
Chain-of-custody compliance extends past METRC into the commercial layer:
- Purchase orders and invoices for each transfer
- Proof of payment or payment-terms documentation
- Weight and laboratory test records linked to the specific packages transferred
- Certificate of Analysis (COA) for the batch tied to each transfer
- Any corrective-action records or deviation reports filed with OCM
License Verification Records
Before dispatching or accepting a transfer, each party is responsible for confirming the counterparty holds a current, active license. OCM has been clear: transferring cannabis to or from an unlicensed entity is a violation regardless of what METRC shows. Retain:
- Printed or timestamped screenshots of license lookups at the time of each transfer
- Any written license-verification confirmations exchanged between parties
Is Your Current System Compliant?
The METRC Gap Most Operators Miss
METRC holds transfer records on behalf of licensees, but it does not guarantee your records are complete, accessible, or in a format OCM will accept during an inspection of your specific license. If your account access lapses, if packages moved under a former employee's login, or if OCM asks for a format METRC does not readily export, the burden is on your business — not the state's tracking system. Build a parallel internal archive that mirrors your METRC history, and schedule the exports rather than running them reactively.
The Format Question
OCM Rules ch. 9810 does not mandate paper, but any electronic system must:
- Produce records within the timeframe set in an inspection notice
- Keep records legible and organized, tied to specific transfer events
- Be backed up in a way that protects against data loss
Cloud storage with version control, indexed by METRC transfer ID and transfer date, is the practical standard. A folder of unsorted PDFs does not meet the spirit of the rule even if it technically holds the right documents.
The Clock Is Transfer-Date Anchored
A transfer on June 1, 2023 must have its complete record package accessible through June 1, 2026 — at minimum. Many operators purge by license year or fiscal year. The correct index is the individual transfer date.
What Does Noncompliance Actually Cost?
OCM's enforcement authority under Minn. Stat. § 342.36 includes:
- License suspension or revocation
- Civil penalties assessed per violation
- Mandatory corrective-action plans
- Enhanced inspection frequency as a condition of continued licensure
Recordkeeping failures are standalone violations. An operator can have clean METRC data on every transfer and still face enforcement if, during an unannounced inspection, they cannot produce physical or digital records on demand. The violation is the failure to produce — not an underlying transaction error.
There is no published schedule of civil-penalty amounts for recordkeeping violations specifically, and OCM has discretion in how it applies enforcement. That discretion does not reduce risk; it makes the outcome of a recordkeeping failure harder to predict.
How to Act: A Practical Checklist
Building a compliant three-year retention system is not complicated, but it does require deliberate setup.
1. Anchor your records index to transfer date, not calendar year. Every document linked to a specific METRC transfer ID is filed under that transfer's date.
2. Export METRC records on a schedule — monthly at minimum. Do not rely on platform access alone.
3. Collect transport documentation at the time of delivery. When you receive a shipment, request the vehicle manifest and driver records for that run and file them with the matching METRC transfer manifest.
4. Verify the counterparty license at the time of each transfer and retain the proof. A timestamped screenshot of the OCM license lookup is sufficient.
5. Store records so they can be produced within 24 hours. An unannounced inspection can land on any business day. "We need to pull that from our accountant" is not an acceptable answer.
6. Set a rolling calendar reminder. On the first of each month, confirm no records from three years prior were inadvertently purged.
The single takeaway: three years from transfer date, every document, no exceptions — and your ability to produce those records on demand is the test, not whether they exist somewhere.
FAQ
Does the three-year rule apply to every cannabis license type in Minnesota, or only cultivators and retailers?
The retention duty applies to every licensed cannabis business involved in a transfer — cultivators, processors, manufacturers, transporters, retailers, microbusinesses, and mezzobusinesses. If your license involves product moving between facilities or between legal entities, the three-year requirement under Minn. Stat. ch. 342 and OCM Rules ch. 9810 applies to your operation.
Does my METRC account satisfy the record-retention requirement on its own?
No. METRC is the state's tracking system, but it does not substitute for your independent retention duty. OCM can require you to produce records in specific formats during an inspection. Keep your own indexed, exportable archive of METRC transfer manifests, transport documents, invoices, COAs, and license-verification records, stored separately from platform access.
When does the three-year clock start — on the transfer date or the shipment date?
The clock starts on the date the transfer event occurred — the date the METRC transfer was completed and the packages were received and reconciled at the destination. It is not anchored to the manufacture date, the purchase-order date, or the license-issuance date.
What happens if OCM requests records during an unannounced inspection and I cannot produce them immediately?
Under Minn. Stat. § 342.36, OCM's enforcement authority includes civil penalties, license suspension or revocation, and mandatory corrective-action plans. The failure to produce records on demand is itself a standalone violation — separate from whether the underlying transfers were compliant. OCM has discretion in how it applies penalties, which makes the outcome harder to predict.
As a dispensary buyer, am I responsible for retaining transport records, or is that the transporter's obligation?
Both parties carry independent retention duties. Your transporter must retain its vehicle manifests, driver logs, and GPS records. You, as the receiving licensee, are separately required to retain the inbound METRC transfer manifest, the COA for the received batch, the invoice, and your own license-verification record for the transferring party. Request a copy of the transport documentation at the time of each delivery.
Does the three-year rule apply to rejected or returned transfers, or only completed ones?
Yes — rejected, returned, and amended transfers all create retention obligations. Any METRC manifest amendment, package rejection, or return shipment generates its own chain-of-custody documentation that must be kept for three years from the date of that transfer event, including the date of the rejection or return.
More from Emerald on METRC & Chain-of-Custody Compliance.
