In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

NY Metrc Package Remediation Guide

TL;DR

• New York licensees must record remediation per package in Metrc after a TestFailed status, including method and detailed steps.

• Once recorded, package status updates to Remediated and displays a visual indicator for inventory and compliance tracking.

• Remediation can be recorded via Metrc UI or API endpoint, requiring accurate method selection and clear documentation for audits.

This article summarizes Metrc (New York) bulletin NY_IB_0022 and explains how New York licensees should record product remediation in Metrc after a package receives a TestFailed lab testing status, including what fields to enter, what status changes to expect, and how the Metrc API supports remediation reporting.

Bulletin scope and why it matters in New York

Bulletin number: NY_IB_0022

Distribution date: 7/30/2026

Effective date: Ongoing

Metrc and the New York Office of Cannabis Management (OCM) issued this guidance to standardize how remediation attempts are documented in Metrc for products that fail testing. The key operational point is accountability: the licensee performing the actual remediation must record the remediation method and the specific remediation steps used in Metrc, and those details must be recorded for each individual Metrc package included in the remediation attempt.

What triggers remediation in Metrc

When a product fails lab testing, the Metrc Package UID is assigned a lab testing status of TestFailed. In some cases, OCM allows licensees to attempt remediation. This bulletin focuses on how to document that remediation attempt inside Metrc so the package history clearly reflects what was done and when.

How to record a remediation in the Metrc user interface

In Metrc, remediation is recorded from the Packages area. Navigate to the Packages module and work from the Active packages view so you can locate the package that currently shows the TestFailed lab testing status.

After you select the appropriate package (the package row will display as selected in the grid), choose the Remediate action to open the remediation entry window. Metrc requires you to document the remediation at the individual package level, so repeat this process for each package included in the remediation attempt.

Required remediation fields you must complete

Remediation method: Select the most accurate option from the drop-down list that matches the process actually performed.

Remediation date: Enter the date the remediation was completed.

Remediation steps: Describe the steps taken in plain language. This narrative should be specific enough that an auditor or regulator can understand what occurred without needing verbal clarification later.

Remediation methods available in Metrc (NY)

Metrc provides a defined set of remediation methods for New York packages. Choose the closest match to your actual process.

• Further Drying and Curing

• High Heat and Solvent Extraction

• Irradiation

• Non-Solvent Extraction

• Ozone

• Reformulation

• Repackaging and Remixing

Once the required fields are entered and verified for accuracy, submit the remediation action to record it to the package.

What changes after remediation is recorded

After you complete the remediation entry, the package lab testing status updates from TestFailed to Remediated. Metrc also displays a visual indicator next to the package label showing the package contains remediated product. Operationally, this is a visibility flag for anyone working inventory, transfers, or downstream manufacturing, signaling that the package has a remediation event in its history.

Day-to-day operational implications for licensees

Recording remediation correctly is not just a “system step”; it directly affects compliance posture and internal controls. Teams should expect remediation documentation to be reviewed during inspections, audits, investigations, or partner due diligence.

Inventory accountability: Because remediation must be recorded per package, remediation workflows should be built around package-level handling, not just batch-level notes.

Process integrity: Selecting an inaccurate remediation method or entering vague remediation steps can create regulatory exposure if the record does not match what was actually performed on-site.

Downstream communication: The remediated-product indicator helps prevent accidental commingling or misinterpretation by other staff, facilities, or trading partners who rely on Metrc status and package history to make compliance decisions.

Metrc API support for remediation (New York server)

Metrc also supports recording remediation via the Web API for New York.

Endpoint and server

Server: https://api-ny.metrc.com/

Endpoint: PUT /packages/v2/remediate

Purpose: Updates a list of product remediations for packages at a specific facility.

Permissions and required parameter

Permissions required: View Packages; Manage Packages Inventory

Parameter: licenseNumber (the facility license number for which you are updating package remediation records)

When using the API, ensure each object includes the correct package label and that the method name and remediation steps align with your SOPs and what was performed. As with the UI workflow, remediation records should be created per package included in the remediation attempt.

Labeling considerations: keeping Retail ID workflows clean

Remediation documentation is only one part of staying inspection-ready. Packaging and retail labeling frequently become the next operational bottleneck when teams are updating inventory status, preparing product for sale, or ensuring identifiers match Metrc records.

DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams maintain clean Metrc Retail ID workflows by standardizing how retail labels are produced and applied.

DistruERP: For larger, multi-team operations, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for end-to-end supply chain management, helping connect compliance inventory controls, production, sales, and labeling workflows in one system.

Where to get help

If you need assistance interpreting the bulletin requirements or troubleshooting remediation actions in Metrc, Metrc Support is available via the Support Portal and phone.

Metrc Support phone: 877-566-6506

API support: api-info@metrc.com

Metrc training and self-service documentation are also available through Metrc Learn and the in-app Metrc Expert knowledge base.

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.