How Maryland Dispensaries Handle Metrc Misconfigured Items

 A misconfigured Metrc item can create problems far beyond a single product record. For Maryland dispensaries, item data can affect package creation, inventory mapping, testing workflows, POS catalogs, and downstream reporting. The safest response is to identify exactly which required fields are missing and correct the underlying item instead of creating duplicate records as a shortcut.

For retailers using a Metrc-compliant POS for Maryland, the operational challenge is keeping the POS product catalog aligned with corrected Metrc data. If a field changes in Metrc but the corresponding POS mapping remains outdated, staff may still encounter mismatched categories, duplicate SKUs, or confusing inventory records.

This became particularly relevant on June 24, 2026, when Metrc introduced a new Misconfigured column for Maryland licensees. Metrc defines a misconfigured item as one that is missing one or more data fields currently required by its assigned Item Category. The new workflow gives cannabis businesses a direct way to find configuration problems before they create additional downstream errors.

What a Misconfigured Item Means in Metrc

A misconfigured item is not necessarily an incorrect product in every respect. The issue may be that the product was created under requirements that later changed or that one or more fields required by its current category are incomplete.

The Items grid now includes a Misconfigured column. When an issue exists, Metrc displays a red badge indicating the number of problems, such as “1 Issue” or “3 Issues.” Items without configuration issues display “No.”

The feature also supports sorting and filtering, which means employees do not need to manually open every item record to find affected products.

The number of issues should be treated as a diagnostic starting point, not as a reason to immediately rebuild the entire product record.

Why Dispensaries Should Review Misconfigured Items

Incorrect or incomplete item data can affect later workflows because Metrc items serve as a foundation for regulated inventory activity.

For Maryland dispensaries, configuration problems can contribute to:

• incorrect POS-to-Metrc mappings;

• package creation problems;

• inconsistent product categories;

• incomplete product information;

• reporting confusion;

• unnecessary duplicate items;

• additional reconciliation work.

Metrc specifically introduced the feature to improve visibility into item configuration issues before affected items are used in downstream workflows such as package creation and testing submission.

Step 1: Filter the Items Grid

Start With the Misconfigured Column

Managers should first identify the scope of the issue.

Rather than editing products individually as employees encounter them, use the Misconfigured column to isolate affected records.

A practical review can include:

• item name;

• item category;

• number of configuration issues;

• whether the item has been used;

• current approval status;

• related POS product mapping.

Metrc also recommends reviewing the “Used” column. If an item was created but never used and will never be needed, the licensee may choose to discontinue it rather than spending time correcting the configuration.

Catalog cleanup should distinguish active operational products from unused records that can simply be retired.

Step 2: Identify the Missing Fields

The Misconfigured feature provides visibility at both the item level and individual field level. This helps staff understand whether the issue involves one missing value or several required attributes.

Before making any correction, compare:

• current Metrc item information;

• assigned Item Category;

• physical product information;

• approved product documentation where applicable;

• corresponding POS record.

Avoid guessing what a missing value should be.

For cannabis stores, this review is also a useful opportunity to find catalog inconsistencies between the compliance system and retail software.

Step 3: Determine Whether State Pre-Approval Applies

Pre-Approved Items Follow a Different Process

Maryland's June 2026 Metrc guidance makes an important distinction between items that require state pre-approval and those that do not.

For a state pre-approved item, the licensee should not simply edit the record immediately. Metrc instructs licensees to contact the Maryland Cannabis Administration at the product-approvals address identified in the bulletin and request that the affected item be reset.

Once MCA resets the item, its approval status changes to “RequiresUpdate.” At that point, the item cannot be used until it has been revised and reapproved.

This status change matters operationally because the timing of the correction can affect inventory workflows that depend on the item.

Step 4: Edit and Resubmit the Item

After a state pre-approved item has been reset, the licensee can select “Edit Items” and correct the required information.

The Maryland workflow then requires the user to select “Revised” on the relevant row to return the updated item to MCA for approval. Metrc notes that MCA review may take up to two weeks after resubmission.

Dispensary managers should therefore avoid treating the reset as a purely technical action that can be performed at any convenient moment.

Before requesting a reset, consider:

• current inventory using the item;

• expected receiving activity;

• packages connected to the product;

• POS availability;

• ecommerce availability;

• operational impact while approval is pending.

Plan the correction before changing the item's approval status.

Step 5: Handle Items That Do Not Require Pre-Approval

The process is simpler for items that do not require Maryland state pre-approval.

Metrc directs licensees to review the Misconfigured column and use “Edit Items” to update the affected information.

However, there is an important limitation: Item Name and Item Category cannot be edited after an item has been created.

This distinction prevents employees from assuming that every configuration issue can be solved by rewriting the existing product record.

If the problem involves information that cannot be changed, staff should follow applicable Metrc and MCA guidance rather than creating an improvised workaround.

