Metrc (Minnesota) Bulletin MN_IB_0070 (distributed 08/04/2026; effective 09/01/2026) introduces a new Package Pre-Treatment workflow that lets cannabis licensees record when and how product is pre-treated before laboratory testing, improving transparency in package history, grids, and API data.
What the new Metrc Package Pre-Treatment workflow does
This update adds a structured, auditable way to document pre-testing handling activities at the package level. Once recorded, the pre-treatment details persist with the package through its lifecycle, including package history, grid indicators, and relevant API endpoints, helping downstream compliance and reporting reflect how product was handled prior to testing.
Where you will see the new Pre-Treat action in Metrc
Within Metrc, eligible users will see a new Pre-Treat action available from the Active Packages area for qualifying packages. Using this action is how a licensee records pre-treatment details in a standardized format rather than relying on external notes or informal documentation.
What information is captured when you pre-treat a package
When the Pre-Treat action is used, Metrc prompts the user to record key fields that become part of the package record.
• Package selection (which package(s) the action applies to)
Method: The pre-treatment method used before testing.
Reason: Why the package was pre-treated.
Pre-Treatment Date: The date the pre-treatment occurred.
Required Pre-Treatment Steps: The specific steps completed as part of the pre-treatment process.
Eligibility rules in Minnesota (what can and cannot be pre-treated)
Metrc limits when the Pre-Treat action appears to ensure it is used only in approved scenarios.
Regulator enablement: The Pre-Treat button is visible only for facilities where pre-treatment is enabled by the regulating agency.
Item Category controls: Pre-treatment is available only for Items assigned to an Item Category where pre-treatment is enabled by the regulating agency.
Lab test status requirement: Only packages with a lab test status of NotSubmitted may be pre-treated.
How pre-treatment shows up in Package History and grids
Once recorded, the pre-treatment event becomes part of the package’s audit trail and is easier to identify across everyday workflows.
Package History recording: Metrc records the pre-treatment Method, Reason, and Steps in Package History for auditing and traceability.
Packages grid indicator: A “Contains Pre-Treated” (Yes/No) column is available in the Packages grid to help operators filter and identify impacted inventory quickly.
Persistent icon: A pre-treatment icon appears next to pre-treated packages throughout Metrc and remains with the package across its lifecycle. The hover text reads “Package contains Pre-Treated Product.”
Practical implications for day-to-day cannabis operations
This workflow changes how teams should document pre-testing handling so that internal practices align with what regulators and labs may review in Metrc.
Inventory and QA workflows: If your operation performs any approved pre-testing preparation, staff should record it at the time it occurs so QA and compliance can validate the package’s handling history before scheduling or submitting lab work.
Testing coordination: Because only NotSubmitted packages are eligible, teams should confirm pre-treatment is recorded before initiating the lab submission process in Metrc to avoid rework and delays.
Audit readiness: With Method, Reason, and Steps stored in Package History, your documentation is centralized and easier to produce during inspections, investigations, or internal audits.
System integrations: Since pre-treatment persists across Metrc history, grids, and API endpoints, integrators and data teams should review any internal dashboards, reports, or middleware mappings that rely on package attributes to ensure pre-treated inventory is correctly flagged and handled in downstream systems.
Labeling and Retail ID: how Distru can help
While the bulletin focuses on pre-testing handling, operators should also keep packaging and Retail ID labeling aligned with state rules and Metrc expectations as product moves from testing to sale.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels and can help teams produce labels that support Metrc Retail ID compliance in day-to-day packaging and fulfillment workflows.
DistruERP: For larger operators, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for end-to-end supply chain management, helping coordinate inventory, compliance processes, and operational execution across multiple departments and facilities.
Metrc support resources referenced in the bulletin
Metrc Support: Submit and track cases through the Metrc Support portal or call 877-566-6506.
Support hours: Monday–Friday 8 a.m. ET–10 p.m. ET; Saturday 10 a.m.–8 p.m. ET; Sunday voicemail or portal only.
Portal access note: First-time portal access requires a username (created when logging in), the respective state, the facility license number, and a valid email to set a password.
Metrc Learn: Metrc’s on-demand training platform is available via Metrc (Support drop-down) and may also be accessed online at metrc.com depending on your state’s training links.
Metrc Expert: Use the in-system widget (lower right corner) to open the Metrc Expert knowledge base for guided articles and step-by-step help.
Metrc.com state resources: Visit Metrc.com and navigate to your state partner page for state-specific training links and resources.
