Odoo and Anaplan integration

What moves between them

The flow moves from Odoo into Anaplan. Journal entries (account.move), purchase orders (purchase.order), and line-item GL postings flow from Odoo into Anaplan models, mapped to Anaplan lists and modules based on cost center, GL account, or purchase category. Employee data (hr.employee) and payroll cost movements can also be synced to keep workforce planning models current. Odoo reads all records by polling on a configurable schedule; Anaplan receives data through its import actions, which transform CSV or JSON into model line items.

How ml-connector handles it

ml-connector stores Odoo API credentials (API key + username) and Anaplan credentials (certificate or OAuth2 token) encrypted. It polls Odoo using search_read with a write_date filter on a schedule you set (daily, weekly, or tied to your close calendar), retrieves records as JSON or XML-RPC result sets, transforms them to Anaplan's list and line-item schema, and uploads the data through an Anaplan import action using a CSV or JSON payload. Anaplan enforces a 600 request-per-minute tenant-wide rate limit; ml-connector backs off and retries on HTTP 429. Because Odoo's XML-RPC and JSON-2 APIs are deprecated in favor of Odoo 22 (2028), ml-connector prefers JSON-2 for Odoo 19+ but falls back to XML-RPC for earlier versions. API calls respect Odoo's record access rules and the integrating user's field-level permissions.

A real-world example

A mid-sized wholesale distributor runs Odoo for purchasing, inventory, and GL. They use Anaplan for sales forecasting, supply chain planning, and expense budgeting across five distribution centers. Before the integration, the planning team exported purchase order data and GL entries from Odoo monthly and manually built Anaplan model line items for each center, then spent days tracking differences when Odoo inventory or GL postings changed. With Odoo and Anaplan connected, each purchasing cycle's new orders flow into Anaplan automatically, allocated to the correct center and cost code. GL monthly accruals post directly into the planning model. The supply chain plan now reflects real Odoo purchases, and headcount and labor cost stay aligned without re-keying.

What you can do

• •Sync Odoo GL journal entries and line-item detail into Anaplan models, mapped to cost center and GL account.
• •Move Odoo purchase orders and supplier invoices into Anaplan supply chain planning models with order date and GL account mappings.
• •Transfer Odoo employee records and labor cost allocations into Anaplan workforce planning modules to keep headcount and expense budgets current.
• •Authenticate Odoo with API key and username login, and Anaplan with certificate-based or OAuth2 credentials, translating between auth schemes transparently.
• •Poll Odoo on a configurable schedule with timestamp-based filters, back off on Anaplan rate limits (600 requests per minute), and audit every record transformation and upload.

Questions

What Odoo records can sync into Anaplan?

Journal entries (account.move, account.move.line), purchase orders and invoices (purchase.order), GL accounts (account.account), cost centers (account.analytic.account), products, and employee records (hr.employee) can all flow into Anaplan models. Each record is mapped to Anaplan lists and line items based on GL account, cost center, supplier, or employee.

How does ml-connector handle Odoo's API key authentication and Anaplan's certificate or OAuth2?

ml-connector stores both credential sets encrypted. For Odoo, it uses the API key as a Bearer token (JSON-2) or includes it in the XML-RPC call bundle (legacy). For Anaplan, it authenticates with the certificate pair or refreshes the OAuth2 token before each request, handling 35-minute expiry windows and retrying on 401 responses.

What happens when Anaplan's rate limit is hit?

Anaplan returns HTTP 429 when the tenant-wide 600 request-per-minute cap is exceeded. ml-connector detects 429, backs off exponentially, and retries the request. If retries are exhausted, the record is queued for replay, and an alert is raised so the integration owner can monitor impact on the planning cycle.