In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

NY Metrc Expiration Dates Required May 2026

New York
May 15, 2026
Link to Metrc Bulletin
TL;DR

• Starting May 15, 2026, New York Metrc requires expiration dates for all final-form, count-based packages.

• Sell-by dates are no longer required in Metrc after the effective date.

• Update packaging SOPs and API integrations to include ExpirationDate before the May 15 deadline.

Metrc (New York) Support Bulletin NY_IB_0015 updates package-creation requirements: beginning May 15, 2026, operators must enter an expiration date for all final-form, count-based (Each) items in Metrc, and Metrc/OCM will no longer require a sell-by date. This article explains what changed, which products are impacted, how to comply in the Metrc UI and via the Metrc API, and what to update in day-to-day packaging and labeling workflows.

Bulletin summary: what changed in New York Metrc

Bulletin: Metrc Support Bulletin NY_IB_0015

Distribution date: May 5, 2026

Effective date: May 15, 2026

New requirement: Expiration date information is required in Metrc to create packages for all final-form, count-based items (Unit of Measure: Each).

Removed requirement: Sell By Date is no longer required in Metrc effective May 15, 2026.

Important context: Metrc previously showed expiration date as optional for these items; after the effective date, it becomes required for package creation to align with New York Office of Cannabis Management (OCM) requirements.

What items are impacted: “final form” and “count-based (Each)”

This change applies when you are packaging a final-form product where inventory is tracked as an Each count (rather than a bulk weight or volume measure). In practical terms, this typically includes retail-ready units that are counted individually (for example, individually packaged finished goods).

Compliance meaning: if the item you are packaging is a final product and its unit of measure is “Each,” Metrc will require an expiration date value to complete the “Create Packages” action after May 15, 2026.

How this affects day-to-day cannabis operations

Package creation will fail without an expiration date: packaging staff will need to enter an expiration date every time they create a new final-form Each package. If your workflow relied on leaving this blank, you should expect interruptions until procedures are updated.

Packaging and label data needs to be aligned: the expiration date stored in Metrc should match what your operation prints on packaging/retail labels where required, and it should be consistently applied across lots/batches based on your internal shelf-life rules and product specifications.

SOP and training updates: update packaging SOPs so the expiration date is determined, documented, and entered at the time of packaging (or prior to packaging if your business logic requires approvals).

Sell-by date workflow changes: if your team was entering Sell By Date because it was historically expected, you can remove that step for New York after May 15, 2026, while still ensuring Expiration Date is populated.

Metrc UI: where expiration date is required when creating packages

The bulletin’s workflow describes creating a new package from an existing package in Metrc and entering the required expiration date during package creation.

Step 1: Navigate to Packages, then select Active.

Step 2: Select the source package you want to use to create a final-form, count-based package.

Step 3: Select New Package.

Step 4: In the New Package window, enter the new tag number, location, and the final-form, count-based item (Each).

Step 5: Deduct the appropriate quantity from the original package into the new package.

Step 6: Add a note if desired (optional).

Step 7: Select the packaged date.

Step 8: Enter the required expiration date (the bulletin notes the field may default to 365 days; your operation remains responsible for entering the correct value for the product).

Step 9: Select Create Packages.

Metrc API (TPI) impact: /packages/v2 now needs ExpirationDate

For integrators and technical teams using the Metrc API in New York, this bulletin includes the relevant endpoint used to create packages.

Endpoint: POST /packages/v2/ (creates new packages for a specified facility)

Key parameter: licenseNumber (the facility license number for which packages are being created)

Permissions noted in the bulletin: View Packages and Create/Submit/Discontinue Packages

Field requirement change: for final-form, count-based (Each) packages created after May 15, 2026, include ExpirationDate in the payload so package creation does not fail due to missing required data.

SellByDate handling: the bulletin indicates Sell By Date will no longer be required effective May 15, 2026; API implementations can keep SellByDate null unless your internal business processes still track it outside Metrc.

Labeling and compliance systems: reducing errors with Distru

Because expiration date capture now gates package creation for final-form Each items, aligning your Metrc data with what prints on packaging is critical for avoiding rework and compliance risk.

DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels. It helps teams consistently print required data elements (including Metrc package information and fields commonly used for Metrc Retail ID compliance) so what’s on the label matches what’s recorded in Metrc.

DistruERP: For larger operators that need end-to-end supply chain management, DistruERP is Distru’s comprehensive Cannabis ERP platform, designed to connect purchasing, production, inventory, sales, and compliance workflows in one system while supporting Metrc reporting requirements.

Support and training resources referenced in the bulletin

Metrc support portal: Submit support requests and access resources at https://support.metrc.com/ (also accessible from the Metrc application’s Support menu).

Metrc Learn: Metrc’s training platform provides role-based courses and educational content to improve user proficiency.

API support: For API/TPI questions, contact Metrc API Support at api-info@metrc.com.

Operational takeaway: before May 15, 2026, confirm your packaging SOPs, training, and any integrated software are ready to consistently populate expiration dates for all final-form Each items in Metrc (New York).

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
Forecasting

Distru Production Forecast

Know how much of each product to make this week, based on real sell-through.

SKILL
Finance and COGS

Past-Due Invoice Emails

Draft one payment reminder per customer for every past-due invoice.

SKILL
Customer Management

Company List Clean-Up

Clean a state license export or lead list before it goes into your CRM.

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.