Real-time
Two-way sync
Changes in Citus or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Citus to Linnworks integration — real-time, two-way sync
Keep Citus and Linnworks 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 Citus and Linnworks
Give your engineers Linnworks's data in Citus: 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 Open Orders, Processed Orders, Stock Items, Stock Levels from Linnworks into Citus and keeps both sides consistent in real time. Whatever Linnworks 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 Linnworks with its validations respected.
Common use cases
- 01 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 02 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 03 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
- 04 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
Common sync patterns
Read ERP records with a query
Records from Linnworks live in Citus as ordinary tables or collections, joinable with the rest of your data.
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Linnworks interface, limits, and retries.
React to ERP changes
Updates in Linnworks arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
What you can sync between Citus and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Reference tables is specific to Citus and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Local tables is specific to Citus and Stock Levels to Linnworks — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Schemas is specific to Citus and Locations to Linnworks — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Views is specific to Citus and Purchase Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Suppliers Vendor records keep procurement data consistent across tools. | Sequences is specific to Citus and Suppliers to Linnworks — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Distributed tables is specific to Citus and Channel Listings to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Linnworks
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.
Citus Linnworks Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Citus Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Citus ⇄ Linnworks
Connect Citus and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Linnworks 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 Citus or Linnworks record.
Observability
Monitoring
Track your Citus ⇄ Linnworks sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Linnworks.
How the Citus and Linnworks connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Citus to Linnworks — 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.
- 01
Connect your apps
Authenticate Citus and Linnworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Linnworks 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.
objects · Citus ⇄ LinnworksCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Linnworks: authenticate both systems, choose the objects to sync (such as Citus's Reference tables and Local tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Citus and Linnworks: Read ERP records with a query; Internal tools and automations without API code; React to ERP changes. Records from Linnworks live in Citus as ordinary tables or collections, joinable with the rest of your data.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
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. Linnworks: Orders are modeled in two populations, open orders and processed orders, and syncs typically treat processing as the state transition that moves a record between them. Stacksync's field mapping accounts for these differences between Citus and Linnworks 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 Linnworks records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Linnworks connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Linnworks integration in-house.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 430 integrations available for Citus and Linnworks.
Popular · 6 of 430
-
Citus ⇄ Microsoft Dynamics GP - Citus ⇄ Microsoft Dynamics NAV
-
Linnworks ⇄ Elasticsearch -
Linnworks ⇄ Google Cloud Spanner - Linnworks ⇄ Google Cloud SQL
-
Linnworks ⇄ IBM AS/400
No integrations match .
