When a cannabis product needs to be recalled, the first challenge is not simply removing it from a shelf. Operators must determine where the affected material originated, which products it entered, what remains in inventory, and what has already been shipped or sold.
Answering those questions can become difficult when cultivation, manufacturing, inventory, and sales records are spread across different systems or spreadsheets.
Flourish Software connects those records into a single seed-to-sale platform. Its recall and traceability tools help cannabis businesses follow products backward to their source and forward through manufacturing, distribution, and sales, giving compliance, quality assurance, and operations teams the information needed to respond faster and document each step.
What Is Cannabis Recall Traceability?
Cannabis recall traceability is the ability to follow a plant, harvest, lot, ingredient, or package throughout its recorded lifecycle.
There are two sides to effective traceability:
-
Backward traceability identifies where an affected product came from, including the plants, harvests, source packages, ingredients, and manufacturing inputs connected to it.
-
Forward traceability identifies every downstream package, product, order, and customer that may have received material from the affected source.
State systems such as Metrc and BioTrack collect required compliance data, but they are primarily regulatory track-and-trace systems. Operators still need an operational system that connects cultivation, production, inventory, and sales records so their teams can use them during an investigation.
That is where Flourish’s cannabis compliance and seed-to-sale platform becomes important.
How Flourish Supports Cannabis Recall Traceability
Flourish provides dedicated recall and traceback reports designed to help operators investigate an affected product across different stages of the supply chain.
These include:
-
Company Lot Recall/Trace Report: Traces inventory and lot relationships across the company.
-
Facility Harvest Recall/Trace Report: Shows what inventory was created from a particular harvest.
-
Facility Plant Recall/Trace Report: Shows which harvests specific plants entered.
Together, these reports help establish a connected chain from plant to harvest, from harvest to package, from package to manufacturing run, and from finished product to sale.
Trace an Affected Lot Through Every Downstream Product
The Flourish Lot Recall and Trace Report allows operators to enter a lot number and identify the products that originated from it.
The report organizes results by how far each product is from the original lot:
-
Depth 0 represents packages belonging to the original lot.
-
Depth 1 represents products created directly from that lot.
-
Depth 2 and beyond represent products created from those products later in the manufacturing process.
Consider a processor that discovers a potential issue with a lot of cannabis biomass. That biomass may have been used to produce crude oil, which was refined into distillate, formulated into finished oil, and then used in vape cartridges.
A basic inventory lookup may only show the original biomass package. Flourish can follow the recorded manufacturing relationships through each additional stage, helping the operator identify the finished cartridges and other products that may require review.
For each downstream package, the report can show information such as:
-
Package and lot number
-
Product or item
-
Quantity
-
Current inventory status
-
Number of associated orders
-
Quantity sold
-
First and last sale dates
This gives the recall team a clearer picture of the total inventory potentially affected.
Trace a Finished Product Back to Its Inputs
Recall investigations do not always begin with a known source lot. Sometimes the problem is discovered in a finished product through a failed test, a customer complaint, a stability issue, a packaging error, or a supplier notice.
In that situation, Flourish’s Lot Origin Trace view helps the operator trace the finished lot back to the inputs used to produce it.
Operators can investigate relationships involving:
-
Cannabis source packages
-
Harvests and plants
-
Intermediate manufactured products
-
Non-cannabis ingredients
-
Packaging or production materials
-
Supplier inventory
-
Manufacturing runs
Flourish also provides package-history views for more focused investigations. The Ancestry view traces a package back toward its recorded source, while the Descendants view shows the packages created or split from a parent package.
This two-way visibility helps operators determine whether the issue is limited to one finished product or may affect other products that share the same source material.
Connect Plants, Harvests, and Finished Packages
For cultivators and vertically integrated operators, recall traceability can begin before the product becomes packaged inventory.
Flourish’s cultivation software maintains the connection between plants, harvests, post-harvest processing, and the inventory packages produced from that material.
Operators can record wet and dry weights, track harvested material during processing, and maintain its relationship as it is separated into flower, trim, shake, or other grades.
If a problem is connected to a particular plant group or harvest, Flourish helps identify the packages created from that material. If the investigation begins with a package, the operator can trace it back through the harvest and plant records maintained in the system.
Maintain Traceability Through Manufacturing
Manufacturing can make recalls especially complicated. One source package may pass through several production stages, while multiple inputs may be blended into a single finished batch.
Flourish’s manufacturing module records the input packages and consumables selected for a production run, and links them to the output packages generated by that run. Operators can also record production quantities, yields, waste, and other run information.
This is useful for businesses producing:
-
Extracts and concentrates
-
Vape products
-
Edibles and beverages
-
Pre-rolls
-
Tinctures and topicals
-
White-label products
-
Products containing blended lots
By recording every manufacturing stage, operators can maintain batch lineage even when the material changes form several times before reaching the customer.
For example, High End Processing uses Flourish to track material through extraction, winterization, distillation, formulation, and finished oil production. Recording each stage creates a more complete chain of custody from raw biomass to the final product.
Determine What Is Still On Hand And What Has Been Left
Once affected products are identified, the operator must determine their location.
Flourish package statuses help distinguish between products that remain under the company’s control and those that have already moved downstream:
-
Created: The package remains active in the facility.
-
Assigned to Order: The package has been allocated but has not yet shipped.
-
Shipped: The package left the facility through a shipment or transfer.
-
Consumed: The package was used to create another product, or its quantity was reduced to zero.
Recall teams can filter for Created and Assigned to Order to identify affected packages still inside the operation. They can then use connected Inventory and Sales views to investigate where each package is located and which customers and orders received shipped products.
This helps answer two critical questions:
-
What inventory can we contain immediately?
-
Who may need to be contacted about inventory that has already left?
Lock Affected Inventory
After identifying affected packages, operators can use Flourish’s inventory-locking functionality to prevent them from progressing through normal workflows.
Packages can be selected individually, scanned, or locked in bulk. A lock code records why the inventory was restricted, while configurable rules determine what employees can or cannot do with it.
For a recall or quarantine, the lock should be configured so that affected inventory cannot be allocated to any other outbound order. Operators may also exclude the locked quantity from global inventory totals so other facilities do not treat it as available inventory.
Flourish can also be configured to automatically lock active packages associated with a final lab result marked Failed or In Progress. The system can identify related packages across facilities using the source package ID, sample package ID, or lot number.
Packages already allocated to manufacturing, outbound, or retail orders require additional attention. Flourish alerts the user to those packages so they can be removed from their current allocation and locked manually.
Export Recall Records for Documentation
Flourish recall results can be exported as CSV, Excel, or PDF files.
These exports can support:
-
Internal recall documentation
-
Regulatory reporting
-
Audit preparation
-
Customer and distributor outreach
-
Product reconciliation
-
Mock-recall records
-
Corrective and preventive action reviews
Operators should compare the quantity originally produced against the amount still on hand, sold, returned, destroyed, remediated, or otherwise accounted for. Any unexplained difference represents a product that still needs to be investigated.
Why Accurate Production Records Still Matter
Recall software is only as effective as the information it records.
A finished product can appear in a Flourish trace only if the affected lot or package was recorded as an input to its manufacturing run. If production inputs are not documented correctly, the system cannot later recreate the missing relationship.
For the strongest recall readiness, operators should:
-
Use lot numbers for cannabis and non-cannabis inventory.
-
Record every manufacturing input and output.
-
Maintain accurate package and order statuses.
-
Apply consistent inventory lock codes.
-
Reconcile production, waste, inventory, and sales quantities.
-
Train employees on the company’s recall procedures.
-
Conduct routine mock recalls.
-
Begin traces with the earliest known source lot whenever possible.
Flourish’s report is also intentionally conservative. When an affected input enters a manufacturing run, the report may identify every output from that run for review. This can produce a broader initial list, but it reduces the risk of overlooking a potentially affected product.
Recall Traceability Is Only One Part of Recall Readiness
Flourish helps operators identify affected products, investigate their origin, locate inventory and sales, contain on-hand packages, and export the resulting records.
The software does not replace the operator’s recall plan. Businesses still need documented procedures for regulatory notifications, customer communications, returns, product disposition and destruction, effectiveness checks, and corrective actions. Those requirements can also vary by state and license type.
The strongest recall program combines accurate seed-to-sale data, trained employees, and a clear standard operating procedure.
Be Ready Before a Recall Happens
A recall is not the time to discover that cultivation records, production runs, inventory, and sales data do not connect.
With Flourish, cannabis operators can maintain traceability throughout their everyday workflows from individual plants and harvests to manufactured products, outbound orders, and final sales. When an issue occurs, that connected data helps teams understand its scope, contain affected inventory, and respond with better information.
More importantly, operators can use the same tools for mock recalls and audits before a real incident tests their systems.
Book a demo with Flourish Software to see how connected cannabis recall traceability can help your operation stay prepared.
