Quick Start Guide

Canix New York Quick Start

Basic setup guide for New York operators using Canix with Metrc. Covers facility setup, package workflows, manifests, finished goods, and the first compliance checks to complete before daily operations.

Product: CanixAudience: Inventory leads, operations managers, and compliance coordinatorsEstimated Time: 20-35 min

Compliance Note

This guide is operational setup guidance, not legal advice. When package state, testing state, manifests, or traceability do not line up, pause movement and confirm the next step with your compliance lead.

1

1. Confirm the operating context before setup

Make sure the facility is working in the right New York license context before anyone starts building packages or transfers.

  • Confirm the exact facility, license, and operational role using Canix.
  • Decide who owns Canix administration, Metrc administration, and day-to-day inventory operations.
  • Make sure the team understands which actions still need to finish in Metrc even when the workflow starts in Canix.
  • Document who approves package corrections, transfer holds, and compliance escalations.
2

2. Verify package and inventory foundations

Package data issues get expensive quickly. Start with the inventory basics before daily use.

  • Confirm the correct package tag prefix is loaded for the facility before creating new packages.
  • Review whether the packages you are building should stay bulk/intermediate or be marked as finished goods.
  • If finished goods are being prepared for retail workflows, confirm the correct Retail Item IDs are available.
  • Teach users what Unverified, Needs Review, Transfer Pending, and Transfer Accepted mean so they do not force inventory actions on the wrong state.
3

3. Set up transfer and manifest habits early

Teams should learn the transfer handoff between Canix and Metrc before the first live shipment.

  • Build the transfer in Canix accurately, then register and print the manifest in Metrc before product leaves.
  • Keep a standard checklist for sender, receiver, transfer ID, manifest status, and receive status.
  • Train receivers to confirm the transfer state in Metrc before assuming inventory is editable in Canix.
  • Store the final manifest copy with the shipment record and internal operations log.
4

4. Build a simple daily review routine

A short daily review prevents most sync and package-state confusion from turning into bigger compliance problems.

  • Review recent package creations, edits, transfers, and receives at the beginning and end of the day.
  • Compare any high-risk package or transfer in both Canix and Metrc before taking corrective action.
  • Treat stale sync, wrong attribution, and status mismatches as same-day follow-up items.
  • Pause sell, relabel, or transfer activity on any package whose state is unclear.

Official Source Links

Related Download Assets

Related Support Tickets

Canix

Canix or Metrc Changes Are Not Syncing to the Other System

Troubleshoot stale Canix-to-Metrc or Metrc-to-Canix updates in New York cannabis operations before users duplicate inventory actions or move product on stale data.

Canix

Canix Package Availability Status Stays Unverified, Needs Review, or Transfer Pending

Interpret Canix availability statuses correctly in New York Metrc workflows so operators know when to wait, when to review data, and when to stop movement entirely.

Canix

Canix Finished Good Toggle or Retail Item ID Is Missing in New York

Fix New York retail-package issues in Canix when inventory should be marked as finished goods and tied to a Retail Item ID before compliant transfer or sale.

Canix

Canix Suggests the Wrong Package Tag Prefix for a New York License

Correct package-tag prefix issues in Canix so New York operators do not create inventory under the wrong package sequence after Metrc tag receipt.

Canix

Canix Transfer Exists but the Shipment Still Cannot Move

Handle New York transfer workflows that start in Canix but still require manifest registration or acceptance in Metrc before product can move or be received.

Canix

Canix Actions Show the Wrong Metrc User or API Key Owner

Resolve Canix-to-Metrc attribution issues so New York operators can tie inventory actions to the right employee and API key instead of an outdated admin account.

Canix

Canix Lab Result or COA Is Not Linked to the Final Package

Resolve package-level test-result mismatches before operators move product that appears to have testing complete in documents but not in the actual inventory record.

Canix

Canix Audit Trail Does Not Clearly Show Who Made the Inventory Change

Investigate package-history and attribution gaps before teams make corrective changes without a defensible audit trail in New York cannabis operations.

Reviewed

Last reviewed on May 11, 2026 by Tamem J, IT Solutions Engineer.

canixnew yorkmetrcinventorydispensaryprocessor