AI Skill

Compliance

Cannabis Traceability Reconciliation

Find out why your physical count doesn't match Metrc or BioTrack.

Requirements
Works with
Works with Claude
Claude
Works with ChatGPT
ChatGPT
Needs
</>
Code execution
Built for
Cultivators, processors, distributors, vertically integrated operators
Find out why your physical count doesn't match Metrc or BioTrack.
i

This is a starting template. Change the questions, thresholds and output to fit how you work. AI can make mistakes, so check the output before you act on it. Report an issue

The problem it solves

Metrc says 14 packages, the vault has 12, and nobody knows which ones or why.

Upload your Metrc or BioTrack package export next to a physical count or ERP on-hand report. The skill matches every package by tag and tells you what's short, over, missing or probably mistyped, then explains the likely cause and ranks what to fix first.

Proposed adjustments are drafts for a human to sign off. The skill never submits anything to the state system and never suggests adjusting just to make the numbers agree.

Used by
Inventory managers, compliance managers and vault leads

What you'll need

Have these ready before you start.

  • Traceability package export as CSV, with the time it was pulled
  • Physical count sheet or ERP on-hand export as CSV, with the time it was pulled
  • State and license type
  • An AI assistant that can run Python, such as Claude

What the AI does

  • Shows the column mapping for you to confirm before it calculates
  • Matches packages by tag and converts pounds, grams and each
  • Sorts each package: short, over, not counted, not in the system, or likely tag typo
  • Explains the probable cause of each variance
  • Drafts corrective actions for sign-off without inventing state adjustment reasons or deadlines

What you get

A discrepancy report with a jurisdiction block, a variance table, draft actions and a sign-off line. In a sample Michigan run comparing 12 packages, 3 matched. Net variance was minus 23.8 g, traced to moisture loss on two bulk flower packages that needed a re-weigh. Gummies came in 12 units over and were flagged high priority, and one rosin package was flagged as a likely typo on the count sheet.

Better with Distru

Distru keeps package-level inventory next to your Metrc data and syncs when you tell it to, so reconciliation becomes the exception instead of a monthly project.

See the Distru MCP

Frequently Asked Questions

Let’s answer the most commonly asked questions about Cannabis Software.

How do I reconcile Metrc with a physical count?

Upload the Metrc or BioTrack package export and your count sheet or ERP on-hand report as CSVs, with the time each was pulled. The skill matches packages by tag, converts units and sorts each one into short, over, not counted, not in the system or probable tag typo.

Does it submit adjustments to Metrc?

No. Proposed adjustments are drafts for a person to sign off. It never submits to the state system, never invents adjustment reasons or deadlines, and never suggests adjusting just to make the numbers match.

How does it explain each variance?

It gives a likely cause and ranks what to fix first. In a sample Michigan run, two short bulk flower packages pointed to moisture loss and a re-weigh, and 12 extra gummies got flagged high priority.

When should I run a traceability reconciliation?

Month-end, before an audit or inspection, or anytime the count and the system don't match. You'll need an AI assistant that can run Python for the bundled calculator.