> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/css/before-you-start/google-merchant-center-account-types.md).

# Google Merchant Center account types

Learn about Google Merchant Center account types, billing, and adding accounts to Channable CSS.

Google Merchant Center has three types of account. Your account type decides how you add it to Channable CSS and how you're billed.

### Account types

<figure><img src="https://channable-test.gitbook.io/channable-test-docs/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FF8GepmoSonQRG6RnHOxJ%2Fblobs%2FNjAOSXQc2pQrMOebyBRp%2F21018541998738&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=69ba4186&#x26;sv=2" alt="" width="375"><figcaption></figcaption></figure>

<details>

<summary>Standalone account</summary>

A standalone account is a Merchant Center account where all operations take place.

* **Billing:** It's charged per account, so an account that sells in several countries still counts once.
* **How to add**: Connect the Google account or add the merchant ID manually.

</details>

<details>

<summary>Multi-client account (MCA)*</summary>

A MCA, also known as an advanced account setup, is a special type of parent Merchant Center account that can have multiple subaccounts.

It's used to manage different Merchant Center accounts with shared settings across all subaccounts.

* **Billing:** Each active sub-account in the MCA is charged at your plan's price. The MCA itself is free. If you use a sub-account per country, each country's sub-account counts separately.
* **How to add:** Connect the MCA's Google account or add the merchant ID manually. It's linked together with all its sub-accounts.

{% hint style="info" %}

#### When a sub-account is considered inactive

A sub-account is inactive if it hasn't had any paid clicks in the last 30 days. Inactive sub-accounts aren't billed. For prices, see [CSS pricing](/account-billing/manage-your-subscription/channables-pricing-plans/css-pricing.md).
{% endhint %}

</details>

<details>

<summary>(Multi-client) Sub-account</summary>

An account inside an MCA. It inherits some settings from its parent.

* **Billing:** Charged as part of its MCA, [if it's active](#multi-client-account-mca). If detached from the MCA, it will be charged as a [standalone account](#standalone-account).
* **How to add:** Add the MCA account.

</details>

{% hint style="info" %}
For more detailed information about Google Merchant Center accounts, refer to [Google's Help Center](https://support.google.com/merchants/answer/13438603?hl=en).
{% endhint %}

### Add an MCA

When you add an MCA, we ask you to confirm that all its sub-accounts will be added too. Only active sub-accounts are billed.

<figure><img src="https://channable-test.gitbook.io/channable-test-docs/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FF8GepmoSonQRG6RnHOxJ%2Fblobs%2FzSzsMNbmdnlVFJVUKwEM%2F22053253172370&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=ec657c29&#x26;sv=2" alt="MCA invitation dialog. Select I understand, invite the MCA, then Continue."><figcaption><p>MCA invitation. Select I understand, invite the MCA, then Continue.</p></figcaption></figure>

{% hint style="info" %}

#### Want to only add some sub-accounts?

You can add their Merchant Center IDs instead, but this will [detach them from the the MCA](#add-a-sub-account-without-its-mca).
{% endhint %}

### Add a sub-account without its MCA

Google doesn't allow more than one CSS within the same MCA. So if you add a sub-account whose MCA isn't in Channable, you have two options:

<figure><img src="https://channable-test.gitbook.io/channable-test-docs/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FF8GepmoSonQRG6RnHOxJ%2Fblobs%2FFMQnaed7Ih2SKTtMX7Jx%2F22053253182610&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=2836b83e&#x26;sv=2" alt="MCA not active in Channable CSS dialog, with options to cancel or to detach the sub-account and continue"><figcaption><p>MCA not active in Channable CSS message. Shows options to cancel or to detach the sub-account and continue.</p></figcaption></figure>

* **Add the whole MCA instead.**
* **Detach the sub-account.** Choose **Detach and continue**. The sub-account leaves its MCA and becomes a standalone account, and we invite it to Channable CSS.

{% hint style="danger" %}

#### **Warning**

Before you detach a sub-account, check:

* **User access -** People who reach the sub-account through the MCA will lose access when it's detached. Make sure to add at least one user directly to the sub-account first to avoid being locked out after transferring. You can't use an email address that's already a user on the MCA.
* **Settings -** Some settings exist only on the MCA. After detaching, you may need to set them up again on the account itself.
  {% endhint %}

#### Approving the CSS Switch <a href="#approving-the-css-switch" id="approving-the-css-switch"></a>

To finalize the CSS switch, administrators of your Google Merchant Center account must approve it. The approval process varies based on your account type (Standalone, MCA, or subaccount).

For more details, please refer to [Approve the switch to Channable CSS](/css/setup/approve-a-switch-to-channable-css.md).


---

# 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://helpcenter.channable.com/css/before-you-start/google-merchant-center-account-types.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.