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

# Introduction

## Customs Management System

P4 Customs is a complete customs management solution for importers, fully integrated with **P4 Warehouse**, our warehouse management system.

With P4 Customs, importers can manage their customs warehouses and handle customs contracts from start to finish — covering every step of the import process.

***

## About This Documentation

The data shown throughout this manual is included for demonstration purposes only, as test examples to help users become familiar with the system's functionality. It does not represent real information. Names, codes, companies, importers, and other records are fictitious and should not be interpreted as actual customer, supplier, or transaction data. This content allows users to understand the process flow without any risk of affecting real data.

***

## Manual Structure

| Section                                                    | Description                                                     |
| ---------------------------------------------------------- | --------------------------------------------------------------- |
| [Configuration](/english-2/configuration/configuration.md) | System settings, reports, and workflow configuration            |
| [Master Data](/english-2/master-data/master-data.md)       | Importers, warehouses, clients, freight providers, and products |
| [Inbound](/english-2/inbound/inbound.md)                   | Contracts and purchase order receipts                           |
| [Outbound](/english-2/outbound/outbound.md)                | Exit invoices and shipping documents                            |


---

# 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.p4.software/english-2/readme.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.