Somewhere in your NetSuite account there is probably a role called Celigo eTail SmartConnectors. Someone on your team has seen it, searched the term, and come back confused, because Celigo's own website barely uses the word anymore.
That confusion is the reason a lot of Celigo projects start with the wrong question. Teams sit down to decide between a SmartConnector and integrator.io as if they were two competing products on a shelf. They are not. One runs on the other.
So before you can make the decision that actually matters, it helps to clear up what these things are.
What Celigo Actually Sells
Celigo is an iPaaS, an integration platform as a service. It sits between your systems and moves data between them, so your ERP, your storefront, your CRM, and your logistics provider all hold the same version of the truth without anyone exporting a spreadsheet.
Underneath everything Celigo offers is one platform: integrator.io. That is the engine. It handles connections, flows, field mapping, transformation logic, scheduling, error handling, and monitoring.
On top of that engine, Celigo ships pre-built packages for common system pairings. A Shopify to NetSuite package. An Amazon to NetSuite package. A Salesforce to NetSuite package. These arrive configured for the typical use case, so you install rather than build.
Those packages used to be called SmartConnectors. In 2019 Celigo renamed them Integration Apps, and said plainly why: the change was made to establish more clearly that the pre-built apps are built on integrator.io. The old name suggested a separate product. The new name reflects the reality, which is that an Integration App is a pre-configured application running on the platform.
The name change never fully landed. NetSuite bundles and role names still carry the old wording, older documentation still uses it, and consultants still say it out of habit. So if you hear SmartConnector, translate it to Integration App and carry on.
Why the "Versus" Framing Leads Teams Astray
Once you know that Integration Apps run on integrator.io, the comparison collapses. Asking whether you need a SmartConnector or integrator.io is like asking whether you need an app or a phone.
This matters more than it sounds, because the false comparison hides the real question. Teams end up debating products when they should be interrogating requirements. They pick the pre-built app because it sounds cheaper, discover three months later that it cannot express a rule their business depends on, and end up paying for custom work anyway on top of an implementation that already happened.
The genuine decision is not which product. It is how much of your integration is standard, and how much is yours.
The Decision That Actually Matters: Pre-Built or Custom
Every integration project sits somewhere on a line between these two poles, and most sit at neither end.
Where a pre-built Integration App wins
If you are connecting two common systems in a common way, the pre-built app is almost always the right starting point. Shopify orders into NetSuite. Amazon settlements into NetSuite. Salesforce opportunities into NetSuite. These are solved problems, and Celigo has solved them thousands of times.
You get speed, because installation and configuration replace design and development. You get lower build cost. And you get something people underestimate: Celigo maintains the app. When Shopify changes its API or NetSuite ships a release that alters record behaviour, the app is updated centrally. A custom flow doing the same job is your problem to fix.
Where a custom flow in integrator.io wins
Custom flows earn their cost when your business logic is genuinely yours. Multi-subsidiary consolidation with rules specific to your group structure. A pricing or discount model that does not map to standard fields. A three-way reconciliation across systems the pre-built apps do not pair. Anything where the answer to "how does this work at your company" is a paragraph rather than a sentence.
The trade is straightforward. More flexibility, more build cost, more ownership of maintenance.
Where most businesses actually land
In practice the majority of Celigo projects are hybrid. You install the Integration App for the standard flows, then build custom flows in integrator.io for the parts of your operation that do not fit the template. That is not a compromise or a failure of planning. It is the normal shape of a well-scoped integration, and it is why the versus framing is unhelpful. You are rarely choosing. You are deciding the ratio.
Getting that ratio right at the start is where the money is made or lost. Scope it accurately and the Celigo integration project lands in the two to eight week range. Assume everything is standard and you discover the exceptions during testing, which is the most expensive moment to find them.
| Pre-Built Integration App | Custom integrator.io Flow | |
|---|---|---|
| Best for | Common system pairings with standard logic | Business-specific logic that does not fit templates |
| Speed to go live | Fast: install and configure | Slower: design, build, and test |
| Build cost | Lower upfront | Higher upfront |
| Maintenance | Managed by Celigo | Managed by your team or partner |
| Flexibility | Limited to what the app supports | Fully configurable |
| Typical use case | Shopify to NetSuite, Amazon to NetSuite | Multi-subsidiary rules, custom pricing, complex reconciliation |
When the Answer Is Not Celigo at All
Worth saying honestly, because it comes up: sometimes neither option is right.
If your requirement is deeply embedded in NetSuite's own logic, involves complex record-level behaviour, or needs to run inside NetSuite rather than between systems, custom NetSuite integration development may serve you better than any iPaaS flow. Celigo is excellent at moving data between systems. It is not the right tool for logic that belongs inside one.
Equally, if you are weighing Celigo against another platform entirely, that is a different evaluation with different criteria around governance, scale, and cost profile.
The point is that a good scoping conversation should be willing to reach any of these conclusions, including the one that sells you less.
How to Scope the Decision Properly
A few questions settle most of this before anyone touches a configuration screen.
Which systems are you connecting, and does Celigo publish an Integration App for that exact pairing? If yes, that is your baseline.
Where does your process differ from how most companies run the same process? Every one of those differences is a candidate for a custom flow. Write them down early.
What happens at the edges? Returns, partial fulfilments, cancellations, currency handling, tax rules. Standard apps cover the happy path well. Edge cases are where custom work usually appears.
Who maintains this in twelve months? If the answer is nobody in particular, weight the decision towards pre-built, because maintained-by-Celigo beats maintained-by-no-one.
Conclusion
There is no contest between Celigo Integration Apps and integrator.io, because one runs on the other. The word SmartConnector is a leftover from before 2019 that survives in bundle names and habit, and it has quietly confused a lot of buying conversations.
The decision worth spending time on is how much of your integration is standard and how much is specific to your business. Get that ratio right during discovery and the build is predictable. Get it wrong and you find out during testing, when changing course costs the most.
That assessment takes an hour or two with someone who has scoped the same decision many times. It is a small investment against the cost of finding out late.
