> For the complete documentation index, see [llms.txt](https://davidreed.gitbook.io/how-missouri-dispensaries-manage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://davidreed.gitbook.io/how-missouri-dispensaries-manage/readme.md).
# How Missouri Dispensaries Manage Product Recalls With POS
Product recalls are among the most time-sensitive inventory events a cannabis dispensary can face. Once a recall is announced, staff may need to identify affected packages, stop further sales, separate remaining inventory, review previous transactions, and document every action. Trying to manage that process with spreadsheets and manual searches can significantly increase the risk of missing affected products.
A[ Metrc-compliant POS for Missouri](https://indicaonline.com/markets/missouri/) can help dispensaries connect package-level inventory, transaction history, and employee workflows during a recall. The most important capability is traceability: managers need to know what affected inventory remains in the store and what has already been sold.
Missouri's Division of Cannabis Regulation (DCR) maintains an official[ Product Recalls page](https://health.mo.gov/business-professionals/cannabis-regulation/licensee-compliance-and-guidance/product-recalls) with current and archived notices, affected products, and consumer guidance. As of 2026, DCR continues to issue recalls involving issues such as testing, contamination, labeling, and regulatory tracking.
### What Happens When a Missouri Cannabis Recall Is Announced?
A recall notice typically identifies affected products through information such as a licensee, product name, source tag, package information, or a downloadable product list. Missouri DCR may issue a public recall when marijuana product presents a potential threat to health and safety.
For a dispensary, the first operational question is simple: Do we currently have, or have we previously sold, any of the affected inventory?
A Missouri cannabis POS should make that question easier to answer without requiring employees to search thousands of transactions manually.
#### Step 1: Identify Affected Packages
Managers should begin with the identifiers provided in the recall notice and compare them with store inventory.
Useful POS search fields can include:
* Metrc package or source tag;
* product or item name;
* manufacturer;
* brand;
* SKU or barcode;
* date received;
* current inventory quantity;
* transaction history.
Searching at the package level is especially important. Two products may have the same retail name but originate from different packages, only one of which is affected.
Recalls should be managed from the regulatory identifier outward, not from the product name inward.
### Immediately Prevent Further Sales
Once affected inventory is identified, the next priority is preventing additional transactions.
A dispensary pos system Missouri operators rely on should allow authorized managers to make recalled inventory unavailable for sale without deleting its history.
Depending on system configuration, that may involve:
* placing affected products or packages on hold;
* disabling them from POS checkout;
* removing them from online menus;
* blocking associated barcodes;
* restricting package availability;
* adding an internal recall status.
The objective is to prevent an employee from accidentally selling recalled inventory during normal checkout.
#### Do Not Simply Delete the Product
Deleting a recalled SKU or package may remove useful information needed for reconciliation and investigation.
A recall requires preserving traceability while stopping availability. Managers should still be able to see when the product was received, which package supplied it, how much was sold, and what quantity remains.
### Physically Isolate Recalled Inventory
Changing the status in software is only part of the process. Remaining recalled products should also be controlled physically according to applicable DCR instructions and store procedures.
Staff should verify the physical quantity against the POS and Metrc records and clearly separate affected stock from sellable inventory.
A practical internal workflow can include:
1. identify the affected package;
2. block it from sale;
3. locate all physical units;
4. count the remaining quantity;
5. move units to a designated secure area;
6. document who completed the action.
This reduces the chance that a recalled unit returns to a sales shelf by mistake.
### Use POS Transaction History to Trace Previous Sales
Some recalled products may already have been sold before the notice was issued. Transaction-level search becomes especially valuable in this situation.
A cannabis pos missouri system should allow authorized employees to trace sales associated with the affected product or package.
Managers may need to review:
* transaction dates and times;
* quantity sold;
* location and register;
* package connected with each sale;
* refund or return status;
* available customer information where its use is permitted.
The POS should make historical sales searchable without changing the original transaction record.
#### Customer Communication Requires a Defined Process
Missouri DCR's recall page instructs patients and consumers who purchased recalled products to stop using them and states that unused recalled products may be discarded or returned to the dispensary where they were purchased.
Stores should have a predefined process for responding to customer questions and handling any communications required or permitted under the applicable recall notice and privacy rules.
Employees should not improvise medical advice. Their role is to communicate the official recall information and follow the dispensary's approved procedure.
### Manage Returned Recalled Products Carefully
Returns related to a recall need a separate workflow from ordinary customer-service returns.
Missouri DCR currently states that unused recalled products may be returned to the dispensary where they were purchased and that returned recalled products do not count toward a patient's purchase limit.
The Missouri dispensary POS platform should distinguish between:
* refunding or otherwise resolving the customer transaction;
* receiving the physical product;
* recording the returned quantity;
* keeping recalled inventory outside sellable stock;
* documenting subsequent disposition.
A customer refund does not make a recalled product eligible for resale.
Employees should never return recalled units automatically to normal available inventory simply because a financial transaction was reversed.
### Reconcile POS, Physical Inventory, and Metrc
During a recall, three inventory views may need to agree:
* physical inventory in the facility;
* inventory recorded by the POS;
* package information in Metrc.
If one system shows ten remaining units and employees physically locate nine, the difference should be investigated rather than hidden with an unexplained adjustment.
A good POS can help managers review package activity chronologically: receiving, sales, returns, transfers, adjustments, and current quantity.
#### Investigate Exceptions Before Correcting Them
Useful exception reports during a recall include:
* recalled packages with continued sales activity;
* inventory showing negative balances;
* recalled items still appearing online;
* physical counts that differ from system balances;
* transactions mapped to unexpected packages;
* failed synchronization events.
The goal of reconciliation is to explain the difference before correcting the number.
Missouri DCR maintains ongoing licensee guidance covering inventory reporting, inventory discrepancies, Metrc practices, and other compliance topics.
### Preserve an Audit Trail
Recall management may involve several employees and multiple actions over several days. The POS should preserve enough history to reconstruct what happened.
An effective audit trail should show:
* who placed inventory on hold;
* when the action occurred;
* quantities affected;
* subsequent returns or adjustments;
* manager approvals;
* notes or reason codes;
* final disposition where recorded.
Managers should avoid using shared employee accounts because they make it harder to determine who performed each action.
Every important recall action should leave a record that another manager can understand later.
### Coordinate POS and Online Menu Controls
For dispensaries accepting online orders, recalling a product at the register is not enough. The product may still be visible through e-commerce or pre-order channels.
The store should confirm that affected items are:
* unavailable for online ordering;
* removed from promotional placements;
* excluded from automatic menu feeds;
* removed from pending orders when required;
* prevented from being substituted into another order.
This is another reason integrated inventory matters. A system that requires employees to disable recalled products manually in several independent platforms creates additional failure points.
### Build a Recall SOP Before You Need It
A recall is easier to manage when employees already know their responsibilities.
A written SOP should define:
* who reviews DCR recall notices;
* who identifies affected packages;
* who can block products in the POS;
* where recalled inventory is physically stored;
* who reconciles POS and Metrc quantities;
* how customer returns are handled;
* how actions are documented;
* who determines final disposition based on official instructions.
Run occasional tabletop exercises using a hypothetical recalled package. This can reveal gaps in permissions, reporting, barcode mapping, and employee training.
### What to Ask a POS Vendor
When evaluating POS software for Missouri cannabis retailers, ask the vendor to demonstrate a simulated recall rather than simply discussing inventory features.
Have the vendor show how quickly a manager can:
* locate every affected package;
* stop future sales;
* disable associated barcodes;
* remove products from online availability;
* calculate remaining inventory;
* search historical sales;
* process a recall-related return;
* review employee actions;
* export relevant records.
Then ask what happens if several stores carry the same affected package.
A strong recall workflow should reduce the number of manual searches required during a high-pressure event.
### Final Thoughts
Product recalls require Missouri dispensaries to move quickly without losing control of inventory history. The POS can support that process by connecting package identifiers, current stock, sales history, online availability, returns, and audit trails.
Recent Missouri recalls demonstrate that the underlying reasons can vary significantly, including testing deficiencies, contamination concerns, labeling problems, and failures involving compliant tracking.
The best recall process does four things well: identify affected inventory, stop additional sales, preserve complete traceability, and document every corrective action. When those capabilities are built into everyday POS and Metrc workflows, dispensaries can respond to a recall with greater speed, accuracy, and operational control.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://davidreed.gitbook.io/how-missouri-dispensaries-manage/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.