Reading a Cannabis Transfer Manifest: Every Field Explained

A Minnesota cannabis transfer manifest is the legal chain-of-custody record that must accompany every transport of cannabis between licensed facilities under Minn. Stat. § 342.35 and OCM Rules 9810. It logs the originating and receiving licensees, product detail, vehicle and driver credentials, and departure and arrival times. Every field is a compliance checkpoint, not a formality.

What a Transfer Manifest Actually Is

If you move cannabis in Minnesota — flower, extract, edible, or biomass — a METRC-generated transfer manifest is your proof of lawful possession in transit. It is not a bill of lading, not a packing slip, and not optional. The Office of Cannabis Management (OCM) requires that every shipment originate from a valid METRC transfer record before the vehicle leaves the originating facility's lot.

The manifest travels with the product. The transporting driver carries it (printed or accessible on the METRC mobile interface). The receiving facility checks it at the dock. Discrepancies between the manifest and the physical shipment trigger a required variance report. Get comfortable with every field before a single gram leaves your facility.

Does This Apply to Your Operation?

If your Minnesota cannabis license falls into any of the following categories, transfer manifests are mandatory for every outbound and inbound movement of cannabis or cannabis-derived product:

  • Cannabis cultivators (Minn. Stat. § 342.28)
  • Cannabis manufacturers (§ 342.29)
  • Cannabis retailers and medical cannabis retailers (§ 342.30)
  • Cannabis microbusinesses with cultivation or manufacturing endorsements
  • Cannabis mezzobusinesses operating across cultivation, manufacturing, or retail
  • Lower-potency hemp edible manufacturers transporting product to retail accounts

The one license class that generates manifests *on behalf of others* is the cannabis transporter — the lane Emerald Enterprise & Distribution holds. A licensed transporter creates or accepts the manifest originating from the shipper's METRC account, drives the route, and delivers with a closed manifest at the destination. If you are a cultivator, processor, or brand shipping through a third-party transporter, you and your transporter both carry obligations on the same document.

The Manifest Header: Facility and License Fields

These fields establish legal identity for both sides of the transfer.

Originating Facility License Number

The OCM-issued license number for the sending facility. This must exactly match the licensee of record in METRC. A transposition error here is enough for an OCM inspector to flag the shipment as non-compliant.

Receiving Facility License Number

Same standard — the destination's active OCM license number. METRC validates that both licenses are in "Active" status at the time of transfer creation. Expired or suspended licenses will block manifest generation.

Planned Route and Estimated Departure / Arrival Times

Under OCM Rules 9810, the manifest must include the planned route and an estimated travel window. This is not a suggestion. If road conditions or a stop require a significant deviation, the transporter is required to document the change. Emerald's dispatch team updates route notes in METRC in real time on every run — that log becomes part of the permanent record.

The Vehicle and Driver Fields

Vehicle Make, Model, Year, and License Plate

Minnesota law (§ 342.35, subd. 4) requires that cannabis transport vehicles be registered to a licensed cannabis transporter. The manifest captures the specific vehicle. Substituting a different vehicle mid-route without updating the manifest is a compliance violation.

Driver Name and State-Issued Driver's License Number

The driver of record on the manifest must be the individual physically operating the vehicle. OCM and law enforcement can cross-reference the manifest against the driver at any point during transit. Drivers employed by a licensed transporter are background-screened per § 342.36 requirements.

Transporter License Number (if applicable)

When a licensed transporter is engaged, their OCM license number appears here alongside — not instead of — the originating facility's information. Both entities carry compliance accountability for the shipment in transit.

The Product Detail Fields: Where Most Errors Happen

These are the fields operators get wrong most often, and where variance reports originate.

Package UID (METRC Tag)

Every package in the transfer carries a unique METRC RFID tag UID. The manifest lists each UID individually. At receiving, the destination scans or manually enters these UIDs to accept the transfer in METRC. If a physical package tag does not match a UID on the manifest, that package cannot be legally accepted without a variance investigation.

Product Category and Product Name

METRC uses OCM-defined product categories (e.g., "Flower," "Concentrate," "Edible — Solid," "Tincture"). The product name must match the item as it exists in the originating facility's METRC inventory. A package labeled "Live Resin Cart 1g" in the facility must appear identically on the manifest — not as "vape" or "extract."

Unit of Measure and Quantity

Quantity is expressed in the unit of measure tied to the product category in METRC. Flower ships in grams or pounds. Edibles typically ship by unit count and total weight. Concentrates ship by gram. Mismatches between the manifest quantity and the physical count at receiving trigger a required variance report to OCM within the timeframe specified in Rules 9810.

