One of the most valuable lessons I learned working with METRC came during my first large-scale commercial cultivation project.

At the time, we were operating a four-acre mixed-light cultivation facility built on a former mill site. Because of the regulatory structure in California at the time, the cultivation operation was divided among 24 separate mixed-light cultivation licenses, each managing its own designated canopy area.

The facility utilized light deprivation techniques throughout the cultivation cycle, which meant we required significantly more plants than a traditional full-term outdoor operation. By forcing plants into flower earlier, we could complete multiple production cycles each year, but this also meant that plants remained smaller and required much larger clone production volumes.

As a result, our nursery systems needed to reliably produce well over 100,000 clones annually to support multiple production cycles across the entire facility.

Fortunately, we had already solved the production side of the problem using our container-based nursery systems.

The next challenge was tracking all of those plants in METRC.

Scaling Up Introduces New Problems

Like many operators trying to improve efficiency, I decided to automate as much of the data entry process as possible.

We had clone packages containing hundreds, and sometimes thousands, of clones.

Rather than manually entering every transfer and planting event, I built a spreadsheet designed to generate CSV files for bulk import into METRC.

On paper, everything looked perfect.

The spreadsheet appeared correct.

The imports completed successfully.

The newly created plant records looked exactly as they should.

Then I checked the source clone packages.

The Moment of Panic

Instead of showing the expected inventory counts, many of the source clone packages showed:

  • negative 8,000 clones,
  • negative 10,000 clones,
  • and other impossible inventory quantities.

Naturally, I panicked.

“When you’re managing tens of thousands of regulated plants across dozens of licensed cultivation areas and your inventory suddenly shows massive negative values, your first reaction isn’t, ‘I’ll fix this.’ Your first reaction is usually, ‘How badly did I just break everything?'”

“I’ll fix this.”

Your first thought is usually:

“How badly did I just break everything?”

One of METRC’s Biggest Challenges

One of the most important lessons I learned that day was this:

METRC has very few guardrails.

Creating a package with a negative inventory quantity should never happen.

It’s an invalid inventory state.

Yet METRC allowed it.

This isn’t necessarily a criticism of the system. It’s simply an operational reality that every compliance manager eventually learns:

METRC assumes that the user knows what they’re doing.

Because of that, operators must verify:

  • spreadsheets,
  • formulas,
  • imports,
  • package quantities,
  • and inventory movements extremely carefully.

Automation can save enormous amounts of time.

It can also create enormous problems very quickly.

Calling METRC Was the Right Decision

At that point, I did what many people are initially hesitant to do:

I called METRC.

Many operators mistakenly believe that contacting METRC is equivalent to reporting themselves to a regulatory agency.

In reality, METRC is a software company.

When you call support, you’re speaking with customer service representatives whose job is to help operators navigate problems with the system.

The support staff documented the issue, attached reference information to the affected records, and provided guidance on the proper corrective actions.

Most importantly, I had documentation showing that:

  • the error had been identified,
  • the issue had been reported,
  • and corrective action had been taken.

Mistakes Happen

One of the most valuable lessons I learned from this experience was that mistakes happen.

Especially when operators begin managing cultivation at larger scales.

The important part isn’t avoiding every mistake.

The important part is:

  • recognizing the mistake quickly,
  • documenting the issue,
  • communicating with the appropriate people,
  • and implementing corrective actions.

In our case, the issue never became a problem during state or county inspections.

But the experience permanently changed the way I approach METRC management.

Automation Requires Verification

Today, whenever I build spreadsheets, import templates, or automated workflows, I assume one thing:

Every automated process should be verified before it is trusted.

This means checking:

  • package quantities,
  • source inventories,
  • destination inventories,
  • transfer counts,
  • and final outputs.

The time spent verifying data is always less expensive than correcting bad data.

Don’t Panic

One of the biggest mistakes operators make when something goes wrong in METRC is panicking.

Most problems can be corrected.

Most mistakes can be documented.

Most situations can be resolved.

The important thing is to approach the problem the same way you would approach any operational issue:

  • stay calm,
  • document everything,
  • contact the appropriate people,
  • ask questions,
  • and work through the solution.

Because in commercial cannabis operations, mistakes are inevitable.

Learning how to recover from them is what separates experienced operators from everyone else.

James Cook
Cannabis Compliance, METRC & Operations Consulting