Orders & customers
Connect order references, customers, addresses and lines to Odoo Sales.
Webshops · Odoo integration
Carry webshop orders forward without retyping. 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
ShopifyData, direction and frequency agreed for your environment.
Where the integration helps
A Shopify order contains more than a customer and a total. Product variants, discounts, shipping and payment status need to reach Odoo together correctly. Radorfa maps them to your order process and defines which stock may be published back to the webshop.
We discuss whether Odoo should publish one or several stock locations and how orders are released for fulfilment. A payment notification differs from a shipping instruction. A partial shipment and refund verify that customer service, warehouse and finance recognise the same order.
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
Shopify orders and customers to Odoo Sales; agreed product and stock data from Odoo back to Shopify.
Connect order references, customers, addresses and lines to Odoo Sales.
Match product codes and variants; distinguish physical stock from availability.
Keep deliveries and tracking traceable; handle cancellations and refunds separately.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
An example to discuss together
This is an illustrative scenario. We confirm the fields and actions available in your versions and subscriptions before making a proposal.
A customer orders one medium shirt and one large shirt. Each variant has its own product code.
We agree how product codes, quantities, discounts and shipping charges appear on the sales order. The Shopify order reference remains recognisable.
We define which stock location supplies the available quantities and when shipment details may be returned.
We test a missing product code, a partially refunded order and the same order message arriving twice.
Bring a sample order with a discount, your variant codes and your stock locations. Remove personal data from shared examples.
Discuss this process →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 agree this with your warehouse: available stock, reservations and excluded locations must have consistent meanings. A trial order confirms the calculation and update.
Not automatically. We agree a start date and assess outstanding or historical orders separately, to avoid recreating orders already processed.
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.