NetSuite Integration FAQs: every sales channel, on your own rules

The InfiPlex NetSuite integration connects your NetSuite ERP to the InfiPlex Inventory & Order Management System — and through it, to 130+ marketplaces, shopping carts, and retail EDI trading partners. Orders from every connected channel push into NetSuite as sales orders (or pull selectively, under custom filters), shipments you make in NetSuite flow back out as tracking, invoice numbers sync to marketplaces, and NetSuite inventory levels sync everywhere in real time. It's InfiPlex's most robust and configurable connection.

Our team configures the connection directly with you and your NetSuite administrator during onboarding — there's no connector to install on the marketplace side and no development work on yours. We handle the account link, then map your items, warehouses, custom rules, and order fields together so data lands in NetSuite the way your finance and operations teams expect.

Your InfiPlex OMS site is provisioned within 1–2 business days of sign-up, and the marketplace connections come up in the usual 1–3 day window. The NetSuite side is scoped with you during onboarding — ERP integrations take longer than a marketplace connection because item, warehouse, and custom rule mapping deserve care — and our team drives the configuration so your involvement is answering mapping questions, not building anything.

No — InfiPlex is a no-code integration, and our USA-based team performs the configuration with you. You don't purchase or maintain per-marketplace SuiteApps: one InfiPlex connection carries every channel, which is the point of the architecture.

All of them — any of the 130+ InfiPlex integrations can feed NetSuite, including Amazon (Seller Central, Vendor Central, FBA, MCF), Walmart, eBay, Etsy, TikTok Shop, Shopify, WooCommerce, and retail EDI partners like Target and Costco. Adding a new channel later doesn't require touching the NetSuite configuration; the new channel simply joins the existing rail.

Yes — that's the standard deployment. NetSuite keeps ownership of items, inventory truth, fulfillment, and financials; InfiPlex acts as the channel layer that moves orders in and inventory out, under rules you control. Your teams keep working in NetSuite exactly as they do today, with the marketplaces abstracted behind one integration.

InfiPlex pulls orders from your connected channels approximately every 15 minutes (faster if needed) and pushes them into NetSuite as sales orders with line items, customer details, and shipping selections mapped to your NetSuite fields, following whatever custom push rules your setup calls for. Your operations team sees marketplace demand inside NetSuite without logging into a single seller portal.

Yes — fulfill the sales order in NetSuite as you normally would, and InfiPlex pulls the shipping information from NetSuite and syncs the tracking number back to the originating marketplace automatically. Amazon, Walmart, eBay, and every other channel get their tracking without anyone re-keying it.

Automatically, regardless of where fulfillment happened. If you ship in NetSuite, InfiPlex pulls the shipment and posts tracking to the channel; if you ship in the InfiPlex OMS or through a connected 3PL, the same confirmation flows to both the marketplace and NetSuite so the ERP record stays complete.

