Cultivation Specific Package Actions

Glossary

Prerequisites & Setup

Step-by-Step Instructions

Important Considerations

System Impacts & Dependencies

Overview: Why We Use This Feature

Canix offers a variety of Package Creation actions that produce new tagged inventory and send that data directly to Metrc, or record it natively in Standalone states. The process is mostly the same between Metrc and Non-Metrc submissions, unique differences will be called out in the documentation.

By creating packages in Canix you can take advantage of the fastest way to find or scan source packages and submit data, as well as optionally add non-compliance data that is important for your operation like COGS and Internal Lot IDs. These actions are all written to a detailed Activity History that covers all updates to a given Package over time, and package lineage is preserved from source to child package.

Split Packages: In Canix, similar to other seed to sale systems, splitting a package means one of two things. First, breaking a package down into smaller package(s) of the same item as the source. This is used when, for example, taking a package of bulk flower and splitting it up into one or multiple, smaller packages of that same item, bulk flower. The second is taking the source package and changing it into a different item(s) with a new package tag. This function has a ton of flexibility to create multiple new packages with the same new item as well as creating multiple new packages all with different items. A simple example of this would be taking a package of bulk flower and splitting it into your A's, B's, smalls and trim packages. You could then use the same function to split your package of A buds into your final packed 8ths.

Combine Packages: When you have 2 or more Packages that need to be combined together down to a single Package or multiple new Packages, use Canix's Combine Packages feature to consolidate them into a "Compound Package".

Create Testing Packages: Once your product is ready for testing, you'll create Testing Packages to send to the Lab. This uses Split Packages but requires carefully marking the new Package as a "Testing Package" during creation; this step is required in order for your Testing Packages to be added to a Lab Transfer.

Create a Package from Untracked Item: This feature can be used by non-Metrc customers to easily create new Packages in your inventory without specifying a Source Harvest or external Source Facility. This action is specific to non-Metrc customers only, as Metrc states will require a defined source for all new Packages.

Glossary

• Package: A tagged unit of tracked inventory in Canix and, where applicable, in Metrc.
• Package Tag: The unique tag identifier assigned to a Package.
• Item: The product definition (Item Name, Item Type, Strain) associated with a Package.
• Metrc: The state-mandated seed-to-sale traceability system that Canix syncs with in certain states.
• Standalone: A facility that is not integrated with Metrc.
• Source Package: The existing Package whose contents are pulled to create one or more new Packages.
• Child Package: A new Package created from a Source Package during a Split or Combine.
• Compound Package: The new Package created when two or more Source Packages are combined together.
• Untracked Item: A Package created without a Source Harvest or external Source Facility. Available to non-Metrc facilities only.
• Testing Package: A Package created solely to submit for testing. This designation is required for the Package to be added to a Lab Transfer.
• Required Tests: The testing option that must be selected on a Testing Package in states that require a test reason (MI, OK, MO, and NV).
• Lab Transfer: The transfer used to send Testing Packages to a lab.
• Packaged Weight and Units: The weight and unit being pulled from the Source Package to create the new Package(s); this is the amount of each new Package, not the total pulled.
• Pulled Weight: The amount being taken out of the Source Package. Optional when the source and child package units match; used to account for changes in Unit of Measurement when splitting into a different item type.
• Pulled Source Quantity: On the Combine Packages screen, the amount taken from each Source Package. Defaults to the full contents of each Package.
• Per Package Quantity: The quantity applied to each new Package when creating multiple new Packages of the same size.
• Number of Packages: The number of new Package(s) being created, each at the Packaged Weight entered.
• Unit of Measure (UOM): The measurement basis assigned to an Item. Canix restricts the UOM to weight, volume, or count-based depending on the item.
• Production Batch: A Metrc-only value that affects package lineage and test results. Left blank, the child package inherits the Source Package's production batch.
• Test Lineage: The inherited testing history passed from a Source Package to a child package via the production batch.
• Finish Source Package: The option to finish a Source Package once its contents have been fully depleted by the new Package(s).
• COGS (Cost of Goods Sold): The tracked cost associated with a package, optionally entered per package for Reporting.
• Internal Lot ID: An optional free-form Lot ID in Canix only, used to track process from seed to sale in Reporting.
• Non-Cannabis Inputs: Non-cannabis inputs from Bills of Materials that are pulled and applied to output packages during a Split or Combine.
• View: Active / View: Finished: The saved views on the Packages table used to display active versus finished/deactivated inventory.
• Activity History: The per-package log of changes, used to track adjustments, item changes, and other package events.
• Metrc Submissions / User Submissions: The Canix pages used to review or check the status of submissions. Metrc facilities use Metrc Submissions; non-Metrc facilities use User Submissions.

