Metrc (Minnesota) issued Support Bulletin MN_IB_0045 (distributed 08/14/2025; effective ongoing) to require a standardized naming convention for new harvest batches and manicure batches created in Metrc, reducing errors and keeping cultivators aligned with OCM naming standards. This article explains the required format, key definitions, how it affects day-to-day cultivation workflows, and where to find Metrc training and support.
What changed: a required harvest and manicure batch naming convention
Metrc is requiring cultivators to use a specific naming convention when creating new harvest batches and manicure batches in Metrc. The goal is consistency and fewer compliance issues caused by unclear or mismatched batch names.
Bulletin reference: MN_IB_0045 (Metrc Support Bulletin).
Effective date: Ongoing (applies going forward to newly created harvest and manicure batches).
Required format for harvest and manicure batch names
Metrc’s required naming convention is:
• Plant Strain Name | Date of Harvest or Manicure | HB or MB | Auto or Photo
How to interpret the fields: The name must include the strain, the activity date (harvest/manicure date), whether it is a harvest batch (HB) or manicure batch (MB), and whether the genetics are autoflower or photoperiod.
Example from the bulletin
Scenario: A batch of Cherry Diesel Auto harvested on 08/11/2025.
Required harvest batch name: Cherry Diesel | 08/11/2025 | HB | Auto
Key definitions (as used in the bulletin)
Harvest Batch: A uniform collection of cannabis plants harvested together, sharing the same strain or genetic stock (see 342.01 Subd. 7(2)).
Manicure Batch: Portions of a plant are harvested while the remainder stays in the ground; each manicure batch is associated with a single day’s harvest activity, and strain specificity should be maintained.
Auto Flower: A cannabis plant variety that automatically switches from vegetative to flowering growth stage based on age.
Photoperiod Plant Flower: A cannabis plant variety where life cycle phases (vegetative growth and bloom) are controlled by the frequency and length of time the plants receive light.
Important clarification: batch naming is not item naming
The bulletin emphasizes that harvest/manicure batch naming is different from item naming (the product/item records you set up in Metrc). In practice, that means you can’t assume your established item SKU or product naming rules satisfy this requirement; the batch name itself must follow the required format when you create the harvest or manicure batch.
Supersedes prior guidance: This required naming convention overrides any previously recommended harvest/manicure batch naming conventions.
Practical implications for day-to-day cannabis operations
More consistent traceability across teams and systems
Because the format forces the strain, date, batch type (HB/MB), and plant type (Auto/Photo) into the name, teams can quickly verify they are working in the correct batch without relying on internal shorthand that varies by employee, room, or shift.
Fewer preventable Metrc data quality errors
Standardized names reduce common issues such as mis-typed dates, missing strain references, or confusion between harvest batches and manicure batches created from similar genetics on different days. That matters for downstream tasks like package creation, transfers, and audits, where unclear naming can slow operations and create compliance risk.
Operational alignment with Minnesota OCM expectations
The stated intent is alignment with OCM naming standards. For Minnesota operators, this is a signal that regulators and auditors may expect to see these conventions used consistently in Metrc records during reviews.
How to implement the convention in your cultivation workflow
Standardize the date format: The bulletin example uses MM/DD/YYYY (e.g., 08/11/2025). Use a single date format consistently so your Metrc search results sort and filter predictably across teams.
Train staff on HB vs. MB: If your site performs partial harvest/manicure activities across multiple days, ensure staff understand when to create a manicure batch versus a harvest batch so the required “HB” or “MB” element is accurate.
Confirm Auto vs. Photo at the cultivar level: Ensure your genetics library (and internal SOPs) clearly designates whether a strain is autoflower or photoperiod so the final element of the batch name remains consistent.
Metrc resources referenced in the bulletin
Metrc Support portal: Use https://support.metrc.com or access Support from within the Metrc system (Support dropdown in the navigation toolbar) to reach the portal.
Metrc Learn training: The bulletin directs users to Metrc Learn and the “Create a Harvest Batch” training video for step-by-step system guidance.
Additional in-system resources: In Metrc, use the Support dropdown to access educational guides, manuals, and other materials.
Where Distru tools can help: labels and ERP alignment
DistruLabels (100% free) for compliant retail labels
While this bulletin focuses on harvest and manicure batch names (not packaging labels), many operators still run into compliance issues later when packaging and retail labeling must match the regulated data trail. DistruLabels is a 100% free tool for creating compliant packaging and retail labels and can help teams stay organized with requirements tied to Metrc Retail ID workflows by reducing manual label errors and improving consistency between your operational records and what prints on the label.
DistruERP for larger, end-to-end supply chain operations
For larger operators who need broader operational control beyond naming conventions, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for complete supply chain management, helping teams coordinate cultivation, manufacturing, inventory, sales, and compliance-related workflows in one system.
Compliance takeaway for Minnesota cultivators
For Metrc (Minnesota) cultivators, the core requirement is straightforward: when you create a new harvest batch or manicure batch in Metrc, name it using “Strain | Date | HB/MB | Auto/Photo.” Build the convention into SOPs and training so every batch created going forward is consistent, searchable, and aligned with OCM-focused naming standards.
