> 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/troubleshooting-and-support/common-questions.md).

# Common questions

Answers about scanning, Post, and the QR code on the pick instruction.

## The scan does not find the item

Check the **GTIN** on the item. The app searches only by GTIN, not by item number. The item must also be an item line on this sales order.

## Post did not post anything

That is expected. **Post** only fills **Qty. to Ship** and **Qty. to Invoice**. Post the shipment and invoice on the sales order.

## Qty. to Ship is empty or too high

**Post** first sets quantity to ship and quantity to invoice on the order to 0, then writes the picked quantity. Anything that was open before and is not in the picking lines is no longer open.

## The QR code on the report is empty

The code is built from the GTIN. Enter the GTIN on the item and print the pick instruction again.

## QR Picking is missing on the order

The action is on the sales order, not on a quote, posted shipment, or invoice. Check that **Picking Instruction QR Code** is installed in the environment.


---

# 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/troubleshooting-and-support/common-questions.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.