Looking for a FarApp (NetSuite Connector) alternative?
FarApp, now sold by Oracle as NetSuite Connector, is a native SuiteApp built to sync a fixed list of ecommerce and marketplace channels into NetSuite, and only NetSuite. InfiPlex is an order management system: 130+ marketplaces, shopping carts, retail EDI partners, and 3PL/WMS systems land in one hub, and your back office, whether that is NetSuite, QuickBooks Online, Dynamics 365, or no ERP at all, is fed once from that hub. Every tier is published, from $49.99/month.
FarApp / NetSuite Connector
- Native NetSuite SuiteApp; pricing is quote-based, no published rate card
- Covers 18 of 46 tracked ecommerce-connector capabilities per independent audit
- Real-time / event-driven sync not evidenced; default cycle runs hourly
- Item / SKU mappings locked once created, per its only public review
- Bogs down at large order quantities, per the same review
What changes
- One hub across 130+ channels, retail EDI, and 3PLs, feeding NetSuite, Dynamics 365, QuickBooks Online, or no ERP
- Inventory pushed to channels automatically as sales are recorded
- Reversible, per-fulfillment SKU maps, re-pointed without a rebuild
- Published pricing from $49.99/mo
- 100,000 orders a month for a single client, about two a minute
Six concrete differences, not marketing language
Built as a hub, not a bolt-on
Before: one connector that bogs down at large order quantities, per its only public reviewFarApp / NetSuite Connector is a native SuiteApp: one connector, syncing a fixed list of channels into NetSuite, on a schedule. InfiPlex is built the opposite way, as a multichannel order management system first, with NetSuite as one of several ERPs it can feed. A single InfiPlex client runs 100,000 orders a month with zero issues; spread across the month that is about two orders a minute, which is not a strain on the hub.
SKU maps that flex without a rebuild
Before: item mappings locked after creation; syncs that can overwrite a whole recordInfiPlex's SKU-map system is reversible and per-fulfillment: point a channel's SKU to a different one, remap quantities, or add a new fulfillment pairing without recreating anything, with tracking and inventory reverse-mapped automatically. A change to one field stays a change to one field, it does not rewrite the rest of the item record.
Inventory accuracy built around NetSuite's own limits
Before: reports of inventory resetting unexpectedly and discounts miscalculating on synced sales ordersOnce NetSuite's Advanced Item Location Configuration is enabled, SOAP, the REST record API, and SuiteScript all stop returning location-level inventory. InfiPlex's connection reads through SuiteQL specifically because it is the one path that still returns it accurately, for exactly the class of data-accuracy issue that gap creates.
Built to solve what your business actually needs
Before: standard workflows only, with paid escalation for anything elseInfiPlex's rule engine, connector logic, and mapping tools are built to be adapted to how a specific business actually runs its orders and inventory, not limited to a fixed set of supported workflows. If there is a real operational need the platform does not already solve, that gets built, not routed to a paid support tier.
Real capability breadth, not 18 of 46
Before: 18 of 46 tracked ecommerce-connector capabilities per independent audit, about 39%InfiPlex covers multichannel order and inventory sync, retail EDI trading partners, 3PL/WMS routing, a full SKU-group, bundle, and SKU-map system, and a connector failure-recovery rule engine, all from one hub, not assembled from whichever of 46 tracked capabilities happen to be built.
Any custom field, mapped either direction
Before: custom field mapping and transformation not evidenced, per independent auditAny custom field a business adds in NetSuite, custbody at the header level or custcol on each line, can be set from order, item, or SKU-level data on push, or used as a filter and read back into an InfiPlex field on pull. It is configured directly, not limited to a fixed list of fields InfiPlex has to support first. The NetSuite custom field mapping and order rules guide covers every rule type.
The comparison, in one table
| Category | FarApp / NetSuite Connector | InfiPlex |
|---|---|---|
| What it is | Native NetSuite SuiteApp, one connector for a fixed channel list | Order management system feeding your ERP as one connection |
| ERP support | NetSuite only | NetSuite, Dynamics 365, QuickBooks Online, or none |
| Order volume | Bogs down at large order quantities, per its only public review | 100,000 orders a month for a single client, about two a minute |
| Capability coverage | 18 of 46 tracked capabilities per independent audit | Multichannel, EDI, 3PL, and inventory-tool coverage in one hub |
| Sync cadence | Hourly by default; real-time not evidenced | Automatic, as sales and changes are recorded |
| Item / SKU mapping | Locked once created, per its only public review | Reversible, per-fulfillment, re-pointed anytime |
| Data accuracy safeguards | Reports of inventory reset and discount miscalculation on sales orders | SuiteQL read path built around NetSuite's Advanced Item Location Configuration limit |
| Custom field mapping | Not evidenced, per independent audit | Open-ended; header and line-level fields, either direction |
| Support model | Paid Advanced Customer Support escalation reported for unresolved issues | Solved as part of the platform, not routed to a paid tier |
| Pricing | Quote-based, not published | Published, from $49.99/mo |
Questions people ask before switching
What is FarApp (NetSuite Connector), and how is it different from InfiPlex?
FarApp, now sold by Oracle as NetSuite Connector, is a native SuiteApp that syncs a fixed list of ecommerce and marketplace channels into NetSuite, and only works with NetSuite. InfiPlex is a multichannel order management system: 130+ marketplaces, shopping carts, retail EDI partners, and 3PL/WMS systems land in one hub, and your ERP, whether that is NetSuite, Dynamics 365, QuickBooks Online, or none, is fed from that hub.
How many integration capabilities does FarApp actually cover?
An independent ecommerce-connector audit credits it with 18 of the 46 capabilities it tracks in that category, about 39%. The gaps that recur across multiple head-to-head comparisons in that research include custom field mapping and transformation, flexible sync scheduling, logging and audit trail, and GL/financial document posting back to the ERP.
Does FarApp sync in real time?
Oracle's own documentation for NetSuite Connector states that syncing from NetSuite takes a few minutes even with real-time sync turned on, and defaults to an hourly cycle otherwise. The same independent audit marks real-time and event-driven sync as unevidenced for it against other connectors. InfiPlex pushes inventory to channels automatically as sales are recorded.
Can InfiPlex handle high order volume?
Yes. A single InfiPlex client runs 100,000 orders a month with zero issues. Spread across the month that is about two orders a minute, which is not a strain on the hub, since InfiPlex was built as a multichannel order management system that keeps every channel, warehouse, and order moving at once, not as a single-purpose connector layered onto one ERP.
Can FarApp's item and SKU mappings be changed after they're created?
Per its only public review on G2, no, mappings cannot be edited once set. A NetSuite user forum thread describes a marketplace feed-spec change forcing a complete mapping rebuild, which then produced new field-mapping errors. InfiPlex's SKU-map system is reversible and per-fulfillment, so a mapping can be re-pointed without recreating it.
Can InfiPlex map NetSuite custom fields, not just standard ones?
Yes. Header-level custom fields (custbody) and line-level custom fields (custcol) can both be set from order, item, or SKU-level data through push rules, or read as a filter condition and written into an InfiPlex field through pull rules. Mapping is configured directly rather than limited to a fixed list of fields InfiPlex has to support first, so a new custom field added in NetSuite can be wired in. The NetSuite custom field mapping and order rules guide walks through each rule type with examples.
What happens if FarApp doesn't support something my business needs?
Its capability set is fixed to what the SuiteApp ships with, and NetSuite user forums describe being directed to paid Advanced Customer Support for issues the standard product does not resolve. InfiPlex's rule engine and connector logic are built to adapt to how a specific business runs its orders and inventory, so a real operational need gets solved rather than escalated.
Does InfiPlex only work with NetSuite?
No. InfiPlex connects to NetSuite, Dynamics 365, QuickBooks Online, or runs with no ERP at all, from the same multichannel hub. FarApp, by contrast, is built specifically for NetSuite and does not apply if you run a different ERP.
I'm on NetSuite with Advanced Item Location Configuration enabled. Does InfiPlex still read location-level inventory?
Yes. Once that feature is on, SOAP, the REST record API, and SuiteScript all stop returning location-level inventory; SuiteQL still does, and InfiPlex's REST connection reads inventory through SuiteQL for exactly that reason.
Does InfiPlex handle kits and bundles?
Yes. Bundle SKUs push to your ERP as one line, and InfiPlex's bundle tool keeps component and bundle quantities accurate so a client can sell both without overselling. SKU maps associated to the ERP or 3PL connection handle the cases where a channel knows an item by a different SKU or quantity, with tracking and inventory reverse-mapped automatically.
What does switching from FarApp to InfiPlex look like?
InfiPlex runs in parallel with FarApp while channels move one at a time, with every order checked in NetSuite before it is pushed so an overlap window does not produce duplicates. The connector migration guide covers the full sequence, including historical order handling and inventory reconciliation.
Is FarApp still a reasonable starting point?
For a NetSuite account with a short, standard channel list and no plans to add retail EDI, 3PL routing, or a second ERP, it can be. The limits above tend to surface as order volume, channel count, or mapping complexity grows.
See the difference yourself
No email, no sales call to see pricing.
