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

# Change a Seller Account's type

> A Seller Account is a Listing or a Storefront. Read it with get, and change it in Seller Settings, in the Account type section of the Seller Setup Page, or with the sellingMode field on save_seller.

A Seller Account is one of two types:

* **Listing.** Your products are listed for buyers. You bring your own sales agent. A Listing account has no access to
  Enhanced Reporting.
* **Storefront.** Apostra hosts the agent that answers buyer briefs for you.

## How the account type affects what you pay

What you are charged follows the plan your organization accepted. The account type changes the charge only on the
Standard plan. Standard prices each metered activity by the type of the account that incurred it, at the moment it
happened. A Listing account has no charged activities. A Storefront account is charged at the plan's rate.

Every other plan keeps the terms its own row states, whatever the account type. On those plans, changing the type
changes the features the account has, and does not change what you are billed. Your plan and its terms are in Plan &
Billing (see [Plan and billing](https://docs.apostra.com/v3/plan-and-billing.md#what-you-pay-as-a-seller)).

The signup screen's Listing option says it "includes your connected sales agent". That means an agent you
connect yourself. Apostra's hosted agent is the Storefront type. Setting up an ad server that Apostra manages
for you records the Storefront type when it has to create your storefront, and it does not change the type of
an account that already has one. [From signup to your first booking](https://docs.apostra.com/v3/seller-first-booking.md) shows where
this matters for a publisher with an ad server.

When a managed sales agent is connected while the account remains on Listing, the Connect form and seller
readiness show an advisory item with the switch action. It does not block transactions or switch the account.
Only a direct administrator of the billing organization can review the charges above and confirm the change.

Both are Seller Accounts. The type is stored on the account itself, so it does not depend on the plan or on any
feature setting of your organization. Some organizations call a Listing account the pass-through account.

## Where the app shows it

The seller rail names the account type under the mode switch: **Listing account** or **Storefront account**. It is
the same stored type `get` returns. The first mode of the switch is **Selling** for both types, because both are
places you sell from.

A Listing account has no Library row. Only Apostra's Storefront agent reads the Library, and a Listing account
brings its own sales agent. The tools that only a Storefront account uses sit under **With a Storefront account**. On
a Storefront account they sit under **Storefront agent**, with Library.

## What each type turns on

The account type decides which seller features the account has. Your plan decides what you pay, not which of
these features you get.

| Feature | Storefront | Listing |
| - | - | - |
| AI Business Rules | Yes | Yes |
| Storefront Agent: Apostra composes and packages your inventory for buyer briefs | Yes | No |
| Demand Inbox | Yes | No |
| Pitches written for buyers' proposals | Yes | No |
| Product marketing material used in proposals | Yes | No |
| Managed campaigns | Yes | No |

* **Each account follows its own type.** In an organization with several Seller Accounts, a Storefront account
  and a Listing account each get their own type's features.
* **A Seller Account with no active storefront counts as a Listing.**
* **Changing the type changes the features** as soon as the change is saved.
* **Distribution and Custom sources are add-ons**, held by the organization. They do not come from the type.
* **Two things can give an account more for a limited time.** A beta Apostra enrolls your organization in
  applies to every Seller Account in the organization, whatever its type, for the beta's term. A Demo
  Storefront applies to its own account, for the demo.
* **Features Apostra once switched on by hand for an account no longer apply.** A Listing account that was given
  Storefront features that way now has the Listing features. To get them back, change the account to a Storefront.

## Change it in Seller Settings

Seller Settings in the web app shows the account type under **Selling mode**. A direct administrator of the billing
organization changes it there with a **Switch to Storefront account** or **Switch to Listing account** button. The
button makes the same `save_seller` call an agent makes, after a confirmation that says what the switch changes.

Seller Settings shows what the API answers and decides nothing itself:

* **Who may switch.** Anyone else sees the type read-only, with the reason the API gives. See
  The Entitlements read, described under Read the type below, carries it.
* **The plan.** If the plan does not cover a Storefront, there is no switch. Seller Settings shows the API's reason
  and its next step, **Move to Standard in Plan & Billing**, which opens Plan & Billing.
* **Running work.** If a switch to Listing is refused, Seller Settings lists each blocker the API names and says
  nothing was saved.
* **A Demo Storefront.** Its type is fixed, so Seller Settings explains that and offers no switch.
* **The result.** After a change, Seller Settings shows what the API reported: the activities that become billable
  or free on the Standard plan with their IU amounts, and the Enhanced Reporting accounts a switch to Listing closed.

An archived storefront is read-only, so it has no switch. The API says so with the reason `storefront_archived`.

## Change it in chat

The Seller Setup Page has an **Account type** section, in Murph and in any chat host that shows the page. It sits
below the setup checklist and is not a setup step: it changes no step, no count of steps left and no next action. It
shows the type, and a direct administrator of the billing organization gets one button for the other type. The button
opens a confirmation that says what the switch changes, then makes the same `save_seller` call an agent makes.

The section shows what the API answers and decides nothing itself:

* **Who may switch.** Anyone else sees the type read-only, with the reason the API gives.
* **The plan.** If the plan does not cover a Storefront, there is no switch. The section shows the API's reason, and
  when you can act on it, a **Move to Standard in Plan & Billing** button that opens Plan & Billing. When only another
  administrator can act, it shows the reason alone.
* **A Demo Storefront or an archived storefront.** The type is read-only, with the API's reason.
* **Running work.** If a switch to Listing is refused, the section lists each blocker the API names with its count and
  examples, and says nothing was saved.
* **The result.** After a change, the section shows the activities that become billable or free on the Standard plan
  with their IU amounts, and the Enhanced Reporting accounts a switch to Listing closed. It then reads the account
  again, because the type decides which Seller Setup view applies.
* **A read that failed.** The section says it could not check, and offers to try again. It never guesses the type or
  who may change it.

An agent in Claude or ChatGPT does not need the page: it reads `sellingModeChange` and calls `save_seller` itself.

## Read the type

`get({ kind: "seller" })` returns `sellingMode`: `listing` or `storefront`.

```json theme={null}
{ "kind": "seller" }
```

The Entitlements read (`include: ["entitlements"]`) still returns `operatingMode` with the same answer under its
older name: `LISTING_ONLY` or `AGENTIC_MEDIA_COMPANY`. It also returns `sellingModeChange`, whether you can change the
type now:

```json theme={null}
{
  "canChange": false,
  "to": "storefront",
  "reason": {
    "code": "plan_does_not_cover_account",
    "message": "Switching an account to Storefront needs the Standard plan. ..."
  },
  "nextStep": { "code": "move_to_standard", "canAct": true, "planBillingUrl": "https://..." }
}
```

| Field | Meaning |
| - | - |
| `canChange` | Whether `save_seller` would accept the change now, by the checks it makes first. |
| `to` | The type a change would set: the one the account does not have. |
| `reason` | Why not, when `canChange` is false. `code` is `not_organization_administrator`, `storefront_archived`, `demo_storefront` or `plan_does_not_cover_account`. |
| `nextStep` | Present when the plan is the reason. `canAct` is false when only another administrator can act. `planBillingUrl` is present when you can. |

`sellingModeChange` is `null` when the server could not work it out. It does not read running work: a switch to
Listing can still be refused with the blockers listed under Rules below. The read gives the first reason that applies,
in this order: not an administrator, an archived storefront, a Demo Storefront, then the plan.

## Change the type

Send `sellingMode` alone to `save_seller`.

```json theme={null}
{ "sellingMode": "storefront" }
```

| Field | What it sets |
| - | - |
| `sellingMode` | `listing` or `storefront`. |

The change happens on the same account. The storefront, inventory sources, connections and history stay as they are.
Each change is recorded with who made it, when, and the type before and after.

The result names the seller-paid activities that become billable (a switch to a Storefront) or free (a switch to a
Listing) on the Standard plan, each with its IU amount. On any other plan billing is unchanged. A period already
earned stays billed. Nothing already billed is repriced.

Setting the type the account already has succeeds and changes nothing. The result reports `selling_mode_unchanged`.

## Rules

* **Only a direct administrator of the billing organization can change the type**, through `save_seller` or Seller
  Settings. The change alters what the
  organization is charged, so it needs the same authority as accepting its Terms. Anyone else is refused with
  `ACCESS_DENIED`.

* **A Storefront needs a plan that covers it.** If the organization's plan does not, the call is refused with
  `CONFLICT`, and the reason says what to do next.

* **A switch to Listing is refused while Storefront-agent work is still running.** The call returns
  [`CONFLICT`](https://docs.apostra.com/v3/errors) with `details.reason` `selling_mode_change_refused` and `details.blockers`. Each blocker
  has a `reason`, a `message`, a `count` and up to five identifying `examples`. Nothing is saved. Finish or stop the
  work, then send the change again.

  | Blocker `reason` | What is running |
  | - | - |
  | `live_managed_campaign` | A managed campaign of this account is active or paused. |
  | `live_media_buy` | A media buy sold through this account is booked and has not ended. |
  | `market_maker` | A Market Maker offer is active for this account. Contact support. |
  | `scope3_adapter_storefront` | This is an Apostra adapter storefront, which Apostra runs as a Storefront. |

* **A Demo Storefront has a fixed type.** A change in either direction is refused with the blocker `demo_storefront`.

* **A switch to Listing closes Enhanced Reporting.** A Listing account cannot hold it. The result says how many
  connected accounts it closed in `closedEnhancedReportingAccounts`. A period already earned stays billed. Switching
  back to a Storefront does not turn it on again.

* **Accepting a plan sets the type.** When an organization accepts a plan, its Seller accounts take the type the plan gives: a plan that includes the Storefront makes them Storefronts, and a Listing plan makes them Listings. Each change is recorded. A Listing plan is refused, with the same blockers, while Storefront-agent work is still running, and nothing about the plan or the account changes. A Demo Storefront keeps its fixed type.

* **Compare plans in Seller Settings does not change the type.** It only records which product you want to see plans for.
  The switch beside it is what changes the type.

* **Send `sellingMode` alone.** Together with any other `save_seller` field it is refused with `VALIDATION_ERROR`.

* **Nothing is deleted** by a switch to Listing. Your demand inbox, product marketing, pitch history and campaigns stay
  stored and return if you switch back.

## Enhanced Reporting on a Listing account

Enhanced Reporting cannot be turned on for a Listing account. The call to turn it on is refused with
`VALIDATION_ERROR` and the reason `listing_account`. The connected account's `enhancedReporting` state reads
`eligible: false` with `ineligibleReason: "listing_account"`. Campaign management accounts are not affected.
See [Set Enhanced Reporting](https://docs.apostra.com/v2/buyer/storefronts/tasks/set-enhanced-reporting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.