Channel & order
Preserve original order and channel references in Odoo.
Marketplaces · Odoo integration
Process Fyndiq orders alongside your other sales. 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
FyndiqData, direction and frequency agreed for your environment.
Where the integration helps
A marketplace brings its own order references and fulfilment rules. We assess how Fyndiq orders connect to Odoo Sales and how your warehouse identifies the correct products. Responses need to match the status expected by the sales channel.
Your warehouse uses internal product codes while Fyndiq may use different sales references. We map that relationship and test an unknown code. The order remains visible for review so a missing mapping does not produce an incorrect picking task.
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
Orders from Fyndiq to Odoo Sales, preserving channel references. Agreed stock and shipping updates return through the capabilities of your seller account.
Preserve original order and channel references in Odoo.
Agree product identification and availability published per channel.
Align shipping, cancellations and any returns with channel rules.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
A practical process example
The same products sell through multiple channels. A marketplace order needs to stay identifiable without requiring a separate manual administration. We record its source channel, agree the stock published and define how fulfilment is reported back.
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.