Prerequisites & Setup

Before beginning, ensure the following requirements are met:

• Permissions: the following permissions control Package Creation actions and are located in Admin & Settings > Permission Groups > [Group Name] > Action Permissions > Inventory > Packages:
  • Split Packages
    • This permission controls Create Testing Packages as well, since Testing Packages are created through the Split Package flow
  • Combine Packages
  • Create Packages
    • This permission controls Create Package from Untracked Item
• Necessary Data:
  • Active Packages in Inventory > Packages > View: Active to act as Source Packages for Split, Combine, and Create Testing Packages.
  • Available Package Tags in your facility.
  • Existing Locations, Items, and Strains configured for your facility.
  • Bills of Materials configured, if non-cannabis inputs will be pulled into the output packages.
  • Non-Metrc facilities only: access to Create a Package from Untracked Item, as Metrc states require a defined source for all new Packages.

Step-by-Step Instructions for Each Action

Split Packages

• Important Considerations
• Step by Step Instructions
• Troubleshooting

Important Considerations for Split Packages

These "pro-tips" and warnings help avoid common pitfalls:

• Field requirement: Packaged Date, Location, Packaged Weight and Units, and Number of Packages must be completed for each new Package.
• Field requirement: Start Tag auto-populates with the next available tag; you can always manually enter or scan a different tag.
• Logic constraint: Finish Source Package can only be selected after all new Package details are completed.
• Logic constraint: Production Batch is optional and for Metrc facilities only — you must leave this field blank to inherit the same Production Batch as the Source Package.
• Logic constraint: Do not select Testing Package if the Package is not being submitted for testing, or it will no longer be able to be transferred for sale.
• Logic constraint: When splitting into a different item, Pulled Weight is optional if the source package unit is the same as the child package unit. If left blank, Canix pulls the same weight out of the source package that is entered in the packaged weight field.
• Logic constraint: Canix will restrict the UOM to either weight, volume, or count-based, depending on what UOM is assigned to the item.
• Best practice: Be sure you are not pulling more weight than what's available in the source package. The line below the Number of Packages field provides a breakdown of the max number of packages that can be created from the Source Package with the weight specified.
• Best practice: If you pull all of the weight out of the source package, be sure to click finish package to save yourself a step.

Step by Step Instructions for Split Packages

Follow these steps or watch the demo video to complete each workflow.

1. Navigate to Inventory > Packages > View: Active
2. Use the filters to narrow down your search (by Tag, Item Name, Item Type, Strain, Location, etc.)
3. Once filtered, select the Source Package(s) you want to split into new Package(s)
   • Note: See our article on Continuous Scanning for Package and Plant Inventory to find out how to scan the tags you'd like to take action on.
4. Select Actions > Split Package(s)
5. Complete all required fields:
   • Source Package will auto-fill showing Source Package details
   • Start Tag: This will auto-populate with the next available tag, you can always manually enter or scan a different tag
   • Packaged Date
   • Expiration Date: Optional date the new Package(s) must be sold/used by
   • Package Locations: Apply the same location/room for the new Package(s)
   • Finish Source Package: Select this option if you are depleting the entire contents of the Source Package, leaving a remaining weight of zero, and wish to Finish Package once completed; this option can only be selected after all new Package details are completed in the next set of steps
6. On the right side of the screen, click on the blue hyperlink of the Item Name
7. Complete all required fields:
   • Tag: If different from what is prefilled, scan or manually edit the last few numbers for a new tag
   • Use Same Item (as source package): Check this box to use the same Item and Strain as the Source Package
     • To use a different Item, uncheck this box and search for the new Item to be used — this workflow is covered in the section below
   • Production Batch: Optional and for Metrc facilities only, you must leave this field blank to inherit the same Production Batch as the Source Package
     • To change it, a new production Batch number can be entered
   • Location: This will auto-populate with the Package Location that has been applied to all packages, or if each package will be in a different location select a new location
   • Testing Package: Select this option if this Package is solely created to submit for testing
     • Do not select this option if this Package is not being submitted for testing, or it will no longer be able to be transferred for sale
   • Packaged Weight and Units: The weight and unit being pulled from the Source Package to create the new Package(s); this will be the amount of each new Package, not the total Pulled
   • Number of Packages: Enter the number of new Package(s) each being created with the Packaged Weight
     • The line below this text box will provide a breakdown of the max number of packages that can be created from the Source Package with the weight specified
   • Cost of Goods Sold (COGS) per package: Optional Cost of Goods for Reporting
   • Internal Lot ID: Optional Lot ID (Canix only) to track process from seed to sale in Reporting
