Compliance and Track-and-Trace
How to reconcile METRC inventory with your POS system

Powered by StealthAgents
Compliance and Track-and-Trace

Inventory reconciliation is the operational task that sits at the center of cannabis compliance. When your METRC record and your POS system disagree about how much product you have, you have a compliance exposure that grows with every transaction you process on top of it.
This guide walks through the reconciliation process step by step, covers the most common causes of mismatches, and explains how to build a daily routine that keeps your records clean before discrepancies compound.
The reconciliation process compares what METRC says you have against what your POS says you have. When the two match, you are in compliance. When they do not, you need to find the source of the gap and correct it in METRC with the right date and reason.
Start with a specific product category or package tag, not your entire inventory at once. Trying to reconcile everything simultaneously makes it harder to isolate where the breakdown happened.
Pull your current package list from METRC and your current inventory from your POS side by side. Look for packages that appear in one system but not the other, and for quantities that differ on packages that appear in both.
The most common cause of a mismatch is a failed sync between your POS and your METRC API connection. Your POS attempted to push a completed sale to METRC but the call failed silently, and the product was deducted from your POS inventory without a matching METRC entry.
The second most common cause is a manual entry error. A cashier keyed a wrong quantity, selected the wrong package tag, or entered a sale against a product category rather than the specific package. Each of these creates a gap that only a transaction-level comparison will find.
The third cause is a receiving error. A transfer was accepted in METRC but with a different quantity than what was physically received, or a package was received physically but the METRC acceptance was never completed. Both scenarios create a persistent mismatch that will not self-correct.
Step 1: Pull your POS end-of-day report. Export your sales transactions for the period you are reconciling, ideally at the end of each shift or business day. The report should show each transaction, the package tag or product ID, the quantity sold, and the timestamp.
Step 2: Pull the corresponding METRC report. Log into your state METRC portal and pull the sales or activity report for the same date range. Filter by package tag if you are investigating a specific item.
Step 3: Compare totals by product category first. If a whole category is off, the issue is likely a batch sync failure or a receiving error affecting multiple packages. If one specific tag is off, the issue is likely a single missed transaction or a manual entry error on that package.
Step 4: Find the missing entry. For a quantity gap on a specific package, pull the full transaction history for that package tag in METRC. Look for a period where sales stopped recording, or where a large quantity dropped without a corresponding METRC entry.
Step 5: Enter the correction. In METRC, enter the missing transaction or adjustment with the correct date it occurred, not today's date. Most states allow corrections within a 30-day window. Document the reason for the correction in your compliance log.
Step 6: Verify the fix. After entering the correction, pull the package report again and confirm that the METRC quantity now matches your POS.
Missing sale entry: Your POS shows a sale occurred, but METRC does not show the corresponding reduction. Enter the sale in METRC with the correct transaction date and package tag.
Duplicate METRC entry: METRC shows a quantity reduction that your POS does not show. This happens when a manual METRC entry was made to correct an earlier problem, then the POS sync also pushed the same transaction. Identify which entry is the duplicate and void the incorrect one.
Wrong package tag on a sale: The sale was recorded correctly in your POS but pushed to METRC under the wrong package tag. Void the entry under the incorrect tag and re-enter it under the correct tag with the original transaction date.
Acceptance quantity error: A received transfer was accepted in METRC with a quantity that does not match the physical product. If the error is recent, contact your state METRC support to correct the acceptance. If time has passed, you may need a formal adjustment with documentation.
A daily reconciliation routine catches problems when they are small. A gap from a single missed transaction is easy to explain and easy to correct. A gap that has been accumulating for two weeks across dozens of transactions requires significantly more time to unwind.
Assign the reconciliation to a single person with a defined time and checklist. Distributing it across whoever is available means it gets done inconsistently and accountability is unclear when something slips through.
Run the reconciliation before closing, while staff who handled transactions during the shift are still on site. If a discrepancy requires a human explanation for something that happened at the register, you want to ask that question the same day.
Most inventory discrepancies are data problems, not physical problems. You are missing an entry, not missing product. Handle these yourself through the standard correction process.
Escalate to your state compliance team when you cannot locate the physical product that METRC shows you should have, when a discrepancy involves a large quantity that you cannot reconcile through your transaction history, or when a discrepancy appears to involve a transfer to an outside facility that you did not initiate.
Early disclosure is consistently treated differently from a discrepancy discovered during an audit. If you discover a gap that you cannot resolve on your own, contact your state compliance team before your next reporting deadline. State-specific METRC documentation, including correction policies and reason code lists, is available through the METRC state portal for your licensed state. For detailed guidance on specific METRC error codes, the METRC errors guide for dispensaries covers the full range of correction scenarios.
Dispensaries that run daily reconciliation consistently typically have one thing in common: the task belongs to one person who owns it completely. When reconciliation is distributed across general staff as a secondary task, it gets deprioritized on busy days, which is exactly when errors are most likely to accumulate.
A trained compliance VA handles the reconciliation process as a core responsibility, not a secondary task. They run the comparison, identify the gaps, enter the corrections, and maintain the compliance log every day without relying on the floor team to remember. For more on what this role covers in practice, see our METRC reporting support page.
Q: How often should I reconcile METRC with my POS?
A: Daily reconciliation is the standard for dispensaries that want to stay compliant without scrambling before inspections. Reconciling at the end of each business day means any gap is at most one day old when you find it.
Q: What if my POS integration is supposed to sync automatically with METRC?
A: Automatic syncs fail. Check your POS system's METRC integration error log daily even if you believe syncing is working. Most POS platforms maintain a log of failed API calls with the specific transaction details, and those failed calls require manual correction entries in METRC.
Q: Can I reconcile weekly instead of daily?
A: A weekly reconciliation is better than no reconciliation, but gaps compound between review cycles. A discrepancy that is one day old is typically a single missed transaction. A seven-day-old gap may involve dozens of transactions across multiple package tags and is significantly more complex to unwind.
Q: What documentation should I keep after making a METRC correction?
A: Keep a log entry for every correction that includes the correction date, the original transaction date, the package tag, the quantity changed, the reason for the correction, and the name of the staff member who made it. State auditors occasionally ask to see correction histories, and a clean log demonstrates that your compliance process caught and addressed the discrepancy rather than ignoring it.
Q: Do I need to notify my state when I find a discrepancy?
A: Most small data corrections do not require state notification. You make the correction in METRC directly and document it in your compliance records. Notification is required when you cannot locate physical product, when a gap exceeds your state's reportable threshold, or when your state's regulations specifically require reporting within a defined timeframe. Check your state's current compliance bulletin for the exact threshold and timing requirements.