PMIS UX
Extends stock and accounting usability with company report settings, product navigation, list and form changes, and local module-version comparisons.
Table of contents
Configuration
Dependencies are delivery, sale_stock, purchase_stock, and stock_account.
Open Settings > PMISuite Settings for the selected company:
Tax Labels on Reports exposes Show taxes as percentage, initially off.
Columns on Reports exposes separate product-code and description columns for sales-order reports, initially off.
Signature on Reports stores a company signature image for invoice, sales, and purchase reports.
Additional blocks expose existing accounting settings, default accounts, credit-limit settings, and the tax cash-basis journal.
The signature is a printed image, not a signing or approval workflow.
Language and formatting
The loaded language data changes both en_US and sl_SI to day-month-year dates (%d. %m. %Y), 24-hour time, a decimal comma, a space as the thousands separator, and Monday as the first weekday. These are shared language records, not per-company settings, and can affect all users of those languages.
Report output
Invoices hide the origin information block, adjust column widths, and print the company signature when configured.
Sales orders add the partner reference and Expected Delivery from the commitment date. The optional code column uses the product's internal reference; the description still uses the full sales-line name.
Purchase orders add Receipt date from the planned receipt date (date_planned), not the actual completion date.
Sales and purchase reports also print the configured company signature.
With the tax-label option enabled, invoice, sales, and purchase reports replace tax labels with a VAT(%) column.
The VAT column reads the tax recordset's amount directly. It assumes a single percentage tax per line: it neither combines multiple taxes nor converts fixed or grouped taxes into an effective percentage. Multiple taxes can cause a singleton error when rendering. Keep the standard labels for those cases.
Purchase, sales, and inventory
Purchase orders show and can be filtered by Last Done Picking Date, the latest completion date of a related picking in Done state. This stored field is separate from the planned date printed on purchase reports.
Purchase payment terms and fiscal position move ahead of the order date. Purchase Orders precedes Requests for Quotation in the menu.
Sales Orders precedes Quotations. The sales form repositions fiscal position, warehouse, Incoterm, and delivery policy. The embedded product-variant column is no longer optional.
The standalone sales-line list shows qty_to_deliver and highlights nonzero values.
Transfer lists sort by date and ID descending and show the completion date. Stock move forms display the picking and linked sales line, and adjust the origin/destination move sections and embedded list order.
Module versions and access
The Apps list adds Repository Version and Newer in Repository, plus Has repository update in search. Values come from locally available addon manifests, not a remote repository query.
Despite its label, Newer in Repository means the local manifest version differs from the installed version when both exist. It does not compare version ordering, prove an upgrade is available, or perform an update.
The addon creates a Super Admin group and assigns base.user_admin. It defines no additional ACLs, record rules, or implied permissions for that group.
Usage
Select the company and configure any report options under PMISuite Settings.
Preview the relevant invoice or order report after changing those options.
Open a product and use Incoming, Outgoing, Stock Moves, or the variant's Stock Valuation Layer button to inspect related records.
Use Last Done Picking Date to find completed purchase receipts, or Has repository update in Apps to identify local version mismatches.
Bug Tracker
Bugs are tracked on PMISuite Repository Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Credits
Contributors
Matjaž Mozetič
Maintainers
Current maintainer:
Luxim is an independent R&D and deployment company focused on solving complex problems in the Odoo ecosystem.
Luxim is an active member of OCA (Odoo Community Association).






