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.
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.
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.
Last updated
Was this helpful?