Most retail and hospitality teams still hand over a thermal paper slip or ask for an email that customers rarely open. Odoo's native Point of Sale can email a receipt when a partner is attached to the order, but there is no built-in path to WhatsApp — the channel your customers actually read within minutes. The result is wasted paper, lost proof-of-purchase, and a missed re-engagement touchpoint at the exact moment a buyer is holding your product. Odoo core runs out of road here: point_of_sale has no WhatsApp transport, no per-session toggle, no delivery audit trail, and Enterprise's WhatsApp connector is oriented toward marketing and discuss threads rather than transactional receipts fired at on_payment from the POS front end.

This is where our build-to-order module comes in. We build a dedicated Odoo application that extends pos.order and the POS OWL front end so that, the moment an order is validated, the receipt is rendered from your existing QWeb POS ticket and pushed to the customer's WhatsApp number. Technically, we add a models.Model extension carrying the delivery state (queued, sent, failed) with @api.depends compute fields for retry counts, an outbound gateway service that talks to your chosen WhatsApp Business API provider over its REST endpoint, and a settings layer in res.config.settings so cashiers and managers control default behavior per POS config. A cashier can also trigger a manual send from an added OWL button in the payment screen — useful when the phone number is captured mid-transaction. Every send writes a log line and (optionally) posts to the order's chatter, giving you a queryable delivery history over the standard XML-RPC/JSON-RPC API for reconciliation or BI.

Because it is a real Odoo module and not a bolt-on, everything respects the framework: access is governed by ir.model.access.csv plus record rules so only POS users see delivery logs and only managers change gateway credentials; the WhatsApp API key is stored as a config parameter rather than hardcoded; and the receipt payload can be a plain text summary, a PDF of the QWeb report, or a media template, depending on what your provider account supports. We target Odoo 17.0, 18.0 and 19.0, and we account for Community vs Enterprise differences — on Community we ship the full transport ourselves; on Enterprise we can either reuse the platform WhatsApp infrastructure or run standalone, whichever keeps your upgrade path clean. Automated actions or ir.cron handle retry-on-failure so a transient provider outage does not silently drop a receipt.

Delivery is build-to-order: after a short scoping call we confirm your Odoo version, edition, POS configuration and WhatsApp provider, agree the exact behavior, then build on a staging copy of your database, run UAT with you, and deploy to production with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company POS estates, multiple WhatsApp sender numbers, deeper provider integrations (interactive templates, delivery-status webhooks) and localization of receipt content increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.