Real-time
Two-way sync
Changes in Cin7 or Citus instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Cin7 to Citus integration — real-time, two-way sync
Keep Cin7 and Citus 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 Cin7 and Citus
Give your engineers Cin7'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 Inventory levels, Sales orders, Purchase orders, Contacts from Cin7 into Citus and keeps both sides consistent in real time. Whatever Cin7 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 Cin7 with its validations respected.
Common use cases
- Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
- Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.
React to ERP changes
Updates in Cin7 arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Where Cin7 is the HR system of record: people data for internal systems
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from Citus back into Cin7, keeping the ERP authoritative.
What you can sync between Cin7 and Citus
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.
| Cin7 objects | Citus objects | |
|---|---|---|
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Sequences Key generators that matter when external writes must not collide with application inserts. | |
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | |
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Views Curated projections over distributed data, often used as read-only sync sources. |
What ships with Cin7 ⇄ Citus
Connect Cin7 and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Citus 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 Cin7 or Citus record.
Observability
Monitoring
Track your Cin7 ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Cin7 and Citus.
How the Cin7 and Citus connectors work
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
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
How it works
How to connect Cin7 to Citus — 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 Cin7 and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Cin7
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 and Citus 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 · Cin7 ⇄ CitusCustomers 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.
Cin7 CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Citus: authenticate both systems, choose the objects to sync (such as Cin7's Stock adjustments and transfers and Credit notes / returns), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Cin7 and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Cin7: Polling on modified-date filters; webhook support exists on some editions for order and stock events. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Citus side: Reference tables, Local tables, Schemas, Views, plus custom fields where Citus exposes them. On the Cin7 side: Inventory levels, Sales orders, Purchase orders, Contacts. 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 Cin7 and Citus: React to ERP changes; Where Cin7 is the HR system of record: people data for internal systems; Controlled write-back. Updates in Cin7 arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Cin7 and Citus.
Popular · 8 of 386
-
Cin7 ⇄ DuckDB -
Cin7 ⇄ Elasticsearch -
Cin7 ⇄ Google Cloud Spanner - Cin7 ⇄ Google Cloud SQL
-
Citus ⇄ Infor M3 - Citus ⇄ Infor WMS
-
Citus ⇄ IQMS (DELMIAworks) -
Citus ⇄ JobBOSS²
No integrations match .
