> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/settings/buyers/view-buyers.md).

# View buyers

This topic describes how to view a list of buyers in your account, as well as details about a specific buyer.

### View the buyers list

To view a list of buyers:

1. Go to **Settings** > **Buyers**.
2. View the list of buyers displayed on the page.
3. Review information such as the buyer's name and address, tax identifier, and contact person. You can also view buyer status, including:
   * **Enabled** – Indicates that the buyer has been created in the system, but it hasn't been activated yet by SoftwareOne.
   * **Active** – Indicates that the buyer is active, and you can select it from your list of buyers when ordering products.
   * **Disabled** – Indicates that the buyer has been disabled, and you can no longer select it when buying products.
   * **Mismatch** – Indicates that the buyer’s data is not in sync with our system. This discrepancy can occur for several reasons. [Contact support](/help-and-support/contact-support.md) for assistance

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/MpoGkj1HS9wPiEsz923P/Buyers.png" alt=""><figcaption><p>Use the Buyers page to view and manage buyers.</p></figcaption></figure></div>

### Open buyer details

On the **buyer details** page, you can view properties, such as account name, ID, and status, SCU identifier (which represents a unique ID for your customer card or profile within the SoftwareOne ERP system), and tax number.

To view buyer details:

1. Go to **Settings** > **Buyers**.
2. Select the buyer you want to view. The buyer details page opens.
3. Use the tabs on the buyer details page to access different types of information:

<table><thead><tr><th width="179">Tab</th><th>Description</th></tr></thead><tbody><tr><td><strong>General</strong></td><td>Displays the buyer's address and the contact person's details.</td></tr><tr><td><strong>Sellers</strong></td><td>Displays the SoftwareOne entity associated with the buyer. There's a 1:1 relationship between a buyer and seller, meaning each buyer is linked to one or more sellers. The <strong>ERP link status</strong> is also displayed on this tab. An <strong>ERP link</strong> is a reference to the customer record in the SoftwareOne ERP system.</td></tr><tr><td><strong>Licensees</strong></td><td>Displays the licensees associated with the buyer, along with their details. </td></tr><tr><td><strong>Details</strong></td><td>Displays timestamps for various events and external IDs, such as Customer Discount Group (CDG) and Company Contact (CON) identifiers. </td></tr><tr><td><strong>Audit trail</strong></td><td>Displays the <a href="/modules-and-features/settings/audit-trail.md">audit trail</a> for the buyer.</td></tr></tbody></table>

{% hint style="warning" %}

* In the Marketplace platform, the buyer's address fields must meet certain requirements. If any address fields are empty on the **General** tab, the SoftwareOne ERP system automatically fills them with the word '**unknown'**. If you notice this, [contact support](/help-and-support/contact-support.md) for assistance.&#x20;
* If the status of the ERP link is **Blocked**, it indicates that you cannot transact with the specified seller. In such cases, [contact support](/help-and-support/contact-support.md) for assistance.
  {% endhint %}


---

# 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.platform.softwareone.com/modules-and-features/settings/buyers/view-buyers.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.
