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

# BOPIS Fulfillment App

Pick, pack, and hand over store pickup orders in the BOPIS Fulfillment App.

The BOPIS Fulfillment App is designed for store managers and associates, providing a focused interface to pick, pack, and hand over store pickup orders. The app also includes features to manage Ship-to-Store items, activate gift cards, and view notifications for new and open orders.

## Pickup lifecycle

Use the order tabs to distinguish preparation from customer collection. Mark an order ready only after its items are picked and the package is prepared. Record handover when the customer actually receives it.

```mermaid
flowchart TD
    accTitle: Store pickup preparation and customer handover
    accDescr: In Open, pick the items and prepare the package. Ready for pickup moves the store pickup shipment to Packed, where it waits for the customer. Handover records customer collection and moves it to Completed.
    Open["Open: pick and prepare package"] -->|Ready for pickup| Packed["Packed: awaiting customer"]
    Packed -->|Handover after collection| Completed["Completed: customer collected"]
```

`Ready for pickup` does not mean the customer has collected the order. Keep it in Packed while awaiting collection. See [Open Orders](/documents/store-operations/orders/bopis/open-orders-page.md), [Packed Orders](/documents/store-operations/orders/bopis/packed-order-tab.md), and [Completed Orders](/documents/store-operations/orders/bopis/completed-orders-tab.md) for actions at each stage.

This flow describes the store's pickup shipment. An order can have other shipments at different locations; review `Other Shipments` in Order Details when checking the full order's progress.

## Key Features

Along with pick and pack, the BOPIS App includes key features for order fulfillment:

### Catalog Page

The Catalog page lets store staff search for products and see if they’re available for pickup at the store. It shows useful details like product name, SKU, and how many units are in stock.

### Orders Page

The Order Details page in the BOPIS App provides comprehensive information about orders and is for store associates to perform key functions such as order picking, packing, and marking orders as ready for pickup or picked up.

### Ship-to-Store Page

This page is used when a customer places a pickup order for a product that is not available at their selected store. In such cases, the item is shipped from another location to the store, where the customer can pick it up once it arrives.

### Gift Card Activation

When a customer buys a gift card online, store staff can activate it before handing it over during pickup.

### Notifications

Whenever a new BOPIS order is placed for store pickup, store associates receive a notification to take action. To access the notifications, tap the bell icon in the top right corner of the page.

## Pre-requisites

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

{% hint style="info" %}
This permission only allows viewing. To perform actions like Pick, Pack, view the `Order Details` page, and manage other store operations, store staff must also have the `COMMON_ADMIN` and `STOREFULFILLMENT_ADMIN` permission.
{% endhint %}


---

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