Your Celigo Shopify–NetSuite connection did not stop on 1 November 2026. That was the date Celigo checked which integrator.io account each Shopify store was connected from. Stores connected from only one account are being moved to Shopify’s new expiring access tokens between 1 and 15 November, with nothing for you to do. Stores still connected from more than one account on 1 November were not migrated, and Celigo says their Shopify connection stops working on 1 January 2027. If your flows are failing already, the most likely cause is a second account, region or environment connected to the same store, because that takes the other connection offline with no warning.
We are ConversionsKing, a Shopify and Shopify Plus agency in Dubai that builds Shopify–NetSuite integrations. We are not a Celigo, Patchworks or Oracle NetSuite partner or reseller, so we have no reason to push you towards any of them. This guide is based on Celigo’s and Shopify’s public documentation at the time of writing (November 2026). It is general information, not contract advice: your Celigo account manager has the final word on your account.
Key takeaways
- Nothing switched off on 1 November. It was the date that decided which stores Celigo migrates. The hard stop for stores that missed it is 1 January 2027, according to Celigo.
- One store, one integrator.io account. Shopify allows only one active token per store, so the same store cannot have live Shopify connections in two Celigo accounts, regions or environments.
- The fix is usually small. Pick a primary account, move users and anything you still need into it, and disable the Shopify flows for that store in every other account, with your Celigo account manager.
- Do not change connectors in a panic. Consolidating keeps your orders flowing through White Friday and the holidays. Choose a replacement later, if you still want one.
- Alternatives exist. Oracle’s NetSuite Connector, an integration platform such as Patchworks, or a custom build all work. Each has a different owner and a different cost.
What exactly changed on 1 November 2026?
Shopify is changing how apps keep access to a store. In its developer changelog, Shopify says that from 1 January 2027 all public apps must use expiring offline access tokens when they call the Admin API. Until now, an app such as Celigo’s held a token that never expired. The new tokens expire and have to be refreshed.
Celigo’s Shopify–NetSuite integration app is a public app, so it has to move. Celigo’s 2026.11.1 release notes say:
- Shopify tokens now expire every 60 minutes, and integrator.io renews them automatically in the background.
- Celigo migrates eligible connections between 1 and 15 November 2026, before Black Friday and Cyber Monday, with no downtime and nothing to reinstall. This covers the integration app and custom flows that use Shopify OAuth 2.0 connections.
- Shopify allows only one active token per store, and renewing a token cancels the previous one. So each store can be connected from only one integrator.io account.
- If a store still had active Shopify connections in more than one integrator.io account on 1 November 2026, Celigo does not migrate it, and its Shopify connection stops working on 1 January 2027.
- If a connection is not used for about 90 days, its authorisation expires and someone has to reauthorise it.
The same warning now sits at the top of Celigo’s install guide. It adds that this includes accounts in different regions (North America, Europe, Australia and Canada), and that connecting the same store from a second account or region takes the existing connection offline with no warning.
Is my store affected?
Probably not, if your business has one integrator.io account and nobody has connected the store from anywhere else. Your connection migrates by itself, and all you need to do is check that flows still run after it does. You are affected if any of these is true:
- You have a production account and a separate sandbox or test account, and both connect to the same live Shopify store.
- You have accounts in two Celigo regions, for example one in North America and one in Europe, after a merger, a new subsidiary or a regional team setting up its own.
- A previous agency or implementation partner connected your store from its own integrator.io account, and the connection was never removed.
Several Shopify connections inside one account are fine. Celigo’s migration FAQ says the rule applies to accounts, not connections, and that production and sandbox connections can stay as long as they are under the same account. The rule also applies per store and integration app, so different stores can still live in different accounts.
Why did my Celigo Shopify flows stop working this month?
If orders stopped reaching NetSuite in November, check these causes in order:
| What you see | Likely cause | What to do |
|---|---|---|
| Connection offline straight after someone set up a new connection | The same store was connected from a second account, region or environment, which cancelled the first token | Decide which account is primary, disable the Shopify flows in the other one, then reauthorise the primary connection |
| Connection in one account went offline around mid-November | Celigo’s FAQ says that if a store stayed active in more than one account, the connection in the other account goes offline after the migration go-live, targeted for around 15 November | Confirm with your Celigo account manager which account was kept, and move anything you need into it |
| A connection asks to be reauthorised | It was not used for about 90 days, so its authorisation expired | Reauthorise it from the connection settings using the store owner’s login |
| Your own custom flows fail, but the integration app works | Celigo moved self-service Shopify OAuth connections to customer-owned Shopify apps on 15 October 2026 | Reauthorise those connections against your own app. Celigo’s changelog says the shared public app stays available as a fallback only until mid-December 2026 |
| Errors on specific orders, not the whole connection | Probably not the token change: mapping, missing items, tax codes or locations | Read the error in integrator.io before you touch the connection |
Celigo’s documents do not fully agree: the September FAQ mentions a 20 October deadline and connections going offline around 15 November, while the November release notes give 1 January 2027. Treat 1 January as the latest possible date, not a safe one.
How do I fix it inside Celigo?
Celigo’s release notes list the steps. You cannot do all of them yourself, so contact your Celigo account manager first.
- List every integrator.io account that touches the store: production, sandbox, every region, and any account owned by a current or former partner. Ask your partners directly. You cannot see their accounts.
- Choose the primary account. Usually it is the one that holds your production flows, settings and error history. Celigo’s FAQ says it treats the account with active Shopify flows for the store as the one to migrate.
- Move what you need. Add users from the secondary account to the primary one. If the secondary account has flows, mappings or settings you still use, ask Celigo to help move them.
- Disable the Shopify flows for that store in every other account. If it makes sense, uninstall the integration app there too. You do not have to close the other account. It can keep running other integrations.
- Ask Celigo to confirm in writing when the store will be migrated.
- Check the flows after migration. Place a test order, refund it, and check that the sales order, fulfilment, refund and inventory all reach NetSuite.
- Stop the problem coming back. Write down which account owns the store, and tell partners and new team members never to connect the store from their own account. Do not try to switch a Shopify flow back on in the secondary account: Celigo says it will fail.
If a partner needs Shopify access to check the set-up, use a collaborator account, not your login. Our collaborator account guide shows how.
Should I leave Celigo instead?
Maybe, but not this month. Moving an ERP integration during White Friday, Black Friday and the year-end rush puts orders and month-end at risk. Consolidate first so the current setup keeps running past 1 January, then compare options in a quiet quarter.
Shopify has also relaxed its own timeline. Its 27 October 2026 update says apps that miss 1 January are removed from the App Store and blocked from new installs, and that Admin API calls with non-expiring tokens return errors from 1 April 2027. Do not count on that extra time. Celigo’s own documents give 1 January 2027 for its connections, and that is the date to plan for.
What are the alternatives to Celigo for Shopify and NetSuite?
| Option | Who maintains it | Good fit when | Watch out for |
|---|---|---|---|
| Fix your Celigo setup | Celigo maintains the app, you or a partner maintain the flows | The integration works and only the account set-up was wrong | The same mistake happens again unless one account clearly owns the store |
| Oracle NetSuite Connector | Oracle | One subsidiary, standard orders, inventory and fulfilment | Less room for unusual flows; added through your NetSuite account manager |
| Integration platform such as Patchworks | The vendor maintains the platform; a partner or your team the flows | Shopify, NetSuite plus a 3PL, marketplaces or other systems | Another licence and another vendor; pricing is quoted, not published |
| Custom build | You own the code; your developer or agency maintains it | Several subsidiaries, B2B, complex VAT or payouts, flows no template covers | You need someone to monitor and support it for years |
Oracle’s NetSuite Connector is the product Oracle gained when it acquired FarApp. Its Shopify set-up guide says you ask your NetSuite account manager to add the Shopify connector, then authorise your store from the connector’s console. If you already pay Oracle and your flows are standard, it is worth a quote.
Patchworks is an integration platform with a Shopify–NetSuite integration. It suits brands that connect several systems and want one place to watch them. Like Celigo, it is a platform, so you still need someone to own the flows.
A custom build uses Shopify’s Admin GraphQL API and NetSuite’s REST web services, ideally through a custom Shopify app that belongs to your store. Shopify lists custom apps as outside this token change, though your developer still has to look after credentials properly. Oracle’s SOAP removal plans mean any new build should use REST, not SOAP. We compare all of these in more depth in Shopify NetSuite connector vs custom integration, and the costs in how much a NetSuite Shopify integration costs.
How do I switch connectors without losing orders?
If you do decide to move, run it as a proper project:
- Write down every flow you have today: orders, customers, items, inventory, fulfilments, refunds, returns and payouts.
- Get finance to sign off the mapping: tax codes, payment methods, subsidiaries, locations and the order fields that reach NetSuite.
- Build and test in a NetSuite sandbox with real order types: discounts, partial refunds, split shipments and cash on delivery.
- Pick a cutover point, such as a quiet day after month-end, and decide which system handles orders placed during the switch.
- Switch, then disable the old flows. Do not leave two systems writing to NetSuite, or you will get duplicate sales orders.
- Monitor for a full month-end close before you call it done.
Our Shopify NetSuite integration checklist covers each step in more detail.
When you do not need us
If you have one integrator.io account, nobody else ever connected your store, and your flows run, you do not need anyone: Celigo migrates you automatically. If you have two accounts and a responsive Celigo account manager, consolidation is mostly admin. Bring in outside help when nobody on your side knows how the integration was set up, when a former partner holds the only working account, or when you are seriously thinking about replacing the connector.
FAQ
Did Celigo stop working with Shopify on 1 November 2026?
No. 1 November was the date that decided which stores Celigo migrates to Shopify’s expiring tokens. Stores connected from one integrator.io account are migrated automatically between 1 and 15 November. Stores connected from more than one account were not migrated, and Celigo says their connection stops on 1 January 2027.
I missed the deadline. Is it too late?
Not necessarily. Contact your Celigo account manager now, consolidate to one primary account, and ask them to confirm in writing when your store will be migrated. Do it well before late December.
Do I need to reinstall the Shopify–NetSuite integration app?
No. Celigo says the migration needs no reinstall and causes no downtime for eligible stores. After it runs, place a test order and refund to check your flows.
What is the best alternative to Celigo for Shopify and NetSuite?
For one subsidiary and standard flows, Oracle’s NetSuite Connector is usually the simplest. For many connected systems, an integration platform such as Patchworks. For several subsidiaries, B2B or complex tax, a custom build you own. Our guide to choosing a Shopify NetSuite integration partner helps you pick.
If you are not sure whether your store is affected, or the cutoff has you rethinking the whole integration, our free NetSuite Shopify integration assessment maps your current flows and accounts and tells you honestly whether to fix Celigo, move to another connector or build custom. You can also see how we build it on the Shopify NetSuite integration page.
