Orders, fulfilment and stock in both directions
Shopify Payments payouts reconciled to the ledger
Built on the GraphQL Admin API and NetSuite's web services
Why it drifts
Why Shopify and NetSuite Drift Apart, and What Fixes It
Both ways orders out, stock back1 reconciliation report
A Shopify store and NetSuite drift apart one shortcut at a time. Orders are keyed into NetSuite by hand, stock by location is a nightly export that is wrong by lunchtime, a Shopify Payments payout lands in the bank as one figure, and a B2B customer has net terms in NetSuite and a card on file in Shopify.
The connector that was meant to fix it is often the next problem. Many were written on Shopify's REST Admin API, legacy since 1 October 2024; since 1 April 2025 new public apps must use the GraphQL Admin API, so a REST integration is on borrowed time.
NetSuite's side is better defined than most expect: its REST web services create, read and update records, run SuiteQL queries and process requests asynchronously, authenticating with OAuth 2.0 or token-based authentication rather than a user's login. An integration is the mapping between the two, written down, built on those services and reconciled on a schedule, so what did not sync is a line in a report rather than a surprise.
Where it drifts
Six Signs Your Shopify and NetSuite Are Out of Step
Each of these is a job someone does by hand on a Friday. Together they are the reason the integration gets rebuilt.
Orders Keyed Twice
An order placed on Shopify is typed into NetSuite by someone in the office, with a different SKU format, a rounding difference and no link back to the Shopify order number.
Stock a Day Old by Location
The nightly export says a warehouse has twelve; it shipped the last four this morning. Shopify sells from the wrong location and support handles the apology.
Payouts That Do Not Match the Bank
A Shopify Payments payout lands as one figure, net of fees and refunds, and finance spends the afternoon working out which orders it contains before the ledger balances.
Customers With Different Terms
A company account has net-thirty terms and a credit limit in NetSuite and pays by card on the storefront, because the customer record was never matched between the two.
A Connector Nobody Can Change
The sync was configured by a vendor years ago on an API that is now legacy. A new location, a custom field or a NetSuite update means a ticket, a wait and a workaround in a spreadsheet.
Sync Failures Nobody Sees
An order with a special character in the address fails to post, no alert fires, and the customer calls two weeks later asking where the parcel is.
What the integration covers
What a Shopify NetSuite Integration Covers
Order and Fulfilment Sync
Paid orders posted to NetSuite as sales orders with the Shopify order number kept, and fulfilment, tracking and invoices sent back to the customer's account.
Inventory by Location
Stock by warehouse pushed to Shopify's locations as it changes, so each location sells what it actually holds.
Pricing and B2B Catalogs
NetSuite price levels mapped to Shopify prices and to the B2B catalogs that give a company its own list, updated when NetSuite changes.
Customers and Companies
Customers and companies matched between the systems once, then kept in step: terms, credit limits, addresses and contacts.
Payouts and Fees to the Ledger
Shopify Payments payouts broken down into the orders, fees and refunds they contain and posted to the ledger, so the bank reconciles.
Monitoring and Reconciliation
A monitor that alerts on a failed message and a scheduled reconciliation that lists what did not sync, by record, before the warehouse does.
Map, build, test, run
How Our Shopify NetSuite Integration Works
Object Inventory
Field Mapping
Owner per Object
Sync Windows
OAuth and Tokens
Webhooks and Bulk Operations
NetSuite Records and SuiteQL
Retries and Alerts
Sandbox Runs
Reconciliation Counts
Edge Cases
Sign-Off per Object
Go-Live Window
Monitoring
Monthly Reconciliation
API Versions Moved
Object by object
What Moves Between Shopify and NetSuite, and How
Minutes for a stock changeYours code and mapping
Orders leave Shopify as they are paid and arrive in NetSuite as sales orders with the Shopify order number kept; fulfilment, tracking and invoices come back and appear in the customer's account. Stock moves the other way, by location, as NetSuite changes it; prices and B2B catalogs follow the price levels NetSuite holds. Customers and companies are matched once and then kept in step both ways.
Volume is handled by the platforms' own machinery. Shopify sends webhooks as events happen and runs bulk operations asynchronously for the large reads, returning a file to parse line by line without paging or throttling; NetSuite processes its side asynchronously too. A queue in between carries the peaks, and a failed message retries, then alerts.
You keep the mapping document, the code in your repository, the monitor and the monthly reconciliation, so a future developer can see what moves, where, and why.
Verified reviews
What Our Clients Say
2.1s
faster largest contentful paint
This team consistently goes above and beyond in terms of helping to ascertain the most viable and feasible outputs and outcomes for our evergrowing business needs.
Anthony Perrotta
E-Commerce Operations Manager
4 yrs
as their sole technical partner
They designed for where the product was going, not just what we asked for. Early on we described a single-company setup; they built the data model and permission layer so multi-tenancy wouldn’t require a rewrite later.
Alex Tee
CTO
Pick the way in
Three Ways Into a NetSuite Sync
NetSuite Integration Build
The full integration: the mapping document, the build on the GraphQL Admin API and NetSuite's web services, the reconciliation runs and the go-live window. For a store keying orders by hand or living with a connector nobody can change.
Mapping before the quote
Both directions
Payouts to the ledger
Reconciled monthly
Magento NetSuite Integration
The same integration for a Magento 2 or Adobe Commerce store: orders, fulfilment, stock, prices and customers on Magento's asynchronous API and NetSuite's web services, with the same mapping method and the same reconciliation.
Magento and Adobe Commerce
Asynchronous API
Same mapping method
Same reconciliation
Keep It Running
For an integration already live, by us or by someone else: the monitor watched, the monthly reconciliation run, the Shopify API version moved before the old one is retired and the NetSuite release tested in the sandbox before it lands.
API versions moved
Releases tested first
Monthly reconciliation
Alerts answered
Not our word for it
Licenses & Certifications
Solution Development Fundamentals
Shopify Verified Skill Badge
9 experts
Solution Planning Fundamentals
Shopify Verified Skill Badge
8 expertsTrusted by 100+ companies
Keep reading
Shopify Reading Before the Call
FAQ
Frequently Asked Questions
Still have questions?
Tell us about your store and we will come back with straight answers.
Talk to us
Do we need a connector app or custom code?
Either can work; what matters is who can change it. An app from the App Store is fast to install and slow to change when your mapping differs from its template. A custom integration on the GraphQL Admin API and NetSuite's web services is built to your mapping and lives in your repository. We build the second and we do not resell connectors, so the recommendation is not a commission.
Which NetSuite accounts and APIs do you work with?
Any NetSuite account with REST web services enabled and a role we can scope: an integration record with OAuth 2.0 or token-based authentication, a dedicated integration user, and permissions limited to the records in the mapping. SuiteQL covers the reads that do not fit a record call. The build runs in your sandbox first; if you do not have one, the mapping says how we test safely without it.
Do we need Shopify Plus for a NetSuite integration?
No. The GraphQL Admin API, webhooks and bulk operations are available to apps on every plan. What depends on the plan is the B2B feature set, company accounts and catalogs included, and some checkout customisation, so a B2B store syncing company terms needs the plan that carries them. We check that in the mapping before anything is built.
How often does stock sync?
As often as NetSuite changes it. Inventory moves on events rather than on a schedule, so a stock adjustment in NetSuite reaches the matching Shopify location in minutes. A scheduled full reconciliation runs alongside, so a missed event cannot leave a location wrong for long.
What about multiple locations or warehouses?
Each NetSuite location maps to a Shopify location, so stock is set per location and Shopify's own routing decides where an order ships from. Locations that should not sell online are excluded in the mapping, and a new warehouse is a mapping change rather than a rebuild.
Can it handle B2B catalogs and company terms?
Yes. NetSuite price levels map to Shopify prices and to the B2B catalogs that give a company its own list, and company records carry terms, credit limits and contacts both ways. Which B2B features your store has depends on your Shopify plan, which the mapping confirms first.
How are Shopify Payments payouts reconciled?
A payout lands in the bank as one figure, net of fees and refunds. The integration breaks each payout into the orders, fees and refunds it contains, using Shopify's own activity records, and posts them to the ledger against the right invoices, so the bank statement reconciles without an afternoon in a spreadsheet.
What happens when a sync fails?
The message is retried, and if it still fails it is logged with the record, the reason and the payload, and an alert goes to the people you name. Nothing is dropped silently. The monthly reconciliation lists anything that did not sync, by record, so a failure the alert missed is still found.
How long does a Shopify NetSuite integration take?
The mapping takes two to three weeks, because it is where every disagreement between the systems is settled. The build depends on the objects: orders, fulfilment and stock alone is a matter of weeks; payouts, B2B catalogs and company terms add to it. The estimate names the number after the mapping.
How is a Shopify NetSuite integration priced?
Fixed scope after the mapping, because the mapping decides how many objects move and in which directions, and no two stores sync the same set. There is no price list on this site; the written estimate comes with the mapping document.
Do you work with our NetSuite partner?
Yes, and we prefer to. Your NetSuite partner owns the account's customisations, saved searches and roles; we own the Shopify side and the integration between the two. The mapping document is the shared contract, and the integration user, roles and tokens are set up with them.
Is the integration code ours?
Yes. The code lives in your repository, the app is installed on your store under your account, the NetSuite integration record and tokens are yours, and the mapping document is written for whoever maintains it next. Nothing is hosted on a server you cannot see.
What happens when Shopify retires an API version?
Shopify releases API versions on a schedule and retires the old ones, which is how a connector written on the REST Admin API ended up on borrowed time. We move the integration to a supported version before the old one is retired and test each NetSuite release in the sandbox before it lands, as part of keeping it running.
Can you fix an integration another agency built?
Yes. We read the existing code and the NetSuite integration record inside two business days, list what moves, what fails and what sits on a retired API, and give you a fixed scope to stabilise it or a reason to replace it. If the mapping was never written down, that is the first thing we produce.
Let’s build something great together!
Ready to Make Shopify and NetSuite Agree?
Send us what moves between your store and NetSuite today, and what does not. We come back with the mapping outline and a written estimate.