Real-time
Two-way sync
Changes in Odoo or Recurly instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Odoo to Recurly integration — real-time, two-way sync
Keep Odoo and Recurly 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 Recurly
Keep Recurly and Odoo 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 Transactions, Line Items, Coupons and Redemptions, Billing Info in Recurly with Inventory Transfers (stock.picking), Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner) in Odoo 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
- 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
- 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 03 Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
- 04 Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.
Common sync patterns
Subsidiary to headquarters
Where Recurly serves a business unit and Odoo is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Recurly handles billing: invoices land in Odoo
Invoices and payment activity from the billing side post through to the enterprise system automatically.
Migration without a hard cutover
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
What you can sync between Odoo and Recurly
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 | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Projects and Tasks (project.project / project.task) is specific to Odoo and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Contacts (res.partner) is specific to Odoo and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Sales Orders (sale.order) is specific to Odoo and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). | Invoices (account.move) is specific to Odoo and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Products (product.template / product.product) is specific to Odoo and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. | CRM Leads (crm.lead) is specific to Odoo and Accounts to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Odoo and Recurly
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.
Odoo Recurly Sub-second propagation
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Odoo Sub-second propagation
DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.
DeliveryEach detected change is written to Odoo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
- Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Odoo ⇄ Recurly
Connect Odoo and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Odoo or Recurly 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 Recurly record.
Observability
Monitoring
Track your Odoo ⇄ Recurly 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 Recurly.
How the Odoo and Recurly 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
Recurly
- Integration surface
- REST API (V3, date-versioned; legacy V2 XML API also exists)
- Authentication
- API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
- Change detection
- Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
- Capabilities
- read · write · webhooks
- Rate limits
- Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works
How to connect Odoo to Recurly — 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 Recurly 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
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Odoo and Recurly 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 ⇄ RecurlyCustomers 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 RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Odoo and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Odoo and Recurly: authenticate both systems, choose the objects to sync (such as Odoo's Projects and Tasks (project.project / project.task) and Contacts (res.partner)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. On Recurly: Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Transactions, Line Items, Coupons and Redemptions, Billing Info, plus custom fields where Recurly exposes them. On the Odoo side: Inventory Transfers (stock.picking), Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner). 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 Odoo and Recurly: Subsidiary to headquarters; Where Recurly handles billing: invoices land in Odoo; Migration without a hard cutover. Where Recurly serves a business unit and Odoo is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
-
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. Recurly: REST API (V3, date-versioned; legacy V2 XML API also exists). Authentication: API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys. Stacksync manages authentication, retries, and rate limits on both sides.
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.
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 515 integrations available for Odoo and Recurly.
Popular · 6 of 515
No integrations match .
