- Sales
Record the customer, products and price in Odoo.
- Inventory
The warehouse sees reserved items and what needs shipping.
- Administration
Delivery and invoice follow the agreed processing rules.
We also test partial deliveries, returns and amended orders with your staff.
Start with the order your colleagues process
Your webshop receives an order, the warehouse needs to know what to ship and administration needs the correct invoice information. If colleagues retype the same data in several places, an integration is worth investigating. Begin with one recognisable order: what information is needed, who checks it and when may the next step start?
Radorfa maps that route with sales, warehouse and administration. This creates a defined question, such as transferring a confirmed webshop order to Odoo and returning the shipping status. A clear process matters more than the number of connected applications.
Agree which system owns each type of information
A customer address may exist in both the webshop and Odoo. Without an agreement, a change in one system could overwrite a newer change in the other. Record where each data group is maintained, its transfer direction and how exceptions are resolved.
- Customers: how do both systems recognise the same customer?
- Products: which product code and unit do they use?
- Orders: which status authorises processing?
- Inventory: are you exchanging physical, reserved or available quantities?
- Invoices: who checks amounts, tax codes and posting status?
Check access before committing to the integration
The route depends on your Odoo version, hosting, subscription and the other application’s capabilities. A catalogue listing does not confirm that your particular environment provides the necessary access. The Odoo external API documentation describes access conditions. During discovery, we check the applicable requirements and available interfaces.
Test the order that goes wrong as well
One successful sample order does not show that the daily process is manageable. Agree tests for a missing product, amended order, partial delivery, return and interrupted connection. Who receives a failure notification? Can a colleague see what has already been processed? How will processing resume without duplicate transactions?
Write down the expected outcome for each test and ask the responsible colleague to verify it in both applications. Then agree who monitors processing and what happens when either system is updated.
A practical example: The Merchandise Company
For The Merchandise Company, Radorfa connects Odoo, LogiAction and Exact Online. Branded webshops, warehouse operations, tracking and financial processing form a connected chain. Read how those parts work together. This case shows a delivered integration; your own fields and process agreements determine the configuration for your business.
Prepare a useful first conversation
Bring your application names and versions, an anonymised sample order and a description of today’s manual work. This helps us discuss the desired data flow, dependencies and a suitable first step. Explore the Odoo integrations or discuss your integration question.