> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/manage-inventory/create-and-print-labels/label-designer-inserting-barcodes.md).
# Insert barcodes into custom labels
You can insert different types of objects into labels, such as text boxes, fields, barcodes, lines, and pictures.
{% hint style="info" %}
You can edit existing labels. However, the best practice is to create a new label (which can be based on an existing label), and save the label with a new name. Refer to [**Create new labels using the Label Designer**](/store-manager/manage-inventory/create-and-print-labels/label-designer-select-label-format.md) for more information.
{% endhint %}
1. Click **Insert** and select **BarCode**. The cursor changes to a pencil icon.
2. Click and drag to draw a barcode box.
3. Connect the barcode object to the item barcode type in the RMH database:
1. On the **Properties** tab, click the **Properties** icon.
2. Click the drop-down beside **Code Type** and select the barcode type, e.g., UPC, EAN.
3. On the **Properties** tab, click the **Bindings** icon.
4. Under **Appearance**, click the ellipsis (...) beside **Code Type**. The **Script Editor** displays.
5. Click the **Data Sources** tab.
6. Expand **NewDataset**, expand **Table**, and double-click **BarcodeFormat**. A SQL command is inserted that will look up the barcode format that is assigned to the item in the RMH database.
7. (Optional) Edit the script to call the **PerpetuumSoft Framework** for barcode formats:\
`(PerpetuumSoft.Framework.Drawing.BarCodeType)Convert.ToInt16(GetData("NewDataset.Table.BarcodeFormat"))`
8. Click **OK**.
{% hint style="warning" %}
If you do not call the PerpetuumSoft Framework, the barcode will not display or print properly on the label. Refer to the [**Report Sharp-Shooter User Guide**](https://www.perpetuumsoft.com/sf/en/fls/rss/ReportSharpShooterUserGuide.pdf) from Perpetuum Software for more information.
{% endhint %}
4. (Optional) Display the **Item Lookup Code** under the barcode:
1. On the **Properties** tab, click the **Bindings** icon.
2. Click the ellipsis (...) beside **Code**. The **Script Editor** displays.
3. Click the **Data Sources** tab.
4. Expand **NewDataset**, expand **Table**, and double-click **ItemLookupCode**. A SQL command is inserted that will look up the Item Lookup Code in the RMH database.
5. Click **OK**.
5. Adjust the barcode position on the label:
1. On the **Properties** tab, click the **Properties** icon.
2. Click the **Properties** icon.
3. Under **Layout**, adjust the **Location** and **Size**.
{% hint style="warning" %}
Make sure that the barcode does not overlap with other objects in the label. Overlaps can cause printing issues.
{% endhint %}
6. Save your changes.
7. Print the label to test the barcode size and location, and the readability of the text.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.rmhpos.com/store-manager/manage-inventory/create-and-print-labels/label-designer-inserting-barcodes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.