Troubleshoot three common Metrc issues in Dutchie POS: Failed Metrc kyes, discrepancy issues, and batch mode errors.

This article highlights three common issues users come across in Metrc and some tips to help you troubleshoot them - Failed Metrc key, tips and tricks for Discrepancy issues, and Batch mode errors

Failed Metrc key

Is the master Metrc key failing? 

  1.  
    1. Are individual user keys required/being used? (check setting in Metrc > Settings > Require individual user keys). If user keys are required, the issue could be the individual user key failing vs the Metrc master key. 
    2. Verify your permissions. To validate, go to Settings > Integrations > Metrc > Validate key, see Update your Metrc API Key.

Discrepancy issues

Discrepancy related issues happen when inventory counts are off in Dutchie/Metrc. Below are some tips to help trouble different discrepancy issue:

  1. Integration Audit: Refresh packages (always use this FIRST to clear out any stale data). Go to Traceability > Integrations audit. Select the products, then click the Bulk Actions dropdown. Select Refresh Packages

     
  2. Avoid using “Syncing levels" as the first step in troubleshooting discrepancy issues.
    Note: This is essentially the same thing as making an adjustment on the inventory level. You should always figure out where the discrepancy came from before making adjustments. 

     
  3.  Deliver error codes. The error code 'Order Failed To Mark Ready for Delivery' can appear when there are discrepancies between inventory quantities in Dutchie POS and Metrc. When quantities are off, Metrc recognizes the insufficient quantities and fails to create a manifest.  
  4. When the Receipt Audit page loads, it checks our database for any transactions for a location with that timestamp and matches the results for display. Check the Receipt Audit to see if there are any sales that have not been posted to Metrc.
    • Another way to confirm if a Dutchie Receipt ID matches to a Metrc receipt ID is to go to Registers > Transactions > All transactions > receipt number (Dutchie) and the External ID (Metrc receipt number) will display confirming its posted to Metrc.

       
  5. If NOT in Batch Mode, check Product transaction history in Dutchie and compare this to the Package history export (PDF format) from Metrc. Compare side by side to see if the sales mirror. If the package history export from Metrc shows “Users” next to any of the sales instead of “API”, this means the sale was posted directly in Metrc as opposed to flowing through the integration (Dutchie to Metrc). 
    •  
      • If sales in Dutchie and in Metrc match, check the allocated Dutchie report for ghost carts. 
      • Look at the product journal in Dutchie. Maybe an adjustment was done in Dutchie only or vice versa. 
      • If sales/counts match in Dutchie and in Metrc you may to need to contact support.

         
  6. If you are in Batch Mode, go to Traceability > Logs > Batch Mode, filter by Error status and you’ll be able to see the Dutchie Receipt ID that didn’t post to Metrc and the error/reason (see image):
    errror_status_logs.jpg
     

    Unreconciled Dutchie Receipt: Sales that haven’t posted to Metrc. 

    Unreconciled Metrc Receipt: Sales that are in Metrc but are not tied to sales in Dutchie (MAY need to be voided but not always). 

    Tip

    Add your email to the Metrc batch mode email list. You will receive notifications.

Batch mode errors

Batch mode attempts to post sales to Metrc up to 3 times before displaying an error. Some states cannot be in Batch mode and must operate in real-time. 

Common Batch Mode Errors What this means  Resolution 
"*** Warning *** The package \"1A4040300000CEE000048683\" will have a negative quantity after recording. Products were adjusted without the sales posting to Metrc. Product has to be re-adjusted. 
Patient Number is required, but was not specified No MMJID listed in patient profile.  Confirm MMJID is listed in patient profile and requeue transaction. 
Contents from Package 1A4010300007D66000046458 cannot be sold because it has been Finished Finished the product in Metrc before the sale posted. Reason for this, sales won’t post and get stuck in error in Batch Mode, EOM will come and operators will attempt reconcile and not realize they had transactions that didn’t post. 

Check with your regulator/state prior to taking any action to confirm if you can compliantly unfinish the impacted package in Metrc. Please attempt to re-queue the transactions from your Batch mode logs.

 

If any adjustments were made prior, will need to re-adjust in Metrc/Dutchie so that their Integration Audit doesn’t get impacted. 

METRC Bad Request-Timeout Expired.  Metrc could’ve blipped for a second and Dutchie didn’t get a successful response from Metrc.  Attempt to requeue transactions and see if any other errors display. 
METRC Unauthorized - Authorization has been denied for this request Metrc key is failing. Could also be individual user key failing.  Batch mode error will show the cashier/budtender name. This employee can log into Dutchie Backoffice, go to validate key tab, confirm if your key or the Metrc master key is failing. Regenerate a new key if needed in Metrc. 

Read more