This article explains Metrc (Rhode Island) bulletin RI_IB_0051, which introduces a new Package Pre-Treatment workflow effective 04/01/2026. You’ll learn what “pre-treating” a package means inside Metrc, when the new action is available, what data gets recorded for compliance visibility, and how this changes day-to-day lab testing and package management operations.
What the Metrc Package Pre-Treatment workflow does
Metrc’s new Package Pre-Treatment workflow creates a structured, auditable way to record product handling activities that occur before a package is submitted for laboratory testing. The key compliance value is that pre-treatment information is captured at the package level and remains visible throughout the package lifecycle, improving transparency for internal QA, regulators, and downstream users who rely on accurate package history.
Bulletin number: RI_IB_0051
Distribution date: 02/25/2026
Effective date: 04/01/2026
Subject: Package Pre-Treatment workflow
Stated reason: Introduce a workflow that allows licensees to record and distinguish product pre-treatment activities.
Where operators will find the new Pre-Treat action
For eligible packages, Metrc adds a new Pre-Treat action on the Active Packages area. Selecting the action opens a dedicated window that guides users through recording pre-treatment details in a consistent format.
What you record during Pre-Treat: Package selection, method, reason, pre-treatment date, and required pre-treatment steps.
Eligibility rules: when Pre-Treat appears and when it will not
The Pre-Treat action is intentionally limited to prevent misuse and to ensure the recorded event aligns with regulated testing workflows.
Agency enablement required: The Pre-Treat button is visible only for facilities where Pre-Treatment has been enabled by the regulating agency.
Item category must allow it: Pre-Treatment is available only for items assigned to an item category where Pre-Treatment is enabled by the regulating agency.
Lab test status limitation: Only packages with a NotSubmitted lab test status can be pre-treated.
How pre-treatment is displayed in Metrc (history, grids, and icons)
Once recorded, pre-treatment data becomes part of the package’s audit trail and day-to-day visibility throughout Metrc.
Package History entries: Metrc records the pre-treatment method, reason, and steps in Package History so reviewers can see what was done, and when, as part of the package’s chronology.
Packages grid indicator: A new column, Contains Pre-Treated, displays Yes/No to quickly distinguish packages that have been pre-treated.
Persistent package icon: A pre-treatment icon appears next to pre-treated packages and persists through the package lifecycle, with hover text indicating the package contains pre-treated product.
API visibility: The bulletin notes that pre-treatment information persists across package history, grids, and API endpoints, which matters for integrators and for any business syncing Metrc data into internal systems.
Practical compliance impacts for Rhode Island operators
This change primarily affects how teams document steps taken before sending product to a lab, and it introduces new “truth data” that will follow the package indefinitely.
Improved defensibility during audits: When pre-treatment is recorded at the package level, your rationale and method are consistently attached to the package record, supporting internal investigations, regulator questions, and partner due diligence.
Timing matters: Because only NotSubmitted packages can be pre-treated, teams should align SOPs so pre-treatment documentation occurs before any lab submission workflow changes the package’s lab test status.
Operational visibility across departments: Cultivation, manufacturing, QA, and compliance teams can use the grid column and persistent icon to avoid confusion about whether a package has undergone pre-test handling, helping prevent duplicate handling steps or inconsistent documentation.
Data consistency for integrated systems: Since the data is available via the API, operations using third-party software should confirm their integration properly ingests and displays pre-treatment fields so internal records match Metrc.
Labeling and operational systems: where Distru fits
While this bulletin is focused on package-level pre-treatment documentation, day-to-day compliance often depends on having reliable labeling and inventory workflows that stay aligned with Metrc changes.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help operators support Metrc Retail ID compliance by producing labels designed for regulated retail and package identification needs.
DistruERP: For larger operators that need end-to-end supply chain management, DistruERP is Distru’s comprehensive Cannabis ERP platform designed to manage inventory, orders, fulfillment, and operational workflows alongside Metrc tracking requirements.
Metrc resources referenced in the bulletin
Metrc Support: Submit and track a case through the 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 (established when logging in), the respective state, facility license number, and a valid email to set a password.
Metrc Learn: On-demand training platform available directly or via the Support drop-down in Metrc after registration.
Metrc Expert: In-app knowledge base accessible from the widget icon in the lower right corner for step-by-step guidance.
Metrc state partner page: Visit https://www.metrc.com and navigate to your state’s partner page for state-specific training links and updates.
