METRC manifest mistakes: rejected and stuck transfers
Posted on July 19, 2026 · Updated July 20, 2026 · By the CropLine dispatch team
A rejected transfer is not a catastrophe. It is a workflow. The catastrophe is what facilities do instead of the workflow: informal returns, quiet edits, product waiting in a back room while somebody "sorts out METRC." This guide covers the manifest mistakes that actually cause rejected and stuck transfers in Nevada, and the clean way out of each one.
If you want the full anatomy of a compliant manifest first, start with our Nevada METRC transfer manifest guide. This is the troubleshooting companion.
The mistakes that cause most rejections
- Counts that do not match the manifest. The classic. The manifest says 40 units, the tote holds 38, and now the receiving dock has a decision to make. Almost always a staging error at origin: packages pulled after the manifest was created, or two orders staged on one cart.
- Wrong receiver on the manifest. Including the specific Nevada error: listing the distributor as the receiver. The manifest names the true destination facility; the carrier is the carrier.
- Package tags that do not scan or do not exist. Retagged inventory where the old tag went on the manifest, or a package split after the manifest was created.
- Agent or vehicle details that do not match reality. A driver swap after the manifest was printed, a different van than the one whose card number is on the document. Small on paper, serious at an inspection stop.
- Product the receiver did not order or cannot accept. Wrong SKU, failed COA paperwork, or a fridge item that arrived warm. The receiver's move is rejection, not improvisation.
What rejection actually does in METRC
When a receiving facility rejects packages, in part or in full, METRC routes the rejected packages back toward the originating license, and Nevada's build (Bulletin 47) expects exactly that: refused product must be transported back to the originating cannabis establishment, under documented custody, the same way it came. The return leg is a real transfer, not an errand.
Three implications operators miss:
- Partial rejection is normal. The receiver can accept 36 units and reject 2. The 2 travel home on the return manifest; the 36 close normally.
- The rejected product is still live inventory. It belongs to the originator's license the moment it is rejected, and it has to physically land back there before anyone decides its future: re-test, re-package, or waste.
- Nobody voids a moving transfer. There is no void-in-transit path in Nevada's bulletins. Fix before departure, or reject at the dock. Those are the doors.
Who can edit what, one more time
Because this is the part that decides whether a mistake stays a mistake or becomes a finding:
- The carrier cannot alter manifest information, full stop
- The originating licensee has a narrow edit path (Bulletin 49) for packages and destinations, meant for corrections
- Everything else is rejection and return
The honest workflow costs an afternoon. The dishonest workflow, editing records to match what physically happened after the fact, is the thing enforcement actions are made of.
When the load cannot go back right away
Sometimes the return leg cannot run today. Nevada's answer is the layover process: the Board gets notified of where product sits and when it will move, nothing rests more than 72 hours without written Board agent consent, and the storage notice rides with the manifest. A rejected pallet in an unlogged corner of the warehouse is not a layover, it is a discrepancy waiting for an inventory audit.
The prevention checklist
Every rejection we see traces back to skipping one of these:
- Create the manifest from the staged order, then stage nothing else on that cart
- Scan-verify every package tag against the manifest before sealing
- Confirm receiver license number, not just the store name; groups with multiple licenses burn people here
- Match the driver and vehicle on the document to the driver and vehicle at the dock, especially after shift changes
- Call ahead on cold chain and COA expectations so the receiver's checklist matches yours
The short version
- Most rejections are staging errors, wrong receivers, tag mismatches, or documentation that does not match the dock
- Rejection is the lawful escape hatch: partial or full, with rejected product returning to the originator under documented custody
- Carriers cannot edit manifests, shippers can correct narrowly, and nothing gets voided mid-trip
- Returns that cannot run immediately go through the layover process, not a back room
CropLine handles the whole loop as part of licensed cannabis transportation in Las Vegas: manifests built right the first time, rejections handled by the book, and return legs that close in METRC the same day. 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.