Direct answer: Under Minn. Stat. §§ 342.35–342.36 and OCM Rules 9810, Minnesota cannabis operators must record every transfer, receipt, and adjustment in METRC in real time. When METRC tag counts diverge from your internal records — even by one unit — you hold a reportable discrepancy. The fix is a reconciliation protocol tied to every manifest event.
What "In Sync" Actually Means Under Minnesota Law
METRC is not a suggestion. The Office of Cannabis Management (OCM) designates METRC as the statewide seed-to-sale tracking system under Minn. Stat. § 342.35, and every licensed cannabis business — cultivator, processor, manufacturer, retailer, and transporter — must record inventory events in it. OCM Rules 9810 extend those obligations to the mechanics: tag assignment, manifest generation, transfer recording, and chain-of-custody documentation.
"In sync" means your internal count, your purchase or sales orders, and your METRC plant and package records agree to the unit at every moment. Not within a reasonable margin. Not after a weekly batch reconciliation. At every transfer event.
This matters most at the handoff — the manifest — because that is exactly where the transport leg begins and where the chain of custody is legally established. Emerald operates that licensed transport lane, so the manifest is where our work and your inventory records meet. Get the numbers right at the handoff and the rest of the chain holds.
Does This Apply to My License Type?
Yes, with no carve-outs. Under ch. 342, the obligation covers:
- Cultivators — every harvest batch tagged and transferred out must match METRC package weights.
- Processors and manufacturers — intermediate and finished goods receive new METRC package tags; input destruction must be recorded.
- Dispensary buyers — received packages must be accepted in METRC before product touches the sales floor.
- Transporters — under § 342.36, each manifest must be generated in METRC before departure, carried in physical or accessible digital form during transport, and closed on delivery.
If you are a wholesale buyer or brand owner receiving a shipment from a licensed distributor, you are the receiving party on that manifest. The sync obligation lands on you the moment the driver arrives.
Where Discrepancies Actually Happen
Understanding the break points is the first step to preventing them. There are three, and they map to the manifest's lifecycle: outbound, in transit, and inbound.
At Outbound Manifest Creation
A manifest is generated in METRC from a specific package tag. If your internal system (ERP, spreadsheet, WMS) shows a different on-hand quantity than METRC reflects — because a prior adjustment was entered in one system but not the other — the manifest will be wrong before the truck rolls.
Common causes:
- Manual weight adjustments entered internally but never posted as a METRC "adjustment" event.
- QA samples pulled but not recorded as a package split or destruction.
- Returned product accepted at the dock without a corresponding METRC transfer receipt.
During Transport
METRC manifests are time-bound. OCM Rules 9810 require that the manifest reflect the actual route and estimated transit time. A manifest not closed within the approved window — or showing a route deviation without documentation — creates a gap between the legal chain-of-custody record and physical reality.
This is the transport operator's direct responsibility, and it is where the licensed lane earns its keep. At Emerald, every driver carries the manifest and dispatch monitors open manifests in real time. A manifest that is not closed on schedule triggers an immediate check-in protocol — before it becomes your discrepancy.
At Inbound Receipt
Receiving is where discrepancies compound. If your intake team counts product and finds a unit-count or weight difference from the manifest, that difference must be documented in METRC as a receiving discrepancy — not absorbed quietly into your internal system. OCM expects both parties, shipper and receiver, to hold a matching record of any variance.
The Compliance Stakes
OCM has enforcement authority under Minn. Stat. § 342.15, including license suspension, civil penalties, and referral to law enforcement where diversion is suspected. An unreconciled METRC discrepancy is evidence of a potential chain-of-custody break.
The practical risk is broader than fines. A manifest discrepancy that suggests diversion — even a clerical error — can trigger an OCM audit, which surfaces every other discrepancy in the trailing period. A single unit-count error that was never corrected becomes the thread that unravels a wider inspection.
There are no published OCM penalty schedules as of June 2026, so no per-unit fine can be cited here. What is documented: OCM holds licensees to a real-time standard, and the burden of proof for any variance sits with the licensee.
Building a Reconciliation Protocol That Holds
A working sync protocol has four checkpoints. Each is a documented step, not a mental note — and each is anchored to the manifest.
Checkpoint 1 — Pre-Manifest Audit (Outbound)
Before generating a METRC manifest, pull your internal on-hand for the package tag and compare it to the METRC package record. The numbers must match. If they do not, resolve the discrepancy in METRC first — using the correct adjustment event type — and document the reason. Only then generate the manifest. This step belongs in your SOP for every outbound transfer.
Checkpoint 2 — Manifest Verification (At Pickup)
When the transport operator arrives, shipper and driver confirm the manifest package count and tag before product is loaded. Any physical count difference found at this stage must be corrected in METRC before the manifest is finalized and the vehicle departs. Under OCM Rules 9810, a manifest cannot be amended mid-route — so pickup is the last clean checkpoint before the legal record is locked.
Checkpoint 3 — Receipt and Close (Inbound)
On delivery, the receiving party counts product against the manifest before signing. Any variance — short shipment, damaged units, wrong SKU — is documented as a receiving discrepancy in METRC. Both parties retain the record. The transporter then closes the manifest in METRC.
Do not accept product into your internal inventory until the METRC receipt is posted. If internal systems update automatically on scan, build a hold step that gates the METRC post first.
Checkpoint 4 — End-of-Day Reconciliation
At close of business, compare all METRC package movements for the day against your internal transaction log. Any unmatched event — a METRC entry without an internal record, or the reverse — gets flagged and resolved before the next operating day. A 24-hour resolution window is a defensible operator SOP standard; OCM has not published a specific deadline for internal reconciliation cycles, but real-time remains the legal standard for the METRC entry itself.
What It Costs to Do This Right
There is no compliant way to run a Minnesota cannabis operation without dedicating staff time to METRC reconciliation. The labor cost depends on volume and system integration.
Operators running METRC entries manually, with no API integration, should budget roughly 15–30 minutes per transfer event for manifest creation, receipt posting, and end-of-day comparison at modest volume. As transfer volume grows, manual entry becomes the compliance bottleneck.
The leverage point is a direct integration between your ERP or WMS and the METRC API. When internal inventory movements automatically post the corresponding METRC events, reconciliation shrinks to exception handling. Most cannabis-native ERP platforms support this; the implementation cost is real but bounded, while the alternative — a recurring compliance gap — is open-ended. Pairing that integration with a transport partner who closes manifests on schedule removes the two largest sources of variance at once.
The One Clear Takeaway
Every METRC manifest event is a legal record. Build your reconciliation protocol around the manifest — not after it. Confirm the numbers match before the manifest generates, before the truck leaves, and before product enters your internal inventory on receipt. That sequence, documented and followed consistently, is your chain-of-custody defense.
FAQ
What is the legal basis for METRC compliance in Minnesota?
Minn. Stat. § 342.35 designates METRC as the required seed-to-sale tracking system. Section 342.36 governs transport manifests specifically. OCM Rules 9810 set the operational mechanics for tagging, transfers, and chain-of-custody documentation.
How quickly must a discrepancy be entered into METRC?
OCM holds licensees to a real-time standard for METRC entries. Manifest events — departure, route, receipt — must be recorded as they occur, not in a batch at end of day.
Who is responsible for closing a METRC manifest after delivery?
The licensed transporter is responsible for closing the manifest in METRC after delivery is confirmed. The receiving party must post a receipt before the manifest can be closed.
What happens if my internal count and METRC count do not match at receiving?
Document the variance as a receiving discrepancy in METRC immediately. Do not absorb the difference silently into your internal system. Both shipper and receiver should retain records of the variance and its documented cause.
Do transporters need their own METRC account?
Yes. Under Minn. Stat. ch. 342, licensed cannabis transporters must have their own METRC account to generate and manage manifests. They are an active node in the chain of custody, not a passive carrier.
Is a digital copy of the manifest acceptable during transport?
OCM Rules 9810 allow the manifest to be carried in an accessible digital format during transport, provided it can be presented to an OCM inspector or law enforcement on demand. A printed copy is the lower-risk standard for any operator that has experienced connectivity issues on route.
More from Emerald on METRC & Chain-of-Custody Compliance.
