This article summarizes Metrc (Minnesota) Support Bulletin MN_IB_0068 (distributed 07/07/2026, effective ongoing), which outlines best practices for creating and receiving Metrc Transfer Manifests to reduce preventable errors that can lock product in Metrc, delay operations, and increase the need for Metrc Support involvement. You’ll learn what commonly goes wrong on transfers, how to receive and reject correctly, and how to use Metrc efficiency features like templates, saved driver/vehicle data, Quick Entry, and CSV uploads.
Bulletin details and intent
Bulletin number: MN_IB_0068
Distribution date: 07/07/2026
Effective date: Ongoing
Subject: Transfers Best Practices
Reason: Provide guidance for creating and receiving Transfer Manifests in Metrc to reduce errors that can cause “locked” product and longer support resolution times.
Why transfer accuracy matters in Metrc (Minnesota)
Metrc transfers are not just paperwork—they are the system-of-record movement event that shifts custody and inventory between licensed facilities. The bulletin emphasizes shared responsibility: both the sending and receiving licensees must ensure that every package on the manifest is correct in Metrc and correct in the physical shipment. Accepting misconfigured packages (wrong tags, wrong quantities, wrong items, or incorrect test information) can create compliance exposure and may result in review or referral to Minnesota’s Office of Cannabis Management (OCM) Enforcement and Compliance for one or both licensees.
Common errors when receiving transfers
Metrc notes that many receiving issues originate from problems on the outgoing Transfer Manifest that were missed or ignored at intake.
• Incorrect package placed on the manifest
• Incorrect package quantity
• Incorrect wholesale price (when applicable)
• Incorrect item name or category
• Packages physically left off the Transfer Manifest
• Receiving in Metrc when you intended to reject
Receiving transfers: day-to-day best practices
The operational goal is simple: verify the physical shipment against the incoming manifest before the driver leaves, and finalize acceptance (or rejection) in Metrc immediately to prevent problems from becoming “stuck” between licenses.
• Thoroughly inspect and weigh/count all packages before the transport driver departs the receiving facility.
• If possible, have a second employee independently verify the shipment and manifest details before accepting.
• Receive the transfer in Metrc before the transporter leaves the facility so any issues can be rejected physically and in Metrc without delay.
• Review the manifest in Metrc as soon as it is generated by the origin facility, because newly created manifests are visible to the destination license right away. This can help catch errors before the shipment arrives (for example, item/category issues, electronic quantity issues, or testing-related issues).
• Confirm lab testing information in Metrc at the package level prior to acceptance by checking package details and the “Lab Test Batches” information so the test status shown in Metrc matches what you are authorized to receive.
• If package details (including testing information) are not correct, reject the affected package(s) and return them to the shipper for correction and reshipment.
Package quantity discrepancies and how to reject correctly
Metrc’s guidance is explicit: do not receive packages when the physical quantity does not match the Transfer Manifest quantity. If there is a difference, that package should be rejected and returned for correction and reshipment. A key operational implication is that if a package is received with a different quantity than shipped, the “extra” product does not automatically return to the origin license’s inventory, which creates immediate reconciliation and compliance risk.
Rejecting a package during receipt
When rejecting, the receiver must use the reject functionality on the incoming transfer before completing receipt.
• In the incoming transfer receipt screen, check the Reject box for the package being rejected (next to the shipped quantity line) before clicking Receive.
• There is no way to undo an accidental acceptance of a package, so confirm your selections carefully before submitting.
Do not edit manifests while receiving
If you identify an error after product has departed the origin facility but before delivery, the bulletin instructs that the package(s) should still be rejected upon delivery. The origin facility should then create a new Transfer Manifest with corrected information and reship. Attempting to edit a Transfer Manifest “in the middle” of receipt can cause the product to disappear from both the origin and destination inventories, creating avoidable Metrc errors that often require support intervention.
OCM review trigger for shipped vs received quantity
The bulletin notes that, in Minnesota, a discrepancy between Shipped Qty and Received Qty when receiving transferred product triggers an automatic OCM review. Practically, that means your receiving procedure should be designed to prevent mismatched quantities from ever being accepted in Metrc.
What changes after acceptance or rejection
After a transfer is received in Metrc, the manifest PDF updates to show which packages were accepted and which were rejected. Operationally, this matters because you should align your physical documentation with the system-of-record outcome.
• When a package is rejected, the driver’s copy of the manifest should be notated, and the rejected product should return with the driver to the origin facility.
• When the origin facility physically receives the returned product, it should bring the product back into inventory in Metrc by going to the Rejected tab in the Transfers area and receiving it back into the origin license.
Important: If an inventory discrepancy is discovered after receiving product in Metrc, the bulletin instructs licensees to contact OCM immediately at metrc.ocm@state.mn.us.
Outgoing transfers: prevent errors before shipment
For outbound transfers, most problems are created before the shipment ever leaves the origin facility. The bulletin highlights recurring mistakes and how to prevent them.
Common outgoing manifest errors
• Incorrect package placed on the manifest
• Incorrect package quantity
• Incorrect wholesale price (when applicable)
• Incorrect item name or category
• Packages physically left off the Transfer Manifest
Operational best practices for outbound manifests
Before the driver departs, confirm the Metrc record matches the physical shipment and business transaction details.
• Packages are created properly (correct item, correct quantity, correct package tag numbers).
• The price on the Transfer Manifest (if applicable) is correct.
• The correct packages are listed on the manifest and are physically packed and present.
• There are no sales associated with any packages on the transfer.
• If a package has a sale that might need edits, do not transfer that package out of the facility that completed the sale, because sale edits may no longer be available once the package is transferred. If remaining quantity must move, repackage the remainder onto a new package tag and transfer the new package.
Where packages go in Metrc after adding them to a manifest
The bulletin reminds users that once packages are added to a Transfer Manifest, they no longer appear in the Active Packages grid. This often creates confusion during day-to-day operations when staff think packages “disappeared.” To locate them:
In Transit: Shows packages currently on a Transfer Manifest that have not yet been received by the destination facility.
Transferred: Shows packages that have been transferred out and are now in another facility’s inventory.
Using Metrc efficiency tools (templates, saved drivers, Quick Entry, CSV)
The bulletin includes several tools that reduce data entry, speed up manifest creation, and lower the risk of manual errors—especially for operators with frequent transfers.
Transfer Templates
Transfer Templates can be created for specific destination licenses and are most useful when you transfer to the same partners repeatedly.
• In Metrc, go to the Transfers area and select Templates, then create a new template from the Licensed Transfer Templates grid.
• Populate the template with destination license number, planned route, transfer type, and driver information.
• When using a template later, you typically only need to add the packages and complete ETD (Estimated Time of Departure/Delivery) and ETA (Estimated Time of Arrival).
• The bulletin notes that creating and editing Transfer Templates is available via Metrc APIs, but creating the transfer itself must be completed in the Metrc user interface.
Save common driver and vehicle information
Metrc allows you to save frequently used transporter driver and vehicle data to reduce repetitive manual entry.
• Navigate to Admin, then Transporters, then add details under the Drivers and Vehicles tabs.
Quick Entry (barcode scanning)
Quick Entry: Enables barcode scanning to add packages to a manifest faster. Ensure Quick Entry is toggled to “On” for the manifest before scanning to avoid missed scans or partial entry.
CSV upload for packages, weight, and price
CSV Upload: Allows uploading a CSV file to add packages to the manifest and, for wholesale manifests, include package weight and price values. This is especially helpful for high-volume outbound transfers where manual entry increases error rates.
Labeling implications: item accuracy and Metrc Retail ID readiness
While this bulletin focuses on transfers, its core themes—correct item names/categories, correct quantities, and correct package identifiers—directly affect packaging and retail label accuracy downstream. When item configuration or quantities are wrong at transfer, those errors can propagate into receiving inventory, production, and ultimately retail labeling, increasing the likelihood of mislabels and Metrc Retail ID mismatches.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams stay aligned with Metrc Retail ID compliance by standardizing how key identifiers and product details are carried onto labels.
DistruERP: For larger operators that need complete seed-to-sale operations support beyond labeling, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for end-to-end supply chain management across purchasing, inventory, production, sales, and compliance workflows.
Support resources referenced in the bulletin
Metrc Support portal: The bulletin directs users to Metrc’s full-service support system (Service Cloud) through Support.Metrc.com or via the Support dropdown in the Metrc application.
Portal access note: First-time portal access typically requires your username, state selection, facility license number, and a valid email to set a password.
Escalation to OCM: For inventory discrepancies discovered after receipt in Metrc, contact Minnesota OCM at metrc.ocm@state.mn.us immediately, as instructed in the bulletin.
