Shopify will require all public apps to replace non-expiring offline access tokens with expiring offline access tokens by January 1, 2027.
Celigo's Shopify - NetSuite integration app is a public app, so this requirement applies to affected Shopify connections. The following FAQs explain how the change affects your integrator.io accounts and Shopify connections.
I have multiple Shopify connections in my account. Do I need to consolidate my connections?
No. Consolidation applies to integrator.io accounts, not individual Shopify connections.
For example, if you use one Shopify connection for Orders and another for fulfillment flows, you can continue to use multiple Shopify connections to the same store within your primary integrator.io account.
I have multiple environments, such as Production and Sandbox. Are they affected?
You can continue to have Shopify connections in multiple environments under the same integrator.io account ownership.
If the same Shopify store has connections across environments in different integrator.io accounts, consolidate them into one primary integrator.io account in the same way as your Production setup.
Will the migration interrupt my flows or require me to reconnect?
Celigo exchanges the tokens on your behalf. No reinstall or additional work is required in your primary integrator.io account.
If all applicable Shopify connections for the store are already in one integrator.io account, no consolidation action is required.
We use both integrator.io accounts for different purposes. Do we have to close one?
No. You do not need to close the secondary integrator.io account.
Only the Shopify flows for the affected store in the secondary account must be disabled. The account itself can remain active for other integrations and purposes.
What happens to the flows and configurations in our secondary account?
The flows and configurations remain in the secondary integrator.io account, but the Shopify flows for the affected store must remain disabled.
If there are flows, configurations, or settings you still need, work with your Celigo account manager to move them to your primary account before October 20, 2026.
How does Celigo know which account is our primary account?
Celigo identifies the integrator.io account with active Shopify flows for your store as the account to migrate.
You select your primary account by disabling the Shopify flows in the other integrator.io account.
What happens after consolidation?
Once your store has a single integrator.io account with active Shopify flows, Celigo will migrate that account's Shopify connection to expiring offline access tokens on the updated Shopify connector.
Shopify flows in the secondary account must remain disabled. If you attempt to reactivate a Shopify flow for the same store in the secondary account, the reactivation will fail with an error.
We have more than one Shopify store. Does this apply to each store?
Yes. The one-account requirement applies to each Shopify store and Integration App combination.
Different Shopify stores can be managed from different integrator.io accounts. However, the same Shopify store should not have active connections for the same integration app across multiple integrator.io accounts.
What if we miss the October 20, 2026 deadline?
If your Shopify store still has active connections in more than one integrator.io account after October 20, 2026, only one integrator.io account can remain active for the same Integration App and Shopify store combination. The connection in the other account will go offline automatically after the migration go-live, currently targeted for around November 15, 2026.
Consolidate before the October 20 deadline so you can choose which integrator.io account remains your primary account.
If you miss the deadline or need assistance, contact your Celigo account manager as soon as possible.
Can I create connections for the same Shopify store in integrator.io accounts hosted in different regions, such as NA, EU, AU, CA??
No. For a given integration app and Shopify store combination, use only one integrator.io account, regardless of region.
Creating connections for the same integration app and store across multiple regional accounts is not supported under the one-account rule.