Skip to content

Metrc

Overview

Metrc (Marijuana Enforcement Tracking Reporting Compliance) is a state-mandated cannabis compliance system, required in various U.S. states to track cannabis cultivation, production, testing, and sales. Developed by Franwell, Metrc operates as a cloud-based platform intended to monitor cannabis products throughout the supply chain.

Which states use Metrc?

Metrc Key Components

Metrc’s compliance ecosystem is built around several key components, each serving a unique role in ensuring cannabis industry compliance with state regulations:

Web UI

The Metrc platform's primary tool is its web-based user interface (Web UI). In states that have adopted Metrc as their compliance tracking system, all licensed cannabis businesses are required to use this interface to report essential compliance data. Key reportable events include:

  • Cultivation Activities: Planting, harvesting, and waste disposal.
  • Manufacturing: Processing raw cannabis into consumable products.
  • Transportation: Tracking the movement of products between licensed facilities.
  • Testing: Documenting results from state-mandated lab testing.
  • Sales: Recording transactions at dispensaries.

Despite the availability of an API, many compliance actions must still be completed through the Web UI due to gaps in API coverage.

Metrc API

Metrc provides an API designed to enable licensed operators and third-party integrators to programmatically interact with its system.

There are two versions of the API:

  • v1 (Free): Available at no cost, this version provides basic functionality for interacting with Metrc’s compliance system.
  • v2 ("Metrc Connect", Paid): A premium version with some additional features, requiring payment for access.

RFID Tags

Radio-frequency identification (RFID) tags are mandatory for tracking every plant and product within the Metrc system. These tags play a critical role in enabling accurate seed-to-sale tracking. States differ in how these tags are funded:

  • In some states, the government covers the cost of RFID tags.
  • In others, the expense is borne by the businesses themselves.

State Agency Interface

Metrc also provides tools for state agencies to monitor and audit cannabis license holders. This lesser-known component of Metrc's platform grants state regulators full visibility into the activity of licensed businesses, enabling enforcement of compliance standards. Features available to state agencies include:

  • Audit Tools: For detailed reviews of licensee data and activity.
  • System-Wide Monitoring: Allowing oversight of all cannabis operations within the state.

These tools form an integral part of Metrc's value proposition to state governments, enhancing transparency and accountability across the regulated market.

Criticisms of the Metrc API

The Metrc API is often criticized for its limitations and challenges.

  1. Dual API Key Requirement The Metrc API operates in an unusual manner by requiring two API keys to function:

    • One API key is issued to the cannabis business itself.

    • The other API key is issued to an approved Metrc integrator.

      Becoming an approved integrator involves navigating a state-specific approval process, as each U.S. state mandates its own procedures. This effectively means:

    • Cannabis businesses cannot directly access their own data through the API unless they work with a state-approved integrator.

    • The added dependency on integrators creates barriers for businesses seeking full control of their data.

  2. Incomplete Compliance Support Neither version of the Metrc API fully supports all required compliance actions. As a result:

    • Cannabis businesses must frequently rely on Metrc’s web-based user interface (Web UI) alongside the API.
    • This dual dependency increases operational inefficiencies and complexity.

  3. Cost of Access

    • Access to the Metrc API v2 is not free. Businesses are charged for using it, effectively imposing a fee for accessing their own compliance data.
    • This pricing structure adds to the financial burden of regulatory compliance.

  4. Performance Issues The Metrc API suffers from significant technical shortcomings:

    • Slow Response Times: The API often performs poorly under load, leading to delays.
    • Lack of Usability: Developers frequently report the API as difficult to use due to its unintuitive design.
    • Poor Documentation: Incomplete or unclear documentation makes implementation and troubleshooting unnecessarily challenging.
    • Unhelpful Error Handling: The API returns generic or unclear error codes, complicating error resolution for developers and users.

State-Specific Metrc Implementations

Each state implements Metrc differently, based on specific regulations and requirements mandated by its regulatory bodies. This means Metrc operates as a slightly different system in each state, adding another layer of complexity for operators who must adapt to the unique requirements where they operate. For multi-state operators, these differences create significant operational challenges, as compliance processes may vary dramatically across state lines.

Next Steps