Skip to Content

Odoo Direct Print 2.0

by
Odoo

$ 358.53

In-App Purchases
v 19.0 Third Party 9
Live Preview
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Versions 17.0 18.0 19.0
OrbitPDF
OrbitPDF
Printing platform for Odoo operations
Contact Us
odoo@sveltware.com
Free Odoo 20 Upgrade
In response to feedback from our early customers, we've decided to offer a free upgrade to Odoo 20 for enterprise customers. Please get in touch to register and claim this offer from us.
By Sveltware Solutions

Every document on the right printer. Instantly.

OrbitPDF Direct Print turns any computer on your network into a shared print station and wires it straight into Odoo. Delivery slips print themselves on validation, labels come out at the receiving desk, receipts fire at the counter, and every job is tracked from click to paper. Built on the open QZ Tray standard: no IoT Box, no cloud relay, no monthly fees. Nothing ever leaves your local network.

No Cloud Relay No IoT Box No Subscription Bespoke POS GDPR: No Third Party Industry-Standard Adapter
Why this is different
All six are testable before you pay, on your own printer, under a 30-day guarantee. They trace to one fact: we built the whole chain, from the rendering engines to the design studio to the delivery layer. No answer here waits on someone else's roadmap.
Do I sit and wait?
5–15× faster, own the engine.
We tuned our render engines down to the metal, so your template prints straight to every standard in use today.
Print from where I work?
One click, anywhere in Odoo.
Reports, labels, even files in the chatter. From a desktop, or a phone in the yard.
With the printers I own?
If your OS sees it, it prints.
Office printers print like they always did. Receipt and label printers we talk to directly. Nothing new to buy.
Can it print itself?
24+ scenarios, one click to live.
Turn one on and it simply runs. Underneath sits a normal Odoo automation rule your admin can open.
And on a bad day?
No duplicates. Nothing lost.
A jam never prints anything twice. A job with no printer waits for a person. Everything stays on record.
The real cost?
One purchase. The last bill.
Next to a cloud plan, it pays for itself in 2 to 16 months. The math is lower on this page.
Try Before You Buy
This demo prints on your printer: test 100% before you buy.
The print bridge runs on your side of the wire, so our hosted database can drive the printer sitting next to you. Prove the whole flow, on your hardware and your labels, before you buy anything.
1 Install QZ Tray 2 Open the demo 3 Printer Manager · Set up trust
https://orbitpdf.sveltware.com/odoo/platoin
Click to select, copy into a new tab. The test page comes out of the printer next to you.

# A Print Server Built Into Odoo

Every document takes the same detour today: download the PDF, open it, pick a printer, click print, walk back. Count those seconds. Multiply by every delivery slip, label, and invoice you print this week.

OrbitPDF deletes the detour. Documents print themselves, land on the right printer, and leave a record you can show. One licence, once. No relay in the middle. No bill that grows with your page count.

Three questions worth asking any print vendor
1. Where does my delivery slip sit while it waits?
2. Who else can open it there?
3. How long is that copy kept?
We have no answers, because there is no copy. Unplug the internet and print. If paper comes out, nothing was leaving.
Where a Print Job Lives
Your Odoo
Click or rule → Which printer → Job on record
↓  localhost
The machine with the printer
QZ Tray → Paper
The same page, through a cloud relay
Your Odoo → the internet → their server → the internet → their agent → Paper
Two trips out of the building to reach the printer beside you. That server is what a subscription pays for.
Built the way Odoo is built
01 · A proven open standard
The print bridge is QZ Tray, open-source and industry-proven: a decade of printing, nothing else. Your IT can audit every line, and commercial support exists when you want it.
02 · Native automation rules
Print Scenarios generate standard Odoo Automation Rules. Enable one and you get a plain, editable rule, not a black box. Your admins already know how to extend it.
03 · Jobs, not fire-and-forget
Every print is a job with a lifecycle: queued, claimed, done, failed, or held for a human. Paper jams and offline stations are handled, never silently swallowed.
As wide as your OS
Every printer the operating system can see
No compatibility list to check, because the list is your OS. Office lasers print through the driver; receipt and label hardware gets spoken to in its own language, driverless:
PDF · any driver printer ESC/POS · receipts ZPL · Zebra EPL · Eltron SBPL · SATO PGL · Printronix PDF rastered to thermal · no driver at all
USB · network · WiFi · Bluetooth. Windows, macOS, and Linux stations, on Intel or ARM, down to a Raspberry Pi.
As short as your LAN
The shortest path a document can take
Click, LAN, paper. A cloud relay adds two internet trips to every single document; OrbitPDF adds zero, so speed scales with your network, not with someone's server load. Large batches ship in slices, and every job is signed before it travels.
Pair it with OrbitPDF Engine and the rendering itself is benchmarked at 5–15× wkhtmltopdf: the whole pipeline moves at hardware speed.
Both claims are yours to torture in the live demo above. Pull the network cable mid-batch and watch every job requeue without a duplicate, on your own printer.

