We are already on NetSuite Connector. Should we move to Patchworks?

Not necessarily. If your estate is one or two of its supported channels, your mappings are standard, and you have no plans to add a 3PL, PIM, returns platform or second ERP, staying on NetSuite Connector is reasonable. We are happy to run an integration audit before you decide; the fee is credited against any project work that follows within 30 days.

Why might we choose NetSuite Connector over Patchworks?

If you want one vendor for ERP and integration, the canonical channels are all you need, and your mappings are standard, NetSuite Connector keeps the relationship simple. The product is owned and supported by NetSuite, sold through the same licence, and the NetSuite ecosystem understands the configuration shape. For a self-contained NetSuite-to-Shopify or NetSuite-to-Amazon shop with no surrounding systems, it is a clean choice.

Why might we choose Patchworks over NetSuite Connector?

Because your estate is more than NetSuite plus a storefront. If you have or are planning a WMS, a 3PL, a PIM, a returns platform, a marketing automation tool, a helpdesk with order context, a marketplace aggregator or a BI warehouse, Patchworks covers them as first-class flows. The same is true if you have non-standard NetSuite mappings (custom record types, OneWorld subsidiary routing, gift cards, B2B price lists) or run materially outside the US tax footprint NetSuite Connector was built around.

Can you migrate us from NetSuite Connector to Patchworks?

Yes. The shape is a fixed-fee integration audit first (current channel inventory, custom mappings, SuiteScript and customisation around the connector, dependency map, deviations from out-of-the-box), then a delivery engagement on Patchworks against the agreed scope. Cutover is endpoint by endpoint with parallel-running so trading does not stop. The audit fee is credited in full against the delivery work if you commission it within 30 days.

Comparison · iPaaS

Patchworks vs NetSuite Connector.
Where each one fits.

NetSuite Connector (formerly FarApp) is Oracle's own integration product for connecting NetSuite to the major ecommerce platforms and marketplaces. Patchworks is a specialist ecommerce iPaaS delivered by a Partner Agency. They overlap on the obvious canonical pattern (Shopify or Amazon into NetSuite) and diverge on everything that sits around it. This page is the honest read on which one fits which estate, written by an agency that ships NetSuite integrations on Patchworks every working day and has audited NetSuite Connector estates as part of customer engagements.

The honest summary

Where NetSuite Connector wins. Where Patchworks wins.

NetSuite Connector is the better fit when

NetSuite Connector is the stronger choice when the merchant has exactly one ERP (NetSuite), exactly one or two of its supported channels, no significant custom logic, and wants the integration purchased, supported and renewed inside the NetSuite licence. Single throat to choke, same support contract as the ERP, and a known configuration shape that the NetSuite ecosystem understands. For a clean Shopify-to-NetSuite store with standard mappings and no plans to add a 3PL, PIM or returns platform later, it is a perfectly reasonable choice.

Patchworks is the better fit when

Patchworks is the stronger choice for estates that are not exclusively NetSuite-to-channel. The connector library covers WMS and 3PL (Descartes Peoplevox, Veeqo, ShipBob, GXO, Bleckmann), PIM (Akeneo, Salsify, Plytix), returns (ReturnGO, returnless), search (Algolia, Bloomreach), helpdesk (Zendesk, Gorgias) and around 100 more platforms NetSuite Connector does not touch. Custom mappings are first-class flows rather than professional-services exceptions. The estate stays independent of NetSuite's licensing posture, so an ERP change later does not detonate the integration layer. Partner-Agency delivery, transparent flow inventory and an SLA-backed support retainer round it out.

What NetSuite Connector is

NetSuite Connector, fairly characterised.

NetSuite Connector is a NetSuite-owned SuiteApp that connects NetSuite to a fixed catalogue of ecommerce and marketplace platforms: Shopify, Amazon Seller Central, Walmart, eBay, BigCommerce, Magento and a handful of others. It started life as FarApp, founded in 2014 by ex-NetSuite engineers, and was acquired by Oracle around 2021 and rebranded. The product is sold through the NetSuite licensing channel, supported by NetSuite directly, and configured inside NetSuite as a series of channels with mappings onto standard NetSuite records.

By dimension

8 dimensions, side by side.

Both columns are framed in the most generous light for their respective platforms. The comparison is about fit, not about claiming an absolute winner.

Ownership and support model

NetSuite Connector
Owned and supported by NetSuite (Oracle). One vendor relationship for ERP and integration; one support contract; one renewal cycle. Single throat to choke is genuine when NetSuite is the centre of the universe.

Patchworks (with eCirql)
Independent iPaaS platform delivered by a certified Partner Agency. Support contract is with the agency on a defined SLA; the platform vendor sits behind the agency rather than in front of the merchant.
Channel and connector breadth

NetSuite Connector
Fixed catalogue centred on canonical NetSuite-to-channel pairs: Shopify, Amazon, Walmart, eBay, BigCommerce, Magento, plus a handful more. No coverage of WMS, PIM, returns or marketing tooling.

Patchworks (with eCirql)
Around 100 connectors covering ecommerce, ERP, WMS, 3PL, marketplaces, PIM, returns, search, helpdesk, marketing, accounting and data. Designed for estates that span more than NetSuite and a storefront.
Build paradigm

