NetSuite guidesNetSuite integration guide

NetSuite + BigCommerce integration: catalog, prices and orders

BigCommerce stores often connect to NetSuite through Oracle’s NetSuite Connector or an integration app, and that works for standard catalogs. The cost and risk rise with B2B pricing, customer-specific catalogs and products that NetSuite stores as kits or matrix items.

Updated
October 5, 2026
Written by
Nitya Hoyos
Covers
Approach, cost, mapping
Questions
3 answered below

(01)The situation

As with any storefront, the core flows are items and inventory from NetSuite to BigCommerce, orders from BigCommerce to NetSuite, and fulfillments with tracking back. The order flow is rarely the problem. The catalog is: BigCommerce products have variants built from option values, NetSuite has matrix items with parent and child records, and the two have to agree on which record is the sellable SKU and which system owns names, descriptions and images.

B2B stores add pricing. BigCommerce uses price lists and customer groups; NetSuite uses price levels, customer-specific item pricing and quantity pricing. If wholesale customers get prices from NetSuite in one place and BigCommerce in another, they will see one price online and another on the invoice. The fix is to choose NetSuite as the source and generate BigCommerce price lists from it, or to read prices from NetSuite at checkout. The second is more accurate and harder to make fast.

Customers are the third decision. A retail store can create a NetSuite customer per order or post every order to a single cash-sale customer; a B2B store needs every company to be a real NetSuite customer with terms, linked to the BigCommerce customer or company account so orders land on the right record.

(02)What it costs

Cost and timeline by approach

Connector

$7,000–$19,000

48–96 hours · 2–4 weeks

Middleware

$14,000–$37,500

93–188 hours · 4–7 weeks

Custom code

$28,500–$79,000

191–395 hours · 7–14 weeks

For a two-way NetSuite–BigCommerce / other storefront integration moving items & catalog, inventory levels, pricing & price levels, sales orders, fulfillments & tracking, at medium volume with hourly sync and some existing NetSuite customization. Hours are priced at $150–$200 an hour and include discovery and 20% for testing and cutover. Connector and middleware figures leave out license fees, which are paid to the vendor. These are estimates from the published method, not a quote.

(03)The options

Which approach fits

ApproachBest forTrade-off
NetSuite Connector or integration appRetail catalogs, one store, standard order and fulfillment flows.Price lists, kits and customer-specific catalogs strain its mappings.
MiddlewareSeveral stores or channels with mostly standard data.License cost, and logic split across mapping screens.
Custom (BigCommerce APIs + NetSuite RESTlets/REST)B2B price lists from NetSuite, kits and assemblies, headless storefronts.You own the code and its monitoring.

(04)Field mapping

Mapping decisions that matter

SourceNetSuiteNote
Variant SKUMatrix child item: itemidMatch on SKU or external ID, never on the option labels.
Price list recordPrice level / customer item pricingGenerated from NetSuite; never edited in BigCommerce.
Order IDSales order: external IDRetries become updates instead of duplicates.
Customer groupCustomer: price level or categoryDecide which system assigns a customer to a group.
ShipmentItem fulfillment: tracking numbersOne shipment per fulfillment; partial shipments included.

(05)Where it goes wrong

The mistakes that cost the most

  1. 01
    Kits sold as one BigCommerce product but stocked as several NetSuite items need the available quantity computed from the components, or the store sells kits it can’t build.
  2. 02
    Price lists built by hand in BigCommerce drift from NetSuite price levels; customers then dispute invoices.
  3. 03
    Tax calculated by BigCommerce and tax calculated by NetSuite can differ by cents; decide which one the sales order keeps.
  4. 04
    Renaming a product in NetSuite can overwrite merchandising copy written in BigCommerce unless descriptions are excluded from the item sync.

(06)Before you build

When not to do this

For a retail store with a simple catalog and one warehouse, do not build custom. Use the NetSuite Connector or an integration app, and spend the money on the storefront instead.

(07)Questions

Does NetSuite integrate with BigCommerce?

Yes. Oracle’s NetSuite Connector supports BigCommerce, integration apps and middleware offer prebuilt flows, and both platforms have APIs for a custom integration.

Can BigCommerce show NetSuite customer-specific prices?

Yes, either by generating BigCommerce price lists from NetSuite pricing on a schedule, or by looking up NetSuite prices at runtime. The first is simpler; the second is always current but must be cached carefully to stay fast.

How are BigCommerce variants mapped to NetSuite?

Usually each BigCommerce variant maps to a NetSuite matrix child item by SKU, and the BigCommerce product maps to the matrix parent. Items that are not matrix items in NetSuite need a mapping table.

Free checklist

(Next step)

Is NetSuite holding you back? Let’s fix it.

Start with a fixed-price integration audit: a written plan showing what’s broken, what will break next, and what to fix first.