Yes — InfiPlex handles retail EDI connections (Target DVS, Costco, Lowe's, Home Depot, and any EDI trading partner) and pushes those orders into NetSuite alongside your marketplace orders. In many cases InfiPlex significantly reduces or eliminates the EDI VAN costs you'd otherwise pay, savings that typically cover the InfiPlex package itself.

Order status updates flow through the OMS between the channel and NetSuite, and our team maps your specific cancellation and adjustment workflow during onboarding so the ERP reflects what actually happened on the marketplace. Every operation runs these flows a little differently, which is exactly why the mapping is configured with you rather than assumed.

Yes — routing rules decide per order whether fulfillment happens in NetSuite, in your own warehouse through the OMS, or at a connected 3PL/WMS via the 3PL Connector. Wherever the order ships from, tracking returns to the channel and the record lands in NetSuite.

Yes — push order rules are configurable rather than a one-size-fits-all default, so you control exactly which channel orders push into NetSuite and how they're mapped once there. Our team builds these rules with you during onboarding based on your actual order-handling workflow.

Yes — rather than syncing every NetSuite order, you can define custom pull filters so only specific orders (for example, ones meeting certain criteria) flow into InfiPlex to be managed there. This is useful when only a subset of your NetSuite order volume needs InfiPlex's multichannel handling.

Some operations enter orders directly into NetSuite through channels or processes InfiPlex doesn't need to touch — phone orders, certain wholesale accounts, or specific order types. Custom pull filters let InfiPlex focus on the orders that actually benefit from its multichannel routing, fulfillment, and tracking, rather than pulling in volume that doesn't need it.

Our team works with you and your NetSuite administrator during onboarding to define the specific criteria — order type, channel, customer group, or other fields your business uses — that determine what pushes, what pulls, and how. This is scoped to your operation rather than offered as a generic toggle.

Yes — as your operation evolves, our team can adjust the rules governing what pushes, pulls, or how orders are filtered, without requiring you to rebuild the underlying connection.

Custom rule configuration is part of the standard NetSuite onboarding process included with Growth Pro, not a separate paid add-on — the depth of configuration is part of why this connection is included at that tier.

Yes — rules can be scoped by order type, channel, or other criteria, so retail marketplace orders, EDI orders, and wholesale orders can each follow their own logic rather than being forced through one blanket rule.

InfiPlex pulls inventory levels from NetSuite and distributes them to every connected channel in real time, so Amazon, Walmart, Shopify, and the rest all reflect what NetSuite says is available. As channel orders arrive, quantities decrement everywhere at once — which is what actually prevents overselling.

Yes — you can map multiple NetSuite warehouse locations to the corresponding locations on your channels (1:1), or total inventory across NetSuite warehouses and send a single combined quantity per SKU. Both patterns are supported, and our team configures whichever matches your fulfillment reality.

Yes — buffers apply per channel in InfiPlex, so you can hold back safety stock on a fast-moving marketplace while exposing full NetSuite availability to your own webstore. NetSuite stays the source of truth; the buffers shape what each channel sees.

Continuously — InfiPlex pulls orders roughly every 15 minutes and pushes inventory adjustments back to every channel in real time as they occur. Cadence can be tightened where an operation needs it.

Item-level data mapping is part of the NetSuite configuration, and the optional Product Information Management (PIM) system on Growth Pro automates pushing SKU data out to marketplaces. Our team scopes your specific product-data flow — what originates in NetSuite versus your webstore — during onboarding.

Yes — custom product-saving rules control exactly how NetSuite product data gets created and matched to SKUs in InfiPlex, rather than relying on a generic default import. This matters most for catalogs with complex naming conventions, variants, or attribute structures.

If your NetSuite catalog uses specific naming conventions, custom fields, or a structure that doesn't map cleanly to a generic default, custom rules make sure products land in InfiPlex correctly the first time rather than needing manual cleanup after the fact.

Yes — beyond choosing 1:1 warehouse mapping or totaled quantities, custom filters can determine which NetSuite inventory records get pulled into InfiPlex at all, useful for operations with SKUs or locations in NetSuite that shouldn't sync to external channels.

Yes — inventory pull filters can be scoped to specific NetSuite locations, so internal, damaged, or non-sellable stock locations don't factor into what channels see as available.

Generally no — rules are configured once during onboarding based on your catalog structure, and our team adjusts them if your structure changes significantly, rather than requiring day-to-day upkeep on your end.

Order push/pull rules govern which orders move and in which direction; product-saving and inventory-filter rules govern how catalog and stock data specifically gets created and scoped once it arrives in InfiPlex. Both are configured together during onboarding since they interact with the same underlying sync.

Yes — custom tracking rules let you consolidate multiple packages in a single shipment into one tracking entry pushed to NetSuite, rather than a separate record per package.

Yes — the opposite configuration is equally supported: each package gets its own individual tracking record synced to NetSuite and the originating marketplace, rather than being consolidated.

It depends on how your fulfillment team already thinks about multi-package orders and what your marketplaces expect for tracking granularity. Our team walks through your specific shipment patterns during onboarding to recommend the right fit.

Tracking consolidation rules are generally set at the account level, though our team can scope exceptions for specific channels with unique tracking requirements during onboarding.

Each shipment leg generates its own tracking data, which then follows your configured consolidation rule — combined per shipment or kept separate — before syncing back to NetSuite and the channel.

Yes — InfiPlex OMS syncs your NetSuite invoice numbers directly with marketplaces, eliminating the manual payment reconciliation work that otherwise falls on your accounting team.

Without it, matching marketplace payments to the correct NetSuite invoice is a manual, error-prone process. Syncing invoice numbers directly closes that gap, turning what used to cost hours of reconciliation work into an automated background process.

Invoicing sync is part of the standard NetSuite integration included with Growth Pro, not a separate line item.

Yes — invoice numbers sync for orders flowing through retail EDI trading partners the same way they do for marketplace orders, keeping reconciliation consistent across your whole channel mix.

Our team maps invoice fields to your specific NetSuite configuration during onboarding, working with your finance team to make sure the numbers that sync are the ones your reconciliation process actually needs.

Per-channel SuiteApps multiply cost and fragility: each has its own license, its own mapping, and its own support queue, and adding a channel means another procurement cycle. InfiPlex is one connection that carries every channel — adding Walmart or TikTok Shop later is a configuration step, not a new integration project — and Growth packages even include InfiPlex building new marketplace APIs at no additional cost.

InfiPlex integrates with FarApp and can coexist with connectors you already run, which matters during a migration — you can move channels onto the InfiPlex rail in phases rather than a big-bang cutover. Most operations consolidate onto InfiPlex over time to retire the per-channel licenses.

Yes — Growth Pro includes Amazon Multi-Channel Fulfillment, FBA Inbound, Vendor Central Direct Fulfillment, and Vendor Central Retail, all flowing through the same NetSuite rail. Vendor purchase orders and marketplace orders land in the ERP through one integration.

InfiPlex supports QuickBooks Online today and NetSuite on Growth Pro, so you can run the OMS through the migration: channels stay connected to InfiPlex while the ERP behind it changes. That decouples your marketplace operations from the ERP cutover, which is usually the riskiest part of the move.

Yes — the 3PL Connector program lets a 3PL connect each client's channels and systems, including NetSuite where a client runs it, with each client in its own Site Area. It's the most cost-effective way for a 3PL to offer ERP-connected fulfillment.

Yes — wholesale orders from the InfiPlex B2B eCommerce Portal or the Faire marketplace push into NetSuite as sales orders just like retail channels, drawing on the same inventory. Retail and wholesale finally reconcile in one ERP without side spreadsheets.

NetSuite and other ERP connections are included with Growth Pro at $999.99/month — which also carries up to 100,000 SKUs, 10,000 included monthly orders ($0.05 per additional order), 4 new marketplace API integrations per year, the Marketplace Repricer, PIM, and the full Amazon channel set. Basic Starter and Growth Starter can upgrade to Growth Pro when they're ready for ERP connectivity; details are on the Pricing page.

The NetSuite integration, including custom push/pull rules, product-saving rules, tracking configuration, and invoicing sync, is part of Growth Pro rather than a per-feature license, and ERP configuration is scoped with you during onboarding so there are no surprises. Where a setup needs a fully separated marketplace configuration, additional Site Areas are $25/month each — but a standard NetSuite deployment doesn't require that.

Operations running NetSuite typically clear Growth Pro's threshold on volume alone — 10,000 included orders at $0.05 overage is priced for that scale — and consolidating several per-channel connector licenses into one integration usually covers a meaningful share of the cost. Add the EDI savings InfiPlex delivers on retail connections and the package tends to pay for itself; schedule a demo and we'll run your numbers.

Growth packages carry a 3-month minimum commitment and Partner packages a 12-month term. Given that ERP integrations are meant to run for years, most NetSuite customers care less about the commitment than about the mapping being right — which is why our team configures it with you rather than handing over a toolkit.

Usually somewhat, since defining push/pull filters, product-saving logic, and tracking consolidation rules takes more onboarding conversation than a simple marketplace connection — but it's time spent once, up front, rather than cleanup work later. Our team scopes the specific timeline once we understand your NetSuite setup.