# Customer Static Category

**Overview**

Go to **Configuration** --> **Customer** --> **Customer Static Category**

Users can create a static group to provide special recognition to customers within these groups. Customers may belong to more than one group. Groups can also be designated as VIP groups giving all customers in that group VIP status.

![](/files/-LwCettdpcv7MFUvjSsR)

Examples of groups can be regions where customers are from or consist of the customers that enrolled during a certain promotional period. When creating a customer, user has the option to put the customer into one or multiple static groups. This function allows users to track sales and understand the buying patterns of different consumer markets.

For each customer category you can create a [**price book**](/portals/central-administration-server-cas/untitled-1/transaction-codes/untitled-5.md) for them.  This allows the user to target their customer groups for special pricing or discounts to provide their best customers the buying experience that will keep them coming back.

If a customer is in multiple static categories, the customer is only eligible for one discount and the discount applied will be the one associated with the customer category last created (typically the one with the highest Customer Category ID). 

Please note - this may not be the customer category with the greatest savings.  

All that is required to create a group is to name the group and designate if it has VIP status or not. It's optional whether to add a Price Book for the group.

**Access**

Access is given to System Administrator and Financial roles.


---

# Agent Instructions: 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:

```
GET https://retailcloud.gitbook.io/portals/central-administration-server-cas/untitled-2/customer/customer-static-category.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.