Most teams selling through social commerce channels end up maintaining a second product catalog by hand: exporting a spreadsheet from Odoo, reshaping columns to match the channel's feed spec, re-uploading it weekly, and then quietly living with stale prices, sold-out items still showing as available, and variants that never map cleanly. Odoo out of the box has no concept of a social channel feed — product.template and product.product hold your data beautifully, but nothing publishes it in the exact schema, currency, availability semantics, and image conventions these external catalogs demand. The manual export/import loop breaks the moment your pricelists, stock, or variant matrix change during the day, which for an active store is constantly.

This is a build-to-order module we design and build for your database. At its core is a new social.catalog.feed model (built on models.Model) that maps your Odoo products, variants, pricelists, and stock to a channel-ready feed. A configurable field-mapping layer lets us translate your product.template/product.product fields, attribute values, brand, condition, and category taxonomy into the destination schema without hard-coding — so a change in your catalog structure is a configuration change, not a re-code. Availability and price are @api.depends compute fields driven by your chosen pricelist and warehouse/quant rules, so "in stock" reflects the same numbers your salespeople see. Feeds are generated on a schedule via ir.cron and can also be pushed on change through Odoo automated actions, and the module exposes an authenticated feed endpoint plus outbound sync so the channel always reads current data. Everything is exposed through standard Odoo views (XML/OWL) with a menu for feed configuration, a mapping editor, and a sync-log model for observability.

We build it to Odoo engineering conventions end to end: a clean __manifest__.py with pinned dependencies, security via ir.model.access.csv and record rules so feeds and credentials are scoped to the right users and companies, QWeb-rendered diagnostics for the sync log, and integration through Odoo's XML-RPC/JSON-RPC layer where your workflows need programmatic access. The module targets Odoo 17.0, 18.0, and 19.0, and we account for Community vs Enterprise differences (for example, where multi-company rules or accounting-adjacent fields behave differently) during scoping so nothing surprises you at go-live. Channel API credentials and secrets are stored using Odoo's configuration/parameter facilities rather than being embedded in code.

Delivery is build-to-order. It starts with a short scoping call where we confirm which channels, catalogs, pricelists, warehouses, and variant rules are in play, then we build on a staging copy of your database, run UAT with you, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope, depending on catalog size, integration count, and localization needs. Pricing starts from $999 (indicative, single-company base scope); additional channels or catalogs, multi-company/multi-currency feeds, deeper localization, and larger data-migration volume increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is indicative, not a firm fixed price.