FarApp Integration FAQs: NetSuite connectors, and where InfiPlex fits

FarApp is an integration platform known for connecting NetSuite to individual marketplaces and shopping carts, giving NetSuite users channel-specific connectors without needing custom development for each one.

Not typically — FarApp is generally positioned as a connector layer for bringing specific channels into NetSuite, rather than a standalone multichannel order and inventory management system with its own retail EDI, 3PL routing, and cross-ERP flexibility.

FarApp's positioning centers on NetSuite integration specifically; if you don't run NetSuite, its core value proposition doesn't apply the same way. InfiPlex, by contrast, works independently of which ERP (or no ERP) you run, then optionally connects to NetSuite, Dynamics 365, or QuickBooks Online.

Some sellers run FarApp connectors for specific channels while adopting InfiPlex for the broader multichannel operation — InfiPlex is built to coexist with existing NetSuite connectors during a transition rather than requiring you to rip everything out on day one.

In principle, yes, though running two systems that both write to NetSuite increases the risk of duplicate or conflicting records — most sellers evaluating this pairing choose to migrate specific channels fully onto InfiPlex over time rather than running both indefinitely on the same channels.

InfiPlex covers 130+ channels under one connection, retail EDI trading partners (Target, Costco, Home Depot, and more), 3PL/WMS routing, and real-time inventory sync across everything — all included at a flat plan plus per-order price, rather than per-channel connector licensing.

FarApp's specific NetSuite field-level mapping and long-standing individual connectors may have depth built up over years for particular channels; if you have a highly customized FarApp setup for a specific marketplace, that history is worth weighing before switching that specific connector.

InfiPlex has its own native NetSuite integration (included with Growth Pro) — it doesn't rely on or require FarApp. Orders push into NetSuite as sales orders, and inventory syncs back out, the same core relationship FarApp provides for individual channels, but consolidated across all of them.

Cost is often part of it — per-channel connector licensing can add up compared to one flat OMS connection — but the bigger driver for most sellers is wanting one system managing every channel, retail EDI partner, and 3PL relationship instead of stitching together several point connectors.

Your current FarApp connector costs and channel coverage, whether retail EDI or 3PL routing matter to your operation, and how quickly InfiPlex's team can get you live — typically 1–3 business days per channel with our USA-based team handling setup.

InfiPlex connects directly to each channel — Amazon, Walmart, eBay, Etsy, and 130+ more — pulling orders about every 15 minutes into one queue, then pushing them into NetSuite as sales orders.

InfiPlex maintains one master inventory pool; a sale on any connected channel updates availability everywhere else in real time, including what's reflected back to NetSuite.

Yes — the OMS routes orders to your own warehouse or a connected 3PL via the 3PL Connector, with tracking and inventory reconciled automatically on return.

Yes — InfiPlex handles retail EDI connections like Target, Costco, and Home Depot, pushing those orders into NetSuite the same way marketplace orders do.

Yes — many sellers move channels over individually, validating each one before decommissioning the corresponding FarApp connector, rather than switching everything simultaneously.

Connecting a channel to InfiPlex generally follows the standard 1–3 business day onboarding window; your NetSuite field mapping is scoped with you and your NetSuite administrator during setup.

Historical orders already recorded in NetSuite remain in NetSuite regardless of which connector brought them in; going-forward order flow simply switches to InfiPlex once a channel is migrated.

Yes — many sellers run a mixed setup during transition, migrating higher-priority or higher-volume channels to InfiPlex first.

NetSuite sellers who've added several FarApp connectors over time and want one system managing channels, retail EDI, and 3PL routing together — particularly once retail EDI or deeper inventory/warehouse features become a priority.

No separate migration fee is charged — setup and configuration are included as part of your InfiPlex plan, with our USA-based team handling the connection work directly.

NetSuite connectivity is included with Growth Pro at $999.99/month (100,000 SKUs, 10,000 orders included, $0.05/order after); Basic Starter ($49.99/month) and Growth Starter ($499.99/month) cover non-NetSuite channel needs. Full details are on the Pricing page.

No — InfiPlex's plan tiers include SKU and order allowances rather than per-channel licensing, so adding another marketplace doesn't mean buying another connector.

Growth packages carry a 3-month minimum commitment and Partner packages a 12-month term; Basic Starter is month-to-month.

Since NetSuite connectivity is a Growth Pro feature, most FarApp users evaluating InfiPlex will land on Growth Pro — schedule a demo and we'll scope it against your actual channel mix and volume.

The goal here is factual comparison, not disparagement — FarApp is an established NetSuite connector platform that serves its niche well. This hub explains where InfiPlex's broader scope differs so you can judge fit for your specific setup.

InfiPlex's NetSuite mapping is configured to your specific fields and workflow during onboarding; extremely bespoke customizations built up over years in a dedicated connector are worth discussing directly with our team to confirm feasibility before switching.