POS Direct Print

What it does

Odoo prints point of sale receipts from the browser, which works perfectly while the till and the printer share a room. Move the database to Odoo.sh, or any server outside the shop network, and that assumption quietly stops holding. It is the kind of thing nobody mentions until go-live week.

POS Direct Print renders the receipt on the server and sends it to the printer directly. Where the server can reach the printer, it speaks raw ESC/POS over TCP. Where it cannot, it relays through PrintNode over plain HTTPS.

A printer that is offline, jammed or misconfigured never rolls back a completed order. The money has already been taken, so the failure and its reason are recorded on the order instead and a manager can reprint.

- Two backends. Raw ESC/POS over the network, or PrintNode when the server cannot see the shop. - Works on Odoo.sh. That is the main reason it exists. - The library is optional. python-escpos is not declared as a hard dependency, so the module installs everywhere. Without it the network backend reports itself unavailable and PrintNode keeps working. Comparable apps refuse to install at all. - A failed print never loses a sale. The order is saved regardless, carrying its print state and the failure reason. - Credentials stay on the server. The PrintNode key is restricted to point of sale managers and is never loaded into the till, so a cashier session cannot read it. - Configuration validated on save. A network printer without a host, or a PrintNode printer without credentials, is refused up front rather than failing at the counter. - Printer per register. Branches and counters print where they should, and printers carry a company.

Who it's for

Anyone running Odoo Point of Sale on Odoo.sh or hosted infrastructure, multi-branch retailers who need each counter printing to its own hardware, and operators who want a receipt to keep printing without a browser session holding the connection.