| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Manufacturing (mrp) • Purchase (purchase) • Sales (sale_management) • Discuss (mail) |
| Lines of code | 955 |
| Technical Name |
codeerts_transaction_flow_visualizer_pro |
| License | OPL-1 |
| Website | https://codeerts.odoo.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Manufacturing (mrp) • Purchase (purchase) • Sales (sale_management) • Discuss (mail) |
| Lines of code | 955 |
| Technical Name |
codeerts_transaction_flow_visualizer_pro |
| License | OPL-1 |
| Website | https://codeerts.odoo.com |
| Versions | 18.0 19.0 |
Flow Visualizer Pro
See the whole story of any transaction on one screen.
An interactive map of every linked document, built with no code.
Sales, Purchases, Manufacturing, Deliveries, Invoices, Projects and Tasks, connected in a single visual flow chart you open straight from the record.
|
0
Code Required
|
Any
Odoo Model
|
1 Click
From the Record
|
Live
Real Odoo Data
|
v19
Compatible
|
What this module does
Odoo links your documents through smart buttons and origin fields, but once a chain grows, a Sale Order that creates a Purchase Order, a Receipt, a Manufacturing Order, several Invoices and a Project, there is no single screen that shows the whole picture. You end up clicking through menu after menu to trace where an order stands.
Flow Visualizer Pro adds a Flow Map entry to the Action menu of any record. Open it and the module builds an interactive flow chart of every related document, laid out left to right by how far each one sits from the record you opened. Each box is colored by document type, carries a status dot, and opens the real record in one click.
The difference in Pro: you decide which models get a Flow Map and which links it follows, entirely from a settings screen, with no development. It ships pre-configured for Sales, Purchase, Manufacturing, Inventory, Accounting, Projects and Tasks, and you extend it to any other model by ticking a few boxes.
|
🗺
One Screen, Whole Chain
Open the Flow Map and the full web of linked documents appears at once, color coded by type with directional connectors that show how the work flows. |
🧩
No-Code, Any Model
Add a model in Settings, tick the relations to follow, and a Flow Map appears in that model's Action menu automatically. No XML, no views, no developer. |
🔒
Read-Only and Secure
The map only reads data, it never writes. Every document is read as the logged-in user, so record rules and company access always apply. |
|
🎨 Color by Document Type
Sales, Purchase, Invoices, Transfers, Manufacturing, Projects and Tasks each get their own color, so you read the kind of document at a glance. |
🟢 Status at a Glance
A status dot on each box shows draft, in progress, done or paid, so delays and bottlenecks stand out immediately. |
|
🔗 Preview or Open Full
Click any box to preview the document in a popup, or use the expand icon to open the full form. The Flow Map stays in the breadcrumb for an easy way back. |
⚙ Built-in Cross-App Links
Ready-made links that are not simple fields, Sale Order to Purchase Order, Invoice to its source, Manufacturing to its transfers, switch on with a tick. |
|
🎛 Depth and Size Controls
Set how many hops out and how many documents each map explores, per model, so large chains stay fast and readable. |
🏢 Multi-Company Aware
Because the map reads as the current user, documents the user cannot see simply do not appear. Company and team rules are respected automatically. |
|
📦 Pre-Configured on Install
Installs with working maps for Sale Order, Purchase Order, Manufacturing Order, Delivery, Invoice, Project and Task. Edit or extend them freely. |
🚀 Self-Contained, No Libraries
The chart is drawn natively inside Odoo. No external services and no third-party chart libraries are loaded. |
How it works
1 |
Install, and it is ready
On install the module seeds working Flow Map configurations for the common Sales, Purchase, Manufacturing, Inventory, Accounting and Project documents. Nothing else to set up. |
2 |
Open the Flow Map from any record
On a Sale Order, Invoice, Manufacturing Order or any configured document, open the Action menu at the top and choose Flow Map. |
3 |
Read the chain visually
The map lays out every linked document left to right. Colors show the document type, status dots show progress, and connectors show direction. Click any box to preview it in a popup, or use the expand icon to open the full form. |
4 |
Add any model, with no code
In Settings, Technical, Flow Map Sources, click New, pick a model, and tick the relational fields the map should follow. Save, and a Flow Map appears in that model's Action menu right away. |
5 |
Tune depth and size
Per model, set how far the map reaches and how many documents it draws, so even large fulfillment chains stay fast and easy to read. |
The configuration, field by field
Each model that should get a Flow Map is one record under Settings, Technical, Flow Map Sources. Every field is point and click, no code:
|
Model
The model whose records get a Flow Map. Saving the record automatically adds a Flow Map entry to that model's Action menu. |
Relations to Follow
The relational fields the map walks from each record. The dropdown lists only that model's link fields, so you simply tick the ones to include (for a Sale Order: Invoices, Transfers, Projects, Tasks). |
|
Built-in Links
Pre-made cross-document links that are not simple fields, such as Sale Order to Purchase Orders, Invoice to its source, or Manufacturing to its transfers. Switch each on with a tick. |
Max Depth
How many hops out from the opened record the map explores. A depth of 3 reaches an order, its invoices, and the documents linked to those. |
|
Max Nodes
A safety cap on how many documents a single map draws, so even very large chains stay fast and readable. The map shows a "truncated" flag if the limit is reached. |
Active
Turns the Flow Map for this model on or off. Disabling it removes the Action-menu entry automatically, without deleting your configuration. |
Screenshots
THE WHOLE CHAIN ON ONE SCREEN: one Sale Order, its Purchase Orders, Receipts, Bills, Delivery, Project and Tasks
ONE CLICK FROM THE RECORD: open the Flow Map from the Action menu of any document
NO-CODE CONFIGURATION: choose any model and the relations the map follows
A SOURCE, FIELD BY FIELD: pick the model, the relations to follow, built-in links, depth and node caps
GROUP BY TYPE: one click rearranges the map into a column per document type
FOCUSED VIEW: status colors and connectors make the path easy to follow
Technical information
|
Version
19.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Apps Covered
Sales, Purchase, MRP, Stock, Accounting, Project
|
Technical name: codeerts_transaction_flow_visualizer_pro · Data stored: none, the map is built live and read-only
Frequently asked questions
Open the order, click the Action menu and choose Flow Map. The module draws an interactive chart of the linked purchase orders, receipts, deliveries, invoices, projects and tasks, all on one screen.
Yes. In Settings, Technical, Flow Map Sources, add a model and tick the relations to follow. A Flow Map entry then appears in that model's Action menu automatically, with no development.
No. The map is read-only and stores nothing. It builds live each time you open it and never writes to your records.
Yes. Every document is read as the logged-in user, so record rules, sales team and company access are always applied. Documents a user cannot see simply do not appear.
No. The map runs only when you open it, and each build is capped by a configurable depth and node limit, so even very long chains stay fast and stop at the limit.
Yes. It is built for Odoo 19.0 and runs on both Community and Enterprise.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency · Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
🏗️ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
🧩 Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
🔄 Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
🔌 Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
🔍 Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
🧑💻 Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
Odoo Certified |
6+ Years |
50+ Projects |
10+ Industries |
Need Help?
Questions, customization requests, or bug reports. We respond fast.
CODEerts · Response within 1-2 business days
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