Real-time
Real-time sync
Changes in Citus or E2 Shop System instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Citus to E2 Shop System integration — real-time data sync
Keep Citus and E2 Shop System 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 E2 Shop System
Give your engineers E2 Shop System's data in Citus: read it with normal queries, write back through the sync, and skip the ERP API entirely.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Citus, so Citus always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
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 Vendors, Parts, Routings / Operations, Purchase orders from E2 Shop System into Citus and keeps both sides consistent in real time. Whatever E2 Shop System 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 E2 Shop System with its validations respected.
Common use cases
- 01 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- 03 Land quote, job cost, and time-ticket data in a warehouse for margin analysis across jobs.
- 04 Keep purchase order data visible to planning or supplier-facing tools without direct ERP access.
Common sync patterns
Where E2 Shop System 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 E2 Shop System, keeping the ERP authoritative.
Read ERP records with a query
Records from E2 Shop System live in Citus as ordinary tables or collections, joinable with the rest of your data.
What you can sync between Citus and E2 Shop System
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 | E2 Shop System objects | How this pairing syncs | |
|---|---|---|---|
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Time tickets Labor collection records used for job costing. | Local tables is specific to Citus and Time tickets to E2 Shop System — 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. | Invoices Billing records synced to accounting for AR reporting. | Schemas is specific to Citus and Invoices to E2 Shop System — 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. | Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. | Views is specific to Citus and Quotes / Estimates to E2 Shop System — 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. | Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. | Sequences is specific to Citus and Jobs / Work orders to E2 Shop System — 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. | Customers Buyer records synced to CRM or accounting counterparts. | Distributed tables is specific to Citus and Customers to E2 Shop System — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Vendors Supplier records referenced on purchasing documents. | Reference tables is specific to Citus and Vendors to E2 Shop System — each maps to any object or custom field on the other side. |
How changes propagate between Citus and E2 Shop System
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 E2 Shop System 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.
DeliveryE2 Shop System does not accept inbound record writes, so this direction carries requests rather than records: E2 Shop System's output flows back as field updates on the originating Citus records.
E2 Shop System Citus Interval-based propagation
DetectionStacksync polls E2 Shop System for changes on an incremental schedule, reading only records changed since the previous pass. Polling database tables or scheduled exports.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- E2 Shop System: Not API-bound; constrained by on-premises database access windows.
What ships with Citus ⇄ E2 Shop System
Connect Citus and E2 Shop System for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–E2 Shop System connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or E2 Shop System 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 E2 Shop System record.
Observability
Monitoring
Track your Citus ⇄ E2 Shop System 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 E2 Shop System.
How the Citus and E2 Shop System 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
E2 Shop System
- Integration surface
- No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
- Authentication
- Database credentials or application-level export access on the on-premises installation
- Change detection
- Polling database tables or scheduled exports
- Capabilities
- read
- Rate limits
- Not API-bound; constrained by on-premises database access windows
How it works
How to connect Citus to E2 Shop System — 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 E2 Shop System 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
E2 Shop System
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and E2 Shop System 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 ⇄ E2 Shop SystemCustomers 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 E2 Shop SystemCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and E2 Shop System integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Citus and E2 Shop System — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and E2 Shop System connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–E2 Shop System integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and E2 Shop System. 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 E2 Shop System: Polling database tables or scheduled exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Citus side: Local tables, Schemas, Views, Sequences, plus custom fields where Citus exposes them. On the E2 Shop System side: Vendors, Parts, Routings / Operations, Purchase orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into Citus. Field mapping and monitoring work the same as for two-way pairs.
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 189 integrations available for Citus and E2 Shop System.
Popular · 3 of 189
No integrations match .
