> 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/ja/herupugadesuka/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor.md).

# BR34 ガラス破壊センサー

BR34 無線ガラス破壊センサーの販売終了情報の詳細を学ぶ

Verkada は、BR34 無線ガラス破壊センサーの全ての国での販売終了予定を発表しています。

{% hint style="danger" %}
BR34 の最終注文は、までに受領される必要があります。 **2025年2月7日**.
{% endhint %}

## FAQ

### これはどういう意味ですか?

2025年2月7日をもって、BR34 無線ガラス破壊センサーの販売を終了します。Verkada は通常、対象製品について販売終了日後10年間サポートを提供します。

### 顧客は購入した BR34 を返品できますか？

顧客は BR34 を返品できます *購入後 30 日以内に返品できます*.

## 主な定義

* **販売終了の発表（この記事）**: 公式な販売終了通知。
* **販売終了日**: 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/ja/herupugadesuka/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor.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.