> For the complete documentation index, see [llms.txt](https://docs.p4.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p4.software/p4warehouse-english/miscellaneous/cycle-count/cycle-count-by-product.md).

# Cycle Count by Product

Cycle Count by Product is a process where the system will direct you to every bin that has a specific product. When entering the Cycle Count by Product menu on your PDT you will be directed to scan a product, then the P4 Warehouse System will begin directing you to the specific bins you will need to count.

{% hint style="warning" %}
When Cycle Count by Product process is used, please remember it is critical you count ALL the bins with the product, or you will lose the product you did not count.

If you are directed to a mixed SKU bin you only count the SKU originally selected.
{% endhint %}

![P4 Warehouse Cycle Count by Product](/files/-MkMgX_9MaeRSHF-ORYr)

In the photo above you will see that there are 4 bins that need to be counted to complete the task. 


---

# 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.p4.software/p4warehouse-english/miscellaneous/cycle-count/cycle-count-by-product.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.