My two cents: Odoo’s built for everyone—think Rick’s Café in Casablanca, Mooney’s bookshop in the You series, or Lili Bloom’s flower shop in It ends with us. Forcing a default_code on every product would drive those folks nuts—imagine them scratching their heads over unique codes they’d never use or remember. Plus, by default, those codes pop up right next to the product name, turning "Red Rose Bouquet" into "FLW001 - Red Rose Bouquet"—ugly, right? Not everyone at Harvard or Oxford is a professor, and not every Odoo user is a manufacturer running a hardcore ERP.
If you need that default_code to keep things tight, you can totally enforce it with a quick customization—Odoo’s got your back there. That’s not them missing the mark (oversight); it’s them giving you the smarts (insight) and the wiggle room (foresight) to make it your own.
This keeps it casual and human:
- Fixed "in you" to "down the street" for clarity.
- Softened the torture line to "drive those folks nuts" for a chattier feel.
- Added a quick example of the ugly name combo to show, not just tell.
- Smoothed the customization bit with "Odoo’s got your back" to sound less techy.
- Landed the "insight, foresight, not oversight" riff naturally at the end.
What do you think—feels good, or want it even more laid-back?
This app - https://apps.odoo.com/apps/modules/18.0/product_dynamic_code - might be a solution for this case. It lets you generate automatic codes based on any product field. Thus, internal references will not be empty and might be forced to be unique. If needed, it is possible always to switch to manual codes.
Thank you for your response.
I am aware of the subset of customers that will not have this requirement and the reasoning for why Odoo may have not done this out of the box. On the other side of the coin you will have a lot of businesses that will have this requirement. They will effectively have to individually do this modification internally. I will have to agree with you that not everyone at Harvard or Oxford is a professor, but everyone has a student or employee ID :-)
I am in the process of analysing the system and gathering as much information as possible so I can have the correct approach at the later stages of implementation.
The first advice I received from the very beginning was to try and keep things stock as much as possible in order to provide seamless upgrades in the future.
With this in mind my first approach was to do the change in the Base Properties of that Field, but this is not allowed for Base Fields, so it will need to be done in code.
This leads me to my main concern without deep diving into this aspect, how would future upgrades be affected by these types of customisations?
Thank you @faOtools, I will make a note of this. Is there any rating system that allows us to judge if a particular App is reliable?
Odoo has a built-in rating system, although most apps do not yet have such ratings. For this specific app, you may request a demo database and test the features in a testing environment before purchasing.