> For the complete documentation index, see [llms.txt](https://docs.venditan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.venditan.com/docs/customer-management-crm/customer-data.md).

# Customer Data

Use Venditan Commerce to securely administer and manage your Customer Data.

***

### Store full Customer Details

When Customers create an account with you while checking out on your website, their details are stored within Venditan Commerce.

You can also manually create individual customers and populate their details in the platform.

This process can also be completed from our [EPOS software](/docs/in-store-epos.md).

**Customer Details** include:

* Title
* First Name
* Last Name
* Customer ID
* Billing Addresses
* Postal Addresses
* Phone Number
* Email Address
* Gender

{% hint style="info" %}
**For B2B**: Company Name, VAT Number, Currency, Credit Limit, INCO Terms, Payment Terms per Sales Channel, Bank Accounts per Sales Channel, Taxation Type per Sales Channel, Marketplaces, and Assigned Sales Agent.
{% endhint %}

***

### Create and assign Customer Types

Create and assign **Customer Types** to help categorise your customers.

By default, all customers must be assigned to a Customer Type. Our default Customer Types are Retail, Trade, and In-Store.

Customer Type history is tracked over time so you can review any changes.

Customer Types drive various platform functions including [Group-Based Pricing](/docs/product-information-management-pim/product-pricing.md#set-different-prices-for-different-customer-types) and customer-specific Delivery Methods.

***

### Create and assign Customer Attributes

Create and assign **Customer Attributes** to customers to enrich the data and help with segmentation, reporting and personalisation.

Venditan Commerce can support an unlimited number of Customer Attributes.

***

### Create and assign Customer Tags

Create and assign **Customer Tags** to customers to group them as you require.

This lets you quickly identify a particular set of Customers when sorting your customer data.

Venditan Commerce can support an unlimited number of Customer Tags.


---

# 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.venditan.com/docs/customer-management-crm/customer-data.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.