Understand the integration between Trym and Dutchie, the sync mechanics, see which actions to take and where, and review exceptions.

Index

• Integration Explained

• Sync Mechanic

  • Trym

  • Dutchie

• Compliance Actions & Where to Take Them

• Caveats and Exceptions

Integration Explained at a High Level

Once the integration is turned on, the vast majority of cultivation operations are handled in Trym. Relevant compliance actions will be reported to both METRC and Dutchie with the click of a button.

Customers can review their plant information in Dutchie, but plant actions taken in Dutchie will not be reported to METRC. Instead, Trym should be used for managing plants - Trym will update Dutchie when plants are edited.

After harvesting, every operation, from creating a package out of a harvest, to selling product to consumers, and everything in between, is handled in Dutchie. A full list of actions can be found in the Compliance Actions & Where to Take Them section of this document.

Sync Mechanic

Trym

When an event is reported to METRC, Trym will report the same event to Dutchie. New information originating from METRC will sync in and commit to Trym first and then be reported to Dutchie.

Due to limitations in METRC’s API, Available, Used, and Voided tags are not synchronized across the API. As a result, the METRC admin that accepts a new delivery of tags in METRC will have to spend approximately 30 seconds importing new tags into Trym. Tags will also be shared with Dutchie across the integration.

Dutchie

Dutchie synchronizes information to METRC instantly, as soon as they are completed in Dutchie.

With the Dutchie x Trym integration, mutual customers enjoy a bidirectional sync between Dutchie and METRC by virtue of Trym’s bidirectional integration.

Dutchie will also reference Trym’s database for the next available package tag when mutual customers create a package.

Compliance Actions & Where to Take Them

Caveats and Exceptions

• Where possible, users should use either Trym or Dutchie and avoid taking action directly in METRC if the action can be taken in either Trym or Dutchie. This is to ensure that there are no data discrepancies between the three systems.

• Plants that are destroyed in METRC will be synced to Trym but will not be reported to Dutchie. To create parity, the corresponding plant record in Dutchie should be retired through the Retire Plant function.

• Immature batch count adjustments are not currently supported, adjustments must be made in Dutchie first, and then METRC. The change will sync through to Trym from METRC.

• Rooms that are deleted in METRC will be synced to Trym but will not be reported to Dutchie. To create parity, the corresponding room should be deleted in Dutchie.

• Strains that are deleted in Trym or in METRC will be synced to Trym but will not be reported to Dutchie. To create parity, the corresponding strain should be deleted in Dutchie.

• Discontinuing a harvest in METRC will require creating a ticket with both the Trym and Dutchie support teams. Please exercise extra caution when harvesting in Trym to ensure the recorded information is correct before sending to METRC and Dutchie.

• Packages that are created, edited, adjusted, or discontinued in METRC will sync to Trym but not to Dutchie. However packages that are transferred to/from a license in METRC will reflect in Dutchie.

• New items, or changes to existing items, should be actioned in Dutchie.

• Manicure Harvests must be actioned in METRC and will then sync to Trym but will not sync to Dutchie.

• The strain, phase and room on the batch object in Dutchie will not necessarily be consistent with the plants it contains