> For the complete documentation index, see [llms.txt](https://www.boxhero.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.boxhero.io/docs/faq/inventory-and-transactions/inventory-counts.md).
# Inventory counts
***
#### **Can I run an inventory count across multiple locations at once?**
No. Each inventory count is tied to a single location, and only the quantities in that selected location are updated when the count is submitted. To count inventory across multiple sites, create a separate count project for each location.
#### **Can the team admin edit task sheets assigned to other members?**
Yes. Even if a task sheet is `In Progress` or `Complete`, team admins can open and edit any staff member's sheet. This is useful when an assignee is unavailable or when corrections are needed before the count is submitted.
#### **What happens to items that aren't counted before submission?**
Any items included in the project but left uncounted are treated as out of stock and set to **0** when the count is submitted. To avoid this, make sure every item in your task sheets has been counted before the admin finalizes the project — or exclude items you don't intend to count when setting up the project.
#### **Can I export inventory count results?**
Yes. After a count has been submitted, open the count project and click `View Results` > `Export to Excel`. The export includes the **Starting** **Quantity**, **Counted** **Quantity**, and the **Difference** recorded.
#### **When should I duplicate an inventory count project?**
Use this feature when you need to count the same set of items again (e.g., monthly inventory checks, quarterly audits, or recurring cycle counts). Duplicating copies the items and task sheet structure from a previous count so you don't have to set it up from scratch.
---
# 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://www.boxhero.io/docs/faq/inventory-and-transactions/inventory-counts.md?ask=&goal=
```
`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.