Branch Transfers
Move stock between branches in two clicks — no transit locations, routes or stock rules to configure by hand.
Request a demoThe problem
Moving goods between branches in standard Odoo means wiring up transit locations, routes, stock rules and inter-company rules by hand — every warehouse, every time. It's slow, error-prone, and impossible to audit.
What it does
One document with a clear workflow — draft → approval → dispatch → transit → receipt — that replaces the whole manual maze. It self-configures on install and gives you full traceability from move line to transfer.
Key features
|
✓
Role-based access levelsEach user gets the right level for their job: branch operators see and act only on their assigned branches, managers get full control. Permissions enforced per branch, automatically. |
✓
Transfer dashboardA visual control center to see every transfer at a glance — to approve, to dispatch, in transit, received — filtered by role and branch. |
|
✓
Reordering-rule automationWire branch transfers into Odoo's replenishment engine: reordering rules raise inter-branch (and inter-company) transfer requests on their own, grouped and ready to approve — no manual document. |
✓
Push & pull flowSend from origin or request from destination — one document with built-in approval, dispatch, transit and receipt. |
|
✓
Auto-setup on installOperation types, sequences and transit locations are created for every warehouse automatically. Zero manual routing. |
✓
Force availabilityDispatch the approved quantity even when the system shows no stock yet — for when the goods are physically there but not registered. |
|
✓
Discrepancies under controlDifferences on receipt are logged automatically, classified by reason (damage, theft, miscount, transit loss, excess) and either auto-adjusted or held for manual review. |
✓
Return to sourceReverse a received transfer back to its origin in a single click — fully traceable. |
|
✓
Multi-company & inter-companyMove stock between related companies with an optional inter-company adjustment entry or invoice, plus product-company restriction checks. |
✓
Portal & PDFBranches validate receipts from the portal without full backend access, and print an internal transfer note (remito). |
How it works
|
1
|
Install & forget the setup Transit locations and operation types are created automatically for every warehouse. |
|
2
|
Create one transfer document Push from origin or pull from destination — approval, dispatch and transit built in. |
|
3
|
Receive with full control Handle partials, discrepancies and returns, all auditable and traceable. |
Built by an Odoo partner who runs the business, not just the software
Need a tweak, a custom feature or a demo on your data? Talk to us.
Contact support| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) |
| Lines of code | 2824 |
| Technical Name |
inveria_branch_transfer |
| License | OPL-1 |
| Website | https://www.inveria.com.ar |
Branch Transfers
Prerequisites
- Odoo 19
- Depends on: stock, mail, portal, product
Installation
- Copy the module into your addons path.
- Update the apps list.
- Install "Branch Transfers" from the Apps menu. Operation types and transit locations are created automatically for every warehouse in the group.
Configuration
- Two security groups are provided: User (operates its assigned branches) and Manager (full access, can reconfigure).
- Assign allowed warehouses per user via the allowed_warehouse_ids field on res.users.
- Optional inter-company behaviour (adjustment entry or invoice) is configured in Settings.
Support
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