BigCommerce Store Connector

The problem

A BigCommerce storefront and a NetSuite account usually end up describing the same business in two incompatible ways. NetSuite holds the item master, the customer record, the pricing structure and the general ledger. BigCommerce holds the product listing, the shopper account and the order. Between them sits a person with a CSV export.

The cost shows up in specific places. Web orders are keyed into NetSuite hours after they were placed, so fulfillment starts late and the finance team cannot see today's revenue. Inventory on the storefront is a snapshot from the last upload, so items sell after they are gone. Worst of all for wholesalers, B2B pricing is maintained twice: NetSuite has the customer's price level and quantity breaks, BigCommerce has a customer group with its own price list, and the two drift apart until a customer notices they were charged the wrong price.

What ECOSIRE builds

This is a build-to-order NetSuite customization. There is no pre-built package to download — ECOSIRE writes the connector against your NetSuite account, your BigCommerce store and your actual pricing model, then hands you the source.

Order and customer sync

A Scheduled Script polls the BigCommerce orders API and creates NetSuite Sales Order records, or Cash Sales where payment is captured up front. The BigCommerce order ID, channel and any storefront-specific attributes are stored in custom body fields. Customers are matched against existing Customer records by email or by a stored BigCommerce customer ID before a new record is created, so repeat shoppers do not accumulate duplicates. Guest checkouts can be routed to a single house account or created as individual Customers — decided during scoping, not by a fixed rule. Order status changes flow back to BigCommerce as NetSuite transactions move through their lifecycle.

Catalogue publishing

A Map/Reduce script publishes catalogue data from NetSuite Inventory Item, Assembly Item, Kit/Package and Matrix item records to BigCommerce products and variants. Matrix parents map to BigCommerce products and their children to variants, with option sets derived from your item options. The field map is held on a custom record so your merchandising team can add or repoint a field without a code change. Images, custom fields, categories and item-level flags are all mappable.

B2B price lists and customer groups

This is where most integrations stop short and where the real work is. NetSuite price levels, customer-specific pricing, quantity price breaks and item pricing are translated into BigCommerce price lists assigned to customer groups. A Scheduled Script keeps them synchronised, so a change made in NetSuite by the sales team is what the logged-in buyer sees on the storefront. In a OneWorld account, price lists can be built per subsidiary and per currency, so a buyer in one legal entity is not shown another entity's pricing. Where pricing is too complex to precompute, a RESTlet can serve a live price lookup at cart time instead.

Inventory and fulfillment

Available quantity is calculated from NetSuite — quantity available on the item, a Location-filtered saved search, or a custom formula agreed during scoping — and pushed on a schedule you set. A User Event script on the Item Fulfillment record marks the BigCommerce order shipped and writes the carrier and tracking number back, so the shopper's confirmation email and order history are populated from the same record the warehouse used. Refunds and cancellations map to Credit Memos and order closures.

Configuration, logging and roles

A custom record holds connection settings and field mappings. A second custom record logs every API call with its request, response, HTTP status and the NetSuite record touched, so a mismatch is diagnosed from a saved search rather than from memory. A RESTlet is deployed for inbound BigCommerce webhooks, giving near-real-time order capture instead of waiting for the next poll. A dedicated integration Role is created with only the permissions the scripts require, and a custom segment can tag storefront transactions for reporting alongside your other channels.

Who this is for

Wholesalers, distributors and brands running NetSuite with a BigCommerce storefront — particularly B2B sellers whose pricing lives in NetSuite price levels and customer-specific rates and who cannot maintain a second copy of it by hand. It also suits merchants running both a B2C and a B2B storefront on the same NetSuite item master.

How delivery works

1. Scoping call. We review your NetSuite pricing model, item types, locations and subsidiaries alongside your BigCommerce customer groups, price lists and storefront setup, and agree exactly which direction each object flows.

2. Fixed quote. You get a written scope covering record mappings, pricing logic, scripts to be built and assumptions, at a fixed price. Nothing is built until you approve it.

3. Build. ECOSIRE develops the SuiteScript 2.1 scripts, custom records, saved searches and role as an SDF project. Typical lead time is two to four weeks depending on catalogue size and pricing complexity.

4. Install in your sandbox. Deployed to your NetSuite sandbox and a BigCommerce staging store first, then tested with your real catalogue and a representative set of B2B accounts. You review; we adjust.

5. Production. After sign-off, the tested artifact goes to production with your team present, and the first catalogue, pricing and inventory syncs run under supervision.

6. Support. A support window follows go-live for defect fixes and configuration changes. You keep the source and the SDF project — the customization belongs to you.