Contents9 sections ↓
"NetSuite connector" means two different things depending on who says it. Oracle sells a product called NetSuite Connector, the integration service it bought with FarApp in 2021. Everyone else uses the phrase for any prebuilt link between NetSuite and another system, from a Celigo integration app to a SuiteApp. This guide covers Oracle's product first, because that is what most people searching the term are evaluating, then places it next to the alternatives.
Direct answer: NetSuite Connector is Oracle's own prebuilt integration product (formerly FarApp) that syncs orders, products, inventory, fulfillments and refunds between NetSuite and Shopify, BigCommerce, Adobe Commerce, WooCommerce, Amazon, eBay, Walmart, ShipStation, Salesforce and several POS systems on fixed schedules. Oracle sells it as an add-on module with no published price.
What NetSuite Connector is (and what else gets called a connector)
Oracle's documentation defines it in one line: "NetSuite Connector (formerly known as FarApp) provides point integration solutions for leading ecommerce, logistics, and point-of-sale providers, enabling businesses to automate the data transfer between systems" (NetSuite Connector). Oracle announced the FarApp acquisition on April 6, 2021, describing FarApp as "a leading provider of eCommerce, logistics, retail and hospitality connectors for Oracle NetSuite" (Oracle and FarApp). The management console still lives at app.farapp.com, which Oracle's prerequisites page asks you to sign up on.
Three other things carry the same name:
- NetSuite Connector Platform (NCP) is a newer Oracle SuiteApp whose connectors are "built on Oracle Integration Cloud"; the Salesforce Connector runs on it and requires a OneWorld account with at least one subsidiary (Managing NCP Connectors).
- NetSuite AI Connector Service is unrelated: it is Oracle's MCP server for connecting Claude, ChatGPT and other AI clients. Oracle's own connector overview adds a note pointing readers there. If that is what you were looking for, start with how to connect NetSuite to Claude.
- Third-party connectors from Celigo, Boomi, Workato and others are iPaaS templates or apps, not Oracle products. They appear in the comparison section below.
Supported platforms
Oracle's product page, checked October 2026, groups the connectors as follows:
| Category | Connectors |
|---|---|
| Ecommerce | Shopify B2C and B2B, BigCommerce B2C, Adobe Commerce B2C, WooCommerce B2C, Loop Returns |
| Marketplace | Amazon Seller Central, Amazon Vendor Central, eBay, Walmart |
| Customer relationship management | Salesforce, Outlook |
| Logistics | ShipStation, Amazon Multi-Channel Fulfillment (MCF) |
| Point of sale | Shopify POS, Oracle Simphony POS, Square |
| Payroll | ADP Workforce Now |
The help center's supported storefronts and 3PLs list is narrower (Amazon Seller Central, Amazon Vendor Central, BigCommerce, eBay, Magento 2, Shipstation, Shopify, Shopify POS, Walmart, WooCommerce), because the Salesforce, Outlook, Simphony, Square, Loop and ADP connectors are documented in their own sections. "Magento 2" in the docs and "Adobe Commerce" on the product page are the same platform. If a platform you run is not on either list, NetSuite Connector is not the answer; see the comparison below.
What syncs, in which direction, how often
Oracle's Sync Frequency and Directional Flows page is the clearest statement of what the product actually does:
| Sync | From | To | Default frequency |
|---|---|---|---|
| Order Sync | Storefront | NetSuite | 20 minutes |
| Fulfillment Sync | NetSuite | Storefront | 90 minutes |
| 3PL Sync, orders | NetSuite | 3PL | 20 minutes |
| 3PL Sync, fulfillments | 3PL | NetSuite | 90 minutes |
| Product Sync | NetSuite | Storefront | 60 minutes |
| Refund Sync | Varies by storefront | Varies by storefront | 90 minutes |
| Amazon Settlement Sync | Amazon | NetSuite | Once a day |
| Amazon Inventory Adjustment Sync | Amazon | NetSuite | Once a day |
| Amazon Inbound Shipping Sync | Amazon or NetSuite | NetSuite or Amazon | 20 minutes |
Behind those rows, per Oracle's business flow and product sync pages:
- Orders and customers come from the storefront into NetSuite. Customer matching is by email plus name or company; no match creates a new customer, and customers never sync without an order.
- Products, prices and quantities go one way, from NetSuite to the storefront, with NetSuite as the master. The product sync has three modes: Price and Quantity Sync, Full Product Sync and Real-Time Price/Quantity Sync, plus a buffered quantity setting and image handling.
- Fulfillments and shipping data go from NetSuite (or the 3PL) back to the storefront.
- Refunds, settlements and inventory adjustments come in from the storefront or marketplace. Oracle's product page says settlement reports, refunds, returns and cancellations are "processed automatically with certain" platforms, not all.
In 2026.1 Oracle added bidirectional order-edit sync for Shopify B2B, automated settlement sync for Amazon Seller Central (full, partial and split payments mapped to the order or invoice), a Loop Returns connector that creates return authorizations, item receipts and cash refunds, and a trigger-based sync engine for the Salesforce connector (2026.1 release article).
Pricing model
Oracle does not publish a price for NetSuite Connector. The product page says users "subscribe to NetSuite for an annual license fee" made up of the core platform, optional modules and user count, that "there is also a one-time implementation fee for initial setup", and that "NetSuite Connector is available as an add-on module." That is the whole public statement: an annual module fee written into your NetSuite contract, plus implementation. Each storefront gets its own connector account, and Oracle's FAQ says a sandbox needs a separate NetSuite Connector sandbox account, which you request from NetSuite Sales.
We do not resell NetSuite licenses and have no price list to share. If you want to know what connectors and modules tend to cost in practice, our NetSuite pricing guide gathers what clients have reported, with the caveat that Oracle sets each quote in the contract.
NetSuite Connector vs Celigo vs custom
Disclosure first: BrokenRubik is a Celigo Standard Partner, and we also build custom integrations in SuiteScript, REST and n8n. We do not sell Oracle licenses. The three options below each fit a different situation; none is the best in general.
| NetSuite Connector | Celigo | Custom build | |
|---|---|---|---|
| Who runs it | Oracle, through app.farapp.com | Celigo's integrator.io platform | You, or a developer you hire |
| Platform coverage | The list above, fixed | Prebuilt Shopify, Amazon, Salesforce, HubSpot and many more, plus universal connectors for other APIs | Anything with an API |
| Data model changes | Mappings and preferences inside Oracle's flows; custom record mapping not supported per Oracle's FAQ | Flows are editable; custom records and logic supported | Fully yours |
| Scheduling | Fixed intervals (20, 60, 90 minutes, daily); first run sets the clock | Configurable schedules and real-time triggers | Whatever you write |
| Fits best | Standard storefront-to-NetSuite flows on a supported platform, one vendor on the contract | Standard flows plus the automations around them, with monitoring, retries and a vendor support line finance can call | Logic close to your records, unusual platforms, or volume and rules a template cannot express |
How we read it:
- NetSuite Connector is the lowest-decision option when your platform is on Oracle's list and your order flow is standard. Oracle supports it, the integration record is created for you, and there is no second vendor. The trade-off is the fixed scope: no custom record mapping, no file transfer, no subscription-order splitting, one NetSuite account per connector, and the sync cadence above.
- Celigo earns its place when finance relies on the flow daily and wants exception handling, retries and a support contract, or when the Shopify or Amazon flow is the core of a larger set of automations across more systems. Celigo's own Shopify to NetSuite template covers orders, customers, fulfillments, refunds, cancellations and products. We compare it with the other iPaaS options in NetSuite integration platforms compared.
- Custom is right when the business rule is the product: multi-entity routing, pricing logic, a 3PL with a bespoke API, or a storefront neither Oracle nor Celigo supports. It costs more to build and you own the maintenance. Our Shopify to NetSuite integration guide walks through what that involves.
Not sure which connector your stack needs?
Tell us your storefront, marketplaces, 3PL and order volume. We will say whether NetSuite Connector, Celigo or a custom build fits, and why.
Talk to a NetSuite integration developerSetup outline
Oracle's setup chapter and prerequisites describe the path:
- Prove the manual process first. Oracle's prerequisites ask that you can already enter, fulfill and bill an order in NetSuite with the right tax nexus, and that every storefront SKU exists in NetSuite with a one-to-one match.
- Enable features at Setup > Company > Enable Features: Customer Relationship Management, Inventory, Custom Records, Client SuiteScript, Server SuiteScript, SOAP Web Services, REST Web Services and Token-Based Authentication. Oracle says to do this before installing the SuiteApp, or you will have to add the REST Web Services (Full) permission to the NetSuite Connector Web Services role by hand.
- Install the NetSuite Connector SuiteApp and create your NetSuite Connector account on app.farapp.com.
- Authenticate. Per Setting Up Token-Based Authentication from NetSuite Connector to NetSuite: enable the NetSuite Connector integration record at Setup > Integration > Manage Integrations, give a user the NetSuite Connector Web Services role with cross-subsidiary record viewing, create an access token at Setup > Users/Roles > Access Tokens, and enter the account ID, token ID and secret under NetSuite > Settings > Credentials in the connector.
- Allowlist Oracle's IP addresses if your storefront or 3PL restricts inbound connections.
- Authorize the storefront or 3PL (Shopify, Amazon, eBay, Magento 2, Loop, Simphony, Square each have their own page).
- Configure order sync and product sync, run the sync tests Oracle documents with test orders, fulfilled orders, products and refunds, then deploy to production. Keep any existing integration running until the new one is verified; Oracle's FAQ says switching early risks losing data.
One thing to raise with Oracle before you start: the connector's documented authentication is token-based (TBA). From NetSuite 2027.1 no new TBA integrations can be created, and Oracle's tentative end of support for existing TBA integrations is 2028.2 (see our NetSuite REST API guide). Oracle's connector pages do not yet describe an OAuth 2.0 alternative, so ask your account team how the product's authentication will be handled on that timeline.
Limits to know before you buy
All from Oracle's General NetSuite Connector FAQ and Shopify Connector FAQ:
- One connector, one NetSuite account, one store. You cannot point a connector at a second NetSuite account or switch after go-live; each Shopify store, including each Shopify Plus store, needs its own connector.
- No custom record mapping, no file or document transfer, no CSV upload (only error export).
- No subscription orders. The storefront must create a separate order per billing interval.
- No payment gateway integration. The connector imports the gateway transaction ID; you capture through NetSuite's own gateway setup.
- No low-inventory alerts; the connector does not track inventory levels, it pushes them.
- Changing items on an order in NetSuite disables partial fulfillment for that order.
- Shopify specifics: wholesale prices arrive as discounts, variant titles cannot be changed, transfer orders and incoming quantities cannot be pushed to Shopify, canceling in NetSuite can refund the Shopify order unless configured otherwise, and metafields are added or updated but never cleared.
- Cadence drifts. You can time the first run, but Oracle notes small variations accumulate, so re-trigger periodically if timing matters.
- Not supported on Release Preview accounts, and sandbox requires its own connector account.
None of these are defects; they are the shape of a fixed-scope product. If your requirements sit inside that shape, it is the simplest option on the market. If two or more of the bullets above describe your business, that is the signal to look at Celigo or a custom flow.
FAQ
What clients ask before signing
Sources
- Oracle, NetSuite Connector, NetSuite Connector Overview, Supported Storefronts and 3PLs, Business Flow, Syncs, Product Sync, Sync Frequency and Directional Flows
- Oracle, NetSuite Connector Setup, Prerequisites, Token-Based Authentication from NetSuite Connector to NetSuite, General FAQ, Shopify Connector FAQ, Managing NCP Connectors
- Oracle NetSuite, NetSuite Connector product page and 2026.1 release article
- Oracle, Oracle and FarApp
- Celigo, Shopify to NetSuite integration template
Get your integration scoped
Tell us what systems you need to connect. We'll recommend the right approach and ballpark the cost.

Gustavo Cañete
Co-Founder & Development Director
Co-founder and Development Director at BrokenRubik overseeing technical excellence and development operations. 12+ years of experience leading NetSuite development teams and delivering complex enterprise solutions.
