In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

Rhode Island Metrc Package Pre-Treatment

Rhode Island
April 1, 2026
Link to Metrc Bulletin
TL;DR

• Rhode Island Metrc adds a Package Pre-Treatment workflow to document product handling before lab testing starting April 1, 2026.

• Only packages with NotSubmitted lab status qualify, so teams must record pre-treatment before submitting samples for testing.

• Pre-treatment data appears in Package History, grid columns, and persistent icons to support audits and compliance reviews.

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.

The AI cannabis library

Free skills to put AI to work on your inventory, compliance and costing, and guides on where it actually saves time.

SKILL
Inventory Management

Distru Expiring Inventory

See stock about to expire, who already buys it, and a promo email draft to review.

SKILL
Compliance

Cannabis Inspection Readiness

Turn an upcoming state inspection into a checklist, binder index and gap list.

SKILL
Compliance

Cannabis Transfer Manifest Precheck

Check a B2B transfer before the driver leaves and get GO or HOLD per line.

SKILL
Purchasing

Cannabis Replenishment Planner

Turn sales and on-hand exports into a reorder plan and a draft PO by vendor.

SKILL
Compliance

Cannabis State Rules Lookup

Get a cited, dated answer to a state cannabis rule question.

SKILL
Operations

Cannabis Staff Scheduling Planner

Build a shift schedule that matches demand and stays inside your labor budget.

SKILL
Cultivation

Cannabis Harvest Yield Analysis

See which rooms and strains actually make money, from your own harvest data.

SKILL
Compliance

Cannabis Traceability Reconciliation

Find out why your physical count doesn't match Metrc or BioTrack.

SKILL
Compliance

Cannabis SOP Generator and Trainer

Turn process notes into an inspection-ready SOP and a staff training packet.

SKILL
Finance and COGS

Cannabis Batch COGS Calculator

Find out what a batch really costs per finished unit, line by line.

AI GUIDE
Blog

Why the Harness Matters More Than the AI Model

Two products can use the exact same AI model and perform completely differently. Here's why the harness, not the model, usually explains why.

AI GUIDE
Blog

What Is an Agent Harness? A Plain-English Primer

An AI model alone can't do much. The 'harness' around it is what makes it useful. Here's what that actually means, no jargon required.

AI GUIDE
Blog

Why MSOs Need an AI Strategy Before More Software

Adding another point solution won't fix an MSO's AI readiness problem. Here's why the data foundation has to come first.

AI GUIDE
Blog

The Supply Chain Buyer's Guide to AI Agents and MCP

Evaluating AI agent features in supply chain software? Here's a practical buyer's checklist, including what MCP means for your evaluation.

AI GUIDE
Blog

AI in Supply Chain: What's Hype, What's Working

AI in supply chain gets a lot of hype. Here's an honest look at what's actually delivering results in 2026, and what still needs a person.

AI GUIDE
Blog

Where AI Agents Fit in Cannabis Compliance

Not every step of your compliance workflow is a fit for AI. Here's a clear map of where it helps, and where it should stay hands-off.

AI GUIDE
Blog

The Skills Ops Teams Will Need When AI Agents Arrive

AI agents are coming for repetitive ops tasks in cannabis. Here's what your team needs to get good at instead, starting now.

AI GUIDE
Blog

What Happens When AI Gets Access to Your ERP

Giving an AI tool access to your cannabis ERP isn't all-or-nothing. Here's what real, scoped access looks like, and what to watch for.

AI GUIDE
Blog

AI and 280E: Where Automation Actually Saves Money

280E just got more complicated for mixed medical and adult-use operators. Here's where automated cost tracking actually helps, and its limits.

AI GUIDE
Blog

Can AI Forecast Wholesale Demand Better Than Excel?

Your wholesale forecast spreadsheet has limits. Here's what AI-assisted forecasting can actually add, and where a spreadsheet still wins.

AI GUIDE
Blog

Should Your Cannabis Business Have an AI Strategy?

You don't need to be an AI company to have an AI strategy. Here's a practical starting point for cannabis operators, no hype required.

AI GUIDE
Blog

What Is Claude Cowork? Could It Kill Data Entry?

Claude Cowork lets AI work directly in your files and tools. Here's what that means for the data entry eating your cannabis team's week.