> 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/receiving.md).

# Receiving

## Overview

The HotWax Commerce Receiving app helps store associates receive inbound inventory from transfer orders, purchase orders, and returns. It runs in a browser, supports barcode scanning, and updates inventory in HotWax Commerce as receiving is saved or completed.

## Getting started

### Logging in

1. Open the Receiving app URL provided by your organization.
2. If you are not already signed in, you will be redirected to HotWax Launchpad.
3. After authentication, you will return to the Receiving app.

### Navigation and dashboard

The left menu includes:

* Transfer Orders
* Returns
* Purchase Orders
* Settings

All list pages support search, open/completed filtering, pull-to-refresh, and load-more actions when additional records are available.

## Guides

* For transfer orders, see [Transfer Orders](https://docs.hotwax.co/documents/store-operations/inventory/receiving/transfer-orders.md).
* For purchase orders and returns, see [Returns and Purchase Orders](https://docs.hotwax.co/documents/store-operations/inventory/receiving/returns-and-purchase-orders.md).
* For app configuration, see [Settings](https://docs.hotwax.co/documents/store-operations/inventory/receiving/settings.md).
* For permission mapping, see [Permissions](https://docs.hotwax.co/documents/store-operations/inventory/receiving/permissions.md).


---

# 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/receiving.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.
