| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 1910 |
| Technical Name |
legion_itemcode_styleno |
| License | LGPL-3 |
| Website | http://www.bytelegions.com |
| Versions | 14.0 15.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 1910 |
| Technical Name |
legion_itemcode_styleno |
| License | LGPL-3 |
| Website | http://www.bytelegions.com |
| Versions | 14.0 15.0 18.0 19.0 |
Days Free Support 365
Custom Apps 1350+
Top Seller Of Odoo Marketplace
Happy Customers 8987+
Years of Experience 10+
Countries 50+
Talented Healers 100+
Industries Served 45+
Why Legion ItemCode StyleNo?
In fashion, textile, and manufacturing businesses, every product has an internal Style Number and Item Code used across the entire supply chain. Odoo's default product form has no such fields, meaning businesses manually track these codes outside the system causing mismatches between orders, invoices, and deliveries.
Get Instant Personalized Demo
View Our Services
Odoo Customization 365
Odoo Implementation 1350+
Odoo Support Marketplace
Odoo Integration 8987+
Odoo Migration 100+
Odoo Consultancy 50+
Odoo Hosting 100+
Industries Served 45+
Custom field add in sale order and order lines
Fetch data from sale order and order lines.
Custom field tree view side
Custom field add in invoice and invoice lines
Custom field add in purchase order and order lines
Sale Order Report
Invoice Report
Purchase Order Report
User go to search bar and search legion_itemcode_styleno then click on and install
Custom field Product side
Custom field add in sale order and order lines
Fetch data from sale order and order lines
Custom field tree view side
Custom field add in invoice and invoice lines
Custom field add in purchase order and order lines
Sale Order Report
Invoice Report
Purchase Order Report
Item Code and Style No in Product.
This module adds Style Number and Item Code fields to the product form, which then automatically flow through to sale order lines, purchase order lines, invoice lines, and delivery orders without any manual entry. It also adds PO Number and Customer Reference fields to sale orders, invoices, and delivery orders, with the sale order search extended to find records by PO Number directly. All custom reports are replaced with branded layouts showing these additional fields — sale order PDF, purchase order PDF, and invoice all display Style Number, Item Code, PO Number and Customer Reference in their printed documents.
Key Features:
- Style Number and Item Code on Products: Adds dedicated Style Number and Item Code fields to the product form, allowing businesses to store their internal product classification codes directly in Odoo. These codes are defined once on the product and automatically flow through to all related documents.
- Automatic Propagation to Sale Order Lines: Style Number and Item Code appear automatically in sale order line items as read-only related fields pulled from the selected product. Sales teams can verify correct product identification without manually cross-referencing external spreadsheets or catalogs.
- Purchase Order Line Integration:Both fields appear on purchase order lines as editable fields, allowing procurement teams to specify or verify style and item codes when placing orders with suppliers. This ensures supplier orders reference the same product classification as internal records.
- Invoice Line Tracking:Style Number and Item Code are visible and editable on invoice lines, ensuring customer invoices clearly reference the exact product codes. This is critical for customers who use these codes in their own internal systems for payment matching.
- PO Number and Customer Reference Tracking:Adds PO Number and Customer Reference fields to sale orders, invoices, and delivery orders with full search and group-by functionality. The global search is extended so users can find any order by typing the customer's PO number directly in the search bar.
Frequently Asked Questions
If I change the Style Number on a product, will it update existing orders?
No. Since order lines use related fields that read from the product, existing confirmed orders will reflect the updated value. However, for historical accuracy it is recommended to use standalone Char fields instead of related fields.
Why does Style Number appear blank on some delivery orders?
The StockRule._get_stock_move_values method propagates style and item codes from sale order lines to stock moves when the order is confirmed. If the sale order was confirmed before module installation, existing moves will not have these values.
Why are style_number and item_code readonly on sale order lines?
They are related fields pulling values from the product. To make them independently editable, change them to standalone Char fields with a separate mechanism to auto-populate from the product on selection.
Does this module work with multi-company setup?
Yes. The fields are added at the model level without any company restrictions, so they work across all companies in a multi-company Odoo environment.
Will PO Number transfer automatically from sale order to invoice?
Yes. The _prepare_invoice method in sale_order.py explicitly passes po_number and customer_ref to the invoice creation dictionary, ensuring these values transfer automatically when creating invoices from sale orders.
Latest release
Top Contributors
Mr. Kamran Yasin
Senior Full Stack Odoo Developer
Miss Rubab Khalil
Senior Odoo Functional Consultant
Mr. Muneeb
Senior Full Stack Odoo Developer
Mr. Wasif Yasin
Senior Full Stack Odoo Developer
Mr. Hamza Khalil
Senior Full Stack Odoo Developer
Please log in to comment on this module