METRC PACKAGE TAG MANAGEMENT PART 2: BATCH TAGGING VS SERIALIZATION

These resources will help you understand this post “Serialization vs. Batch Tagging Part 2”

• Serialization Vs. Batch Tagging Part 1

• RMCC’s Track & Trace Administration Certification

• RMCC Blog: The Most Common METRC Transition Challenges Across The Supply-Chain

---

strategizing metrc package tag management is one of the first decisions an operation needs to make while implementing metrc.

And there is no one size fits all when managing your METRC inventory by package tag.

First, let’s define our language.

View fullsize

the definitions are important to understand the flow in the hierarchy chart below.

Pallet, Master Case, and Case can be referred to as a Parent METRC Package Tag, Child METRC Package Tag, and Grandchild METRC Package Tag, respectively. The Parent vs Child METRC Package Tag management is referring to the creation of METRC Package Tags from the source package. Pulling from a source (or “Parent”) METRC Package Tag ensures inventory is deducted from the Parent Tag and moved into the Child Tag. If inventory is not pulled from the Parent Tag, the user has created “Ghost Weight” resulting in duplicate virtual records. Ghost Weight is an RMCC definition that identifies when virtual records are recorded in METRC, however, not physically in the licensed premise.

View fullsize

impacts of the operational differences between batch vs serialized metrc inventory:

Dependent on when the Certificate of Analysis (COA) is issued by the lab will determine when the most efficient time will be to move to serialization inventory. While distributing inventory, it is RMCC’s best practice to move to a serialization workflow. 

View fullsize

“Currently, do I have a master case and individual case levels? Or will orders be picked at the time of the sales order?

Is one batch of inventory located in multiple areas in the warehouse?

What endpoints is my third party software solution utilizing within METRC? ”

— Questions every Operator should be asking themselves prior to Implementation

rmcc is in favor of serialization workflows for the following reasons:

1. Rejection Workflows Between Licensed Cannabis Businesses: During a shipment to a retailer, five cases of Wyld Huckleberry 100mg Gummies are recorded under one METRC package tag. However, only two cases physically arrive in the shipment. The Retailer would need to reject the entire package containing five cases and send the shipment back to the originating licensee to be corrected in METRC and re-shipped. Instead, if the cases were serialized with a 1:1 ratio between physical case to METRC Package Tag, the Retailer would be able to compliantly “accept” the two physical cases of Wyld Huckleberry 100mg Gummies and “reject” the remaining three cases virtually recorded on the manifest.  

2. METRC Package Tags are to accompany physical inventory at all times: Immature regulated cannabis markets that are new to METRC are usually unaware the physical METRC Package Tag is to be with the inventory at all times. RMCC has seen every mature regulated METRC state adapt their regulations to ensure more accuracy in traceability through serialization METRC Package Tag management. If inventory is recorded under one METRC Package Tag, however, physically placed in multiple separate locations in the warehouse, the user should transition from batch tagging to serialization by Pallet or Master Case immediately to ensure compliance. 

3. Save Labor Cost on Reconciles: RMCC has found physical inventory reconciliation is quickest when each Pallet, Master Case, or Case has a 1:1 ratio between METRC and physical inventory. 

4. Streamline Manifest Creation: Managing METRC by serialization increases efficiency while building manifests. Managing inventory by batch requires the user to create a new Child Package prior to each manifest creation causing an internal bottleneck in the operation.