> 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/edit-buyers.md).

# Update buyer details

Edit the general information and contact person for a buyer.

After SoftwareOne links buyers to your account, you can manage them in the platform and update buyer details as needed. You can edit information such as the buyer’s assigned contact person and the buyer’s logo.

### Update buyer details

To update the buyer details:

1. Go to **Settings** > **Buyers**. 
2. Select the buyer you want to update. The buyer details page opens.
3. Select **Edit**.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/fHj6pPrsQP9hB3ViE0OR/Buyer.png" alt=""><figcaption><p>Use the <strong>Edit</strong> option to update buyer details.</p></figcaption></figure></div>

4. In the **Edit buyer** flow, do the following as needed:
   * **General** – Add or update the buyer's logo. You can upload an image by selecting **Select file** or by dragging the image into the field.&#x20;
   * **Buyer address** – Update the buyer's address.
5. Select **Save**. The details are updated, and a confirmation message is displayed.


---

# 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/edit-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.