> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/using-tuplo-studio/inventory-tool/print-product-labels.md).
# Print Product Labels
Inventory Tool / Print Product Labels
Print preview showing what labels are going to be printed.
Once products are added to the inventory tool, you can print labels for them. The number of labels sent to this window is determined by the quantity of products entered into the Inventory Tool.
Do do this:
1. **Add** products to the Inventory Tool.
2. **Click** the Print Labels button.
A print preview window will open, displaying labels matching the quantity value for each product in the Inventory Tool.
{% hint style="info" %}
**For more info:**
You can view the [Connect Printers](/setup/hardware-set-up.md#zebra-label-printer) page for information on setting up label printers
{% endhint %}
***
## Additional Label Settings
Additional Label Settings in the Inventory Tool.
You can modify label dimensions depending on your printer by selecting one of two options.
* 1 1/4" x 1" labels.
* 2 1/4" x 1 1/4" labels.
Activating the following checkboxes will alter the behavior of the Inventory Tool when printing labels.
* **Print Selected Only**: Only the products selected from the Inventory Tool are added to your print preview screen.
* **Clear After Printing**: Products are removed from the Inventory Tool after printing their labels.
---
# 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.tuplo.com/using-tuplo-studio/inventory-tool/print-product-labels.md?ask=&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.
