| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Point of Sale (point_of_sale) • Discuss (mail) • Inventory (stock) |
| Lines of code | 1549 |
| Technical Name |
neurona_sale_center |
| License | OPL-1 |
| Website | https://neurona.cloud |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Point of Sale (point_of_sale) • Discuss (mail) • Inventory (stock) |
| Lines of code | 1549 |
| Technical Name |
neurona_sale_center |
| License | OPL-1 |
| Website | https://neurona.cloud |
| Versions | 18.0 19.0 |
Store sales attribution
Neurona Sale Center
Recover real store-by-store sales totals, even when salespeople rotate between shops, counters, and POS terminals. Sale Center assigns the most likely operating center to POS tickets, quotations, orders, and customer invoices, so commercial reporting reflects what actually happened on the ground.
Category: Sales
Use case: Store-level sales attribution
License: OPL-1
Editions: Community & Enterprise
Scope: POS, Sales, and customer invoicing
Why it matters
Accuracy: sales follow the real operating store, not only the salesperson
Continuity: standard Odoo Sales, POS, and Invoicing stay in place
Control: admins can review, correct, and recalculate history when needed
Trust: store-by-store analysis becomes easier to defend internally
Highlights
- Assign the right store across commercial documents
- Use real operational signals instead of late manual tagging
- Keep sales analysis cleaner by center
- Control overrides and corrections without operational chaos
- Understand where each attribution came from
- Repair historical data with recalculation tools
- Keep invoices aligned with the commercial origin
- Expose the center broadly, keep control narrow
- See exactly what is included in the module
- Evaluate where it creates the most value
- Review compatibility and scope notes
Why teams buy it
This module is built for businesses that sell through multiple stores, branches, counters, or POS terminals and need total sales by location to remain reliable even when the same team works across several places.
Best fit: retail, showroom, and branch operations that want stronger store-level commercial reporting without replacing standard Odoo documents.
Assign the right store across commercial documents
Sale Center turns store attribution into an explicit commercial dimension instead of leaving it to memory, side notes, or downstream spreadsheet fixes.
Dedicated sale-center master data
- Create a clear list of operating stores, counters, or branches.
- Work with a controlled master dimension instead of ad hoc document notes.
- Make store ownership visible directly on commercial records.
Automatic attribution on live operations
- Keep POS tickets tied to the operating terminal or session.
- Assign the most likely center on quotations and sales orders.
- Bring that context into customer invoices when the flow supports it.
Result: stronger store ownership on the documents that drive day-to-day sales reporting.
Use real operational signals instead of late manual tagging
The module relies on evidence that already exists in the operation, so attribution is based on how the business actually sold, not only on what someone remembers later.
POS-driven evidence
- Link each POS configuration to its operating center.
- Use recent POS activity as the strongest clue for the responsible salesperson.
- Capture the real store or counter behind the transaction.
Fallback and inheritance logic
- Use controlled user fallback rules where stronger evidence is missing.
- Inherit the center from linked sales orders whenever the invoice flow allows it.
- Keep attribution coherent across related documents.
Keep sales analysis cleaner by center
Store attribution only matters if teams trust it. The objective here is better reporting confidence, not more admin burden.
Cleaner analysis by store
- Expose the center as a usable reporting dimension in standard analysis views.
- Reduce ambiguity in store-level sales and invoicing totals.
- Give managers a more credible operational view by location.
Less downstream cleanup
- Capture attribution earlier in the workflow.
- Reduce late corrections once documents already exist in the system.
- Improve consistency between live operations and reporting output.
Control overrides and corrections without operational chaos
Sale Center is designed to stay light for daily users while still giving administrators the governance they need.
Simple operating model
- Maintain centers as standard business records.
- Link POS terminals to the right center once.
- Keep the attribution model understandable for admins and users alike.
Controlled override and correction
- Allow explicit manual correction when business reality requires it.
- Preserve source visibility instead of hiding exceptional cases.
- Keep corrective actions traceable and auditable.
Understand where each attribution came from
A good attribution model should not feel magical. Teams need to understand why a document ended up under a given store.
| Signal | Typical source | Operational value |
|---|---|---|
| POS linkage | POS terminal or session connected to a center | Captures the real store or counter behind the sale. |
| User fallback | Responsible user with a controlled fallback center | Provides a baseline when stronger store evidence is missing. |
| Document inheritance | Invoice linked to one or more sales orders | Keeps downstream accounting aligned with upstream commercial origin. |
Repair historical data with recalculation tools
When center definitions evolve or legacy records need cleanup, administrators need a safe recovery path instead of one-by-one document edits.
Mass recalculation tools
- Recompute attribution by company and date range.
- Limit recalculation to empty centers or force a wider correction when needed.
- Avoid manual cleanup on large historical datasets.
Protected historical intent
- Keep manual overrides protected unless admins explicitly force recomputation.
- Make historical correction deliberate rather than accidental.
- Preserve trust when old sales data needs repair.
Keep invoices aligned with the commercial origin
Customer invoices should not lose the store context that existed when the sale actually happened.
Inheritance where possible
- Bring the center from linked sales orders into the invoice flow.
- Reduce divergence between commercial and accounting documents.
- Keep attribution coherent after confirmation and invoicing.
Honest handling of mixed origin
- Detect invoices that combine lines from more than one center.
- Mark them as mixed instead of forcing a misleading single assignment.
- Preserve clarity for finance, operations, and reporting teams.
Expose the center broadly, keep control narrow
Most users only need to see attributed centers on documents and reports. A much smaller group should define centers or run corrections.
Operational visibility
- Show attributed centers in standard commercial flows.
- Keep day-to-day users focused on documents and outcomes.
- Support clearer internal conversations around store performance.
Admin governance
- Reserve center definitions and recalculation powers for administrators.
- Keep exceptional corrections explicit.
- Reduce the risk of casual manual tampering.
What is included in the module
Included scope
- Sale center master data with POS linkage and user fallback support.
- Automatic assignment on POS tickets, quotations, sales orders, and customer invoices.
- Traceable assignment sources plus recalculation tools for controlled correction.
Outside scope
- No stock-picking attribution layer.
- No commissions engine or BI dashboard replacement.
- No redesign of standard Odoo commercial documents.
Where it creates the most value
Operational value
- Clarifies which store really produced each sale.
- Supports businesses where sales staff rotate between locations.
- Creates a more defensible view of store performance over time.
Typical environments
- Retail groups with multiple POS endpoints.
- Showrooms, counters, and branches sharing the same salespeople.
- Teams that need better store totals without replacing standard Odoo flows.
Compatibility and scope notes
Supported environments
- Dedicated packages for Odoo 18 and Odoo 19.
- Community and Enterprise compatible.
- Standard dependencies:
sale,account,point_of_sale.
Important scope notes
- Built for commercial attribution, not full financial or logistics allocation.
- Best results come from meaningful POS mapping and sensible fallback rules.
- Designed to strengthen reporting confidence without replacing broader analytics stacks.
Bottom line: if you need cleaner sales totals by store inside standard Odoo, Sale Center gives you a focused and traceable way to get there.
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