Skip to content
ERP ⇄ Database

Cin7 to TiDB integration — real-time, two-way sync

Keep Cin7 and TiDB 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 TiDB

Give your engineers Cin7's data in TiDB: 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 Contacts, Branches / locations, Stock adjustments and transfers, Credit notes / returns from Cin7 into TiDB 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 TiDB sync back into Cin7 with its validations respected.

Common use cases

  • 01 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • 02 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • 03 Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
  • 04 Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.

Common sync patterns

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Cin7 interface, limits, and retries.

React to ERP changes

Updates in Cin7 arrive as row changes in TiDB, 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 TiDB for provisioning, access, and reporting systems that read from the database.

What you can sync between Cin7 and TiDB

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 TiDB objects How this pairing syncs
Branches / locations Warehouse entities that scope every stock movement and order allocation. Databases MySQL-style schemas addressed by any MySQL-compatible client. Branches / locations is specific to Cin7 and Databases to TiDB — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Stock adjustments and transfers is specific to Cin7 and Tables to TiDB — each maps to any object or custom field on the other side.
Credit notes / returns Return documents synced so finance and support see the same refund state. Views Logical views for shaping reads before syncing outward. Credit notes / returns is specific to Cin7 and Views to TiDB — each maps to any object or custom field on the other side.
Products SKU records with options and pricing, synced with storefront and marketplace catalogs. Columns MySQL-compatible types mapped to fields in the paired system. Products is specific to Cin7 and Columns to TiDB — each maps to any object or custom field on the other side.
Inventory levels Stock on hand by branch or location, published outward for availability. Indexes Secondary indexes that keep incremental sync queries efficient. Inventory levels is specific to Cin7 and Indexes to TiDB — each maps to any object or custom field on the other side.
Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. Sequences Server-side ID generation relevant when external systems write rows. Sales orders is specific to Cin7 and Sequences to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Cin7 and TiDB

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.

Cin7 TiDB Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

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

TiDB Cin7 Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

DeliveryEach detected change is written to Cin7 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Cin7 ⇄ TiDB

Connect Cin7 and TiDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–TiDB connection.

Real-time

Two-way sync

Changes in Cin7 or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Cin7 or TiDB 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 TiDB record.

Observability

Monitoring

Track your Cin7 ⇄ TiDB 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 TiDB.

How the Cin7 and TiDB 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

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

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

    Choose tables

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

Cin7 and TiDB 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 423 integrations available for Cin7 and TiDB.

Popular · 7 of 423
All Cin7 integrations All TiDB 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