The Treez integration with Metrc operates in real-time. Meaning, that unless there are pending sales and/or adjustments that have not yet been uploaded to Metrc, every package’s quantity should always match across both systems. However, there are a variety of circumstances (such as manual action in Metrc, API outages, human error, etc.) that can cause these quantities to fall out of sync, and create an inventory discrepancy. When discrepancies occur it’s important you promptly identify them, determine the cause, and take necessary corrective action to bring these numbers back into alignment.
NOTE: We recommend investigating discrepancies only after completing an inventory count for the packages in question.
- Identifying Inventory Discrepancies
- Comparing Package Histories
- Common Causes and Resolution
Identifying Inventory Discrepancies
Being able to find where discrepancies exist is the first step to resolving them. You can easily see a list of all the packages with different quantities in Treez and Metrc by following these steps.
Step 1: Navigate to Inventory > Compliance Management and click on the Metrc True Up tab.
TIP: All packages included in the True Up table have a discrepancy between the Treez quantity and the Metrc quantity.
Step 2: Reference the ‘Treez Count’ and ‘Current Metrc Qty’ columns to see each system’s count, and the ‘Adjustment’ column to see the difference.
Comparing Package Histories
A package’s history can give you clues as to where the discrepancy may have originated. Every sale, return, and adjustment in a package’s history in Treez should have a corresponding ‘twin’ in Metrc. Follow the steps below to compare a package’s history between Treez and Metrc.
Downloading Metrc Package History
Step 1: Log-in to Metrc and click Packages.
Step 2: Select the appropriate tab (Active, On Hold, Inactive, or In Transit) for the package you’re investigating.
Step 3: In the ‘Tag’ column, click the vertical 3 dots and then click Filter.
Step 4: Set the filter dropdown to ‘Ends with’ and enter the package ID into the text box. Click the orange Filter button.
Step 5: On the far left-hand side of the package’s row, click the arrow to expand the package’s details.
Step 6: Click on the History tab and click the ‘Date’ column once to sort the actions on the package with the oldest actions displayed first.
Step 7: On the far right-hand side of the package’s menu, click the printer icon, and select either Excel or PDF, whatever your preferred format is for viewing the package’s history.
Step 8: Open the file that downloads from Metrc.
Opening the Package History in Treez
Step 9: In Treez, navigate to Reports > Inventory > Log.
Step 10: Click the filters icon, and enter the Metrc package ID in the ‘State Tracking ID’ field and hit the Enter key to filter for only the relevant package.
Step 11: In the ‘Activity’ column, uncheck these actions:
- Created from Split
- Split Batch
Step 12: Set the date range filter to include the first date on the Metrc package history to today’s date.
Step 13: Click the ‘Date Modified’ column header once to sort the results with the oldest actions displayed first.
Comparing the Metrc and Treez Histories
Step 14: Open the Metrc package history.
TIP: For ease of comparison, we recommend keeping the Metrc and Treez package histories adjacent to each other, either in separate windows on a computer or printed out.
Step 15: Starting with the oldest action, match each sale, adjustment, and return across both package histories.
In some cases, the order of the package history actions and/or the date and timestamp may be different, and so you can also try to count and match the number of each action across both systems. For example, matching 10 total sales with the same total number of units across both package histories (regardless of their chronological order and date/timestamp) would indicate the same sales were recorded but perhaps at different times.
If you identify an action that is present in one package history but missing from the other, follow the steps in the Common Causes and Resolutions to investigate and address the discrepancy.
NOTE: If there is a sale discrepancy, note the Receipt ID number, because you’ll need it for resolution.
Common Causes and Resolutions
There are many different scenarios that could cause a discrepancy, but there are simple steps for resolving the vast majority of them.
Sale or Adjustment in Treez, but Missing from Metrc
The Metrc API allows communication between Treez and Metrc but when there are issues with this connection, Metrc becomes unable to accept tasks sent from Treez. The most common cause of this issue is the Metrc API being unavailable, overloaded, or other technical issues making it unable to receive sales or adjustments. Though less common, if your API Key was changed in your Metrc portal or you recently received a new license number without updating this information in Treez, this could also cause errors with the API connection.
NOTE: Once the API Key is generated and shared with Treez, it should never be changed without proper coordination with Treez. When an API Key is changed, all sales and inventory adjustments made in Treez will be rejected by Metrc, causing many 401 errors on the Metrc Control page. If this is the case, contact support as soon as possible for assistance updating your integration credentials.
If a sale or adjustment is present on the Treez package history but missing from the Metrc package history, follow these steps to resend the task from Treez to Metrc on the Metrc Control page. If there are any sales or adjustments remaining on the page after resending, review them carefully by following the steps in Troubleshooting Tasks Stuck on Metrc Control. They may require manual correction and upload into Metrc.
If you have sales or adjustments missing from Metrc, it’s vital to your compliance to resend tasks from Metrc Control or troubleshoot using a CSV, instead of performing a true-up. This is why:
A true up adjusts packages, and doesn’t report sales. So even though a true-up would make the inventory counts match between Treez and Metrc, the sales would be unreported to Metrc and create a discrepancy in the package’s history.
Resending adjustments from Metrc Control maintains data from the original adjustment such as timestamp, amount, reason, and notes. A true-up works as a separate adjustment to make Metrc counts match Treez counts, which won’t accurately reflect the original adjustment.
Sale in Metrc, but Missing from Treez
If a sale is present on the Metrc package history, but missing from the Treez package history, it indicates the sale was recorded in Metrc without using the Treez integration.
The most common cause of this issue is when an employee manually enters a sale directly into the Metrc portal. Though less common, if your shop uses multiple Metrc integrations, the sale might’ve been sent to Metrc by another software provider.
TIP: The ‘External App’ column on the Metrc package history shows which integrator recorded the sale — if you find sales discrepancies from any integration that isn’t Treez, contact the source before proceeding.
To resolve this issue, follow these steps to void the sale in Metrc.
Step 1: Log in to your Metrc portal, and navigate to Sales > Active.
Step 2: In the ‘Receipt’ column, click the vertical 3 dots and then click Filter.
Step 3: Set the filter dropdown to ‘Ends with’ and enter the Receipt ID (from Step 15 above) into the text box. Click the orange Filter button.
Step 4: On the far right-hand side of the sale’s row, click the Void button.
Once the sale is voided, it’s essentially ‘undone’ and removed from the package’s sales history in Metrc.
Adjustment in Metrc, but Missing from Treez
If an adjustment is present on the Metrc package history, but missing from the Treez package history, it indicates the adjustment was recorded in Metrc without using the Treez integration.
The most common cause of this issue is when an employee manually adjusts a package in the Metrc portal. Though less common, if your shop uses multiple Metrc integrations, the adjustment might’ve been sent to Metrc by another software provider.
TIP: The ‘External App’ column on the Metrc package history shows which integrator recorded the adjustment — if you find adjustment discrepancies from any integration that isn’t Treez, contact the source before proceeding.
Unlike sales, there is no way to void an adjustment in Metrc. Follow these steps to use the Metrc True Up page to easily adjust the package’s inventory count or weight in Metrc, bringing it back in sync with Treez.
Article is closed for comments.