Comparisons
Celigo alternative: an integration built for your systems and run for you
Celigo is an iPaaS with managed Integration Apps, editable templates and a flow builder, priced by endpoints and flows. Its documentation is precise about what a template covers and what the customer sets up and maintains. A custom integration from us starts where those documented limits are: more than one price level, events instead of schedules, and no record skipped without a notice.
What Celigo does well
Celigo's integrator.io offers three layers on one platform, in Celigo's own terms. Integration Apps are managed products for common pairs: Celigo states they receive bug fixes, new functionality and settings, documentation and domain support, and that their managed components are locked so they can be upgraded. Integration templates are prebuilt flows that are fully editable after installation. Platform flows connect any endpoint. Templates install from the marketplace; Integration Apps are installed after requesting a demo.
The coverage is broad. The Shopify to NetSuite D2C template ships as 32 prebuilt flows, and the list goes further than most connectors:
| Flow group | Flows | What it covers |
|---|---|---|
| Orders and customers | 6 | orders both ways, customers both ways, customer deposits |
| Fulfillment, products, inventory | 10 | fulfillments both ways, matrix items, metafields, inventory, transfer orders |
| Billing and refunds | 4 | invoice or cash sale, refunds both ways |
| Returns, exchanges, cancellations | 6 | return authorizations, RMA receipt, exchanges, cancellations both ways |
| Payouts | 3 | Shopify payouts to custom records, reconciliation, bank deposits |
| Setup | 3 | store, markets, business entity |
For EDI, Celigo sells B2B Manager on the same platform and prices it by trading partners and document types rather than per transaction. Its implementation guide is specific about operations: recommended lags per flow, what to do on a Shopify THROTTLED error, batches of 100 to 250 items per inventorySetQuantities call, and a troubleshooting path from the flow dashboard to the source payload and error response. Pricing is metered in endpoints and active flows per edition, with no per-transaction charge.
Statements about Celigo on this page come from docs.celigo.com and celigo.com, read on October 3, 2026.
What an implementation asks of you
Celigo's D2C implementation guide is explicit about the setup on the customer's side before the order flow is enabled:
- NetSuite bundle 20038 for the base RESTlets, and bundle 81289, which deploys 30 saved searches plus custom records for the item ID map. The guide says not to rename, modify or delete any of these searches, because flows reference them by internal ID.
- Token-based authentication and a cloned integration role; an Administrator role is advised against.
- The Shopify store owner's login for the connection; a staff account cannot authorize it.
- A Celigo account with the Shopify to NetSuite connector license.
- Setup flows run in order, then the item ID map, then discount items created in NetSuite by hand.
Steps 5 and 6 are data modelling. Without the item ID map, the guide says, order imports fail because NetSuite cannot identify the item on each line. Without discount items, orders with discounts error at import. Both are tables someone on your side keeps current: a new variant needs a map record, a new kind of discount needs an item.
Where the documented limits are
Celigo documents its boundaries clearly. These are the ones that matter for a B2B or high-volume store:
| Area | What Celigo documents |
|---|---|
| Price levels | The D2C settings take one NetSuite price level for the selling price, one for compare-at, and one currency. A help article from April 2021 states that Celigo can only pass one price level at a time; further levels go through custom fields filled by a script |
| B2B customers and catalogs | A separate Shopify B2B template maps price levels to catalogs and company locations to sub-customers. Used next to the Integration App, B2B orders have to be filtered out of the app's order flow |
| Timing | Order flows are scheduled with a recommended lag of 10 to 15 minutes. With a 15-minute order lag and a 60-minute billing lag, the guide says, an order may take over an hour to appear as billed |
| Inventory | Location mapping is 1:1 or many to 1. A NetSuite item without a map record is skipped by the inventory sync silently |
| Recovery | A stuck delta after a paused flow is named as the most common cause of missing records after maintenance. Retrying in bulk before the cause is fixed can create partial records |
| Upkeep | Templates receive no bug fixes, new functionality or domain support after installation; they are yours to maintain |
| Sandbox | The pricing page lists a sandbox from the Professional edition up |
The B2B template states that its company flow needs Shopify Plus "as specified by Shopify". Shopify's own plan page now lists B2B companies on Basic, Grow, Advanced and Plus, with direct catalog assignment to company locations on Plus only, so check this point against both vendors for your plan.
Timing is the limit that shows up in day-to-day operations. A scheduled order flow running every 15 minutes with a 15-minute lag picks up an order placed at 10:02 on the run of 10:30: 28 minutes. At 500 orders an hour that is 8.3 orders a minute, so between 15 x 8.3 = 125 and 30 x 8.3 = 250 orders are in Shopify and not yet in NetSuite at any moment. The full comparison is on custom integration vs iPaaS.
What a custom integration does differently
We build the integration to your systems and your rules, then host and run it. The differences follow from that, point by point against the table above:
| Area | Custom integration, hosted and run |
|---|---|
| Price levels | Every NetSuite price level, quantity break and customer price mapped to Shopify catalogs and price lists in one integration |
| Timing | Orders arrive by webhook into a queue and are written to NetSuite within its concurrency limit; scheduled runs only for bulk data and a nightly comparison |
| Unmapped items | An item without a mapping goes to a review list with the reason; nothing is skipped without a notice |
| Recovery | Retries with growing pauses, a dead-letter queue with the original payload, replay after the cause is fixed; the store order ID travels as external ID so a retry finds the first order |
| Upkeep | We follow Shopify's quarterly API versions and NetSuite releases and change the integration when a source changes |
| Before go-live | A dry run against your real data, approval, exclusions and overrides, and a diff per run |
Required fields such as subsidiary, department, class and location are filled by rules written down per field, as described in required fields the source never sends. The order flow as a whole is on ecommerce ERP integration.
Moving off Celigo without a gap
A switch does not need a cut-over weekend. The new integration runs next to the Celigo flows with writes disabled: it reads the same orders, items and stock, computes what it would write, and its output is compared with what Celigo wrote. Differences show up without touching NetSuite or Shopify.
When the output matches, flows move over one record type at a time: stock first, then orders, then fulfillments and billing. The Celigo flow for that record type is switched off in the same step, so there is always one owner per record. Celigo's 32 flows also serve as a checklist of what has to move or stay, payouts and returns included. The Celigo bundles and saved searches stay in NetSuite until the last Celigo flow is off. How the parallel run works in general is in replacing an integration.
Tell us which Celigo flows you run and where they stop, and you get a fixed price for the integration that replaces them.
Frequently asked questions
Is SyncMyShop an iPaaS like Celigo?
No. Celigo is a platform on which you or a partner assemble and maintain flows. We build one integration for your systems and your rules, then host it, monitor it and change it when a source changes. You get a dashboard with logs, a dry run before go-live and a diff per run, not a flow builder.
Can we keep Celigo for some flows and move others?
Yes. A common split is to keep flows that work, such as payout reconciliation or EDI, and move the flows that hit a documented limit, such as B2B pricing or the order flow. The rule is one owner per record type: two integrations that both write sales orders or both write stock to the same item will overwrite each other.
What happens to the Celigo bundles and saved searches in NetSuite?
They stay until the Celigo flows that use them are switched off. Celigo states that its flows reference the 30 saved searches by internal ID and break if one is renamed or deleted. During a parallel run nothing of Celigo's is touched; the bundles are removed only after the last Celigo flow on that account is off.
Does a custom integration handle more than one NetSuite price level?
Yes. Every price level, quantity break and customer agreement that can be stated as a rule is mapped, and Shopify B2B catalogs are filled from them. Celigo documents one price level plus one compare-at level for its D2C template, and covers price levels per company in a separate B2B template.
How is a custom integration priced compared with Celigo?
Celigo prices by endpoints and active flows per edition and publishes no amounts. We charge a fixed price for the build and a monthly fee for hosting and running it, without a count of endpoints, flows or transactions. Tell us what you run and you get a fixed price for your setup.
Tell us what you need
Tell us which systems you use and what needs to work better. We reply personally within one working day. We help you define the work, then agree the price and timing before you commit.
- You know the price and the timeline before you commit to anything
- We work out the connection that takes the work off your hands
- We handle the build, hosting, monitoring and maintenance
- Your team has less information to retype and fewer discrepancies to chase