This article explains Metrc (Minnesota) Support Bulletin MN_IB_0053 (effective 11/24/2025) and what Minnesota OCM stability testing requirements mean in practice, including how to run Stability Study T0 in Metrc, manage timepoints, and correctly calculate and label best-if-used-by and expiration dates.
Bulletin context: MN_IB_0053 (OCM Stability Testing Requirements)
Bulletin number: MN_IB_0053
Distribution date: 11/24/2025
Effective date: 11/24/2025
Subject: OCM Stability Testing Requirements
Purpose: Update Minnesota cannabis and hemp licensees on OCM stability testing requirements used to support product dating on labels.
Minnesota OCM product dating: best-if-used-by vs expiration
Minnesota requires cannabis and hemp products to carry date-based labeling tied to stability.
• Flower must be labeled with a best if used by date.
• Concentrates and infused products must be labeled with an expiration date.
The bulletin points operators to the Cannabis Technical Authority (referenced in the bulletin as page 14) for the stability testing framework used to determine the appropriate best-if-used-by or expiration date for each product.
What “stability testing” means under this bulletin
OCM’s approach (as summarized in the bulletin) requires a business to demonstrate product stability by submitting sample material from the first batch of a cultivation or manufacturing process for shelf-life stability analysis by a licensed testing facility.
Stability is demonstrated for products in their final packaged form, which is why Metrc’s stability testing test types are only available for packaged product categories.
How to set up Stability Study T0 correctly in Metrc
To start a stability study, the business prepares a representative lab sample package and assigns both required compliance testing and the Stability Study T0 test to that initial lab sample package.
Business responsibility (sample preparation and assignments): The business prepares the representative sample for transfer to the testing facility, prepares stability samples for each timepoint in the study, and assigns required compliance testing plus Stability Study T0 to the initial lab sample package.
Business responsibility (coordination with the lab): The business must coordinate with the testing facility to ensure enough material is provided for compliance testing and stability analysis, consistent with what the business and lab agree is necessary.
Critical Metrc workflow constraint: The business should not assign any stability testing to the stability timepoint packages other than Stability Study T0 on the initial lab sample package. The bulletin warns that assigning stability tests beyond T0 in the wrong place can potentially freeze the entire batch of products until the stability study is completed.
Operationally, this means your Metrc testing request should be structured so that compliance tests and Stability Study T0 are tied to the initial lab sample package, while later stability timepoints are handled as the study progresses (and are typically reported by the lab at the agreed intervals).
Metrc reference: The bulletin directs licensees to Metrc Bulletin 54 for instructions on creating a lab sample package and creating the individual packages for each stability timepoint.
Stability timepoints (T1, T2, etc.): how results get reported
The bulletin explains that additional stability timepoints are not requested by the business in Metrc the way typical compliance tests are. Instead, stability timepoint results are reported by the testing facility at the agreed-upon intervals.
Stability results are entered by the testing facility as part of the stability study, and the status of the batch can be affected if a product fails at a particular timepoint. If the product fails a stability timepoint, Metrc may update the testing status to Test Failed, and that status can affect child packages derived from the original batch.
Storage options for stability packages
The bulletin provides two storage models. In both models, the business and testing facility communicate outside of Metrc to define storage conditions and timing for transportation and evaluation.
Option 1: Licensed business holds and stores stability packages: The business stores the stability timepoint packages. When reporting results, the testing facility uploads results using Stability Study T1, Stability Study T2, and so on to the package tag that was tested. The timepoint package is not a lab sample package and will not have any testing requested. The bulletin notes that if stability T1 is requested, it may lock the source package and any child packages created from that source package.
Option 2: Testing facility holds and stores packages: After timepoint packages are created (per Metrc Bulletin 54), the license holder includes those packages on the manifest when sending the initial lab sample package for testing. The license holder adds a manifest note indicating which package corresponds to which stability timepoint. The testing facility stores the packages until the predetermined timepoints and then uploads results using Stability Study T1, Stability Study T2, and so on to the package tag tested. As in Option 1, the stability timepoint package is not a lab sample package and will not have any testing requested, and requesting stability T1 may lock the source package and any child packages.
How stability results can impact child packages and “finished” status
The bulletin highlights an important downstream effect: if stability study results are entered on a batch package (passing or failing), those results may populate onto child or derived packages.
It also warns that if child or derived packages were previously marked finished, later-entered test results may cause those packages to become unfinished. If that happens, the business can use the Finish button in Metrc to finish the package again.
Practically, operators should expect that long-running stability studies can create delayed status changes in Metrc, and internal teams should have a plan for monitoring package status changes that occur after products have already moved through downstream workflows.
When a batch is released vs when a stability study finishes
Batch release: The business and testing facility report batch compliance testing results and Stability Study T0 results on the initial lab sample package. The bulletin indicates that compliant results will release the batch.
Stability study completion: The stability study continues through the agreed timepoints. A product’s demonstrated stability lifetime is determined after the study is complete (based on the last passing result), and the business must then communicate completion and submit the study to OCM (described further below).
Determining shelf life and calculating expiration dates
The bulletin defines product stability lifetime as the last passing result for stability testing for that product.
• Example logic from the bulletin: if a product passes stability at 9 months but fails at 12 months, the product is assigned a 9-month stability lifetime.
The business calculates the expiration date by adding the demonstrated stability lifetime to the date of product batch release testing (the compliance testing completion date used to release the batch).
• Example from the bulletin: if stability lifetime is demonstrated as 372 days on the first batch of a product, and compliance testing for the next batch is completed on July 1, then the expiration date for that next batch would be April 1.
Metrc data entry reference: The bulletin points to Metrc Bulletin 37 for instructions on how to enter item expiration date information in Metrc.
OCM reporting after the stability study is complete
Once the stability study is complete and each product has a demonstrated stability lifetime, the business must communicate to the office that the study has been completed and state the shelf life demonstrated for each product.
The bulletin instructs businesses to submit the completed study to OCM through the Stability Testing form.
Day-to-day operational implications for Minnesota operators
Plan stability at product launch: Because the stability study is tied to the first batch of a cultivation or manufacturing process, operators should incorporate stability planning into product development and initial production scheduling, including reserving adequate sample quantities for timepoints.
Coordinate tightly with your lab: The bulletin repeatedly emphasizes that the business and testing facility must agree on storage conditions, timepoints, sample quantities, and logistics outside of Metrc. This is operationally significant because it affects manifests, storage chain-of-custody, and the timing of later test result uploads.
Avoid unintended batch holds: The warning about assigning stability testing beyond Stability Study T0 to the wrong packages matters in real workflows. Mis-assigned stability tests can potentially freeze the entire batch and disrupt fulfillment timelines.
Expect delayed Metrc status changes: Stability timepoint failures can update a batch to Test Failed and may affect derived inventory. Teams should build monitoring and internal communication around potential downstream impacts, especially for products already converted into child packages.
Label execution: using DistruLabels and planning for Metrc Retail ID
Once you’ve calculated the correct best-if-used-by or expiration date logic from your demonstrated stability lifetime, you still need to execute compliant labels consistently across production runs and retail-ready units.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels. It helps teams standardize required fields and supports Metrc Retail ID compliance by making it easier to generate consistent labels aligned with Metrc-tracked identifiers and packaging workflows.
DistruERP: For larger Minnesota operations that need end-to-end inventory, manufacturing, distribution, and compliance workflows, DistruERP is Distru’s comprehensive Cannabis ERP platform designed to manage the full supply chain alongside Metrc processes.
Metrc support and training resources
Metrc Support Portal: Access help at https://support.metrc.com or via the Support dropdown within Metrc to reach the portal.
Metrc Learn: Metrc Learn provides interactive training organized by facility-specific programs. Access it through Metrc’s training resources or your Metrc Learn login page as provided by Metrc.
For Minnesota licensees implementing OCM stability testing for the first time, these resources can help align your internal SOPs with the correct Metrc package creation, testing submission, and results-handling workflows described in MN_IB_0053.
