Skip to the page

Data / Product recalls / ScentLok Technologies

ScentLok Technologies: 1 recall in 2022 (NHTSA)

ScentLok Technologies is named in 1 recall in 2022: all from the NHTSA. The latest, on November 17, 2022, covers OZ OZ20 (16,667). Hazard: A deodorizer that overheats increases the risk of a fire. Source: NHTSA recall 22E096000.

SpecStream is the live web data engine for teams and agents. It reads every recall from the CPSC, FDA and NHTSA each morning, and this page is that reading. Ask for the brands, categories or stores you follow and each new recall arrives in your sheet, CRM, Slack or agent as the agency publishes it.

Agencies
National Highway Traffic Safety Administration
First recall
November 17, 2022
Latest recall
November 17, 2022

Recalls

Each recall is listed once, with the role this firm has in it. Roles: manufacturer (1).

DateAgencyProductHazardUnitsRemedySold atRoleSource
November 17, 2022NHTSAOZ OZ20A deodorizer that overheats increases the risk of a fire.16,667Nexus Outdoors (ScentLok Parent Company) will replace the deodorizers, free of charge. Owner notification letters are expected to be mailed in November 2022. Owners may contact Nexus Outdoors at 231-220-1600 or by email at ScentLok's...Manufacturernhtsa.gov

By agency

AgencyRecallsLatest
National Highway Traffic Safety Administration1November 17, 2022

Categories

Where each agency publishes its recalls

Updated November 17, 2022. Read from National Highway Traffic Safety Administration recall data. Public domain (U.S. government work). Recalls are as the agencies published them: the CPSC, FDA (food enforcement reports) and NHTSA. A firm is one firm only when its exact name and country match; the CPSC and FDA print no firm ID. Stores are listed only when the agency's sold-at text names them, and an agency often adds that more stores sold the product. Categories are grouped by SpecStream from the words in the agency's title and product text. Free to reuse with credit to SpecStream under CC BY 4.0. Spot a wrong value? Write to [email protected] with the link to this page.