Product Issues
Product issues let you track problems with products in your catalog. Whether a product is moldy, defective, expired, damaged, or has other concerns, the product issues system gives you a centralized place to log and resolve these problems.

Why Track Product Issues?
- Quality control -- Log quality concerns for follow-up with suppliers.
- Trends -- Identify products or suppliers that consistently have problems.
- Compliance -- Document quality issues for regulatory purposes, especially in cannabis retail.
Accessing Product Issues
- Log in to the Admin Panel.
- Click Products in the top navigation bar, then navigate to Product Issues.
- The issue list loads, showing all open issues by default.
Understanding the Issue Table
| Column | Description |
|---|---|
| Issue ID | Auto-generated identifier. |
| Product | The product this issue is about. Click to view the product. |
| Type | Category of issue: moldy, defective, expired, damaged, or other. |
| Status | Open or Resolved. |
| Action Taken | The action taken on the issue (e.g., returned, destroyed, quarantined, pulled). |
| Customer Name | The customer associated with the issue, if applicable. |
| Amount | The monetary amount associated with the issue (e.g., refund amount). |
| Reported By | The user who created the issue. |
| Created | When the issue was reported. |
Creating a Product Issue
Product issues are reported by budtenders at the POS register. Managers and admins can then review and resolve them in the admin panel.
When a budtender encounters a product issue at the register, they can report it through the POS interface. The issue is created with the product pre-selected and the budtender as the reporter. The report includes the issue type, a description, the action taken (such as returned, destroyed, quarantined, or pulled), and optionally the customer name and amount (e.g., refund amount). An admin or manager can then review it in the admin panel.
Action Taken
When reporting an issue, the budtender must specify what action was taken:
| Action | When to Use |
|---|---|
| Returned | Product was returned to the customer or supplier. |
| Destroyed | Product was destroyed or disposed of. |
| Quarantined | Product was set aside for further inspection. |
| Pulled | Product was pulled from the shelf. |
Issue Types
| Type | When to Use |
|---|---|
| Moldy | Product shows signs of mold or contamination. |
| Defective | Product is defective or not functioning as expected. |
| Expired | Product has passed its expiration date. |
| Damaged | Product packaging or product itself is damaged. |
| Other | Any other issue not covered by the above types. |
Managing Issues
Viewing Issue Details
Click an issue in the list to see:
- Full description
- Product details with a link to the product page
- Issue type and status
- Resolution notes (when resolved)
Resolving an Issue
- Open the issue.
- Update the issue to mark it as resolved.
- The issue is marked as resolved.
- Click Save.
Filtering Issues
Filter by Status
- Open -- Issues that have not yet been resolved.
- Resolved -- Issues that have been resolved.
- All -- Every issue regardless of status.
Filter by Type
Show only moldy, defective, expired, damaged, or other issues.
Best Practices
- Report early -- Do not wait to report an issue. The sooner it is logged, the sooner it gets fixed.
- Be specific -- "Price is wrong" is not as helpful as "Price shows $29.99 but should be $34.99 per the latest price list."
- Set priority honestly -- Not everything is critical. Reserve critical priority for genuine emergencies.
- Assign immediately -- Unassigned issues tend to be forgotten. Assign every issue to a specific person.
- Close the loop -- After resolving an issue, the reporter should verify and close it. Do not let resolved issues sit unconfirmed.
- Review trends -- If the same product or supplier keeps generating issues, address the root cause rather than treating symptoms.
- Use for compliance -- In cannabis retail, logging quality and compliance issues demonstrates due diligence to regulators.
What's Next?
- Activity Logs -- See all actions taken on product issues.
- Audit Trail -- View field-level change history when issues result in product edits.
- Managing Products -- Navigate to the product catalog.
- Compliance -- Handle compliance-related product issues.