> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/manufacturing-guide/labels.md).

# Labels

Each MO has printable labels with a QR code.

## Print

1. Open the part from **Manufacturing › Parts** and select the MO.
2. Click **Print label** and print.
3. When asked, confirm with **Yes, they printed**.

The labels are only marked printed after you confirm, so a jammed printer doesn't hide a missing label. After that, the button reads **Labels printed**.

![A part's MO, with Reprint label and Cancel MO (as an admin sees it)](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-19993628e9c89e8d6bfcacc7cf367292bf85cbc3%2Fpart-mo.jpg?alt=media)

Canceled and on-hold MOs can't get labels.

## Reprint

Only admins can reprint, with **Reprint label** on the part, or **Reprint** in **Admin › MO History**.

## Labels to print (admins)

**Manufacturing › Labels** (or **Admin › Labels to print**, the same list) shows every open MO in the active season whose labels haven't been printed, oldest first. Use **Print** on one order or **Print all** for the whole list, then confirm with **Yes, they printed** to take them off the list. On-hold MOs are left off until an admin decides. The tab shows how many are waiting. Only admins see it.

## Scan

Scanning a label's QR code opens that MO's work card on the Workstation.


---

# 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.raidrobotics.org/raidparts/manufacturing-guide/labels.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.