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

As spring arrives, work on the next version and on improving existing features is moving steadily forward across Odoo and OCA. In March 2026, Quartile continued proposing and improving things in OCA and in Odoo core, mainly on themes close to daily operations: attendance, sales, purchasing, printed documents and Japanese localisation.

What we worked on in March 2026

OCA module proposals around attendance management

We proposed two modules to OCA: hr_attendance_flex_rest_time, which automatically suggests break time for employees on flexitime, and hr_attendance_manage_own, which makes it easier for employees to manage their own attendance records. Both are Odoo 18.0 features intended to fit how attendance is actually run.

Reference: https://github.com/OCA/hr-attendance/pull/253, https://github.com/OCA/hr-attendance/pull/264

Improvements to the sales and purchasing processes

OCA pull requests moved forward on a number of fine-grained operational improvements to sales and purchasing: an option not to show the product internal reference on sale order lines, warehouse suggestion based on the customer and delivery address, filtering invoice and delivery addresses by commercial partner, and adding ETD / ETA fields to purchase orders.

Reference: https://github.com/OCA/sale-workflow/issues/3967, https://github.com/OCA/purchase-workflow/pull/2941

Continued improvements around printed documents and display control

An improvement giving more flexible control over when numeric formatting applies in QWeb PDF documents was merged into OCA. We also progressed Odoo 19.0 support for report_qweb_field_option and report_partner_address, carrying existing reporting assets forward onto the newer version.

Reference: https://github.com/OCA/reporting-engine/issues/1139

Japanese localisation and consolidated invoicing

For l10n_jp_summary_invoice, the consolidated invoice feature for Japan, we proposed a fix and added tests for a problem that could create unnecessary tax adjustment entries when the company currency and the invoice currency differ.

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

A fix proposed to Odoo core

We proposed a fix to the Odoo core repository for a bug in the behaviour when adding attributes to an archived product template. Our feedback goes to Odoo itself, not only to OCA modules.

Reference: https://github.com/odoo/odoo/pull/252927

Writing about OCA activity

We also published an article to help people understand what OCA does and how it works. For companies using Odoo and for service providers, understanding how OCA works is an important foundation for thinking about long-term maintainability and version upgrades.

Reference: https://quartile.co/blog/odoo-1/odoo-oca-161

A word from the team

We took our OCA work into timesheets and attendance, areas we had not had much occasion to get into before. Our feeling is that this makes adopting Odoo's HR and labour features at Japanese companies a little more approachable than it was.

Customer feedback has moved the consolidated invoice and reporting features up another notch in maturity. Much of what we publish as open source is close to essential for trading companies, wholesalers and manufacturers, and we would be glad to see it used.

We have been publishing blog posts to encourage Odoo service providers to take part in OCA, though it is slow to show visible results. We will keep taking action to get the word out and to make the benefits easier to see.