Kentucky Metrc Processing Jobs Guide

This article explains Metrc (Kentucky) Support Bulletin KY_IB_0015 (distributed 03/17/2026, effective ongoing) on the new Processing Jobs functionality, including how Kentucky’s Office of Medical Cannabis (OMC) expects licensees to configure job types, start and adjust jobs, create batch packages, and properly finish jobs with recorded waste.

What “Processing Jobs” Means in Kentucky Metrc

Kentucky’s new Processing Jobs workflow is designed to document common manufacturing activities (such as extraction and infusion) in a more structured way. Practically, this creates a clearer chain of custody from input packages to output batch packages, with an auditable history of changes and completion.

For day-to-day operations, Processing Jobs becomes the hub where operators record what went into a run (inputs), what came out (new packages), and when the work was completed (finish), including any process waste.

Processing Job Categories and Attributes (State-Configured)

In Kentucky, Processing Job setup relies on state-configured categories and attributes. These options are defined by the OMC and cannot be edited by licensees. Your team should standardize internal naming and SOP language around these fixed selections to prevent inconsistent records.

Processing Job Categories

When you create a Processing Job Type, you must select a category that identifies the general purpose of the activity.

• Infusion
• Extraction

Processing Job Attributes

Attributes are required identifiers used to further describe the job. They are applied at the job/type level (as configured in Metrc) and can be selected in combination where applicable.

• 1 Day
• 2 Day
• 3 Day
• Allergen
• Non-Solvent Extraction
• Solvent Extraction

Operationally, these attributes help Kentucky regulators and internal QA teams understand the nature of the process (for example, solvent vs. non-solvent) and the intended processing duration (1/2/3 day), which supports consistent documentation across shifts and facilities.

Admin Setup: Configuring Processing Job Types in Metrc

Processing Job Types are the templates your facility uses to start Processing Jobs consistently. The facility’s Industry Administrator is automatically granted access to the Processing Job Type grid. Other users must be granted access through employee permissions by an Admin (or another user who can manage employee permissions).

Where to create Processing Job Types

In Metrc, navigate to the Admin section and open Processing Job Types, then add a new job type.

Required fields for a Processing Job Type

When creating a Processing Job Type, Metrc requires specific information that should align with your internal SOPs:

• Name: Use a clear, consistent name that matches how operators talk about the process (for example, “Ethanol Extraction – Crude”).
• Category: Select the OMC-configured category (Infusion or Extraction).
• Description: Add a plain-language summary of what the job type is for.
• Processing Steps: Enter the procedural steps (many operators copy relevant SOP steps here for standardized execution).
• Attributes: Select one or more OMC-configured attributes that describe the job type (for example, Solvent Extraction, 2 Day, Allergen as applicable).

Important limitation: once a Processing Job Type has been used to create any Processing Job, it can only be edited if it has not been used. Practically, this means you should treat Processing Job Types as controlled templates: validate the naming, category, attributes, and step text before deploying it to production.

Starting a Processing Job (Inputs and Start Date)

After Processing Job Types are created, authorized staff can start Processing Jobs. Metrc requires employees to have permission to manage Processing Jobs inventory, which must be granted via employee permissions.

Where to start a Processing Job

In Metrc, go to the Packages area and open Processing Jobs, then start a job from the Active view.

What you must record when starting the job

Starting a Processing Job is where traceability begins for the run. Metrc captures the job identity and the material being consumed from input packages.

• Processing Job Type: Choose from your previously configured types.
• Processing Job Name: Assign a job name that your team can reference (this job becomes the parent record for resulting production batches).
• Start Date: Record the date the processing begins.
• Input Packages: Add one or more packages used as inputs (searched/selected from active packages).
• Input Quantities and Unit of Measure: Record how much is used from each input package and confirm the correct unit of measure.

Day-to-day impact: accurate input selection and quantity entry reduces reconciliation issues later, especially when multiple departments (extraction, infusion, packaging, compliance) rely on the same batch history.

Correcting Mistakes: Adjusting Processing Job Inputs

If an error is discovered in the recorded inputs (wrong package selected, wrong quantity entered, or similar data entry issues), Metrc provides an Adjust function.

Key constraint: a Processing Job can only be adjusted if no packages have been created from that job. Once outputs exist, the job is effectively locked for input correction, so catching errors early matters.

How adjustments work in practice

When you adjust, Metrc requires:

