METRC Audit Prep: What Inspectors Actually Check (and Where Operators Fail)

TL;DR: State regulators don't walk in blind. Before your inspector crosses the threshold, they've already run queries against your METRC account and flagged packages, manifests, and adjustment logs that don't reconcile. The physical walk-through confirms what the data already told them. This guide breaks down their checklist by category, names the violations that generate the most citations, and gives you a 48-hour prep protocol that holds up.

METRC audit prep gets treated like a fire drill at most dispensaries. Someone runs an active-packages report the night before, skims for obvious flags, and decides the store is clean. That is not a strategy. Inspectors arrive with printed discrepancy reports pulled directly from your METRC account. They already know where the gaps are before they knock.

This guide is for dispensary operators and compliance managers in METRC-regulated states. It covers what regulators actually audit, step by step, and where the typical retail licensee fails each check.

Step 1: Understand what inspectors pull before they arrive

Regulators in most states have direct read access to your METRC licensee account. Before the site visit, they pull:

• All active packages where the quantity in METRC does not match the last recorded adjustment
• Packages in “Transferred” status that have not been received by the destination facility within the required window
• Manifests where the vehicle arrived outside the declared route or time window
• Adjustment entries with no attached reason code, or with reason codes that appear at an unusual frequency
• Packages with no linked Certificate of Analysis, or with a COA tied to a different lot than the package tag

None of this is secret. Every METRC state publishes its inspection criteria in licensing regulations. Most operators do not read them. The inspection is not a surprise. It is a query you can run yourself.

Step 2: Package tag reconciliation

The inspector's first walk-through is a sample audit of active inventory against METRC. They pick a subset of packages and check five things:

Tag number. Every METRC package carries a 24-character UID that begins with 1A. The inspector scans it or reads it visually and confirms it matches the record for that package. A tag on the wrong package, a package with a missing tag, or a tag number that got one digit wrong in manual re-entry: all of these generate citations.

Quantity and unit of measure. If METRC says a package contains 28.35 grams, the physical container must contain 28.35 grams. Inspectors in most states carry a reference scale. The tolerance for finished retail packages in the majority of METRC states is zero. That is not a rounding window. It is zero.

Item category. The item category on the METRC tag must match the physical product class. Flower cannot be tagged under pre-roll. Concentrate cannot be tagged under edible. A category mismatch is treated as a potential diversion indicator, not a clerical error.

Location. Some states require packages to be tagged with a specific room or location ID in METRC. If the package record says Vault A and it is sitting in retail staging, that is a location discrepancy.

Movement timing. Most state regulations require METRC to reflect physical movements within the same business day. The most common failure: packages moved during closing and logged the next morning.

Step 3: Transfer manifest verification

Transfer manifests generate more citations than any other category. They are also the most fixable.

The receiving window. Most METRC states require the receiving licensee to formally accept the transfer in the system within 24 hours of physical receipt. Colorado requires acceptance the same calendar day. Michigan allows the next business day. The rule varies, but the failure mode is always the same: the delivery came in, receiving staff signed the paper, and nobody touched METRC for two days. An inspector who pulls a manifest sitting in “In Transit” status 36 hours after your staff signed for the product has an open-and-shut citation.

Manifest quantity vs. received quantity. A common error: the delivery arrives, the receiver signs the paper copy, and whoever enters METRC rounds the weight. A 0.3-gram difference on a bulk flower shipment creates a discrepancy that compounds every time that package is split or transferred downstream.

Operators who use a Zebra Android scanner to scan each incoming package tag at the point of receipt cut transcription errors sharply. The scan creates the METRC receiving event with the tag number pre-populated. The human enters the weight. If that weight comes from a connected scale rather than a handheld readout, the entry is close to error-free. Cloudbox scale setups pair directly with dispensary receiving environments to eliminate this transcription gap at the source.

