kingfisher systems
Menu

Integration platforms

iPaaS or custom integration?

For a business connecting Shopify to an ERP, a warehouse, a wholesale portal or the accounts, and weighing Celigo, Jitterbit and Patchworks against a connection built for it. Ten needs scored on what keeps an integration working after launch, not on the length of the connector list.

At a glance

Overall integration fit

A higher score means a closer fit. These are our assessments, not measured benchmarks or averages.

  1. Patchworks

    Shopify stacks covered by its connectors, with built in deduplication, tracking and scripting.

    4 / 5
  2. Celigo

    NetSuite operations needing managed apps and error recovery. Confirm hosting and retention in the quote.

    3.75 / 5
  3. Custom integration

    Unusual rules or missing connectors, with reconciliation and ownership designed around your records.

    3.75 / 5
  4. Jitterbit

    Larger systems with varied connectors and managed or private agents. Recovery depends on the workflows you build.

    3.25 / 5

Ten needs, four options

Scores by integration need

Swipe to compare. The first column stays visible.

Integration platform comparison: integration needs by option, shown as a score out of five with short notes.
Integration needPatchworksCeligoCustom integrationJitterbit
Prebuilt connectors
4 / 5
  • Shopify GraphQL, NetSuite, Cin7, Brightpearl and Xero connectors
  • Confirm coverage for your exact warehouse, shipping and finance systems
4 / 5
  • Shopify to NetSuite app plus a broad connector library
  • Confirm coverage for your exact systems, records and API versions
1.5 / 5
  • Nothing prebuilt
  • Each connection is written for the API you actually use
4 / 5
  • Connectors for Shopify, NetSuite, Xero, MYOB and ShipStation
  • Confirm the Shopify API version and operations required
Unusual business rules
4.5 / 5
  • Scripts in seven languages plus try, catch, route and cache shapes
  • Script authoring depends on role and tier
3 / 5
  • JavaScript hooks have a 4 second processing limit per invocation and 120 seconds of API calls per flow run
  • Server side hooks are another option
5 / 5
  • Business rules implemented around the APIs and data available, with tests
3.5 / 5
  • Jitterbit Script and JavaScript
  • JavaScript is not supported inside transformations
Data mapping
4 / 5
  • Automatic mapping from tagged fields, manual rules and transforms
  • AI mapping is metered in tokens
4.5 / 5
  • Mapper 2.0 with lookups and AI mapping that leaves manual mappings alone
3.5 / 5
  • Mappings live in code and tests, readable to a developer rather than in a mapping screen
3.5 / 5
  • Side by side mapping, automapping, conditional rules and a Data Mapping AI Assistant
Error handling
4 / 5
  • Try and catch paths, automatic retries and retry from run logs
  • Test partial failures and repeated runs
4.5 / 5
  • Error dashboards, automatic retries, tagging and assignment
  • Confirm retry timing and recovery for each flow
4 / 5
  • Retries, held records and alerts designed for each flow
  • They exist only if they are built
2.5 / 5
  • On fail chaining and email notifications
  • Design and demonstrate retry behaviour for the selected connectors
Reconciliation
4 / 5
  • Track data shape made for comparing inbound and outbound records
  • Tracked data is kept 15 days, 90 on request
2.5 / 5
  • Trace keys and flow event exports support investigation
  • Demonstrate how source and destination records will be compared
4.5 / 5
  • Run summaries and source to destination checks built for the records that matter
2.5 / 5
  • Operation logs count source and target records
  • Define the comparison and exception report the team needs
Change management
3.5 / 5
  • Draft, deployed and inactive versions with virtual environments
  • Confirm the review and rollback process
4 / 5
  • Revisions, diffed pulls and snapshots
  • Standard is production only and sandbox costs extra
4 / 5
  • Version control, staging and releases of your choosing
  • The discipline is yours to keep
3.5 / 5
  • Environments and project migration
  • A migrated schedule is enabled by default on first deploy
Ongoing ownership
3.5 / 5
  • Role based access with self serve or supported onboarding
  • Confirm who can administer the account
3.5 / 5
  • Roles scoped by environment and integration
  • Complex rules may need JavaScript
3 / 5
  • A developer relationship for changes
  • No licence tier, and no vendor roadmap either
3 / 5
  • Managed cloud agents, or private agents where needed
  • Confirm connector support, access roles and maintenance responsibilities
Operational visibility
3 / 5
  • Run logs and a queue view
  • Run logs kept 7 days, payloads 72 hours
4 / 5
  • Dashboards and three levels of execution logs, kept 30 days by default and up to 180
3.5 / 5
  • Logs and dashboards as designed, kept as long as you decide
  • Nothing arrives by default
3.5 / 5
  • Runtime view, dashboard and operation logs with payloads, kept 30 days
Speed of initial delivery
4 / 5
  • Blueprints install flows, scripts and lookups for Shopify with NetSuite, Brightpearl and Peoplevox
4 / 5
  • Integration apps and quickstart templates that the docs say still need modifying
2.5 / 5
  • Slower to the first flow than a template
  • Faster where no connector exists
3.5 / 5
  • Marketplace recipes and Shopify templates for NetSuite, Dynamics and Epicor
  • Annual contract
Avoiding missing or duplicate records
4.5 / 5
  • Dedupe shape with retained data pools and an optional atomic mode for concurrent flows
  • Atomic mode is off by default; test retries and partial writes
3 / 5
  • Error trace keys and automatic resolution help recovery
  • Demonstrate duplicate prevention on retries and partial writes
4.5 / 5
  • Idempotency keys, a record of what was processed, and reruns that know about both
2 / 5
  • Upsert and chunking controls
  • Demonstrate duplicate prevention and missing record checks in the selected Studio workflow
Overall integration fit
4 / 5
3.75 / 5
3.75 / 5
3.25 / 5

Sources and pricing

Platform features are assessed from vendor documentation; the custom integration column describes the approach we build for clients.

Integrations in practice

Connected retail systems in practice

ELK's retail systems connect Shopify, NuORDER, Datapel and ShipStation. Bicycle Superstore's dispatch connects Shopify, Starshipit and Retail Express.

Work directly with Chris

Platform or custom? Describe the workflow

Tell us the systems involved and describe a redacted or fictional example order. Chris will look at it and reply with which approach fits and why.

Discuss your project