Metrc (West Virginia) Bulletin WV IB 00 46 (distributed 06/16/2026; effective 06/24/2026) announces a new “Misconfigured” column in the Items grid to help operators spot item setup problems early, reduce downstream errors, and improve traceability when item data must be corrected.
What changed in West Virginia Metrc
The Items grid now includes a dedicated Misconfigured column positioned after the Category column. This column surfaces whether an item is missing one or more fields that are currently required for its assigned Item Category.
Practically, this means West Virginia licensees can identify item setup issues before those items are used in workflows that depend on accurate item definitions, such as package creation and lab testing submissions.
What “misconfigured” means in Metrc
Misconfigured item: An item that is missing one or more data fields required by its assigned Item Category at the time you are viewing/editing it.
Because Item Category requirements can drive what Metrc expects for downstream activities, this feature is intended to reduce preventable failures (or rework) caused by trying to use an item that lacks required configuration data.
How the Misconfigured column displays status
Each item row shows one of two outcomes in the Misconfigured column:
• A red “# Issues” badge (for example, “1 Issue” or “3 Issues”) when required data is missing for that item’s category.
• No when the item has no configuration issues based on current category requirements.
Sorting and filtering: The Misconfigured column supports sorting and filtering so teams can quickly isolate affected items instead of scanning the entire grid manually.
Field-level indicators: finding exactly what’s missing
Metrc provides visibility at two levels so staff can both identify a problem item and pinpoint the specific fields that require attention.
Item-level indicator: The red “# Issues” badge shows the total number of fields currently missing required data for that item.
Field-level indicator: Within the row, each misconfigured field displays a “Missing Data” label to show precisely which data points must be updated.
As users correct missing fields, the “Missing Data” labels and the badge count update to reflect the item’s new configuration status.
History tracking and auditability for item corrections
History tab logging: Changes related to misconfigured fields are recorded in the item’s History tab to create an auditable trail of corrections.
Chronological order: History records display in time order, supporting traceability when teams need to confirm what changed, when it changed, and how configuration issues were resolved.
This is especially useful for internal QA, compliance reviews, and troubleshooting scenarios where an item definition may have contributed to workflow interruptions.
Operational impact: where this prevents day-to-day workflow problems
For West Virginia operators, misconfigured items most commonly create friction at the moment a team tries to use an item in a dependent workflow. By flagging issues directly in the Items grid, Metrc helps prevent avoidable delays such as:
• Package creation failures or rework when item attributes required by the category are missing.
• Slower lab submission preparation when an item is not fully configured to meet current category expectations.
• Increased back-and-forth between compliance/admin staff and production teams when an item must be corrected urgently.
Using the Misconfigured filter as part of routine admin review (for example, before new production runs, new SKU onboarding, or lab submission cycles) can reduce operational interruptions.
How to update misconfigured items in West Virginia
Items that are pre-approved by the state (OMC)
Required action: Contact OMC to request that the misconfigured item(s) be reset.
What happens after reset: The item status becomes RequiresUpdate and the item cannot be used until it is revised and reapproved.
How to complete the update: Use Edit Items to make the necessary corrections, then click Revised on the right side of the row to submit the item back for OMC approval.
Related reference: Metrc notes that additional detail on the reset/revise process is available in WV IB #43.
Items that do not require state pre-approval
Required action: Use the Edit Items button to update the missing required fields directly, then save the changes so the misconfiguration indicators clear.
Labeling and SKU readiness: where compliance meets execution
Item configuration accuracy matters beyond Metrc navigation—it affects how reliably teams can generate compliant packaging/retail labels and keep products moving without relabeling or last-minute corrections.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels and can help teams stay aligned with Metrc Retail ID label requirements by producing consistent, scannable labels tied to the correct product and inventory records.
DistruERP: For larger West Virginia operations that need end-to-end coordination, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for complete supply chain management, helping connect inventory, production, sales, and compliance workflows in one system.
Metrc support and training resources
Metrc Support: Submit and track a case via the Metrc Support portal or call 877-566-6506.
Support hours (ET): Monday–Friday 8 a.m.–10 p.m.; Saturday 10 a.m.–8 p.m.; Sunday voicemail or portal only.
Portal access note: First-time portal access requires a username (established when logging in), the respective state, facility license number, and a valid email to set a password.
Metrc Learn: Metrc’s on-demand training platform provides interactive education on system functionality and workflow efficiency. Access it directly or via the Support drop-down in Metrc.
Metrc Expert: In Metrc, use the widget icon in the lower right to open the Metrc Expert knowledge base for step-by-step guides and answers.
Metrc.com: Visit https://www.metrc.com/ and navigate to your state partner page for additional training links and guidance.
