> 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/readme/migrate-from-producthero-to-channable/add-a-channable-supplemental-source-after-migrating-from-producthero.md).

# Add a Channable supplemental source after migrating from Producthero

If you moved from Producthero, you may already have a supplemental source in Google Merchant Center. After Channable merged with Producthero, your Producthero source URL continues to work for now. We will retire this URL in the future.

To future-proof your setup, create a Channable Google connection and supplemental source. Keep your existing Producthero supplemental source to avoid disruptions during the transition.

***

### <i class="fa-memo-circle-check">:memo-circle-check:</i> Before you start

**You'll need**

* Admin access to the relevant Google Merchant Center account.

**Good to know**

* Create a Channable source for each label and language combination.

{% stepper %}
{% step %}

### Create a Channable Google connection and copy the source URL

1. Go to **\[your company] > CSS Merchants**.
2. In the **CSS Connections** tab, click **Sign in with Google**.
3. Sign in with the Google account that has admin access to your merchant(s). This creates a future-proof Channable connection to Google.
4. In the **CSS projects overview** tab, locate the merchant for which you want to set up the supplemental source.
5. In the **Suppl. source exported** column, click the dropdown arrow.
6. For the relevant shop, click **Copy URL**.
   {% endstep %}

{% step %}

### Create a Channable supplemental source in Google Merchant Center

1. Log in to the Google Merchant Center account with admin access to the merchant.
2. In **Settings**, go to the **Data source setup** tab.
3. In **Supplemental sources**, click **Add supplemental product data**.
4. Select **Add product data from a file**.
5. Paste the URL you copied from Channable.
6. Select the matching feed label and language.
7. Select the relevant primary data source.
8. Click **Create data source**.
   {% endstep %}

{% step %}

### Fetch the Channable source and check its priority

1. In **Data sources > Supplemental source**, click <i class="fa-arrow-rotate-right">:arrow-rotate-right:</i> **Update** for the source you just added. Google Merchant Center then fetches the Channable data.

<figure><img src="/files/9xo6WAIKq7XuvsamM2Bv" alt=""><figcaption></figcaption></figure>

2. Return to **Data sources > Primary sources** and click your primary data source.
3. Go to the **Attribute rules** tab.
4. Confirm that Google Merchant Center reads from the Channable supplemental source first. It should use the legacy Producthero source as a backup.

<figure><img src="/files/sImNlnQEYMR7yUXZW6yq" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

Repeat these steps for every label and language combination.

### Related topics

* [Set up the supplemental source for your merchant in Google Merchant Center](/css/readme/set-up-the-supplemental-source-for-your-merchant-in-google-merchant-center.md)
* [How to set up a Channable CSS Merchant](/css/readme/how-to-set-up-a-channable-css-merchant.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpcenter.channable.com/css/readme/migrate-from-producthero-to-channable/add-a-channable-supplemental-source-after-migrating-from-producthero.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.