Real-time
Two-way sync
Changes in Odoo or Supabase instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Odoo to Supabase integration — real-time, two-way sync
Keep Odoo 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.
- 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 Odoo and Supabase
Give your engineers Odoo's data in Supabase: 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 (res.partner), Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product) from Odoo into Supabase and keeps both sides consistent in real time. Whatever Odoo 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 Odoo with its validations respected.
Common use cases
- Consolidate Supabase project data into a warehouse for analytics while keeping the app database as the system of record
- Sync application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
- Sync employee records from an HR system of record into Odoo for expense and timesheet workflows.
- Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
React to ERP changes
Updates in Odoo arrive as row changes in Supabase, so jobs and triggers can respond as the business record changes.
Where Odoo is the HR system of record: people data for internal systems
Worker and org records stay current in Supabase for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from Supabase back into Odoo, keeping the ERP authoritative.
What you can sync between Odoo and Supabase
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.
| Odoo objects | Supabase objects | |
|---|---|---|
| CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | Views Read-side projections exposed to outbound syncs. | |
| Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Schemas Namespaces (public and custom) that scope sync access. | |
| Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Employees (hr.employee) HR records read for directory and provisioning syncs. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Projects and Tasks (project.project / project.task) Work items synced with external project tools. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Database Functions Postgres functions that can transform or validate synced rows. |
What ships with Odoo ⇄ Supabase
Connect Odoo and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Odoo or Supabase 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 Odoo or Supabase record.
Observability
Monitoring
Track your Odoo ⇄ Supabase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Odoo and Supabase.
How the Odoo and Supabase connectors work
Odoo
- Integration surface
- XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
- Authentication
- Database user credentials or per-user API keys
- Change detection
- Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
- Capabilities
- read · write · webhooks
- Rate limits
- Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
Supabase
- Integration surface
- 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
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Odoo to Supabase — 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 Odoo 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.
Odoo
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Odoo 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.
objects · Odoo ⇄ SupabaseCustomers 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.
Odoo SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Odoo and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Odoo and Supabase: authenticate both systems, choose the objects to sync (such as Odoo's CRM Leads (crm.lead) and Purchase Orders (purchase.order)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Odoo and Supabase: React to ERP changes; Where Odoo is the HR system of record: people data for internal systems; Controlled write-back. Updates in Odoo arrive as row changes in Supabase, so jobs and triggers can respond as the business record changes.
-
Odoo: XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink). Authentication: Database user credentials or per-user API keys. 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.
-
Supabase: Supabase Realtime is built on the Postgres write-ahead log, streaming row changes over websockets. Odoo: The external API exposes the ORM generically: any model (res.partner, sale.order, account.move) is accessed with the same execute_kw call pattern rather than per-object endpoints. Stacksync's field mapping accounts for these differences between Odoo and Supabase without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Odoo and Supabase records are not retained after a sync operation.
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 Odoo and Supabase.
Popular · 8 of 386
-
Odoo ⇄ SingleStore -
Odoo ⇄ Amazon Aurora -
Odoo ⇄ Amazon Lightsail -
Odoo ⇄ Apache Cassandra -
Supabase ⇄ Microsoft Dynamics GP - Supabase ⇄ Microsoft Dynamics NAV
-
Supabase ⇄ Plex ERP -
Supabase ⇄ QAD ERP
No integrations match .
