> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/store-operations/inventory/cycle-count.md).

# Cycle Count

## Sign in to the correct instance

Open the Cycle Count app URL provided by your organization. If the app asks for an `OMS`, enter the instance name provided by your administrator and select `Next`. Check the instance name above the sign-in fields before entering your account credentials.

<figure><img src="https://3058674140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0w9O4LtMBdjROn7iZ1X%2Fuploads%2Fgit-blob-44e6e9b07b220b3d940963c6d89e3121f800d617%2Fcycle-count-instance-sign-in.jpg?alt=media" alt="Cycle Count sign-in screen with the selected demo instance displayed above empty username and password fields"><figcaption><p>Confirm the selected instance before signing in. The demo instance shown here is an example; use your organization's instance.</p></figcaption></figure>

## Dashboard

When the store associate or manager logs into the application, all assigned cycle counts appear on the dashboard. Each count card shows the type (Hard/Directed), name of the count, start date & time, and due date.

## Open app navigation

On a phone or tablet, use the top-left menu button on the list and settings pages to open navigation. On Assigned and Pending review, the separate top-right filter button opens filters for that page.

When opening the app inside Shopify POS, confirm that its selected facility matches the POS location. If login reports that your user is not associated with that location, ask an administrator to check your facility access and location mapping.

## From counting to final review

Submitting a session finishes one associate's work. Submitting the count sends the store's combined work to head office. These are separate steps; head office reviews the proposed variances before closing the count.

```mermaid
sequenceDiagram
    accTitle: Cycle count handoff between store and head office
    accDescr: Associates submit their sessions, the store manager checks completeness and submits the count for review, and head office reviews variances and closes the count.
    participant A as Store associates
    participant M as Store manager
    participant H as Head office
    A->>A: Count in assigned sessions
    A->>M: Resolve unmatched items and submit sessions
    M->>M: Review remaining requested and undirected items
    M->>H: Submit count for review
    H->>H: Accept or reject proposed variances
    H->>H: Close count and retain history
```

## Cycle count workflow

* [Plan your count with a preview](/documents/store-operations/inventory/cycle-count/plan-cycle-count.md)
* [Create sessions and complete your count](/documents/store-operations/inventory/cycle-count/start-complete-session.md)
* [Add hand-counted items](/documents/store-operations/inventory/cycle-count/start-complete-session.md#add-hand-counted-items)
* [Review counts at the store before submitting for review](/documents/store-operations/inventory/cycle-count/count-progress-review.md)
* Review and approve variances at head office
* [Go back and review old counts and export](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/retail-operations/inventory/cycle-count/closed.md)

{% embed url="<https://drive.google.com/file/d/1D-DbMBTo41v_OKKyuE_TXzQHcni1FSt_/view?usp=drive_link>" %}
Inventory Cycle Count
{% endembed %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/store-operations/inventory/cycle-count.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.