A Shopify store that runs its finance, inventory and warehouse on NetSuite needs the two systems to agree on every order, stock count, shipment and refund. Without an integration, someone keys orders into NetSuite by hand, stock levels drift, and customers get tracking numbers late. That gets harder as order volume grows, and harder still for stores with several storefronts or B2B channels.
This guide explains what a Shopify NetSuite integration actually moves, the three ways to build one (Oracle's own connector, an iPaaS template, or a custom build on the APIs), how setup works on the most common path, where these integrations usually go wrong, and what the costs look like.
What a Shopify NetSuite Integration Syncs
Most integrations follow the same split. Shopify is where customers place orders, so orders, customers and refunds requested at checkout start there. NetSuite is the system of record for items, stock, fulfillment and accounting, so those flow out of NetSuite back to the store.
| Data | Usual direction | Notes |
| Orders | Shopify to NetSuite | Become NetSuite sales orders; cancellations follow |
| Customers | Shopify to NetSuite | Created or matched on the order |
| Items and products | NetSuite to Shopify | Titles, prices, images, metafields depending on the tool |
| Inventory | NetSuite to Shopify | Per location where multilocation inventory is mapped |
| Fulfillments | NetSuite to Shopify | Carrier, ship date, ship method, tracking number |
| Refunds | One direction, chosen per account | Cash refund or credit memo in NetSuite |
| Payouts | Shopify to NetSuite | Payout reports for reconciliation, where supported |
Oracle's documentation for its NetSuite Connector describes this flow plainly: the order and refund syncs export orders from the sales channel into NetSuite, and the fulfillment sync sends fulfillment data from NetSuite back to the storefront. By default the connector sends the carrier, ship date, ship method and tracking number once an item fulfillment record exists in NetSuite, for partial or complete shipments.
Celigo's Shopify NetSuite integration app lists a similar set of flows: Shopify orders to NetSuite sales orders, order cancellations, customers from Shopify to NetSuite, NetSuite items to Shopify products, fulfillments in both directions, and refunds in both directions (Shopify refunds become NetSuite cash refunds or credit memos).
Integration Options
There are three realistic ways to connect the two systems.
Oracle NetSuite Connector. This is Oracle's own connector product. It is configured in the FarApp portal (app.farapp.com), and Oracle documents a Shopify connector with order, refund, fulfillment, inventory, multilocation inventory and payout report syncs, plus a separate Shopify B2B connector. It is added to your account through your NetSuite account manager.
iPaaS templates. Integration platforms ship prebuilt Shopify NetSuite flows that you then adjust. Celigo's integration app is one example: it covers orders, cancellations, customers, items, fulfillments and refunds, and offers a 30-day free trial. An iPaaS gives you more room to add custom steps and other systems (a 3PL, a marketplace, a CRM) on the same platform, at the cost of another subscription and someone who knows the tool.
Custom integration via the APIs. Your own service reads orders and events from Shopify through its APIs and writes the matching records into NetSuite through NetSuite's APIs. You own every mapping rule, the retry logic and the monitoring. It is the most work up front and the only option with no ceiling on custom logic.
| Option | Best for | Limits | Cost basis |
| Oracle NetSuite Connector | Standard order to cash flows on one or a few stores | Maps only standard storefront API fields; refunds sync one way per account | NetSuite subscription add-on; real-time order sync may raise it |
| iPaaS template (for example Celigo) | Teams that want prebuilt flows plus room to customize | Another platform to license and maintain | Platform subscription; price not on the integration page |
| Custom build on the APIs | Unusual business rules, high volume, many entities or systems | Build time; you own maintenance | Development project plus hosting |
How to Set Up the Oracle NetSuite Connector for Shopify
This is the most common path for NetSuite customers, so the steps below follow Oracle's documentation.
Get the connector added to your account
The Shopify connector has to be on your NetSuite account before you can configure it. Oracle's docs say to contact your NetSuite account manager to add a new connector. Ask at the same time whether you need the B2C connector, the Shopify B2B connector, or both, and what real-time order sync would add to the price.
Authorize the Shopify store
Log in to the FarApp portal, select the Shopify connector and account, and open Settings, then Credentials. In the Shopify Shop Name field, enter only the shop name from your yourshopname.myshopify.com address, not the full URL. Save the settings and click Authorize Account. You are sent to Shopify to approve access and should get a success message back in NetSuite Connector. If authorization fails, Oracle's instruction is to contact NetSuite Support.
Decide how orders become transactions
Choose how Shopify orders should land in NetSuite: sales orders billed as cash sales, or invoices. This choice matters later, because the payout report sync only works when Shopify orders are billed as cash sales. Map payment methods, shipping methods, tax items and the customer record logic (one customer per buyer, or a shared web customer) before the first live sync.
Set up items and inventory
Match NetSuite items to Shopify products and variants by SKU. In Shopify, inventory tracking has to be on for each product you want to receive stock levels; Oracle's docs warn that sending inventory for an item that does not track inventory causes an error. If you sell from several Shopify locations, map each numeric Shopify location ID to a NetSuite location internal ID. If you mapped inventory before turning on Shopify's multilocation feature, delete the old mappings first.
Configure fulfillments and refunds
Fulfillment sync works without extra mapping for carrier, ship date, ship method and tracking number. Additional fields can be mapped, but only to standard Shopify API fields, not custom fields. For refunds, pick one direction per Shopify account. Oracle's recommendation for carts like Shopify is to process refunds in NetSuite and let the connector push them to the store.
Turn on payout reconciliation
Payout Report Sync creates a deposit record in NetSuite, deposits the matching cash sales and cash refunds, and adds lines for Shopify's fees. It runs every 24 hours from the moment you enable it. Before enabling it, reauthorize the Shopify account, define the payout accounts on the Settlement tab, and make sure cash sales are left undeposited so the sync can link them to the deposit.
Test, then go live
Run test orders through the full cycle: order import, partial and full fulfillment, a refund, and one payout. Add your email address to the connector's notification settings for each error type, since error emails are not sent otherwise.
Common Problems and Limits
Orders that bypass the connector. NetSuite Connector only looks for fulfillments on orders it synced itself. Orders imported into NetSuite by CSV are unknown to it, so their tracking numbers never reach Shopify.
Duplicates and resyncs. When the connector posts an order, it stores the NetSuite internal ID and marks the order as posted, which prevents duplicates. The flip side: an order that posted and was then deleted in NetSuite is not reposted automatically. To resend it, you delete it from the connector and retrieve it manually.
One-way refunds. A single Shopify account cannot sync refunds in both directions. Teams that refund in both places end up with refunds missing on one side. If cash refunds show wrong tax amounts, Oracle points to the Enable Order Total Validation on Cash Refund setting.
Custom fields. Fulfillment mappings reach only standard Shopify API fields. Data kept in Shopify custom fields needs another route.
Archived orders. The connector archives orders at 120 days old. They remain searchable by order number, and some processes, such as a late refund, pull them back out of the archive.
Payout reconciliation. Payout sync assumes cash sales in undeposited status. Stores that bill on invoices, or that deposit cash sales manually, will not get clean deposits from it.
Sync timing. Standard order sync runs on a schedule, and fixed errors are picked up on the next automatic run. Real-time order sync uses a Shopify webhook and, per Oracle, may increase your connector subscription.
Costs
Neither Oracle nor Celigo publishes a price for its Shopify NetSuite integration on the pages that describe it. Oracle's docs say NetSuite Connector is added through your account manager and that enabling real-time order sync may increase the subscription. Celigo's page offers a 30-day free trial and no price. Expect a quote in both cases, based on the connectors, flows and order volume you need.
A custom build is priced as a development project. Itexus publishes general figures on its fintech software development page: discovery and prototyping "start from around $30,000", and enterprise fintech projects "often range from $150,000 to $1,000,000+". A focused Shopify NetSuite integration usually sits well below a full enterprise project, but the scope (number of stores, entities and flows) decides the number.
When a Custom Integration Makes Sense
Your order logic does not fit standard fields. Bundles that explode into components, subscriptions, preorders or B2B price rules that live in Shopify custom fields are hard to express in a connector that maps only standard API fields.
You run several stores or subsidiaries. Multiple Shopify stores feeding different NetSuite subsidiaries, currencies and tax setups multiply mapping rules. A custom service can route each order by store, region or channel in code you control.
Refunds and returns happen in both systems. If customer service refunds in Shopify while the warehouse processes returns in NetSuite, a one-direction refund sync leaves gaps. Custom logic can reconcile both sides.
Finance needs exact reconciliation. Payout matching that depends on cash sales in undeposited status may not fit how your accounting team works, especially with invoices, gift cards or several payment providers.
Volume and timing matter. Flash sales and high order volume need queueing, retries and monitoring you can see and change, not a scheduled job you wait on.
How Itexus Can Help
Itexus has delivered 120+ integrations for neobanks, payment providers, robo-advisors, and trading systems, and takes on Shopify NetSuite integration projects. We have not published a NetSuite case; our closest work is a B2B billing and payments platform with real-time synchronization of invoicing and financial data with Xero and QuickBooks.
- Scoping: we map your order, refund, fulfillment and payout flows before choosing connector, iPaaS or custom.
- Custom connectors and middleware: built where off-the-shelf tools stop.
- Reconciliation logic: payouts, fees and refunds matched to your chart of accounts.
- Monitoring: errors and retries visible to your team.
Talk to our integration team about your setup.
Itexus is a trusted partner
Itexus delivered the app according to the requirements. The team met all development milestones and deliverables. They were efficient, friendly, and cooperative. Itexus team was very timely with updates, a regular meeting cadence, and ad-hoc questions and answers via Slack. The team was very responsive and still is.
Stive Jackson
RMD, Investing Fund
Itexus’ work positions the business well for an imminent launch. They excel at managing their team, presenting frequent product demos to ensure that the project is aligned with development goals. An affordable price structure coupled with remarkable technical skill makes them an attractive partner.
Phill Osolinski
CEO Ryze Rewards
The assigned team was easy to work with and they are especially strong collaborators and communicators. They demonstrated flexibility, professionalism, and trust in everything they did, and completed the work on time and budget.
Sue Wollan Fan
CEO Mango Connects
Itexus excelled at both experimental AI and sprint-oriented UI/UX tasks. Itexus did strong project management work, too, a necessity in such a complicated project.
Jesse Dubin
Senior PM Standard&Poors
They’re a great group of developers who really understand the reality of business.
Andreea Vanacker
CEO SPARKX5
Frequently Asked Questions
Does NetSuite have a native Shopify integration?
Yes. Oracle's NetSuite Connector includes a Shopify connector and a separate Shopify B2B connector. It is added to your account through your NetSuite account manager and configured in the FarApp portal.
What does a Shopify NetSuite integration sync?
Orders, customers and refunds go from Shopify to NetSuite; items, inventory and fulfillment details go from NetSuite to Shopify. Payout reports with Shopify Payments fees can be synced into NetSuite deposits.
Does the integration work with Shopify Plus?
The connector and iPaaS pages describe Shopify integrations without separate Plus editions, so confirm your plan and store setup with the vendor. Stores that run several storefronts, B2B channels or custom logic are where mapping and routing rules get complex. For B2B, Oracle documents a Shopify B2B connector with company, catalog, price list and reverse payment syncs.
How much does a Shopify NetSuite integration cost?
Oracle and Celigo do not publish prices for their Shopify NetSuite integrations; both are quoted. Oracle notes that real-time order sync may increase the connector subscription. Custom builds are priced by scope.
Can refunds sync both ways?
Not with NetSuite Connector on one Shopify account: you choose one direction. Oracle recommends refunding in NetSuite and syncing the refund to Shopify.
Should I use a connector or build a custom integration?
Start with a connector if your flows are standard. Consider a custom build when you need custom fields, several stores or subsidiaries, two-way refunds, or reconciliation the connector cannot produce. For related guides, see Stripe NetSuite integration and Shopify QuickBooks integration.
