> 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/changelog/2026/september/single-connection-restriction-for-shopify-credentials.md).

# Single-connection restriction for Shopify credentials

September 23, 2026

### What’s changed

While previously you could set up multiple Shopify connections using the same credentials, Shopify authentication tokens and access keys now only support one active connection in Channable. 

This prevents duplicate connections from disconnecting existing Shopify connections.

### **Who's affected**

* **Affected:** Agencies or companies who create multiple Shopify connections that use the same credentials (duplicate connections) across companies and/or projects under the same Channable account 
* **Not affected:** Users who don’t use Shopify, or users reusing a Shopify connection across projects

### **Why we made this update**

Historically, creating duplicate Shopify connections across Channable projects or companies worked without issue. However, Shopify now enforces strict [single-use access token retirement](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens?).

Under this policy, creating a new Shopify connection automatically revokes any preexisting connections using the same credentials, which would break active product imports and channel exports relying on that connection. 

To protect your automated workflows from syncing disruptions, Channable now blocks duplicate Shopify connections at setup. 

For details on how Shopify manages application authorizations, see[ Shopify's documentation on Managing App Credentials](https://shopify.dev/docs/apps/build/authentication-authorization/manage-credentials?).

### How this affects your workflow

| **Scenario**                                                    | **Impact**                                                                                          | **Action required**                                                            |
| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Existing active duplicate Shopify connections                   | No current known impact. Your active connections are expected to continue to run normally.          | None.                                                                          |
| Creating additional Shopify connections within the same company | New enforcement: You can no longer create duplicate connections using the same Shopify credentials. | Select and reuse an existing Shopify connection instead of creating a new one. |
| Reusing Shopify credentials across different companies          | New enforcement: Credential sharing across companies is no longer supported.                        | Use different Shopify credentials for each company environment                 |

#### Troubleshooting disconnected imports

If your Shopify connection stopped working prior to this update due to a token conflict, re-authorize the connection by [renewing your connection](/get-started/getting-started/connections-in-channable/how-to-renew-a-connection.md).

<br>


---

# 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/changelog/2026/september/single-connection-restriction-for-shopify-credentials.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.