The Nevada METRC transfer manifest, explained
Posted on July 19, 2026 · Updated July 20, 2026 · By the CropLine dispatch team
Every legal gram that moves between two Nevada cannabis licenses moves on a METRC transfer manifest. It is the single document that connects your inventory, the vehicle, the driver, and the receiving dock, and it is the first thing a CCB agent asks for when a transfer goes sideways.
Most of what is written about transfer manifests is national boilerplate or buried in state bulletin PDFs. This is the Nevada version, in plain English: what goes on the manifest, who creates it, what can and cannot be changed once the vehicle moves, and where operators get burned.
What a transfer manifest is
METRC is Nevada's seed to sale tracking system. A transfer manifest is METRC's travel document: a record, created inside the system before transport, that says exactly what is leaving, where it started, who is carrying it, and where it is going. The paper (or PDF) copy rides with the driver for the entire trip, and the digital record closes when the receiver accepts.
The legal backbone is NAC 678D.020, the section operators knew as NCCR 13.015 before Nevada's 2026 recodification. It is not a suggestion: transporting product between licenses without a manifest is the kind of violation that shows up in disciplinary filings.
Who creates it, and when
The originating licensee enters the transfer in METRC before handing product to anyone. Two details matter here:
- Before, not during. The manifest exists before the vehicle is loaded. Creating it after the fact, even minutes after, inverts the whole point of the record.
- The receiver is the receiver. The originator may not list the distributor as the receiving licensee. The manifest names the true destination facility; the distributor is the carrier in the middle.
What has to be on it
Nevada's required manifest contents, straight from the regulation:
- Departure date and approximate time
- Name, address, and license number of the originating facility
- Name, address, and license number of the receiving facility
- Name, address, and license number of the distributor carrying the load
- Every product being transported, by name and quantity, by weight or unit, broken out per destination
- Estimated arrival date and time
- Vehicle make, model, license plate, and the vehicle's Board identification card number
- Each transporting agent's name, agent card number, and signature
If a manifest is missing one of those, it is not a formality problem. It is the difference between a documented transfer and an undocumented one.
At the dock: counts first, signatures second
The physical count and the manifest have to agree at both ends. At pickup, the originator and the carrier verify counts, seal the product, and sign. At delivery, the receiving facility confirms the contents against the manifest and documents any discrepancy separately. Counting after signing is how facilities end up owning someone else's shortage.
Can a manifest be changed after the vehicle leaves?
This is the question that decides whether your bad day stays small, so here is the precise Nevada answer:
- The distributor cannot alter it. The regulation is blunt: the carrier shall not alter the information entered into the tracking system.
- The shipper has a narrow edit path. Nevada's METRC build (Bulletin 49) allows the originating licensee to edit packages and destinations of transfers even after a transporter has accepted them, which exists for legitimate corrections, not for rewriting history.
- There is no void-in-transit button. A load that is wrong or unwanted at the dock is handled through the formal rejection flow (Bulletin 47): the receiver rejects some or all packages, and rejected product must be transported back to the originating facility under the same documented custody it arrived with.
The practical rule: fix manifests before departure, reject at the dock when you must, and never handle a mistake with a side agreement. Side agreements are how METRC and reality drift apart, and drift is what auditors find. We wrote a companion guide to the manifest mistakes that cause rejected and stuck transfers.
Layovers and storage along the way
Sometimes a load has to rest. Nevada has a process instead of a gray area: the carrier notifies the Board of the layover premises and expected delivery time, product cannot sit more than 72 hours without written consent from a Board agent, and the Distributor Temporary Storage Notice gets filed with the transfer manifest attached. If your carrier's answer to "where does it sit overnight" is anything other than that process, keep asking questions.
Where waste destruction fits
Waste has its own METRC workflow that runs through notices and inventory records rather than standard transfer manifests in most cases; we covered it in how cannabis waste destruction works in METRC. The theme is identical though: the system is told first, the physical event happens second, and the records agree at the end.
The short version
- Every facility-to-facility movement rides a METRC manifest created before transport by the originating licensee
- The manifest names the true receiver, the carrier, the vehicle and its card number, every product, and every agent
- Counts are verified against the manifest at both docks, with discrepancies documented separately
- The carrier cannot alter a manifest; shippers have a narrow correction path; wrong loads go through rejection and documented return
- Layovers over 72 hours need written Board consent, with the storage notice filed
CropLine creates, carries, and closes manifests every day across the Las Vegas Valley as part of licensed cannabis transportation, and the CropLine portal keeps every manifest number tied to its live transfer status. Request a quote or call (702) 907-1425.
This article is educational and not legal advice. Verify current requirements in NAC 678D, the Nevada METRC bulletins, and with the CCB before acting.