Manufacturing software has a particular talent for accumulating interface clutter. Every feature someone once requested gets a button. Every workflow fork gets its own screen. Over time, what started as a clean process management tool turns into a cockpit full of switches that nobody quite remembers the purpose of. The best antidote is periodic trimming—going back to existing interfaces and asking whether every element still earns its screen real estate.
Odoo’s PLM module receives exactly this kind of treatment in version 19.4. The changes are modest in scope—twenty-three lines added, twenty-two removed—but they address real friction points in the engineering change order workflow that anyone managing product revisions has bumped into.
One Less Thing Happening When You Click Start Revision
Previously, clicking the Start Revision button on an engineering change order triggered four simultaneous actions: creating a new BOM version, archiving the original BOM, advancing the ECO through its stages, and displaying the Review Changes smart button. That last action—showing the button—was listed as a discrete event in the documentation and in the interface’s implied mental model, even though it is really a consequence of the first three actions rather than a standalone operation.
In 19.4, Odoo drops it from the list. Start Revision now triggers three actions: create the new version, archive the old one, advance the stages. The Review button still exists, but it is no longer treated as something that “happens” when you start a revision. Instead, it appears only after changes have actually been made to the bill of materials. This is a subtle but meaningful distinction. The button’s appearance is now driven by state rather than by ceremony—it shows up when there is something to review, not simply because a process was initiated.
A Shorter Label That Says the Same Thing
The button itself has been renamed from “Review Changes” to “Review.” Two words become one. In a toolbar crowded with smart buttons, the extra word added cognitive load without adding information. The button already sits in the context of an engineering change order, attached to a specific BOM revision. The user does not need the button label to remind them that what they are reviewing is changes—that is the entire purpose of the ECO form they are already looking at.
This kind of label tightening rarely makes feature lists, but it reflects a mature approach to interface design. The first version of a feature tends to be verbose because the designer is explaining the concept. The refined version is concise because the concept has been absorbed into the platform vocabulary.
Updated Assets and Examples
Alongside the workflow changes, Odoo has refreshed several of the screenshots that illustrate the ECO process. The ECO form, archived BOM view, and BOM changes summary all receive updated visual assets that reflect the 19.4 interface. The example product used to illustrate revision tracking has been changed from keyboards to tables—a minor detail, but one that suggests the documentation team is actively maintaining these guides rather than carrying forward stale examples from earlier versions.
The BOM changes summary screen—where users compare the original and revised bills of materials side by side—has been reframed as the “ECO Changes Summary report” rather than the informal “BoM Changes tab.” This naming shift aligns with how the screen actually functions: it is a structured comparison report, not a tab within the BOM form. Calling it what it is helps users find it when searching for documentation and sets accurate expectations about what they are looking at.
The Compound Effect of Small Refinements
None of these changes will make someone choose Odoo’s PLM module over a competitor’s. That is not the point. The point is that manufacturing teams using this module every day will spend fractionally less time parsing redundant labels, mentally discounting non-actions in action lists, and searching for buttons that haven’t appeared yet because no changes exist to review.
Multiply those fractions across every engineer managing product revisions, across every day of the work week, across every month of a product’s lifecycle, and the compound effect is a quieter, less distracting tool that stays out of the way and lets people focus on the actual engineering decisions. That is what good PLM software refinement looks like—not more features, but less noise.