Odoo Slides & Videos

These slides are in Japanese. They were presented at an Odoo Open Talk held on 31 July 2026, and set out how to start contributing to the OCA (Odoo Community Association) — for people who write code and for people who don't.

The number of companies using Odoo in Japan has grown, but the number giving back to the ecosystem has not. This deck assumes that gap is not about willingness but about knowing where the entry points are, and aims to make the first step concrete.

What the deck covers

• What the OCA (Odoo Community Association) is — its relationship with Odoo S.A., and its AGPL/LGPL output
• Contribution is not only writing code — translation, issues, review, documentation
• Turn what troubles you into an issue — put it in the open instead of solving it internally
• The developer route — from signing the CLA to opening a small PR
• How a PR reaches merge, and how long that realistically takes
• A worked example: how a two-line PR progressed (OCA/account-invoicing#2201)
• Mistakes new contributors commonly make — opening translation PRs directly, and others
• Rules for contributing with AI — the OCA Generative AI / LLM Policy (effective July 2026)
• Beyond individual contribution — why company commitment is necessary
• Realistic entry points for the Japanese community
• Glossary

Links

• OCA repositories (GitHub)
• CLA (Contributor License Agreement)
• Weblate — the OCA translation platform
• OCA Generative AI / LLM Policy
• The PR used as the worked example: OCA/account-invoicing#2201
• OCA Days 2025 — Daniel Reis on how to contribute
• Unofficial Japanese Odoo community Discord

Links inside the slides are clickable once you download the PDF.

Presented at the Odoo Partner Session on 24 June 2026. The deck sets out how far Odoo gets in the Japanese market, where it stalls, and the role open source plays in getting past that.

The slides are mainly in English, with Japanese alongside the key points.

What the deck covers

• Why the playbook that worked globally stalls in Japan — Japanese UI and documentation are mandatory, the linguistic distance is large, processes bend to trading partners, commercial customs are distinctive, adoption decisions are cautious and precedent-driven, and domestic accounting and HR software is strong
• The turning point — Odoo brought translation in-house in 2023 and the Japanese UI is now genuinely usable, awareness is rising, and AI is collapsing the language and implementation barrier
• The state of OCA contribution — 448 of 3,300 partners contributed to OCA in 2024, and as the partner count passes 16,000 that share keeps shrinking
• Three asks of Odoo S.A. — recognise the partners who contribute, collaborate on Japanese localization instead of duplicating it, and teach new partners the norms of open source
• What breaks the virtuous cycle — free-riding on OCA, treating "open" as marketing rather than practice, localization lag eroding satisfaction, and losing differentiation into price competition
• Why a healthy OSS ecosystem serves Odoo S.A.'s own business — lower acquisition cost, faster product improvement, and stronger partners

Related links

• Choosing an Odoo partner by their OCA contribution
• Odoo Community Association (OCA) official site

Used at an Odoo Open Talk in June 2024. These slides are in Japanese. Before telling anyone to contribute, the deck explains how the Odoo ecosystem actually turns and why it needs more participants right now.

This session is about background and reasoning rather than procedure.

What the deck covers

• Odoo's history and licence changes — from TinyERP to OpenERP to Odoo, through GPL and AGPL, and the move to an LGPL-plus-proprietary open core model in October 2015
• Why the shift to open core happened — under AGPL the vendor struggled to secure revenue and had to lean on selling services
• How the licences differ — LGPLv3 lets proprietary features sit on top; AGPLv3 extends to dependent code and requires source to be obtainable
• Odoo's growth cycle — product improvement, user base, monetisation, and reinvestment, with open source acting as the leverage
• Who is in the ecosystem — Odoo S.A., partners, other service providers, OSS contributors, and users, and how each connects
• How Odoo's focus changed — after the open core shift, the sales side of the business inevitably grew louder
• The present concern — many market-facing staff and partners appear indifferent to the OSS ecosystem, and newly joining partners do not take part in it
• The worst case for users — roughly 60% of user requirements can be met with existing OCA modules, so if that ecosystem dies the answer reverts to bespoke proprietary development
• Reasons to take part, set against the reasons people give for not taking part
• What anyone can do first — use a community module, tell your users you are using it, and write about it publicly

Related links

• Odoo Community Association (OCA) official site
• OCA repositories on GitHub

Used at an Odoo Open Talk on 14 June 2024. These slides are in Japanese. When Odoo's Japanese display will not behave, this deck explains what to touch and why, starting from how translation is built.

Note that Odoo core has since moved its translation platform from Transifex to Weblate. For the current procedure, see the separate Weblate deck.

What the deck covers

• What is translatable — field labels, menus, buttons, help text, reports, mail templates, the website, error and warning messages, and data fields defined as translatable
• How to spot it in the source — translate=True on a Python field definition, messages wrapped in the underscore function, and strings inside XML views and templates
• Differences by ownership — Odoo core, OCA modules, and your own custom modules each update their translation files by a different route
• Differences by engine — some strings are handled server-side and some on the front end, and website templates are where the constraints bite
• Where translation data is stored — held in a table up to 15.0, then as jsonb on the field itself from 16.0. Faster, but harder to adjust from the UI
• Applying project-specific wording — update the translation file normally for custom modules, and drop override translations into an i18n_extra folder for standard features
• A common problem — term collisions within one module, where words like Send or State need different translations by context but share one source string
• Useful OCA modules — template_content_swapper and report_qweb_field_converter

Related links

• Translating Odoo and OCA into Japanese with Weblate (current procedure)
• OCA/l10n-japan — Japanese localization modules

Presented at the Fukuoka Integration X (FIX) online event on 7 February 2024. These slides are in Japanese. Aimed at people new to Odoo, the deck lays out the product and its ecosystem, then shows how to handle the things that trip people up when using it in Japan.

It focuses in particular on partner address handling and on printing quotations, invoices, and purchase orders.

What the deck covers

• What Odoo is — the most widely used open source business application suite, its technical stack, the breadth of what it covers, multi-currency and multi-language support, and the size of its community
• What makes Odoo distinctive — low cost, broad functional coverage, and genuine global capability
• Odoo and open source — the growth cycle, the difference between Community and Enterprise, and where OCA sits
• Characteristics of the Japanese market — Japanese-language material and a Japanese product UI are mandatory, commercial customs are distinctive, failure is avoided, and little is published in English
• Working through the friction in a demo — how far OCA community modules get you against Japan-specific requirements
• How to try Odoo for yourself
• Practical advice for running an Odoo implementation project

Related links

• Fukuoka Integration X event page
• OCA/l10n-japan — Japanese localization modules

Slides from the live webinar "Get to know Odoo customization" on 31 August 2023. These slides are in Japanese. Aimed at drawing software engineers toward Odoo, the deck takes two real business requirements and shows the standard-configuration answer next to the custom-code answer.

It goes all the way down into code and module structure.

What the deck covers

• What customizing Odoo means — configuration versus add-on development, and the Python, PostgreSQL, JavaScript, and QWeb stack behind it
• Why customization should be avoided where possible — it costs money, makes maintenance harder, and makes version upgrades painful
• Worked example 1 — showing the tax registration number on invoices for Japan's qualified invoice system. Document layout settings cover most of it; an add-on module handles the rest
• Worked example 2 — preventing deletion of accounting evidence attachments for Japan's electronic bookkeeping law, using attachment_delete_restrict to set which groups and users may delete per model
• Odoo's module structure — every feature is a module, stacked by dependency through base, web, mail, product, account, and sale. A custom module is technically the same kind of thing as a standard one
• What a module is made of — business objects, data files, web controllers, and static web assets
• Real code — __manifest__.py, a model definition, and the XML for inheriting a view
• Rules for writing modules — extend rather than override, go through the ORM, do not build what is not needed, split by business purpose, and do not breach licences
• Understanding open source — what OCA does, and how LGPLv3 differs from AGPLv3. Odoo is not licence-free

Related links

• Webinar recording: Get to know Odoo customization
• Blog post: what we wanted to get across in the customization webinar
• OCA/server-tools — the repository holding attachment_delete_restrict

A Japanese adaptation of an illustrated Odoo introduction created in 2015. These slides are in Japanese. With almost no jargon, it follows in story form what happens when a business consolidates onto one system.

A good first thing to show someone new to Odoo, or a colleague you need to bring along internally.

The story

• Mr. Horiba runs an audio equipment manufacturer. With 45 staff handling 4,500 orders a day, the business ran at 100 orders per person
• Mr. Saito, the finance director, is buried in invoices raised from the logistics system, timesheet imports, refunds, reports for the boss, syncing the online shop, and payment runs
• Over a few years, separate IT tools piled up one after another, leaving the work more complex and still disconnected
• By 2015 headcount had reached 90, yet orders stalled at 5,000 a day. That is 55 per person — a 45% fall in five years — and margins fell with it
• When the HR director asks for recruitment software, Mr. Horiba balks at adding yet another system
• Wanting to consolidate the sprawl, he encounters Odoo and starts small with the recruitment app alone
• As CRM, manufacturing, sales, BI, project, and accounting follow, orders per person climb back from 55 step by step while annual IT cost falls from its starting point of 7.5 million yen

Related links

• Getting Around Odoo — implementing efficiently with open source
• Quartile's business and culture

An Odoo user guide. These slides are in Japanese. They walk through exporting the records shown in a list view to Excel or CSV, screen by screen.

Beyond feeding reports, the exported file is a convenient way to build a template for creating new records or updating existing ones.

What the guide covers

• Exporting from a list view — open the list for the model you want, tick the records on the left, and choose Export from the Action menu. The Action button only appears once something is selected
• Choosing the fields — pick what you need from the list on the left and export as either Excel or CSV
• Saving a field list — storing a combination you use often saves reselecting the fields every time
• Choosing between the two export types — "export all data" reaches beyond the current model into related models, which suits reporting and other read-only purposes
• The other option, "export in an import-compatible format", returns only the fields held directly on the model. This is the one for building an import template, or for editing exported data and loading it back in

Related links

• Odoo official documentation: exporting and importing data

A working guide to improving the Japanese translation of Odoo core and OCA modules through the Weblate translation platform. These slides are in Japanese. Translation is the easiest way into community contribution — no code required — and the deck walks through it screen by screen.

Odoo and OCA both use Weblate, but they differ in how you register and how changes land. The deck treats the two separately.

Translating Odoo core

• How it works — Odoo's in-house team manages the translation, which syncs to the Odoo GitHub repository every few days. Anyone outside that team submits suggestions, which appear once approved
• Getting set up — register an account, then apply to translations@odoo.com. Vetting has tightened, so include your company, ERP background, and translation experience
• If you have no Odoo environment for translating, runbot works as one
• How Weblate is organised — a project maps to an Odoo version, a component maps to a module
• Finding the right module — use developer mode to inspect the field; its "related module" is the Weblate component
• Writing search queries — source: for the English, target: for the translation, component: and project: (the project slug, not its name). Append = for an exact match
• A warning about markup — never alter tags inside the source string. Removing one causes a runtime error in Odoo
• Which versions to fix — submit to every major version and to the newest SaaS version. New releases take their translations from the latest SaaS build, so skipping it leaves the old wording in place
• Quality conventions — half-width colons and parentheses, polite form for errors and help text, plain form for field descriptions, and consistent terminology checked against past translations rather than loosely reinterpreted
• Uploading translation files per component (suggestion mode only), and refreshing translations inside Odoo afterwards

Translating OCA modules

• How it differs from Odoo — a project is a repository-and-version pair, the sync to GitHub runs daily, and your change lands without waiting for approval
• Getting set up — register with a GitHub account, then email transbot@odoo-community.org with the language you want (about a week to process)
• Where a component has no Japanese yet, add the language yourself before translating
• Because OCA work tends to be module by module, downloading and uploading the translation file is the practical route

Related links

• Odoo's translation platform (Weblate)
• OCA's translation platform (Weblate)
• Odoo's translation guide (GitHub Wiki)

Presented at the Odoo Roadshow in Tokyo on 23 March 2018, the first such event held in Japan. These slides are in Japanese. Across 78 pages it covers what kind of product Odoo is and how its being open source bears on an implementation.

The material reflects March 2018. Figures and screens differ from current versions, but the thinking on how to use open source and how to choose a partner still holds.

What the deck covers

• Odoo's market position — search trend comparisons against the major ERPs, and against other open source ERPs
• Why Odoo became popular worldwide — low cost, broad functional coverage, and global capability
• The growth cycle of an open source product — and why Odoo turns that cycle more successfully than any other open source ERP
• Characteristics of the Japanese market — Japanese material and a Japanese UI are mandatory, commercial customs are distinctive, and failure is avoided
• What open source is, and what it offers users, service providers, and the vendor respectively
• Routes to implementation — engaging a partner versus doing it yourself
• Why the Odoo Community Association exists, with a breakdown of module counts by version
• An introduction to Quartile and the community work it does
• Customization examples — extra fields captured at purchase registration, pulling records from the supplier table, auto-archiving out-of-stock web products, and bulk-importing auction results
• Feedback from an implementation customer, and why the choice of partner matters so much

Related links

• Blog post: Japan's first Odoo Roadshow event
• OCA/l10n-japan — Japanese localization modules