Skip to content
CRM · Two-way sync platform

Shopify connector for two-way sync.

Keep Shopify and your business systems aligned with Stacksync. Sync Customers, Products and ProductVariants within the connector’s object and field requirements, with two-way sync for eligible records.

  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Shopify

Adopted by fast-scaling companies moving mission-critical data in real time

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
Record types

Shopify objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Products
Supported
ProductVariants
Supported
Orders
Supported
Customers
Supported
View all 6 object types and restrictions
ProductMedias
Supported
Abandoned Checkouts
Supported

Read the Shopify object and setup guide

Connection setup

Shopify connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
GraphQL Admin API (primary) and REST Admin API (legacy)
Account access
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
How changes are detected
The Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Sync directions

  • Read data Documented
  • Write data Documented
ShopifyStacksync setup guide
Setup prerequisites for your administrator
  • 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.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Shopify integration.

Assign product content, variants, prices, customer identity, stock, and order state to explicit owners. A catalog update and a fulfillment command need different permissions and acceptance tests.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
ShopifySource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Keep Product and ProductVariant identifiers separate from SKU and display title. Retain the Order and Customer identifiers needed to resolve a purchase without relying only on email.
Load related records in the right order
Resolve the customer and product/variant references needed by the destination order model. Inventory, fulfillment, and refund requirements need explicit operation-level confirmation beyond the six listed objects.

Mapping checks by record type

Customers

✅ Supported

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.
Fields to consider
Source customer ID · Person/company classification · Legal entity or business unit · Destination identity reference
Related records to resolve first
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test before going live
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Products

✅ Supported

Identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Fields to consider
Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference
Related records to resolve first
Resolve units, variants, categories, and applicable price lists before order lines.
Test before going live
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

ProductVariants

✅ Supported

Identity
Retain variant ID separately from parent-product ID and SKU; a product with several variants must keep several identities.
Fields to consider
Source variant ID · Parent product reference · SKU · Option values · Unit or pricing reference
Related records to resolve first
Resolve the parent product and variant options before order or stock references.
Test before going live
Test two variants sharing a parent product and a changed SKU without losing order-line identity.

Orders

✅ Supported

Identity
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Fields to consider
Source order ID · Customer reference · Line references and quantities · Order status · Currency
Related records to resolve first
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test before going live
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Shopify integration in four steps.

A multi-line purchase retains the correct variant and customer references, while repeated delivery leaves one intended order and fulfillment state.

View the four setup tests and expected results

  1. Confirm the intended Shopify account and grant

    Use the documented setup with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity.

    Expected result: The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure.

  2. Exercise a product variant and an order independently

    Validate one selected writable product field and one required order operation under the configured app scopes. Reconcile quantity and money fields using the agreed destination model.

    Expected result: The correct variant and order are addressed, and every requested operation is confirmed rather than inferred from the object name.

  3. Test writes in the directions you need

    Select one eligible Shopify object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Shopify records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Shopify integration.

Diagnose record matching, delayed changes, and rejected operations
Product data works but an order workflow cannot complete
Review the selected object, required app scopes, writable fields, and exact business operation. Objects outside the six listed objects require confirmation.
The first load looks correct but later results differ
The Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Shopify object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Shopify workflow with an engineer

Shopify integration guides

FAQ

Shopify connector FAQ

How should I plan an integration with Shopify?

Products, variants, customers, and orders need separate identity and operation checks. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Shopify connector write changes back?

Stacksync supports reads and writes for eligible Shopify objects. Check the selected fields, account permissions, and the other system’s connector. Validate one selected writable product field and one required order operation under the configured app scopes. Reconcile quantity and money fields using the agreed destination model.

Which identifiers should I preserve for Shopify data?

Keep Product and ProductVariant identifiers separate from SKU and display title. Retain the Order and Customer identifiers needed to resolve a purchase without relying only on email.

Which related records should I load first for Shopify?

Resolve the customer and product/variant references needed by the destination order model. Inventory, fulfillment, and refund requirements need explicit operation-level confirmation beyond the six listed objects.

What should I check if Shopify data is missing or delayed?

Review the selected object, required app scopes, writable fields, and exact business operation. Objects outside the six listed objects require confirmation.

What will we cover in a Shopify integration demo?

Start with one workflow and a sample record from Customers, Products and ProductVariants. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore Shopify connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

280 integration guides

CRM · 45

ERP · 45

Database · 49

Data warehouse · 29

Business productivity · 38

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 5

E-commerce · 8

Human resources · 13

Marketing · 9

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

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.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started