Batch Number / Lot Number

Traceability under Minnesota's seed-to-sale mandate runs through the batch. The manifest links each package UID back to its originating cultivation or manufacturing batch. If a recall is ever issued under § 342.62, the batch number on every manifest in the chain is how OCM identifies affected product in the market.

Lab Testing Status and COA Reference

A transfer of adult-use or medical cannabis product to a retailer requires that the associated Certificates of Analysis (COA) from an OCM-accredited lab confirm the product meets applicable potency and contaminant standards before the transfer is initiated. The manifest field for testing status must read "Passed" — not "Pending," not "Submitted." Shipping a "Pending" status to a retailer is a Category 1 compliance violation under OCM's enforcement framework.

Departure, Transit, and Arrival: The Timestamp Chain

Departure Time (Logged at Origin)

The originating facility records the actual departure time in METRC when the transport vehicle leaves. This starts the clock on the planned travel window.

Arrival Time (Logged at Destination)

The receiving facility records the actual arrival time when the vehicle arrives and the transfer process begins. Significant deviation from the estimated travel window — without a documented explanation — is a red flag in an OCM audit.

Transfer Acceptance or Rejection

The receiving facility must accept or reject each package UID in METRC at the time of receipt. Acceptance finalizes the chain-of-custody transfer. Rejection returns the package to the originating facility's inventory in METRC and requires a return manifest. Partial rejections are processed package by package.

What a Manifest Mismatch Actually Costs

Operators ask what a manifest error costs. The honest answer is not a flat dollar figure — it is exposure. A quantity variance of any amount between manifest and physical shipment must be reported. OCM Rules 9810 specify the reporting obligation; the precise timeframe and threshold are defined in the current rules and your license conditions. Unexplained variances exceeding threshold levels can escalate to license corrective action, and a corrective action against your license costs far more than any single load. The practical standard in Minnesota is direct: if it doesn't match, document it before anyone leaves the dock.

The One Takeaway

Every field on a METRC transfer manifest is a chain-of-custody link. A clean manifest — accurate license numbers, matched package UIDs, correct quantities, passed lab status, and closed timestamps — is the only documentation that proves lawful possession of cannabis from origin to destination under Minnesota law. Build the discipline of reading the full manifest before departure and before acceptance. That discipline is what keeps an OCM inspection from becoming a license action.

Emerald Enterprise & Distribution generates, carries, and closes METRC manifests on every transport run as a licensed Minnesota cannabis transporter. If your receiving or shipping team has questions about how manifest fields map to your METRC workflow, contact us before the next scheduled pickup.

FAQ

Who is responsible for creating the METRC transfer manifest in Minnesota?

The originating (shipping) facility creates the transfer in METRC before the transport vehicle departs. When a licensed third-party transporter like Emerald is used, the transporter may be granted permissions to assist, but the originating licensee's METRC account initiates the transfer and retains compliance accountability for accurate product data.

Can a cannabis transport vehicle leave before the METRC manifest is finalized?

No. Under Minn. Stat. § 342.35 and OCM Rules 9810, the manifest must be generated and the departure logged in METRC before the vehicle leaves the originating facility. A driver in transit without a valid, open manifest is transporting cannabis without required documentation — a serious violation regardless of whether law enforcement stops the vehicle.

What triggers a required variance report to OCM?

Any discrepancy between the quantities, package UIDs, or product details on the manifest and what is physically present at the receiving facility triggers a variance. OCM Rules 9810 define the reporting obligations. Both the transporter and the receiving facility have documentation responsibilities when a variance is identified at the dock.

Does the transfer manifest cover the return of rejected product?

Yes. If a receiving facility rejects one or more packages, a return transfer must be created in METRC with a new manifest covering the rejected packages for the return trip. The rejected packages are moved back into the originating facility's METRC inventory upon return acceptance.

What lab testing status is required before transferring cannabis to a Minnesota retailer?

The product must have a Certificate of Analysis from an OCM-accredited testing laboratory showing a "Passed" status for applicable potency and contaminant parameters before a transfer to a retail licensee can be initiated. Transferring product with a "Pending" testing status to a retailer is a compliance violation under OCM's enforcement framework.

How long must transfer manifests be retained?

Minnesota cannabis licensees are required to retain all METRC records, including transfer manifests, as part of their seed-to-sale traceability obligations. METRC itself maintains the electronic record permanently within the state system. Licensees should also retain their own copies consistent with OCM recordkeeping requirements specified in their license conditions and Rules 9810.

More from Emerald on METRC & Chain-of-Custody Compliance.


Leave a Comment