[February 2026] Odoo community activity and Quartile's contributions

February 2026 was a month of pressing on with Odoo 18.0 support at OCA while continuing to propose improvements that follow Japanese business requirements. Across invoicing, purchasing, inventory, manufacturing and product management, we are accumulating small, practical changes that reduce the daily operational load. The 2025 OCA contribution ranking also gave us an occasion to look back at how far Quartile's technical contribution now reaches.

What we worked on in February 2026

The 2025 OCA contribution figures were published

The 2025 OCA contribution ranking has been compiled, and Quartile came in at 127 PRs / 476 reviews. Alongside a large increase in the volume of technical contribution, we are continuing to develop modules for Japanese requirements.

Reference: https://www.quartile.co/blog/odoo-1/2025-oca-160

Improvements proposed around invoicing

We proposed account_billing_from_cutoff to OCA, which creates consolidated invoices in bulk based on a cut-off date. We also proposed account_billing_portal, which shows consolidated invoices in the portal, so that the work is improving both the efficiency of invoicing and the customer-facing side of it.

Reference: https://github.com/OCA/l10n-japan/pull/83

Progress on the "actual date", which matters in manufacturing and inventory

We worked on 18.0 support for mrp_stock_move_actual_date, which adds an actual date to manufacturing and unbuild orders. In stock_move_actual_date, which gives stock moves an actual date, we also made progress on an improvement that lets inventory reports show quantities as at a past point in time on an actual-date basis. This is an area of real practical weight for how Japanese manufacturers operate.

Reference: https://github.com/OCA/manufacture/pull/1731

We also covered finer points of inventory operation, such as FIFO valuation and subcontracting

For FIFO-valued products, we worked on 18.0 support for stock_account_fifo_return_origin, which applies the original purchase price when goods are returned to a supplier. We also progressed 18.0 support for mrp_subcontracting_skip_no_negative, which stops stock_no_negative interfering unnecessarily in subcontracting scenarios. Both matter in practice, for auditing as much as for shop-floor operation.

Reference: https://github.com/OCA/stock-logistics-workflow/pull/2255

Improvements and ports around purchasing and reports

We proposed purchase_order_etd_eta, which adds ETD and ETA to purchase orders and shows them on the printed document. We are also working on 18.0 support for purchase_order_report_hide_tax, which can conditionally hide the tax column on the purchase order PDF. Both consider purchasing practice and the readability of the document together.

Reference: https://github.com/OCA/purchase-workflow/pull/2941

Improvements proposed to make product and variant management easier to live with

We proposed product_variant_search, which makes searching by attribute value easier; product_tag_view, which allows tags to be handled on the general information tab as well; and improvements to product_secondary_unit, the foundation of the secondary-unit module family. Tidying up everyday screen operation and searchability is aimed at taking friction out of daily use.

Reference: https://github.com/OCA/product-variant/pull/433

We kept up the small, nimble improvements around the edges too

We worked on 18.0 support for report_partner_address, which handles a partner's address as shown on printed documents, and for mail_send_confirmation, which raises a confirmation dialog when sending mail to an external user. hr_timesheet_sheet_prefill, which lets you add the previous period's projects and tasks with zero hours, has also had a warm reception from customers. Accumulating changes at this scale is, we think, an important part of what makes Odoo work in the field.

Reference: https://github.com/OCA/timesheet/pull/871

A word from the team

We put deliberate effort into community work at OCA through 2025, and seeing it show up as a ranking gave the Quartile team a small piece of confidence and encouragement.

Among February's work, the widening range of consolidated-invoice solutions and the improvements underpinning the secondary-unit module family were probably the most meaningful for the community, in that they extend Odoo's reach (the secondary-unit proposals have not been merged yet, mind).

AI has raised the speed at which solutions can be built, but our sense is that patiently refining something that fits real operations, and growing it within the community, matters just as much as it ever did. We will keep at the work of building good systems this month too.