8. Verify everything looks correct
9. Select Update
10. If your new Package(s) will deplete the total contents of the Source Package and leave it with a quantity of zero, you can now select Finish Source Package
    • If selected, enter a Finish Date
11. The new Package's details will be displayed under the line item; if you would like to add an additional new Package to split the Source Package into, select Add Item in the top right corner
12. If you'd like to simultaneously split an additional Source Package into new Packages, select + Add Package from the top right corner of the page and repeat the same steps
13. Once finished, verify everything looks correct
14. Select Submit
15. View Packages. Navigate to Inventory > Packages > View: Active

Split Package into a Different Item

1. From the split package page, select the blue Item Name text
2. Deselect the "Use Same Item" option
   • If unchecked, Canix defaults to searching for items with strains that match the item on the source package. You can toggle to "All Items" to search across all of your active items in Canix.
3. Start typing the item you are creating and select it from the drop down
4. Fill in all of the required and desired optional fields as the instructions explain above
5. You will now see a pulled weight field available when changing the item, allowing you to account for changes in the Unit of Measurement when splitting into a different item type
   • Pulled Weight is the amount you are taking out of the source package
   • This is an optional field if the source package unit is the same as the child package unit (i.e. Grams)
   • If left blank, Canix pulls the same weight out of the source package that is entered in the packaged weight field
   • Generally these weights match when working within similar item types. Example: Packaging 8ths from Bulk Flower — we pulled the same weight/amount out of the source package that is going to be packaged into the new child package(s)
   • This weight may be different than the packaged weight when changing item types. Example: Splitting Bulk Flower into Bulk Concentrate — the weight of the flower we used for the extraction process is different from the weight of the Bulk Concentrate package we are creating
   • The new package might also be a different unit of measurement. Canix will restrict the UOM to either weight, volume, or count-based, depending on what UOM is assigned to the item
6. Verify everything looks correct
7. Select Update

You now have the opportunity to create additional packages from the source. These additional packages can either match the item we just created, the source package, or a completely new item.

Non-Cannabis Inputs Tab

The Split Package page also gives visibility into any non-cannabis inputs from Bills of Materials that will be used on the output packages being created. When any non-cannabis inputs are pulled during a package split, the "Non-Cannabis Inputs" tab will be enabled and will show the quantity required, and the quantity that will be applied.

Track Submissions

Track Split Packages from your Submissions page in the Canix Web Application.

• Metrc Facilities: Navigate to Admin > Metrc Submissions > All to review or check the status of your submissions to Metrc. If the submission status is Failed, click on the submission name to see the Metrc error message.
• Non-Metrc Facilities: Navigate to Admin > User Submissions > All

Troubleshooting for Split Packages

If you encounter an error, check these common scenarios before contacting support.

• You've pulled more weight than the source package holds. Be sure you are not pulling more weight than what's available in the source package. The line below the Number of Packages field provides a breakdown of the max number of packages that can be created with the weight specified.
• The new package can no longer be transferred for sale. The Testing Package option was selected. Do not select this option if the Package is not being submitted for testing.
• The test lineage changed unexpectedly. Production Batch is Metrc facilities only and must be left blank to inherit the same Production Batch as the Source Package.
• You can't find the item when splitting into a different item. Canix defaults to searching for items with strains that match the item on the source package. Toggle to "All Items" to search across all of your active items in Canix.
• The source package still shows a remaining quantity. If your new Packages deplete the total contents of the Source Package, select Finish Source Package and enter a Finish Date. This option can only be selected after all new Package details are completed.
• The unit of measure isn't what you expected. Canix restricts the UOM to either weight, volume, or count-based, depending on what UOM is assigned to the item.
• The submission failed. Navigate to Admin > Metrc Submissions > All; if the submission status is Failed, click on the submission name to see the Metrc error message.

Combine Packages

• Important Considerations
• Step by Step Instructions
• Troubleshooting

Important Considerations for Combine Packages

These "pro-tips" and warnings help avoid common pitfalls:

