Skip to content
Database ⇄ ERP

Citus to QAD ERP integration — real-time, two-way sync

Keep Citus and QAD ERP 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 QAD ERP

Give your engineers QAD ERP'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 Items, Customers, Suppliers, Sales orders from QAD ERP into Citus and keeps both sides consistent in real time. Whatever QAD ERP 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 QAD ERP with its validations respected.

Common use cases

  • 01 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 02 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • 03 Push EDI orders from trading partners into QAD as sales orders.
  • 04 Keep supplier and purchase-order records aligned with procurement or AP automation tools.

Common sync patterns

Controlled write-back

Choose exactly which tables and fields may flow from Citus back into QAD ERP, keeping the ERP authoritative.

Read ERP records with a query

Records from QAD ERP 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 QAD ERP interface, limits, and retries.

What you can sync between Citus and QAD ERP

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 QAD ERP objects How this pairing syncs
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Suppliers Vendor master data aligned with procurement and AP automation tools Local tables is specific to Citus and Suppliers to QAD ERP — 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. Sales orders Demand records written in from EDI or e-commerce and read out for status Schemas is specific to Citus and Sales orders to QAD ERP — 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 Procurement documents mirrored to planning and finance systems Views is specific to Citus and Purchase orders to QAD ERP — 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. Work orders Production records replicated for scheduling and shop-floor analytics Sequences is specific to Citus and Work orders to QAD ERP — 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. Inventory balances Stock levels by site and location, synced for multi-plant visibility Distributed tables is specific to Citus and Inventory balances to QAD ERP — 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. General ledger transactions Financial postings exported for consolidated reporting Reference tables is specific to Citus and General ledger transactions to QAD ERP — each maps to any object or custom field on the other side.

How changes propagate between Citus and QAD ERP

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 QAD ERP 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 QAD ERP through its API, with automatic retries and rate-limit backoff.

QAD ERP Citus Interval-based propagation

DetectionStacksync polls QAD ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the API surface.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • QAD ERP: Subject to instance capacity and the platform's API limits.
What ships with Citus ⇄ QAD ERP

Connect Citus and QAD ERP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–QAD ERP connection.

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or QAD ERP 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 QAD ERP record.

Observability

Monitoring

Track your Citus ⇄ QAD ERP 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 QAD ERP.

How the Citus and QAD ERP 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

QAD ERP

Integration surface
REST APIs plus the QXtend XML integration framework
Authentication
instance credentials; specifics depend on the deployment and version
Change detection
polling on the API surface; document-based event exchange available through QXtend in supported configurations
Capabilities
read · write
Rate limits
subject to instance capacity and the platform's API limits
How it works

How to connect Citus to QAD ERP — 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 QAD ERP 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
    QAD ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and QAD ERP 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 ⇄ QAD ERP
    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 QAD ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and QAD ERP integration FAQ

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.

Learn more about security
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:

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 431 integrations available for Citus and QAD ERP.

Popular · 7 of 431
All Citus integrations All QAD ERP 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