# Three Ways to Print From Odoo

You have tried more than one way to print from Odoo, yet you are still reading. That usually means each one solved a slice and stopped: cloud relays brought zero-touch convenience, agent apps brought local control at a one-time price. Both were milestones, both partial. OrbitPDF covers the whole path in one system: it renders on a self-built engine that is dramatically faster than the legacy core both older tools still ship, keeps the local-first economics, replaces the closed agent with an open standard, and adds the layer both generations skipped. An operational one that tracks every job to paper. Compare the three architectures dimension by dimension:

The adapter question nobody asks out loud
Every direct-print tool runs on one desktop bridge, and that bridge is where your trust actually lives.
Odoo The desktop bridge Your printers
The bridge you can look up, before you trust it
10 years
since 2016, still active this month
~1,500
public issues resolved, on real printers
40,000
lines your IT can read, open source
0
private agents we ask you to trust
We did not invent an agent and ask for your trust. We print through the one bridge this industry already audits, and every number here is public: read the code, read the issue history, see who runs it at qz.io.
A vendor's companion app
✕  Closed source, a black box
✕  A socket on every desk
✕  One vendor's side project
QZ Tray, OrbitPDF's bridge
✓  Open source, auditable
✓  A decade of public scrutiny
✓  Prints only what Odoo signed
Dimension Cloud Print Relays Proprietary Agent Apps OrbitPDF Direct Print 2.0
What makes it 2.0: the layer cloud relays and agent apps never built
Printer Management The Vendor's Cloud Console The Companion App's Screens Industrial Manager, Inside Odoo
Rendering Core wkhtmltopdf (legacy) wkhtmltopdf (legacy) Native PlutoPrint Engine (5–15×)
Print Automation Vendor Rule Engine Vendor Rule Engine Native Odoo Automation Rules
When a Print Fails Fire and Forget Fire and Forget Retry + Held for a Human
Audit Trail On the Provider's Side App-dependent Full Job Ledger in Odoo
The bridge you can trust
Print Client Managed Cloud Agent Closed Vendor App Open Standard (QZ Tray)
Request Security Account API Key Vendor-defined PKI-signed per Job
Bridge Pedigree Provider's Cloud Agent One Vendor's Companion App Decade-mature, Publicly Audited
Local-first economics & reach
Cost Over Time Subscription + Quotas One-time Purchase One-time + Open-Source Bridge
Fleet Model Per-account Mapping Per-device Setup Shared Print Stations
Phones & Tablets Via Cloud Account Companion App Required Any Browser, No App
Document Path Vendor Cloud (WAN) Local Network LAN Only, Zero Egress
Internet Outage Printing Stops Printing Continues Continues + Wake Queue
Staying Reachable Cloud-Mapped Account Pinned to a Fixed IP Zero Network Setup

# The Payback Math

Everything above is a story until it is a number. Put the public price lists side by side and the answer writes itself:

