> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/purchases/placing-purchase-orders/purchase-order-approvals.md).
# Purchase Order Approvals
Order Approvals improve purchasing control and accuracy by ensuring selected orders are reviewed and authorised before being sent to suppliers.
Purchase Order Approvals allow businesses to control purchasing by requiring orders placed by selected users to be reviewed before they are sent to suppliers. Designated approvers can review, approve or modify an order, helping ensure purchases are accurate, authorised and aligned with business requirements.
This document will guide you through setting up order approvals and the approval process.
* [#setting-up-order-approvals](#setting-up-order-approvals "mention")
* [#approving-an-order](#approving-an-order "mention")
***
## Setting Up Order Approvals
Setting up **Order Approvals** allows you to choose which users require approval before their orders are sent to suppliers and assign the users responsible for reviewing them. This helps establish a clear purchasing workflow and ensures orders are authorised by the appropriate person.
{% stepper %}
{% step %}
#### Open the Users Page
Click on your name or company logo in the top right, then select **Users**.
{% hint style="success" %}
The **Users** page can also be accessed by going to **Settings**, scrolling down, and selecting **Users** from the menu.
{% endhint %}
The **Users** page will open listing all the **Users** that have access to your account.
***
{% endstep %}
{% step %}
#### Select the User
Select the user from the list. The user’s **Details** page will open.
{% hint style="success" %}
To open or close the sections on this form click the little arrows to the right of the titles (as circled in red above).
{% endhint %}
\
Complete the sections as per the guidelines below:
***
{% endstep %}
{% step %}
#### Select Edit User
Click on the 3 dots in the top right and select **Edit User**. The **Edit User** form will open.
***
{% endstep %}
{% step %}
#### Access
Scroll to the **Access** section and select **Purchases** under **User Access**. This gives the user access to purchasing features in Supply’d.
***
{% endstep %}
{% step %}
#### User Restrictions
In the **User Restrictions** section, use the **Purchase Orders Require Approval** field to choose whether the user’s orders must be approved before they are placed.
**Purchase Orders Require Approval**
* **Yes** – Purchase Orders created by this user must be reviewed and approved before they are placed with suppliers.
* **No** – The user can place Purchase Orders without approval.
When **Yes** is selected, an **Orders Approvers** field will appear.
**Orders Approvers**
Select the users that can approve orders from this user. You can add as many approvers as you would like. Only 1 of the approvers will need to approve the order for it to be processed.
***
{% endstep %}
{% step %}
#### Click Save
Click to apply the settings for the user.
{% endstep %}
{% endstepper %}
***
## Approving an Order
When a user who requires Order Approval submits a Purchase Order, the designated approver is notified and asked to review it. The approver can check the supplier, products, quantities and order details before approving the order or making any required changes.
When a user who requires approval submits an order:
{% stepper %}
{% step %}
The order is sent to the designated approver for review before it is placed with the supplier.
{% endstep %}
{% step %}
The approver receives an email containing the order details and a link to review the order in Supply’d.
{% endstep %}
{% step %}
The approver checks the supplier, products, quantities, prices and other order details to confirm that the purchase is accurate and authorised.
{% endstep %}
{% step %}
If no changes are required, the approver can select **Approve** from the email and follow the prompts in Supply’d.
{% endstep %}
{% step %}
Alternatively, the approver can open the **Orders** section in Supply’d to locate and review orders awaiting approval.
{% endstep %}
{% step %}
If changes are needed, the approver can modify the order before placing it with the supplier. The products from the order will be added to the approver’s cart, where quantities can be changed and products can be added or removed before the order is submitted.
{% hint style="success" %}
👉 See the [Managing Purchase Orders](/supplyd-erp/purchases/managing-purchase-orders.md#modify-order) section of the [Managing Purchase Orders](/supplyd-erp/purchases/managing-purchase-orders.md) document for more details.
{% endhint %}
{% hint style="warning" %}
**Important:** It is important to note that selecting **Modify Order** replaces any products already in the approver’s cart with the products from the order being reviewed. Complete or remove any existing cart orders before modifying an order awaiting approval.
{% endhint %}
{% endstep %}
{% endstepper %}
---
# 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://help.supplyd.co/supplyd-erp/purchases/placing-purchase-orders/purchase-order-approvals.md?ask=&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.
to apply the settings for the user.