> 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/check-if-an-account-can-switch-to-channable-css.md).

# Check if an account can switch to Channable CSS

Find out why your Merchant Center account can't switch to Channable CSS, and what you can do next.

Google doesn't let some Merchant Center accounts switch to a CSS partner such as Channable. If your switch request fails, check whether your account matches one of the cases on this page.

{% hint style="info" %}
Where you advertise doesn't affect whether you can switch. To learn what changes when you advertise outside CSS program countries, see [Using Channable CSS outside CSS program countries](https://helpcenter.channable.com/css/before-you-start/channable-css-outside-css-program-countries.md).
{% endhint %}

### Common reasons

<details>

<summary>Your account is a marketplace sub-account</summary>

If your Merchant Center account is a sub-account in a marketplace's multi-client account (MCA), Google doesn't allow it to switch. An MCA is a Merchant Center account that manages several other accounts.

[Regular MCA sub-accounts can switch](https://helpcenter.channable.com/css/before-you-start/google-merchant-center-account-types.md). Channable detaches them from their MCA during the switch, because Google doesn't allow one MCA to use more than one CSS.

</details>

<details>

<summary>Your account is already switching to another CSS</summary>

After you approve a switch, your account enters a grace period before the switch completes. During that grace period, Google rejects new switch requests.

Wait until the earlier switch completes, then ask Channable to send a new switch request.

</details>

<details>

<summary>Your account has no admin user</summary>

Only a Merchant Center admin can approve a switch request. If your account has users but none of them is an admin, the switch fails.

To fix this, add an admin user to your Merchant Center account, then ask Channable to [send a new switch request](https://helpcenter.channable.com/css/setup/approve-a-switch-to-channable-css.md).

</details>

<details>

<summary>Your account runs Vehicle Ads</summary>

Vehicle Ads aren't part of the CSS program. Google requires a dedicated Merchant Center account for them, so an account with Vehicle Ads enabled can't switch to a CSS partner.

To use Channable CSS for your other products, keep your Vehicle Ads in their own Merchant Center account, then switch a separate account that holds your other products.

For details, see Google's [prerequisites for Vehicle ads in the EEA and the UK](https://support.google.com/merchants/answer/15560833).

</details>

### What you can still do <a href="#what-you-can-still-do" id="what-you-can-still-do"></a>

If your account can't switch, while you can't use Channable CSS, you can still use the optimization tools for your Google Shopping campaigns.

For the full list of switch requirements, see Google's [Switch merchant accounts between Comparison Shopping Services](https://support.google.com/css-center/answer/11144098).


---

# 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/check-if-an-account-can-switch-to-channable-css.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.
