Comparisons
NetSuite Connector alternative: an integration built around your rules
Oracle's NetSuite Connector, formerly FarApp, links NetSuite to storefronts, marketplaces and 3PLs with prebuilt syncs on a fixed schedule. Oracle documents those schedules, the connector's mapping limits and what it leaves to scripts in NetSuite. A custom integration starts from your rules instead: events instead of 20 and 90-minute runs, logic in the integration instead of in workflows, and an exportable record of every mapping.
What NetSuite Connector does well
NetSuite Connector is Oracle's own integration product for NetSuite, formerly known as FarApp. It provides prebuilt syncs between NetSuite and storefronts, marketplaces, 3PLs and point-of-sale systems, configured in the connector's own interface. For a Shopify store the documentation covers products, inventory, multi-location inventory, orders, fulfillments, refunds, cancellations, gift cards, POS orders and a payout report sync that creates deposit records with Shopify's fees as lines.
Three things stand out in Oracle's documentation:
- It sits inside the NetSuite account's governance. Oracle states that NetSuite Connector is excluded from the scope of concurrency governance, and that it keeps retrying a request that fails on a concurrency limit until it finishes. By default it uses five concurrent sessions.
- A B2B connector for Shopify. It syncs Shopify B2B companies as customers with their buyers as sub-customers, posts invoices or customer deposits with terms such as Net 30, pushes NetSuite payments back to mark Shopify invoices paid, and syncs catalogs built from a NetSuite price level with fixed price overrides per item.
- Marketplace coverage. Amazon settlement, inventory adjustment and inbound shipping syncs run next to the storefront syncs.
Statements about NetSuite Connector on this page come from Oracle's NetSuite help center, read on October 3, 2026.
How it moves data: a schedule per sync
NetSuite Connector runs each sync on a schedule. Oracle publishes the default frequencies:
| Sync | Direction | Default frequency |
|---|---|---|
| Order sync | storefront to NetSuite | 20 minutes |
| Fulfillment sync | NetSuite to storefront | 90 minutes |
| Product sync | NetSuite to storefront | 60 minutes |
| Refund sync | varies by storefront | 90 minutes |
| 3PL orders and fulfillments | NetSuite to 3PL, 3PL to NetSuite | 20 and 90 minutes |
| Amazon settlement | Amazon to NetSuite | once a day |
The schedule can be triggered by hand, and Shopify orders can come in real time through a webhook; Oracle's setup page warns that real-time order sync may result in a subscription increase. The real-time option Oracle documents is for orders; the other syncs keep their schedule.
The arithmetic for one order: placed at 09:01, just after a run, it waits 19 minutes for the 09:20 order sync. Shipped at 11:05, just after a fulfillment run at 11:00, the tracking waits for the run of 12:30: 85 minutes, in which the customer has a shipped parcel and no tracking email. On average an event waits half the interval, 10 minutes for orders and 45 for fulfillments; the worst case is the full 20 and 90.
Where the documented limits are
Oracle's help center is specific about what the connector does not do, and about where it expects logic to live:
| Area | What Oracle documents |
|---|---|
| Mapping logic | The connector "works best with simple mappings". Complex logic belongs in NetSuite, as a formula field, script or workflow |
| Order changes | It does not support adding items to orders, such as a default line on every order; that needs a workflow or script in NetSuite |
| SKU matching | SKUs must match exactly between storefront and NetSuite, are case-sensitive, and must be unique across all item types, including inactive items |
| Customers | Matched by name, company name or email; a mistyped email can create a duplicate customer, to be merged by hand |
| B2B catalogs | Assigned at company level and applied to all company locations; per-location catalog assignment is not supported. A catalog without a mapping is skipped |
| Stores | One Shopify store per connector; several Plus stores need several connectors |
| Locations on orders | The Shopify location ID on orders is populated only for POS orders, so the location mapping on orders applies to POS |
| Inventory | No transfer orders or incoming quantities in Shopify |
| Export | Mappings, orders, refunds and products cannot be exported to a file; only sync errors can |
The first two rows add up. Logic that the connector does not hold goes into NetSuite workflows and scripts, which then run on every record the connector creates and need their own maintenance after NetSuite releases. The integration's behavior is spread over the connector's screens and the account's customizations, and the export row means the connector's half is not available as a file.
What a custom integration does differently
We build the integration to your systems and your rules, then host and run it. Against the table above:
| Area | Custom integration, hosted and run |
|---|---|
| Timing | Orders by webhook into a queue, fulfillments written to the store when NetSuite records them; scheduled runs only for bulk data and a nightly comparison |
| Mapping logic | Rules written in the integration, per field, including default lines, translations and conditions; no extra scripts needed in NetSuite |
| SKU matching | A maintained mapping table between store variants and NetSuite items, with normalization for case and spaces; an unmatched SKU goes to a review list |
| Customers | A matching chain on company, email and external ID, and a review list for near matches instead of a new record |
| B2B catalogs | Price levels, quantity breaks and customer prices mapped to Shopify catalogs, per company location where Shopify allows it |
| Visibility | A dashboard with logs per run, a diff of what changed, and the mapping written down as documentation you keep |
| Concurrency | Counts against the account limit, and is built to stay within its share with a queue that waits instead of failing |
The last row is the trade-off to plan for. NetSuite Connector's exemption from concurrency governance is a real advantage for an account that runs several integrations. A custom integration shares the account limit, 5 on Standard, 15 on Premium, 20 on Enterprise and Ultimate, plus 10 per SuiteCloud Plus license, and is designed to it. The sums for an order sync are in NetSuite concurrency limits. More on the NetSuite side is on the NetSuite integration page, and the comparison with an iPaaS is on Celigo alternative.
Switching without losing orders
The new integration first runs next to the connector with writes disabled. It reads the same orders and items, computes what it would write, and its output is compared with what the connector posted. Because the connector's mappings cannot be exported, this is also where they are read from its screens and written down as rules.
Then one record type moves at a time, and the matching connector sync is switched off in the same step: orders together with their fulfillments and refunds, products and inventory separately. Marketplaces and other stores can stay on the connector, since each Shopify store has its own connector account. Status handling during the switch is covered in order status mapping.
Tell us which NetSuite Connector syncs you run and what you have added in NetSuite around them, and you get a fixed price for the integration that replaces them.
Frequently asked questions
Is NetSuite Connector the same as FarApp?
Yes. Oracle's documentation calls it NetSuite Connector, formerly known as FarApp, and its settings are still reached at app.farapp.com. It provides prebuilt syncs between NetSuite and ecommerce, marketplace, logistics and point-of-sale systems.
How often does NetSuite Connector sync orders?
Oracle's table of default frequencies gives 20 minutes for the order sync, 90 minutes for fulfillments and refunds and 60 minutes for products. The actual frequency per account is shown in the connector. Real-time order sync for Shopify is available through a webhook, and Oracle notes that enabling it may increase the subscription.
Does a custom integration count against our NetSuite concurrency limit?
Yes. Oracle excludes NetSuite Connector from concurrency governance, and every other integration shares the account limit: 5 on Standard, 15 on Premium, 20 on Enterprise and Ultimate, plus 10 per SuiteCloud Plus license. A custom integration is built to stay within its share, with a queue that waits instead of failing. The sums are in NetSuite concurrency limits.
Can we keep NetSuite Connector for marketplaces and move Shopify?
Yes, as long as each record type has one owner. NetSuite Connector needs a separate Shopify connector per store, so moving one store leaves the others untouched. The integration that takes over orders for that store also takes over its fulfillments and refunds, so two systems never write the same order.
Can we export our NetSuite Connector mappings before switching?
Not to a file. Oracle states that the connector cannot export mappings, orders, refunds or products, only sync errors. The mappings are read from its screens during the parallel run and written down as rules in the new integration, where every rule is visible in the documentation and the log.
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