
Your count day starts at 7am. By noon, you're three shelves in and one employee is arguing with the spreadsheet. By 4pm, METRC still doesn't match. By 6pm, someone makes a decision: enter it anyway and figure it out later.
This is how compliance violations start. Not from malice. From a process designed for a smaller operation that never got replaced.
METRC inventory reconciliation doesn't require a full-facility shutdown every quarter. Here's how to do it continuously instead.

METRC is a seed-to-sale tracking system. It records what regulators need to see: who transferred what, to whom, when. It's not designed to verify physical quantities in real time. That gap is your problem.
The discrepancies that trigger violations usually come from four places.
First, packaging yield variance. You process a batch. You package 48 units instead of 50 because two were damaged. If that variance doesn't get logged correctly in METRC, you have two phantom units in the system.
Second, transfer entry lag. Product moved. The METRC entry happened the next morning. For eight hours, the physical count and the record don't match.
Third, manual transcription errors. Weight on the scale. Employee reads it, writes it down, types it into METRC. Three steps where the number can drift.
Fourth, batch rounding. Unit weights vary slightly. Rounding during lot entry compounds over time. What looks like a rounding error on day one is a 10-unit discrepancy by month three.
None of these are auditor red flags on their own. All of them become red flags when the physical inventory doesn't match METRC on inspection day.
Before you fix anything, write down exactly what happens between a product receiving a METRC package tag and that product being available for sale. Include every person who touches it, every system it passes through, and every point where someone writes something down by hand.
The manual handoffs are where errors live. You're looking for every step that requires a human to transcribe a number from one place to another.
Most dispensaries find three or four of these. Some find eight.
Go through your workflow map. For each manual handoff, assign it to one of these categories.
Transcription risk: a human copies a number from a scale, a sheet, or a screen into METRC. The number can change in transit.
Timing risk: the physical action and the METRC entry happen at different times. An audit or count that happens in the window between them will find a discrepancy.
Yield risk: a process produces variable output like packaging, trimming, or splitting. The planned yield and actual yield diverge, and nobody logs the difference.
Transcription risk is the one that weight-based verification eliminates most directly. When the scale communicates directly with METRC, there's no human in the transcription step. The number doesn't change.

A count day is a snapshot. It tells you what you had at 7am on a Tuesday. By 7:05am, the count is already wrong.
Continuous weight monitoring is different. It tells you what you have right now. It updates when product moves. It flags when a container's weight doesn't match the expected unit count for the SKU inside it.
Setting this up requires three things.
A scale under each container or storage location you want to monitor continuously. The Ohaus Ranger 3000 is the most common choice for dispensary shelving: NTEP-certified, legal-for-trade, accurate to 0.1g.
A Cloudbox Station connected to that scale, with each container's SKU and unit weight configured. Once a SKU's unit weight is loaded, the system converts grams to units automatically.
A METRC integration that writes updates to your license immediately when the weight changes.
Once this is in place, your reconciliation becomes an exception report. You're not counting everything. You're reviewing the containers where the weight doesn't match what METRC expects.
Once continuous weight monitoring is running, your reconciliation cadence changes. Instead of a full count every quarter, you run three checks.
Daily: review the exception report. Flag any container where the current weight is outside the expected range for its recorded METRC quantity. Investigate the same day.
Weekly: audit the exception log for the past seven days. Look for patterns. If the same SKU keeps flagging, there's a yield or unit-weight calibration problem, not an inventory problem.
Quarterly: a spot count of your top 20 SKUs by value. This still happens. It takes two hours, not eight, because you're verifying, not discovering.
The distinction matters for compliance. An operator who can show a continuous audit trail of daily exception reviews is in a different position with a state regulator than one who can show a quarterly count sheet.
Calibrating unit weights once and never updating them. SKU weights drift. Vendor packaging changes. A product that weighed 3.6g per unit in January may be 3.7g in June. Recalibrate unit weights on each new lot receipt.
Treating METRC as the source of truth instead of the record of truth. METRC records what happened. Weight is what's happening now. Your verification system is the source of truth. METRC is where you report that truth to regulators.
Counting containers that don't need counting. Not every SKU carries the same risk. Concentrate containers have higher value per gram and need continuous monitoring. Focus your verification resources where the compliance exposure is.
Running METRC entries on a lag. If your weight system triggers a METRC update, run it immediately. Batch entries at end of day re-create the timing risk we identified in Step 2.
Even with continuous verification, you'll get exceptions you can't immediately explain.
First, re-weigh the container on a second scale. Confirm the weight is accurate before you start investigating the discrepancy. Scale calibration errors look identical to inventory discrepancies until you catch them.
Second, pull the audit log for that SKU and container. When did the weight last match? What happened between then and now?
Third, document what you find before you correct the METRC record. The documentation is what you hand a regulator if this becomes a violation report. "We identified a discrepancy, traced it to a packaging yield variance on [date], and corrected the record on [date]" is a story. An unexplained correction is a red flag.
The operators who come through inspections cleanly aren't the ones with zero discrepancies. They're the ones with clear records of how they found and fixed every discrepancy they had.
Setting up continuous weight monitoring for a dispensary's main storage area typically runs three to five days. The first day is hardware placement and scale calibration. The second and third days are SKU configuration: entering unit weights for each product and running test weighs to confirm accuracy. Days four and five are a parallel run where the weight system and the manual count run simultaneously, so you can confirm they agree before you stop doing the manual count.
After that, your count day is optional. Most operators run a quarterly spot check to validate the system, not to generate a count from scratch. The spot check takes two hours.
Learn more about how Cloudbox integrates with METRC for cannabis retail operations at cloudboxapp.com/cannabis, review compliance documentation at cloudboxapp.com/compliance, or contact the team at cloudboxapp.com/contact-us to discuss your specific reconciliation setup.
With continuous weight-based monitoring, reconciliation becomes a daily exception review rather than a periodic count. You review flagged containers daily (5-15 minutes), investigate exceptions weekly, and run a spot count of high-value SKUs quarterly. The goal is to catch discrepancies the same day they occur, not weeks later.
The four main causes are packaging yield variance (actual units differ from expected), transfer entry lag (product moved before METRC was updated), manual transcription errors (weight copied incorrectly from scale to system), and batch rounding (unit weights that vary slightly and compound over time). All four are addressable with a continuous weight-based verification layer.
If the physical weight and METRC record cannot be reconciled after pulling the audit log and tracing the discrepancy, document your investigation findings before correcting the METRC record. The documentation (what you found, when, what caused it, how you corrected it) is the record you present to a regulator if the discrepancy comes up in a future inspection.
Yes. The Cloudbox Station integrates with METRC through the state compliance API. When a container weight changes, Cloudbox converts the weight to units using the stored per-unit weight for that SKU and writes the update to your METRC license in real time. No manual entry required.
A standard dispensary setup runs three to five days: day one for hardware placement and scale calibration, days two and three for SKU configuration (entering unit weights and running test weighs), and days four and five for a parallel run where the new system and the manual count run simultaneously. Most operators stop the manual count after the parallel run confirms agreement.