Four lines, one answer
Your relay plan, per its own price list €8 to €72 / month
Three years of that €288 to €2,592
The module it rides on + €199
Direct Print 2.0, Once = €320
The bills stop. Break-even lands between month 2 and month 16; every month after, printing costs nothing.
And the €130 agent app? Cheapest on paper only: the dashed bar in the chart is every gap your warehouse discovers on first contact, quoted back to you as paid work, and every hour the floor stands still waiting on a ticket queue. Nobody prints you that invoice; you pay it anyway.
Every figure above comes from a public price list, no assumptions. The live demo is where you verify the rest.
Three years, list prices
Cumulative spend over 36 months, in euros:
Proprietary agent app
≈ €130 + tickets = ?
OrbitPDF Direct Print, once
€320 · flat forever
Cloud relay · smallest: €199 module + €8/month quota
€487
Cloud relay · premium: €199 module + €72/month quota
€2,791
Everything at list prices, in euros; the $149 agent app converted at ≈ €130. Relay totals are the module plus its required print-quota subscription.
And the scenarios driving these numbers are scoped with you before you buy; support comes from the engineers who built the module, not a ticket queue.
The bill that never arrives
A ten-station warehouse on a cloud relay pays every month, forever, and again for every document past the quota. OrbitPDF is a one-time purchase on top of open-source infrastructure that runs entirely on your hardware. The difference compounds every year you operate.
The failure nobody notices
With fire-and-forget printing, an offline station means labels that simply never appear, and nobody knows until a shipment is late. OrbitPDF queues the job, alerts an admin, and prints the backlog the moment the station wakes up.
24+
ready-made print scenarios
5
raw printer languages, driverless
3
steps from install to first page
0
monthly fees or print quotas
Pillar 1 · Routing
Not just the back office
The counter prints on the same rail
A receipt goes from the cashier’s own screen to the printer an arm’s length away, and the cash drawer opens through the same cable. Thermal printers get a driverless ESC/POS raster. A POS invoice is an Odoo report, so it takes the rail every other report takes. Nothing is rendered on your server while a customer stands there.
Receipts Cash drawer ESC/POS, no driver Invoices on the same rail
The POS piece is a satellite module: included with your licence, handed over in a conversation so it fits your counter. Ask before you buy: odoo@sveltware.com.
At the till
Receipt Counter_TM88
Cash drawer same printer
Server hop none
The cashier’s browser talks to the printer beside it.

# Print From Anywhere, Land Exactly Right

Print Stations
Any machine running QZ Tray becomes a shared print station in one click. Its printers serve the whole team: a phone in the yard prints to the desk in the office.
odoo-warehouse STATION
Printer Rules That Learn
Quotes to the office laser, labels to the label printer, per user. Tick Remember when OrbitPDF asks you to pick, and the rule writes itself. No settings screen to maintain.
PDF Quote PDF_Printer
Where Will It Print?
The routing inspector answers before you print: pick any document, see the printer it lands on and which setting decided that. Wrong-printer surprises end here.
Office_Laser via My rule for this report
Not just reports
Print any attachment, straight from the chatter
A Direct print button sits on every file attached to a record, right next to Download. A carrier shipping label from your delivery connector, an e-signed PDF, an uploaded ZPL file: one click sends the exact bytes to the right printer, routed, held, and audited like any other job. The label prints at the packing desk without anyone opening a download.
Carrier shipping labels Signed PDFs ZPL files Images
Attachment in the chatter
PDF
ShippingLabel_DHL.pdf
91 KB
Download Direct print Delete
Direct print (highlighted) lands next to Download and Delete.
Pillar 2 · Automation

# The Busywork Prints Itself

