Metrc (Kentucky) Support Bulletin KY_IB_0015 (distributed 03/17/2026, effective ongoing) explains how Kentucky cannabis licensees should use Metrc’s new Processing Jobs functionality, including how to configure Processing Job Types, start and adjust jobs, create packages (production batches) from jobs, and finish or unfinish jobs with proper permissions and traceability.
What this Kentucky Metrc bulletin changes for operators
Processing Jobs are a structured way to document common manufacturing workflows (like infusion and extraction) while tying source packages, inputs, and resulting “production batch” packages together in Metrc.
Practically, this feature affects day-to-day operations in three main ways: it standardizes how teams record processing activity, it strengthens package genealogy (inputs to outputs), and it adds clear controls around when you can edit inputs (before outputs exist) versus when you must correct errors through adjustments.
Processing Job Categories and Attributes in Metrc (Kentucky)
Kentucky configures Processing Job Categories and Processing Job Attributes at the state level. Licensees can select from the available options, but cannot edit, add, or change these state-configured values.
Processing Job Categories (state configured)
• Infusion
• Extraction
Processing Job Attributes (state configured)
Attributes are required selections used to further describe the job. A single Processing Job Type or Processing Job can include multiple attributes when applicable.
• 1 Day
• 2 Day
• 3 Day
• Allergen
• Non-Solvent Extraction
• Solvent Extraction
Admin setup: configuring Processing Job Types
To use Processing Jobs effectively, you first create Processing Job Types (your standardized templates). In Metrc, the Industry Administrator for the license is automatically granted access to the Processing Job Type grid. Other staff must be granted permission by an Admin (or any user authorized to manage employee permissions).
Where to create Processing Job Types
Navigation: Admin > Processing Job Types
Action: Select the option to add a new job type in the Processing Job Types grid.
Required fields when adding a Processing Job Type
Name: The standardized name your team will recognize (for example, “Ethanol Extraction” or “Butter Infusion”).
Category: Select the Kentucky OMC-configured category (Infusion or Extraction).
Description: A clear summary of what the job type is used for.
Processing Steps: The step-by-step workflow; many operators paste SOP steps here to make the job type self-documenting.
Attributes: Select one or more relevant attributes (for example, Solvent Extraction, Allergen, 1 Day/2 Day/3 Day) based on how the job is performed.
Edit limitation: Once a Processing Job Type has been used to create any Processing Job, it can no longer be edited. Plan naming conventions and SOP text carefully before putting a job type into production use.
Starting a Processing Job in Metrc (Kentucky)
After Processing Job Types exist, staff with permission to manage Processing Jobs inventory can start individual Processing Jobs. Admins can grant this permission to other employees as needed.
Where to start a job
Navigation: Packages > Processing Jobs
Action: On the Active tab, start a new job and complete the required fields.
Key fields when starting a Processing Job
Processing Job Type: Choose from the Processing Job Types you previously created.
Processing Job Name: The unique job name that your operation will use to group production activity (this becomes the anchor for recording batches produced from the job).
Start Date: The date the job begins.
Input Package(s): Add one or more source packages used as inputs (you can search active packages and select them).
Input Quantity and Unit of Measure: Record how much material is taken from each input package, using the appropriate unit of measure; Metrc will sum total input weight/quantity at the top.
Operational implication: Train staff to enter accurate input quantities at the time the run starts. This reduces later corrections and supports clean, auditable package genealogy.
Adjusting Processing Jobs to correct input errors
If an entry mistake occurs in job inputs, Metrc provides an adjustment workflow. However, a Processing Job can only be adjusted if no packages have been created from that job.
Where to adjust a job
Navigation: Packages > Processing Jobs
Action: On the Active tab, select the job and open the Adjust function.
What you must record during an adjustment
Reason: Select the appropriate reason from the dropdown list.
Note: Add clarifying detail so auditors and internal reviewers can understand what changed and why.
Adjust Quantity: Enter a positive number to add input quantity or a negative number to subtract input quantity; the total input weight/quantity updates automatically.
Compliance implication: Because adjustments are blocked once outputs exist, operators should validate inputs before creating any packages from the job. After outputs are created, corrections typically require different inventory actions and may increase compliance risk if handled inconsistently.
Creating packages (production batches) from a Processing Job
This bulletin explains that packages you previously might have created and labeled as “Production Batch” packages should now be created directly from the Processing Job to accurately reflect which job produced which batch packages.
Where to create packages from a job
Navigation: Packages > Processing Jobs
Action: On the Active tab, select the job and use the Create Packages function.
Required fields to create a package from a Processing Job
New Tag: Select/enter the package tag for the new production batch package.
Location: Identify where the new package is physically stored.
Item: Choose the correct item for the new package being created.
Quantity: Record the quantity of the new production batch package.
Note: Optional operational notes (for example, run details, operator initials, or internal lot references).
Production Batch No.: Enter the batch name/number; if multiple batches are created from the same processing job, each production batch should have a different identifier.
Package Date: Record the date the package is created.
Finish Processing Job: If the job is complete after this package creation, select the option to finish the job.
Operational implication: This workflow makes it easier to demonstrate traceability from source packages to batch outputs, and it supports stronger internal batch records aligned with how Metrc expects manufacturing activity to be documented.
Viewing job details: created packages, source packages, and history
Each Processing Job provides drilldown details that help teams verify traceability and troubleshoot discrepancies.
Created Packages: Shows all production batch packages created from the processing job.
Source Packages: Shows all input packages used to create the processing job.
History: Shows a complete audit trail of job activity.
Finishing and unfinishing Processing Jobs in Metrc (Kentucky)
Finishing a Processing Job (and recording waste)
Once a Processing Job has produced all production batch packages it will produce, it should be finished. The bulletin notes that finishing is also the point where the operation records waste associated with the process (the byproduct used in the process).
Navigation: Packages > Processing Jobs > Active tab
Action: Select the job, choose Finish, enter the Date Finished, and finalize.
Unfinishing a Processing Job
If a Processing Job was finished in error, Metrc allows the job to be unfinished so the facility can make additional changes or create additional packages as needed.
Navigation: Packages > Processing Jobs > Inactive tab
Action: Select the job, choose Unfinish, and confirm in the unfinish window.
Operational implication: Use unfinish sparingly and document why it occurred, since frequent finish/unfinish activity can indicate process control issues and may draw scrutiny during internal reviews or state inspections.
Permissions and accountability: who can do what
Metrc separates Processing Job responsibilities into at least two key permission areas: managing Processing Job Types (templates) and managing Processing Jobs inventory (creating and working active jobs). Kentucky operators should align these permissions to job roles.
Recommendation: Limit Processing Job Type creation/editing access to SOP owners or production leadership, and grant Processing Job execution permissions to trained production staff who understand package selection, units of measure, and batch naming conventions.
Metrc support and training resources referenced in the bulletin
Metrc Support: Use https://support.metrc.com (also accessible through the Support option inside Metrc). First-time portal access requires your state selection, facility license number, and a valid email to set a password.
Metrc Learn: Training is available at https://learn.metrc.com and via “Sign up for Training” in the in-system Support menu.
Metrc Expert: The in-system knowledge base is accessible through the widget icon in the lower-right corner of Metrc for step-by-step guides and searchable help.
Labeling implications: Retail ID, DistruLabels, and DistruERP
While this bulletin is focused on Processing Jobs, it directly impacts how batch packages are created and identified in Metrc, which in turn affects downstream labeling accuracy (for example, ensuring the correct Metrc identifiers and batch references flow to packaging and retail labels).
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams stay aligned with Metrc Retail ID compliance by consistently printing the right identifiers on the right label formats.
DistruERP: For larger operations that need end-to-end supply chain management beyond Metrc entries, DistruERP is Distru’s comprehensive Cannabis ERP platform that supports workflows across manufacturing, inventory, sales, and operations so production-to-package-to-label processes stay coordinated as scale increases.
