> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Buyer Account Mapping

> Review one seller relationship per operator and brand, inspect private inventory-source coverage, and export normalized source-binding files

Buyer Account Mapping gives a seller one consolidated record for each exact
operator-and-brand relationship, such as a brand buying through its agency. An
authorized buyer sees one account for that relationship, rather than one per
inventory source. The seller can privately see whether each source has a current
binding.

Open the portable Page with the storefront MCP tool:

```json theme={null}
{
  "name": "get_seller_accounts",
  "arguments": {}
}
```

## What is canonical

The relationship is identified by the storefront, operator domain, and brand
domain. A CRM record, GAM advertiser, FreeWheel reference, or another native ID
can support that relationship, but none replaces it.

This keeps two native accounts with the same literal ID separate. For example,
`1234` under `gam-primary` and `1234` under `freewheel-ctv` are different source
bindings even when both support the same buyer relationship.

## Page views

* **Accounts** shows each consolidated relationship and linked buyer access.
* **Source coverage** expands the relationship across active inventory sources.
  Coverage is `Bound`, `Not required`, `Missing`, `Unbound`, or `Stale`.
  Source names and native IDs remain seller-private.

The Page is paginated and searchable. It does not expose private source topology
or source-native account IDs to buyers.

## CSV exports

The Page can download:

* an empty `source_account_bindings.csv` v1 template;
* current healthy source bindings; and
* active native accounts with their source namespace, generation,
  status, and listing version.

The normalized binding columns are:

```text theme={null}
schema_version,operation,operator_domain,brand_domain,inventory_source_key,source_external_account_id
```

Spreadsheet-formula leads are neutralized in every exported field.

<Note>
  Upload, preview, and commit are not enabled in this release. The platform will
  not apply a CSV row by row: account imports require a signed upload, a complete
  dry run, and one atomic version-checked commit so a failed row cannot leave a
  partially changed routing configuration.
</Note>

## CRM and commercial policy

A CRM is optional evidence and workflow acceleration. Runtime product discovery,
execution, and reporting use the inventory-source binding for the relevant leg.
Credit limits, billing approvals, and permissions remain in their owning typed
commercial contracts; the account-mapping export does not copy or interpret
arbitrary CRM fields.

Native binding support is runtime-specific. Only agent-backed inventory sources
currently consume explicit native-account bindings. The Page labels other source
types accordingly; they may participate only through an explicit,
contract-valid `Not required` decision.