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

# Fulfillment App

Pick, pack, and ship orders in the Fulfillment App.

The Fulfillment App is designed for store managers and associates, providing a focused interface to pick, pack, and ship orders. The app also includes features to create and update rejection reasons, manage carriers and shipping methods, and more.

## Fulfillment stages

The tabs describe the store shipment's work. `Completed` includes packed shipments awaiting shipping, as well as shipments shipped during the current day in the facility's time zone. Opening that tab does not establish that the entire order has shipped.

```mermaid
flowchart TD
    accTitle: Fulfillment App picking packing and shipping stages
    accDescr: Open orders enter In Progress after picklist and shipment preparation. Packing moves the shipment to Completed while it is still ready to ship. Packed shipments can be unpacked back to In Progress. Shipping is a separate action, and shipped shipments cannot be unpacked in this flow.
    A[Open: assigned store orders] -->|Create picklist| B[In Progress: pick and pack]
    B -->|Pack| C[Completed: packed and ready to ship]
    C -->|Ship| D[Shipped: still visible in Completed today]
    C -->|Unpack before shipping| B
```

Creating the picklist starts the fulfillment work; it does not prove that staff have physically picked every item. Verify the products and quantities before packing. A packed shipment still needs the shipping step, and other shipments on the same order can remain open.

See [Open Orders](/documents/store-operations/orders/fulfillment/open-orders.md), [In Progress Orders](/documents/store-operations/orders/fulfillment/in-progress.md), and [Completed Orders](/documents/store-operations/orders/fulfillment/completed-orders.md) for the controls at each stage. The Shopify fulfillment update is a separate handoff; see [Order fulfillment sync](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/learn-shopify/shopify-integration/order-fulfillment/README.md).

## Key Features

Along with core functions like Pick, Pack, and Ship, the app includes helpful tools for both associates and managers:

* **Download Shipping Manifest for Carriers**: Managers can generate and download a shipping manifest. It is a detailed list of all ready-to-ship packages that will be shipped by a carrier.
* **Gift Card Activation**: Associates can activate gift cards directly from the app to speed up in-store gift card fulfillment.

## Pre-requisites to Use the App

To access the Fulfillment App, users must have the `FULFILLMENT_APP_VIEW` permission.


---

# 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/orders/fulfillment.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.
