> 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/designer-guide/change-a-part.md).

# Change or retire a part

## Edit a part

Open the part from **Manufacturing › Parts**. It opens read-only.

![A part open in Manufacturing, read-only, with the Edit part button](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-f34d63470e513eb651255a903f19754e2dcc4da6%2Fpart-detail.jpg?alt=media)

1. Click **Edit part**. The fields turn into inputs.
2. Change what you need. Each field saves when you leave it.
3. Click **Done editing**.

![The same part in edit mode, with Done editing](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-1ccd3e09f5a7970f4e1f64d164b7edd4ebc7157d%2Fpart-detail-editing.jpg?alt=media)

Only the part's designer (whoever created it) or an admin sees **Edit part**. Parts on hold stay read-only.

### Parts with open MOs

If a change affects an open MO (cut length, color, material, type, CNC, lathing or bends), RAIDParts asks whether to apply it to the MO. Applying it updates the MO and adds or removes only steps that haven't started, so work already done on the floor is safe.

If you skip it, an **Out of date** banner stays on the part's MOs, with **Update MO** to apply the change later.

![An Out of date banner over the part's manufacturing orders, with Update MO](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-c7e70ba2e89edd1443c6abca9576e2e98b1799a3%2Fpart-mo-out-of-date.jpg?alt=media)

## Make a part obsolete

Open the design part in **Design** and click **Make obsolete**. Add a reason, then confirm.

|          | Part not created yet                  | Part already created                                                                            |
| -------- | ------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Designer | **Mark obsolete**: applied right away | **Send request** (reason required): the part and its open MOs go on hold until an admin decides |
| Admin    | **Mark obsolete**: applied right away | **Mark obsolete**: applied right away, open MOs are canceled                                    |

While a request is waiting, the shop floor sees **On hold · Obsolete requested** and stops work. An admin then approves or releases it in **Admin › Holds**. See [Holds](/raidparts/admin-guide/holds.md).

## Delete a part

Only admins can delete a design part: **Delete**, then **Delete part**. It removes the design part, its thread and any manufacturing part, and cancels open MOs. To keep the history, make it obsolete instead.

![Holds and cancel requests](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-09beaf3692fd74714ee35858086690f15d369e23%2F08-holds.png?alt=media)


---

# 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/designer-guide/change-a-part.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.