Master data
Identify customers, suppliers and products through stable references.
ERP · Odoo integration
Connect on-premises Business Central with 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
Microsoft Business Central On-PremiseData, direction and frequency agreed for your environment.
Where the integration helps
With an on-premises Business Central installation, data exchange passes through your own infrastructure. We assess with your administrator how Odoo can securely access the required interface. Version, customisations and server connectivity determine the appropriate setup.
Your administrator determines how the local environment can be reached without granting unnecessary access. We discuss maintenance windows, technical accounts and customisations. Upgrades receive a repeatable check of the agreed data flow.
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
Selected customer, product or document data between Microsoft Business Central On-Premise and Odoo. We agree the source and direction for each data item; installed modules and interfaces determine available actions.
Identify customers, suppliers and products through stable references.
Connect the agreed handover to Odoo Sales, Purchase or Invoicing.
Align administrations, warehouses, company permissions and currencies.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
A practical process example
One business unit records a sale and another handles inventory or finance. We turn that transition into an explicit agreement: which document moves, under which reference and who corrects exceptions? The integration follows the chosen responsibilities across systems.
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.