> For the complete documentation index, see [llms.txt](https://ask.simplehw.eu/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.simplehw.eu/kb/provisioning-and-device-setup/quality-control.md).

# Quality control

Each batch that is produced receives 3 stages of verification/testing:

1. We test the firmware and configuration and HW for consumption and intended behavior against the Expected behavior and consumption\
   This can cause an issue sometimes because if the customer presses us with time the configuration can happen that is not fully tested. It is rare but happens and then additional reconfigurations after production are needed.
2. Firmware flashing and hardware testing are done always and eliminate any hardware issues.
3. End-product testing with final batteries tests the device behavior before the expedition and eliminates any battery or mechanical assembly issues.

<br>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ask.simplehw.eu/kb/provisioning-and-device-setup/quality-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.