Two-way sync
Changes in Deposco or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Keep Deposco and DuckDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Receipts, Warehouses / Locations, Customers, Items / SKUs from Deposco into DuckDB and keeps both sides consistent in real time. Whatever Deposco 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 Deposco with its validations respected.
Choose exactly which tables and fields may flow from DuckDB back into Deposco, keeping the ERP authoritative.
Records from Deposco live in DuckDB as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Deposco interface, limits, and retries.
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.
| Deposco objects | DuckDB objects | |
|---|---|---|
| Customers Ship-to parties referenced on orders and shipments. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | |
| Items / SKUs Product master records that fulfillment operations pick and ship against. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | |
| Inventory On-hand and available quantities by warehouse and location, read frequently by storefront syncs. | Schemas Namespaces within a database used to organize tables in sync outputs. | |
| Sales orders Orders flowing in from ERP or e-commerce systems for fulfillment. | Tables Columnar tables created via SQL; the destination for materialized sync data. | |
| Shipments Outbound shipment and tracking records synced back to order-origin systems. | Views SQL views used to shape or filter data for downstream consumers. | |
| Purchase orders / ASNs Inbound expectations used to plan receiving. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Deposco–DuckDB connection.
Changes in Deposco or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Deposco or DuckDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Deposco or DuckDB record.
Track your Deposco ⇄ DuckDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Deposco and DuckDB.
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.
Authenticate Deposco and DuckDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Deposco and DuckDB 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Deposco and DuckDB: authenticate both systems, choose the objects to sync (such as Deposco's Customers and Items / SKUs), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Deposco: Polling on order and inventory endpoints, subject to the platform's integration patterns. On DuckDB: Polling or full re-reads; no change feed or transaction log API. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the DuckDB side: External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas, plus custom fields where DuckDB exposes them. On the Deposco side: Receipts, Warehouses / Locations, Customers, Items / SKUs. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Deposco and DuckDB: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from DuckDB back into Deposco, keeping the ERP authoritative.
Deposco: REST API plus file-based interfaces (EDI and flat file) common to WMS integrations. Authentication: API credentials issued per integration (API key or basic authentication). DuckDB: 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). Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Deposco and DuckDB.