Analysts and managers do their real work in spreadsheets, but the numbers they need are locked inside Odoo. Today the workaround is a manual dance: open a list view, apply filters, hit Export, download a CSV, re-import into Google Sheets, then fix broken formulas and pivot tables every single time. Odoo's native export is a one-shot snapshot — it has no schedule, no refresh, and no way to write a corrected value back. QWeb reports and dashboards live inside Odoo where a CFO who prefers Sheets can't touch them, and stitching a custom pivot across sale.order, account.move and stock.quant in the UI is painful. The moment someone wants "the same view, but updated automatically and shareable with a link," Odoo native runs out of road.

The Google Sheets Live Connector closes that gap. We build a dedicated Odoo module (__manifest__.py declaring dependencies on base plus whichever business apps your reports touch) that exposes a governed read path over Odoo's JSON-RPC / XML-RPC API and a companion Google Apps Script bound to your target spreadsheet. From a sidebar in Sheets an authorized user picks an Odoo model (sale.order, account.move.line, crm.lead, or any custom model), selects the exact fields and a domain filter, and the data materializes into a named range. A new ir.model in Odoo stores each connection's definition — model, field list, domain, target range, refresh cadence — so the mapping is versioned, auditable, and reusable rather than trapped in one person's macro.

Under the hood, refresh is driven by a ir.cron automated action on the Odoo side (or a time-based trigger in Apps Script) that re-runs each saved query on the schedule you choose — every 15 minutes, hourly, or on open. Reads honor ir.model.access.csv and record rules, so a Sheets user only ever sees rows their linked Odoo user is entitled to see; there is no bypass of Odoo's security layer. Where you need editable lists, we build an optional two-way write-back: edited cells in a whitelisted range are validated against field types and access rights, then pushed back via write() with a full audit log and conflict detection, so a stale cell never silently clobbers a newer Odoo value. Connection uses a dedicated service account or OAuth credential configured once — no passwords pasted into cells.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to map exactly which models, fields, filters and refresh cadences you need, whether you're on Odoo 17.0, 18.0 or 19.0, and Community vs Enterprise (both supported — no Enterprise-only dependency). We then build the module and Apps Script against your data model, run UAT on a staging database, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source, documentation, a training session, and a post-go-live support window — and you own the Git repository outright.