> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/features/barcode-labels/printing.md).
# Printing
Inventory, location, and other screens now include an option to print barcodes as shown below.
In addition, a QR code and full label is rendered in the print modal as a preview.
### Printer requirements
Not all printers will work with ION's v1 implementation. We require printers to do be able to do 2 things:
1. Connect to the internet(wifi or ethernet)
2. Work with middleware named [**Zebra Browser Print**](https://www.zebra.com/us/en/support-downloads/software/printer-software/browser-print.html)**. This has to be downloaded** on each users computer to enable printing. ION communicates with this desktop application, which then in turn communicates with the printers.
#### Printers that work with ION
The Zebra brand Printers generally work with Zebra Browser Print and therefore ION. You should order one of those printers to print barcodes with ION.
## Troubleshooting
If you get an error message that looks like this:
If means you have the "Use Print Server" button checked, but you don't have an API key set in your organizational settings. Please check that you meant to enable the print server feature, and either fill in the API key or uncheck the box.
---
# 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://manual.firstresonance.io/features/barcode-labels/printing.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.
