This is a build-to-order module, not an instant apps.odoo.com download — there is no .zip to grab today. After purchase we run a short discovery call to confirm your KPI definitions, warehouse structure and Odoo version, then build, install and validate the module on your instance. Typical lead time is one working week depending on scope and how many custom metrics or integrations you need. You receive the addon as a Git repo plus a versioned .zip, installed and working on your environment, not just handed over as code.

Delivery includes a support window covering bug fixes, configuration questions and help reading the KPIs. We also keep the module compatible with the Odoo versions you run (17, 18 and 19) so an Odoo upgrade doesn't break your dashboard. Because you receive the full source in a Git repo, you own the code — you can extend it in-house or ask ECOSIRE for enhancements. Ongoing support and version-maintenance can be extended beyond the initial window under a support agreement.

Both. The core module depends only on the standard stock (Inventory) app, so it runs on Odoo Community and Enterprise for versions 17, 18 and 19. If you use Enterprise-only apps such as advanced Barcode or Quality, we can wire those data sources in as an optional dependency during scoping. We confirm your exact edition and version in discovery so the __manifest__.py declares the right dependencies.

No. The heavy aggregation runs on a scheduled ir.cron job (for example every 15 minutes) that rolls metrics into dedicated KPI records, so the dashboard reads pre-computed data instead of scanning millions of stock.move rows on every page load. It reads from your existing inventory records and never modifies your operational picking, receiving or transfer flows — it's a reporting layer on top of the data you already generate.

Yes — that's the whole point of building it to order. Metric definitions are set during discovery: where your dock-to-stock clock starts and stops, what counts as a pick error, whether a line is measured per SKU or per move line, and how shifts and breaks affect labor utilization. We can also add warehouse-, zone- and team-level breakdowns and expose the data over Odoo's XML-RPC/JSON-RPC API if you want to feed it into another system later.

Security is configured for your org using Odoo's standard mechanisms: ir.model.access.csv for model-level create/read/write/unlink rights, and ir.rule record rules for row-level scope. A typical setup lets operators see their own numbers, supervisors see their team or warehouse, and executives see everything — all mapped to Odoo security groups so it slots into your existing user roles.