> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.8-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/v.8-documentation/user-guide/selling/managing-customers/customer-addresses.md).
# Customer addresses
By clicking on the "Addresses" page, you will have access to the list of your customer's addresses (home, work, etc.). You can edit them using the "Edit" button, or delete them altogether.
Below the addresses table is the "Set required fields for this section" button. It opens a form where you can indicate if a database field is necessary or not by checking the appropriate boxes: this way, you can make it so fields such as "company" or "phone number" are mandatory when a customer is registering a new address on your shop.
## Adding a new address
You have the possibility to create new addresses for a client yourself with the "Add new address" button. It opens a form with the kind of field you might expect.
Some fields, however, require special care:
* **Customer email**. This field is essential: if you are adding an address for an existing customer, you MUST identify this customer using her/his email address. Otherwise, PrestaShop will not know who to assign this address to.
* **Identification number**. The national ID card number of this person, or a unique tax identification number. This field is of course optional.
* **Address alias**. A short description, in order to help the customer choose the correct address: "Home", "Office", "Aunt Beth's", etc.
* **Company**. The name of the customer's company, if needed.
* **VAT number**. The VAT identification number for the customer (or the customer's company).
* **Other**. Some additional information that might be useful to the shipment.
---
# 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.prestashop-project.org/v.8-documentation/user-guide/selling/managing-customers/customer-addresses.md?ask=&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.