Compliance and Track-and-Trace
METRC common errors and fixes: the dispensary operator guide

Powered by StealthAgents
Compliance and Track-and-Trace

Cannabis dispensaries in METRC states operate under one rule that has no exceptions: what the system shows must match what is on your shelves. When those two views diverge, you have a compliance problem, and compliance problems have real consequences for your license.
This guide covers the METRC errors dispensary compliance teams encounter most often, the exact steps to resolve each one, and the daily procedure that prevents most of them from ever occurring. It also covers employee training, API integration with your point-of-sale system, audit preparation, and the state-by-state rule differences that trip up multi-location operators.
METRC errors fall into a small number of categories. Knowing which category an error belongs to tells you where the breakdown occurred in your workflow, which makes resolving it faster and more defensible during a state review.
The most common categories are package discrepancies, transfer errors, sales entry mismatches, adjustment failures, and API sync gaps. Each has a distinct root cause and a specific resolution path.
Starting with the right category saves significant time. A package-not-found error has a different fix than a quantity mismatch, even though both surface as red flags in your compliance dashboard.
| Error Category | Common Cause | First Resolution Step | Correction Window |
|---|---|---|---|
| Package not found | Transfer received but not accepted in METRC | Locate open transfer, complete acceptance with correct date | Same day preferred |
| Quantity mismatch | Unrecorded sale or receiving discrepancy | Pull POS sales report, match each line to METRC entries | Up to 30 days in most states |
| Transfer manifest error | Wrong unit, quantity, or tag from originating licensee | Contact originating licensee to void and resubmit | Before state acceptance deadline |
| Adjustment failure | Missing supervisory approval or incorrect adjustment type | Review state compliance bulletin for current approval requirements | 7-30 days depending on state |
| API sync gap | POS-to-METRC queue backed up or integration failure | Force sync from POS admin panel, verify in METRC dashboard | Immediate action required |
METRC is a seed-to-sale tracking system used by state regulators to follow cannabis from cultivation through the final retail transaction. For a dispensary, the tracking begins the moment you accept an inbound transfer from a licensed cultivator, manufacturer, or distributor.
Every package entering your facility carries a METRC tag, a barcode that remains attached to that product until it is sold, destroyed, or transferred out. Your obligation is to record every movement of that package within your facility in real time.
The gap between what happened physically and what was entered into METRC is where most errors originate. A sale that closed at 9:45 PM and was not recorded until the next morning creates a discrepancy in the system, even if your inventory count is accurate. METRC does not know about physical events; it only knows about entries.
A "package not found" error occurs when METRC cannot match a barcode scan to an active package record in your facility. This appears most often during retail sales or when running an inventory count against your active package list.
The most common cause is an intake error. A transfer was physically received and placed on shelves, but the acceptance was not completed in METRC. The product exists in your building but does not exist in your active inventory as far as the system is concerned.
To resolve it, go back to your transfer records and check whether the incoming manifest was formally accepted. If you find an unaccepted transfer, complete the acceptance with the correct date and verify that the package tags on the manifest match what is on your shelves. If the tags do not match, contact your state METRC support line with the manifest ID, since they can often locate the package record using batch or source data even when the tag scan fails.
If the transfer was accepted correctly and the package still does not appear, the tag itself may have been damaged or entered incorrectly during intake. Your state METRC administrator can create a correction entry with proper documentation.
Prevention is simpler than the fix. Run a tag-by-tag verification against the physical manifest before completing any transfer acceptance. Your receiving staff should confirm that each barcode scan returns an active record in the transfer before they finalize the intake.
Quantity mismatches are the most common METRC error in active dispensaries. Your POS shows 12 grams of a product remaining; METRC shows 15. That 3-gram gap must be explained and documented.
Start with your end-of-day sales reconciliation for the period in question. Pull your POS sales report and compare each transaction line to the corresponding METRC sales entry. The missing record is usually there, either unsubmitted or submitted against the wrong package tag.
Once you identify the unrecorded transaction, enter it in METRC using the correct transaction date and time, not the current date. Most states allow corrections within a 30-day window, though some require supervisory sign-off for corrections older than seven days. Check your state's current bulletin for the applicable policy.
If your line-by-line comparison does not surface a missing transaction, the gap may reflect a physical inventory problem rather than a data entry problem. Run a cycle count for that specific product category and compare the physical result to your METRC active packages. A physical count that comes out different from both your POS and METRC records points to a receiving or theft issue, not a data entry issue, and requires a separate investigation path.
Transfer manifest errors appear when a package arrives from a licensed supplier but the manifest data does not match your order, your state's format requirements, or the product you physically received. Common causes include incorrect unit-of-measure fields, mismatched product categories, quantities that do not match the delivery, and package tag numbers that differ from what is on the physical product.
When a manifest arrives with errors, do not accept the transfer in METRC until the originating party corrects it. You cannot edit an incoming manifest yourself. The correction has to be submitted by the cultivator, manufacturer, or distributor who created it through their own METRC account.
Contact the originating licensee immediately with the specific discrepancy. Ask them to void the original manifest and resubmit a corrected one with the right information. Document your outreach with timestamps. If they are slow to respond, note that your state regulator may need to be notified if the transfer remains open past your state's acceptance window.
Once you receive the corrected manifest, verify it against the physical product before accepting. Keep the original rejected manifest and your correspondence in your compliance records. Auditors occasionally ask to see the chain of corrections for a transfer.
A transfer is voided when a shipment is rejected at your facility, the wrong product was sent, or the manifest was created by mistake. The void process is time-sensitive in most states and must happen before the physical product is moved or stored.
In METRC, navigate to the incoming transfers section, locate the transfer record, and select the reject or void option. A rejected transfer returns the packages to an active status with the originating licensee. They must then reconcile those packages on their end.
Do not void or reject a transfer after you have already completed the acceptance in METRC. Once a transfer is accepted, those packages are in your active inventory. Correcting an accepted transfer requires an adjustment or a coordinated correction with your state compliance team, not a void.
If you accepted a transfer that should have been rejected and you realize the error shortly after, contact your state METRC support line the same day. Some states have a brief window during which an accepted transfer can be corrected without a formal compliance report. Acting quickly gives you options that waiting does not.
Sales entry discrepancies occur when the quantities recorded in METRC do not match your POS transaction records at the end of the day. There are two root causes: manual entry errors and POS-METRC integration failures.
For dispensaries with a direct POS-METRC integration, a sync failure is the most common culprit. Your POS attempted to push a sales record to METRC but the API call failed, and the failure was not visible to floor staff. Check your POS system's METRC integration error log at the end of every shift. Any failed call shows up there and requires a manual correction entry.
For dispensaries using manual METRC entry, entry errors are almost always the cause. Misread package tags, wrong quantities, and incorrect unit-of-measure fields each cause a discrepancy that the daily reconciliation should catch. Running the reconciliation before closing, while staff who made the entries are still on site, makes corrections faster.
A consistent daily reconciliation procedure eliminates most METRC errors before they compound. Build it into your closing checklist, run it at the same time every day, and assign it to one person, not to whoever has time.
The procedure runs in four steps.
First, pull your POS end-of-day sales report. This should show every transaction, the product sold, the quantity, the unit of measure, and the timestamp.
Second, pull your METRC sales history for the same date range. Most METRC state portals have a sales report you can filter by date.
Third, compare total units sold in each product category. Any category where POS totals and METRC totals do not match requires a transaction-by-transaction comparison. Find the specific entries that did not cross over.
Fourth, enter any missing records in METRC with the correct transaction date and timestamp. Document the correction in your compliance log with a brief note explaining why it was needed.
A reconciliation that takes more than 30 minutes every night signals that your POS-METRC connection is not working correctly, or that your manual entry volume is too high for your current team capacity. Either issue is solvable with the right tools or support structure in place.
Package adjustments are required whenever product is damaged, spilled, contaminated, or otherwise cannot be sold. Adjustment errors occur when the wrong reason code is selected, the quantities do not match the physical event, or the entry is logged on the wrong date.
Your state regulator publishes an approved list of reason codes for your METRC instance. Using a reason code that is not on the approved list generates an automatic compliance flag. Download your state's current reason code list and post it in your compliance area so staff can reference it before entering any adjustment.
Match the date on every adjustment to the date the event actually occurred, not the date you are entering it. An adjustment dated after the physical event it explains will appear inconsistent in an audit review, even with documentation. If you need to log a past event, use the correct historical date and note in your records when the entry was actually made.
For product destruction events, check whether your state requires advance notice to the regulator or a licensed witness for events above a certain weight threshold. California, Colorado, and Michigan each have different requirements for witnessed destruction. Getting this wrong generates a compliance notice even when the underlying disposition of the product was legitimate.
A missing package investigation starts when a package appears in your METRC active inventory but cannot be physically located in your facility. This is a high-priority compliance event that requires immediate, documented action.
Step 1: Conduct a physical count of all products in the category the missing package belongs to. Do not rely on your POS inventory report for this count. Go to the physical product and count it.
Step 2: Pull the full transaction history for the missing package tag in METRC. Look for a transfer, adjustment, or sale that may have moved the product without a corresponding physical movement.
Step 3: Check whether the package was accidentally included in an outgoing transfer to another licensed facility. If you find it in a completed transfer, the receiving licensee holds it in their METRC inventory. Contact them and your state compliance team.
Step 4: Check for a receiving error. The package may have been accepted in METRC but stored under a different tag or in a location not reflected in your inventory system.
Step 5: Document every step you take with timestamps and the names of staff involved. This documentation is your compliance record.
Step 6: If you cannot locate the package after completing steps 1 through 4, report it to your state compliance team before your next reporting deadline. Most states have a formal process for reporting missing inventory. Early disclosure is treated differently from a discrepancy discovered during an audit.
METRC errors are almost always caused by a process gap or a training gap. Process gaps require workflow changes. Training gaps require a structured program that covers both the system and the stakes.
A METRC employee training program that reduces error volume covers four areas.
Tag handling and package verification is the foundation. Every employee who touches product should be able to match a physical tag to its METRC record, identify a damaged or misread tag, and know who to notify before a scan failure becomes an accepted error.
Transfer intake is where many dispensaries take on compliance risk without realizing it. Receiving staff should know how to verify a manifest against the physical delivery, how to identify a quantity or category mismatch, and how to pause an acceptance until a discrepancy is resolved rather than accepting and correcting later. Accepting and correcting is significantly more complicated than refusing and requesting a corrected manifest.
Sales entry and POS integration knowledge matters even for floor staff who never log directly into METRC. They should understand whether their sales actions in the POS push to METRC automatically, which ones require manual follow-up, and what a failed sync looks like in the POS interface.
Compliance incident reporting is the final area, and the one most often omitted from training. Every employee should know who the compliance lead is, how to report a discovered discrepancy, and what not to do while waiting for direction. Acting on a discovered discrepancy without guidance from your compliance team often makes the documentation trail harder to explain, not easier.
Keep training records. Log who was trained on what and when, with a signature or timestamped acknowledgment from each employee. Training records are routinely requested during state inspections.
New staff who have never used METRC need hands-on practice before they touch live records. Most state METRC portals have a training or sandbox mode that lets new employees practice package creation, transfers, and adjustments without affecting your real inventory. Use it.
Walk through the METRC support portal training guides with new compliance-adjacent employees before their first shift on live records. These guides are maintained by METRC for each state and cover the role-specific actions your staff will actually perform.
Pair new staff with an experienced team member for the first two weeks of METRC work. Catching an entry error in real time, before it compounds, is the most effective training for preventing the next one. A new employee who makes a mistake and watches it get corrected properly learns more from that single event than from any amount of classroom instruction.
A direct METRC API integration between your point-of-sale system and your METRC state instance is one of the most reliable ways to reduce manual entry errors. When the integration is working correctly, retail sales push to METRC in real time without any additional staff action.
Dutchie, Flowhub, and Treez are among the POS platforms that offer documented METRC integrations for dispensaries. The quality and state coverage of those integrations varies. Before selecting a POS system, verify which states that integration is certified for, because METRC API certification is state-specific and a POS certified in Colorado may not be certified in Michigan.
When evaluating a POS-METRC integration, check for three things: real-time sync rather than batch sync, a visible error log that shows failed API calls with enough detail to identify the specific transaction, and a manual override path for transactions that the automatic sync cannot process.
An integration that syncs on a batch schedule, pushing records every hour or at shift end, still leaves a window during which your POS and METRC are out of alignment. For a high-volume dispensary, that window is enough time for a quantity discrepancy to grow into a reportable gap.
If your current POS does not have a certified METRC integration for your state, compare current manual-entry time, correction workload, implementation costs, and state-specific integration support before switching. Document baseline error and correction metrics so the operator can evaluate any change using its own results.
A state cannabis inspection is less stressful when your daily reconciliation is current and your adjustment records are complete. The two most common audit triggers are unexplained inventory gaps and adjustments that lack supporting documentation.
Audit preparation begins 30 days before the inspection date, not the evening before. Pull your METRC audit report and look for open discrepancies, incomplete adjustments, and packages with unusual transaction histories. Resolve every open item you can find before the inspection.
An auditor who finds a discrepancy you were not aware of is in a different position than an auditor who finds a discrepancy you already corrected and documented. The former suggests a systemic problem; the latter demonstrates that your compliance process caught the issue.
Your audit prep checklist should work through these areas in order.
Current physical inventory: run a full physical count within two weeks of the inspection and reconcile it to your METRC active package list. Document the count date, the staff who participated, and any discrepancies found and resolved.
Adjustment records: pull all adjustments entered in the past 12 months and verify that each one has a reason code, a date that matches the physical event, and supporting documentation where required by your state. Flag any that are missing documentation and fill the gap before the inspection.
Transfer records: pull your inbound and outbound transfer history and verify that each accepted transfer has a completed acceptance entry with the correct date. Look for any transfers that show as pending longer than your state's acceptance window allows.
Employee training records: compile a list of every employee with METRC access and verify that each one has a training record on file. Include the date of training, the topics covered, and any competency verification you completed.
Compliance notices: if your dispensary has received any compliance notices or violation warnings in the past 24 months, have your written responses and corrective action documentation ready. An auditor who sees a past notice and no documented response has reason to ask more questions.
METRC operates in roughly 30 states as of 2026, but the compliance rules are not identical across those states. METRC is the software; your state cannabis regulator sets the specific reporting requirements, deadlines, and correction policies. The same error can have different consequences depending on where your dispensary operates.
The four differences that matter most to daily operations are correction windows, transfer timing requirements, destruction witness rules, and package manipulation restrictions.
Correction windows vary more than most operators realize. Some states allow corrections to past entries for up to 30 days with no special approval. Others require supervisory sign-off or a compliance team review for any correction older than seven days. A few states require a formal amendment request for corrections beyond 48 hours. Not knowing your state's window is a risk that surfaces when you try to correct an old entry and find you cannot.
Transfer timing requirements also differ. Several states require that incoming transfers be accepted in METRC on the same business day they are physically received. Others allow acceptance within one business day or within a defined window. If your receiving process finishes after business hours and the acceptance happens the following morning, you may be creating a reportable timing gap depending on your state's rule.
Destruction and waste events are among the most state-specific areas. Some states require advance notice to the regulator before any product destruction event above a certain threshold. Others require a licensed employee or state representative to witness the destruction. A few require the witness to be a compliance officer with specific credentials. Disposing of unsaleable product without meeting your state's witness or notice requirement generates a compliance violation even when the disposition itself was legitimate.
Package splitting and combining rules vary as well. Some states allow a METRC package to be split into two smaller packages for operational or sales reasons. Others prohibit splitting entirely or require a specific reason code and advance approval. Using an unsupported package manipulation in a state that restricts it will generate an automatic flag.
Check your state's current METRC documentation regularly. Regulations change when a state updates its cannabis program rules, and those changes sometimes take effect before operators are aware of them. The state-specific documentation and bulletin archives are available through the METRC state portal for each licensed state.
Audit flags are patterns in your METRC records that signal potential compliance issues to state regulators reviewing your activity. Understanding which patterns generate flags lets you avoid creating them.
Frequent voids are one of the first patterns regulators notice. A high volume of voided transfers or voided packages signals that transfers are being created before verification, or that products are moving without proper documentation. Individual voids are legitimate and expected. A pattern of them suggests that the front end of your intake process is skipping verification steps.
Late adjustments are another common flag. An adjustment entered weeks after the event it describes, without a clear explanation in the record, looks like a retroactive cleanup rather than a genuine record of what happened. If you must enter a late adjustment, note the reason for the delay in your documentation alongside the entry.
Below-zero package quantities appear when a sale is recorded against a package that METRC shows as empty or when a quantity error from an earlier entry compounds. Negative quantities are a high-priority flag because they represent a scenario where the system believes you sold product you did not have. They are almost always data entry problems, not inventory problems, but they require immediate correction and clear documentation.
Unusual after-hours transaction activity, meaning records entered in METRC well outside your operating hours or on days your dispensary is closed, can prompt questions from reviewers. Not every after-hours entry is a problem, but patterns of after-hours adjustments without explanation look like retroactive record cleaning.
Irregular reconciliation history is visible in audit reports. A compliance record that shows clean daily entries for weeks followed by a cluster of same-day corrections for that entire period tells a story that the corrections were batched rather than real-time. Consistent daily reconciliation, even on quiet days, creates a record that looks like a real operational process.
Most METRC errors happen when compliance reporting is a secondary task, handled by someone whose primary responsibility is something else. A budtender entering METRC records at the end of a nine-hour shift is more likely to make a mistake than a staff member whose morning routine is built around accurate data entry and reconciliation.
A trained compliance VA handles the daily METRC tasks that are error-prone when left to general staff: transfer acceptance verification, sales entry reconciliation, adjustment documentation, and audit prep organization. These are time-consuming, repetitive, and high-stakes tasks. They benefit from consistency and attention to detail, not speed.
The common pattern in dispensaries with high METRC error rates is that compliance tasks are distributed across multiple people who each own a piece without anyone owning the whole. A VA dedicated to the compliance workflow closes that gap.
For more on what a dedicated compliance VA handles in practice, see our METRC reporting support page. For a detailed walkthrough of the daily reconciliation steps, the dispensary daily reporting guide covers the core procedure in depth.
Q: How far back can I correct a METRC entry?
A: The window depends on your state. Most METRC states allow corrections within 30 days. Some states require supervisory approval for corrections older than seven days. Check your state's current METRC bulletin or contact your state's METRC administrator for the exact policy in your jurisdiction.
Q: What is the difference between a package adjustment and a package void in METRC?
A: An adjustment reduces or modifies the quantity on an active package. It is used for waste, damage, spillage, or inventory corrections. A void removes a transfer record entirely and is used when a transfer was created in error or rejected before acceptance. You cannot void a package after it has been accepted into your active inventory.
Q: What happens if my POS and METRC fall out of sync and I cannot find the cause?
A: Start with your POS integration error log. Most POS systems with a METRC integration maintain a log of failed API calls, showing the specific transaction and the reason the call failed. If you cannot find a clear cause there, contact your POS support team with the specific package tags and transaction dates. They can usually identify where the sync broke down faster than a manual line-by-line comparison.
Q: What does a METRC compliance violation notice require from me?
A: Respond in writing within the timeline specified in the notice. Your response should describe what happened, the corrective steps you have already taken in METRC, the process changes you have made to prevent recurrence, and any supporting documentation. A prompt, documented response with real corrective action is treated differently from silence or a vague acknowledgment. Keep copies of both the notice and your response in your compliance file.
Q: Does every dispensary employee need their own METRC login?
A: No. METRC access should match the role. Floor staff typically need access only for retail sales entry, if your POS integration does not handle that automatically. Compliance managers need access to transfers, adjustments, and audit reports. Reducing the number of users with full access reduces the surface area for entry errors and creates clearer accountability when something goes wrong.
Q: What is seed-to-sale tracking and how does METRC fulfill it?
A: Seed-to-sale tracking is the regulatory requirement that a state can follow any cannabis product from the point of cultivation through every business transaction to the final consumer. METRC is the software that most states use to fulfill that requirement. As a dispensary, your portion of the chain begins when you accept an inbound transfer and ends when you record a retail sale or log a final disposal.
Q: Can my dispensary use METRC without a POS integration?
A: Yes. Manual METRC entry is operationally acceptable, and many dispensaries operate this way, particularly in markets where their POS does not have a certified state integration. Manual entry carries a higher error rate than a direct integration, especially at volume. For high-volume dispensaries doing manual entry, a dedicated compliance staff member or VA handling that function significantly reduces error rates compared to distributing it across general staff.
Q: How often should we run a full physical inventory count against our METRC records?
A: Most state regulations require at least an annual physical inventory count. Many dispensaries run cycle counts monthly or quarterly on high-value or high-volume product categories. The more frequently you reconcile physical counts to METRC records, the shorter the window in which a discrepancy can grow. A dispensary that only counts annually may not discover a meaningful gap until it has compounded over months.