Sales conversations happen in chat, but the order still has to be created somewhere else. Your team fields product questions, prices, and confirmations inside Odoo Discuss (or a linked channel), then has to leave the thread, open the Sales app, hunt for the customer, rebuild the line items from memory, and only then confirm and invoice. Odoo core does not expose an order-taking surface inside mail.channel / Discuss — the chatter can log a message on an existing sale.order, but there is no native way to spin a quotation up, add lines, price it, confirm it, and raise the account.move invoice without abandoning the conversation. That round trip is where lines get dropped, the wrong pricelist gets applied, and follow-through stalls.

This is a made-to-order module we build for your Odoo. We add a chat-native ordering surface: an OWL-based composer action inside the Discuss thread that lets an authorised user attach or create a res.partner, search product.product with your live pricelist and tax rules applied, add order lines, and generate a real sale.order — all from within the conversation. The order is a first-class Odoo record from the moment it is created (not a shadow object), so sale.order.line prices, account.tax, and pricelist logic resolve exactly as they would in the Sales app. A dedicated model links each conversation to the orders it produced, with @api.depends computed fields surfacing order state, invoiced/to-invoice amounts, and payment status back into the chat header. When the customer says yes, a confirm action moves the order to sale, and an invoice action calls the standard _create_invoices() flow to produce the account.move and, optionally, render the QWuoTE/QWeb invoice PDF and post it back into the thread.

Technically it is a clean, upgrade-safe addon: its own __manifest__.py declaring dependencies on sale_management, account, and mail; models extending rather than overwriting core (sale.order, mail.channel); permissions enforced through ir.model.access.csv plus record rules so a chat agent can only act on partners and orders their team owns; and views/OWL components layered as inherited XML so a version upgrade never clobbers Odoo's own screens. Server-side automation (automated actions / ir.cron where needed) can push status changes — order confirmed, invoice posted, payment received — as system messages into the thread. Everything the chat surface does is also reachable over the XML-RPC/JSON-RPC external API, so a website widget, WhatsApp bridge, or third-party chat front end can drive the same order-taking flow. We support Odoo 17.0, 18.0, and 19.0, on Community or Enterprise (Enterprise's richer Discuss and accounting features are used when present; the module degrades gracefully on Community).

Delivery is build-to-order: after a short scoping call we confirm the exact partner-matching rules, pricelist/tax behaviour, which chat surface (native Discuss, livechat, or an external channel), and the invoice/payment steps you want automated, then hand back a fixed quote and a written scope. Typical delivery is one working week from confirmed scope, built and tested on a staging copy of your database before we touch production. Pricing starts from $999 (indicative, single-company base scope); multi-company chat routing, external chat-channel integrations (e.g. a WhatsApp or website widget over JSON-RPC), deeper localization of the invoice/tax flow, or migrating historical conversation-to-order data increases the quoted scope.