A Catalog of One-Click Scenarios
Curated automations for the documents operations actually print, each one click from live. These ship in the box:
Delivery Slip on Transfer validation Lot/Serial label on creation Package label on Put in Pack Invoice on posting Receipt Operations on validation Sales Order on confirmation Purchase Order on confirmation Production Order on confirmation Backorder document on creation + your own, built in a form
Native Underneath, Editable Forever
Enabling a scenario generates a standard Odoo Automation Rule, not a black box. Your admins can open it, extend it, and filter it like any rule they already know.
Rehearse Before You Trust
The test-fire button runs the exact production path against the newest matching record. The test job routes, holds, and gets remembered like a real one, so your test prints are the setup.
Pillar 3 · Operations

# Run It Like Infrastructure

A Real Job Lifecycle, With Receipts
Every print is a job: queued, claimed by exactly one machine, then done, failed, or held for a human. The audit records the physical device each sheet came out of, and any job reprints in one click.
21:39 DONE Quotation / Order: Office_Laser
16:20 QUEUED Package Barcode: Warehouse_Desk
14:05 FAILED PRO-FORMA Invoice: Office_Laser
13:31 DONE Lot/Serial Number: Zebra_ZT411
11:52 HELD Delivery Slip: pick a printer
11:47 DONE Receipt Operations: Warehouse_Desk
10:15 DONE PDF Quote: PDF_Printer
09:02 DONE Delivery Slip: Packing_Desk
Held, Never Lost
An unroutable job parks for a human instead of failing silently, pinned with an alert until someone decides. Admins also get a badge when a station goes dark with work queued.
Trusted Printing, PKI-Signed
Your Odoo signs every print request with its own keypair; QZ Tray verifies and prints without nagging prompts. Certificates are managed from the Printer Manager.
QZ Tray · connected · Trusted
Receipt, Label & Page Printers
PDF reports render through the printer driver. Raw languages go straight to the metal, driverless, and OrbitPDF detects each printer's language to pick the right test page by itself.
ESC/POS ZPL EPL SBPL PGL PDF
Multi-Company, Group-Fenced
Stations, printers, scenarios, and jobs respect company walls out of the box, with shared infrastructure when one print room serves every entity. Station access narrows to the user groups you choose, enforced when the job is queued.
From click to paper
Every step runs inside your own network, and lands in the audit trail.
1 · Odoo decides
A user hits Print, or an enabled scenario fires on its own. Routing rules resolve the target printer.
2 · A job is born
Queued, PKI-signed, and recorded: document, requester, target device, all frozen for the audit.
3 · A station claims it
Exactly one machine wins the claim, over your LAN. Asleep? The job waits and prints on wake.
4 · Paper, proven
QZ Tray verifies the signature and prints. The job closes with the exact physical device on record.
A Tuesday at the warehouse
What "reliable" actually means, hour by hour
09:02
A packer validates transfer WH/OUT/00042 on a scanner tablet. The delivery slip is printing at the packing desk before they look up. Nobody touched a print dialog.
11:47
The label printer jams mid-batch. The stale job requeues automatically and no duplicate labels come out; the audit knows which sheets were already sent.
11:52
A printer nobody re-plugged after cleaning takes a job that cannot route. Instead of vanishing, the job parks as held and pins itself at the top of every admin's manager with an alert.
11:55
An admin resolves it from their phone, picks the spare printer, and ticks Remember. The backlog prints. And the routing rule that failed has just taught itself the fix.
17:00
End of day, the job history reads like a flight recorder: every document, every decision, every physical device. That is the difference between a print button and print infrastructure.

# One Family, The Whole Path to Paper

Printing is really two problems wearing one name: building the document and getting it onto paper. Labels quietly add a third, speaking each printer's own language. Most tools solve one slice and leave you to duct-tape the rest. The OrbitPDF family covers the whole path with independent modules that snap together, one design language, one support inbox, and two rendering engines of our own: one tuned for paged documents, one born for thermal labels.

