Delivery Carrier Return Barcode Pattern
Adds a return_barcode_pattern field on carriers, allowing to parse the origin from the provided barcode.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you store a return barcode pattern on each delivery method so Odoo can read the original document reference from a carrier's return barcode.
This module adds one extra field to delivery methods (carriers): a return barcode pattern. You fill it in on the delivery method form, right after the production environment setting.
The pattern must be a valid regular expression; if you type something that is not valid, Odoo refuses to save and shows an error. The field's help text explains that the pattern is used to parse a return barcode coming from the carrier, and gives an example where the whole barcode is the sales order reference.
The module also adds a helper that, given a barcode, checks it against the patterns defined on the selected carriers (or on all active carriers when none is specified) and returns the list of origin references found. If nothing matches, it returns an empty list. This is a building block used by other modules or customisations to link a returned parcel back to its original document.
It does not add menus, reports, emails or scheduled actions. It only touches the delivery carrier model and its form view.
Depends on
Models and fields (1)
- delivery.carrier · extends an existing modelreturn_barcode_pattern
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.