Less duplicate entry
Sales, purchasing, inventory and invoicing use connected data, with clear ownership for each data source.
Odoo ERP
Does your team enter the same information into separate systems? Radorfa connects sales, inventory and administration in Odoo, configured around everyday work.
Start with your question. We agree the work and costs before starting.

From our customer cases
Radorfa connected Odoo, LogiAction and Exact Online for branded webshops, warehouse operations and financial processing. Read how the systems and responsibilities fit together.
Odoo supports the order process, LogiAction the warehouse work, and Exact Online the financial processing. Radorfa connected those parts around the route from order to shipment and invoice.
Read the case →What this means for your team
Sales, purchasing, inventory and invoicing use connected data, with clear ownership for each data source.
Roles, fields and steps match how colleagues work. Users review configuration with familiar examples.
Custom modules, integrations and changes receive documentation, tests and an agreed maintenance route.
Odoo in everyday work
Sales follows the customer enquiry in Odoo CRM, then creates a quotation and confirmed order in Odoo Sales. Inventory and, where needed, Purchase support delivery; administration handles the invoice. We test the process with your products, roles and exceptions.
Modules, accounting configuration and integrations depend on your processes. This is a process example.
Record the customer, products and price in Odoo.
The warehouse sees reserved items and what needs shipping.
Delivery and invoice follow the agreed processing rules.
We also test partial deliveries, returns and amended orders with your staff.
We map processes, roles, source data and current systems. We select modules, prepare migration and validate trial imports, totals and access rights.
Where needed, we connect Microsoft 365, webshops or an existing administration system. We document data flows and error handling. Custom modules receive version control and tests for the agreed Odoo version.
Users test real scenarios before handover. We provide guidance and agree support, updates, backups and checks for future releases.
From setup to everyday use
An order needs to work beyond the screen. We go through the agreed steps with your users and check data, roles and exceptions.
Our approach
We follow work from request to completion and identify duplicate tasks.
We configure modules, migrate sample data and test the full process.
Your team receives guidance and a clear route for questions, changes and management.
Before we start
No. We agree a practical sequence and dependencies. A defined first phase makes data, processes and adoption easier to verify.
Yes. We assess configuration, modules, integrations and problems, then propose improvement, migration, support or management.
When standard features or configuration do not adequately solve the process requirement. We discuss value, maintenance and upgrade implications before development.
Modules, roles, data quality and volume, integrations, customisation and training. We discuss these requirements before proposing a scope and budget.
Tell us about your situation
Describe one process that currently involves too much manual work and which systems it uses. We discuss a practical first step with Odoo.