Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v19.0
License
Point
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
973 lines (Python / XML / JS)
Overview & Description
Point of Sale POS Print Spooler A print queue for the Point of Sale, with a documented agent API. Register each printer as a device, queue receipts instead of firing them at a browser dialog, retry whatever fails, and see exactly what printed and what did not â including on USB and Bluetooth printers a browser cannot reach. Odoo 19.0 Odoo 20 Community Enterprise Version 19.0.1.0.0 OPL-1 No IoT Box required 3 API endpoints to implement 5 Job states, all visible 76 Automated tests 0 Extra dependencies Module Overview Odoo can print a receipt three ways, and all three fail silently. The problem The browser print dialog, an IoT Box, or an Epson ePOS printer on the network. When any of them fails there is nothing in the database to look at â no job, no error, no log. Only a counter that goes up whether or not paper came out. And none of the three reaches a USB or Bluetooth printer, because a browser cannot open one. The approach Documents are queued as records, not printed directly. A small agent next to the printer polls Odoo for work over a documented JSON API, prints it, and reports back. Odoo never opens a connection to a printer â the agent always calls Odoo. That single decision is why USB printers, Bluetooth printers, printers on a private shop Wi-Fi and printers behind NAT all work with no firewall rule, port forward or static IP. What the three standard routes record when they fail Route Fails when What Odoo records Browser print dialog The cashier dismisses it, or the printer is asleep Nothing IoT Box The box is offline, or the cable is out Nothing Epson ePOS on the network The printer is off, on another VLAN, or DHCP moved it Nothing This module Anything at all A job, its state, its attempts and the agent's own error text Key Features A queue you can audit, a retry policy you can trust, and a protocol you can implement in an afternoon. Print Devices One record per printer A device registry under Point of Sale configuration, each with its own 256-bit token generated on creation. The token is the agent's only credential â there is no login to provision on a shop PC. Copy-ready poll URL The full URL to paste into an agent sits on the device form with a copy button. Setting up a printer is copy, paste, run. Regenerate a token instantly One button invalidates the old one immediately, for a machine that is lost, sold or re-imaged. The token itself is visible to managers only â cashiers never see it. Device kinds and routing Receipt, preparation, label or other. Bind a device to specific shops, or leave it open to all; limit a preparation printer to certain product categories. A kitchen printer is never sent receipts. Paper width, handled 58 mm or 80 mm â 32 or 48 characters per line. Odoo does the column arithmetic, because a thermal printer is a character device, not a page. Online, and provably so A live indicator from the last poll, searchable as a filter that agrees with the displayed value, plus queued and failed counters per device and a test page that proves the whole chain without touching an order. The Queue Every document is a record What, where, when and how it went â numbered from a sequence, so a job can be quoted in a support ticket rather than described. Five honest states Queued, Taken, Printed, Failed, Cancelled. When a shop says the receipt did not print, there is finally something to look at. Retry with a backoff Five seconds, fifteen, a minute, five minutes, fifteen â then left Failed for a human, with the agent's own error text on the record: "out of paper", "USB device not found". No double printing A job is claimed at poll time, so two agents pointed at one device cannot both print it. A crashed agent cannot strand work A job taken and never confirmed is handed back after two minutes, so the queue recovers itself rather than waiting for someone to notice. Priority, copies and cleanup A customer waiting at the till beats a label batch; one job can carry N copies; and printed or cancelled jobs older than a week are removed nightly while pending work is never touched. Receipts and the Agent API Queued automatically, never blocking A paid order puts its receipt in the queue on the sync path. A missing or misconfigured printer is logged and the order still syncs â printing must never cost you a sale. Rendered on the server Built from the order, not captured from the screen. An agent that was offline for ten minutes prints exactly the paper it would have printed at the till. A complete receipt Company header, VAT, reference, date, cashier, customer, lines, per-line discount, notes, subtotal, tax, total, payments, change and the configured footer â laid out to the paper width, with long product names handled at both widths. Three endpoints, flat JSON Poll for work, acknowledge results in a batch, or ping to report online without taking anything. Documented field by field, with explicit rules on what an agent may assume. Scoped, not merely authenticated A token can only take and acknowledge its own device's jobs, so a stolen shop-floor token cannot touch another printer's work. Batch sizes are capped server-side. Cross-platform by design HTTP and JSON only â anything from Python to a shell script with curl can implement it. The included reference agent is about sixty lines and runs on Windows, Linux, macOS and Android. Business Benefits What changes on the shop floor and in the support queue. "It didn't print" becomes answerable There is a record with a state, an attempt count and the reason, instead of a conversation about what someone remembers happening. Use the printers you already own USB and Bluetooth thermal printers work, which no standard route supports, so a shop is not forced into new network hardware. No network engineering The agent calls out to Odoo, so there is no firewall rule, no port forward and no static IP for a printer behind NAT or on shop Wi-Fi. No IoT Box, no Enterprise One dependency and no external Python packages. The hardware bill for reliable printing is a machine you already have on the counter. A blip stops being an incident The backoff absorbs a printer asleep, a cable knocked out or an agent restarting, without anyone at the counter noticing. Nothing is lost or duplicated Claim-at-poll prevents double prints and stale recovery prevents stranded ones â the two ways a print queue usually goes wrong. The sale always completes Printing is decoupled from the order, so a printer problem can never hold up the till. Multi-shop and multi-company ready Devices route per shop and per category, and both devices and jobs are isolated by company record rules. Scope â read this before you buy. This module is the Odoo half: the queue, the API, the payload generation and the back office. The agent that runs beside the printer is separate software. A complete reference agent is included and it works â it is what the end-to-end tests run against â but there is no packaged installer, Windows service wrapper, Android APK or tray icon. If you need those, build on the reference agent or use a client that speaks this protocol. Screenshots The device, the queue, and what happens when something fails. Screenshot placeholder A print device Kind, paper width, payload format and shop routing, with the agent section showing the poll URL and the online indicator. Screenshot placeholder The print queue Jobs grouped by device with their states and attempt counts, filtered to waiting work by default. Screenshot placeholder A failed job The attempt count, the agent's own error text, the exact payload that was sent, and the retry button. Screenshot placeholder Print jobs on an order The job count on a POS order and the Queue Receipt button for a reprint. Workflow How a receipt gets from a paid order onto paper. Step 1 â The order is paid On the sync path, the receipt is rendered on the server and a job is queued for every receipt printer of that shop. The same order re-sent does not print twice. Step 2 â The agent polls The agent beside the printer asks Odoo for work. Jobs handed out are marked Taken, so no other agent can claim them, and the device is stamped as seen. Step 3 â It prints and reports The agent sends the payload to the printer and acknowledges each job as printed or failed, with its own error text when it failed. Step 4 â Odoo reacts A failure is retried on the backoff until the device's allowance runs out; a job taken and never confirmed comes back after two minutes. Nothing is stranded and nothing prints twice. Getting a printer running Point of Sale → Configuration → Settings, pick your shop, turn on Print Spooler. Configuration → Print Devices → New. Name it, choose 58 mm or 80 mm, save. Copy the poll URL from the agent section of the device form. Run the agent on the machine next to the printer. Point it at the console first â it is the fastest way to prove the chain works before any hardware is involved. Press Queue Test Page on the device. It should print, the job should reach Printed, and the device should show Online. Configuration Two switches on the shop, and the device record itself. Per shop — Configuration → Settings Setting Default Print Spooler Off Queue Receipts Automatically On Turning off automatic receipts leaves printing entirely manual, driven by the Queue Receipt button on an order. Where things live Devices Point of Sale → Configuration → Print Devices Queue Point of Sale → Reporting → Print Queue Per order The Print Jobs button on a POS order The print device — Configuration → Print Devices Field What it does Default Device The printer's name, as it appears on jobs and in the queue. Required Type Receipt, Preparation, Label or Other â decides what is ever sent to it. Receipt Paper Width 58 mm or 80 mm, i.e. 32 or 48 characters per line. 80 mm Payload Format Plain text for a thermal printer, or HTML for an agent printing through the operating system. Text Points of Sale Which shops this device serves. Empty serves every shop. Empty Product Categories Limits a preparation printer to specific categories. Empty Device Token The agent's only credential. Manager-visible, regenerable, read-only. Generated Poll URL Read-only. The full URL to paste into an agent. Computed Max Attempts How many times a job is retried before it is left for a human. Per device Company Devices and their jobs are isolated by a company record rule. Current The token is the whole security model for an agent. It is visible to Point of Sale managers only, it can be regenerated at any time, and it scopes an agent to a single device â a token from one shop floor cannot take or acknowledge another printer's jobs. Technical Details For whoever has to run it, and whoever has to write the agent. Module Technical name pos_print_spooler_aura Version 19.0.1.0.0 Category Sales / Point of Sale Licence OPL-1 Dependencies point_of_sale External libraries None New models pos.print.device, pos.print.job Models extended pos.config, pos.order, res.config.settings Scheduled jobs Stale-job recovery and nightly cleanup of finished jobs Automated tests 76, including the API over real HTTP The agent API Call What it does poll Hands over the next jobs and stamps the device as seen. Batch size clamped server-side. ack Reports success or failure per job, batched into one call. ping Reports online without taking work â for startup checks and while a printer is unavailable. No Odoo login Public routes with the token in the URL. There is nothing to provision on a shop PC beyond the URL itself. Hostile input survived Unknown tokens, unknown job ids, garbage in the results array, a non-array where an array was expected and absurd batch sizes are all handled without a server error. A stable contract Three endpoints and flat JSON, documented field by field, with explicit rules about what an agent may and may not assume. Test coverage Queue mechanics Claiming, state transitions, priority, copies and the cancel rules. Failure paths The backoff, the attempt allowance, stale recovery, and manual retry after a definitive failure. Receipt rendering Both paper widths, full content, and a 120-character product name that must not break the layout. The API for real Driven over actual HTTP, including the hostile-input cases and the device-scoping rule. Compatibility Where this module runs, and what it can print to. Item Supported Notes Odoo 19.0 Yes Built and tested for 19.0. Odoo 18.0 and earlier Not in this build Contact support if you need a backport. On-Premise Yes Drop the module in your addons path and update the app list. Odoo.sh Yes Add it to your repository and let the build install it. Odoo Online (SaaS) No Odoo Online does not allow custom modules to be installed. Agent platforms Windows · Linux · macOS · Android The reference agent needs only Python and one HTTP library; Android runs it under Termux. USB and Bluetooth printers Yes The whole reason the agent exists â no browser can open one. Printers behind NAT or on shop Wi-Fi Yes The agent calls out, so no inbound rule, port forward or static IP is needed. IoT Box Not required This module is an alternative to it, not a companion. Packaged agent installer Not included A working reference agent is shipped; a signed installer, service wrapper or APK is not. Multi-company Yes Devices and jobs are isolated by record rules. Supported Editions The module depends on point_of_sale only, so both editions are covered. Community Edition Fully supported Every feature works on Community, with no IoT Box and no Enterprise subscription involved anywhere in the chain. Enterprise Edition Fully supported Same behaviour on Enterprise, and it can run alongside an existing IoT Box setup rather than replacing it outright. Installation A standard module install, then one agent per printer. Download the module and copy the pos_print_spooler_aura folder into your Odoo addons directory. Restart the Odoo service so the new addon is picked up. Enable developer mode, then go to Apps and choose Update Apps List. Search for POS Print Spooler, remove the Apps filter if needed, and click Install. Turn on Print Spooler for the shop and create a device under Configuration → Print Devices. Install the agent on the machine next to the printer, give it the poll URL, and print to the console first to prove the chain. Press Queue Test Page and confirm the job reaches Printed and the device shows Online. The agent protocol is documented in full. The module ships an endpoint-by-endpoint specification and a working reference agent of about sixty lines, so you can start from it or write your own in any language that can make an HTTP request. Frequently Asked Questions What buyers ask before installing, answered without hedging. Yes â an agent runs on the machine next to the printer, and that is what makes USB and Bluetooth printing possible at all. This module is the Odoo half: the queue, the API, the payload generation and the back office. A complete working reference agent is included, about sixty lines, but there is no packaged installer, service wrapper or APK. No. This is an alternative route, not a companion to one. It needs no IoT Box, no Enterprise subscription and no external Python packages â but it can coexist with an existing IoT Box setup if you are migrating gradually. Yes, and that is the point of the design. Odoo never opens a connection to a printer â the agent always calls Odoo. So there is no inbound firewall rule, no port forward and no static IP to arrange, wherever the printer sits. The job waits in the queue and prints when the agent comes back. Because the receipt is rendered on the server at the time of the sale, a job printed ten minutes later produces exactly the paper it would have produced at the till. No. A missing or misconfigured printer is logged and the order still syncs. Printing is deliberately decoupled from the sale, so the queue can never hold up the till. Two protections cover it. An order the Point of Sale re-sends does not queue a second job, and jobs are claimed at poll time so two agents pointed at the same device cannot both take one. A job that was taken and never confirmed is handed back to the queue after two minutes, so a crashed or killed agent cannot strand work. When it restarts, it picks the job up again. The token is 256-bit, visible to Point of Sale managers only, and regenerable in one click. It is also scoped rather than merely authenticated: it can take and acknowledge only its own device's jobs, so a token lifted from a shop floor cannot touch another printer's work or read anything else in the database. Serve Odoo over HTTPS, as you would anyway. Yes. A device has a kind â receipt, preparation, label or other â and can be bound to particular shops and particular product categories, so a kitchen printer only ever receives what belongs to it and never a customer receipt. No. Printed and cancelled jobs older than a week are removed nightly, while anything still pending is never touched. Batch sizes are also capped server-side, so a misbehaving agent cannot drain the table. Changelog Release history for Odoo 19.0. Version 19.0.1.0.0 Initial release Print device registry with per-device tokens, copy-ready poll URLs, online indicators, live counters and a test page. A print queue with five states, numbering from a sequence, priority, copies, payload inspection and origin links back to the order. Retry with backoff, a per-device attempt allowance, stale-job recovery, manual retry and nightly cleanup of finished jobs. Automatic receipt queueing on payment, rendered on the server at both paper widths, idempotent and never blocking a sale. A documented three-endpoint agent API with device scoping, capped batches and hostile-input handling. Security: manager-only tokens, access rights for cashiers and managers, and multi-company record rules on devices and jobs. Documentation: agent protocol specification, a reference agent, a user guide and a technical guide. 76 automated tests, including the agent API driven over real HTTP. Support Written and maintained by Aura Odoo Tech. Email Questions, problems or a feature you need â write to us directly. odooaura@gmail.com Website More Odoo modules, documentation and customisation services. www.auraodoo.tech Included Free installation help, bug fixes and compatibility updates for the Odoo 19.0 release line. Before you write in: the module ships a user guide, a technical guide, the full agent protocol specification and a working reference agent. Most setup questions and every question about writing an agent are answered there. POS Print Spooler Odoo 19.0 · pos_print_spooler_aura · depends on point_of_sale only Odoo 19.0 19.0.1.0.0 OPL-1 Community & Enterprise Copyright 2021-2026 Aura Odoo Tech. All rights reserved.
Key Capabilities & Features
- "It didn't print" becomes answerable There is a record with a state, an attempt count and the reason, instead of a conversation about what someone remembers happening.
- Use the printers you already own USB and Bluetooth thermal printers work, which no standard route supports, so a shop is not forced into new network hardware.
- No network engineering The agent calls out to Odoo, so there is no firewall rule, no port forward and no static IP for a printer behind NAT or on shop Wi-Fi.
- No IoT Box, no Enterprise One dependency and no external Python packages. The hardware bill for reliable printing is a machine you already have on the counter.
- A blip stops being an incident The backoff absorbs a printer asleep, a cable knocked out or an agent restarting, without anyone at the counter noticing.
- Nothing is lost or duplicated Claim-at-poll prevents double prints and stale recovery prevents stranded ones â the two ways a print queue usually goes wrong.
- The sale always completes Printing is decoupled from the order, so a printer problem can never hold up the till.
- Multi-shop and multi-company ready Devices route per shop and per category, and both devices and jobs are isolated by company record rules.
- Point of Sale → Configuration → Settings, pick your shop, turn on Print Spooler.
- Configuration → Print Devices → New. Name it, choose 58 mm or 80 mm, save.
- Copy the poll URL from the agent section of the device form.
- Run the agent on the machine next to the printer. Point it at the console first â it is the fastest way to prove the chain works before any hardware is involved.
- Press Queue Test Page on the device. It should print, the job should reach Printed, and the device should show Online.
- No Odoo login Public routes with the token in the URL. There is nothing to provision on a shop PC beyond the URL itself.
- Hostile input survived Unknown tokens, unknown job ids, garbage in the results array, a non-array where an array was expected and absurd batch sizes are all handled without a server error.
- A stable contract Three endpoints and flat JSON, documented field by field, with explicit rules about what an agent may and may not assume.
- Download the module and copy the pos_print_spooler_aura folder into your Odoo addons directory.
- Restart the Odoo service so the new addon is picked up.
- Enable developer mode, then go to Apps and choose Update Apps List.
- Search for POS Print Spooler, remove the Apps filter if needed, and click Install.
- Turn on Print Spooler for the shop and create a device under Configuration → Print Devices.
- Install the agent on the machine next to the printer, give it the poll URL, and print to the console first to prove the chain.
- Press Queue Test Page and confirm the job reaches Printed and the device shows Online.
- Print device registry with per-device tokens, copy-ready poll URLs, online indicators, live counters and a test page.
- A print queue with five states, numbering from a sequence, priority, copies, payload inspection and origin links back to the order.
- Retry with backoff, a per-device attempt allowance, stale-job recovery, manual retry and nightly cleanup of finished jobs.
- Automatic receipt queueing on payment, rendered on the server at both paper widths, idempotent and never blocking a sale.
- A documented three-endpoint agent API with device scoping, capped batches and hostile-input handling.
- Security: manager-only tokens, access rights for cashiers and managers, and multi-company record rules on devices and jobs.
- Documentation: agent protocol specification, a reference agent, a user guide and a technical guide.
- 76 automated tests, including the agent API driven over real HTTP.
- 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.
Screenshots & Previews
1 image availableExpand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.