Upgrades and customization
Upgrade-safe builds, automation rules, and where Studio stops and real development starts.
Customizing Odoo is easy. Keeping those customizations working through the next upgrade is harder. This category is about building in a way that survives new versions, and knowing where configuration ends and real development begins.
The guides explain why an upgrade can break your customizations and how to build upgrade-safe from the start, and where Odoo Studio stops and code takes over. They also cover the technical problems that land on an Odoo admin's desk: a system that has become slow and the practical fixes, outgoing email that won't send because of port 25 or SPF and DKIM, and the difference between access rights and record rules when a user can or cannot see something. The posts help in-house Odoo admins, IT leads and owners who want to understand what their partner is building, and why some choices cost more later than they save now. They are practical, not theoretical.