Real-time
Two-way sync
Changes in Cin7 or Rillet instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Cin7 to Rillet integration — real-time, two-way sync
Keep Cin7 and Rillet 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 Rillet
Keep Rillet and Cin7 agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Reimbursement, Custom Field, Account, Customer in Rillet with Branches / locations, Stock adjustments and transfers, Credit notes / returns, Products in Cin7 in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- Sync AR and collection status back to customer success tools ahead of renewals.
- Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- Consolidate stock movements from multiple branches into one reporting database.
- Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
Migration without a hard cutover
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
Subsidiary to headquarters
Where Rillet serves a business unit and Cin7 is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
What you can sync between Cin7 and Rillet
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 | Rillet objects | |
|---|---|---|
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Charge Synced with incremental and full sync per the Stacksync docs. | |
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Account Synced with incremental and full sync per the Stacksync docs. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Customer Synced with incremental and full sync per the Stacksync docs. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Vendor Synced with incremental and full sync per the Stacksync docs. |
What ships with Cin7 ⇄ Rillet
Connect Cin7 and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Rillet 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 Rillet record.
Observability
Monitoring
Track your Cin7 ⇄ Rillet 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 Rillet.
How the Cin7 and Rillet 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
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Subject to the platform's API rate limits.
How it works
How to connect Cin7 to Rillet — 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 Rillet 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
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 and Rillet 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 ⇄ RilletCustomers 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 RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Rillet: authenticate both systems, choose the objects to sync (such as Cin7's Credit notes / returns and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Cin7: Polling on modified-date filters; webhook support exists on some editions for order and stock events. On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rillet side: Reimbursement, Custom Field, Account, Customer, plus custom fields where Rillet exposes them. On the Cin7 side: Branches / locations, Stock adjustments and transfers, Credit notes / returns, Products. 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 Rillet: Migration without a hard cutover; One customer and vendor master; Subsidiary to headquarters. When one system is replacing the other, run both in parallel with records matching until the switch is complete.
-
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). Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
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 Rillet.
Popular · 8 of 386
-
Cin7 ⇄ Anaplan -
Cin7 ⇄ Chargebee -
Cin7 ⇄ Hyperline -
Cin7 ⇄ Pigment -
Rillet ⇄ Sage X3 -
Rillet ⇄ SAP -
Rillet ⇄ Snapfulfil -
Rillet ⇄ Syspro
No integrations match .
