1. Home
  2. NetSuite integration
  3. NetSuite and Shopify

NetSuite Shopify integration: Oracle's connector pulls orders every 20 minutes, with limits worth knowing first

Oracle has its own Shopify connector for NetSuite, part of a tool called NetSuite Connector. It pulls Shopify orders into NetSuite every 20 minutes and sends fulfillments back every 90. Each Shopify store needs its own connector, even on Shopify Plus.

Checked 18 November 2026

Oracle’s NetSuite Connector syncs Shopify on a fixed timetable

NetSuite Connector is Oracle’s tool for linking NetSuite to online stores. Shopify and Shopify POS are both on its list. You add the Shopify connector through your NetSuite account manager. Orders sync to NetSuite, and fulfillments sync from NetSuite.

Scroll the table sideways to see every column.

Sync From To How often, per Oracle
Order sync Shopify NetSuite Every 20 minutes
Fulfillment sync NetSuite Shopify Every 90 minutes
Product sync NetSuite Shopify Every 60 minutes
Price and quantity sync NetSuite Shopify At 60-minute intervals
Payout report sync Shopify NetSuite Every 24 hours

So an order may wait up to 20 minutes to reach NetSuite. Tracking can take up to 90 minutes to reach Shopify after you ship.

There are faster options. Real-time order sync adds a webhook in Shopify, and Oracle warns it “may result in a subscription increase”. Real-time price and quantity sync depends on scripts in NetSuite. Either way, NetSuite stays the primary record for SKU data, so product data is entered in NetSuite first.

Each Shopify store needs its own connector

Oracle says you need a separate Shopify connector account for every store, even on Shopify Plus. You must not point an existing connector at a different shop. Add a new connector instead.

Plan for it early. A US store, a Canada store and a wholesale store mean three connectors, each with its own mappings.

The connector signs in to NetSuite with token-based authentication

Oracle’s setup page says NetSuite Connector uses token-based authentication (TBA) to reach your NetSuite account. TBA is the older key-and-secret sign-in that Oracle is phasing out.

  • The token belongs to an employee who must have the Administrator role. Oracle’s own REST setup page says the opposite for web services in general. It does not advise the administrator role there, for security reasons.
  • Oracle warns that deleting or inactivating that user stops the token and breaks the connection. So use a named integration user, not a person who may leave.
  • NetSuite Connector does not support Release Preview accounts. Oracle points to a sandbox for testing.

Oracle closes TBA to new links at 2027.1. Support for existing ones ends at 2028.2, for now. The full list of dates is on our NetSuite integration page. The Shopify connector pages we read on 18 November 2026 do not say how the connector will move to OAuth 2.0. Ask Oracle before you sign a renewal that runs past 2027.1.

Eight limits in Oracle’s own Shopify connector help

Oracle’s FAQ and troubleshooting pages list these. Read them before you sign.

  1. Wholesale prices arrive as discounts. Oracle says the connector sends the regular price discounted down to the wholesale amount, because of which Shopify field holds the item price.
  2. No default item on every order. The connector cannot add one. Oracle points to a NetSuite workflow or script.
  3. Metafields can be added and updated, never deleted. Shopify metafields are custom fields on a product. Deletes are done by hand in Shopify.
  4. No transfer orders in Shopify. So the connector cannot show incoming stock there.
  5. Variants: a 100 cap that Shopify may no longer have. Oracle’s troubleshooting page says a parent item can have at most 100 variants and calls it a Shopify limit. Shopify’s GraphQL Admin docs, which we read on 18 November 2026, give a default of 2048 variants per product. If a product has more than 100 variants, test it in a sandbox first.
  6. Order totals must match. A validation script checks the NetSuite totals against the order. If the check fails, the transaction is not created and the error shows in NetSuite Connector.
  7. SuiteTax needs its script first. With SuiteTax, the STE UE Transaction script must run before the connector’s other scripts.
  8. Payout sync needs cash sales. The Shopify payout report sync works only when Shopify orders are billed as cash sales, not invoices.

Shopify B2B orders follow their own rules in the connector

