Two-way sync
Changes in Citus or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Körber WMS 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 Shipments, Locations, Tasks, Returns from Körber WMS into Citus and keeps both sides consistent in real time. Whatever Körber WMS is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Citus sync back into Körber WMS with its validations respected.
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Citus back into Körber WMS, keeping the ERP authoritative.
Records from Körber WMS live in Citus 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.
| Citus objects | Körber WMS objects | |
|---|---|---|
| Sequences Key generators that matter when external writes must not collide with application inserts. | Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Shipments Ship confirmations and tracking references return to the order source system. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Locations Bin and zone definitions scope inventory data during mapping. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Tasks Warehouse task data supports labor and throughput reporting. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Items Item definitions keep the WMS aligned with the ERP item master. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Körber WMS connection.
Changes in Citus or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Körber WMS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or Körber WMS record.
Track your Citus ⇄ Körber WMS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Körber WMS.
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 Citus and Körber WMS 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 Citus and Körber WMS 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 Citus and Körber WMS: authenticate both systems, choose the objects to sync (such as Citus's Sequences and Distributed tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Citus: Distributed tables are sharded by a declared distribution column, and reference tables are fully replicated to all nodes; the table type changes how writes and joins behave. Körber WMS: Körber's warehouse management portfolio grew in part from its acquisition of HighJump, and the product line is positioned as modular software for complex, multi-site warehouse operations. Stacksync's field mapping accounts for these differences between Citus and Körber WMS 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 Citus and Körber WMS records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Körber WMS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Körber WMS integration in-house.
Yes — Stacksync ships production-grade connectors for both Citus and Körber WMS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On Körber WMS: Polling or message/file-based export from the WMS host interface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 Citus and Körber WMS.