> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/idemia-sigma-obsolescence-june-2026.md).

# IDEMIA SIGMA obsolescence - June 2026

**For All Regions**

#### Notification![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

IDEMIA has officially announced the [end of sale](https://biometricdevices.idemia.com/sfc/servlet.shepherd/document/download/069cy00000SYo0vAAD) for its SIGMA Wide fingerprint biometric terminal, effective 15 June 2026.

The following part numbers are affected:

* C864173 – 293638877

Key dates to note:

* **Last purchase order deadline:** 15 October 2026
* **Final deliveries:** 15 December 2026
* **End of life:** 15 December 2028

Please note that security support has already ended. From now until end of life, firmware updates will be limited to major bug fixes, with service and repairs continuing under standard conditions.

Replacement

IDEMIA has indicated that SigmaTouch Pro will be the successor to the SIGMA Wide range.

However:

* IDEMIA has not yet launched SigmaTouch Pro, so it is not currently generally available
* Support within Gallagher Command Centre is planned from v9.60 onwards

#### Questions![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Please direct questions to your local Gallagher representative.


---

# 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.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/idemia-sigma-obsolescence-june-2026.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.
