> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/asset-management/assets/generating-barcodes.md). # Generating Barcodes For easier check in/out you can generate bar codes for printing. Here is how: ## 1 - Select your assets that you would like to create barcodes for. Once you've selected your assets, click the + menu button in the top right corner of the page and select the Generate Barcode option.

The Asset Tag will be used as the barcode, so be mindful when printing not to use too many with long tags codes.

When the reports first generates, your tags may be all together. You are able to use the printer options that we have, or customize your own dimensions. After choosing the printer, or dimensions, select the apply/ save button to see the new layout.

Longer Asset Tags require a larger barcode.

Once you are satisfied with your layout, the print feature is at the top right of the page. You will be prompted to choose the printer you'd like to use to print the barcodes. ## 2 - Generating Barcodes by Bulk Checkout If you would like help with Bulk Checkout see out documentation [HERE](/asset-management/assets/checking-assets-out-and-in.md#2-bulk-checkout-by-checking-assets-boxes). Once you have mapped your assets to your users, you will be asked to print barcodes on the last screen before you save your changes. By clicking the Print button, you can chose to Print Tags, or Print Report, or both!
Printing Tags will allow you the same printer and customization options as above. **Make sure you save your mapping after printing.**
--- # 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.adminremix.com/asset-management/assets/generating-barcodes.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.