Harvest Release and Package Creation Workflows: Why Cannabis ERP Genealogy Matters

Start with harvest records that downstream teams can trust

Harvest release should not be treated as a loose milestone. Operators need clear harvest identity, source plant or batch details, facility, room, owner, wet or dry weight details, status, release decision, and review history.

If harvest records are incomplete, package creation can push uncertainty into inventory, WMS, retail availability, wholesale fulfillment, and compliance-sensitive queues.

• Capture harvest ID, source details, facility, room, owner, status, and release decision.
• Keep hold, QA, quarantine, and release states visible before packages move downstream.
• Use owner assignment and approval gates for release exceptions.

Preserve package genealogy from creation forward

Package genealogy helps teams understand where a package came from, how it was created, which harvest or source material connects to it, and what happened before it reached inventory or retail workflows. This matters for investigation, inventory accuracy, and audit-friendly traceability.

• Link packages back to source harvest, batch, or material records where applicable.
• Track creation time, user, role, facility, reason, and package status.
• Keep split, merge, conversion, and movement history reviewable where the workflow requires it.

Link lab, COA, and package status before movement

Packages should not move into retail or wholesale availability without status awareness. Test passed, test failed, hold, quarantine, QA review, release, and COA visibility should remain tied to package records and downstream decisions.

• Show lab or COA details beside package status where available.
• Separate sellable, held, quarantined, staged, and released packages.
• Avoid hiding test or hold details inside notes that downstream teams may miss.

Prepare WMS and inventory handoff

Once packages are created or released, WMS and inventory teams need location, bin, custody, status, and movement history. A clean handoff helps receiving, putaway, cycle counts, transfer staging, fulfillment, and exception review use the same operating record.

• Assign location and custody history before packages enter active inventory workflows.
• Route WMS exceptions to review instead of overwriting package records informally.
• Keep package creation, location movement, and release decisions connected.

Use event queues and audit logs for sensitive work

Metrc-ready workflow support starts with internal data quality and reviewable decisions. Operators should be able to see pending, reviewed, failed, retried, or completed compliance-sensitive work while audit logs preserve who requested, approved, rejected, or executed each action.