Two-way sync
Changes in Cin7 or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Cin7 and Supabase 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 Sales orders, Purchase orders, Contacts, Branches / locations from Cin7 into Supabase 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 Supabase sync back into Cin7 with its validations respected.
Records from Cin7 live in Supabase as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Cin7 interface, limits, and retries.
Updates in Cin7 arrive as row changes in Supabase, so jobs and triggers can respond as the business record changes.
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 | Supabase objects | |
|---|---|---|
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Tables Standard Postgres tables; the primary two-way sync target. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Supabase connection.
Changes in Cin7 or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Cin7 or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Cin7 or Supabase record.
Track your Cin7 ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Cin7 and Supabase.
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 Cin7 and Supabase 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 Cin7 and Supabase 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 Cin7 and Supabase: authenticate both systems, choose the objects to sync (such as Cin7's Stock adjustments and transfers and Credit notes / returns), 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 Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Supabase side: Storage Object Metadata, Tables, Views, Schemas, plus custom fields where Supabase exposes them. On the Cin7 side: Sales orders, Purchase orders, Contacts, Branches / locations. 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 Supabase: Read ERP records with a query; Internal tools and automations without API code; React to ERP changes. Records from Cin7 live in Supabase as ordinary tables or collections, joinable with the rest of your data.
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). Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. 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 Cin7 and Supabase.