Skip to content
Database ⇄ ERP

DuckDB to Snapfulfil integration — real-time, two-way sync

Keep DuckDB and Snapfulfil in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

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
Why teams connect DuckDB and Snapfulfil

Give your engineers Snapfulfil's data in DuckDB: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Items (SKUs), Inventory balances, Shipments, Warehouse locations from Snapfulfil into DuckDB and keeps both sides consistent in real time. Whatever Snapfulfil is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in DuckDB sync back into Snapfulfil with its validations respected.

Common use cases

  • 01 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • 02 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 03 Mirror fulfillment activity into a database for operational reporting outside the WMS
  • 04 Push sales orders from an ERP or e-commerce platform into Snapfulfil for fulfillment without file drops

Common sync patterns

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Snapfulfil interface, limits, and retries.

React to ERP changes

Updates in Snapfulfil arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.

Where Snapfulfil is the HR system of record: people data for internal systems

Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.

What you can sync between DuckDB and Snapfulfil

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

DuckDB objects Snapfulfil objects How this pairing syncs
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Sales orders Orders pushed into the WMS for picking, packing, and dispatch. Database files is specific to DuckDB and Sales orders to Snapfulfil — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. Purchase orders / ASNs Inbound expectations that drive receiving and putaway. Schemas is specific to DuckDB and Purchase orders / ASNs to Snapfulfil — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. Items (SKUs) The item master, usually sourced from the ERP or storefront. Tables is specific to DuckDB and Items (SKUs) to Snapfulfil — each maps to any object or custom field on the other side.
Views SQL views used to shape or filter data for downstream consumers. Inventory balances On-hand and allocated stock, read back to keep the ERP and selling channels accurate. Views is specific to DuckDB and Inventory balances to Snapfulfil — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. Shipments Dispatch confirmations with carrier and tracking details returned to the order source. External files (Parquet/CSV/JSON) is specific to DuckDB and Shipments to Snapfulfil — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Warehouse locations Bin and zone structure referenced by stock and movement records. Attached databases is specific to DuckDB and Warehouse locations to Snapfulfil — each maps to any object or custom field on the other side.

How changes propagate between DuckDB and Snapfulfil

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

DuckDB Snapfulfil Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

DeliveryEach detected change is written to Snapfulfil through its API, with automatic retries and rate-limit backoff.

Snapfulfil DuckDB Interval-based propagation

DetectionStacksync polls Snapfulfil for changes on an incremental schedule, reading only records changed since the previous pass. Polling, subject to the platform's API rate limits.

DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • Snapfulfil: Specific quotas are not publicly standardized; treat throughput as instance-dependent.
What ships with DuckDB ⇄ Snapfulfil

Connect DuckDB and Snapfulfil for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Snapfulfil connection.

Real-time

Two-way sync

Changes in DuckDB or Snapfulfil instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DuckDB or Snapfulfil data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single DuckDB or Snapfulfil record.

Observability

Monitoring

Track your DuckDB ⇄ Snapfulfil sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DuckDB and Snapfulfil.

How the DuckDB and Snapfulfil connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

Snapfulfil

Integration surface
REST-style web service API
Authentication
API credentials issued for the warehouse instance
Change detection
Polling, subject to the platform's API rate limits
Capabilities
read · write
Rate limits
Specific quotas are not publicly standardized; treat throughput as instance-dependent
How it works

How to connect DuckDB to Snapfulfil — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate DuckDB and Snapfulfil with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    DuckDB connected
    Snapfulfil connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB and Snapfulfil objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · DuckDB ⇄ Snapfulfil
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    DuckDB Snapfulfil
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB and Snapfulfil integration FAQ

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 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 219 integrations available for DuckDB and Snapfulfil.

Popular · 5 of 219
All DuckDB integrations All Snapfulfil integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own