Social storefronts and live commerce sell fast and settle slowly. Orders land in a seller centre app, stock is decremented in a place your ERP cannot see, refunds and cancellations happen inside a short window you never hear about, and weeks later a payout arrives net of commission, shipping subsidies, promotion co-funding and adjustments that nobody can tie back to a specific order. Odoo out of the box has no concept of any of this. sale.order is happy to record a sale once someone types it in, stock.quant will reserve goods once a picking exists, and account.move will post an invoice — but nothing bridges the social platform to those models. Teams end up exporting CSVs from the seller centre, re-keying orders, and discovering oversells only when a picking cannot be reserved. The Odoo eCommerce module does not help here either: it drives your own website, not somebody else's storefront.

The Social Commerce Connector is the missing bridge, written as a proper Odoo module rather than a scripted import. We add a social.commerce.account model holding one authenticated shop connection (credentials in an encrypted field, token refresh handled by an ir.cron), plus social.commerce.listing linking a product.product to its remote listing id and variant/SKU mapping. Catalog publishing pushes titles, descriptions, images, variant attributes and prices out of Odoo, then stores the remote id so the mapping is never lost. Order capture receives webhooks on a dedicated controller route with a polling fallback, and every payload is written to a social.commerce.raw.order staging record first — so a malformed or unexpected message is retried and inspected rather than silently dropped. From that staging record we create a real sale.order with the correct customer, fiscal position, delivery address, taxes and analytic distribution, and confirm it so Odoo does what Odoo is good at: reserving stock, generating the picking and running your existing delivery workflow.

Stock flows in both directions. A @api.depends compute on free-to-promise quantity, with configurable buffers and a per-listing safety stock, drives a queued push back to the platform so the storefront stops advertising units you have already committed elsewhere. Warehouse-scoped and multi-company setups are respected — the connector never reserves out of a warehouse the shop is not allowed to sell from. Fulfilment goes the other way: when a stock.picking is validated, the carrier and tracking reference are pushed to the platform inside its shipping SLA, and acknowledgement states are written back onto the order so your team sees one truth in Odoo. Payout reconciliation lands settlement statements as a social.commerce.payout record with lines matched to orders, commission and fee lines posted to the accounts you nominate, and an explicit variance list for anything that will not tie — the report finance will actually open every week.

Everything ships as maintainable Odoo, not a black box: a versioned __manifest__.py per target series, ir.model.access.csv plus record rules so a shop operator sees only their own accounts, list/form/kanban views and an operations dashboard in XML/OWL, QWeb reports for payout reconciliation and daily order intake, and an ir.actions.server and automated-action layer so routing rules can be extended without touching Python. Every remote call is idempotent and keyed, so a retried webhook cannot create a duplicate sale order, and all connector models are readable over the XML-RPC/JSON-RPC API for your BI tooling. The connector runs on Odoo Community; where you have Enterprise we wire into what you already pay for, including the full accounting reconciliation widget for payouts and Studio-compatible field extension. Odoo 17.0, 18.0 and 19.0 are supported, built against your exact series rather than back-ported blindly.

This is a build-to-order product, so nothing is downloaded and nothing is guessed. We start with a scoping call to confirm which platforms and shops you sell through, your API access level, warehouse and company topology, tax treatment for marketplace-facilitated sales, and how you want commission and fees posted. You get a written scope, a fixed price and a delivery date. Typical delivery is one working week from confirmed scope, depending on how many storefronts and how much settlement complexity is in play. We build against a copy of your database, hand you a staging instance for UAT, then install on production in a scheduled window with a rollback plan. You receive the full source code and the git repository — no licence key, no obfuscation, and no dependency on us to keep running.