> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/input/barcode-qr.md).

# Barcode / QR

Scans barcodes and QR codes with the device camera, single or multiple capture mode

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-71135569bd4cf8c5e393c24e8a2ee520112464b9%2Fwidget-barcode-qr.png?alt=media" alt="Goods receipt panel with a Scan pallet button and the last scanned pallet label next to it" width="568"><figcaption></figcaption></figure>

The barcode widget is a scan button: a tap opens the device camera, and the code it reads goes to your logic as text. It reads barcodes and QR codes. In single mode one scan finishes the job; in multiple mode users scan several codes in a row and save them as a list. Your logic can clear the scans and restyle the button.

**Good for:** goods receipt and picking, identifying machines, containers and batches, quick lookups on the shop floor.

## Properties

The widget's General tab lists these properties under Receives and Emits. Drop an executor's output, input or trigger onto a row to link it. An example also fills an unlinked widget as demo data in the App Builder.

{% tabs %}
{% tab title="Receives" %}
**`clear`** (from an output, `boolean`): Clears all captured barcodes on truthy values.

<details>

<summary>Example</summary>

```json
true
```

</details>

**`button`** (from an output, `object`): Configures the scan button.

<details>

<summary>Example</summary>

```json
{
  "text": "Scan now",
  "type": "success",
  "stylingMode": "contained"
}
```

</details>
{% endtab %}

{% tab title="Emits" %}
**`text`** (into an input, `string | Array<string>`): The scanned result: a single barcode text in `single` scan mode, or an array of all captured texts when saving in `multiple` mode. Writes `''` when cleared.
{% endtab %}
{% endtabs %}

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs. Settings marked *set per screen* are pinned by nature: every screen keeps its own value.

<details>

<summary>Look &#x26; feel</summary>

* **Scan mode**: Single writes the first code read and closes the camera; multiple collects codes until the check button writes them as an array. Choices: Single, Multiple.
* **Button**: The button members press to scan, upload or take a photo.
  * **Button Text**: Label shown on the button; empty shows none.
  * **Icon**: Font Awesome class of an icon shown left of the label, e.g. fa-light fa-camera; empty shows none.
  * **Text Size**: Font size of the label in px. Range 8 to 40. *Set per screen.*
  * **Icon Size**: Size of the icon in px. Range 20 to 100. *Set per screen.*
  * **Button Type**: Color scheme: default uses the accent color, normal is neutral, success green, danger red. Choices: Default, Normal, Success, Danger.
  * **Styling Mode**: Contained fills the button with its color, outlined draws only a border, text shows the label alone. Choices: Text, Contained, Outlined.
  * **Hover Text**: Tooltip shown while the pointer rests on the button; empty shows the label or nothing.
  * **Initially Disabled**: Starts the button greyed out and unclickable until a bound button value enables it.

</details>


---

# 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://docs.heisenware.com/reference/widgets/input/barcode-qr.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.
