Wednesday, June 24, 2026
3 changes · saas-19.1
New functionality added to Odoo
This update introduces on-demand printing of kitchen order tickets directly from the kitchen station. When an order moves to a defined stage, the system automatically generates and prints a KOT. The tickets now include barcodes for efficient scanning and streamlined order processing.
Original PR description
*: pos_restaurant_preparation_display, pos_urban_piper In this commit: ------------------- - Introduced functionality to print KOTs on demand from the kitchen. - Added support for automatic printing when an order is moved to a configured stage. - Added barcodes to KOTs printed from the kitchen, allowing kitchen staff to scan them and directly move the order to the next stage. task: 6131467 Community PR: https://github.com/odoo/odoo/pull/266273
This update enables automatic receipt of vendor bills from the Hungarian tax authority (NAV) via their API. A new 'Sync with NAV' button allows users to schedule bill retrieval based on a date range, and supports both API integration and direct XML uploads for seamless invoice processing. This improves efficiency and accuracy for Hungarian businesses.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910 Forward-Port-Of: odoo/odoo#240919
This update adds the ability to generate invoice PDF reports in multiple formats (Original, Duplicate, Triplicate) to comply with government regulations regarding GST documentation. Users can now print two or three copies of invoices with distinct titles, catering to different recipient types like transporters and suppliers. This ensures accurate record-keeping and adherence to tax requirements.
Original PR description
The Goverment specifies that invoice should be printed in different formats as per the different parties the invoice is been given to. Invoice should be marked as "Original" for receiver's copy. Invoice should be marked as "Duplicate" for transporter's (incase of goods supply) or supplier's copy. Invoice should be marked as "Triplicate" for supplier's (incase of goods supply) copy. This commit adds two new report actions, for Duplicate and Triplicate on invoice, visible in the Print section under the gear icon. When user prints Duplicate, 2 copies will be printed and for Triplicate, 3 copies will be printed at once, with different titles set on each copy of invoice. task-5899610 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#270813