NetSuite Connector
Channel-based configuration inside NetSuite, mapping channel records onto NetSuite records. Custom logic outside the configured surface area becomes a NetSuite professional-services or SuiteScript engagement.

Patchworks (with eCirql)
Process flows authored by a Partner Agency in Patchworks. Canonical patterns cover the common shapes; flows are tuned to the merchant's actual data shape. Custom logic, branching and enrichment are first-class, not paid extras.
ERP coupling

NetSuite Connector
NetSuite-only by design. The product exists to connect NetSuite to channels. If NetSuite is replaced, the integration is replaced. The same is true if a second ERP joins the estate.

Patchworks (with eCirql)
Vendor-neutral. NetSuite is one ERP among several supported at depth (also Sage 200, Microsoft Dynamics Business Central, Brightpearl, Odoo). An ERP migration later does not require rebuilding every channel flow.
Custom mapping and edge cases

NetSuite Connector
Standard mappings work cleanly; non-standard mappings go through SuiteScript, custom record types or workarounds. Each customisation becomes its own thing the merchant has to maintain alongside the connector.

Patchworks (with eCirql)
Per-merchant data mapping is the normal mode of operation. Gift cards, deferred revenue, multi-currency rounding, OneWorld subsidiary routing, B2B price lists, custom transaction fields and Patchworks-side enrichment all live in flow.
Adding a new system later

NetSuite Connector
Anything outside the supported channel list lives outside NetSuite Connector. The merchant ends up with NetSuite Connector for the canonical channels and a second integration tool for everything else, which defeats the single-vendor pitch.

Patchworks (with eCirql)
Adding a WMS, a returns platform, a PIM, a second sales channel or a BI warehouse is a new flow in the same canvas. The integration estate grows; the architecture does not change.
Geography and tax

NetSuite Connector
US-built. Strong coverage of US tax patterns and major US marketplaces. UK and EU edge cases (OSS, postponed VAT, reverse-charge, multi-rate VAT groups) are workable but tend to need the NetSuite consultant to step in.

Patchworks (with eCirql)
UK-headquartered with strong UK, EU, US and APAC coverage. Multi-currency, multi-locale, EU OSS and UK MTD VAT handling are first-class. Designed for retailers operating across regions.
Pricing and licensing

NetSuite Connector
Per-channel licensing inside the NetSuite contract. Pricing is opaque outside a NetSuite quote. Renewal cadence and price increases follow the wider NetSuite contract rather than being negotiated separately.

Patchworks (with eCirql)
Subscription on Patchworks tiered by process-flow count and event volume. Partner-Agency delivery and support retainers are separate, transparent line items.

The eCirql delivery angle

Whichever iPaaS, the team is the variable.

We deliver NetSuite integrations on Patchworks because the partner-built flow model fits real retail estates better than a fixed-channel SuiteApp. When the estate is genuinely just one Shopify store talking to one NetSuite account with no custom mappings, we will tell you NetSuite Connector is a reasonable choice and worth costing against a Patchworks build. When the estate has a WMS, a PIM, a returns platform, a second channel or non-standard NetSuite fields, the Patchworks build pays back across the long tail of changes the business will ask for over the next three years. We also audit and migrate NetSuite Connector estates onto Patchworks where merchants have outgrown the supported configuration surface.

For the depth of our Patchworks delivery practice specifically, see the Patchworks integration service page and the buyer guide on choosing a Patchworks Partner Agency.

Start with an Integration audit Talk to us

Questions

Common questions.

01 We are already on NetSuite Connector. Should we move to Patchworks?

Not necessarily. If your estate is one or two of its supported channels, your mappings are standard, and you have no plans to add a 3PL, PIM, returns platform or second ERP, staying on NetSuite Connector is reasonable. We are happy to run an integration audit before you decide; the fee is credited against any project work that follows within 30 days.
02 Why might we choose NetSuite Connector over Patchworks?

If you want one vendor for ERP and integration, the canonical channels are all you need, and your mappings are standard, NetSuite Connector keeps the relationship simple. The product is owned and supported by NetSuite, sold through the same licence, and the NetSuite ecosystem understands the configuration shape. For a self-contained NetSuite-to-Shopify or NetSuite-to-Amazon shop with no surrounding systems, it is a clean choice.
03 Why might we choose Patchworks over NetSuite Connector?

Because your estate is more than NetSuite plus a storefront. If you have or are planning a WMS, a 3PL, a PIM, a returns platform, a marketing automation tool, a helpdesk with order context, a marketplace aggregator or a BI warehouse, Patchworks covers them as first-class flows. The same is true if you have non-standard NetSuite mappings (custom record types, OneWorld subsidiary routing, gift cards, B2B price lists) or run materially outside the US tax footprint NetSuite Connector was built around.
04 Can you migrate us from NetSuite Connector to Patchworks?

Yes. The shape is a fixed-fee integration audit first (current channel inventory, custom mappings, SuiteScript and customisation around the connector, dependency map, deviations from out-of-the-box), then a delivery engagement on Patchworks against the agreed scope. Cutover is endpoint by endpoint with parallel-running so trading does not stop. The audit fee is credited in full against the delivery work if you commission it within 30 days.

Get in touch

Tell us what you’re trying to connect.

And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.

Direct: contact@ecirql.com