NetSuite

NetSuite Shopify Experts for ERP Sync and B2B

Oracle NetSuite builds its own connector for Shopify. Oracle's docs call it NetSuite Connector, while its Shopify App Store listing reads NetSuite ERP Connector. It's an add-on module to a NetSuite subscription that syncs products, customers, inventory, sales orders and fulfilment details, and it covers Shopify B2C, B2B and POS.

A NetSuite Shopify project is mostly preparation: switching on the right NetSuite features, matching every SKU, setting tax up properly and deciding how Shopify Payments payouts become deposits. That preparation decides whether month-end closes cleanly or turns into a spreadsheet exercise.

The people who do it are usually a NetSuite consultancy, or with an independent NetSuite developer who has run the Connector before. If the listing below doesn't fit your setup, the order and inventory management services linked under it take on the same NetSuite Connector jobs.

For a short brief, list your Shopify plan, your sales channels (online, POS, B2B), your warehouse locations and any 3PL, and whether you take payments through Shopify Payments.

NetSuite Connector work, from SuiteApp to payouts

NetSuite is strict about one thing above all: every Shopify SKU must match a NetSuite item exactly, one to one. Connector projects are won or lost on preparation like that, long before the first order syncs.

Account preparation. Switching on the NetSuite features the Connector depends on, installing the Connector SuiteApp, then authorising the Shopify store in the Connector and mapping fields.

Items and SKUs. Aligning the item hierarchy so those matches hold. Catalogues with years of edits leave strays on both sides, and each one needs fixing before go-live.

Tax and test orders. Setting up tax nexus, then creating taxable test orders to confirm NetSuite assigns tax to each item correctly. Oracle expects you to supply sample or test data during set-up, so plan for it.

Fulfilment routing. Tracking inventory across several warehouse locations and sending orders on to 3PLs, vendors or warehouses for fulfilment.

B2B. Syncing companies, catalogues and price lists, posting invoices and handling customer deposits for trade buyers.

Payouts. Configuring Shopify Payments payout sync so fees appear as lines on the NetSuite deposit linked to each order, with cash sales and cash refunds set up to match.

Metafields and monitoring. Mapping Shopify metafields and custom fields into NetSuite, then watching the sync once orders flow. A quiet error in week one becomes a reconciliation problem in month three.

Choosing a NetSuite developer who has run the Connector

One question sorts NetSuite candidates fast: where do you configure the Connector? Its administration still runs in its own older web portal, not inside the NetSuite UI. Anyone who has taken a Shopify store live on it knows that, along with how store authorisation and field mapping work there.

Ask for a live store. Implementing NetSuite and running the Connector against a live Shopify store are different skills. Ask for a store they took live, the channels it sells through and how its payouts reconcile today.

Ask about SKUs before anything else. If their plan starts with field mapping rather than an audit for exact SKU matches, they're working in the wrong order.

Ask how payouts will reconcile. Payout sync needs cash sales, not invoices, left undeposited. If your finance team relies on invoices for online orders, that's a design conversation, not a checkbox.

Red flags. No test orders before go-live. Switching on real-time order sync without checking what it does to the subscription. Vague answers about who watches for errors after launch.

Start with a SKU audit. Pay for a list of mismatches and a proposed fix. It's small, useful on its own whoever does the build, and it reveals their method.

NetSuite Shopify prerequisites and the traps after launch

It's a paid add-on. The Connector is a module on top of your NetSuite subscription, added through your NetSuite account manager. Its App Store page lists separate plans for B2C, POS and B2B. Confirm billing terms with Oracle before you budget, and keep it apart from implementation time.

Features first. NetSuite features, including SOAP and REST web services and token-based authentication, must be enabled before the Connector SuiteApp installs. They are a prerequisite, not something to fix afterwards.

Real-time sync is optional. Orders can sync in real time through a webhook, but switching it on may raise the subscription. If you used it before and want it back, remove the old webhook in Shopify first.

Payout sync needs re-authorising. Before Shopify Payout Report sync works, the Shopify account has to be re-authorised in the Connector to update its permissions. It also fails on cash sales that are already deposited, so switching it on mid-month needs care.

B2B catalogues are per company. The Connector assigns catalogues to a company, not to individual company locations. A trade buyer whose branches need different catalogues needs a workaround designed up front.

POS is its own channel. Shopify POS is supported, so shop sales can flow into NetSuite with online orders. Decide early how each shop maps to a NetSuite location.

Two names, one product. The App Store says NetSuite ERP Connector; Oracle's docs say NetSuite Connector. Search both when you hit an error.

NetSuite configuration jobs to brief

Treat these as separate jobs with separate sign-offs. A SKU clean-up and payout reconciliation share nothing except the Connector, and often need different people.

Connector go-live

Feature checks, SuiteApp install, store authorisation, field mapping and test orders

SKU and item clean-up

Every Shopify SKU matched to a NetSuite item, one to one

Payout reconciliation

Shopify Payments payouts as NetSuite deposits, fees as deposit lines

B2B catalogues and invoicing

Companies, price lists, invoice posting and customer deposits

3PL and warehouse routing

Orders sent to 3PLs, vendors or warehouses, stock tracked by location

Metafield mapping

Shopify metafields and custom fields carried into NetSuite records

Questions for a NetSuite expert before go-live

How do I check whether a NetSuite expert is an Oracle partner?

Ask, then verify. Oracle NetSuite runs its own network of Solution Providers and Alliance Partners, who provide consulting, integration and implementation services alongside the NetSuite sales team. Where the status matters, get the firm's programme name and confirm it with Oracle NetSuite yourself.

Do I need a NetSuite developer, or can an administrator set up the Connector?

Much of it is configuration: features, the SuiteApp, store authorisation, field mapping and tests. A capable NetSuite administrator can handle a lot of that. A developer earns their fee at the edges, such as metafield and custom field mappings, tax set-up across several nexuses, and anything the standard flows don't cover.

How do Shopify refunds reach NetSuite?

Through refund sync in the Connector. If you also want payouts to reconcile, Oracle's guidance is to use cash refunds in NetSuite and keep refund sync enabled. That is a finance decision as much as a technical one, so agree the refund method with your accountant before go-live, not after the first payout refuses to reconcile.

What does a NetSuite integration cost for a Shopify store?

Three separate lines. The NetSuite subscription, the Connector add-on and implementation time. Real-time order sync can add to the subscription, so decide whether you need it before signing. Ask for implementation quoted by job rather than as one lump, so you can see where the hours go.

How should we test the Connector before go-live?

Trace each channel to the record NetSuite should create. An online order paid through Shopify Payments should become a cash sale, a B2B order should post as an invoice, and a POS sale should land at the right location. Check tax on each one, then confirm the deposit's fee lines match what Shopify Payments actually paid.