Skip to Content
SELF-HOSTED DIRECT PRINTING FOR ODOO

Direct printing.
Under your control.

Keep the Odoo workflow your teams already know while running the printing service layer on infrastructure selected and operated by your organization.

Built specifically for the separately licensed Odoo Direct Print PRO (by VentorTech), technical module name printnode_base.

Explore the guided demo View pricing →
Odoo 19 & 18 Self-hosted Runtime Reversible migration path
first-print
XiotBox Runtimehealthy
Odoo 19 / 18→Runtime→Printer
10:42:16 installation token accepted
10:42:17 printers discovered: 2
10:42:21 test job completed
Delivery path active inside your network
DESIGNED FORManufacturingWarehousesLogisticsMulti-site operations
ONE PRODUCT, TWO STARTING POINTS

Start self-hosted, or migrate without rebuilding Odoo.

XiotBox adds a customer-operated service path to a familiar Direct Print PRO workflow. Choose the path that matches the database you have today.

NEW DEPLOYMENT

Begin with your own service layer.

Create the self-hosted account, deploy Runtime and SocketD, connect a supported desktop client, and select the discovered printers in Odoo.

  • No existing PrintNode cloud account required
  • Guided account and default-printer setup
  • One documented path to the first print
Read the requirements →
EXISTING DEPLOYMENT

Move the route, keep the records.

Preserve the existing Direct Print account and match computers and printers in place so Odoo references can remain attached throughout acceptance.

  • Original endpoint retained for rollback
  • Existing records matched instead of recreated
  • Test before cancelling the former service
Review the migration path →
BUILT AROUND OPERATIONS

Control the route, the records, and the transition.

A small set of clearly separated components keeps the Odoo module installable while the desktop compatibility and delivery services run outside the Odoo worker.

01

Control the route

Run Runtime and SocketD on a Linux host, virtual machine, or supported container environment selected by your team.

02

Control the records

Accounts, devices and job history remain normal Odoo records covered by your access, backup and retention procedures.

03

Control the transition

Keep the former endpoint and desktop configuration available until the self-hosted path passes acceptance.

ARCHITECTURE

Three layers, with explicit boundaries.

Odoo keeps business configuration. Runtime owns the compatibility API. SocketD carries jobs to supported desktop clients and printers.

Read the deployment architecture
BUSINESSOdoo 19 / 18Configuration and records
01
SERVICERuntime + SocketDCustomer-operated host
02
DEVICEDesktop + PrinterLocal print execution
PREDICTABLE OWNERSHIP

One production-database licence, with the delivery components explained before purchase.

See the current price, required third-party dependency, included downloads, update period and support boundary on one dedicated page.

See pricing and inclusions Read the documentation
THE PURCHASE PATH
  1. BuyOdoo module licence and customer entitlement
  2. DownloadPublished Runtime, SocketD and patch artifacts
  3. DeployFollow the versioned first-print guide
COMMON QUESTIONS

Know the boundaries before you deploy.

Compatibility is deliberately narrow so the supported path stays understandable.

Which Odoo printing module is supported?

Odoo Direct Print PRO (by VentorTech), technical module name printnode_base. It must be obtained and licensed separately.

Which Odoo versions are supported?

Odoo 19.0 and Odoo 18.0 are supported on separate release branches. The XiotBox and printnode_base branches must match the Odoo major version.

Can I install XiotBox on Odoo Online?

No. XiotBox requires an Odoo environment where third-party Python modules can be installed. Self-managed Odoo and supported Odoo.sh layouts are documented separately.

Does the Odoo Apps ZIP contain Runtime or SocketD?

No. The Apps ZIP contains the Odoo module. Executable delivery components are published separately through the authenticated customer portal and are not downloaded or launched by the module.

Can an existing deployment roll back?

Yes, when the former endpoint, API key and desktop configuration are retained until acceptance. The migration guide describes the required order.

SEE THE WORKFLOW

Walk through the first print before touching production.

Inspect connection, discovery, record matching, PDF delivery and rollback in the guided Odoo 19 demo.

Open the guided demoReview pricing