Authority note: all HempDash actions on this page are platform-scoped (delist on the Platform, revoke the Seal, suspend the account) — HempDash cannot stop a vendor's off-platform sales or mandate a recall. See Authority Boundary.
Owner: Ayisha (Compliance) · Department: Compliance · Status: Live · Version: 1.0
Effective Date: 2026-06-13 · Last Reviewed: 2026-06-13 · Next Review Date: 2026-09-13
Source of Truth: this page · Maturity: 4 (Operational)
Classification drives notification urgency and regulator involvement. Used by the Recall Fan-Out SOP and Recall Execution playbook.
| Class | Health hazard | Examples | Notify | Regulator |
|---|---|---|---|---|
| Class I | Reasonable probability of serious harm/death | THC over limit in a CBD product, undisclosed allergen, contamination (pesticide/heavy-metal failure) | Immediate (all affected customers + consignees) | DSHS notify immediately |
| Class II | Temporary/reversible harm, low probability of serious harm | Mislabeled potency within safe range, minor labeling defect | Within 24h | DSHS notify |
| Class III | Unlikely to cause harm | Cosmetic packaging defect, non-safety labeling error | Standard | Log; notify if asked |
CURRENT-STATE note (Gate 6): the platform does not auto-delist on the Platform of a recalled product today — removal from sale is a manual step in the Recall Execution playbook. Notifications fan out automatically once a recall is created. (Source: backend-truth audit §17.8, §18.17.)
Reference index · SOPs · Playbooks · Home