Siso SmartPOS

About Siso SmartPOS

Siso SmartPOS is a direct-to-printer receipt module for Odoo Point of Sale. It replaces Odoo's default IoT Box–dependent printing with a browser-native approach: raw ESC/POS data is generated in the browser and sent directly to a thermal printer over USB, serial, or TCP — no additional hardware, no proxy service (except for network printers), no cloud dependency.

The module has three major components:

• Receipt Renderer — A template engine that translates a simple XML tag language into both ESC/POS binary (for the printer) and HTML (for the browser preview and document archive). The renderer supports a rich set of layout primitives: multi-column tables, bold/underline/reverse text, font sizes, QR codes, barcodes, logos, and conditional whitespace.
• Printer Driver — Thin adapters for USB (WebUSB API), serial (WebSerial API), and TCP (local bridge relay). The first time a print job is sent, the browser presents a device-picker dialog; the selection is remembered for the rest of the session.
• Compliance Engine — Automatic archival of every document type (sales receipts, return receipts, training receipts, pro-forma drafts, X-reports, Z-reports) with lifetime grand-total counters and per-session breakdowns satisfying the mandatory requirements of Norwegian kassasystemforskriften.

Part 1 of this document covers the day-to-day features available to cashiers and operators. Part 2 covers installation, configuration, and the administrative tools. Part 3 is a full reference for the receipt template language.

Printing Receipts

When SmartPOS is installed and configured, receipt printing works as it always has in Odoo POS — the operator completes a sale, and the receipt is printed automatically if the POS is configured to auto-print, or manually via the Print Receipt button on the receipt screen.

Behind the scenes, SmartPOS intercepts the print job before Odoo's default handler, generates ESC/POS data from the active receipt template, and sends it directly to the configured printer. The customer sees no difference; the operator sees a faster, more reliable print path.

Reprinting

Opening any past order from the Ticket Screen and clicking Print Receipt sends a reprint. SmartPOS tracks reprints as "copies" for compliance purposes — the copy counter increments and the reprint is recorded in the session's X/Z-report data.

Return Receipts

When a return (refund) order is finalised, it is automatically archived as a return receipt — a distinct document type from a standard sales receipt. The return count and amount are reported separately on X and Z reports.

Printing a Draft (Pro-forma)

A draft receipt — also called a pro-forma — is a non-finalised printout of the current order before payment. It is useful for showing a customer the total before they pay, printing a kitchen order, or obtaining a signature on a quote.

Each draft print increments the pro-forma counter in the session statistics. The printed document is archived as a proforma type in the Document Archive and counts toward the session's pro-forma total in X/Z reports.

X-Report — Interim Session Report

The X-Report is a non-closing snapshot of the current session's turnover. It shows accumulated totals, VAT breakdown, payment method summary, and correction counts — identical in structure to a Z-Report, but printing it does not close the session or reset any counters.

X-Reports use the X-Report Body template section, sharing the same Header and Footer as sales receipts. The body template is separately configurable so reports can be formatted differently from customer receipts.

Sending a Receipt by Email

SmartPOS integrates with Odoo's built-in receipt email functionality. On the receipt screen, enter the customer's email address in the send-by-email field and click the send button.

When a customer is attached to the order, their email address is pre-filled automatically. SmartPOS generates the receipt as an HTML document (using the same template as the printed receipt) and sends it via Odoo's standard mail server.

Customer Omni-Search

The receipt screen includes a customer search field — labelled Kundesøk by default — that lets the operator find and attach a customer to the current order without leaving the receipt screen.

Configuring Search and Display Fields

The fields searched and the columns shown in the multi-match popup are configurable in POS Settings → Siso SmartPOS:

Installing Siso SmartPOS

Upgrading Siso SmartPOS

Printer Configuration

SmartPOS supports three connection types. All are configured in Point of Sale → Configuration → Settings under the Siso SmartPOS Printer section.

USB

Uses the browser's WebUSB API to send ESC/POS data directly over a USB connection. This is the fastest and most reliable connection type for a dedicated POS terminal.

How to find your IDs:

• Linux: Run lsusb. Each line shows ID vendor:product.
• Windows: Device Manager → right-click printer → Properties → Details → Hardware IDs. Look for VID_XXXX&PID_XXXX.
• macOS: Apple menu → About This Mac → System Report → USB.

Serial (RS-232 / USB-Serial)

Uses the browser's WebSerial API. Suitable for older printers connected via RS-232 or USB-to-serial adapters.

The baud rate is set in the printer's hardware configuration (DIP switches or service menu). Check your printer's manual; 9600 is the most common default.

Network (TCP)

Sends ESC/POS data over TCP to a network-connected printer. Requires the Siso Local Bridge — a small service that runs on the POS workstation and relays print jobs from the browser to the printer.

