产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $299.00 USD
- Odoo 版本
- 17, 18, 19
- 设置时间
- 21分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Multi-Branch / Multi-Location Operations Manager for Odoo
A Branch dimension across sales, purchase, stock, POS & accounting — branch-scoped access, sequences & reporting, below full multi-company.
$299.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
A new res.branch model with branch code, address, contact, linked warehouse and company — the single source of truth for the Branch dimension.
branch_id Many2one added to sale.order, purchase.order, stock.picking, account.move, and pos.order (plus lines where reporting requires it), with sensible computed defaults from the user's branch.
Per-user allowed-branches Many2many on res.users plus a default branch, so a user's activity is pre-filtered to where they actually work.
Branch-scoped data isolation via ir.rule record rules and ir.model.access.csv — branch users see only their branch's documents while managers retain the consolidated view.
Automatic branch propagation with @api.onchange / @api.depends: the branch flows from order → order lines → generated invoice and stock moves without re-keying.
Per-branch document sequences using ir.sequence, so each location numbers its own quotations, sales orders, POs, invoices, and delivery orders (e.g. SO/DXB/2026/0001).
Consolidated and per-branch reporting: because branch is a real field, it appears natively in pivot/graph views, filters, group-bys, and saved searches across Sales, Purchase, Inventory and Accounting.
Branch dimension on journal entries and analytic reporting for a per-branch P&L and balance view alongside the company-level financials.
Inter-branch transfer workflow: request, approve, ship, and receive stock between branches with linked pickings and a full move audit trail.
POS integration: each POS session and order inherits the cashier's branch, keeping retail sales attributable to the correct location.
Branch-aware QWeb report layouts — invoices, delivery slips, and POs print the originating branch's name, address, and details in the header.
Optional branch filter widget / default filter on the main list views so users land on their branch's records first, with one click to see all.
Automated actions (base.automation / server actions) to auto-stamp branch on records created via imports, XML-RPC/JSON-RPC API calls, or portal actions.
Access-matrix configuration screen for admins to map users → branches → allowed operations without editing security files by hand.
Compatible with Odoo 17, 18 and 19 on both Community and Enterprise, adapting field placement to what each edition exposes (e.g. Enterprise-only apps).
关于此产品
Running several outlets, warehouses, or regional offices inside a single Odoo company usually forces an uncomfortable choice: either spin up a separate legal company per location — inheriting the full weight of inter-company invoicing, consolidation, and duplicated master data — or leave everything in one pool where every salesperson sees every order and every P&L blends into one number. The Multi-Branch / Multi-Location Operations Manager gives you the missing middle layer: a lightweight but pervasive Branch dimension that threads through Sales, Purchase, Inventory, Point of Sale, and Accounting without fragmenting your company into separate Odoo companies.
为什么选择 Multi-Branch / Multi-Location Operations Manager for Odoo
A new res.branch model with branch code, address, contact, linked warehouse and company — the single source of truth for the Branch dimension.
branch_id Many2one added to sale.order, purchase.order, stock.picking, account.move, and pos.order (plus lines where reporting requires it), with sensible computed defaults from the user's branch.
Per-user allowed-branches Many2many on res.users plus a default branch, so a user's activity is pre-filtered to where they actually work.
Branch-scoped data isolation via ir.rule record rules and ir.model.access.csv — branch users see only their branch's documents while managers retain the consolidated view.
Automatic branch propagation with @api.onchange / @api.depends: the branch flows from order → order lines → generated invoice and stock moves without re-keying.
Per-branch document sequences using ir.sequence, so each location numbers its own quotations, sales orders, POs, invoices, and delivery orders (e.g. SO/DXB/2026/0001).
At the data layer, ECOSIRE adds a branch_id Many2one (to a new res.branch model) onto the operational documents that matter — sale.order, purchase.order, stock.picking, account.move, pos.order, and their lines where reporting needs it. Each user is assigned one or more allowed branches via a Many2many on res.users, and record rules (ir.rule) plus ir.model.access.csv entries enforce that a branch-scoped user only reads and writes documents belonging to their branch — while managers keep the consolidated view. Because it is a genuine field on the models, the Branch flows automatically into pivot views, graph views, filters, and group-bys, so consolidated-versus-per-branch reporting is native rather than bolted on.
We wire branch defaulting the Odoo way: computed defaults derived from the user's branch, @api.onchange/@api.depends propagation from order to lines to the resulting invoice and stock moves, and per-branch document sequences (ir.sequence) so each branch numbers its own quotations, invoices, and delivery orders (e.g. INV/DXB/2026/0001 vs INV/AUH/2026/0001). QWeb report headers pick up the branch address and details, POS sessions inherit the operator's branch, and an inter-branch transfer workflow lets one location request and receive stock from another with a clean audit trail. Everything is delivered as a proper installable module — a versioned __manifest__.py, models, security CSV/XML, views, and reports — tested and installed on your Odoo 17, 18, or 19 (Community or Enterprise) by our engineers.
This is a build-to-order engagement, not an instant apps.odoo.com download. After purchase, an ECOSIRE Odoo engineer confirms your exact scope (which apps carry the Branch dimension, your access matrix, your sequence scheme), builds and hardens the module against your version and edition, installs it in staging, migrates your existing records with a branch backfill, and hands over the source. Typical lead time is 2–4 weeks depending on how many flows and the depth of the access model.
你得到什么
- Installable Odoo module (source code) — __manifest__.py, Python models, security (ir.model.access.csv + record-rule XML), views, and QWeb reports — for your target version(s): 17, 18, and/or 19.
- Scope-and-design document: the confirmed list of apps carrying the Branch dimension, your branch/access matrix, and the per-branch sequence scheme, signed off before build.
- Staging installation and configuration on your Odoo instance, including res.branch records, per-user branch assignments, and sequence setup.
- Data migration / backfill script that stamps branch_id onto your existing historical sales, purchase, stock, and accounting records where applicable.
- Admin & end-user documentation: how branches, access rules, sequences, and inter-branch transfers work, plus a short how-to for adding new branches later.
- A live handover / training session for your admins and key users, recorded for future reference.
- Post-go-live support window (bug fixes and adjustments) plus a written summary of upgrade considerations for future Odoo version jumps.
这是给谁的
Retail / franchise operations manager
Runs multiple stores or outlets on one Odoo instance and needs each location's sales, POS takings, and stock kept separate for accountability — but wants a single roll-up dashboard without maintaining a separate company per shop.
Multi-warehouse distribution / trading owner
Operates several warehouses or regional depots, needs branch-scoped delivery orders, per-branch PO numbering, and clean inter-branch stock transfers, while still consolidating purchasing and inventory value at the company level.
Finance controller / CFO of a multi-site SME
Wants a per-branch P&L and branch-tagged journal entries and invoice sequences for internal reporting and audit, without the overhead of inter-company eliminations that full Odoo multi-company would impose.
Odoo administrator / internal IT lead
Responsible for user access and data governance; needs record-rule-enforced branch isolation so staff only see their own branch's documents, configured through a maintainable module rather than ad-hoc filters and manual permissions.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Multi-Branch / Multi-Location Operations Manager for Odoo 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Multi-Branch / Multi-Location Operations Manager for Odoo，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Multi-Branch / Multi-Location Operations Manager for Odoo 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Branch dimension across sales, purchase, stock, POS & accounting | 包含 | Possible but you build every model extension and integration point yourself | Varies — often covers only a subset of apps | |
| Branch-scoped access enforced by record rules (ir.rule) | 包含 | Only if you design and test the security correctly | Sometimes; depth and correctness vary by author | |
| Per-branch document sequences (ir.sequence) | 包含 | You wire ir.sequence per journal/document manually | Sometimes included | |
| Consolidated + per-branch reporting out of the box | 包含 | Depends on how you model the field | Partial — usually per-app, not unified | |
| Inter-branch stock transfer workflow | 包含 | Built from scratch on stock.picking | Rarely included | |
| Keeps a single company (no inter-company overhead) | 包含 | Your call, but you own the design risk | Usually yes | |
| Built, installed & tested on your exact Odoo 17/18/19 + edition | 包含 | Only if you have in-house Odoo engineers | 不包括在内 | |
| Historical data backfilled with branch on existing records | 包含 | You write and run the migration | 不包括在内 | |
| Source code handover + upgrade notes + support window | 包含 | You already own it | Code yes, tailored support/upgrade usually no |
关于Multi-Branch / Multi-Location Operations Manager for Odoo的常见问题
How long does delivery take, and what happens after I buy?
This is a build-to-order engagement, not an instant download. Typical lead time is 2–4 weeks depending on how many apps carry the Branch dimension and how deep your access model is. After purchase, an ECOSIRE Odoo engineer confirms scope (models to extend, your branch/access matrix, sequence scheme), builds and tests the module against your exact version and edition, installs it in staging, backfills your existing records, and then hands over the source and moves it to production with you.
How is this different from Odoo's built-in multi-company feature?
Multi-company splits your data into separate legal companies and brings inter-company invoicing, consolidation, and duplicated master data. This module keeps everything in one company and adds a lightweight Branch dimension instead — a res.branch model, a branch_id field on your operational documents, record-rule-based access isolation, and per-branch sequences and reporting. You get location-level accountability and roll-ups without the overhead of eliminations and cross-company setup.
What support and updates do I get, and does it survive Odoo upgrades?
Every build includes a post-go-live support window for bug fixes and adjustments. Because the module is delivered as clean, versioned source with a proper __manifest__.py, it upgrades with your Odoo like any addon — we hand over written upgrade notes, and when you move to a new major version (e.g. 18 → 19) we can port and re-test it as a follow-on engagement. You own the code, so you're never locked to us.
Which Odoo versions and editions are supported?
Odoo 17, 18, and 19, on both Community and Enterprise. We adapt field placement and integration points to what your edition exposes — for example, Enterprise-only apps or accounting features — and confirm the exact target during scoping so the module installs cleanly on your instance.
Will branch-scoped users be truly prevented from seeing other branches' data?
Yes. Isolation is enforced at the ORM level via ir.rule record rules combined with ir.model.access.csv, not just hidden columns or UI filters. A branch-scoped user reads and writes only records for their assigned branch(es); managers and admins keep the consolidated view. Because it's server-side, the rules also apply to XML-RPC/JSON-RPC API access, imports, and automated actions.
Can the Branch dimension flow into my reports and printed documents automatically?
Yes. Branch is a real field on the documents, so it appears natively in pivot views, graph views, filters, and group-bys — you can build consolidated or per-branch views of sales, purchases, stock, and P&L without extra tooling. QWeb report layouts (invoices, delivery slips, POs) are extended so each printout shows the originating branch's name and address in the header.
相关模块
申请报价
Multi-Branch / Multi-Location Operations Manager for Odoo
A Branch dimension across sales, purchase, stock, POS & accounting — branch-scoped access, sequences & reporting, below full multi-company.
- A new res.branch model with branch code, address, contact, linked warehouse and company — the single source of truth for the Branch dimension.
- branch_id Many2one added to sale.order, purchase.order, stock.picking, account.move, and pos.order (plus lines where reporting requires it), with sensible computed defaults from the user's branch.
- Per-user allowed-branches Many2many on res.users plus a default branch, so a user's activity is pre-filtered to where they actually work.
- Branch-scoped data isolation via ir.rule record rules and ir.model.access.csv — branch users see only their branch's documents while managers retain the consolidated view.