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 / ERP · Two-way sync platform
MotherDuck and Snapfulfil integration
Plan how MotherDuck and Snapfulfil should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
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
Proposed workflow
Sales order reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed sales order table in MotherDuck or Snapfulfil Sales orders needs a defined result in the other system.
Start with the proposed sales order table in MotherDuck and Snapfulfil Sales 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 ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| MotherDuck record | Snapfulfil record | Record matching | Field ownership |
|---|---|---|---|
| Proposed sales order tableProposed table; choose its name and schema.Reporting dataset | Sales ordersProposed record; confirm Stacksync object support. | 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 inventory or stock position tableProposed table; choose its name and schema.Reporting dataset | Inventory balancesProposed record; confirm Stacksync object support. | Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. | Choose the stock authority and distinguish available, reserved, and physical quantities. |
| Proposed shipment or fulfillment tableProposed table; choose its name and schema.Reporting dataset | ShipmentsProposed record; confirm Stacksync object support. | Retain shipment/fulfillment and line IDs, order reference, and carrier context. | The fulfillment owner controls shipped quantities and cancellation eligibility. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Snapfulfil
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | MotherDuck | Snapfulfil |
|---|---|---|
| Integration interface | SQL through DuckDB clients and drivers using a MotherDuck (md:) connection | REST-style web service API |
| Authentication | Access token created in MotherDuck | Confirm the credentials, API plan, and permissions required for Snapfulfil. |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Available for supported records | Confirm with Stacksync |
| Write access | Available for supported records | Confirm with Stacksync |
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.
Snapfulfil
- Integration interface
- REST-style web service API
- Authentication
- Confirm the credentials, API plan, and permissions required for Snapfulfil.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Snapfulfil account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Snapfulfil, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Snapfulfil and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare MotherDuck and Snapfulfil 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.
Snapfulfil setup checklist
- Identify the Snapfulfil account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Snapfulfil, including read/write support, authentication, and initial-load limits.
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 Snapfulfil 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
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Proposed sales order table in MotherDuck (choose its name) / Sales orders
Plan a sales order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- MotherDuck
- Your database schema
- Snapfulfil
- Object support to establish
- 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.
Reporting dataset
Proposed inventory or stock position table in MotherDuck (choose its name) / Inventory balances
Plan a inventory or stock position dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- MotherDuck
- Your database schema
- Snapfulfil
- Object support to establish
- Record identity
- Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
- Field ownership
- Choose the stock authority and distinguish available, reserved, and physical quantities.
Fields to include
- Product reference
- Location reference
- Quantity type
- Quantity
- As-of time
- Record dependencies
- Resolve product, unit, warehouse/location, and lot/serial references.
- Validation
- Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
- Recovery
- Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Reporting dataset
Proposed shipment or fulfillment table in MotherDuck (choose its name) / Shipments
Plan a shipment or fulfillment dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- MotherDuck
- Your database schema
- Snapfulfil
- Object support to establish
- Record identity
- Retain shipment/fulfillment and line IDs, order reference, and carrier context.
- Field ownership
- The fulfillment owner controls shipped quantities and cancellation eligibility.
Fields to include
- Source shipment ID
- Order/line references
- Carrier
- Tracking reference
- Fulfillment status
- Record dependencies
- Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
- Validation
- Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
- Recovery
- Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
Reporting dataset
Proposed purchase order table in MotherDuck (choose its name) / Purchase orders / ASNs
Plan a purchase order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- MotherDuck
- Your database schema
- Snapfulfil
- Object support to establish
- Record identity
- Retain purchase-order and line IDs together with the supplier and legal-entity context.
- Field ownership
- Keep procurement approval separate from receipt and payment states.
Fields to include
- Source purchase-order ID
- Supplier reference
- Line references
- Quantity
- Approval status
- Record dependencies
- Resolve supplier, product, business unit, and delivery-location references before lines.
- Validation
- Test a partially received purchase order and an amendment after approval.
- Recovery
- Reconcile receipts already recorded before resubmitting an amended order.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Proposed sales order table in MotherDuck (choose its name) / Sales orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- 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 Snapfulfil 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) / Sales orders, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when MotherDuck and Snapfulfil 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. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time MotherDuck / Snapfulfil 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
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed sales order table in MotherDuck (choose its name) or Sales orders record needs a defined result in the other system.
- Start with MotherDuck Proposed sales order table in MotherDuck (choose its name) and Snapfulfil Sales 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.
Inventory or stock position reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed inventory or stock position table in MotherDuck (choose its name) or Inventory balances record needs a defined result in the other system.
- Start with MotherDuck Proposed inventory or stock position table in MotherDuck (choose its name) and Snapfulfil Inventory balances. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve product, unit, warehouse/location, and lot/serial 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 the same SKU in two locations, a reservation, and an older snapshot arriving late.
If it fails: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Shipment or fulfillment reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed shipment or fulfillment table in MotherDuck (choose its name) or Shipments record needs a defined result in the other system.
- Start with MotherDuck Proposed shipment or fulfillment table in MotherDuck (choose its name) and Snapfulfil Shipments. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve order lines, delivery address, carrier, and any partial-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 split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
If it fails: Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
Reconcile Snapfulfil business records with MotherDuck
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Snapfulfil needs operational visibility through a selected destination dataset.
- Select Sales orders or Purchase orders / ASNs with the correct legal entity, period, and currency.
- Define a reporting relationship in MotherDuck; 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.
Proposed sales order table in MotherDuck (choose its name) / Sales 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 inventory or stock position table in MotherDuck (choose its name) / Inventory balances
Test case
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Expected result
The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.
Proposed shipment or fulfillment table in MotherDuck (choose its name) / Shipments
Test case
Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
Expected result
The expected shipment or fulfillment relationship is preserved with no duplicate action or unintended write.
Proposed purchase order table in MotherDuck (choose its name) / Purchase orders / ASNs
Test case
Test a partially received purchase order and an amendment after approval.
Expected result
The expected purchase order relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
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 Snapfulfil Sales 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 inventory or stock position change
Investigate
Inspect MotherDuck Proposed inventory or stock position table in MotherDuck (choose its name) and Snapfulfil Inventory balances, their IDs, and the destination error.
Next action
Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Rejected or repeated shipment or fulfillment change
Investigate
Inspect MotherDuck Proposed shipment or fulfillment table in MotherDuck (choose its name) and Snapfulfil Shipments, their IDs, and the destination error.
Next action
Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
A record type or update is unavailable
Investigate
Check the MotherDuck and Snapfulfil 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 Snapfulfil
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
MotherDuck Snapfulfil Direction requires confirmation
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesConfirm that Stacksync can create or update the records you need in Snapfulfil.
Snapfulfil MotherDuck Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in MotherDuck.
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.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
MotherDuck and Snapfulfil integration FAQ
-
Explore a MotherDuck and Snapfulfil integration with a Stacksync engineer. Stacksync support for Snapfulfil is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
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. Identify the Snapfulfil account, edition, environment, and business objects the integration must access. 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 Sales orders in Snapfulfil. 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.
-
Choose a method around one example record and the update your business needs. Use Proposed sales order table in MotherDuck (choose its name) / Sales orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 218 integrations listed for MotherDuck and Snapfulfil.
Popular · 3 of 218
No integrations match .
Next step
Plan your integration with an engineer
Walk through your MotherDuck and Snapfulfil records, field mappings, and requirements with an integration engineer.