• Field requirement: Two or more Packages must be selected before the Combine Packages action can be used.
• Field requirement: Starting Package Tag, Packaged Date, and Location must be completed for the newly created Package.
• Logic constraint: The Combine screen defaults to pulling all contents of each Package. If you wish to only use part of the Package contents, update the amount listed in Pulled Source Quantity.
• Logic constraint: Per Package Quantity only applies when simultaneously creating multiple new Packages of the same size from the Source Packages; if left blank, it will automatically split the Source Package contents equally between all new Packages.
• Logic constraint: If all source packages have the same production batch, you can leave the child package production batch blank to receive the same test lineage from the sources.
• Logic constraint — WARNING: production batches are case sensitive and must be entered exactly as on the source package to retain the same test lineage.
• Logic constraint: The Finish Package toggle is only enabled when the Remaining Quantity After Combine for the Source Packages is equal to 0.
• Best practice: Review your selection to confirm accuracy before selecting Actions > Combine Packages.
• Best practice: If you are using a different Item than the Source which also has a different Unit of Measure, calculate the change in Quantity per Units before submitting.

Step by Step Instructions for Combine Packages

Follow these steps or watch the demo video to complete each workflow.

1. Navigate to Inventory Management > Cannabis Inventory > View: Active
2. Use the filters to narrow down your search (by Tag, Item Name, Item Type, Strain, Location, etc.)
3. Once filtered, check the boxes next to two or more Packages to select them
   • To select multiple consecutive Packages, check the box of the first one then hold shift when selecting the last one
   • Also see our article on Continuous Scanning for Package and Plant Inventory to find out how to scan the tags you'd like to take action on
4. Review your selection to confirm accuracy
5. Select Actions > Combine Packages

6. On the next screen, you will see all Source Package details first — this will default to pulling all contents of each Package
   • If you wish to only use part of the Package contents, update the amount listed in Pulled Source Quantity
   • Select Add Source Package if you need to add another Package to be combined

7. Scroll down and complete all required fields for the newly created Package:
   • Starting Package Tag: This will auto-populate with the next available tag
   • Number of Packages: If you wish to simultaneously create multiple new Packages of the same size from the Source Packages, enter the total number of Packages to create here
   • Use same item as source packages: Check this box to use the same Item as the Source
   • Item: To use a different Item, leave the box above unchecked and select a new Item here
     • If you are using a different Item than the Source which also has a different Unit of Measure, calculate the change in Quantity per Units here
   • Per Package Quantity: This field only applies when simultaneously creating multiple new Packages of the same size from the Source Packages; if left blank, it will automatically split the Source Package contents equally between all new Packages
     • Units: If using the field above to create multiple new Packages, enter Unit of Measure
   • Packaged Date
   • Expiration Date: Optional date the new Package(s) must be sold/used by
   • Location: Of the new Package(s)
   • Production Batch: Optional and for Metrc facilities only, enter a Production Batch if needed
     • If all source packages have the same production batch, you can leave the child package production batch blank to receive the same test lineage from the sources
     • If you enter the same production batch on the child package as the source package, the test lineage will remain the same and the child package will not be considered a new production batch
     • WARNING: production batches are case sensitive and must be entered exactly as on the source package to retain the same test lineage
   • Internal Lot ID: Optional Lot ID (Canix only) to track process from seed to sale in Reporting
   • Per Package COGS: Optional Cost of Goods for Reporting

8. Verify everything looks correct
9. Select Submit
10. View Packages. Navigate to Inventory > Packages > View: Active

Finish Packages During Combine

Packages can be finished during the Combine Package action. When the Remaining Quantity After Combine quantity for the Source Packages is equal to 0, the Finish Package toggle will be enabled. When checked, the Finish Date will prefill with today's date but can be edited. Upon submission, the packages will be combined and the packages delineated to be finished will be finished.

Non-Cannabis Inputs Tab

The Combine Package page also gives visibility into any non-cannabis inputs from Bills of Materials that will be used on the output packages being created. When any non-cannabis inputs are pulled during a package combination, the "Non-Cannabis Inputs" tab will be enabled and will show the quantity required, and the quantity that will be applied.

Track Submissions

Track Combined (Compound) Packages from your Submissions page in the Canix Web Application.

• Metrc Facilities: Navigate to Admin > Metrc Submissions > All to review or check the status of your submissions to Metrc. If the submission status is Failed, click on the submission name to see the Metrc error message.
• Non-Metrc Facilities: Navigate to Admin > User Submissions > All

