Key takeaways
- Orders flow into NetSuite; items, inventory, prices and tracking flow out. Decide which system owns each record before choosing a tool.
- Oracle's NetSuite Connector supports Amazon Seller Central and Vendor Central, BigCommerce, eBay, Magento 2, Walmart and WooCommerce; on BigCommerce it lists $2,000 upfront plus $83.23 per month.
- Matrix items versus storefront variants, marketplace fees and order edits after export cause most sync failures, not the order import itself.
- Marketplaces need their own finance flow: Amazon and eBay settle net of fees, so payouts must be broken into sales, fees and refunds in NetSuite.
- A custom multi-channel integration is roughly 430 to 960 hours for a typical scope.
A NetSuite ecommerce integration sends orders and customers from your storefronts and marketplaces into NetSuite, and sends items, inventory, prices and fulfillment tracking back out to each channel. You can buy it from Oracle as NetSuite Connector, use a platform plugin or an iPaaS, move the store onto SuiteCommerce, or build a custom sync for the channels you have.
We are integration engineers, so this guide is about record ownership, data flow and failure points. Prices are list prices as published by each vendor in November 2026; where a vendor only quotes, we say “quote-based”. This post covers Magento (Adobe Commerce), WooCommerce, BigCommerce, Amazon and eBay. For Shopify, see our separate Shopify NetSuite integration guide. We have not published a NetSuite case; the patterns below come from order, inventory and accounting syncs we built on other systems.
What syncs, and in which direction
Every ecommerce integration with NetSuite comes down to six flows.
Orders and customers, into NetSuite. Each web or marketplace order becomes a sales order (or a cash sale for prepaid orders), with tax, shipping, discounts and the payment reference. Customers are matched or created; marketplace buyers are often posted to one customer per channel because the marketplace owns the buyer.
Items, out to channels. NetSuite usually owns the item master: SKU, name, weight, cost. Storefronts often own the marketing content: descriptions, images, SEO fields. NetSuite matrix items (a parent with one child per size and color) must become configurable products in Magento, variable products in WooCommerce or variants in BigCommerce.
Inventory, out to channels. Available quantity by location, minus a safety buffer, pushed often enough that two channels cannot sell the last unit.
Prices, out to channels. Base prices, sale prices and, for B2B, price levels per customer group.
Fulfillments, back to channels. When NetSuite or a 3PL ships, tracking numbers go back so the store emails the buyer and the marketplace sees on-time shipment. Our NetSuite 3PL integration guide covers the warehouse side.
Returns and money. Returns become return authorizations and credit memos; refunds have to match what the channel actually refunded. Marketplaces add one more flow: settlements that pay you net of fees.
Your options
| Option | Best for | What it covers | Pricing as published | Limits |
|---|---|---|---|---|
| NetSuite Connector (Oracle, formerly FarApp) | Standard flows on supported channels | Oracle lists Amazon Seller Central and Vendor Central, BigCommerce, eBay, Magento 2, Walmart, WooCommerce, Shopify and ShipStation; on BigCommerce it syncs products, customers, stock, orders and fulfillments | BigCommerce listing: $2,000 upfront plus $83.23/month; other channels quote-based through Oracle | Configured mappings, not code; unusual flows need workarounds |
| SuiteCommerce | B2B and B2C stores run on NetSuite itself | Storefront on NetSuite data, no product or order sync | Quote-based | Replatforming an existing store; marketplaces still need a connector |
| Platform plugins | One storefront, simple catalog | Example: a NetSuite extension on the WooCommerce Marketplace maps orders to sales orders or cash sales, imports matrix items, syncs fulfillments and refunds | WooCommerce example: $399 for one year | One channel per plugin; support depends on the plugin vendor |
| iPaaS (for example Celigo) | Several channels plus other systems (CRM, 3PL, EDI) | Prebuilt integration apps and templates, custom flows | Quote-based; Standard, Professional and Enterprise editions, 30-day trial | Subscription grows with flows and endpoints; edge cases still need scripting |
| Custom integration | Multi-channel sellers with unusual catalogs, pricing or marketplace finance | What you specify, including fee and settlement posting | Hours times rate (see below) | You own maintenance when channel APIs change |
NetSuite Connector is Oracle’s own answer and the natural first look. It is licensed per channel, and its strength is the standard flows. Check how it handles your matrix items, your tax setup and marketplace settlements before you sign.
SuiteCommerce removes the storefront sync entirely, because the store reads NetSuite records directly. That is attractive for B2B sellers with price levels and account terms. For a working Magento or WooCommerce store, though, replatforming usually costs more than a sync.
Marketplaces are a separate project even when the storefront is solved. Amazon orders, listings and stock run through the Selling Partner API (SP-API), with per-operation rate limits and a separate Finances API for money. eBay splits orders, inventory and finances across several Sell APIs. Our NetSuite EDI integration guide covers retail partners that order by EDI instead.
Platform differences matter more than logos. Magento (Adobe Commerce) brings multiple websites and store views, so one NetSuite item can need different prices, names and stock sources per store. WooCommerce stores run on WordPress plugins that also touch orders and products, such as subscriptions, bundles and custom checkout fields, and each one adds fields the sync has to understand. BigCommerce has a cleaner API with built-in variants and price lists, but multi-storefront setups raise the same per-store questions as Magento. On the marketplace side, Amazon sellers often split between merchant-fulfilled and FBA orders, and FBA stock lives in Amazon’s warehouses, so NetSuite needs a location for it and a way to record what Amazon shipped.
Where these integrations break
1. Matrix items versus variants. NetSuite matrix options and storefront attributes drift: “Navy” in one system, “Dark Blue” in the other; a child item that exists in NetSuite but was never published. Fix: one option dictionary, SKU as the only join key, and a report of children that exist on one side only.
2. Order edits after export. A customer service agent changes the shipping address or swaps a size in Magento after the order already reached NetSuite. Most connectors import once and ignore later edits. Fix: define a cutoff (for example, the order is locked once a fulfillment exists), sync allowed edits as updates, and alert on the rest.
3. Overselling across channels. Stock pushed every hour to five channels means the last units sell twice. Fix: push available quantity, not on-hand, keep a per-channel buffer for slow-syncing marketplaces, and push immediately on large changes.
4. Marketplace fees and net payouts. Amazon and eBay pay you net. Amazon’s Finances API returns financial events per order or date range before a statement period closes; eBay’s Finances API returns payouts and transactions such as buyer refunds, shipping labels and listing fees, and a transaction appears only after the payment executes. Posting the net payout as revenue hides fees and breaks margin reporting. Fix: post the gross sale on the order, fees and refunds as their own records, and the settlement as a deposit that nets them. Our Stripe NetSuite integration guide covers the same deposit logic for card processors.
5. Partial shipments and split orders. One order ships from two locations, or one line is backordered. Fix: send tracking per fulfillment, not per order, and let the channel close the order only when every line has shipped or been canceled.
6. Returns that do not match refunds. A store refunds shipping, or refunds before the item comes back; NetSuite expects a return authorization first. Fix: decide whether the channel or NetSuite triggers the refund, and post the credit memo for exactly what was refunded.
7. Tax and rounding. The store calculates tax per line, NetSuite per order, and they differ by a cent. Fix: import the channel’s tax as calculated and post differences to a rounding account rather than letting NetSuite recalculate.
What a custom integration costs
Start with NetSuite Connector or a plugin if your channels are supported and your flows are standard. Custom work makes sense with several channels, a marketplace finance flow, a catalog the connector cannot express, or logic that has to run between the store and the ERP. Hours are our planning ranges; rates are market bands, since 2026 outsourcing rate surveys put Eastern Europe at about $35 to $80 per hour and North America at $80 to $180 or more. We use $80 to $160 for US onshore.
The preselected scope in the estimator (one storefront with orders, matrix items, inventory, fulfillments, returns, a queue with retries, monitoring, catalog cleanup and a parallel run) comes to about 430 to 960 hours. That is about $15,000 to $77,000 at Eastern European rates and $34,000 to $154,000 at US onshore rates, or roughly 5 to 11 weeks with three engineers. A marketplace channel and its fee and settlement posting add 140 to 300 hours together.
How to run the project
1. Name an owner for every record. Items, descriptions, images, stock, prices, customers, order status. Two owners for one field is the most common root cause of sync bugs.
2. Clean the catalog first. One SKU per sellable unit, options aligned between NetSuite and every store, no duplicates. Fixing this during the build costs more than before it.
3. Start with one channel. Pick the channel with the most orders, prove the order, stock and fulfillment loop, then add the rest.
4. Test the edge cases on purpose. Order edits, partial shipments, returns before and after shipping, discounts, gift cards, a marketplace refund.
5. Run in parallel. Let the new sync create orders in a sandbox or alongside the old process for a week and compare.
6. Add marketplaces last. Amazon and eBay bring rate limits and finance flows that are easier to add on top of a stable core.
From related work
We haven’t published a NetSuite case; these patterns come from order, payment and accounting syncs we built on other systems.
For Aspect, a print workshop selling on Amazon in the US, UK and EU, we connected 7 Amazon marketplaces through SP-API and the Amazon Advertising API. Orders and stock sync every 15 minutes, and a profit view deducts marketplace fees, delivery, advertising, reprints and materials to show real margin per product. That fee breakdown is exactly what a marketplace-to-NetSuite flow has to reproduce.
For ProdUp, a product hub for WooCommerce stores, we refactored bulk imports through the WooCommerce API into parallel tasks with retries, stored the result of every import, and added a dashboard that flags duplicate SKUs and products missing descriptions or attributes. For Peregrine Ship, a dropshipping platform, we built per-order sourcing from 1688 suppliers with tracking import and billing that charges clients only when each stage completes.
On the accounting side, our custom ERP system and One Motion ERP both sync with QuickBooks, including invoices, tax and tariff rules, duplicates and reconciliation. For the bigger picture, see our NetSuite integration guide, HubSpot NetSuite integration and, if you are still choosing the ERP, best ERP for ecommerce.
Where OSKI fits
OSKI is a .NET and React engineering company with a team mostly in Ukraine. We build integrations, ecommerce systems, Amazon SP-API integrations and custom ERP modules. If NetSuite Connector covers your channels, use it. If it does not, send us your channel list and a sample of your catalog, and an engineer will reply with a written estimate and the assumptions behind it.
- Storefronts and marketplaces → Orders, customers, tax and shipping NetSuite
- NetSuite → Items and matrix items as variants Storefronts
- NetSuite → Available stock by location All channels
- NetSuite → Price levels and customer pricing Storefronts
- NetSuite or 3PL → Fulfillments and tracking All channels
- Channels ⇄ Returns, refunds and cancellations NetSuite
- Amazon and eBay → Settlements, fees and payouts NetSuite
● Works natively● Partial or one-way● Needs custom work
Typical directions for a mid-size multi-channel seller. Green is covered by most connectors, amber needs careful mapping, red usually needs custom work or an iPaaS add-on.
- Items, prices and customers live in NetSuite, no product sync
- Fits B2B with price levels and account terms
- Means replatforming an existing store
- Marketplaces still need a connector
- Keeps the storefront, themes and extensions you have
- Needs item, stock, order and fulfillment sync
- Connector, plugin, iPaaS or custom
- Two systems to keep in step
Neither is cheaper in every case; replatforming cost and how much logic lives in the store usually decide it.
- 01 Owner per record
Items, stock, price, customer, order status.
- 02 Clean the catalog
One SKU per sellable unit, options aligned.
- 03 Map one channel
Start with the channel that has the most orders.
- 04 Test edge cases
Edits, partial shipments, returns, fees.
- 05 Parallel run
Old and new order flow side by side for a week.
- 06 Add channels
Marketplaces after the core flow is stable.
Estimate a custom NetSuite ecommerce integration
Pick the flows and channels you need. Hours include design, QA and project management. Change the rate band and team size to see cost and calendar time.
Sources
Based on the following official vendor and regulator materials:
- Oracle NetSuite Help: NetSuite Connector Supported Storefronts and 3PLs
- BigCommerce: NetSuite Connector by Oracle NetSuite
- WooCommerce Marketplace: NetSuite Integration for WooCommerce
- Amazon Selling Partner API: Finances API
- eBay Developers Program: Finances API overview
- Celigo: Pricing



