Metrc (Maryland) is updating how growers record immature plant batches: beginning August 25, 2026, licensees must assign a Metrc location when creating immature plant batch plantings. This article summarizes Metrc Support Bulletin MD_IB_0127, explains what changes in the Maryland Metrc workflow, and outlines the practical day-to-day operational impacts for Standard Grower Businesses and Micro Grower Businesses.
Bulletin summary (MD_IB_0127) and key dates
Bulletin number: MD_IB_0127
Distribution date: 08/12/2026
Effective date: 08/25/2026
Who this applies to: Maryland Standard Grower Businesses and Maryland Micro Grower Businesses using Metrc
What Metrc and MCA are implementing: Locations will be enabled for tracking on immature plant batches in Maryland Metrc, and a location will be required when creating immature plant batch plantings.
What is changing in Maryland Metrc for immature plant batches
As of August 25, 2026, Maryland Metrc will require a Location to be selected when you create an immature plant batch planting. In practical terms, the “Create Plantings” action for immature batches will not save unless the Location field is completed.
This change is specifically about immature plant batches (the batch-level record created during “Create Plantings”), not only about later-stage plants. The intent is to ensure immature inventory has a defined, trackable physical place in the facility as soon as it is created in Metrc.
How to designate a location when creating immature plantings
In Metrc, go to Plants, then Immature, then select Create Plantings. When entering planting details (batch name, plant type, plant count, strain, and planting date), you must select a Location before submitting.
Metrc also notes that a location must already exist in your Metrc facility configuration before it can be assigned. If your team does not see the correct rooms or areas available in the Location field, you will need to create or update facility locations in Metrc before attempting to create the planting.
Sublocation is optional: Maryland Metrc will also allow a Sublocation field during Create Plantings. This can be used to track more granular placement (for example, a shelf, rack, table, or bay) under the broader Location. Metrc indicates Sublocation is optional and references additional guidance in MD IB #104 regarding sublocations.
Practical operational impact for grow teams
This update adds a required data point at the moment immature batches are created, which changes daily workflows in propagation and early cultivation. If a cultivation user attempts to create an immature batch without choosing a location, the record will fail validation and the planting will not be created, potentially delaying daily production logging.
To stay compliant and avoid rework, most teams will need to align three things: the physical facility layout (rooms and areas), the Metrc Location list, and internal procedures for where immature batches are placed immediately after creation. This is especially important if your operation frequently creates multiple immature batches per day across multiple rooms or benches.
Once locations are consistently captured at creation, the location history becomes more useful for internal controls and regulatory review because it creates clearer traceability for where immature inventory was kept during critical early stages.
Location and sublocation structure: what “good” looks like
A strong setup is one where every staff member can confidently pick the same location choice for the same physical area every time. Many operators accomplish this by using clear, unambiguous names for Locations that mirror signage in the facility (for example, “Immature Room,” “Clone Room,” or “Propagation Room”), and then using Sublocations only where additional granularity actually improves day-to-day management.
If you choose to use Sublocations, treat them as an optional precision layer rather than a requirement. Overly complex sublocation maps can slow down data entry and increase selection errors, while a thoughtfully limited set (for shelves, racks, or zones that matter operationally) can improve consistency without adding friction.
Related compliance tooling: labels and end-to-end operations
While this bulletin focuses on plant tracking locations, accurate Metrc data often connects downstream to packaging and retail workflows. DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams keep labeling aligned with Metrc requirements, including workflows where Metrc Retail ID values must be represented correctly on retail labels.
For larger operators who need broader visibility and control across cultivation, manufacturing, inventory, orders, and distribution, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for complete supply chain management alongside compliance-focused execution.
Metrc support and training resources
If you need help updating locations, troubleshooting required-field errors, or training staff on the updated immature planting workflow, Metrc provides several support channels.
Metrc Support: Submit and track a case via the Metrc Support portal or call 877-566-6506.
• Monday–Friday, 8 a.m. ET–10 p.m. ET
• Saturday, 10 a.m.–8 p.m. ET
• Sunday, voicemail or portal only
Metrc Learn: On-demand training focused on system functionality and workflow efficiency (available via Metrc).
Metrc Expert: In-app knowledge base accessed from the widget icon in the lower right corner of Metrc.
Metrc.com: Visit Metrc.com for state partner pages, training links, and additional resources.
