1.7.3 Status Setting 状态分类

> Welcome to Procurement Management Setup. Establishing a robust procurement workflow requires three critical phases: 1. Supplier Management, 2. Status Settings, and 3. Purchase Order Operations. 欢迎来到采购管理设置。建立一个完善的采购工作流需要经历三个关键阶段：1. 供应商管理，2. 状态设置，3. 采购单实操。
>
> This second document focuses on Purchase Order Status Setting. Here, you define the lifecycle of a PO and configure operational nodes that strictly control backend inventory and financial payments. 这第二份文档将聚焦于“采购单状态设置”。在此，您将定义采购单的生命周期，并配置严格控制后台库存与财务结算的操作节点。

#### Purchase Order Status Setting 采购单状态设置
![](/media/202605/2026-05-13_184613_3627270.300932765863242.png)

**Location:** Backend -> Purchase Management -> Status Setting. **位置：** 系统后台 -> 采购管理 -> 状态设置。
This page defines the available statuses and their sequence when staff process a Purchase Order. 本页面定义了员工在处理采购单时可用的单据流转状态及其顺序。

| Field/Action 字段/操作名称 | Explanation & Effect 含义与前端效果 |
| :--- | :--- |
| **Sort** 排序 | The display order of the status in the system. You can drag the icon to dynamically adjust the sequence. 状态在系统中的显示顺序。您可以拖动图标动态调整阶段的排列顺序。 |
| **Status** 状态名称 | The name of the specific procurement stage (e.g., Draft, Sent). This will be displayed as a tag on POs. 特定采购阶段的名称（如：待发送、已发送）。它将作为标签显示在采购单上。 |
| **Colour** 关联颜色 | The visual color assigned to the status, helping staff quickly identify the order progress. 为该状态分配的视觉颜色，帮助员工快速识别订单进度。 |
| **Action** 操作 | Click to edit or delete the custom status. 点击即可编辑或删除该自定义状态。 |

#### Add Status 新增状态
![](/media/202605/2026-05-13_184643_6359130.030823290720955687.png)

Click the **+ Add Status (+ 新增状态)** button to create a customized workflow stage. The **Operation Nodes (操作节点)** you select here dictate exactly what staff must, or can, do when an order enters this stage. 点击 **+ 新增状态** 按钮创建自定义工作流阶段。您在此选择的 **操作节点** 将严格决定当订单进入该阶段时，员工必须或可以执行的操作。![](/media/202605/2026-05-13_184807_1722360.36643423718691615.png)

| Field/Node 字段/操作节点 | Explanation & Effect 含义与前端效果 |
| :--- | :--- |
| **Status** 状态名称 | Name of the new status stage. 新状态阶段的名称。 |
| **Status Icon** 状态图标 | An optional visual icon displayed next to the status text. 在状态文字旁边显示的可选视觉图标。 |
| **Colour** 关联颜色 | Choose a hex color code for the status tag. 为状态标签选择一个十六进制颜色代码。 |
| **Sort** 排序 | Lower number = higher priority in the sequence. 数字越小，在流程顺序中的优先级越高。 |
| **Allow Deletion** 允许删除 | **[Operation Node]** Allows deletion of POs. Best for Draft status before committing to suppliers. **[操作节点]** 允许删除采购单。最适合在提交给供应商之前的草稿状态使用。 |
| **Allow Editing** 允许编辑 | **[Operation Node]** Allows editing of PO details and line items. Usually paired with "Allow Deletion". **[操作节点]** 允许修改采购单基础信息和商品明细。通常与“允许删除”搭配使用。 |
| **Mandatory Attachments** 强制上传附件 | **[Operation Node]** Requires supporting docs (e.g., DO, Invoice) to be uploaded to enter this status. **[操作节点]** 必须上传相关凭证（如水单、发票）才能将单据流转至此状态。 |
| **Mandatory Receiving Qty** 强制填写入库数量 | **[Operation Node] Crucial for Finance.** Requires actual received quantity to update stock. The final payment amount processed by Finance is strictly based on this receiving quantity, NOT the ordered amount. **[操作节点] 对财务极其关键。** 必须填写实际验收数量以更新库存。财务最终支付的金额严格根据此入库数量计算，而不是最初的订货数量。 |
| **Auto-Send Email** 自动发送邮件 | **[Operation Node]** Auto-emails the PO to the supplier instantly when entering this status. **[操作节点]** 单据流转至该状态时，系统自动向供应商发送包含采购单的邮件。 |

### 2. Frequently Asked Questions (FAQ) 常见问题

* **Q: Can I combine "Allow Editing" and "Mandatory Receiving Qty" in the same status?** **Q：我可以在同一个状态中同时勾选“允许编辑”和“强制填写入库数量”吗？**
 * **A:** While the system allows flexible configuration, it is not recommended for a standard workflow. "Allow Editing" is typically used for the draft stage before the order is sent. "Mandatory Receiving Qty" is used after the goods arrive. Mixing them could cause logical conflicts and financial discrepancies in your procurement process. **A**：虽然系统允许灵活配置，但在标准业务流中不建议这样做。“允许编辑”通常用于订单发送前的草稿阶段，而“强制填写入库数量”用于货物送达后。将它们混在一个状态里会导致采购流程出现逻辑冲突和财务对账差异。