# Customer Management

Customer management is the One Platform area used to find, create, inspect, and update customer records.

Customers are managed from **Consumers > Customers** and can represent direct customers, end customers, legal representatives, professional individuals, or other consumer entities used by product activation flows.

## Main Capabilities

| Capability | Description |
|  --- | --- |
| Customer search | Find an existing customer before creating a new one. |
| Quick filter | Search across the most common customer identifiers with a single input. |
| Specific filters | Narrow the list by structured customer fields. |
| Customer creation | Register a new customer with legal, fiscal, contact, and optional product-specific data. |
| Customer modification | Update existing customer information while keeping the same customer identity. |
| Customer detail | Review the complete customer profile before using it in contracts or service activation flows. |


## Customer List

The customer list is the entry point for customer operations.

Use it to:

- verify whether a customer already exists;
- open a customer detail page;
- create a new customer when no matching record exists;
- check customer data before creating contracts or activating services.


## Search

The customer page provides two complementary search modes: quick filtering and specific filters.

### Quick Filter

The quick filter is intended for broad searches when the operator has one known value and wants to quickly check the customer list.

Use the quick filter for values such as:

- legal name;
- VAT number;
- tax code or national identifier;
- customer identifier;
- email or another known contact reference.


The quick filter is useful during operational flows because it reduces the chance of creating duplicates before a contract or service activation is started.

### Specific Filters

Specific filters are used when the operator needs a more controlled search.

They narrow the list using structured fields, for example:

| Filter area | Typical use |
|  --- | --- |
| Customer type | Find only companies, private individuals, or professional individuals. |
| Country | Limit the list to customers registered in a specific country. |
| Fiscal identifiers | Search by VAT, tax code, SIREN, SIRET, or other national identifiers when available. |
| Contact data | Find customers by email, PEC, or phone data when supported by the customer record. |
| Status or flags | Filter billable customers or other operational categories when exposed by the UI. |


Use specific filters when a broad quick search returns too many results or when the same legal name can appear in multiple customer contexts.

## Customer Detail

The customer detail page shows the complete customer profile and is the main place to verify whether the record is suitable for a contract, service activation, or consumption monitoring flow.

The page groups customer information by data area so operators can review only the information relevant to their task.

## Consumer Types

When creating a new record from **Consumers > Customers**, One Platform can create two different types of consumers:

| Consumer type | Purpose |
|  --- | --- |
| `Customer` | Represents a legal or physical subject that can be used in customer management, contracts, service activation, billing, and fiscal flows. |
| `Monitoring Unit` | Represents an operational unit used to monitor consumptions or product usage without necessarily modelling a billable legal customer. |


The consumer type defines the role of the record inside One Platform. It is different from the customer type, which describes the fiscal or legal nature of a `Customer`, such as `Corporate`, `PrivateIndividual`, or `ProfessionalIndividual`.

Use `Customer` when the record identifies the subject that buys, receives, signs for, or is billed for a service. Use `Monitoring Unit` when the record is needed as an operational aggregation point for monitoring and reporting usage.

## Creation and Modification

Customer creation and modification use the same information model.

Creation is used when no existing customer matches the subject. Modification is used when the customer already exists and its information must be corrected or completed.

The same editor is used to maintain the main customer information areas.

### Customer Type

The customer type defines which information is expected and how the customer can be used by downstream flows.

The available customer types depend on the customer's fiscal country. One Platform uses the fiscal country to determine which customer types are valid and which fiscal fields must be filled in.

| Customer type | Use when |
|  --- | --- |
| `Corporate` | The customer is a company or legal entity. |
| `PrivateIndividual` | The customer is a private person. |
| `ProfessionalIndividual` | The customer is a professional person with a fiscal or business identity. |
| `PublicAdministration` | The customer is a public administration, where available for the fiscal country. |
| `NonProfit` | The customer is a non-profit entity, where available for the fiscal country. |


Select the customer type carefully. Product activation flows, fiscal validations, and contract data can depend on this value.

For example, Italy exposes the full customer type set:

France exposes a smaller subset:

### Basic Information

Basic information identifies the customer in One Platform.

Typical fields include:

- legal name or display name;
- country;
- customer type;
- external references or identifiers;
- language or operational preferences when available.


This information is used throughout the platform in search results, contract forms, service activation screens, and monitoring views.

### Fiscal Information

Fiscal information describes the customer's tax identity.

Fiscal fields are country-dependent. The fiscal country selected for the customer determines which fiscal identifiers are required, optional, or not applicable.

Depending on the fiscal country and customer type, fiscal information can include:

- VAT number;
- tax code;
- national company identifiers;
- establishment identifiers;
- other country-specific fiscal values.


Fiscal data is commonly required by service activation, invoicing, reporting, and billing flows. Keep these values aligned with the official customer registry data.

Country-specific fiscal rules
Do not apply the same fiscal field mapping to every customer. A French customer and an Italian customer can expose different customer type options and require different fiscal identifiers, even when both represent companies.

### Billing Information

Billing information is used when the customer is billable or when a product flow requires invoice-related data.

Typical data includes:

- billable flag;
- billing address;
- city, state, postal code, and country;
- billing contact data when available.


Billing information can differ from residence or registered office information, depending on the customer and product flow.

### Personal Information

For individual customers, additional personal information can be required.

This can include:

- first name and last name;
- birth date;
- birth city or country;
- residence address;
- personal fiscal identifiers.


Only use these fields when they apply to the selected customer type and to the product or compliance flow being executed.

### Contact Information

Contact information defines how the customer or representative can be reached.

Common fields include:

- primary email;
- certified email or PEC, when applicable;
- phone number;
- additional contact channels.


Contact information is often used by activation flows, signature flows, operational notifications, and support processes.

### Custom Data

Custom data stores product-specific metadata that does not belong to the standard customer fields.

Use custom data for additional identifiers or flags required by a product line, integration, or country-specific activation process.

Use custom data intentionally
Custom data should be meaningful and documented by the product flow that uses it. Avoid storing values that duplicate standard fiscal, billing, or contact fields.

## Related Sections

- [Key Concepts - Customers](/products/oneplatform/one-platform-knowledge-center/01-get-started/02-key-concepts/key-concepts#customers)
- [Contracts Management](/products/oneplatform/one-platform-knowledge-center/03-products-and-modules/01-web-platform/contracts-management)
- [Consumptions Monitoring](/products/oneplatform/one-platform-knowledge-center/03-products-and-modules/01-web-platform/consumptions-monitoring)