Real-time
Two-way sync
Changes in Odoo or Pigment instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Odoo to Pigment integration — real-time, two-way sync
Keep Odoo and Pigment 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 Pigment
Keep Pigment 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 Metrics, Dimension lists, Tables, Scenarios in Pigment with Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead) 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
- Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- Sync headcount and compensation data from an HRIS into workforce planning models.
- Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
- Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.
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 Pigment serves a business unit and Odoo is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Pigment handles billing: invoices land in Odoo
Invoices and payment activity from the billing side post through to the enterprise system automatically.
What you can sync between Odoo and Pigment
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 | Pigment objects | |
|---|---|---|
| Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | |
| Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | Tables Row-based transactional data loaded into models from source systems | |
| CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | |
| Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | |
| Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | Users and permissions Access controls governing which model areas a sync can touch | |
| Employees (hr.employee) HR records read for directory and provisioning syncs. | Applications Planning models organized by domain such as finance, sales, or workforce |
What ships with Odoo ⇄ Pigment
Connect Odoo and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Odoo or Pigment 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 Pigment record.
Observability
Monitoring
Track your Odoo ⇄ Pigment 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 Pigment.
How the Odoo and Pigment 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
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Odoo to Pigment — 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 Pigment 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
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Odoo and Pigment 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 ⇄ PigmentCustomers 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 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Odoo and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Odoo and Pigment: authenticate both systems, choose the objects to sync (such as Odoo's Invoices (account.move) and Products (product.template / product.product)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Odoo and Pigment: One customer and vendor master; Subsidiary to headquarters; Where Pigment handles billing: invoices land in Odoo. Where both systems keep records of the same organizations, corrections made in either propagate to the other.
-
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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Odoo: Custom fields added through Odoo Studio or modules (prefixed x_) are exposed through the same API automatically. Stacksync's field mapping accounts for these differences between Odoo and Pigment 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 Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Odoo and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Odoo–Pigment integration in-house.
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 Pigment.
Popular · 8 of 386
-
Odoo ⇄ Workday -
Odoo ⇄ Anaplan -
Odoo ⇄ Chargebee -
Odoo ⇄ Hyperline -
Pigment ⇄ TikTok Shop -
Pigment ⇄ Unleashed Software -
Pigment ⇄ Visibility ERP -
Pigment ⇄ NetSuite
No integrations match .
