> 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/using-existing-stock-before-ordering.md).

# Using Existing Stock Before Ordering

The cheapest device is the one you already own. Before a new order goes out, equipme shows you whether a matching item is sitting in your warehouse — at two points in the ordering flow, so the information reaches you before the decision is made rather than after.

### Stock is visible while browsing the Marketplace

Products that are currently in stock are labelled directly in the Marketplace. You see this while searching or browsing, without opening each product first.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2F1J9CH6MR5CkzLq0omTnB%2Fimage.png?alt=media&#x26;token=8b21a814-0a50-403e-9431-18e6bc735b99" alt=""><figcaption><p>Stock label on a product in the Marketplace.</p></figcaption></figure>

You can also filter the catalog down to products that are available from stock, or keep browsing everything. Which of the two makes sense depends on the situation: if the request is urgent, stock is often the deciding factor.

### Exchange for Stock in Order Requests

The second checkpoint sits in the Order Requests view. When an order request is created, equipme checks the inventory in the background and shows the available quantity for matching items directly in the list.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FTUxcEC60ca9DgOPtHfql%2Fimage.png?alt=media&#x26;token=cbbd1746-4366-4411-803b-c9df34eefdd1" alt=""><figcaption><p>Available stock shown for a requested product.</p></figcaption></figure>

There is no separate workflow for this and no extra step. The availability appears in the list you are already working in, so you can decide right there whether to place the order or use what is already available.

If you only want to see items that match the requested product exactly, you can narrow the list down with filters.

### Why this matters

Without this visibility, the default behaviour is to order. A returned laptop sits in the warehouse while a new one is bought for the next hire, simply because nobody knew the first one was there.

Seeing stock at the moment of the decision changes that. Teams can cover a request from existing assets, avoid the purchase, and keep the warehouse from turning into storage nobody looks at.

What happens to an item once you decide to use it from stock is handled in the warehouse, where you can reserve it for a team or request its provision to a location or employee. See [Warehouse management](/equipme/assets/warehouse-management.md) for those actions.


---

# 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/using-existing-stock-before-ordering.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.
