Combine Packages

Glossary

Prerequisites & Setup

Step-by-Step Instructions

Important Considerations

System Impacts & Dependencies

Troubleshooting Common Issues

Overview: Why We Use This Feature

Combining two Packages, two independently labeled and barcoded containers of cannabis material, can be especially helpful in the following scenarios:

• Combining Packages for Fulfillment, to make intake easier after transfer
  • Instead of sending 5 packages with 5 separate barcodes that each need to be scanned into the destination facility separately, you can send a single package with a single barcode.
• Storing leftover shake / trim in a single Package after the majority of the flower has been processed
  • This can help keep inventory organized and easy to store
• Tracking the creation of a new product that combines two existing products, for example hash and flower for an infused pre-roll

Use the following capabilities to Combine Packages more efficiently:

• Scan packages to select
  • For example if you have leftover shake from multiple different packages, you can quickly scan those tags and combine them into a single Package.
• Add information about Lot IDs, Locations and Costs in the same screen
• Use Permission Approvals to control quality of submissions (optional)

Once Packages are combined, there is a permanent connection established with the source packages. The following information is displayed on the output packages, and helps describe how the package(s) were created which can be helpful for compliance audits, recalls if necessary, and cost accounting:

• Source Tags
  • Traceability is maintained through this action
• Source Lot IDs
• Costs / COGS from Source Packages

Glossary

• Compound Package: The new single Package (or multiple new Packages) created by consolidating 2 or more existing Packages.
• Source Package: An existing Package whose contents are pulled into the newly created Package.
• Pulled Source Quantity: The amount of a Source Package's contents to use in the combine. Defaults to all contents of each Package; update it if you wish to only use part of the Package contents.
• Number of Packages: The total number of new Packages to create from the Source Packages.
• Per Package Quantity: The amount per new Package. If left blank, it will automatically split the Source Package contents equally between all new Packages.
• Production Batch: (Metrc facilities only) An optional batch identifier that controls test lineage. Production batches are case sensitive.
• 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. COGS data will be carried forward from the Source Packages to the Compound Packages.
• Non-Cannabis Inputs: Non-cannabis inputs from Bills of Materials that will be used on the output packages being created.
• Finish Package: Marking a Source Package as finished during the combine, available when its Remaining Quantity After Combine equals 0.

Prerequisites & Setup

Before beginning, ensure the following requirements are met:

• Permissions: Edit access to “Split & Combine” under the “Packages” section is required for this action.
• Non-Cannabis Inputs: For non-cannabis inputs to be listed, the relevant Bill of Materials must already be configured.
• Related Resources:
  • Bill of Materials Setup
  • Inventory Course
  • Costing Guide

Step-by-Step Instructions

Follow these steps to complete the workflow. Each article should ideally include a video or screenshot walkthrough for visual learners.

1. Access the Module: Navigate to the specific section in the main menu.
2. Initiate Action: Click the "Create New" or "Sync" button.
3. Input Data: Enter required fields. Note: If a field like "Order Number" is left blank, the system may auto-generate a unique ID to prevent conflicts.
4. Review & Save: Confirm all entries are correct before finalizing.
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
     1. 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: Date the Package was created.
   • 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
     1. 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
     2. 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
        1. 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

Important Considerations

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

• Field Requirements: Complete all required fields for the newly created Package before submitting. The Starting Package Tag will auto-populate with the next available tag; Expiration Date, Production Batch, Internal Lot ID, and Per Package COGS are optional.
• Per Package Quantity only applies when simultaneously creating multiple new Packages (of the same size). If left blank, it will automatically split the Source Package contents equally between all new Packages.
• Production Batch is for Metrc facilities only. 
  • ⚠️ WARNING: production batches are case sensitive and must be entered exactly as on the source package to retain the same test lineage.
• The Finish Package toggle is only enabled when a Source Package's Remaining Quantity After Combine equals 0.
• 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.
• 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.

System Impacts & Dependencies

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

Troubleshooting Common Issues

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

• Failed Metrc submission: 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. (For non-Metrc facilities, review submissions at Admin > User Submissions > All.)
• Test lineage not retained on the child package: Production batches are case sensitive and must be entered exactly as on the source package to retain the same test lineage. To inherit lineage automatically, leave the child package production batch blank when all source packages share the same production batch.
• Missing or insufficient non-cannabis inventory: When non-cannabis inputs are pulled, the "Non-Cannabis Inputs" tab shows the quantity required versus the quantity that will be applied. To learn about Canix's ability to track, view, and remediate Non-Cannabis Inventory use during Cannabis Output creation, see: Remediate Missing Non-Cannabis Inventory Quantity.

For further assistance please or join our Office Hours.