Skip to Content

Sales, Quotations & Layaway from POS

by
Odoo

$ 47.37

In-App Purchases
v 19.0 Third Party
This module requires Odoo Enterprise Edition.
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Point of Sale (point_of_sale)
• Sales (sale_management)
• Invoicing (account)
• Discuss (mail)
• Inventory (stock)
Lines of code 1073
Technical Name xb_sale_order_from_pos
LicenseOPL-1
Websitehttps://www.xubax.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Point of Sale (point_of_sale)
• Sales (sale_management)
• Invoicing (account)
• Discuss (mail)
• Inventory (stock)
Lines of code 1073
Technical Name xb_sale_order_from_pos
LicenseOPL-1
Websitehttps://www.xubax.com

Sales, Quotations & Layaway from POS

Create quotations, orders and layaways at the till — collect advances, settle the balance, print an enriched receipt with an online-payment QR.

[ Banner / hero screenshot — POS with the “Order / Layaway” action ]

Built clean-room on native Odoo (point_of_sale, pos_sale, sale, l10n_mx_edi). It coexists with — does not replace — the native Quotation/Order loader. Every feature is optional and configured per Point of Sale.

🌎 Works with any localization. First-class support for Mexican CFDI 4.0 (advances / settlement invoicing, SAT payment forms, branch RFC). l10n_mx_edi ships as a dependency but stays dormant unless your company uses the Mexican localization — non-MX companies get pure native invoicing.

What it does

📝 Quotations, Orders & Layaways

Create the three document types straight from the POS. None is confirmed on creation — confirmation happens natively when the payment is validated.

💵 Multiple advances

Collect one or more partial advances (down payments) through the native down-payment product. The balance is payment-based and always up to date.

🧾 Enriched receipt

State-aware title, payment summary (Total / Advance / Balance), product detail on advance tickets, and a consistent cash-rounding line.

🔗 Online payment QR

While a balance remains, the receipt prints a portal QR so the customer can review and pay online. A configurable self-invoice QR is also supported.

Three document types

Type Created as Advance Confirmed
Quotation sent quotation optional natively, on payment
Order sent quotation optional natively, on payment
Layaway (apartado) sent quotation required ( > 0 ) natively, on payment
[ Screenshot — document-type selector at the POS ]

Required setup (per selling company)

Configuration requirements learned in the field — the module attributes the invoice to the right company automatically, but the fiscal/accounting master data must exist on each selling company.

  1. Down-payment product (native POS) — set its income account for every selling company (on the product or its category). A branch without it fails the advance invoice with “Falta la cuenta requerida.”
  2. Settle rounding product (optional) — a 0%-IVA service with Available in POS = OFF (mandatory; if left visible it can break POS loading), an income account per company, and — in Mexico — a SAT ClaveProdServ (placeholder 01010101 if none applies). If unset, an all-16% settle simply tolerates a ±0.01 residual.
  3. POS payment method → SAT “Forma de pago” — map each method (e.g. MX: Cash → 01, Transfer → 03, Debit → 28, Credit → 04) so the CFDI reports the real payment form.
  4. Multi-company / branches — when branches share a sales journal, the invoice is attributed to the order’s company; the CFDI is issued under the branch RFC if it has one, otherwise under the nearest ancestor with a VAT (native l10n_mx_edi behaviour).
  5. Cash rounding — “only on cash” rounding is excluded from the CFDI automatically; the cash difference stays in the session. Intended behaviour.

Configuration

Settings ▸ Point of Sale ▸ “XUBAX – Sale Order / Quotation”. English source with an es_MX translation. A single master switch enables the feature; every sub-option below depends on it.

  • Create Sale Order / Quotation — master switch.
  • Default document state — which type is pre-selected by default (does not confirm anything on creation).
  • Allow quotations — let the cashier save a draft quotation.
  • Differentiate Order and Layaway — separate actions vs. one combined.
  • Show total & pending balance — in the POS order panel.
  • Detailed order receipt — product detail, total and balance.
  • Show customer reference — before the customer name.
  • Auto-print receipt on create.
  • Show online portal link on receipt — the payment QR (needs Detailed order receipt).
  • Self-invoice QR only when settled — avoids a double QR on advances (needs Self-Invoicing).
  • Settle rounding product — absorbs the rounding cent.
[ Screenshot — POS settings section, two columns ]

The receipt

[ Screenshot — advance ticket with balance + payment QR ]

Title by document state, a Total / Advance / Balance summary, the payment QR while a balance remains, a configurable self-invoice QR, the advance’s product detail, and a cash-rounding line that always reconciles (Total + Rounding = To Pay; Cash − To Pay = Change).

Note for implementers: installing over existing data recomputes amount_unpaid on POS-linked sale orders (a native-compute correction), which may surface a real pending balance on orders that previously looked paid.

Requirements

  • Odoo 19.0 Enterprise.
  • Depends: point_of_sale, pos_sale, sale, l10n_mx_edi (the latter a hard dependency that stays dormant on non-Mexican companies — keyed on the fiscal country, like l10n_mx_edi itself).
  • Soft dep: order-level internal note maps to sale.order.internal_note only when sale_subscription is present — guarded, no error otherwise.

Known limitations

  • Only a single rounding currency (MXN) tested.
  • SO header delivery_status stays empty — delivery is fulfilled through the POS picking, not an SO picking (by design).
  • No in-POS customer signature yet (roadmap).

XUBAX

Support: soporte@xubax.com · www.xubax.com
License: OPL-1 · Odoo 19.0 Enterprise 

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.