ERP
Odoo
Read ledger, inventory and sales data from Odoo into the G1 data layer.
Where this actually stands
PlannedPlanned
Designed and on the roadmap: we know what it would do and roughly what it takes. No code has been written, and we are not going to imply otherwise.
Connection type
API
A direct connection to the other system's interface, reading and writing on a schedule or on an event.
What it would do
Odoo, connected.
Connect an Odoo estate without replacing it.
G1 does not ask you to replace a system that works. Where a connection exists, the point of it is to remove the person in the middle — the weekly export, the re-key, the spreadsheet that reconciles two tools that should have agreed in the first place.
Large ERPs are rarely worth ripping out. G1 is designed to read from them and add the layers they do not give you, rather than compete with them.
Every categoryModules it feeds
- AccountingAvailableA general ledger that drills back to the document behind every number.
- InventoryPlannedWhat you hold, where it is, and what it is worth.
- AnalyticsAvailableAnalysis on the live ledger, not a copy of last month's export.
A connector is only as useful as the module reading it. Where the module is still in development, the connector waits for it.
ERP
Others in the same category.
- On requestExplore
Data feed
SAP
Read from SAP and add the layers it does not give you.
- On requestExplore
API
Oracle NetSuite
Connect NetSuite as a source, not a rival.
- On requestExplore
API
Microsoft Dynamics 365
Bridge Dynamics into a single group view.
Names listed here are trademarks of their respective owners and appear only to describe compatibility and connection plans. No partnership, endorsement or affiliation is implied, and no third-party logos are used anywhere on this site.
Connect what you already use
Tell us how Odoo is used where you are.
What matters is not the connector — it is the work it removes. Describe the manual step and we will tell you whether a connection actually fixes it.