> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/inventory-management/requests-processing-a-request-for-inventory.md).
# Requests – Processing a Request for Inventory
## **Purpose**
The Requests page allows Inventory Management teams to review material requested from sites.\
Each request contains the item list, quantities, dates and supporting documents.
Once approved, the request automatically converts into a **Pending Delivery**, where adjustments and final dispatch preparation can be completed.
{% hint style="info" %}
[Learn about how to process a delivery](/inventory-management/deliveries-overview-of-the-delivery-process.md)
{% endhint %}
***
### **How to Access**
Open the Side Navigation → Select Inventory → Click the Requests tab
> **Note:**\
> If your role has the **Notification Permission** enabled, you will also receive an alert when a site submits a new request.
{% hint style="info" %}
[Learn about roles and permissions](/settings/user-management/role-builder-add-or-update-roles.md)
{% endhint %}
***
## **Processing a Request – Step-by-Step**
### **1. Identify New Submitted Requests**
When new material requests are submitted by a site user, the Requests tab will show a red alert counter.
Click **Requests** to open the list.
***
### **2. View Submitted Requests**
The page displays grouped accordions:
* Submitted Requests
* Approved Requests
* Voided Requests
All new site requests will appear under **Submitted Requests**.
Use the search bar to filter by:
* Code
* Site name
* Customer
* Reference number
***
### **3. Open the Request**
Click on the row of the request you want to process.
This opens the full **Request Form** submitted by the site.
> **Important notes:**
>
> Request data is **not editable** at this stage.
>
> You may only: **Approve Request or Void Request**
***
### **4. Approving or Voiding the Request**
#### **If You Void the Request**
* The request moves to **Voided Requests** in the Inventory management section
* It also moves to **Voided Requests** under the site user’s view
* This prevents it from being processed or turned into a delivery
#### **If You Approve the Request**
Select **Yes** to continue.
***
### **5. After Approval**
Once approved:
* The request is removed from **Submitted Requests**
* It moves into the **Approved Requests** accordion
***
### **6. Converted to a Pending Delivery**
After approval, the request automatically converts into a **Pending Delivery**.
This is where the inventory team can make final adjustments before issuing stock to site.
In the Pending Delivery phase you can:
* Add items
* Remove items
* Edit quantities
* Change dates
* Edit drivers or notes
* Upload documents, photos, or videos
This flexibility allows the delivery to be prepared accurately before being issued to site.
{% hint style="info" %}
[Learn how to process a delivery](/inventory-management/deliveries-overview-of-the-delivery-process.md)
{% endhint %}
***
## **Process Flow Summary**
1. Site submits a Request
2. Notification appears (if permitted)
3. Open Requests tab in the inventory management section
4. Review Submitted Request
5. Approve or Void
6. If Approved → request converts into a Pending Delivery
7. Delivery team finalises quantities and dispatch
8. When delivered, the site will sign for receipt and stock becomes In-Use
***
---
# 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://docs.cloudscaff.com/inventory-management/requests-processing-a-request-for-inventory.md?ask=&goal=
```
`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.