Skip to content
  • There are no suggestions because the search field is empty.

Retail | How to Address Metrc Transaction Submission Errors

Submitting your transactions to Metrc can periodically return errors due to data mismatches, API delays, or inventory discrepancies. Don't worry—most of these are quick fixes! This guide provides a troubleshooting decision tree, a quick-reference table, and step-by-step resolutions to get your sales synced and keep your compliance data accurate.


Prerequisites

  • App: BLAZE Web Dashboard

  • Requirement: Metrc Account Access

  • Permissions: Inventory Management and/or Global Settings Access (depending on the error).

  1. Submission Error: The Unit of Measure "Grams" is invalid. Valid values are: Each. [or vice versa]
  2. Submission Error: Package [compliance tag] cannot be sold by "Each" (CountBased), because it is not compatible with "Grams" (WeightBased)
  3. Metrc ID: Not Submitted
  4. Submission Error: Package [compliance tag] does not exist in the current Facility
  5. Submission Error: The Package [compliance tag] will have a negative quantity after recording
  6. Submission Error: Package [compliance tag] has been discontinued and cannot have its contents sold
  7. Metrc ID: SubmissionInProgress
  8. Metrc ID: SubmissionWaitingID
  9. Submission Error: Unauthorized

Troubleshooting Decision Tree

Not sure where to start? Use this quick triage flow to identify your next steps:

Start Here: Navigate to Compliance > Pending Transactions or view the Metrc ID column on the Transactions page.

  1. Is the Metrc ID Not Submitted? * Yes: If it's a non-cannabis accessory, you're fine! If it's cannabis, it's missing a package tag. Proceed to Error 3.

  2. Is the Metrc ID SubmissionInProgress or SubmissionWaitingID? * Yes: This is a sync delay, not a hard failure. Wait 15 minutes, then click Resync Compliance. Proceed to Errors 7 or 8.

  3. Does the error say Unauthorized? * Yes: Your API key is expired or lacks permissions. Proceed to Error 9.

  4. Does it show a specific Submission Error text (e.g., "Invalid UOM", "Negative Quantity")? * Yes: You have a data mismatch between BLAZE and Metrc. Find the exact error in the Quick Reference Table below.

Quick Reference Table: Metrc Errors

Error Code / Status Description Quick Fix
Unit of Measure Invalid Mismatch between "Grams" and "Each" in the product profile. Update BLAZE Metrc Category and Weight Per Unit.
Cannot be sold by "Each" Product weight is set to "Each" instead of its exact weight (e.g., Eighth). Change Weight Per Unit to a specific weight.
Not Submitted Item is non-cannabis, or it is missing a Metrc tag. No action for accessories; assign a tag for cannabis.
Package does not exist Tag is missing or unassociated in your Metrc facility. Verify tag in Metrc and resync BLAZE.
Negative quantity You sold more in BLAZE than you received in Metrc. Audit package in Metrc and adjust quantity.
Package discontinued Package is marked inactive/finished in Metrc. Unfinish the package in Metrc.
SubmissionInProgress Data is in BLAZE's queue waiting to push. Wait 15 minutes or verify manually in Metrc.
SubmissionWaitingID Data sent to Metrc; waiting for Metrc to return the ID. Click Resync Compliance on the receipt.
Unauthorized Your API key lacks permissions or expired. Enable "Manage Sales" in Metrc and replace API key.

1. Submission Error: The Unit of Measure "Grams" is invalid. Valid values are Each.[or vice versa]

Note: You may also see the reverse of this error depending on the mismatch.

This error indicates that your item needs its unit of measure corrected in BLAZE to match Metrc's exact requirements.

  1. Navigate to Inventory > All and click into the specific product prompting the error.

  2. Edit the Metrc Category to perfectly match how the item is categorized in Metrc.

    • If you do not see the specific category to select: Open a separate tab, navigate to Compliance > Compliance Sync Jobs, and click Resync. After the sync is complete, return to the original tab to select the newly updated category.

  3. Verify that the Weight Per Unit is set appropriately (e.g., 'Each', Half Gram Unit, Whole Gram Unit, Eighth Per Unit, or Custom Weight).

  4. After correcting the item, navigate back to Pending Transactions and resubmit.

NOTE: For a 0.5 oz item, you would select Custom Weight, set the Custom Weight Option to 'Gram', and the Custom Weight Value to 14.


💡 PRO TIP: Prevent this error! Always verify that the "Weight Per Unit" and "Metrc Category" fields perfectly match the Metrc manifest before completing intake on a Purchase Order.

2. Submission Error: Package cannot be sold by "Each" because it is not compatible with "Grams"

This error is commonly returned when a product's weight is incorrectly set to "Each" instead of the actual g/mg weight in your BLAZE account.

  1. Open your Metrc account, copy the package number from the submission error, and search for that package to identify the associated product.

  2. Return to BLAZE, navigate to Inventory > All, and select the product prompting the error.

  3. Edit the Weight Per Unit field to specify the actual weight in g/mg (e.g., an eighth of cannabis should be set to "Eighth Per Unit," not "Each").


  4. Return to the transaction details page and click Resync Compliance at the bottom of the page. Refresh your browser to see the updated status.

