This article explains Metrc (Missouri) Bulletin MO IB 0050 on Harvest Batch best practices, issued with the Missouri Division of Cannabis Regulation (DCR). It covers how to correctly create, verify, edit, package, and finish harvest batches in Metrc so your cultivation records stay strain-accurate, weights are defensible, and downstream compliance reporting is clean.
What the bulletin covers (MO IB 0050)
Missouri’s guidance focuses on consistent use of Metrc’s Harvest workflow to reduce common mistakes that can create compliance risk later (inventory discrepancies, incorrect strain reporting, inaccurate waste, and packaging errors). The bulletin emphasizes strain integrity, accurate wet-weight capture at harvest, timely corrections, and clean transitions from plants to harvest batches to packages.
How Harvest Batches work in Metrc (Missouri)
In Metrc, the Harvest action can be applied to a single plant or multiple plants at once. When you harvest multiple plants together, those plants become one harvest batch in the system. Missouri’s key rule highlighted in the bulletin is that a harvest batch must be single-strain and include plants harvested on the same day.
Metrc also supports creating harvest batches via CSV upload, which can be useful for high-volume harvest days where operators want standardized data entry.
Creating a harvest batch from flowering plants
The bulletin’s workflow begins in the Plants area, where operators select the plants to be harvested from the Flowering grid. The plants selected together will form the harvest batch, so the selection step is where most strain-mixing errors originate.
Manicure vs. Harvest: when to use each action
Metrc includes a Manicure action for situations where usable cannabis is removed from the plant before the whole plant is fully harvested (for example, if you anticipate selling or processing material taken off the plant early). The bulletin notes that Manicure is available from both the vegetative and flowering tabs.
Use Harvest when plants are cut down and you are formally moving them into the harvest batch workflow.
Wet weights and harvest batch naming conventions
After flowering plants are cut down, the bulletin instructs that they must be individually weighed and each plant’s wet weight recorded in Metrc. You will also select the location the harvested plants are moved into and assign a harvest batch name.
Missouri’s recommended best practice for naming is to use strain name + harvest date. This makes it easier to troubleshoot, reconcile, and audit harvests later (and aligns with how operators often name immature plant batches).
Verifying harvest batch details in the Harvested tab
Once the harvest batch is created, the bulletin instructs operators to verify the batch in the Harvested grid. Operationally, this is where you catch issues before they cascade into packaging, transfers, or manufacturing.
Confirm strain is not “Multi-Strain”
In the Harvested view, confirm the harvest batch name and total wet weight are correct, and verify the Strain column reflects the correct strain. If it shows “Multi-Strain”, that indicates a compliance problem under Missouri expectations because DCR requires harvest batches to contain only a single strain.
The 72-hour edit window (Missouri operational impact)
The bulletin states licensees have 72 hours to edit a harvest batch. This matters day-to-day because your team needs a tight post-harvest verification routine: if the wrong strain plants were accidentally included, you can remove them during this window.
If the harvest batch is past the 72-hour discontinuation window, the bulletin directs operators to contact Missouri DCR at CannabisCompliance@health.mo.gov or work with their assigned Compliance Officer for assistance.
Reporting harvest waste in Metrc
After a harvest batch is created, the bulletin reminds operators that physical waste attributed to the harvest batch must be collected and recorded using Metrc’s Report Waste function. From an operations standpoint, accurate harvest waste entry helps prevent unexplained yield loss later and supports defensible inventory and production metrics.
Creating packages from a harvest batch
When plant material is ready to be packaged, the bulletin instructs operators to create packages directly from the harvest batch. Metrc will provide a creation template to help populate the required fields, and the resulting packages will appear in the active Packages grid.
Packaging different item categories as separate packages
The bulletin notes that it’s common to pull multiple item categories from the same harvest batch (for example, buds versus shake/trim). These must be recorded as separate packages to keep inventory categorized correctly for downstream workflows such as transfers, lab testing, manufacturing, and sales.
Verify package creation before moving forward
Metrc package mistakes can ripple into sales, transfers, and audits. The bulletin emphasizes verifying packages immediately after creation. If a package was created incorrectly, discontinue it and recreate it correctly rather than trying to “work around” a bad package record.
Drying and curing must stay under the harvest license
A key compliance constraint in the bulletin is that the entire drying and curing process must be completed under the same license where the harvest occurs. The bulletin explicitly states cultivation licensees cannot transfer whole wet plants to another cultivation licensee for drying, curing, or packaging on their behalf.
Practically, this affects production planning, labor allocation, and space utilization: your drying/cure capacity must match your harvest schedule at the licensed premises where harvest is recorded.
Finishing a harvest batch and moisture loss in Metrc
Once waste has been reported and packages have been created, the harvest can be finished in Metrc. When a harvest batch is finished, it moves to the Inactive tab in the Harvested section.
The bulletin also explains that any remaining weight still associated with the harvest batch will be attributed to moisture loss and recorded under the moisture loss column. Operationally, this system behavior makes it important to finish harvests only after packaging and waste steps are truly complete, so moisture loss is not masking unrecorded activity.
Unfinishing a harvest batch (when it was finished too early)
If a harvest batch was finished in error or prematurely, Metrc allows you to unfinish it. The bulletin directs users to find the harvest in the Inactive harvest list and use the Unfinish action to return it to the active Harvested grid.
This capability is operationally useful when teams discover late-stage issues such as missing waste, incomplete packaging, or data-entry errors that must be corrected before the harvest record is finalized again.
Metrc training and support resources referenced in the bulletin
Metrc Expert (in-app guidance)
The bulletin points operators to Metrc Expert, available inside Metrc on grids. The navigation path provided for harvest batches is:
Browse Guides & Resources > Plants > Flowering Plants > Creating Harvest Batch
Metrc Learn (LMS course)
The bulletin references Metrc Learn and the course titled “Create A Harvest Batch”, accessible via My Courses and Learning Plans.
Metrc Support portal
For assistance, the bulletin directs users to Metrc’s support portal at https://support.metrc.com (also reachable from within the Metrc system through the Support navigation). It notes first-time portal access typically requires a username setup, selecting the state, entering the facility license number, and using a valid email to set a password.
Labeling and downstream compliance: where tools can help
Although the bulletin is focused on harvest batches, the practical compliance impact usually shows up downstream during packaging and retail readiness. Once harvest material becomes Metrc packages, operators often need accurate, consistent labels tied to package data, including identifiers used for retail workflows.
DistruLabels is a 100% free tool for creating compliant cannabis packaging and retail labels, and it can help teams stay aligned with Metrc Retail ID compliance by producing consistent label outputs when products move toward retail use cases.
For larger operators who need deeper operational control across cultivation, manufacturing, distribution, inventory, sales, and compliance workflows, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for end-to-end supply chain management.
What Missouri operators should change day-to-day
The bulletin’s best practices translate into a few practical operational priorities:
- Prevent strain mixing at selection time by harvesting and selecting plants in clearly separated, strain-specific groups.
- Capture wet weights accurately per plant to reduce disputes, shrink questions, and reconciliation problems later.
- Standardize harvest batch naming (strain + date) so harvest-to-package traceability is easy for staff and auditors.
- Verify the harvest record immediately in the Harvested grid, especially checking for “Multi-Strain,” and use the 72-hour edit window proactively.
- Report waste and create packages carefully, separating item categories into distinct packages and discontinuing/recreating incorrect packages rather than carrying errors forward.
- Plan drying/cure capacity under the harvesting license to avoid prohibited wet-plant transfers for drying/curing/packaging.
Following these steps keeps Metrc records aligned with Missouri DCR expectations and reduces the likelihood of harvest-driven discrepancies that surface later during packaging, transfers, or compliance reviews.