Three layers, one pipeline
1 · Rendering
Two engines build the document
QWeb reports become PDF at native speed on the PlutoPrint core; labels render straight to their printer's own language on the Skalar engine.
Powered by OrbitPDF Fast Report & Skalar
2 · Orchestration
Odoo decides and remembers
Routing rules, the job queue, retries, held decisions, and the audit ledger live inside your database, editable like anything else in Odoo.
Powered by OrbitPDF Direct Print
3 · Execution
Stations put it on paper
PKI-verified QZ Tray stations claim jobs over your LAN and hand the bytes to physical printers. Nothing crosses the internet.
Powered by OrbitPDF Direct Print
The Label Branch · Skalar Design Studio
Design once. Every printer agrees.
The strongest design studio on this market today: one template deploys to PDF, ZPL, TSPL, EPL, and ESC/POS, with typography that survives thermal printing, diacritics and all. Change the layout once, and every printer in the building prints the same label.
PDF ZPL TSPL EPL ESC/POS
Not on the store: the studio arrives through a conversation. Write to odoo@sveltware.com.
The label template gallery: thirty-two ready templates, from Avery address sheets and DHL shipping labels to GS1 pallets, Amazon FBA, EU shelf tags and hangtags, each with its size, print density, sheet layout, and a one-click test print
Thirty-two templates ship in the box, Avery sheets to DHL to GS1, and every one test-prints in a click.
The Document Engine
OrbitPDF Engine
The next-generation HTML-to-PDF engine on PlutoPrint. Production-grade rendering, watermarking built in, 5–15× faster than wkhtmltopdf.
View on Odoo Apps
The Drop-in Upgrade
OrbitPDF Fast Report
The lean path to faster reports: replaces wkhtmltopdf in production with pre-calibrated patches for every standard Odoo layout. Install and print.
View on Odoo Apps
The Delivery Layer You are here
OrbitPDF Direct Print
Print stations, one-click automations, and the full job audit trail. Takes any document, from any engine, and puts it on the right printer instantly.
Independent by design
No module in the family requires another; each one earns its place alone. Direct Print delivers documents from any rendering engine, including stock wkhtmltopdf, and the engines render for any delivery path, including plain downloads. Install the pieces you need today and add the rest when the friction tells you to.

Can I see it working with my own printer before buying?

Yes, and that is the point of our live demo. Because the print bridge runs on your machine, the hosted demo database can print on the printer sitting next to you: install QZ Tray, open the demo's Printer Manager, walk the short setup card, and press Test. In a few minutes you know exactly how it behaves with your hardware, your labels, and your network, before spending anything. The demo address is at the top of this page.

Very likely, and it is worth settling before you buy. Every scenario is a print action combined with a filter, built on native Odoo automation rules, so most requests are a small configuration rather than custom development. Tell us the workflow you need before purchasing: we confirm together whether it fits, and any scenario we agree is in scope, we add during your first three months of support. If something needs deeper work, we say so plainly up front, never after the sale.

Your purchase includes three months of support directly from the author, from the date of purchase: installation help, configuration questions, fixes for any genuine defect, and the print scenarios we agree are in scope. Refunds go beyond what the store asks of us, a 30-day money-back guarantee, one email and no forms. Fixes within your Odoo 19 version ride along for the same period. Custom development beyond the module's scope, and upgrades to a future major Odoo version, are separate work. We always say which is whichbefore any of it starts.

Then you get your money back. Every purchase carries a 30-day guarantee: run it on your real printers, your real labels, and your real network load, and if OrbitPDF does not do what this page says and we cannot make it right, we refund the purchase in full. One email, no forms. We can afford this because the live demo lets you verify the hard parts before you spend anything.

No hardware beyond the computers you already have. Any machine that can see your printers becomes a print station. Documents travel over your local network only, so printing keeps working even when the internet connection does not, and your business documents never pass through anyone's cloud.

QZ Tray is an open-source print bridge for Windows, macOS, and Linux that talks to every printer the operating system can see. It has done nothing but printing for over a decade, is widely adopted across industries, and its source is open for your IT to audit, so the component that touches your printers is never a black box. The open-source edition covers everything OrbitPDF uses: we integrate against its official signing contract, so the connection is trusted and prompt-free. QZ also offers commercial support directly, so a dedicated team stands behind the bridge whenever your organization wants one. OrbitPDF works the same either way.

