In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

NJ Metrc Stability Studies in Metrc

TL;DR

• New Jersey requires stability testing at T1 (6 months) and T3 (12 months) after initial full panel compliance testing.

• Create one dedicated Stability Study package in Metrc with enough product reserved for all planned timepoint samples.

• T0 and T2 are information only and don't update compliance status, but T1 and T3 are required submissions.

This article explains Metrc (New Jersey) Support Bulletin NJ_IB_0061 on Stability Studies, including what stability timepoints mean, which tests are required, and how New Jersey operators should create stability study packages and test samples in Metrc for ongoing compliance.

Bulletin overview (NJ_IB_0061)

Bulletin number: NJ_IB_0061

Distribution date: 08/05/2026

Effective date: Ongoing

Subject: Stability Studies

Published by: Metrc Support, in conjunction with the New Jersey Cannabis Regulatory Commission (NJ-CRC)

What “stability studies” mean in New Jersey Metrc

Stability Studies are scheduled lab tests performed at defined intervals to evaluate how a product’s potency and contaminant profile change over time. The purpose is to validate that a batch remains safe, consistent, and effective throughout its intended shelf life.

Per the bulletin, Stability Study data must be recorded in Metrc. Operationally, that means licensees should plan inventory and testing workflows so stability samples can be pulled and submitted at the correct timepoints without disrupting production, fulfillment, or retail supply.

Key compliance rule: full panel testing first

Before starting any Stability Study timepoints, the product must pass the appropriate initial full panel compliance testing for its item category. This initial compliance test establishes the benchmark that later stability results will be compared against.

Example from the bulletin: For a Vape Cart item category, the product should first be tested using the Inhalable/Vape Concentrate full panel lab test batch. Only after that initial compliance test should later stability timepoints be submitted using the relevant Stability Study lab test batch.

Stability Study timepoints and what they do in Metrc

Metrc records stability testing at standardized timepoints. Each timepoint corresponds to a stability interval and is submitted as a specific Stability Study test selection in Metrc.

T0: 3-month stability check (information only; not a regulatory requirement)

T1: 6-month stability check (required)

T2: 9-month stability check (information only; not a regulatory requirement)

T3: 12-month stability check (required)

In day-to-day operations, the practical takeaway is that T1 and T3 drive required stability compliance activity, while T0 and T2 can be used for internal quality monitoring without updating the source package’s lab test status as required tests do.

How stability studies work in Metrc: the two-package approach

The bulletin’s workflow is built around creating one dedicated Stability Study package (a “source” set-aside package) and then pulling individual test samples from that package at each timepoint. This reduces the chance of pulling from the wrong inventory later and makes it easier to manage planned sampling across a 12-month period.

Create a Stability Study package in Metrc (set aside enough for 12 months)

The Stability Study package should contain the total quantity needed for all planned stability samples (T0, T1, T2, and T3) over the next year.

Step 1: In Metrc, go to Packages and open the Active tab.

Step 2: Locate and select the source batch package with enough quantity to cover all stability samples planned over the next 12 months.

Step 3: Select New Packages.

Step 4: Complete the required fields in the New Packages window.

Same Item setting: Select Same Item to indicate the Stability Study package uses the same item as the source package.

Step 5: Select Create Packages to generate the Stability Study package that will be used as the long-term sampling source.

Operational implication: once created, treat this package as reserved stability inventory. Doing so prevents accidental depletion, simplifies audits, and keeps sampling consistent across timepoints.

Create a Stability Study test sample in Metrc (submit at each timepoint)

At each scheduled timepoint (or when required), you will submit a sample for stability testing from the Stability Study source package.

Step 1: In Metrc, go to Packages and open the Active tab.

Step 2: Find and select the Stability Study source package, then choose Submit for Testing.

Step 3: Complete all required fields in the Submit for Testing window.

Same Item setting: Select Same Item to ensure the test sample uses the same item as the source package.

Choose the correct Stability Study test: Select the appropriate Stability Study timepoint (typically T1 or T3 for required submissions).

Metrc status note: T0 and T2 are designated as Information Only and do not update the lab test status of the source package; T1 and T3 are the required Stability Studies.

Step 4: Select Submit for Testing to create the test sample package to be transferred to the testing facility.

Day-to-day operational impacts for NJ licensees

Inventory planning: Set aside enough product in the Stability Study package to avoid shortages at T1 and T3. If the reserved package is accidentally sold, remediated, or otherwise altered, it can disrupt the stability schedule and complicate documentation.

Item and test alignment: Use the correct test type for the item category on the initial full panel, then use the corresponding Stability Study test selections for timepoints. Misalignment (wrong test selection) can create compliance risk and rework.

Audit readiness: Because the bulletin emphasizes that Stability Study data must be recorded in Metrc, maintaining a clean package lineage (source stability package → submitted test sample packages) supports defensible records during NJ-CRC or internal audits.

Quality and shelf-life decisions: Even when not required, information-only timepoints (T0, T2) can provide valuable trend data to support internal shelf-life validation, packaging decisions, and customer complaint investigations.

Labeling and traceability considerations (including Metrc Retail ID)

Stability study workflows increase the number of packages and test samples a team must label and track accurately. To reduce label errors and improve consistency, DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams stay aligned with Metrc Retail ID compliance where applicable to downstream labeling workflows.

For larger New Jersey operations that need deeper inventory controls across cultivation, manufacturing, distribution, and retail workflows, DistruERP is Distru’s comprehensive Cannabis ERP platform designed to support end-to-end supply chain management alongside compliance processes.

Metrc support resources referenced in the bulletin

Metrc Support Portal: https://support.metrc.com

Metrc Support phone: 877-566-6506

Support hours (ET): Monday–Friday 8 a.m.–10 p.m.; Saturday 10 a.m.–8 p.m.; Sunday voicemail or portal only

Metrc Learn: Available via the Support drop-down in Metrc for on-demand training content

Metrc Expert: Accessible in-system via the help/widget icon for knowledge base articles and guided help

Metrc state resources: Visit https://www.metrc.com and navigate to your state 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.