> For the complete documentation index, see [llms.txt](https://docs.p4.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p4.software/p4warehouse-english/setup/products/packsize.md).

# Packsize

## Packsize configuration and management is a power function!

P4 Warehouse can have unlimited packsizes per product. Each packsize should be identified by a unique barcode for the packsize. If each packsize has a unique barcode P4 Warehouse will not ask what packsize you are processing, the software will simply ask for the quantity of packs.

{% hint style="info" %}
An example would be if I have a product setup to the following packsizes, each, inner pack, outer pack, pallet packsize, and I am receiving a container with 20 pallets I would scan the pallet barcode and receive 20 pallets in one operation.
{% endhint %}

Once the product is in the warehouse, You can sell the product in any packsize as the software will ask to break the pallet quantity to any lesser packsize (Pallets to boxes for example). As demonstrated in the photo each packsize has a unique barcode.

![P4 Warehouse Multi Pack Product](/files/-MivHUWFagc9qzX0qgNi)

{% hint style="warning" %}
Serialized Products can only be managed in units.&#x20;
{% 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 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.p4.software/p4warehouse-english/setup/products/packsize.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.
