Two-way sync
Changes in Azure Cosmos DB or Cin7 instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Cosmos DB and Cin7 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Credit notes / returns, Products, Inventory levels, Sales orders from Cin7 into Azure Cosmos DB 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 Azure Cosmos DB sync back into Cin7 with its validations respected.
Worker and org records stay current in Azure Cosmos DB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Azure Cosmos DB back into Cin7, keeping the ERP authoritative.
Records from Cin7 live in Azure Cosmos DB as ordinary tables or collections, joinable with the rest of your data.
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.
| Azure Cosmos DB objects | Cin7 objects | |
|---|---|---|
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Credit notes / returns Return documents synced so finance and support see the same refund state. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Inventory levels Stock on hand by branch or location, published outward for availability. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Purchase orders Supplier orders synced with procurement and accounting workflows. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Cin7 connection.
Changes in Azure Cosmos DB or Cin7 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Cosmos DB or Cin7 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Cosmos DB or Cin7 record.
Track your Azure Cosmos DB ⇄ Cin7 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Cin7.
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.
Authenticate Azure Cosmos DB and Cin7 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Azure Cosmos DB and Cin7 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and Cin7: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Partition keys and Change feed entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. On Cin7: Polling on modified-date filters; webhook support exists on some editions for order and stock events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Azure Cosmos DB side: Databases, Containers, Items (JSON documents), Partition keys, plus custom fields where Azure Cosmos DB exposes them. On the Cin7 side: Credit notes / returns, Products, Inventory levels, Sales orders. 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 Azure Cosmos DB and Cin7: Where Cin7 is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in Azure Cosmos DB for provisioning, access, and reporting systems that read from the database.
Azure Cosmos DB: REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces. Authentication: Account keys, resource tokens, or Microsoft Entra ID role-based access. Cin7: 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). Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Azure Cosmos DB and Cin7.