# Inventory Control (pending)

Having 1 Shopify location as the source location and multiple points of sales means you have to distribute stock count.&#x20;

### Stock allocation table

<figure><img src="/files/HxiiJ3h4LcKEzSMrLup5" alt=""><figcaption></figcaption></figure>

Stock allocation table or Inventory control table should have 6 columns: 5 visible and fixed columns and the last one hidden and changes per the location selected.&#x20;

The meaning of each columns are as followed:

* Product name: Product name.
* Variant: Variant of the product. Each row is a variant, and once hovered, you can see the picture of the product/variant.
* Quantity: The number of available stock for that variant. Note that this number is taken from Shopify. Example: Shopify location A has 100 available stock of that variant, the number in this column will be 100.&#x20;
* Distributed: the total number of stock of that variant which has been allocated to all locations, including the one being selected.
* Undistributed: (Quantity - Distributed), the number of stock left and haven't been allocated to any other locations.&#x20;
* Location's column: this is where the stock moving happens. You can see the number of stock which the warehouse can commit to that location. The default value is 0, and once hover over, you can see the edit icon, and edit the number using the text field. Any editing in this column will change the number in the Distributed and Undistributed column.&#x20;

{% hint style="info" %}
Due to the fact that stock count can change constantly, we have also provided a refresh button so you can update the latest stock count&#x20;
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.dingdoong.io/inventory-management/inventory-control-pending.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