Oracle documents a separate set of B2B syncs. These are the parts that change the NetSuite setup.

  • Each Shopify B2B company’s buyers sync to NetSuite as sub customers.
  • One setting, PostCustomerDepositForShopifyB2B, changes how orders land. With it on, a B2B order becomes a sales order in Pending Approval.
  • That flow supports Net 30, 60 and 90 terms and partial shipments.
  • The reverse payment sync looks only at NetSuite transactions from the last 90 days by default.
  • Catalogs attach to a company and apply to all its locations. Per-location catalogs are not supported.

A distributor with branch-level price lists should test that last point early.

A custom build must use Shopify’s GraphQL API and handle webhook retries

Shopify’s REST Admin API became a legacy API on October 1, 2024. From April 1, 2025, new public apps must use only the GraphQL Admin API. Two webhook rules then shape the code:

  • A failed webhook is retried 8 times over 4 hours. After that, a subscription made through the API is deleted.
  • The same webhook may arrive twice. The X-Shopify-Webhook-Id header lets your code skip the copy.

Oracle’s own FAQ says the connector cannot handle transfer orders because “Shopify currently does not support transfer orders in REST API”. That suggests the connector still calls Shopify’s REST Admin API. Ask Oracle which Shopify API it uses before you plan around it.

On the NetSuite side, a Shopify order becomes a sales order, record ID salesorder. REST web services need the SuiteTax feature to create one. Shipping it means a conversion to item fulfillment, which needs the inventoryLocation field. Map locations first.

A custom build fits when stores, variants or B2B catalogs break the connector’s rules

The connector suits a store whose orders are standard and whose product data lives in NetSuite. Look harder at a custom build, or a mix, when any of these is true:

  • You run many stores and want one set of rules across them.
  • Orders need logic the connector cannot hold, such as a default item on every order.
  • You sell products with more than 100 variants.
  • Your B2B catalogs differ by location.
  • You need orders in NetSuite in less than 20 minutes and do not want a subscription change.

Agents that work on top of NetSuite data are covered on NetSuite AI agents.

Our team has taken NetSuite live

That is the experience we bring to this pairing. On a Shopify project, our part would start on the NetSuite side: items and SKUs, tax, forms, roles and the integration user. For a new account, see NetSuite implementation.

The first call is free.

Questions

Does Oracle have its own Shopify connector for NetSuite?

Yes. Oracle's NetSuite Connector lists Shopify and Shopify POS among the storefronts it supports. You add the Shopify connector by contacting your NetSuite account manager. It moves orders into NetSuite and sends fulfillments, products, prices and stock back to Shopify on a timetable.

How often does NetSuite Connector sync Shopify orders?

Every 20 minutes by default, from Shopify into NetSuite. Fulfillments go the other way every 90 minutes, and product data every 60. Oracle also offers real-time order sync through a webhook. Its help page warns that turning that on may raise your NetSuite Connector subscription, so price it before you switch.

Does NetSuite Connector work with Shopify B2B?

Yes, Oracle documents a set of Shopify B2B syncs. Company buyers come into NetSuite as sub customers. Orders can arrive as sales orders in Pending Approval status with a customer deposit, which suits Net 30, 60 and 90 terms. Catalogs and price lists sync from NetSuite. One gap: catalogs attach to a whole company, never to a single location.

Can one connector run several Shopify Plus stores?

No. Oracle says you need a separate Shopify connector account for every store, even on Shopify Plus. You also must not repoint an existing connector to a different shop. A brand with a retail store and a wholesale store needs two connectors.

What API integrations are available for NetSuite?

For a Shopify link, there are three paths. Oracle's NetSuite Connector covers it ready-made. An iPaaS tool can host the flow, if you check which NetSuite API its connector calls. Or a custom build reads Shopify's GraphQL Admin API and its webhooks, then writes to NetSuite's REST web services with OAuth 2.0. Our NetSuite integration page compares all the NetSuite routes.

What does a NetSuite Shopify integration cost?

We found no public NetSuite Connector price on Oracle's help pages, so ask Oracle for a quote. Three things move the number. Each store needs its own connector. Real-time order sync may raise the subscription. And any rule the connector cannot hold, such as a default item on every order, becomes a NetSuite script or a custom build.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Decide between Oracle's Shopify connector and a custom build

The first call is free. Bring your store count, your B2B rules and your largest products, and we can go through where the connector fits and where it does not.

Book a NetSuite and Shopify call