> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/qr-picking/qr-picking-en/picking/scan-a-gtin.md).

# Scan a GTIN

Add each item to the picking lines by scanning its GTIN.

Add a line in **Picking Lines** and scan into **GTIN**. The field accepts a barcode.

{% stepper %}
{% step %}

### The item is recognized

The GTIN must be stored on the item, and the item must be an item line on this order. The line fills in the item number, description, ordered quantity, quantity already shipped, and location. **Picked Qty.** is set to 1. The time and the user are stored.
{% endstep %}

{% step %}

### Scan the next item or the next unit

Each scan creates a line with quantity 1. To pick two units, scan the GTIN twice.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
These messages come from the app:

* **GTIN is required.** Nothing was scanned.
* **Item not found.** No item has this GTIN.
* **Item not found in the sales order.** The item is not on the order.
* **Item is already shipped.** The line is already fully shipped.
* **Item is already picked.** The open picked quantity already matches the quantity to ship.
  {% endhint %}


---

# 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.solutioo.de/qr-picking/qr-picking-en/picking/scan-a-gtin.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.