Subject:
Upcoming California Release and Configuration Changes
Bulletin Number:
CA-066
Distribution Date:
April 23, 2020
Effective Date:
May 1, 2020
Contact point:
api-info@metrc.com
Reason:
To provide third party integrators with advance notice of an upcoming release and configuration changes that could impact their software.
Hard copy of Bulletin:
Download PDF

We have an important update regarding configuration changes that impact the Metrc API program for the State of California.

Below is a summary of the changes that will take place on 5/1/2020:

  • Licensees will be unable to create a new package without a source package.
  • A new endpoint will be available to Cultivation licensees and Microbusinesses (authorized to engage in cultivation activities) to create packages of clones (cuttings and tissue cultures) from mother plants housed in plant batches.
  • A new endpoint will be available to Cultivation licensees and Microbusinesses (authorized to engage in cultivation activities) to create packages of clones (cuttings and tissue cultures) from mother plants moved to the flowering phase.
  • A new endpoint will be available to Cultivation licensees and Microbusinesses (authorized to engage in cultivation activities) to create a new plant batch from an existing plant batch.

Below is a summary of the changes that will take place on 6/1/2020:

• Licensees will be unable to create a new immature plant batch without a source plant or source package.


New Packages Require Source Package

Currently, when creating new packages, the recording of a contents package, sometimes referred to as a source package, is optional. When this change is implemented on 5/1/2020, a new package cannot be created without identifying the package(s) being pulled from to create the new package

Starting on 5/1/2020, the endpoint below will require an entry of one or more contents packages, labeled as Ingredients in the request, as highlighted in Figure 1 below.

• POST /packages/v1/create

Figure 1: Create Packages


New Immature Plant Batches Require Source Package or Source Plant

Currently, a new immature plant batch can be created without specifying the source of the immature plants. When this change is implemented on 6/1/2020, a new immature plant batch cannot be created without identifying the plant or package being used to create the planting.

Starting on 6/1/2020, an error will be generated if the endpoint below is initiated to create a planting.

• POST /plantbatches/v1/createplantings

Cultivators and Microbusinesses Only: Creating Packages of Clones

Mother plants may be tracked in either immature plant batches or individually as flowering plants. When clones (cuttings or tissue cultures) are taken from the mother plant, they may not immediately meet the regulatory definition of an immature plant. Allowing for packaging of the clones provides a tracking mechanism until the clones are mature enough for planting.

Starting on 5/1/2020, the following endpoints will be available to package clones taken from immature plant batches and flowering plants, as shown in Figure 2 and Figure 3 below.

  • POST /plantbatches/v1/createpackagesfrommother

POST /plants/v1/plantbatchpackage

Prior to using these endpoints, licensees may need to add new Items utilizing the “Clone – Cutting” or “Clone – Tissue Culture” Item Categories configured by the State.

The existing endpoint POST /packages/v1/create/plantings can be used to create new plant batches from the packages of clones created with the endpoints discussed above.

In addition, the existing endpoint to create packages of immature plants was renamed from POST /plantbatches/v1/createpackages to POST /plantbatches/v1/packageplantings.

Figure 2: Create Packages from Mother Plant in Plant Batch

Figure 3: Create Packages from Mother Plant in Flowering Phase

Some of the plants in an immature plant batch may have different lighting needs than the rest or it may be discovered that the original strain designation was incorrect for some on the plants in the batch.

Starting on 5/1/2020, the following endpoint will be available to ”split” one or more plants in an immature plant batch into a new immature plant batch, which can be assigned to a different location and/or a different strain, as shown in Figure 4 below:

• POST /plantbatches/v1/split

Figure 4: Split Immature Plant Batch

If you have questions about this bulletin, please contact Metrc support at api-info@metrc.com.


Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.