Troubleshooting for Combine Packages

If you encounter an error, check these common scenarios before contacting support.

• The Combine Packages action isn't available. Two or more Packages must be selected to combine them into a Compound Package.
• The test lineage changed unexpectedly. Production batches are case sensitive and must be entered exactly as on the source package to retain the same test lineage. If all source packages share the same production batch, leave the child package production batch blank instead.
• The new packages are the wrong size. Per Package Quantity only applies when simultaneously creating multiple new Packages of the same size. If left blank, Canix splits the Source Package contents equally between all new Packages.
• You only want to use part of a source package. Update the amount listed in Pulled Source Quantity — the screen defaults to pulling all contents of each Package.
• The Finish Package toggle is unavailable. It is only enabled when the Remaining Quantity After Combine for the Source Packages equals 0.
• The quantities don't line up after changing the Item. If the new Item has a different Unit of Measure than the Source, calculate the change in Quantity per Units before submitting.
• The submission failed. Navigate to Admin > Metrc Submissions > All; if the submission status is Failed, click on the submission name to see the Metrc error message.

Create Testing Packages

• Important Considerations
• Step by Step Instructions
• Troubleshooting

Important Considerations for Create Testing Packages

These "pro-tips" and warnings help avoid common pitfalls:

• Field requirement: The Testing Package box must be checked. This option must be enabled to allow the Package to be added to a Lab Transfer.
• Field requirement: For MI, OK, MO, and NV, you must select a testing option from the Required Tests dropdown menu.
• Logic constraint: Creating Testing Packages uses the Split Packages flow, so the same fields and constraints apply.
• Logic constraint: If your state requires a "Required Test" reason to be entered for each Testing Package created, Canix will require a reason to be selected when creating a Testing Package.
• Logic constraint: Production Batch is optional and for Metrc facilities only — you must leave this field blank to inherit the same Production Batch as the Source Package.
• Logic constraint: Finish Source Package typically does not apply when creating Testing Packages.
• Best practice: Keep Use Same Item checked to use the same Item and Strain as the Source Package.
• Best practice: Typically a single Testing Package is created from each Source Package, but regulations may vary by state.
• Best practice: Confirm the Testing Package box is checked before submitting, since this is the step that makes the Package eligible for a Lab Transfer.

Step by Step Instructions for Create Testing Packages

Follow these steps or watch the demo video to complete each workflow.

1. Navigate to Inventory > Packages > View: Active
2. Use the filters to narrow down your search (by Tag, Item Name, Item Type, Strain, Location, etc.)
3. Once filtered, select the Source Package(s) you will be using to create new Testing Packages
   • You can also select multiple Source Packages to create multiple Testing Packages at once
4. Select Actions > Split Package(s)
5. First, on the left side of the screen, complete all required fields:
   • Source Package: This will auto-fill showing Source Package details
   • Start Tag: This will auto-populate with the next available tag
   • Packaged Date: Typically today's date
   • Expiration Date: Optional
   • Location: Current location of the new Package
   • Finish Source Package: This option typically does not apply when creating Testing Packages
6. On the right side of the screen, click on the blue hyperlink of the Item Name
7. Complete all required fields:
   • Tag: This will auto-populate with the next available tag
   • Use Same Item (as source package): Keep this box checked to use the same Item and Strain as the Source Package
   • Production Batch: Optional and for Metrc facilities only, you must leave this field blank to inherit the same Production Batch as the Source Package
   • Testing Package: Check the box to enable this option and mark this as a Testing Package
     • This option must be enabled to allow the Package to be added to a Lab Transfer
     • For MI, OK, MO, and NV, you must select a testing option from the Required Tests dropdown menu
   • Packaged Weight and Units: The weight and unit being pulled from the Source Package to create the new Package(s); this will be the amount of each new Package, not the total Pulled
   • Number of Packages: Typically a single Testing Package is created from each Source Package, but regulations may vary by state
   • Cost of Goods Sold (COGS) per package: Optional
   • Internal Lot ID: Optional Lot ID (Canix only)
8. Confirm the Testing Package box is checked to ensure the new Package is marked for Testing
9. Verify everything looks correct
10. Select Update
11. The new Package's details will be displayed under the line item
    • If you need to create an additional new Package to split the same Source Package into, select Add Item in the top right corner
