This is a build-to-order engagement, not an instant download. Typical delivery is one working week from kickoff, depending on the state of your sales history and how deep the MPS/MRP integration needs to go. We work in stages: data assessment and forecast modeling first, then module build, then deployment to a staging database for your sign-off, and finally production go-live. You'll have checkpoints along the way rather than a single hand-off at the end.

Every engagement includes a defined post-go-live support and warranty window for bug fixes, forecast tuning, and questions from your team. Because you receive the full source code, the module is yours to keep and extend. We also offer ongoing support and Odoo version-upgrade retainers (for example, moving your build from Odoo 17 to 18 or 19) as a separate arrangement so the forecasting logic keeps working across future Odoo releases.

It works on both. The Master Production Schedule (MPS), MRP, reordering rules, and the ORM/security/cron building blocks we rely on are available in Odoo Community, and the module targets Odoo 17, 18, and 19. If you're on Enterprise, it also plays cleanly with the Enterprise Manufacturing and Inventory features. We confirm the exact edition and version during scoping so the delivered build matches your instance.

We don't publish a blanket accuracy number because it depends entirely on your demand patterns — steady, seasonal products forecast far better than brand-new or highly erratic SKUs. What we do commit to is measuring accuracy honestly: the module computes MAPE and bias per SKU automatically and shows forecast-vs-actual so you can see where it performs well and where human judgment should override it. For modeling we typically want 12–24 months of Odoo sales/delivery history; the more clean history you have, the stronger the seasonal signal.

No. The module writes forecasts into the planning layer (MPS demand and forecast inputs) and leaves your MRP execution, BoMs, routings, and reordering-rule logic intact — MRP simply replenishes against better numbers. Planners keep full manual override on every forecast line, changes are logged in the chatter, and access is scoped by record rules so nobody sees warehouses they shouldn't. We deploy to staging first and validate against your real data before anything touches production.

Yes. Planners can edit any forecast line directly, and the module ships with optimistic/base/pessimistic scenario variants you can compare side by side and promote into the MPS. Every override is auditable. If you later want new scenario logic or additional drivers (promotions, new-product introductions, external demand signals), those extend the same `demand.forecast` model — and since you own the code, either your team or ECOSIRE can build them.