• Reason: Selected from Metrc’s dropdown reasons.
• Note: A clarifying explanation to support auditability.
• Adjust Quantity: A positive number to add input quantity, or a negative number to subtract input quantity. Metrc automatically recalculates totals.

Operationally, this reinforces a best practice: review inputs immediately after job creation (same shift, same day) so corrections happen before downstream packaging.

Creating Packages (Production Batches) From a Processing Job

Once a Processing Job is underway or complete enough to generate outputs, you create new packages from the job. The bulletin explains that outputs that might previously have been represented as “Production Batch” packages should now be created directly from the Processing Job to accurately reflect what was produced.

What Metrc captures when creating packages from the job

When creating output packages, you will record:

• New Tag: The Metrc package tag for the newly created package.
• Location: Where the package will be physically stored.
• Item: The item being produced (your catalog item in Metrc).
• Quantity: The amount created into the new package.
• Note: Optional context (useful for internal batch notes).
• Production Batch No.: Your batch identifier for the output. If multiple batches come from the same processing job, each should have a distinct batch number/name.
• Package Date: The date the output package is created.
• Finish Processing Job: If you are done producing outputs from this job, you can finish it as part of the workflow.

Day-to-day impact: consistent Production Batch numbers and naming conventions make recalls, investigations, and internal quality reviews dramatically easier because teams can quickly link finished goods to source material and process records.

Using Processing Job Drilldowns for Audit-Ready Records

Metrc provides detailed job-level visibility so compliance teams can trace activity without piecing together multiple screens.

• Created Packages: Shows all output packages created from the job.
• Source Packages: Shows all input packages consumed by the job.
• History: Provides the full activity log for the job, supporting audits and internal investigations.

Operationally, this reduces time spent preparing for inspections because job-level documentation is centralized.

Finishing and Unfinishing Processing Jobs (Including Waste)

Finishing a Processing Job

Once a Processing Job has produced all intended output packages, the job should be marked Finished. The bulletin emphasizes that finishing includes recording the amount of material waste associated with the process (the byproduct or unusable material generated).

Day-to-day impact: finishing jobs promptly helps keep active work queues accurate, supports inventory reconciliation, and ensures waste is not left unrecorded (a common compliance risk area).

Unfinishing a Processing Job

If a Processing Job is finished in error, Metrc allows you to Unfinish it so you can make additional changes or create additional output packages as needed. Unfinishing is performed from the Inactive job view.

Operationally, this provides a controlled correction path when a job is closed prematurely, helping prevent inaccurate completion records.

Practical Implications for Kentucky Cannabis Operations

Kentucky operators should expect Processing Jobs to become part of routine production controls, not just “Metrc data entry.” To keep operations smooth and defensible:

• Standardize job names and batch numbers so Metrc records match floor language, SOPs, and QA documentation.
• Align Processing Job Types with SOP versions because job type edits may be restricted once used.
• Train by role (Admin vs. production vs. compliance) to avoid permission bottlenecks and prevent accidental mis-posting.
• Correct input mistakes early since adjustments are blocked after outputs are created.
• Close the loop with waste recording when finishing jobs to reduce inspection exposure and improve inventory accuracy.

Labeling and Retail ID Support (Distru Tools)

Processing Jobs improves production traceability, but operators still need accurate, compliant labels as packages move toward wholesale or retail readiness.

DistruLabels is a 100% free tool for creating compliant cannabis packaging and retail labels. It helps teams generate consistent labels and supports stronger Metrc Retail ID compliance by making it easier to keep label data aligned with what is recorded in Metrc.

For larger, multi-department operations that need end-to-end supply chain control, DistruERP is Distru’s comprehensive Cannabis ERP platform built for complete inventory, production, fulfillment, and operational management across the organization.

Official Metrc Resources for Help and Training

Metrc Support Portal

Metrc support is available at https://support.metrc.com. If you are accessing the portal for the first time, Metrc requires your username (created at login), state selection, facility license number, and a valid email to set a password.

Metrc Learn (Training)

Metrc Learn provides interactive training to improve system proficiency and workflow efficiency. You can access it directly at https://learn.metrc.com or from within Metrc via the Support menu by selecting “Sign up for Training.”

Metrc Expert (In-App Knowledge Base)

Within Metrc, the Metrc Expert widget provides step-by-step guides and knowledge base support for common tasks, including Processing Jobs navigation and actions.