MotherDuck
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Data warehouse / CRM · Two-way sync platform
MotherDuck and Shopify integration — two-way sync
Keep supported MotherDuck and Shopify records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
- Field mappings and sync direction under your control
- Inspect and resolve record errors in one dashboard
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 reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving the proposed sales order table in MotherDuck or Shopify Orders needs a defined result in the other system.
Start with the proposed sales order table in MotherDuck 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.
What to verifyTest a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Review records and field ownershipMapping essentials
Records and field ownership
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| MotherDuck record | Shopify record | Record matching | Field ownership |
|---|---|---|---|
| Proposed sales order tableProposed table; choose its name and schema.Reporting dataset | OrdersDocumented record: Supported | Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. | Decide which system approves the order and which can cancel or amend it after fulfillment begins. |
| Proposed product or catalog item tableProposed table; choose its name and schema.Reporting dataset | ProductsDocumented record: Supported | Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. | Assign ownership for catalog content, price, and stock separately. |
| Proposed product variant tableProposed table; choose its name and schema.Reporting dataset | ProductVariantsDocumented record: Supported | Retain variant ID separately from parent-product ID and SKU; a product with several variants must keep several identities. | Choose who owns variant definitions, prices, and availability; they may have different sources. |
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 MotherDuck and Shopify
Put your MotherDuck 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 MotherDuck and Shopify workflow to test, define what success looks like, and decide who handles failed updates.
Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
Sync modeled MotherDuck tables outward to operational tools for activation
Sync orders, customers, and inventory into Postgres for operational reporting across stores.
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.
Shopify
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | MotherDuck | Shopify |
|---|---|---|
| Integration interface | SQL through DuckDB clients and drivers using a MotherDuck (md:) connection | GraphQL Admin API (primary) and REST Admin API (legacy) |
| Authentication | Access token created in MotherDuck | OAuth via a custom Shopify app |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
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.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
MotherDuck
- Integration interface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- 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
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Limitations to check
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Shopify
- Integration interface
- 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.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare MotherDuck and Shopify access
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.
MotherDuck setup checklist
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Shopify setup checklist
- 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.
Setup guides: Authorize Shopify
Prepare to go live
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.
Use the MotherDuck and Shopify planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Proposed sales order table in MotherDuck (choose its name) / Orders
Plan a sales order dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- MotherDuck
- Your database schema
- 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.
References: Shopify: Orders documentation
Reporting dataset
Proposed product or catalog item table in MotherDuck (choose its name) / Products
Plan a product or catalog item dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- MotherDuck
- Your database schema
- Shopify
- Documented record · ✅ Supported
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
References: Shopify: Products documentation
Reporting dataset
Proposed product variant table in MotherDuck (choose its name) / ProductVariants
Plan a product variant dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- MotherDuck
- Your database schema
- Shopify
- Documented record · ✅ Supported
- Record identity
- Retain variant ID separately from parent-product ID and SKU; a product with several variants must keep several identities.
- Field ownership
- Choose who owns variant definitions, prices, and availability; they may have different sources.
Fields to include
- Source variant ID
- Parent product reference
- SKU
- Option values
- Unit or pricing reference
- Record dependencies
- Resolve the parent product and variant options before order or stock references.
- Validation
- Test two variants sharing a parent product and a changed SKU without losing order-line identity.
- Recovery
- Repair parent and variant references before retrying dependent inventory or order updates.
References: Shopify: ProductVariants documentation
Reporting dataset
Proposed customer table in MotherDuck (choose its name) / Customers
Plan a customer dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- MotherDuck
- Your database schema
- 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.
References: Shopify: Customers documentation
Compare integration approaches
Use MotherDuck Proposed sales order table in MotherDuck (choose its name) and Shopify Orders for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
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: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. 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 MotherDuck 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 Proposed sales order table in MotherDuck (choose its name) / Orders, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when MotherDuck and Shopify need a transformation, approval, or action outside a direct record sync.
- 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.
File or scheduled snapshot
- Best fit
- Consider for a one-time MotherDuck / 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 reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed sales order table in MotherDuck (choose its name) or Orders record needs a defined result in the other system.
- Start with MotherDuck Proposed sales order table in MotherDuck (choose its name) 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 multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Product or catalog item reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed product or catalog item table in MotherDuck (choose its name) or Products record needs a defined result in the other system.
- Start with MotherDuck Proposed product or catalog item table in MotherDuck (choose its name) and Shopify Products. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve units, variants, categories, and applicable price lists before order lines.
- 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 two variants of one product, a changed SKU, and a price that applies to only one market or currency.
If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Product variant reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed product variant table in MotherDuck (choose its name) or ProductVariants record needs a defined result in the other system.
- Start with MotherDuck Proposed product variant table in MotherDuck (choose its name) and Shopify ProductVariants. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the parent product and variant options before order or stock 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 two variants sharing a parent product and a changed SKU without losing order-line identity.
If it fails: Repair parent and variant references before retrying dependent inventory or order updates.
Coordinate Shopify commerce data with MotherDuck
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A catalog, order, or fulfillment change in Shopify matters to a selected destination dataset.
- Choose the commerce entity from Products or ProductVariants; separate products, variants, orders, and fulfillments.
- Preserve order and line references through the MotherDuck process. Define many-to-one or one-to-many relationships explicitly.
- Assign separate ownership for commercial approval, inventory, and fulfillment, including partial cancellations or returns.
Expected result: A split fulfillment and repeated request preserve line quantities without duplicate orders or shipments.
If it fails: Look up existing downstream records before retrying creation; reconcile current order and fulfillment states.
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.
Proposed sales order table in MotherDuck (choose its name) / 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.
Proposed product or catalog item table in MotherDuck (choose its name) / Products
Test case
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Expected result
The expected product or catalog item relationship is preserved with no duplicate action or unintended write.
Proposed product variant table in MotherDuck (choose its name) / ProductVariants
Test case
Test two variants sharing a parent product and a changed SKU without losing order-line identity.
Expected result
The expected product variant relationship is preserved with no duplicate action or unintended write.
Proposed customer table in MotherDuck (choose its name) / 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.
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 MotherDuck Proposed sales order table in MotherDuck (choose its name) 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 product or catalog item change
Investigate
Inspect MotherDuck Proposed product or catalog item table in MotherDuck (choose its name) and Shopify Products, their IDs, and the destination error.
Next action
Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Rejected or repeated product variant change
Investigate
Inspect MotherDuck Proposed product variant table in MotherDuck (choose its name) and Shopify ProductVariants, their IDs, and the destination error.
Next action
Repair parent and variant references before retrying dependent inventory or order updates.
A record type or update is unavailable
Investigate
Check the MotherDuck 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.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between MotherDuck and Shopify
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
MotherDuck Shopify 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 Shopify. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Shopify MotherDuck 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 MotherDuck. 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.
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
FAQ
MotherDuck and Shopify integration FAQ
-
Stacksync connects MotherDuck 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. Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form. 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 Proposed sales order table in MotherDuck (choose its name) in MotherDuck 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.
-
Use MotherDuck Proposed sales order table in MotherDuck (choose its name) and Shopify Orders for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 475 integrations listed for MotherDuck and Shopify.
Popular · 6 of 475
-
MotherDuck and SugarCRM -
MotherDuck and Veeva CRM -
MotherDuck and Vtiger CRM -
Shopify and Databricks -
Shopify and Amazon S3 -
Shopify and Amazon Redshift
No integrations match .
Next step
See your workflow in Stacksync
Walk through your MotherDuck and Shopify records, field mappings, and requirements with an integration engineer.
