> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-sv11.md).

# SV11

Learn more about the end-of-sale information for the Verkada SV11 Environmental Sensor

Verkada is announcing the upcoming end-of-sale of the [SV11 Environmental Sensor](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf),

to be replaced by the [SV23 Air Quality Sensor](https://www.verkada.com/air-quality/sensors/sv23/).

{% hint style="danger" %}

* Final orders for the **SV11** must be received by **March 1, 2023**.
* End-of-Support date for this product is **March 1, 2033**.
  {% endhint %}

## FAQ

### What does this mean?

As of **March 1, 2023**, we will no longer sell the SV11 Environmental Sensor for net new installations. All existing orders for the SV11 will be fulfilled. Verkada typically provides support for a given product for a period of ten (10) years after the end-of-sale date.

### Can customers return a SV11 that they have purchased?

Customers may return SV11 *within 30 days of purchase*.

### What happens if a SV11 under warranty needs to be replaced?

We will replace SV11 units with an SV23 unit if SV11’s are no longer available.

## Key definitions

* **End-of-Sale Announcement (this article)**: Official End-of-Sales notice.
* **End-of-Sale Date**: The last date to order the product through Verkada.
* **End-of-Support Date**: The last date a product will be supported by Verkada.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-sv11.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.