Internal references for every product and every variant
Configure pattern-based rules once and every new product — and every variant it creates — gets a correct, unique Internal Reference automatically. Clean up an existing catalog with a bulk generator that previews every code before it touches a single record.
Odoo leaves the Internal Reference field blank by default, so operations and purchasing teams end up inventing SKUs by hand for every new product. Worse, when a template creates multiple variants, most auto-numbering tools give the parent a code and leave every variant unreferenced, forcing manual cleanup across catalogs with hundreds or thousands of SKUs.
Auto Generate Product Internal Reference builds each code from configurable pattern rules that combine static text, category, product name, variant attributes and a zero-padded sequence — resolved per category with priority and ancestry fallback. Every variant gets its own distinct, correct reference the moment it is created, existing catalogs can be cleaned up with a dry-run bulk wizard, and duplicate codes are blocked catalog-wide.
Everything a growing catalog needs
Every capability below is implemented in the module.
Pattern-Based Rule Builder
Combine static text, category name, product name, variant attributes and a zero-padded sequence, in any order, to build the exact code format your catalog needs.
Category & Global Rules with Priority
Assign a rule to a specific product category with a priority order, or fall back to a single global default rule for everything else.
Category Ancestry Resolution
A rule defined on a parent category automatically applies to every child category that has no rule of its own — configure once, cover a whole tree.
Correct Per-Variant References
Every variant, including every attribute combination, gets its own distinct, correctly generated Internal Reference — the gap most competing apps still leave open.
Live Example Code Preview
See exactly what a generated code will look like as soon as you change a rule's components, separator or letter case — before you save it.
Per-Product Override & Regenerate
Turn auto-generation off, force a specific rule, or regenerate a fresh code on demand directly from the product form.
Bulk Generation with Dry-Run Preview
Generate references for an entire catalog in one pass. Preview every proposed code first — no sequence number is consumed until you apply.
Conflict Detection
The bulk wizard flags any proposed code that would collide with another product before you ever commit a change.
Catalog-Wide Duplicate Prevention
A validation guard blocks saving two active products with the same Internal Reference, keeping every code in your catalog unique.
How it works
Define a Rule
Build a pattern from category, product name, attribute and sequence components, with a separator and letter-case option.
Assign It to a Category
Or leave it global. Category rules win over the default, with ancestry fallback for subcategories left unconfigured.
Create Products
As products and variants are created, their Internal Reference generates automatically from the resolved rule.
Clean Up Existing Catalogs
Preview and apply bulk generation for any product missing a reference, with conflicts flagged before you apply.
See it in action
From rule configuration to a cleanly referenced catalog.
The Reference Rules list shows every configured rule, global and per-category, with each rule's live Example Code so you can see the resulting pattern at a glance.
Build a rule from ordered components — static text, category name, product name, variant attributes and a zero-padded sequence — with separator and case options, and watch the Example Code update live.
The bulk generation wizard previews the current and proposed code for every targeted product and flags conflicts — no sequence number is consumed until you apply.
Every product form gets an Auto-Generate toggle, a Reference Rule override, and a Regenerate Reference button for full manual control when it's needed.
Each variant receives its own distinct, correctly generated Internal Reference the moment it is created — the gap most competing apps still leave open.
A Reference Rule smart button on the category form is the entry point for category-level configuration, so setup lives right where categories are already managed.
Frequently asked
Does every product variant get its own Internal Reference?
Yes. References are generated on the variant itself, so each attribute combination — color, size and so on — gets a distinct, correct code, not just the parent product.
What happens to products that already have an Internal Reference?
Auto-generation only fills a blank Internal Reference. Existing codes are never overwritten unless you explicitly click Regenerate Reference or run the bulk wizard's Apply step.
Can I preview bulk changes before they are applied to my catalog?
Yes. The bulk generation wizard's Preview step shows the current and proposed code for every targeted product and flags conflicts — nothing is written and no sequence numbers are consumed until you click Apply.
Can I control which pattern rule applies to which products?
Rules can target a specific category, with ancestry fallback to a parent category's rule, or you can set a single global default rule. Any product template can also override with a specific rule via the Reference Rule field.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Configurable pattern rules auto-generate correct, unique Internal References for every product and variant, with a dry-run bulk wizard to clean up existing catalogs.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 687 |
| Technical Name |
cerevantix_auto_generate_product_internal_reference |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module