| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 743 |
| Technical Name |
gb_pos_offline_receipt_email_sms |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
POS Digital Receipts
Branded digital POS receipts delivered by email or SMS with BYOK gateways
When an order is paid, the cashier can email or text a branded receipt to the customer. Deliveries that cannot go out immediately — no connectivity or a missing contact — are queued and retried automatically. Bring your own SMS gateway key (a Twilio-style HTTP API) so there is no per-message middleman taking a cut.
Key Features
Email & SMS receipts
A per-POS-config toggle enables email receipts, SMS receipts, or both, with a branded header and footer so every receipt carries your shop's identity.
Delivery records & audit
Every send attempt creates a delivery record with channel, status, retry count and any error message, all tied back to the originating POS order.
Offline-friendly queue & retry
Failed or pending deliveries are queued and retried automatically by a cron, so a flaky till connection never means a lost receipt.
BYOK SMS gateway
Configure your own SMS gateway on the company — endpoint, sender ID and credentials. No reseller, no markup, you keep full control of delivery and cost.
Customisable email body
Receipts render through a customisable text template with named tokens ({order_name}, {total}, {header}, etc.) on top of the native Odoo mail layer, so non-technical staff can tailor the wording without any code changes.
Delivery analytics
Track success rate, channel split and per-config counters to see how digital receipts are performing across your shops.
Screenshots
Receipt Settings
Receipt Templates
Why Choose This Module
Native POS receipting is paper-first and offers no clean email/SMS delivery with retry and audit. This app fills that gap and keeps you off expensive per-message reseller plans by letting you bring your own gateway key. No external lock-in, no subscriptions — just branded digital receipts your customers actually keep.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: point_of_sale, mail
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 743 |
| Technical Name |
gb_pos_offline_receipt_email_sms |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module