Odoo 19

What we scope together

Review the installed edition and supported API, map customer and product identifiers, define tax and UoM handling, then agree invoice/payment references and recovery from sync failures. Availability depends on the scoped connector and acceptance tests.

Odoo depth, Ever operational focus

The intended connection combines Sales, Solar, Field and Trade workflows with Odoo enterprise ERP depth. Planned scope includes customers, products, units of measure, taxes, purchasing, inventory, invoice/payment and accounting references. Odoo 19 is Coming Soon: the connector is not yet implemented or live. Ever Digital’s Odoo partnership and implementation services are separate from connector availability.

AI respects the source permissions

Any future Ever AI use of Odoo data must follow agreed authorization and data boundaries. An integration does not grant every user access to accounting or other restricted records.

Odoo is the priority ERP connection

Plan Odoo 19 customer/product references, commercial documents and agreed operational handoffs around installed modules and API access. Keep Odoo implementation services separate from an Ever connector: being an official partner does not make the connector live. Define stock and accounting ownership before proposing synchronization, and include duplicate/retry handling in acceptance.

What to bring to discovery

Provide the system/version, hosting model, relevant modules, record types, data owner and desired direction of flow. Describe one successful handoff and one exception, such as a duplicate or rejected record. We can then scope mapping, authorization, retries, reconciliation and acceptance. Share synthetic examples first; credentials and private exports belong in an agreed secure implementation process.

Your questions, answered