Every printer your operating system can print to: office lasers, thermal receipt printers, and label printers over USB, network, WiFi, or Bluetooth. Any QWeb PDF report prints through the driver pipeline. Raw formats print driverless: ESC/POS for receipts, ZPL, EPL, SBPL, and PGL for labels. Pre-rendered attachments (PDF, ZPL, images) print too.

Yes to all three. OrbitPDF is a standard Odoo 19 module with no external service dependencies. Community and Enterprise are both supported; on Odoo.sh and any hosted setup, the server side installs normally while QZ Tray runs on the machines that do the printing, inside your own network.

Direct Print depends on three standard Odoo modules (mail, base_setup, base_automation) and a small set of Sveltware frontend libraries shared across our suite. The libraries are UI infrastructure only: no new database tables, no schema changes, no background jobs, and nothing that touches business data. The full list is open in the manifest for your IT to review. Nothing alters your schema. Uninstalling leaves the database exactly as it was.

Yes, that is exactly what print stations are for. The phone does not need to see the printer; it only needs Odoo. A worker validates a transfer on a tablet, the job routes to the warehouse station, and the label prints at the packing desk. If the station machine is asleep, the job waits and prints the moment it wakes.

A station is an ordinary Odoo session: the machine that owns the printers stays signed in to your database in a browser, with QZ Tray running beside it. There is no extra agent to install or babysit. If the browser closes or the machine reboots, nothing is lost: jobs for that station queue in Odoo, admins see it go dark, and the backlog prints the moment the session is back. Most teams pin the station as a browser tab that opens with the machine, and the Printer Manager shows its live presence at a glance.

No. There is no fixed address to keep alive and no network settings to maintain: the print bridge runs on the same machine as the printer, so a reboot or a new router IP changes nothing. The connection re-establishes itself, and any jobs that queued while a station was down print the moment it comes back.

Every print is a job record with its full story: who requested it, which document, which printer and station, what happened, and when. Failures show up with their error, jobs that lost their machine are retried or held for a decision, and admins get an attention badge when a station goes dark with work queued. Reprint any job in one click; the audit keeps both walks.

Yes. The print bridge runs on Windows, macOS, and Linux, on Intel and ARM alike, so a Raspberry Pi wired to your label or receipt printer makes a solid, low-cost station. Register it once and it serves the whole team like any other machine.

No. Each license covers a single project or database, with unlimited stations, printers, and users inside it. If you run several Odoo databases or deploy for several clients, you need a separate purchase for each one. Reselling or redistributing the module is not permitted.

# Who We Are

Sveltware Solutions is a specialist studio building premium extensions for the Odoo backend. We work close to the metal, its OwlJS layer, rendering pipeline, and extension points, so we can change how Odoo feels without touching what keeps it stable: we build on the framework's own hooks, never override its internals.

Not one add-on but a connected ecosystem, themes, list and kanban tools, faceted search, printing, activity, and AI, under one design language. Every module is plug-and-play: zero config, no schema changes, clean uninstall, and proven on production-scale data.

It is built to be looked at, too: Apple-grade spacing, a flat-premium finish, strict WCAG 2.2. Our standard is effectiveness first, every module earns its place by making real work faster, and so does our support: you write to the engineers who built it, not a ticket queue.

Sveltware Logo
Sveltware Solutions
Crafting pixel-perfect, zero-configuration enhancements for Odoo environments.

# How We Build

Six standards every Sveltware module must pass before it ships:

