> For the complete documentation index, see [llms.txt](https://anymind-group.gitbook.io/anylogi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anymind-group.gitbook.io/anylogi/en_us/fulfillment/inventory/inventroy.md).

# Manage Inventory Status

{% hint style="danger" %}
Inventory page is merely a report page showing each SKU with inventory status. Edit / Add / Delete cannot be done on inventory page.
{% endhint %}

### ① Go to Inventory Page

<div align="left"><img src="/files/-MgtHgapL79EdOxILiOM" alt=""></div>

### ② You can check inventory information in the list

{% hint style="info" %}
Status bar at the top shows numbers based on SKU type

Below table shows numbers based on the number of items.
{% endhint %}

![](/files/-MgtI6jCd2VLVmYfcFIh)

| Item         | Description                                                           |
| ------------ | --------------------------------------------------------------------- |
| Product Name | Name of the product                                                   |
| SKU          | Unique ID assigned to each and every SKU                              |
| Content      | Content / description of the SKU                                      |
| Arriving     | SKUs that are to be arrived at the warehouse                          |
| Warehousing  | SKUs that are to be inspected at the warehouse                        |
| Free         | SKUs that can be allocated to orders                                  |
| Preparing    | SKUs that have been allocated to orders, but have not been shipped    |
| Allocating   | SKUs that cannot be allocated to orders because they are out of stock |
| Damaged      | SKUs that cannot be allocated to orders                               |
| Out of Stock | SKUs that are out of stock                                            |

###


---

# 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://anymind-group.gitbook.io/anylogi/en_us/fulfillment/inventory/inventroy.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.