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.
