Marketing and sales teams that already run their operation in Odoo end up managing Facebook in a completely separate tab: drafting posts in the native Meta interface, copying engagement numbers into spreadsheets, and losing track of who replied to which comment. Odoo's Enterprise social app covers part of this, but its stream model is opinionated and hard to bend — you can't easily reshape the data into your own records, tie a post back to a UTM campaign or a CRM lead, expose page insights inside custom dashboards, or trigger publishing from your existing automated actions. Community editions have nothing native at all. The result is a marketing function that Odoo can neither report on nor automate.

Social Facebook is a module we build to close that gap. It authenticates against the Facebook Graph and Pages API using a long-lived page access token stored encrypted in Odoo, and models each managed page, published post, scheduled post, comment, and inbound message as first-class Odoo records. Concretely, we ship models such as facebook.page, facebook.post, and facebook.insight built on models.Model, with fields.Many2one relationships back to res.company and (optionally) utm.campaign, @api.depends compute methods for derived metrics like engagement rate and reach-per-post, and ir.cron jobs that poll the API on a schedule to pull fresh insights and push queued posts at their publish time. Publishing supports text, link, single-image, and multi-image posts, with an approval state machine so a draft moves through review before it goes live.

On the technical surface, everything is wired the Odoo way. Access is governed by ir.model.access.csv plus record rules so a multi-company deployment only ever exposes a user's own pages; a dedicated "Social Manager" group gates publishing and token management. The UI is delivered as standard XML views — list, form, and a calendar view of the publishing schedule — with an optional OWL component for a live engagement widget. QWeb templates drive a periodic performance report (top posts, follower growth, reach by placement) that can be emailed or exported to PDF. Because every record is native Odoo, the whole thing is reachable over the external XML-RPC / JSON-RPC API, so an external scheduler or another system can create scheduled posts programmatically. We target Odoo 17.0, 18.0, and 19.0, and adjust the manifest (__manifest__.py) dependencies to whatever your edition and installed apps require.

Delivery is build-to-order. After a short scoping call we confirm exactly which pages, post types, insight metrics, and approval rules you need, agree the Odoo version and edition, and return a fixed quotation and timeline — typically 2–4 weeks from confirmed scope. We build on a staging copy of your database, run UAT with you, then install to production with a rollback plan and hand over the git repository. Pricing starts from $249 (indicative, single-company base scope); managing many pages, deeper insight history, extra post formats (reels/video), or tying posts into CRM/UTM attribution increases the quoted scope.