01 · Architecture
Extend, Never Override
We hook into Odoo's official extension points instead of monkey-patching internals. Standard views, workflows, and other modules keep working exactly as before.
02 · Data Safety
Fully Reversible
No schema rewrites, no data migration, no leftovers. Removing one of our modules returns your database to exactly the state it was in before.
03 · Onboarding
Zero Configuration
Install and use. Our modules read your existing setup, attributes, views, and access rights, instead of asking you to rebuild it in a settings screen.
04 · Performance
Fast on Real Data
We test against large, production-shaped databases, not demo data. Indexed domains, client-side caching, and lazy loading are the default, not an afterthought.
05 · Design
Native and Accessible
Every interface follows Odoo's native design language and meets WCAG 2.2: full keyboard support, real focus states, and contrast that holds up in light and dark mode.
06 · Longevity
Maintained Across Versions
We track Odoo's release cycle and update our suite for each major version, so upgrading Odoo never means abandoning the tools your team relies on.

# The Sveltware App Suite

One family of modules, designed to work seamlessly together. Click any app to open it on the Odoo Apps store in a new tab.

Flagship · Backend Themes
Omux & Lavend · Backend with Agentic AI
A complete redesign of the Odoo backend, available as Omux or Lavend, each running on both Community and Enterprise: dual sidebars, custom presets, hybrid start menus, dark/light modes, and WCAG 2.2 compliance, with agentic AI woven in.
Omux Backend Lavend Backend
Adaptive Split View
View on Odoo Apps
Adaptive Product Hub
View on Odoo Apps
Adaptive List View
View on Odoo Apps
Approval Gates
View on Odoo Apps
OrbitPDF Engine
View on Odoo Apps
Activity Management 360
View on Odoo Apps
Multi-Website Catalog Control
View on Odoo Apps
Website Theme Sitewave
View on Odoo Apps
See the whole suite
Browse every Sveltware module and theme on the Odoo Apps store, always up to date.
Browse all apps
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 6078
Technical Name orbitpdf_print
LicenseSee License tab
Websitehttps://www.linkedin.com/in/sveltware 
Sveltware Business License v1.1

Copyright © 2026 Sveltware Solutions ("the Authors",
including their successors and assigns)
All rights reserved.

------------------------------------------------------------------------

1. Who may buy

This License is for business use, including sole traders and
freelancers. For personal, non-business use, write to us first;
personal arrangements are made by direct written agreement only.

2. What you may do

One license covers one production Odoo database, operated for one end
customer (the business the deployment serves), with unlimited users on
that database. Staging, testing, development, and non-concurrent
disaster-recovery copies of that database are included at no extra
charge, as long as they stay within the end customer's organization
and its contractors. Each additional production database or end
customer requires an additional license.

This License is perpetual for the purchased version. It is not
transferable, except once, in whole, to a legal successor of the
licensed deployment (merger, acquisition, or restructuring), with
written notice to the Authors.

You may modify the Software for your licensed deployment, and build
your own modules that import, inherit, or extend it. You may not copy
its source code into your own products, and you may not distribute
modules whose primary purpose is to re-expose or replicate the
Software's features.

3. What you may not do

Publish, resell, sublicense, or redistribute the Software, in original
or modified form, or operate it for anyone who does not hold their own
license, including any SaaS or multi-tenant setup. Installing or
hosting the instance of an end customer who holds their own license is
fine. Implementers and agencies who want to offer the Software to
their clients as part of their services must have a written agreement
with the Authors first. Any other use requires a separate written
agreement with the Authors.

This License ends automatically if you breach it. Any use or
distribution after that is copyright infringement.

4. Integration deliverables

Custom integrations the Authors build and deliver to you are part of
the Software under this License, unless the project agreement says
otherwise. This section does not restrict modules you build yourself.

5. No warranty

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. TO THE
MAXIMUM EXTENT PERMITTED BY LAW, THE AUTHORS' TOTAL LIABILITY SHALL
NOT EXCEED THE AMOUNT PAID FOR THIS LICENSE.

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.
Great implementation
by
Liz Yokum
on 8/6/26, 7:31 PM
The printer manager is what stands out. Printers, stations, which ones are online, test prints, certificates, it's all in one screen. We've known QZ Tray for years and nobody has built printer management on top of it like this before. It picked up every printer straight away, nothing missing.

