Metrc (New York) bulletin NY_IB_0015 announces that, beginning May 15, 2026, Sell By Date and Expiration Date fields become required when creating certain packages in Metrc. This article explains what changed, which products are impacted (final-form “Each” items), how to enter the dates in the Metrc user interface and API, and what operators should update in day-to-day workflows to stay aligned with New York Office of Cannabis Management (OCM) expectations.
Bulletin summary: what changed and when
Bulletin: NY_IB_0015
Distribution date: May 5, 2026
Effective date: May 15, 2026
Core change: Sell By Date and Expiration Date information is required for all final-form, count-based (Unit of Measure: Each) items in Metrc.
Metrc notes these fields are currently optional in the system, but after the effective date they must be populated to create packages for the impacted item types. In practice, this means package creation workflows that previously left these dates blank will start failing validation after May 15, 2026 for applicable “Each” items.
Which products are affected (final-form, count-based “Each” items)
The bulletin specifically targets final-form, count-based items, meaning products tracked as individual units using Each (not bulk, weight-based units) when packaging in Metrc.
In most operations, this category commonly includes finished goods such as individual pre-roll units or packs, vape cartridges, edibles units, capsules, topicals, or other retail-ready items configured as “Each” in the Metrc Item catalog.
If you are unsure whether an item is impacted, confirm the item’s configuration and unit of measure used during packaging. The requirement is tied to the “final form” and “Each” packaging context described in the bulletin, so aligning item setup with real-world packaging is important to avoid unexpected package-creation errors.
How to enter Sell By and Expiration Dates in the Metrc UI
Metrc’s bulletin guidance focuses on the “New Package” workflow. When you create a new final-form, count-based package from an existing (bulk/source) package, you must populate the required date fields.
Step 1: Navigate to Packages, then select Active.
Step 2: Select the bulk (source) package you want to convert into a final-form, count-based package.
Step 3: Select New Package.
Step 4: In the New Package window, enter the New Tag, Location, and the Item (final-form, count-based/Each).
Step 5: Deduct the appropriate quantity from the original package (right side) into the new package (left side).
Step 6: Add a Note if desired (optional).
Step 7: Select the Packaged Date (often shown as the actual date of the packaging event).
Step 8: Enter the required Sell By Date. Metrc indicates this may default to 365 days, but you are responsible for ensuring the date aligns with your product’s shelf-life policy and OCM expectations.
Step 9: Enter the required Expiration Date. Metrc indicates this may also default to 365 days, and should be reviewed for accuracy.
Step 10: Select Create Packages.
Operationally, the key point is that Sell By and Expiration Dates are no longer “nice to have” data fields for these packages; they become required inputs that can block package creation if omitted.
Metrc API impact: POST /packages/v2 now needs the date fields
For integrated operators and software vendors, the bulletin includes Technical Platform Integrator (TPI) context for package creation using the New York API endpoint: https://api-ny.metrc.com/.
Endpoint: POST /packages/v2/
Parameter: licenseNumber (the facility license number where packages are being created)
After May 15, 2026, integrations creating final-form “Each” packages should expect Sell By Date and Expiration Date to be required where applicable, and should populate those fields consistently to prevent transaction errors or rejected package creation.
The bulletin’s example payloads show fields named SellByDate and ExpirationDate included alongside other package creation attributes.
{
"Tag": "ABCDEF012345670000020201",
"Item": "Your Final Form Item",
"Quantity": 100,
"UnitOfMeasure": "Each",
"ActualDate": "2026-05-15",
"SellByDate": "2027-05-15",
"ExpirationDate": "2027-05-15"
}
Coordinate internally between compliance and technical teams so your configured shelf-life rules (and any defaulting logic) match what your facility intends to represent in Metrc and on consumer-facing labels.
Day-to-day operational implications for New York operators
This change is primarily a workflow and data discipline requirement. Once effective, teams that package finished goods as “Each” should plan for these practical impacts.
Packaging may be blocked if dates are missing: If staff are used to leaving Sell By/Expiration blank, packaging events can fail at the point of creating the new package in Metrc, delaying production, transfers, or deliveries.
Alignment between Metrc data and printed labels matters: When Sell By and Expiration Dates are captured in Metrc, operators should ensure the same dates appear on the retail label where required by internal policy and applicable OCM rules, so there is no mismatch between system-of-record and packaging.
Standardization reduces errors: The bulletin mentions 365-day defaults. Defaults can be helpful, but only if they reflect your product category’s intended shelf-life; otherwise, they can create systematic inaccuracies across many SKUs.
Training and SOP updates are required: Packaging staff, inventory staff, and anyone creating packages (including through integrations) should be trained on which SKUs are “Each” final form and how to select the correct dates.
Using DistruLabels to support compliant retail labeling
DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can support operational consistency by helping teams produce labels that match required tracking data elements. For operators managing Metrc workflows, a well-controlled label process also helps reduce discrepancies that can show up during audits or inventory reconciliation.
DistruLabels can be particularly useful for teams working to maintain Metrc Retail ID compliance by ensuring retail label outputs are generated in a consistent, standardized way alongside the product attributes your operation tracks and prints.
For larger operations: DistruERP for end-to-end supply chain management
For multi-site or high-volume operators that need deeper controls than labeling alone, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for complete supply chain management. As compliance requirements in Metrc become more data-dependent (like required Sell By and Expiration Dates), ERPs can help centralize item setup, standardize shelf-life logic, and coordinate packaging, inventory, and fulfillment across teams.
Support resources referenced by Metrc
Metrc Support: Submit and manage support requests via https://support.metrc.com/ (also accessible from within Metrc through the Support dropdown).
Metrc Learn: Metrc’s training platform offers role- and facility-specific learning content to help users apply system requirements correctly.
API support (TPI): For API-related questions, Metrc references contacting the API Support team at api-info@metrc.com.
If you operate in New York, incorporate this change into packaging SOPs before May 15, 2026 so your final-form “Each” package creation remains uninterrupted and your Sell By/Expiration Date data stays consistent across Metrc records and retail labels.
