> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alforse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change types

> Version, Revision, Replacement Part, and New Part — the per-affected-item choice that decides what you can edit and what release creates.

Each affected item has a change type, defaulting to **Version**. The type determines which draft fields are editable and what release creates. The four types differ by whether they have a predecessor and whether the result keeps the same part number.

## The four types

| Change type | You edit | Release creates | Auto-supersession |
| - | - | - | - |
| Version | BoM and BoP on the **same item** | A new **method version**; the prior Active version is archived | None |
| Revision | Attributes, documents, BoM and BoP | A new **item revision** (same Part ID, next revision) | Old revision → new revision |
| Replacement Part | Attributes, documents, BoM and BoP | A **new part number** derived from the affected part | Affected part → new part |
| New Part | Attributes, documents, BoM and BoP | A **net-new part** minted under the change notice | None — it has no predecessor |

NOTE

**A Version bumps the method; the two replacement types mint a new item; New Part is net-new.**

A **Version** creates a method version on the same item and does not supersede anything. A **Revision** or **Replacement Part** creates a new item derived from the affected part and writes a supersession from old to new. A **New Part** has no predecessor and therefore creates no supersession. See [Supersession & cutover](/docs/reference/change-orders/supersession.md).

## When to use which

* **Version** — use for manufacturing-method changes that do not require a new item revision or stock phase-over.
* **Revision** — the part is formally revising (new drawing revision, new dimension) and you want old and new
  to coexist while stock phases over. This is the everyday engineering-change case. You can name the revision
  (for example `A`) when you add the item, or leave it blank to take the next revision automatically.
* **Replacement Part** — use for a one-to-one replacement with a new part number derived from the old part.
* **New Part** — you're introducing a genuinely new part under change control, with no old part behind it.
  Nothing is superseded. This is also how a consolidation is modeled: when several components collapse into
  one, the consolidated "1" is added as a **New Part** and the old lines are dropped from the parent
  assembly's draft BoM.

NOTE

**A New Part's change type is fixed.**

Because a New Part is net-new by construction, you can't switch it to another change type after you add it,
and it shows no cutover card. The other three types can be switched, but switching discards the draft and mints
a fresh one, so any edits are reset.

## What each type gates

Change type also controls the editable surface on the affected item:

* **Version** exposes the **Bill of Material** and **Bill of Process** editors on the draft method.
* **Revision**, **Replacement Part**, and **New Part** add **Part Properties** (attributes) and documents on
  top of BoM and BoP, because each is producing a genuinely new item, not just a new recipe.

HEADS UP

**Change notices operate on Parts only.**

The **Add Affected Item** picker accepts **Parts only** — the existing-item selector is filtered to Parts, and
the New Part mini-form always mints a Part. There's no Tool path in the change-notice UI.

HEADS UP

**A purchased item can't take a Version.**

A purchased (**Buy**) item has no bill of materials or process, so a **Version** is meaningless for it. The
picker hides **Version** for Buy items and restricts a Version's item selector to **Make** parts; adding a Buy
item defaults its change type to **Revision** instead.

## Add a net-new part

Choosing **New Part** in the change-type selector swaps the affected-item modal to a short mint-a-part form:

FieldType

<details>
  <summary>**Part Number**required</summary>

  The new part's readable id. Type `...` to pull the next id in the Part sequence.
</details>

<details>
  <summary>**Name**required</summary>

  What the part is.
</details>

<details>
  <summary>**Replenishment System**required</summary>

  Buy, Make, or Buy and Make. Defaults to **Make**.
</details>

<details>
  <summary>**Tracking Type**required</summary>

  Inventory, Non-Inventory, Serial, or Batch. Defaults to **Inventory**.
</details>

Submitting creates an inactive Part and adds it as a **New Part** affected item. The part remains hidden until release.

## Supplier parts on a purchased line

A **Revision**, **Replacement Part**, or **New Part** whose draft item is purchased (**Buy** or **Buy and
Make**) gets a **Supplier Parts** grid on its line, right alongside the properties editor. You use it to set up
how the new part or revision is bought: **Supplier**, **Supplier ID** (the supplier's own part number), **Unit
Price**, **Unit of Measure**, **Minimum Order Quantity**, and **Conversion Factor**. Add, edit, and delete rows
here the same way you would on a live part.

A **Revision** draft starts with the source revision's supplier parts and their price breaks, along with its
batch size, scrap percent, lead time, reordering policy, preferred supplier, and item group. It releases ready
to plan and buy, so edit the grid only where the new revision differs. The change notice's
[changes](/docs/reference/change-orders/lifecycle.md#review-the-changes-then-release) list only the suppliers you
added, changed, or removed.

HEADS UP

**Set suppliers up on a Replacement Part or New Part before you release.**

These two drafts start with **no** supplier parts. A Replacement Part does not inherit the source item's
suppliers, and a New Part has no source to inherit from. If a purchased one releases with an empty grid, the
new part is stocked but has no way to buy it, so a purchase order can't reference it. Fill the grid on the line
first. The suppliers you add show up in the change notice's changes as additions.

## Related

**Lifecycle & release**

What release does with each change type.

[Open](/docs/reference/change-orders/lifecycle.md)

**Methods & sourcing**

Method versions and the Draft/Active/Archived states a change notice drives.

[Open](/docs/reference/methods.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.