Two-way sync
Changes in DuckDB or Extensiv (3PL Central) instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Extensiv (3PL Central) 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 Customers, Items, Inventory, Orders from Extensiv (3PL Central) into DuckDB and keeps both sides consistent in real time. Whatever Extensiv (3PL Central) 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 Extensiv (3PL Central) with its validations respected.
Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from DuckDB back into Extensiv (3PL Central), keeping the ERP authoritative.
Records from Extensiv (3PL Central) live in DuckDB as ordinary tables or collections, joinable with the rest of your data.
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 | Extensiv (3PL Central) objects | |
|---|---|---|
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Inventory On-hand and available quantities by warehouse, mirrored out to drive channel availability. | |
| Views SQL views used to shape or filter data for downstream consumers. | Orders Outbound fulfillment orders pushed in from commerce or ERP systems. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Receivers Inbound receiving records (receipts/ASNs) that confirm stock arrival back to purchasing systems. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Shipments Carrier and tracking details synced back once orders ship. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Warehouses Facility records that partition inventory and order routing. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Inventory adjustments Manual stock corrections that reconciliation syncs need to capture. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Extensiv (3PL Central) connection.
Changes in DuckDB or Extensiv (3PL Central) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Extensiv (3PL Central) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Extensiv (3PL Central) record.
Track your DuckDB ⇄ Extensiv (3PL Central) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Extensiv (3PL Central).
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 DuckDB and Extensiv (3PL Central) 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 DuckDB and Extensiv (3PL Central) 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 DuckDB and Extensiv (3PL Central): authenticate both systems, choose the objects to sync (such as DuckDB's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 DuckDB and Extensiv (3PL Central): Where Extensiv (3PL Central) is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
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). Extensiv (3PL Central): REST API. Authentication: Short-lived access tokens obtained from integration client credentials (client ID and secret). Stacksync manages authentication, retries, and rate limits on both sides.
DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Extensiv (3PL Central): Order lifecycle status determines when fulfillment and tracking data exists to sync back to the merchant. Stacksync's field mapping accounts for these differences between DuckDB and Extensiv (3PL Central) without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DuckDB and Extensiv (3PL Central) records are not retained after a sync operation.
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 DuckDB and Extensiv (3PL Central).