Integrates delivery carrier with base_location, to allow to use zip codes in the delivery methods' destinations.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you restrict a delivery method to specific zip codes, so the carrier is only offered when the customer's address matches one of the listed zip codes.
This module adds a new field called "Zip codes" to delivery methods (carriers). You can find it on the delivery method form, right after the list of cities, and you can add as many zip codes as you need using tags.
When Odoo checks whether a delivery method is available for a customer address, it now also looks at the zip code. If you have entered zip codes on the carrier, the address must match one of them; otherwise the carrier is not offered for that address. The comparison ignores upper/lower case differences.
- Adds a "Zip codes" field to
delivery.carrier. - The field links to the zip code records from the location module (
res.city.zip). - Extends the address matching rule (
_match_address) so the zip code is taken into account. - If no zip codes are set on the carrier, the previous behaviour is kept.
- The field appears on the delivery method form, after the cities field.
It works together with the city-based restriction module, so you can limit a delivery method by both cities and zip codes. It touches the delivery carrier configuration and the address matching used when choosing shipping options.
Depends on
Models and fields (1)
- delivery.carrier · extends an existing modelzip_ids (Zip codes)
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/delivery-carrier.
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.