One thing to know, a print station is a browser session that stays logged in, not a background service. Jobs wait if it goes offline so nothing gets lost, but worth knowing before you set it up.

The author asked us to be his first reviewers. Everything above is what we actually got. Recommended.

Very happy with my order!
by
Kutlu AC
on 7/27/26, 9:29 PM

One of the better direct printing app out there

by
Kang M.
on 7/24/26, 10:47 AM

Hi, Module looks great, planning to try the demo this week. One thing I need to know before getting too excited: how well does the PlutoPrint engine handle Korean text? Most of our reports are in Hangul and wkhtmltopdf was always a headache with CJK fonts. Also curious about Zebra labels, can we get Hangul out through raw ZPL or should we just use the PDF-to-thermal raster mode for that? Thanks!

by
Peter Nguyen
on 7/24/26, 11:16 AM Author

Hi,

Two questions, two answers below.

1. Korean text in PlutoPrint reports

Short answer: yes, Hangul renders correctly.

  • wkhtmltopdf's CJK problems came from its outdated WebKit build. PlutoPrint uses the same modern text stack as browsers: FreeType, HarfBuzz, ICU. Hangul shaping, wrapping and line-breaking follow the same rules your browser applies.
  • One requirement: a Korean font installed on the Odoo server. Noto Sans KR is the usual choice, a one-package install.
  • Fonts are embedded and subset into the PDF, so output is identical on every machine that opens it.
  • Verification: when you run the demo this week, paste real Hangul into a report. That is the honest test.

2. Hangul on Zebra labels: raw ZPL or raster?

Short answer: use PDF-to-raster mode. Raw ZPL works only if your printer has a Korean font on board.

  • Raster mode: the server renders the label with your Korean fonts, the printer receives pixels. No printer-side font setup, what you see is exactly what prints. This works on any Zebra unit.
  • Raw ZPL: Zebra printers only print Korean natively when a Korean font is loaded. Units sold for the Korean market (or ordered with Zebra's Korean font option) have it pre-loaded; then raw ZPL with UTF-8 (^CI28) pointing at that font works. International units do not, and you would be uploading Korean TTFs into each printer's flash and managing them per device, the same class of font headache you had with wkhtmltopdf.
  • Recommendation: start with raster mode, it removes the question entirely. Raw ZPL stays available whenever you want maximum throughput and your printers have the font.
Quick question about Direct Print stations
by
Saori yagui
on 7/23/26, 11:14 PM Confirmed Purchase
Hi,

Tested Fast Report on our own docs and I'm getting 5-15x, so your numbers are legit. Now eyeing Direct Print 2.0.

One thing decides it for me. The warehouse PC reboots overnight, nobody logs in, and someone validates a transfer from a tablet in the morning. Does the label print or not? Basically: does a station need an open Odoo browser session, or is there something running in the background?

And just to be safe on QZ Tray: no scenario where we'd end up paying QZ Industries for certs, right, since you sign with our own keypair?

Thanks!

Quick question about Direct Print stations
by
Peter Nguyen
on 7/24/26, 1:16 AM Author

Hi,

  1. QZ license / cert: No, you don't need a separate QZ license. The module generates its own signing cert right inside Odoo. You install that into QZ Tray once and after that it prints silently, no popups. It's the standard free QZ trust setup, so you'd only buy QZ's own license if you specifically want it for other reasons.

  2. Reboot scenario: Yes, it prints, the way this is run in practice: the warehouse PC is set up once as a print station (OS auto-login, browser in startup apps, QZ Tray autostarts by itself). After that a reboot is a non-event: the machine boots straight back into its station role with nobody touching it, and it immediately picks up anything that was validated while it was down. Nothing is ever lost in between either: jobs queue on the server for up to 24h and the tablet user is told the station will catch up.

Only if you skip that setup and leave the PC at a login screen does the label wait for someone to log in. So it's a 10-minute configuration decision at install time, not something your team manages day to day. Happy to walk through it with you.

Thanks!