Master data
Identify customers, suppliers and products through stable references.
ERP · Odoo integration
Connect AFAS with Odoo.
Keep Odoo and AFAS aligned on business data. 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
AFASData, direction and frequency agreed for your environment.
Where the integration helps
Keep Odoo and AFAS aligned on business data.
When Odoo supports commercial processes and AFAS runs another administration, clear responsibilities matter. We discuss the customer, product or financial data that needs to move. Available AFAS GetConnectors and UpdateConnectors, together with your Odoo setup, determine the technical approach.
We start with a limited data set, such as customers and final sales invoices. Your AFAS administrator confirms the available connectors. We also test a missing required value: the issue must reach the right colleague for correction.
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
How AFAS and Odoo exchange data
Relevant customer and financial data between Odoo and AFAS Profit using available GetConnectors and UpdateConnectors.
Orders & documents
Connect the agreed handover to Odoo Sales, Purchase or Invoicing.
Organisation & access
Align administrations, warehouses, company permissions and currencies.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
An example to discuss together
The same customer in two administrations
This is an illustrative scenario. We confirm the fields and actions available in your versions and subscriptions before making a proposal.
In Odoo
An employee changes a business customer’s details.
Into AFAS
We define which account reference identifies the customer and which fields may be updated through the available connectors.
When records differ
A missing reference or conflicting change needs an agreed check. The latest message should not blindly overwrite earlier information.
What your team checks
We test a new account, an existing account with a different address and missing permissions on the agreed AFAS connector.
Useful for a first conversation
Bring the relevant administrations, available Get and Update Connectors and account management agreements.
Discuss this process →From requirements to everyday use
From agreed scope to a managed integration.
Map your process
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.
Configure and test together
We connect relevant Odoo modules such as Sales, CRM, Inventory and Invoicing. Test orders help us check fields, permissions, returns and duplicate messages.
Deliver and keep track
You receive guidance on operation and error messages. We agree on monitoring, support, maintenance and checks following software updates.
Existing connector or custom development?
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.
Ready for exceptions
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
Discuss your AFAS integration.
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
Clear agreements before we start.
Which system may change customer details?
We agree this for each type of data. Commercial contacts may be managed in Odoo while AFAS owns a financial reference. Both systems do not need to write back every field.
Can we start by only reading data?
Yes. A limited first scope can be read-only if your available connectors and process allow it. Writing to AFAS is a separate decision with its own permissions and tests.
What does an Odoo integration cost?
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.
Will the integration keep working after an update?
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.