Skip to content
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

  • Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
  • Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock

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
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.
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.
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.
Views Curated projections over distributed data, often used as read-only sync sources. Purchase Orders Replenishment POs sync with suppliers and accounting systems.
Sequences Key generators that matter when external writes must not collide with application inserts. Suppliers Vendor records keep procurement data consistent across tools.
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.
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.

Real-time

Two-way sync

Changes in Citus or Linnworks instantly reflect in both systems. No stale data, no manual imports.

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.

  1. 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Linnworks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ Linnworks
    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
    Citus Linnworks
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Linnworks integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Citus and Linnworks.

Popular · 8 of 386
All Citus integrations All Linnworks 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