Documents
Connect SharePoint files with recognisable Odoo references.
Microsoft 365 · Odoo integration
Bring Odoo information into collaboration. 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 365Data, direction and frequency agreed for your environment.
Where the integration helps
Your team discusses work in Microsoft Teams and manages documents in SharePoint. Radorfa can connect that workplace to Odoo, for example through document links or agreed Power Automate notifications. Access to customer and order information is checked on both sides.
We decide whether staff need to open a file from Odoo or only receive a Teams notification. A document link does not replace SharePoint permissions. We test different user roles to verify intended access and the agreed boundaries.
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
Link a document for an Odoo order to SharePoint, or send an agreed notification to Teams through Power Automate.
Connect SharePoint files with recognisable Odoo references.
Send agreed events to the correct destination through Power Automate.
Align Microsoft 365 and Odoo permissions with the customer task.
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.
An employee opens a job and needs to find the project documents.
We assess a reference to the correct document location and an agreed Teams notification, for example through Power Automate.
We test that an authorised colleague opens the right folder and someone without project access cannot view the documents.
We check a new project member, revoked access and a moved folder or broken document reference.
Bring your project structure, Microsoft 365 licences and document access agreements. Do not share sign-in credentials.
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
That may not be necessary. We first decide where documents remain managed and whether a reference is sufficient, so there is no confusion about the authoritative version.
No. Access is configured and checked in each environment. A document reference does not automatically grant permission to those documents.
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.