In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

Maryland Metrc: Immature Plant Batch Locations

Maryland
August 25, 2026
Link to Metrc Bulletin
TL;DR

• Starting August 25, 2026, Maryland growers must assign a Metrc location when creating immature plant batch plantings.

• Locations must already exist in your facility configuration before you can assign them to new immature batches.

• Align your physical layout, Metrc location list, and internal procedures to avoid failed validations and workflow delays.

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.

The AI cannabis library

Free skills to put AI to work on your inventory, compliance and costing, and guides on where it actually saves time.

SKILL
Inventory Management

Distru Expiring Inventory

See stock about to expire, who already buys it, and a promo email draft to review.

SKILL
Compliance

Cannabis Inspection Readiness

Turn an upcoming state inspection into a checklist, binder index and gap list.

SKILL
Compliance

Cannabis Transfer Manifest Precheck

Check a B2B transfer before the driver leaves and get GO or HOLD per line.

SKILL
Purchasing

Cannabis Replenishment Planner

Turn sales and on-hand exports into a reorder plan and a draft PO by vendor.

SKILL
Compliance

Cannabis State Rules Lookup

Get a cited, dated answer to a state cannabis rule question.

SKILL
Operations

Cannabis Staff Scheduling Planner

Build a shift schedule that matches demand and stays inside your labor budget.

SKILL
Cultivation

Cannabis Harvest Yield Analysis

See which rooms and strains actually make money, from your own harvest data.

SKILL
Compliance

Cannabis Traceability Reconciliation

Find out why your physical count doesn't match Metrc or BioTrack.

SKILL
Compliance

Cannabis SOP Generator and Trainer

Turn process notes into an inspection-ready SOP and a staff training packet.

SKILL
Finance and COGS

Cannabis Batch COGS Calculator

Find out what a batch really costs per finished unit, line by line.

AI GUIDE
Blog

Why the Harness Matters More Than the AI Model

Two products can use the exact same AI model and perform completely differently. Here's why the harness, not the model, usually explains why.

AI GUIDE
Blog

What Is an Agent Harness? A Plain-English Primer

An AI model alone can't do much. The 'harness' around it is what makes it useful. Here's what that actually means, no jargon required.

AI GUIDE
Blog

Why MSOs Need an AI Strategy Before More Software

Adding another point solution won't fix an MSO's AI readiness problem. Here's why the data foundation has to come first.

AI GUIDE
Blog

The Supply Chain Buyer's Guide to AI Agents and MCP

Evaluating AI agent features in supply chain software? Here's a practical buyer's checklist, including what MCP means for your evaluation.

AI GUIDE
Blog

AI in Supply Chain: What's Hype, What's Working

AI in supply chain gets a lot of hype. Here's an honest look at what's actually delivering results in 2026, and what still needs a person.

AI GUIDE
Blog

Where AI Agents Fit in Cannabis Compliance

Not every step of your compliance workflow is a fit for AI. Here's a clear map of where it helps, and where it should stay hands-off.

AI GUIDE
Blog

The Skills Ops Teams Will Need When AI Agents Arrive

AI agents are coming for repetitive ops tasks in cannabis. Here's what your team needs to get good at instead, starting now.

AI GUIDE
Blog

What Happens When AI Gets Access to Your ERP

Giving an AI tool access to your cannabis ERP isn't all-or-nothing. Here's what real, scoped access looks like, and what to watch for.

AI GUIDE
Blog

AI and 280E: Where Automation Actually Saves Money

280E just got more complicated for mixed medical and adult-use operators. Here's where automated cost tracking actually helps, and its limits.

AI GUIDE
Blog

Can AI Forecast Wholesale Demand Better Than Excel?

Your wholesale forecast spreadsheet has limits. Here's what AI-assisted forecasting can actually add, and where a spreadsheet still wins.

AI GUIDE
Blog

Should Your Cannabis Business Have an AI Strategy?

You don't need to be an AI company to have an AI strategy. Here's a practical starting point for cannabis operators, no hype required.

AI GUIDE
Blog

What Is Claude Cowork? Could It Kill Data Entry?

Claude Cowork lets AI work directly in your files and tools. Here's what that means for the data entry eating your cannabis team's week.