> For the complete documentation index, see [llms.txt](https://docs.p4warehouse.com/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p4warehouse.com/v2/fulfillment/pick-tickets/picking-or-handheld-interface/pick-ticket-list.md).

# Pick Ticket List

Pick ticket list shows available pick tickets within the user's default warehouse ( to change default warehouse setting go to Setup > System > Users). 

{% hint style="info" %}
Notice: Pick ticket list does not include order with 'Draft' and 'Unallocated' pick ticket state because handheld users cannot perform actions on these orders.
{% endhint %}

<figure><img src="/files/lBj7PvhSxmQONrJkErqx" alt=""><figcaption></figcaption></figure>

Pick List can be used to allow the handheld users to select the next order for picking. Outside of an eCommerce fulfillment center this option is normally disabled as it is the responsibility of the Web dispatcher to decide what orders get picked.

## Picking Steps

After selecting an order from the pick ticket list, user will see the details of order and further instructions as shown below.&#x20;

<figure><img src="/files/DgodK77iUcZ3UqW0udtC" alt=""><figcaption></figcaption></figure>

In this case pick ticket has 3 different picks and contains a grand total of 110 units.&#x20;

Image below highlights the exact details regarding the first pick of the order. These details includes product location in the warehouse, Sku number, and quantity needed.

### Step 1

<figure><img src="/files/GZzycml9MHsNvHbDcaIi" alt=""><figcaption></figcaption></figure>

Follow the directions generated by the android handheld device to continue the process of picking.

### Step 2

<figure><img src="/files/H0ofR2BEIIAQqvXSlk8B" alt=""><figcaption></figcaption></figure>

Completed steps are displayed in the status window and system automatically generates instructions for next steps. Continue to follow these instructions until the current pick is completed.

### Step 3

<figure><img src="/files/gYV2r9XOJTubNF2udjD6" alt=""><figcaption></figcaption></figure>

If the picking location has sufficient amount of the product enter the required quantity (in this case the quantity is 20 units of selected product). Click the check mark button to continue to the next step.

{% hint style="info" %}
Notice: If the product is not available then the order needs to be shorted.
{% endhint %}

### Step 4

After the goods are picked, move them to a tote that was generated for this pick ticket. Follow the instructions as shown below.

<figure><img src="/files/QLkzQwe2WNcL7Xi8Rfyc" alt=""><figcaption></figcaption></figure>

A tote label can be provided by a web dispatcher or can be printed using an android handheld device if the user is setup accordingly.

### End of the Pick

<figure><img src="/files/5uDEvjPciwErZ3vI6GFP" alt=""><figcaption></figcaption></figure>

The system will automatically queue up the next pick for the current order. Follow these steps to complete all the picks.

After all the pick are done the system will generate a corresponding message as shown below.

<figure><img src="/files/tJxNKkGiGJQN7E92u8Aj" alt=""><figcaption></figcaption></figure>

Now the pick ticket state has been changed from 'Waved' to 'Rating', which means that this order is ready to be shipped using one of four shipping methods available in P4W system.


---

# 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://docs.p4warehouse.com/v2/fulfillment/pick-tickets/picking-or-handheld-interface/pick-ticket-list.md?ask=<question>&goal=<endgoal>
```

`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.