This article explains Metrc (Minnesota) Support Bulletin MN_IB_0062 on how to assign, calculate, and update cannabis package expiration dates and use-by dates in Metrc, effective June 15, 2026, including the role of stability testing and day-to-day operational impacts for licensees.
Bulletin overview (MN_IB_0062) and effective date
Bulletin: Metrc Support Bulletin MN_IB_0062
Distribution date: May 11, 2026
Effective date: June 15, 2026
Purpose: Define how expiration dates and “best if used by” (use-by) dates must be used for items and packages in Metrc for Minnesota operators.
Use-by date vs expiration date in Metrc (by product type)
Beginning June 15, 2026, Metrc will require an expiration-related date on items and packages, and the required date type depends on the product category.
Flower products: Licensees must enter a Use By date.
Concentrates and finished products: Licensees must enter an Expiration date.
Operationally, this means item setup must align with the correct date type so that downstream package creation, labeling, inventory control, and retail readiness workflows don’t break due to missing or mismatched shelf-life data.
Default shelf-life behavior when creating a new package
When you create a new package, Metrc will automatically populate the expiration or use-by date based on a short default rule.
Bulk flower: The use-by date will default to 1 day after the harvest date.
Concentrates and finished products: The expiration date will default to 1 day after the packaging date.
Metrc allows the date to be manually updated during new package creation when you have stability testing results that support a longer shelf life.
Six-month expectation until stability is demonstrated
Until product stability has been demonstrated on the first batch of a cultivation or manufacturing process, expiration or use-by dates should be set within 6 months of the harvest date (for flower) or manufacturing date (for manufactured products).
In practice, Minnesota operators should align their SOPs so that initial item setup and package creation procedures reflect a conservative shelf-life window until stability evidence is documented, reviewed, and applied consistently.
How to calculate shelf life after stability is established
Once stability is established, the item should be updated in Metrc so the system reflects the demonstrated stability period for future packages.
Key calculation rule: The expiration or use-by date for a batch is determined from the date the batch compliance testing was successfully completed, plus the demonstrated stability duration.
Example from the bulletin: If a product demonstrates 8-month stability and compliance testing was successfully completed on January 1, the expiration date would be August 31.
This matters operationally because it ties shelf-life control to testing completion (not only harvest, manufacture, or package dates), so QA teams should ensure the “testing complete” milestone is captured and communicated clearly to production, packaging, and inventory teams.
Updating a package expiration or use-by date in Metrc
Metrc supports updating shelf life after package creation, which is important when stability determinations change, corrections are needed, or a default date was applied initially.
Manual update during new package creation
The expiration or use-by date can be updated manually when creating a new package using a new item, reflecting stability testing results rather than the default 1-day rule.
Repackaging behavior (same item)
When repackaging an existing package using the same item, Metrc will not show an expiration or use-by date field in the repack action window. If you need to adjust the date for the resulting package, you must do so after the package exists.
Edit Shelf Life on an existing package
Navigation: Go to the Packages area in Metrc, select the package, and use the Edit Shelf Life action to enter an updated expiration or use-by date.
This workflow is the primary method for correcting or extending shelf life for packages already created, and teams should document when edits are permitted, who can approve them, and what stability/testing documentation supports the change.
Practical compliance implications for day-to-day operations
Item setup governance: Because the requirement is applied at the item level (flower uses “Use By,” manufactured items use “Expiration”), operators should standardize naming conventions and item templates to prevent mismatched product types and shelf-life rules.
Packaging and production planning: The default 1-day-from-harvest or 1-day-from-packaging behavior can create extremely short shelf life if not updated, potentially triggering internal holds, blocked transfers, or retail readiness issues. Packaging teams should confirm shelf life before finalizing lots for distribution.
Inventory rotation and disposal risk: Accurate expiration/use-by dates improve FEFO (first-expire, first-out) inventory movement and reduce the chance of holding “expired” inventory that becomes unsellable or requires remediation steps based on internal policy.
QA and testing coordination: Because stability-based expiration is calculated from successful compliance testing completion, QA teams should ensure test completion dates are tracked reliably and that stability assumptions are applied consistently across batches and items.
Audit readiness: Edits to shelf life should be traceable to stability evidence and internal approvals. Even when Metrc permits the edit, licensees should be prepared to explain why a date was changed and what documentation supports it.
Labeling support: DistruLabels and DistruERP
Expiration and use-by dates affect not only Metrc records but also what must appear (or be derived) on packaging and retail labels, depending on product type and Minnesota requirements.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels. It helps operators standardize label fields and reduce errors when aligning label data with Metrc records, including supporting workflows that depend on accurate Metrc Retail ID information for retail-ready operations.
DistruERP: For larger operators that need end-to-end supply chain management, DistruERP is Distru’s comprehensive Cannabis ERP platform designed to manage inventory, manufacturing, compliance workflows, and multi-step operational processes that connect back to Metrc reporting.
Minnesota rule and technical references cited in the bulletin
Minnesota Rules (9810.3100): https://www.revisor.mn.gov/rules/9810.3100/
Minnesota Cannabis Technical Authority (Standards for Sampling and Testing Cannabis Products): https://mn.gov/ocm/businesses/resources/producttesting/technical-authority.jsp
These references provide the state-level framework that supports how stability testing relates to shelf-life expectations, and they should be used to align internal QA documentation with Metrc data entry.
Metrc support and training resources
Metrc Support Portal: Access support through https://support.metrc.com or from within Metrc via the Support dropdown on the navigation toolbar.
Portal access note: First-time access typically requires a username, the correct state selection, your facility license number, and a valid email to set a password.
Metrc Learn: Metrc Learn provides interactive training and facility-specific learning paths for users who need to improve day-to-day system proficiency.
Additional in-system resources: Within Metrc, use the Support dropdown to access guides, manuals, and other educational materials relevant to packages, items, and compliance workflows.
