> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/main-menu/approvals/pending-and-approved-order-requests.md).

# Pending and approved order requests

<figure><img src="/files/5Dfi3wjcHVCoczIBMooj" alt=""><figcaption></figcaption></figure>

The Order requests area shows which requests are ready to move forward and which requests still need approval.

When a marketplace or self service request is created, equipme checks the active approval setup. Depending on the selected approval mode, the request can either be approved automatically or wait for an approval decision first.

To make this status clear, order requests are separated into two areas: Approved and Pending approvals.

### Approved order requests

Approved order requests are requests that can move forward in the order process.

A request can become approved in different ways.

With Automatic Approval, the request is approved immediately after it is submitted. It appears directly in the approved order requests.

With Simple Approval, the request appears in the approved order requests after the responsible approver has approved it. If no manual approval is required based on the selected setup, the request can also move directly into the approved order requests.

With Custom Approval, the request appears in the approved order requests once the configured workflow has marked the request as approved.

Approved requests can then be processed and ordered as usual.

### Pending approvals

Pending approvals are requests that have been submitted but are not approved yet.

These requests still need an approval decision before they can move forward in the standard order process. They may be waiting for a supervisor, department manager, location manager, cost center manager, or a custom approval workflow.

The Pending approvals area helps teams understand why a request is not available for ordering yet. It shows requests that exist in the system, but still need approval before they can continue.

### A clearer order request view

The separation between approved requests and pending approvals makes the order process easier to follow.

Approved requests are ready for the next operational step.

Pending approvals still need a decision.

This helps teams avoid mixing requests that are already approved with requests that are still waiting for approval. It also gives admins a clearer view of where a request currently stands.

### What happens when a request is approved

When a pending request is approved, it moves into the approved order requests.

From there, the responsible team can continue with the order process. The request is no longer waiting for an approval decision and can be handled like any other approved request.

### What happens when a request is rejected

When a request is rejected, it does not move forward into the order process.

Rejected requests are discarded and do not appear as approved order requests. This keeps the ordering area focused on requests that are allowed to continue.

### Admin visibility

Admins can use the Pending approvals area to keep visibility into requests that are still waiting for approval.

This can be useful when an approval is delayed, when a request needs to be checked, or when a team needs to understand why a request has not moved forward yet.

In the standard process, requests should move from pending approval to approved order requests through the selected approval mode. Admin visibility helps make exceptions and blocked requests easier to identify.

### How this works with the approval modes

The request status depends on the selected approval mode.

With Automatic Approval, new requests move directly into approved order requests because no manual approval step is required.

With Simple Approval, requests usually remain pending until the responsible approver approves or rejects them. If no manual approval is required based on the selected setup, they can move directly into approved order requests.

With Custom Approval, new requests remain pending until the configured workflow completes the required approval logic and marks the request as approved.

This keeps the order request process consistent across different approval setups, while still allowing each company to choose the level of control it needs.

### A clearer path from request to order

Pending and approved order requests help teams understand exactly where each request stands.

Pending means the request still needs a decision.

Approved means the request can move forward.

This creates a clearer path from internal demand to ordering and gives companies better control over which requests are ready to be processed.


---

# 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://hub.equipme.io/equipme/main-menu/approvals/pending-and-approved-order-requests.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.