> 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/english-2/inbound/inbound/history.md).

# History

The **Purchase Order Receipts** section displays purchase orders that have already been received into the warehouse through **P4 Warehouse**.

***

## Overview

This section shows only orders whose receiving process has been **fully completed**. Partial or in-progress receipts are not shown here.

> 📷 Screenshot: Purchase Order Receipts list showing completed orders with their dates, importer, and warehouse.

***

## How Orders Appear Here

An order appears in the History section once the full receiving process has been completed in P4 Warehouse's Entry module. This provides a clear audit trail of all merchandise that has been officially received into the customs warehouse.


---

# 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/english-2/inbound/inbound/history.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.
