Teams that run their whole business in Odoo still bounce out to separate tabs and third-party dashboards to publish social content. That fragmentation means marketing calendars live outside the ERP, campaign results never link back to the leads and sales orders they generated, and post approvals happen over chat instead of an auditable workflow. Odoo core has no first-class concept of a social channel, a scheduled post, or a publishing queue — the marketing and mail layers stop at email and internal messaging — so the moment you need multi-platform scheduling with a shared editorial calendar, native Odoo runs out of road.

ECOSIRE builds a purpose-designed social media module that lives inside Odoo. At its core is a new social.post model (with models.Model, fields, and @api.depends computes that roll up per-channel status) plus a social.channel model that stores each connected account and its credentials as encrypted parameters rather than plaintext fields. Posts move through a state machine (draft → scheduled → queued → published / failed) driven by an ir.cron job and Odoo automated actions, so a marketer can compose once, attach media via ir.attachment, target several channels, and let the scheduler fan the content out at the planned time. A calendar view, Kanban pipeline by state, and list/form views (XML on 17.0/18.0, with OWL components where an interactive composer helps) give the team the editorial board they expect, and QWeb reports produce a printable content calendar or per-campaign performance sheet.

Publishing itself is handled by connector services that call each platform's own API using stored tokens, with retry and back-off logic recorded on the post so failures are visible instead of silent. Because everything is a real Odoo record, we wire the module into the objects you already use: link a social.post to a utm.campaign, a crm.lead, or a product so downstream reporting ties social activity to pipeline. Access is governed properly through ir.model.access.csv and record rules — for example, editors draft, a marketing manager approves, and only approved posts reach the queue — and the whole model is exposed over Odoo's XML-RPC/JSON-RPC API so external tools or your own automations can create and query posts programmatically. We target your edition and version specifically; multi-company channel isolation, Enterprise-only view widgets, and localization are all handled per your environment across Odoo 17.0, 18.0, and 19.0.

Delivery is build-to-order: it starts with a scoping call to confirm which platforms, accounts, approval roles, and reporting links you need, after which we produce a fixed quotation and a staging build for UAT before anything touches production. Typical delivery is one working week from confirmed scope, and you receive the full installable source, a git repository, and a post-go-live support window. Pricing starts from $999 (indicative, single-company base scope); the number of connected platforms, multi-company channel isolation, deeper analytics ingestion, and integration with additional Odoo apps increase the quoted scope.