Do Not Automatically Stop Using Every Flagged Item

One detail in Maryland's guidance deserves particular attention.

Metrc states that a misconfigured pre-approved item continues to be usable until its approval status changes, such as when MCA resets it.

That means seeing a red issue badge does not by itself mean the POS team should immediately remove every related product from sale.

Instead, management should determine:

• which field is missing;

• whether the item requires state approval;

• whether a reset is necessary;

• when the correction should occur;

• what downstream operations will be affected.

A misconfiguration alert is a signal to investigate and correct the record—not a substitute for understanding its current status.

Keep POS Product Mapping Aligned

Correcting Metrc is only one part of the dispensary workflow.

If the POS maintains a mapped product catalog, administrators should review the corresponding retail item after the Metrc correction.

Check:

• product name;

• category;

• SKU;

• unit of measure;

• package mapping;

• ecommerce listing;

• inventory relationship.

A Maryland dispensary POS platform should make it possible to preserve the correct relationship between operational retail inventory and Metrc records.

Do not create another POS product simply because the Metrc item temporarily requires attention. Duplicate products can split sales history and make inventory reconciliation more difficult.

Check Ecommerce After the Correction

Product configuration can also affect customer-facing menus.

After an item or mapping changes, verify that ecommerce still displays the correct:

• product;

• size;

• category;

• price;

• available quantity.

If a correction causes the POS integration to interpret the item as a new product, an online menu could display duplicate listings.

A compliance-data correction should not silently create a customer-facing catalog problem.

Use Metrc History to Document Changes

Metrc's Misconfigured Items feature includes history tracking. Correction records appear chronologically in the History tab of the Items grid, providing an audit trail of misconfigured fields and subsequent updates.

Retailers can review the official Metrc Maryland Misconfigured Items bulletin for the current workflow.

For internal documentation, managers may also record:

• date the issue was identified;

• affected item;

• fields requiring correction;

• person responsible;

• MCA communication where required;

• reset date;

• resubmission date;

• approval status;

• POS mapping verification.

The audit trail should explain both what changed and how the dispensary kept its retail systems aligned afterward.

Avoid Duplicate Items as a Quick Fix

Creating a replacement item may appear easier than correcting an existing one, but unnecessary duplicates create long-term catalog problems.

They can lead to:

• inventory split between several records;

• duplicate ecommerce products;

• inconsistent sales reporting;

• employees selecting the wrong SKU;

• difficult historical analysis.

The better workflow is to determine whether the existing item can be corrected under the applicable Metrc procedure.

When a genuinely new or materially different product requires its own item, follow the normal item-creation and approval process instead of using duplication simply to bypass a configuration warning.

Assign Clear Permissions

Misconfigured-item corrections should generally be handled by employees who understand both Metrc and the dispensary's product catalog.

Consider restricting access to:

• item creation;

• item editing;

• POS mapping;

• SKU creation;

• inventory adjustments;

• product activation and deactivation.

Front-of-house employees can report an issue without needing permission to modify compliance data.

The person who notices the problem does not necessarily need to be the person who fixes the underlying configuration.

Build a Routine Misconfiguration Review

The new column is most useful when it becomes part of normal catalog maintenance.

A weekly review can include:

• filtering for misconfigured items;

• checking new issue badges;

• reviewing unused products;

• identifying state pre-approved items;

• assigning corrections;

• checking pending MCA approvals;

• verifying corrected POS mappings.

Maryland requires every MCA licensee to participate in the state's Metrc tracking program, making reliable item maintenance part of a broader regulated inventory environment.

Review Before Receiving New Inventory

If a known misconfigured item is about to be used for new packages or incoming inventory, resolve the issue as early as practical.

This reduces the chance that the same configuration problem becomes attached to additional operational records.

Misconfigured Item Checklist

When a Maryland dispensary finds a flagged item, verify:

• the Misconfigured badge and affected fields;

• whether the item has previously been used;

• whether it requires state pre-approval;

• current approval status;

• whether MCA reset is required;

• which fields can legally and technically be edited;

• POS and ecommerce mappings;

• history after correction;

• final approval status where applicable.

Do not consider the task complete until both Metrc and connected retail systems reflect the intended product configuration.

Final Takeaway

Maryland's new Misconfigured Items functionality gives cannabis businesses better visibility into incomplete item records. The process is especially important because state-pre-approved items and items that do not require pre-approval follow different correction paths.

The best dispensary workflow is to identify the exact problem, follow the correct Metrc correction process, protect downstream operations during the update, and then verify the POS mapping once the item is corrected.

For Maryland cannabis retailers, disciplined item maintenance can prevent small catalog problems from becoming larger inventory, ecommerce, reporting, or reconciliation issues—and provides a much cleaner audit trail when product data changes over time.