> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-barcode-scanning.md).

# Mobile Barcode Scanning

The Mobile Barcode Scanner feature allows the user to scan and decode configured barcodes using an iPhone or Android device. The Mobile Client will recognise that barcode as a card number, allowing it to look up the cardholder to whom the barcode belongs.

### Compatibility

The Mobile Barcode Scanner feature supports the Gallagher Command Centre mobile app vMBC7.70 (or later).

It is compatible with any Apple mobile device running iOS 9 or later, which supports the Command Centre mobile app.

Android devices running the Command Centre app are also supported.

### Barcodes

Gallagher has successfully tested this feature with the following barcode formats:

| <ul><li>Aztec Code 2D</li><li>QR Code 2D</li><li>Code 128 1D</li><li>EAN-13 1D</li><li>EAN-99 1D</li><li>UPC-A 1D</li></ul> | <ul><li>DataMatrix 2D</li><li>Macro PDF417 2D</li><li>Code 32 1D</li><li>EAN-8 1D</li><li>EAN-Velocity 1D</li><li>UPC-E ID</li></ul> | <ul><li>PDF417 2D</li><li>Semacode 2D</li><li>Code 39 1D</li><li>ISBN 1D</li><li>Interleaved 2 of 5 1D</li></ul> |
| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |

Gallagher cannot guarantee the support for all barcodes, however other barcode formats may work. We recommend using QR codes if the option is available as they produce a superior user experience, with faster read times and successful scanning even when not aligned straight to the camera.

### Configuration

To configure this feature, perform the following procedures on the Command Centre server in the order specified:

### Creating a Card Type

Barcodes must be entered into the Configuration Client as cards, and require a Facility Code to be added in the Card Type **Setup** tab. If a user scans a barcode that has not been set up as a Card Type in the Configuration Client, an error message will display. If no Card Types have been configured, the 'Scan Code' option will not be available in the main menu.

Set up a Card Type in the Configuration Client to represent the barcodes, as follows:

1. Click **Configure** from the menu bar, then **Card Types**.

   The Card Type Master List Window opens.
2. Create a new Card Type and complete the fields as required.

   For full details on setting up a new Card Type, refer to the topic *"Setting up Card Types"* in the Configuration Client online help.
3. Click the Setup tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-dd9151b081702d58f1ffcbd9905f0e2adaef3a56%2Fcardsetup_textformat.png?alt=media)
4. Assign the card type a unique **Facility Code** and change the Card Number **Format** to 'Text' (this prevents issues with barcode numbers that have leading zeros).

   **Notes:**

   * Once you have clicked **OK** or **Apply**, the Region Code, Facility Code, Format and Card State Set fields cannot be altered.
   * The Issue Level of the cards (barcodes) will be ignored, so the **Card Issue Level must match default** checkbox can be left unticked.

### Configuring the Mobile Device's settings

You need to give mobile devices permission to scan barcodes before they are able to do so.

When a barcode is scanned, the associated Cardholder and their configured information will display. You can configure what is displayed via Command Centre.

Refer to [Configuring settings for all Mobile Devices](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings.md) for further detail.

### Confirming configuration

To ensure that the Mobile Barcode Scanner feature has been configured correctly, open the Command Centre app on an iOS device and ensure the **Scan Code** option is available from the main menu:

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-90c0c6702ddb693ab58bd6ecb81db05e0dc84dee%2Fmobileclient_scancodeoption.png?alt=media)

**Note:** The "View Cardholder" privilege is required to use this feature. If an operator doesn't have the "View Cardholder" privilege, the main menu entry will not appear. For more information, refer to the topic *"Cardholder Access"* in the Configuration Client online help.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-barcode-scanning.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.
