METRC best practices

Modified on Sun, 26 Jun 2022 at 10:08 PM

We've compiled a list of best practices for METRC. These best practices are helpful for not only optimizing and getting the most out of your reports in Broadleaf, but also for your own clarity when reviewing METRC directly. 


Finishing harvest batches

Per METR guidelines, when all packages have been created from a harvest batch and no physical material remains, the batch should be "finished" in METRC, which will zero out the remaining weight on the harvest batch as "waterloss". This is an important part of maintaining the data integrity of METRC, but also an important element for reports within Appature

Logging waterloss

METRC will automatically log waterloss on a harvest batch if you finish the batch with weight left on the batch. Users should only log physical waste, and then let METRC automatically log their waterloss, instead of manually logging the waterloss as physical waste. 

Location names

If you have multiple licenses under the same physical building, you already know that you need to recreate each room under each license. Ensure that your rooms:

  • Have the same name under each license
    • Ex: Calling each room "Flower Room 4" instead of "Flower 4" and "Flower Rm #4"
    • This helps ensure there are no entry errors and allows us to coalesce data from multiple licenses into a single physical location
  • Make sure each name is descriptive
    • Ex: "Bulk storage 1" instead of "General room 1"
    • Helps easily identify when something is not where it should be
  • If you expand, use the same naming convention
    • Ex: your current facility has "Flower 1", "Flower 2" and "Flower 3" you build a new facility that will have 3 additional flower rooms.
      • Instead of naming the new flower rooms "Flower 1", "Flower 2", and "Flower 3", name them "Flower 4", "Flower 5", and "Flower 6"
      • If you want to use "Flower 1/2/3", add additional words to make it clear where they are located. Ex: "Flower 1 - Building 1", "Flower 1 - Building 2", etc

Strain Names

Just like locations, if you plan to grow the same strain under multiple licenses, you need to recreate the strain under every license. Ensure each strain:

  • Has the same name under each license
    • Unless the strain truly is a new phenotype, use the EXACT same name
    • Ex: Do not call it "GG4" under one license and "Gorilla Glue" under another, UNLESS you are treating them as truly separate strains. Otherwise, use the same name "GG4" and "GG4" under both licenses
  • Deactivate strains and phenos you are no longer growing
    • Broadleaf will still pull data on deactivated strains, and your active strain list should only consist of strains that you are actively growing or will be growing again in the near future

Item Names

Just like locations and strains, items must be recreated under each license. Ensure that each item:

  • Has the same name under each license
    • Consistency is key! Avoid examples like: "Sour Diesel - bulk flower" under one license and "Sour Diesel - flower bulk"
  • Create a naming convention
    • Typically organizations will have some combination of "Strain", "quantity" and and "Item type"
    • Whatever you use, use it consistently, and in the same order
    • Example of what not to do:"Kush mints - buds - bulk" and "Kush mints - ounces - kolas"
      • Even though these are two different items, they follow different patterns. The first is "strain - item type - quantity" and the second is "strain - quantity - item type"
  • Deactivate items no longer used
    • Whether its items for strains no longer grown, or a product or item for a strain you no longer offer, deactivate unneeded items

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article