Keep supported NetSuite and Shopify records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Example workflow
Sales order process handoff
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting eventA change involving NetSuite Invoice or Shopify Orders needs a defined result in the other system.
01
Start with NetSuite Invoice and Shopify Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
02
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
03
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Set up NetSuite and Shopify from Claude or ChatGPT
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
1. Add the Stacksync MCP server
Server URL
https://mcp.stacksync.com/mcp
In Claude
Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.
In ChatGPT
Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Record matchingDetermine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownershipSeparate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect NetSuite and Shopify
Put your NetSuite and Shopify data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one NetSuite and Shopify workflow to test, define what success looks like, and decide who handles failed updates.
01
Sync customers, sales orders, and invoices to an operational Postgres database so teams query ERP data without writing SuiteScript.
02
Expose item and inventory data to internal applications through a continuously synced database table.
03
Sync orders, customers, and inventory into Postgres for operational reporting across stores.
04
Keep customer records aligned between Shopify and a CRM for segmentation and lifetime-value analysis.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
NetSuite
Read and write support varies by record
Record types covered in the setup guide
Record types
Coverage and requirements
Customer
Contact
Nexus
Tax Type
Sales Tax Item
Billing Schedule Customer Subsidiary Relationship
Vendor
Vendor Category
Employee
Other Name Category
Vendor Subsidiary Relationship
Project
Project Status
Project Task
Job Type
Task
Partner
Customer Status
Phone Call
Support Case
Calendar Event
Note Type
Message
Job Status
Reading: Supported. Updating this object: Supported.
Invoice
Sales Order
Check
Credit Card Charge
Credit Card Refund
Credit Memo
Currency Revaluation
Customer Deposit
Customer Payment
Customer Refund
Deposit
Deposit Application
Estimate
Expense Report
Intercompany Journal Entry
Advanced Intercompany Journal Entry
Item Fulfillment
Item Receipt
Journal Entry
Opportunity
Purchase Order
Transfer
Vendor Bill
Vendor Credit
Vendor Payment
Supported. Confirm field permissions and sync direction.
All custom objects
Reading: Supported. Updating this object: Request access.
Account
Accounting Period
Bin Transfer
Currency Rate
Price Level
Term
Subsidiary
Contact Category
Contact Role
Customer Category
Customer Message
Department
Expense Category
Classification
Location
Reading: Supported. Updating this object: Coming soon.
Lead
Case
Reading: Request access. Updating this object: Request access.
Saved Searches
Reading: Supported. Updating this object: Read-only object.
Published Reports
Reading: Request access. Updating this object: Read-only object.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
NetSuite
Integration interface
SuiteTalk REST and SOAP web services, plus SuiteQL queries
Authentication
Token-Based Authentication (TBA): enable REST Web Services (and SOAP Web Services) + Token-Based Authentication in NetSuite, create an integration record to get Consumer ID/Secret
Change detection
Read and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.
Limitations to check
Write coverage varies: the saved support matrix marks several accounting objects as Coming soon and custom-object writes as Request access.
NetSuite Account is an accounting object; do not map it to a CRM Account merely because the names resemble each other.
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
Have the Shopify administrator create the custom app described in the connection guide and configure its required scopes and redirect URL.
Supply the shop name, client ID, and client secret through the Stacksync authorization flow.
Limitations to check
The saved catalog lists six supported object types. Objects outside that list require confirmation. The connector documents two-way sync; confirm writable fields and operations for each selected object.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
NetSuite setup checklist
Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Order-to-invoice handoff: Shopify Orders provides context for NetSuite Invoice. These are related records, not equivalent entities.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
NetSuite
Documented record · Supported
Shopify
Documented record · Supported
Record identity
Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
Field ownership
Finance owns invoice posting; the order system supplies the approved commercial context.
Fields to include
Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Order-to-fulfillment handoff: Shopify Orders provides context for NetSuite Item Fulfillment. These are related records, not equivalent entities.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
NetSuite
Documented record · Supported
Shopify
Documented record · Supported
Record identity
Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.
Field ownership
The fulfillment owner decides when an approved order can ship and how cancellations are handled.
Fields to include
Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Compare whether NetSuite Customer and Shopify Customers describe the same customer in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
NetSuite
Documented record · Read: Supported. Write: Supported.
Shopify
Documented record · Supported
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Compare whether NetSuite Sales Order and Shopify Orders describe the same sales order in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
NetSuite
Documented record · Supported
Shopify
Documented record · Supported
Record identity
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership
Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
Source order ID
Customer reference
Line references and quantities
Order status
Currency
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Before linking NetSuite Contact to Shopify Customers, check whether the customer is an individual or a company. Match the correct record type in each system.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
NetSuite
Documented record · Read: Supported. Write: Supported.
Shopify
Documented record · Supported
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
This pair can involve both record sync and process handoffs. Keep the Invoice / Orders relationship explicit: copying fields and creating a downstream business transaction require different validation.
Stacksync managed sync
Best fit
Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
Best fit
A vendor-built integration may fit if it supports your NetSuite and Shopify record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Invoice / Orders, update direction, account tier, and related-record handling.
Custom API or workflow
Best fit
Consider explicit orchestration for the Invoice / Orders handoff.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
Best fit
Consider for a one-time NetSuite / Shopify migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Sales order process handoff
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Invoice or Orders record needs a defined result in the other system.
Start with NetSuite Invoice and Shopify Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Sales order process handoff
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Item Fulfillment or Orders record needs a defined result in the other system.
Start with NetSuite Item Fulfillment and Shopify Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Customer sync test
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Customer or Customers record needs a defined result in the other system.
Start with NetSuite Customer and Shopify Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Reconcile NetSuite business records with Shopify
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in NetSuite needs operational visibility through Products or ProductVariants.
Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in Shopify; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Invoice / Orders
Test case
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Item Fulfillment / Orders
Test case
Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Customer / Customers
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Sales Order / Orders
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated sales order change
Investigate
Inspect NetSuite Invoice and Shopify Orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated sales order change
Investigate
Inspect NetSuite Item Fulfillment and Shopify Orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated customer change
Investigate
Inspect NetSuite Customer and Shopify Customers, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
A record type or update is unavailable
Investigate
Check the NetSuite and Shopify connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
See how each system detects changes and which updates the other system can receive.
Each direction has its own permissions and record requirements.
NetSuite → Shopify Timing depends on the connected systems
Detect changesRead and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.
Apply updatesSelected writable fields update in Shopify. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Shopify → NetSuite Timing depends on the connected systems
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in NetSuite. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Update timing and record limits
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
FAQ
NetSuite and Shopify integration FAQ
Stacksync connects NetSuite and Shopify with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token. Have the Shopify administrator create the custom app described in the connection guide and configure its required scopes and redirect URL. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Invoice in NetSuite and Orders in Shopify. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
This pair can involve both record sync and process handoffs. Keep the Invoice / Orders relationship explicit: copying fields and creating a downstream business transaction require different validation.