Route timing. METRC manifests specify departure time, vehicle ID, and planned route. Inspectors cross-reference manifest timestamps against logged arrival times. A 45-minute transit logged for a 15-minute route is a flag.

Step 4: Adjustment log review

Every inventory adjustment in METRC must carry a reason code: theft/loss, destroyed, quality degradation, administrative correction, METRC entry error. Inspectors look at three things:

Frequency by reason code. One or two administrative corrections per quarter is unremarkable. Twelve in a month signals a systemic input problem, or a manual fudge. Regulators know the difference.

Adjustments without linked waste logs. In most states, product destruction requires a witness signature and a METRC waste entry. An adjustment that moves a package to zero quantity without a linked destruction record is a compliance gap with no clean explanation.

After-hours entries. Not always a violation, but it prompts follow-up questions. If your compliance manager is logging adjustments at 11pm on a Saturday, the inspector wants to know why.

Step 5: Lab result linkage

Every sellable package in METRC must have a passing Certificate of Analysis from a licensed third-party lab. The inspector checks that the COA linked in METRC:

• Comes from a licensed testing lab in your state
• Covers the same lot or batch as the package
• Has not expired (most states require retest after a defined window if the product has not sold)
• Shows passing results for all required panels: cannabinoid potency, pesticides, microbials, and residual solvents for concentrates

The most common failure: a COA linked to a parent batch that was split into multiple child packages, where the child packages do not have individual COA entries. Some states allow batch-level COAs to carry through to all children. Some require individual linkage at the child level. Know your state's rule.

Step 6: The 48-hour prep protocol

Run this two days before any scheduled inspection, or as a standing monthly practice.

1. Pull the Active Packages report. Filter for packages with a last-modified date more than 30 days ago. Any active package that has not had a METRC entry in 30 days is either stale data or a product that moved without a corresponding update.

2. Pull the adjustment log for the previous 90 days. Count by reason code. If any category shows more than three entries in a single month, document the root cause before the inspector asks.

3. Pull all manifests in In Transit status. If any are more than 24 hours old, contact the originating licensee, confirm whether the physical transfer occurred, and update METRC with the correct status and received quantity.

4. Run a 20-package physical spot check. Pick randomly. For each package: scan the METRC tag, confirm the quantity on a reference scale, confirm the physical location matches the METRC location field, and confirm the COA is linked and valid.

5. Confirm your scanning hardware is operational. Scanner batteries charged. METRC integration syncing.

Common mistakes that compliant operators still make

Receiving in METRC before weighing. Sequence matters: weigh first, receive second. Staff who click receive the moment the driver shows up force a correction entry if the weights differ from the manifest.

Leaving transferred packages on-site. A package in Transferred status in METRC that is still physically in your vault is a contradiction. A transferred package must leave the facility before the manifest closes.

Inconsistent decimal rounding. Round every weight entry to the same number of decimal places your scale reports. Small discrepancies accumulate across a large inventory and at volume they look deliberate.

Not knowing your state's specific windows. The 24-hour transfer receipt rule is common but not universal. Colorado's same-day rule has caught operators who knew the 24-hour standard from a previous license in a different state.

What a connected-scale setup changes

The inspection category that benefits most from hardware is the quantity check. A connected scale that writes weight directly to METRC at the point of receipt removes the manual transcription step. The inspector pulls the receiving history for any package and sees the weight as-recorded by the scale, not as-remembered by whoever typed it in. That audit trail is a different conversation with a regulator.

Cloudbox integrates with METRC via the compliance API and supports connected-scale setups for both receiving verification and ongoing package weight tracking. For a full picture of how continuous inventory verification works in cannabis retail, see Cloudbox for Cannabis. To walk through how weight verification slots into a dispensary receiving operation, book a session with the Cloudbox team.

For state-specific METRC requirements, verify against your state cannabis control board regulations and your state's METRC implementation guide before your next inspection.

This guide reflects METRC requirements as published in state licensing regulations. Specific windows, tolerance thresholds, and required fields vary by state.