---
title: Buyer groups
slug: buyer-groups
abstract: Streamline buyer management in your marketplace by organizing similar buyers into groups
content_type: concept
audience: \[developer, architect]
---

# Buyer groups

 Buyer groups organize buyers with similar needs into groups, enabling you to manage catalog access, defaults, and shared metadata at scale. They can reduce repetitive configuration when many buyers share pricing, catalogs, or business rules.

 > [!important]
 > Buyer groups is currently in Beta and is subject to change

 ## Implementation benefits

 1. Scalable management: Manage large buyer sets by applying group-level settings.
 2. Shared catalog access: Assign catalogs to a buyer group and grant visibility to all members.
 3. Centralized configuration: Define `DefaultCatalogID` and other properties at the group level.
 4. Inheritance model: Buyers inherit group configurations while maintaining the ability to override.

 ## Core concepts

 ### Group assignment

 - A buyer can belong to at most one buyer group. Membership is tracked using the buyer's `GroupID` property.
 - Buyers with no `GroupID` remain independent and do not inherit group settings.

 ### Catalog inheritance

 - Catalogs assigned to a buyer group are inherited by every buyer in that group as if assigned individually.
 - Individual buyer catalog assignments can supplement group assignments but do not negate group-level visibility.

 ### Default catalog

 - A buyer group can specify `DefaultCatalogID`. Buyers without an individual `DefaultCatalogID` inherit the group's default.
 - If a buyer has it's own `DefaultCatalogID`, it takes overrides the any group level default.

## Security roles

Access control through:

- BuyerReader: View access
- BuyerAdmin: Full management

 ## API endpoints

 Core operations:

- `GET v1/buyergroups`
- `GET v1/buyergroups/{buyerGroupID}`
- `POST v1/buyergroups`
- `PUT v1/buyergroups/{buyerGroupID}`
- `PATCH v1/buyergroups/{buyerGroupID}`
- `DELETE /v1/buyergroups/{buyerGroupID}`

 ## New properties

 ### Buyer.GroupID

 - Used to include a buyer in a buyer group
 - Set to `null` to remove buyer

 ### CatalogAssignment.BuyerGroupID

 - Used to assign a buyer group to a catalog

 ## Best practices

 ### Use when:
 - Managing 10+ buyers with shared catalog access.
 - Applying bulk pricing to distinct customer segments (enterprise, small business, etc.).
 - Common business rules or meta data that can be stored in extended properties.

 ### Avoid when:
 - There are few buyers with unique requirements
 - Buyers require different catalog access

