> For the complete documentation index, see [llms.txt](https://manual-v2.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-v2.firstresonance.io/supply-chain/readme/approve-purchases.md).

# Approve Purchases

### **Step 1: Submit Purchase Order for Approval** [0:00](https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3?t=0)

![generated-image-at-00:00:00](https://loom.com/i/81295eed9aa94af8bfa1947b419575ac?workflows_screenshot=true)

* Ensure that the purchase order is complete with all necessary lines, fees, and taxes.
* Click on 'Approval Setup' to configure the approval process.
* Set the approval threshold (e.g., $2,000) and designate the engineering team as the approvers.

### **Step 2: Review Purchase Order** [0:27](https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3?t=27)

![generated-image-at-00:00:27](https://loom.com/i/69d94fc2c0224fe2ad5d016781ff4db3?workflows_screenshot=true)

* As the reviewer, navigate to the review section of the purchase order system.
* Click on 'Reviews' to find the purchase order that needs approval.
* Check who is responsible for reviewing the order.

### **Step 3: Assign Review Responsibility** [0:45](https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3?t=45)

![generated-image-at-00:00:45](https://loom.com/i/27cec3062413403394d398e66068e2da?workflows_screenshot=true)

* If necessary, assign the review task to yourself by selecting the appropriate option.
* Ensure you have the required roles and permissions to approve or reject the purchase order.

### **Step 4: Approve Purchase Order** [1:05](https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3?t=65)

![generated-image-at-00:01:05](https://loom.com/i/023ceb3059714a2c99853151ce06adcd?workflows_screenshot=true)

* Click on the 'Approve' button to approve the purchase order.
* Confirm that the status of the purchase order changes to 'Approved'.

### **Step 5: Notify and Mark as Ordered** [1:23](https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3?t=83)

![generated-image-at-00:01:23](https://loom.com/i/04791e37897e43a6a0fa2d99cacc65cb?workflows_screenshot=true)

* The original owner of the purchase order should send an email to notify relevant parties.
* Use the email client that opens to send the purchase order.
* Click the Order button to mark the Purchase as Ordered after emailing the relevant supplier.

#### Cautionary Notes

* Ensure all details in the purchase order are accurate before submission to avoid delays in approval.
* Double-check the approval threshold to ensure it aligns with company policy.

#### Tips for Efficiency

* Familiarize yourself with the purchase order system to navigate quickly.
* Keep a checklist of required information for purchase orders to streamline the submission process.

#### Link to Loom

<https://loom.com/share/37cb13c6737b4caba27c59a018d33ae3>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual-v2.firstresonance.io/supply-chain/readme/approve-purchases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.