Use this article as a Manager or Compliance Officer to troubleshoot Metrc transfer manifest errors in Dutchie POS.
What is the issue?
Transfer manifest errors occur when a transfer between licensed facilities fails to properly record or sync in the Metrc system. Common errors include:
- Missing or invalid destination facility license numbers
- Package tags not found or already in a closed status
- Weight or quantity mismatches between the manifest and the actual packages
- Missing transporter or driver information
- Manifests stuck in a pending or rejected state
What's causing the issue?
These errors are typically caused by incomplete or mismatched data between Dutchie POS and Metrc. This can happen when required fields are missing, package information doesn't align between systems, or a sync failure prevents the manifest from being transmitted to Metrc.
How do I solve the issue?
- Log in to your Metrc account and review the transfer manifest. Metrc will display specific error messages indicating what's wrong.
- In the Dutchie Backoffice, navigate to the Transfers section and check if the transfer was created and whether it shows any sync errors.
- Verify that all required fields are populated:
- Origin and destination facility license numbers
- Package tag numbers
- Quantities and item categories
- Transporter details (driver name, vehicle info, and planned route if required by your state). If you used placeholder information when you created the manifest in Dutchie, be sure to fill in the actual driver and vehicle details in Metrc.
- If a manifest was rejected by Metrc, void it and create a new one with corrected information.
Additional possible causes
- Transporter not registered in Metrc: The transporter, driver, or vehicle may not be registered or active in Metrc, which will cause the manifest to be rejected.
- Destination facility license expired or inactive: If the receiving facility's license is expired, revoked, or inactive in Metrc, the transfer will fail.
- Package already received or in transit: If a package tag is already associated with another open or completed transfer, Metrc will reject the manifest.
- State-specific route requirements: Some states require a planned route on the manifest. If this field is missing, the transfer may fail validation.
If you're unable to resolve the manifest error, contact Dutchie Support and provide the following:
- The transfer manifest number
- The facilities involved (origin and destination)
- The specific error message displayed in Metrc or Dutchie
Commonly asked questions
- Why is my transfer manifest showing an error in Metrc?
- How do I fix a rejected transfer manifest?
- Why does my manifest say "package tag not found"?
- My transfer is stuck in a pending state in Dutchie but shows differently in Metrc — how do I fix this
- Why is Metrc rejecting my transfer due to a license number issue?
- How do I resolve weight or quantity mismatches on a transfer manifest?
- Why is my manifest being rejected because of missing transporter or driver information?