Printer Width

Set Printer Width (chars) to the number of characters that fit on one line at normal font size. This drives all column layout calculations.

Run a self-test print from the printer itself — it typically prints a full-width line of characters you can count directly.

OS-Level Setup for USB Printing

WebUSB requires the operating system to grant the browser access to the USB device. Each OS handles this differently.

Linux

Linux automatically binds USB printers to the usblp kernel module, which blocks WebUSB. You must unbind the driver and prevent it from re-attaching.

lsusb
# Example: Bus 005 Device 003: ID 1504:003d Bixolon SRP-350plusIII

sudo tee /etc/udev/rules.d/99-usb-printer.rules << 'EOF'
SUBSYSTEM=="usb", ATTRS{idVendor}=="1504", ATTRS{idProduct}=="003d", MODE="0666"
EOF

sudo tee /etc/modprobe.d/blacklist-usblp.conf << 'EOF'
blacklist usblp
EOF

# Find interface name — look for DRIVER=usblp
grep -r usblp /sys/bus/usb/drivers/usblp/*/uevent 2>/dev/null

# Unbind it (replace 5-1:1.0 with your interface name)
echo -n "5-1:1.0" | sudo tee /sys/bus/usb/drivers/usblp/unbind

sudo udevadm control --reload-rules
sudo udevadm trigger --attr-match=idVendor=1504

macOS

macOS does not need driver replacement. Chrome and Edge can access USB printers through WebUSB directly. If the printer does not appear in the device picker, try unplugging and replugging. On macOS Ventura and later, allow USB accessories access in System Settings → Privacy & Security → USB Accessories.

Windows

Windows assigns the usbprint.sys driver to USB printers, which blocks WebUSB. Replace it with the generic WinUSB driver using the free tool Zadig.

The Receipt Designer

The Receipt Designer is accessed from Point of Sale → Configuration → Receipt Templates. Each template consists of five separate sections printed in order:

Assigning a Template to a Register

Go to POS Settings for the target register and set the Receipt Template field. If no template is assigned, SmartPOS falls back to built-in default templates that satisfy basic compliance requirements.

Compliance Settings

Two compliance flags are available on each template:

• Prevent Archive Deletion — When enabled, Odoo will refuse to delete any archived document linked to this template. Recommended for regulated environments.
• Code Page — Selects the ESC/POS character table sent at the start of every print job (e.g., PC858 for Western European + Euro symbol). Choose the code page that matches your receipt language.

Field Dump Template

SmartPOS ships with a special field dump template that prints every available context variable and its current value. Assign it temporarily to a register and print a test receipt to see exactly what data is available for your layout — useful when building a new template from scratch.

The Document Archive

SmartPOS automatically archives every document it prints. Six document types are supported:

Each archive record stores three payloads:

• HTML Preview — Rendered HTML viewable directly in the Odoo form.
• ESC/POS Data — The binary data that was sent to the printer. Can be used for reprinting.
• JSON Context — The complete rendering context at the time of printing. Useful for auditing and dispute resolution.

Accessing the Archive

Navigate to Point of Sale → Reporting. Each document type has its own menu entry. The SmartPOS: Full Archive view (under Configuration) shows all types in a single filterable list.

Template Language Overview

Receipt templates are written in a simple XML-based tag language. Each tag maps to one or more ESC/POS commands when printing, and to equivalent HTML for the preview and archive. Tags can be nested freely unless otherwise stated.

Placeholders

Dynamic values are inserted with curly-brace placeholders:

{variable}                 ← plain value
{variable:.2f}             ← numeric format (2 decimal places)
{variable:dd.MM.yyyy}      ← date format (Luxon tokens)

Variable names are case-sensitive dotted paths (e.g., head.company.name, line.price_total_incl). Unknown paths render as an empty string — they never cause an error.

Structure of a Typical Receipt

<!-- HEADER -->
<center><logo max-width="80"/></center>
<feed lines="1"/>
<center><x2>{head.company.name}</x2></center>
<center>{head.company.address.line1}</center>
<center>{head.company.address.postal_code} {head.company.address.city}</center>
<center>Org.nr: {head.company.vat_id}</center>
<hr/>
<center>{doc.type_label}</center>
<hr/>

<!-- BODY -->
<row><left>{order.name}</left><right>{head.date:dd.MM.yyyy HH:mm}</right></row>
<hr/>
<lines>
<table><tr>
  <td wrap="1">{line.name}</td>
  <td w="5" align="right">{line.qty}</td>
  <td w="8" align="right">{line.price_total_incl:.2f}</td>
</tr></table>
</lines>
<hr/>
<row bold="1"><left>TOTAL</left><right>{order.amount_total:.2f}</right></row>

<!-- FOOTER -->
<feed lines="1"/>
<center><qr size="4"/></center>
<feed lines="3"/><cut/>

Context Variables

The following variables are available in all template sections unless noted otherwise.

Document (doc.*)

Company (head.company.*)

POS Terminal (head.pos.*)

Date and Time

Order (order.*)

Customer (customer.*)

Only populated when a customer is attached to the order.

Order Line Variables (inside <lines> loops)

Tax Variables (inside <taxes> loops)

Payment Variables (inside <payments> loops)

X/Z-Report Variables (z.*) — X-Report and Z-Report Body only

Text and Formatting Tags

Alignment

Alignment tags reset to left after the closing tag. They map to ESC a commands.

Text Modifiers

All modifiers nest freely and reset on their closing tag.

Font Selection

Character Size

Size is set with GS !. Width and height are scaled independently; normal size is restored on the closing tag.

Whitespace and Rules

Column and Row Layout

Two-Column Row (<row>)

Left-aligns the left side, right-aligns the right side, and fills the gap with spaces to exactly fill one line.

<row><left>Subtotal</left><right>{order.amount_untaxed:.2f}</right></row>
<row bold="1"><left>TOTAL</left><right>{order.amount_total:.2f}</right></row>

The optional bold="1" attribute makes the entire row bold.

Multi-Column Table (<table><tr><td>)

The preferred approach for new templates. Supports word-wrap and flexible column widths.

Columns without a w attribute share the remaining width equally (flex behaviour).

<!-- 4-column line items table -->
<table>
  <tr bold="1">
    <td>Varenavn</td>
    <td w="5" align="right">Ant.</td>
    <td w="7" align="right">Pris</td>
    <td w="7" align="right">Sum</td>
  </tr>
</table>
<lines>
<table>
  <tr>
    <td wrap="1">{line.name}</td>
    <td w="5" align="right">{line.qty}</td>
    <td w="7" align="right">{line.price_unit_incl:.2f}</td>
    <td w="7" align="right">{line.price_total_incl:.2f}</td>
  </tr>
</table>
</lines>

Dot-Column Layout (<dot><col>)

An older but fully supported column layout. Each <col> is allocated a fixed number of character positions; content is padded or truncated to fit.

Both <table><tr><td> and <dot><col> can be mixed in the same template.

Loop Sections

Loop tags iterate over a list from the rendering context. The content between the opening and closing tag is repeated once per item, with the item's fields available as short-form variables.

<lines> — Order Lines

Iterates once per order line. All {line.*} variables are available inside.

<lines>
<row><left>{line.name}</left><right>{line.price_total_incl:.2f}</right></row>
</lines>

<taxes> — Tax Breakdown

Iterates once per tax rate applied to the order. Satisfies the Norwegian requirement for per-rate VAT disclosure.

<taxes>
<row><left>MVA {tax.rate:.0f}%</left><right>{tax.amount:.2f}</right></row>
</taxes>

<payments> — Payment Lines

Iterates once per payment line on the order (e.g., cash, card, Vipps).

<payments>
<row><left>{payment.method}</left><right>{payment.amount:.2f}</right></row>
</payments>

<categories> and <products> — Report Loops

Available in X/Z-Report Body templates. Iterate over POS category sales and product sales for the session, respectively. Use {category.name}, {category.amount}, {product.name}, {product.qty}, {product.amount} inside these loops.

Graphic Elements

Logo

<logo max-width="80"/>

Fetches the company logo, scales it to the specified percentage of the printer dot width, and rasterises it to 1-bit for GS v 0 printing.

QR Code

<qr size="4" error="M" data="{order.name}"/>

Prints a QR code via GS ( k (Model 2).

Barcode (CODE128)

<barcode height="50" text="1" data="{order.name}"/>

Prints a CODE128 barcode via GS k 73.

Overview

Append a colon and a format string after any variable to control how its value is rendered: {variable:format}. If no format is given, the raw string representation is used.

Numeric Formats

Numeric format strings follow Python's format specification:

Date/Time Formats

Date and datetime variables use Luxon format tokens:

Full Luxon token reference: moment.github.io/luxon.

Norwegian Kassasystemloven

Norway's kassasystemforskriften (the Cash Register Regulation) mandates specific capabilities and data requirements for all electronic cash register systems used in business. The key sections relevant to SmartPOS are:

§ 2-8-2 — Mandatory Counters and Report Fields

X and Z reports must include the following data, which SmartPOS populates automatically:

§ 11 — Document Archiving

All documents generated by the cash register must be stored and retrievable for a minimum period. SmartPOS satisfies this requirement through its automatic Document Archive — every document type is archived with full content at the moment of printing.

Training Mode

When the POS is in training mode, receipts are printed with a ØVELSE (training) designation and archived as training_receipt — a distinct type that does not count toward official sales totals or lifetime counters.

Complete Tag List