In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

Submit a Testing Sample in Metrc (New York)

TL;DR

• New York operators must choose the correct item category when creating Metrc testing samples to avoid downstream compliance issues.

• Split bulk packages before sampling if one lot will become multiple final form SKUs to keep testing aligned.

• Duplicate testing samples can lock packages in "Testing in Progress" status until all duplicates are discontinued in Metrc.

This article summarizes Metrc (New York) Support Bulletin NY_IB_0006, which provides step-by-step direction for creating cannabis testing sample packages in Metrc and transferring those samples to a licensed testing facility. It covers two common workflows (bulk item category that is physically in final form, and final form “-each” items) plus the required transfer steps and key operational implications for keeping testing status, inventory, and compliance accurate.

Bulletin scope and why it matters for New York operators

New York cannabis operators using Metrc must create testing sample packages correctly so lab results can be reported against the appropriate product type and test batch, and so the source inventory and compliance status remain accurate.

Bulletin reference: NY_IB_0006 (Metrc Support Bulletin), distributed 1/14/2025, effective ongoing.

Who this affects: Any New York licensee creating lab samples in Metrc (including scenarios described as electronic sampling for distributors during beginning inventory).

Core compliance point: The Metrc “Submit for Testing” action creates a distinct testing sample package and places the source package into a testing workflow; mistakes (like duplicate samples or wrong item selection) can cause testing status and downstream packaging/retail compliance issues.

Workflow 1: Create a testing sample from a bulk item category that is physically in final form

This workflow is used when the product is still represented in Metrc as a bulk item category, but the physical product is already “ready-to-consume” final product form and only needs final packaging after testing.

Start from the source package in Metrc

In Metrc, navigate to the Packages area and open the Active tab.

Select the bulk source package you intend to test, then choose Submit for Testing.

Complete the “Submit for Testing” details

In the submission window, enter the required fields, including the new testing sample Package UID and the location where the physical sample will be stored in your facility.

Item selection (critical): For the Item field, select the Final Form – Each product category that the tested product will be packaged into after results are returned. This ties the sample to the correct final form compliance pathway.

If you need help locating the right item, use the item search (magnifying glass) and choose from your item list.

If one bulk lot will become multiple final form “-each” SKUs

If a single bulk source package will be packaged into multiple different final form items (for example, 1g each, 3.5g each, and 7g each), you must repackage/split the bulk inventory into separate packages allocated to each final form item before creating test samples from those packages.

This matters operationally because New York operators often align a specific test result and lab test batch with a particular final form product pathway; splitting first helps keep items, results, and future packaging actions consistent and defensible in Metrc.

Adjust quantities from source to sample

Use the quantity adjustment panel to deduct the required sample amount from the source package and add it into the newly created testing sample package.

Select the correct final form lab test batch

Select the appropriate final form lab test batch required for the product type you are submitting (the bulletin’s example references a final form raw plant material batch). Then complete the action by submitting for testing.

How to visually confirm the sample package: Metrc displays a testing sample package with a graduated cylinder icon, allowing staff to quickly identify which packages are samples versus sellable or production inventory.

Workflow 2: Create a testing sample for Final Form “-each” item categories

This workflow is used when the source package is already in a final form “-each” item category in Metrc (the bulletin also notes use for electronic sampling by distributors during beginning inventory).

Submit the “-each” package for testing

In Metrc, go to Packages > Active, select the final form (-each) source package, and choose Submit for Testing.

Use “Same Item” for item selection

In the submission window, enter the new testing sample Package UID and the sample location in your facility.

For the Item field, select the Same Item option so the testing sample remains tied to the same final form item as the source package.

Deduct the sample quantity and choose the test batch

Deduct the required amount from the source package and add it to the newly created testing sample package.

Select the correct final form lab test batch for the product category (the bulletin example references an infused preroll batch), then submit to finalize the sample creation.

How to confirm you created a sample: The testing sample package is marked with the graduated cylinder icon.

Testing status management: avoiding “TestingInProgress” issues

Metrc’s testing workflow can remain in a “TestingInProgress” status until all required test results are recorded for the package(s) associated with the submission.

Practical implication: If you accidentally create duplicate testing samples, your package status may not resolve as expected when the lab reports results. The bulletin advises discontinuing the duplicate testing sample so the testing status can display correctly once results are fully reported by the testing facility.

Day-to-day operations impact: Unresolved testing statuses can delay packaging, transfers, and retail fulfillment because many SOPs require a “passed” status before product can move to the next compliant step.

Creating a transfer for the testing sample to the lab

After the testing sample package is created, you must transfer the sample to a licensed testing facility for analysis.

Initiate the transfer from the sample package

In Metrc, go to Packages > Active, select the testing sample package (identified by the graduated cylinder icon), and choose New Transfer.

Enter required transfer details

In the transfer window, complete the fields required for a compliant shipment, including destination testing facility, planned route, transporter license number, transporter phone number, driver details, and vehicle details.

Transfer type: Select Transfer to Testing Facility. The selected sample package should already be populated in the transfer’s package section.

Register the transfer to generate the outgoing transfer record.

Where to confirm the registered transfer

To view the registered transfer, navigate to Transfers and open the Outgoing tab, where the newly created transfer will appear in the outgoing transfers grid.

Operational takeaways for New York Metrc compliance

Correct item mapping prevents downstream errors: Choosing the correct final form item (or “Same Item” for -each) helps ensure test results align to the intended product category, which supports compliant packaging, labeling, and inventory actions after results.

Split bulk before sampling when multiple SKUs are planned: If one bulk lot will feed multiple final form SKUs, splitting into separate packages first reduces reconciliation risk and helps keep testing documentation aligned to the product pathway you will actually sell.

Sample identification supports floor execution: Training staff to recognize the testing sample icon reduces accidental use of sample packages in production or shipping workflows.

Duplicate samples can block status resolution: Discontinuing mistakenly created duplicate samples helps avoid “stuck” testing statuses that can halt operations.

Metrc training and support resources referenced in the bulletin

Metrc Learn: The bulletin points operators to beginning inventory training content in Metrc Learn for additional guidance on submitting test samples.

Metrc Expert widget: The bulletin notes that Testing Tips and Best Practices are available inside Metrc through the Metrc Expert widget.

Metrc Support: For help, use the support portal at https://support.metrc.com/ (also accessible from within Metrc via the Support dropdown). The bulletin notes first-time portal access requires facility/state information and an email to set a password.

How labeling tools support Metrc testing-to-retail workflows

Once testing is complete and you move toward final packaging and retail readiness, labeling becomes a practical compliance bottleneck—especially when teams need to stay aligned with Metrc package details and Retail ID requirements.

DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, helping teams generate labels that support Metrc Retail ID compliance and reduce rework when packages move from testing status to sellable inventory.

DistruERP: For larger operations that need end-to-end visibility beyond sampling and transfers, DistruERP is Distru’s comprehensive Cannabis ERP platform designed to support complete supply chain management across inventory, orders, fulfillment, and compliance workflows.

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.