> For the complete documentation index, see [llms.txt](https://docs.lionparcel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lionparcel.com/guides/guides-en/features/data-management/customer-data-management.md).
# Customer Data Management
The Customer Management menu is used to manage all customer data registered in the system, both recipients and senders. This way, when making a booking, the user does not need to re-enter the booking details for the same customer.
Through this feature, users can:
* View the complete customer list.
* Filter customers by location.
* View detailed customer information.
* Edit or delete customer data.
* Import customer data in bulk through the Bulk Customer feature.
### A. Main Customer Data Management Page
Figure 1 Customer Data Management
**Explanation:**
1. Customer Data Column: The table displays a list of customers with the following information:
1. Customer name.
2. Phone number used for contact.
3. Email (if filled in by the customer).
4. Full address for delivery or pickup.
5. District & City, Postal Code, and Address Type.
6. Created and Updated Date to monitor data changes.
2. Search Feature: The search field at the top can be used to find customers by name or phone number.
3. Filter Feature: Used to filter customer data by location (see the following figure).
4. “Bulk Customer” Button: Allows users to import large amounts of customer data through an Excel file (.xlsx).
5. “Customer” Button: Used to manually add new customer data.
### B. Customer Data Filter
Figure 2 Customer Data Filter
**Explanation:**
1. District, City → Determines the customer's geographic location.
2. Postal Code → Filters customers by a specific area code.
3. Sort By → Displays customers from the newest or oldest data.
Note: This filter is useful for companies with a large amount of customer data in various locations.
### C. Manage Customer Data
Figure 3 Manage Customer Data
**Explanation:**
1. Click the three-dot button (⋮) in the Manage column to open several action options:
* Details → Displays complete customer information.
* Edit → Edits customer data such as address or phone number.
* View STT List → Displays the list of receipts that have been sent or received by that customer.
* Delete → Deletes customer data from the system.
Warning: Deleted data cannot be restored, so make sure to confirm before deleting a customer.
### D. View Customer Data Details
Figure 4 View Customer Data Details
**Explanation:**
1. This view shows all customer information in full, including:
* Name, Phone Number, and Email.
* Customer Notes (if any, containing additional information from the admin).
* Customer's Full Address.
* District, City, and Postal Code.
* Address Type (such as home, office, warehouse, etc.).
* Created and Updated Date.
2. In the upper right corner there are two main buttons:
* Edit → To update customer data.
* Delete → To permanently delete customer data.
---
# 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.lionparcel.com/guides/guides-en/features/data-management/customer-data-management.md?ask=&goal=
```
`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.