12. If you'd like to simultaneously split another different Source Package into new Packages, select + Add Package from the top right corner of the page and repeat the same steps
13. If you are splitting multiple Packages, be sure to scroll down to complete the steps for each one
14. Once finished, verify everything looks correct
15. Select Submit
16. View Testing Packages. Navigate to Inventory > Packages > View: Active. On the table, scroll to the right to find the Is Testing Package? column and click the filter icon; check the box for Yes and select Apply

Metrc Facilities — Required Test Reasons

If your state requires a "Required Test" reason to be entered for each Testing Package created, Canix will require a reason to be selected when creating a Testing Package.

Track Submissions

Track new Packages from your Metrc Submissions page in the Canix Web Application.

• Navigate to Admin > Metrc Submissions > All to review or check the status of your submissions to Metrc. If the submission status is Failed, click on the submission name to see the Metrc error message.

Troubleshooting for Create Testing Packages

If you encounter an error, check these common scenarios before contacting support.

• The Testing Package can't be added to a Lab Transfer. The Testing Package option must be enabled during creation. Without it, the Package is not eligible for a Lab Transfer.
• The submission is blocked by a Required Tests field. For MI, OK, MO, and NV, you must select a testing option from the Required Tests dropdown menu. If your state requires a "Required Test" reason, Canix will require a reason to be selected.
• You can't find your Testing Packages. Navigate to Inventory > Packages > View: Active, scroll right to the Is Testing Package? column, click the filter icon, check the box for Yes, and select Apply.
• The test lineage changed unexpectedly. Production Batch is Metrc facilities only and must be left blank to inherit the same Production Batch as the Source Package.
• The Item or Strain on the Testing Package is wrong. Keep Use Same Item checked to use the same Item and Strain as the Source Package.
• The submission failed. Navigate to Admin > Metrc Submissions > All; if the submission status is Failed, click on the submission name to see the Metrc error message.

Create a Package from Untracked Item

• Important Considerations
• Step by Step Instructions
• Troubleshooting

Important Considerations for Create a Package from Untracked Item

These "pro-tips" and warnings help avoid common pitfalls:

• Availability: This action is specific to non-Metrc customers only, as Metrc states will require a defined source for all new Packages.
• Field requirements: New Package Tag, Item, Location, Packaging Date, and Weight and Units are required. Production Batch Number, Internal Lot ID, and Owner are optional.
• Logic constraint: Only enable Testing Package if the Package is being submitted for testing now.
• Best practice: If you instead wish to create Package(s) with a Source Harvest or external Source Facility, use Accept Incoming Transfers, Create a Single Package from a Harvest, or Create Multiple Packages from a Harvest.
• Best practice: Use the optional Internal Lot ID to track process from seed to sale in Reporting.

Step by Step Instructions for Create a Package from Untracked Item

Follow these steps or watch the demo video to complete each workflow.

1. Navigate to Inventory > Packages > Active
2. Select Actions > + Create Package > From Untracked Item
3. Complete all required fields:
   • New Package Tag: This will auto-populate with the next available tag
   • Item: Select the Item to be used on the new Package or create a new one
   • Location: Room for the new Package
   • Packaging Date
   • Weight and Units: Enter the weight and units for the new Package
   • Testing Package: Only enable this if the Package is being submitted for testing now
   • Production Batch Number: Optional
   • Internal Lot ID: Optional Lot ID to track process from seed to sale in Reporting
   • Owner: Optional field to specify a Canix User to be the Package Owner
4. Verify everything looks correct
5. Select Create
6. View Packages. Navigate to Inventory > Packages > View: Active

Track Submissions

Track Create a Package from Untracked Item from your Submissions page in the Canix Web Application.

• Navigate to Admin > User Submissions > All

Troubleshooting for Create a Package from Untracked Item

If you encounter an error, check these common scenarios before contacting support.

• The From Untracked Item option isn't available. This action is specific to non-Metrc customers only, as Metrc states will require a defined source for all new Packages.
• The new Package needs a source. If the Package requires a Source Harvest or external Source Facility, use Accept Incoming Transfers, Create a Single Package from a Harvest, or Create Multiple Packages from a Harvest instead.
• The new package can no longer be transferred for sale. Testing Package was enabled. Only enable this if the Package is being submitted for testing now.
• You can't find your submission. Navigate to Admin > User Submissions > All.

System Impacts & Dependencies

Changing data in one area often triggers updates elsewhere. Understanding these relationships is critical for data integrity.

For further assistance please contact support or join our Office Hours.