> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/profile-and-settings/organization-settings/order-workflows.md).

# Order Workflows

Define ordered status steps a PO progresses through from Acceptance to Received, with per-supplier defaults for different fulfillment processes

Order workflows define the sequence of **status steps** that a purchase order moves through from the time it's issued to when it's received. Workflows provide structure and visibility into the lifecycle of an order, making it easier for teams and suppliers to stay aligned on progress.

## Overview

Each organization has:

* **An overall default workflow** — This is applied to all suppliers by default.
* **Optional per-supplier defaults** — You can assign a different workflow to a specific supplier if they follow a unique fulfillment process.

For example, you might use a **COTS/Raw Materials** workflow as your default and then assign the a **Fabricated Parts** workflow to suppliers who provide machined/fabricated parts.

## Workflow Steps

Workflows are made up of ordered steps that reflect key stages in your procurement and fulfillment process. Two steps are required in every workflow:

* **Acceptance** — The starting point when the supplier confirms the order.
* *(All other steps)*
* **Received** — The final step when the goods or services are received.

## Managing Workflows

You can create and edit workflows yourself from **Organization Settings → Order Workflows**.

* **Create a workflow** — Click **New Workflow**, give it a name, then add its phases.
* **Edit a workflow** — Open a workflow to rename it, add or remove phases, and drag phases to reorder them.
* **Delete a workflow** — Remove a workflow that is no longer needed (see the limits below).

{% hint style="warning" %}
**Edits apply to future orders only.** Renaming, reordering, adding, or removing phases affects only orders **released after you save**. Orders already in progress keep the phases they started with, so changing a workflow never disrupts work already underway.
{% endhint %}

### Backfill open orders

Some open order lines have no workflow phases: for example, a line added to an order after it was released. Open a workflow and use **Backfill open orders** under **Tools** to create its phases on every open line that resolves to this workflow and has none.

* The tool first shows how many lines and orders are affected, then asks you to confirm.
* Each backfilled line starts at the first phase. Lines that already have received units move to the final phase.
* Orders that have no workflow assigned are assigned this workflow when their lines are backfilled.
* Lines that already have phases, closed lines, and closed orders are never changed. Running the tool again is safe.

Backfilling requires both the **Edit organization settings** and **Edit orders** permissions.

### What you can and can't delete

To protect orders in progress, Silkline blocks deletes that would break existing data and explains why:

* A **workflow** can't be deleted while it is the organization default, the non-receivable material default, assigned to a supplier, or used by any order. Reassign those first.
* A **phase** can't be removed once an order that's already in progress has reached or passed it — that order keeps its own copy of the phase.

Deleting an unused workflow asks you to type its name to confirm.

## Example Workflows

Different categories of purchases often follow different fulfillment lifecycles. Below are some example workflows you might use for common procurement categories. These can be set as the organization default or applied to specific suppliers.

<details>

<summary><i class="fa-cart-shopping">:cart-shopping:</i>COTS / Raw Materials</summary>

For commercial off-the-shelf items and raw material purchases, the workflow is typically straightforward, focused on shipping and receipt:

1. **Acceptance**
2. **Processing** *(e.g., order fulfillment)*
3. **Transit**
4. **Received**

{% hint style="info" %}
Keep this workflow simple — the main goal is to identify when orders are confirmed and items have shipped. Most COTS vendors provide their order tracking and won't complete [https://github.com/Silkline/client-app/tree/development/docs/for-customers/profile-and-settings/check-ins.md](https://github.com/Silkline/client-app/tree/development/docs/for-customers/profile-and-settings/check-ins.md "mention")
{% endhint %}

</details>

<details>

<summary><i class="fa-industry">:industry:</i>Fabricated Parts</summary>

For made-to-order or custom fabricated components, the workflow usually includes production and pre-shipment steps to reflect manufacturing progress:

1. **Acceptance**
2. **Processing** *(e.g. material procurement, scheduling)*
3. **Production**
4. **Outside Processing**
5. **Quality Checks**
6. **Preparing to ship** *(e.g. inspection, packaging)*
7. **Transit**
8. **Received**

{% hint style="info" %}
Delayed **outside processing** and **failed QC/inspection** are the most common causes of unexpected delays. Including workflow steps to track these steps can help identify delayers earlier.
{% endhint %}

</details>

<details>

<summary><i class="fa-plug">:plug:</i><strong>Electronics / PCBAs</strong></summary>

Electronics workflows typically involve multiple distinct stages: procuring components, kitting, fabricating boards, assembly, testing, and shipping. Capturing each step improves visibility into lead time drivers and manufacturing progress.

1. **Acceptance**
2. **Material Procurement**
3. **Kitting**
4. **PCB Fabrication**
5. **Assembly**
6. **Testing**
7. **Preparing to ship**
8. **Transit**
9. **Received**

{% hint style="info" %}
**Kitting** is especially useful for distinguishing between *material readiness* and *production progress*. Many delays occur at the kitting stage, so surfacing it as its own step provides better schedule control.
{% endhint %}

</details>

<details>

<summary><i class="fa-arrows-rotate">:arrows-rotate:</i>Outside Processing</summary>

For processes like plating, heat treat, coating, or NDT, orders often involve sending parts to a supplier for a service, then receiving them back:

1. **Acceptance**
2. **Outbound transit**
3. **Scheduling**
4. **Prep** *(e.g., masking, cleaning, surface prep)*
5. **Outside Processing** *(the actual service step)*
6. **Quality Checks**
7. **Preparing to ship**
8. **Return transit**
9. **Receive**

{% hint style="info" %}
We recommend keep this workflow general rather than having different workflows for different kinds of finishing/processing steps (e.g. "Anodize" or "Heat Treat") to help prevent an overwhelming number of different workflows.
{% endhint %}

</details>

<details>

<summary><i class="fa-laptop-code">:laptop-code:</i>Software / Services</summary>

For non-physical purchases, shipping steps may not apply. The workflow focuses on delivery milestones and final acceptance:

1. **Acceptance**
2. **In Progress** *(e.g. onboarding, setup, or project execution)*
3. **Delivered** *(e.g. license issued, service completed)*
4. **Received**

{% hint style="info" %}
Confirming fulfillment for non-receivable items is critical for accounts payable. Even for intangible items, the "Received" step helps to standardizes reporting and closure across all order types.
{% endhint %}

</details>
