Contact profiles
Select the customer identifiers and attributes actually required.
Marketing & email · Odoo integration
Give marketing useful customer context from Odoo. Radorfa maps your process, configures the data exchange and tests it with your team.
First, we review your processes and systems. Then you receive a proposal with scope and costs.
Start with a feasibility check
We check API access, version and subscription before confirming the integration route.
ERP & CRM
ActiveCampaignData, direction and frequency agreed for your environment.
Where the integration helps
A customer buys a product or reaches a sales stage in Odoo. That event may inform an agreed follow-up in ActiveCampaign. We define the minimum data required and how both systems respect changes to contact preferences.
A changed customer field and a new purchase are different triggers. We separate contact updates from campaign starts. An administrative correction in Odoo should not unintentionally start another sequence of messages.
We start with the task your colleagues need to complete. Which information is copied today, who checks it and which exceptions occur? Those answers determine the integration scope. We agree responsibilities with the people managing both applications before configuring access or transferring data.
Odoo and your application
Relevant customer attributes and agreed Odoo events to ActiveCampaign. Subscriptions, preferences and opt-outs follow defined source and processing rules.
Select the customer identifiers and attributes actually required.
Define ownership and handling of subscriptions and opt-outs.
Pass purchases, returns or customer changes only as agreed triggers.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
A practical process example
A purchase is complete and marketing wants to send suitable follow-up information. We define the event allowed to pass through and its contact preferences. Integration recovery must not start a second campaign, and changed email addresses need to remain identifiable.
The starting point is a recognisable reference, such as an order, customer or file number. We record what has been processed and make failed steps visible. Recovery must continue from the right point without creating another copy of the same transaction.
From requirements to everyday use
We discuss the required data flow with sales, warehouse or finance. For each piece of information, we define where it originates and which system leads.
We connect relevant Odoo modules such as Sales, CRM, Inventory and Invoicing. Test orders help us check fields, permissions, returns and duplicate messages.
You receive guidance on operation and error messages. We agree on monitoring, support, maintenance and checks following software updates.
We first review what your Odoo version and existing modules provide. Where needed, we use an existing connector, an integration platform or custom API development. Our advice considers your process, costs and ongoing management.
A delayed API, expired access or duplicate message should remain visible. We test retries, duplicate handling and notifications, and agree who follows up on exceptions.
A useful first conversation
Tell us which versions you use, which information should move and where your team loses time. We will discuss a concrete next step.
Frequently asked questions
We check this first. According to Odoo, external API access on Odoo Online is available on the Custom plan, not Standard or One App Free. For Odoo.sh or self-hosted installations, we assess the version, modules and permissions. The other application may also require an additional licence.
This page presents implementation options delivered by Radorfa. We assess whether an existing connector is sufficient or custom development is required. We agree the fields, sync direction and exceptions with you; the listed applications are not a promise of connectors you can activate immediately.
Costs depend on your systems, data flows, data quality, existing modules and required controls. We distinguish configuration, any licences and ongoing management. Share your applications and one concrete process so we can prepare a focused proposal.
Software updates can change fields, permissions or APIs. We document the configuration and agree how changes are tracked and retested. We also clarify the management and support process for incidents and functional changes.