Retail counters increasingly serve two customers at once: the walk-in who pays and leaves, and the B2B or special-order buyer who wants a formal quotation, an advance deposit, and delivery of goods you do not have in stock today. Native Odoo POS is optimized for the first case — an order closes atomically against on-hand stock, prints a receipt, and settles the payment immediately. The moment your cashier needs a sale.order with a proper quotation number, a credit check against the customer's property_account_receivable, or a partial delivery that leaves a backorder open, the register runs out of road. Staff drop the customer, walk to a back-office desktop, re-key the cart into Sales, and hope the two documents reconcile. That handoff is where margin, accuracy, and the customer's patience leak away.

This build-to-order module closes that gap by adding a "Create Sale Order / Quotation" action inside the POS UI (an OWL component wired into point_of_sale assets) that serializes the current order lines and customer into a real sale.order record via a controller/ORM path — not a pos.order. The customer set on the register maps straight through, product lines carry their unit price, taxes, and discounts, and you choose the outcome at the counter: a draft quotation (state='draft') to email and print, or a confirmed sale order that reserves stock and generates the delivery. Advance payments are captured as a deposit using Odoo's down-payment product on the order (Enterprise's down-payment wizard where available, an equivalent sale.advance.payment.inv flow on Community), so the deposit posts against the eventual invoice rather than floating as an unlinked POS payment. Where the customer wants some items now and some later, the confirmed order feeds stock.picking so Inventory can validate a partial delivery and Odoo keeps the backorder open automatically.

Technically, the module is a clean, upgrade-safe addon: a declared __manifest__.py depending on point_of_sale, sale_management, and stock; server-side extensions on pos.order/sale.order using models.Model inheritance with @api.depends computes for any derived totals; a credit-limit guard that reads the partner's outstanding receivable and blocks or warns per your policy via a configurable res.config.settings field; access controlled through ir.model.access.csv plus record rules so only permitted POS roles can raise orders or override the credit block; and QWeb reports for the pro-forma and quotation PDFs branded to your template. The register-to-order call is exposed cleanly so it also works over the JSON-RPC/XML-RPC API if you drive it from another system. Everything targets Odoo 17.0, 18.0, and 19.0, and we confirm Community vs Enterprise behavior for the down-payment and any studio-adjacent flows during scoping.

Because this is built to order, there is no instant download. After a short scoping call we confirm your exact flows — quotation numbering, deposit product, credit policy, which POS roles get the button, report layout — write a fixed scope, and build against your Odoo edition and version. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, UAT on a staging copy of your database, a training session for counter and back-office staff, and a post-go-live support window. The Git repository is handed over to you at the end so the code is yours to keep and extend.