💡 PRO TIP: Prevent this error! Ensure bulk flower or weight-based products are never mapped as "Each" during the product creation or intake mapping phases.

3. Metrc ID: Not Submitted

This status is commonly returned for two reasons: The transaction is for a non-cannabis product, or the cannabis product in the transaction does not have a Metrc ID assigned to it.

  1. If the transaction is for a non-cannabis product (lighters, t-shirts, etc.), no further action is needed! BLAZE intentionally does not send these to Metrc.

  2. If it is a cannabis product: Click on the product line item in the transaction, then select the Batches tab.

  3. Check if any batches have the Tracking System set to MANUAL instead of METRC.

  4. If so, assign the correct Metrc package tag to that batch.

  5. Go back to the transaction and click Resync Compliance.

💡 PRO TIP: Prevent this error! Do not sell cannabis products from a "Manual" tracking batch. Always ensure incoming inventory is properly mapped to a Metrc package tag.

4. Submission Error: Package does not exist in the current Facility

This error is returned when no product in your Metrc account is associated with the tag BLAZE is trying to send.

  1. Ensure that the tag is properly associated with the product in your Metrc account.

  2. Ensure the tag is correctly typed/scanned and associated with the product's batches in your BLAZE account.

NOTE: If the error reads "Package N/A does not exist," it is likely a non-cannabis item that was accidentally assigned a Metrc tracking category. Change the product category to a non-cannabis option.

💡 PRO TIP: Prevent this error! Never manually type package tags into BLAZE. Always use a barcode scanner or copy/paste directly from Metrc to avoid typos.

5. Submission Error: The Package will have a negative quantity after recording

This error occurs when BLAZE attempts to tell Metrc you sold an item, but Metrc believes that package tag currently has an inventory of zero (or a quantity less than what you just sold).

  1. Log into your Metrc account and review the sales and history of this specific package to confirm the discrepancy.

  2. If Metrc is incorrect, manually adjust the package in your Metrc account to reflect the true physical quantity on hand.

  3. Once Metrc has enough inventory to cover the sale, resubmit the transaction in BLAZE.

💡 PRO TIP: Prevent this error! Perform regular Cycle Counts in BLAZE to ensure your physical inventory exactly matches your Metrc inventory, preventing overselling.

6. Submission Error: Package has been discontinued and cannot have its contents sold

This error means the product/package is recognized by Metrc, but it has been marked as inactive, finished, or discontinued in the state system.

  1. Log into Metrc.

  2. Locate the product using the package number specified in the BLAZE error.

  3. Review its history. If it was prematurely finished, you must unfinish the package in Metrc before BLAZE can push the sale through.

💡 PRO TIP: Prevent this error! Do not "Finish" packages in Metrc until you are absolutely certain the physical inventory is depleted and no lingering sales need to be synced.

7. Metrc ID: SubmissionInProgress

This status is not an error! It means BLAZE has queued the transaction and is currently processing the data push to Metrc.

  1. BLAZE batches data to ensure system stability. Wait 15 to 30 minutes.

  2. If the status does not update, log in to your Metrc account and check the Sales > Receipts section to see if the transaction arrived successfully.

  3. If it is in Metrc, you can click Resync Compliance on the BLAZE transaction to force the ID to pull down.

💡 PRO TIP: Prevent this error! API delays happen. Give the system a few minutes to process during peak retail hours before assuming a sync has failed.

8. Metrc ID: SubmissionWaitingID

This status means the transaction in BLAZE was successful and the data has been sent to Metrc, but BLAZE is still waiting for Metrc to send the confirmation ID back.

  1. Navigate to the transaction details page in BLAZE.

  2. Click Resync Compliance.

  3. Refresh the page, and the Metrc ID will populate.

NOTE: You can also manually locate the Metrc ID by viewing the package history in Metrc. Once located, navigate back to the BLAZE transaction details page to manually type it in.

💡 PRO TIP: Prevent this error! Similar to "SubmissionInProgress", this is typically caused by Metrc API lag. Routine sync jobs will usually resolve this automatically within an hour.

9. Submission Error: Unauthorized

This error is returned when the Metrc Employee account linked to your API key does not have the necessary permissions enabled for submitting sales, or the API key has expired.

  1. Log into Metrc with an Admin account.

  2. Check the affected employee's permissions. Ensure they have MANAGE checked for the correct sales types (if they are restricted to "view" only, the API will reject sales).

  3. Generate a new API key from that Metrc employee login.

  4. Log into BLAZE, navigate to Global Settings > Integration Settings > Compliance > Metrc Facilities.

  5. Click Edit, paste the new key, click the Spyglass, and click Save.

    Screen Shot 2026-05-13 at 1.36.02 PM

💡 PRO TIP: Prevent this error! Always generate your BLAZE Metrc API key using a dedicated "Admin" level profile in Metrc to ensure permissions are never accidentally restricted during employee role changes.

For further troubleshooting steps when receiving Metrc Error notifications, please review this article.