Changelog
Follow up on the latest improvements and updates.
RSS
Users are now able to update non-compliance fields (e.g., SKU) on Inactive Items without being required to re-enter missing compliance fields, as they could previously.

Related Important Note:
For Inactive Items that are transferred in from other facilities, where the Metrc Item Category requires binary files (such as Photos), WILL NOT have the binary files that were associated with the incoming transferred item be part of the transfer, per Metrc (by design), and you must populate those compliance fields with the respective binary data manually.Users of Canix who have integrated their QuickBooks Online account to Canix in Admin -> Integrations will be happier.

Previously if you wanted to associate your Canix account's Cannabis Items to one of your QBO Items you could not because Items lacked a field for QBO Item assignment (similar to Sage Product, LeafLink Product, and Dutchie Product).

To resolve this Canix has added a new column on
Admin -> Facility Data → Items Table
: QBO Product
so you can properly track and manage your items associated with your QuickBooks integration enabled Canix account.
[Standalone & Biotrack]
The new QBO Product
field can also be set/edited as part of the Items Bulk Uploader. Coming soon for Metrc-Integrated customer accounts.

Creating Production Batches from Templates just got more flexible.
The Challenge
Previously, when starting a batch from a template, output quantities were locked to the defaults. Adjusting for real-world variation meant editing each run individually—a slow, error-prone process.
The Solution
We’ve introduced an optional Multiplier field on the Create Batch page. With it, you can:
- Apply a single multiplier to instantly scale all output quantities defined in the template.
- Preview estimated inputs and outputs before finalizing.
How It Works
- Leave the field at 1 → outputs use template defaults.
- Enter a value greater than 1 → all outputs scale accordingly (e.g., Multiplier = 2 doubles every output).
- Make adjustments on the fly before saving.
The Impact
Save time, reduce errors, and ensure more accurate batch planning—while keeping the flexibility to edit runs afterward.

Canix now supports changing the strain assigned to existing Plant and Plant Batch records for Metrc-integrated customers. This update aligns Canix functionality with Metrc’s native capabilities, allowing users to modify strain assignments without recreating batches or plants.

# Details
- Users can now update/change strain values on existing Plant and Plant Batch records within Canix.
- When a strain change occurs, Metrc will automatically be updated via API sync to ensure data consistency.
- Existing workflows for strain assignment during: Plant creation, Plant Batch creation
NOTE:
Plant Batch splitting process remains unchanged, and you may still change strains while splitting.Applies only to Metrc-connected facilities.
Why this matters:
Previously, strain fields were locked post-creation, preventing users from aligning their Canix data with Metrc when strains changed. This improvement ensures full parity with Metrc functionality and streamlines corrections or updates to strain data.
To ensure Canix is providing relevant Lab Test Results URL to customers, we need to add the following test results fields from BT and make them available in Canix, and align to the appropriate fields on Harvests, Packages, Labels, and any other downstream objects where these fields are pertinent:
"CertOfAnalysisHyperlink": String, # ← URL to COA document (COA, if not already used)
"QualityControlDataHyperlink": String, # ← URL to QC data (Lab Test URL, if not already used)
"QualityControlResultsReceivedDate": String, # ← (NEW FIELD: timestamp of receipt from BT, or if supported: receipt from Confident Cannabis)
"CertOfAnalysisReceivedDate": String, # ← URL to QC data (NEW FIELD: timestamp of receipt from BT, or if supported: receipt from Confident Cannabis)
This is available in the Canix App's UI and in the REST APIs.
Canix now supports Application API keys from LeafLink to be entered in Canix.
Application API keys tie to a single LeafLink company, instead of using a user API key which links to all companies the user has access to.
Using an Application API key for the LeafLink integration helps shorten the list of LeafLink "default facilities" like Warehouse 01 and Facility 01 in the LeafLink Facility dropdown when sending inventory to LeafLink from Canix.
To use Application Keys to their greatest value, ensure that the relevant Canix Facilities are selected in the Canix Facilities select for each API key.

We’re excited to share that the Canix Shop is transitioning into a full retailer marketplace experience — designed to better connect you with licensed retailers and streamline order management.
This release is expected to be live mid-to-late November.
As part of this transition, password-protected shops will be turned off upon release (mid-to-late November). Instead, buyers and retailers will gain access through our new Canix Marketplace, where they can browse your shop, view product listings, and place orders directly.
What’s Changing
- Retailers will now need to apply for access to the Canix Marketplace.
- This application includes a simple vetting process similar to LeafLink, requiring license and tax documentation.
- Once approved, retailers will be able to log in, browse, and order from your shop within the marketplace.
What You Need to Do
Please share the link below with your retailers and buyers so they can apply for access:
We’ll handle the rest — verifying accounts and onboarding approved retailers to ensure a secure, compliant, and high-quality marketplace experience.
Thank you for being part of this next step in the Canix Shop journey. We’re thrilled to bring you a more connected, professional retail experience that helps your business grow.
If you have any questions about the transition, please reach out to your Canix representative or contact us at support@canix.com.

The Harvest Table was causing some customers frustration because they would have to spend time/clicks configuring the default sort to use Harvested Date [DESC].
We listened, and now the all three Harvest Table views (Active, Inactive, Unsubmitted) sort the harvests data using
Harvested Date
[DESC] by default.
We believe this will improve customer's experience with your Harvests in Canix.

Using the Canix REST API: GET Harvests
The Canix REST API supports sorting the result set, but it doesn't default to sorting by the harvest object's
date
property descending, here is an example API Request showing you how to set the GET Harvests (list of Harvest objects) to sort the API Response's ResultSet descending and limiting the number of results to twenty (20):curl -X 'GET' \
'https://api.canix.com/api/v1/harvests?limit=20&order_by=date%20desc' \
-H 'accept: application/json' \
-H 'X-API-KEY: {REPLACE_WITH_YOUR_CANIX_API_KEY}'
NOTE:
you'll need to set the X-API-Key
header value to be one of your company's API Keys for this API Request to execute successfully.Managing package tags just got easier. Canix now automatically pulls the lowest available Metrc tags and lets you apply them consecutively across splits, combines, manufacturing runs, harvests, and production batches.
You can also view your live Metrc tag inventory directly in Canix, so there’s no more switching between systems to find your next tag.
Check out this help center guide walking through the functionality in-depth.
This update ensures:
- Accurate, Metrc-verified tag selection
- Faster consecutive package creation
- Full visibility into your live tag inventory
Simplify your tagging process and keep every package perfectly aligned with Metrc — all from within Canix.
Currently, while users are viewing Packages, and they choose any Actions, the list of available actions is dependent on the columns/fields being visible on the Packages table BEFORE you click to view the Actions Menu.
In this fix, we've resolved this issue to ensure Package -> Actions are enabled and can be used regardless of the column/field visibility settings.

Load More
→