Sale Order Import with Extended Addresses
This module implements correct parsing of partners' addresses from files when importing sale orders. It extends the default behavior to handle street name and number according to module base_address_extended.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0When importing sale orders from files, this module splits the customer's street address into street name and house number so that the extended address fields are filled correctly.
This is a small glue module that works together with the sale order import tool and the extended address feature. It does not add any new screen or menu of its own; it changes what happens behind the scenes while importing sale orders from a file.
When the import creates a new customer because the address in the file does not match an existing contact, the module takes the street text coming from the file and separates it into a street name and a house number. The street name is stored in the street name field, the number in the street number field, and any extra part (such as a box or suffix) in the second street number field.
- If no street name can be detected, the whole street text is kept as the street name.
- If no number is found, the number fields are simply left empty.
- Existing values already provided for the number fields are not overwritten.
This only affects the customer creation step of the sale order import wizard (sale.order.import). It relies on the standard address fields added by the extended address module, so imported contacts follow the same address format as manually created ones.
Depends on
Models and fields (1)
- sale.order.import · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/edi.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.