> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/order-management/settings/workflow-manager/step-types.md).

# Step types

The type of a step decides what it does, not its name. A step called "Order Approval" that isn't the Order Approval system action looks right but does none of the work. This page explains each step type in an OrderEazi workflow, and what each system action does when it's completed.

### The step types

* **Start:** Where every project begins. It completes itself, and it's locked.
* **End:** Where the workflow finishes. It completes itself.
* **Action:** A task a person completes, such as "Confirm artwork with client".
* **System Action:** A task a person completes that also makes OrderEazi do something, such as creating the sales order. You choose which in **Action Type**.
* **Condition:** A question with two or more answers, such as "Is the order over R50 000?". The project follows the answer chosen, and the other paths are skipped.
* **Status Change:** Moves the project into a section of My Workspace, such as **In Progress**. It completes itself.

Action, System Action, and Condition steps wait until someone with access completes them.

### The system actions

| Action Type             | What happens when it's completed                                                                  |
| ----------------------- | ------------------------------------------------------------------------------------------------- |
| OrderApproval           | Records the approval date, turns a new client into a saved client, and can create the sales order |
| CreditLimitCheck        | Checks the order against the client's credit limit. It completes itself for cash-only clients     |
| AllocatePickingslip     | Allocates picking slips in the warehouse. It can't complete until they're created                 |
| ReadyForProduction      | Marks the project as in production                                                                |
| ReadyForDelivery        | Ends production, and books the shipment if your courier app books automatically                   |
| InTransit               | Records that the shipment is on its way                                                           |
| AtCourierHub            | Records that the shipment is at the courier's hub                                                 |
| ProofOfDeliveryReceived | Records that proof of delivery has come in                                                        |
| Delivered               | Records that the goods have been delivered                                                        |
| CallClient              | A reminder to call the client. It does nothing else                                               |

Most of them also send a webhook (a message to your other systems) if you've set one up, so those systems know the step is done.

**OrderApproval**, **AllocatePickingslip**, **ReadyForDelivery**, and **Delivered** can't be completed on a project with no product lines. You see "Cannot complete" with the step's name and "the project has no line items".

**Example:** Your workflow has a **ReadyForDelivery** step, and you have a courier app that can book automatically. When the warehouse completes the step, OrderEazi books the shipment with the courier, and the waybill appears on the project's **Shipments** tab.

### Reserved names

You can't name an ordinary step "Order Approval" or "Allocate Pickingslip". Those names are kept for the system actions, so a step that looks like one always does its work. If you try, saving tells you to change the step's type or give it a different name.

### Related pages

* [Configuring a step](/central/order-management/settings/workflow-manager/configuring-a-step.md): set up a step after you've added it
* [The Default Workflow](/central/order-management/settings/workflow-manager/the-default-workflow.md): the system actions most workflows use