Skip to Content

Stock Statistical Orderpoint

by
Odoo

$ 351.77

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Inventory (stock)
• Purchase (purchase)
• Discuss (mail)
• Invoicing (account)
Lines of code 1679
Technical Name stock_statistical_orderpoint
LicenseOPL-1
Websitehttp://www.sandas.eu
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Inventory (stock)
• Purchase (purchase)
• Discuss (mail)
• Invoicing (account)
Lines of code 1679
Technical Name stock_statistical_orderpoint
LicenseOPL-1
Websitehttp://www.sandas.eu
Versions 18.0 19.0

Odoo Inventory Management

How to Automatically Calculate Optimal Stock Levels

Automate inventory planning with Odoo, reduce warehouse costs, avoid stockouts, and make replenishment decisions based on real data instead of guesswork.

Effective inventory management is one of the most critical areas of business, directly impacting profitability. Excess inventory ties up capital, while insufficient stock leads to lost sales.

By using Odoo with Statistical Orderpoint functionality, inventory planning becomes automated and based on real data rather than guesswork.

This is especially relevant for growing companies, where manual planning becomes too slow and inefficient. An automated solution saves time and reduces the risk of human error.

What is a Statistical Orderpoint in Odoo?

Statistical Orderpoint is an advanced inventory management method that automatically determines the minimum quantity and maximum quantity for each product and warehouse location.

The system analyzes:

  • historical sales
  • stock movements
  • supplier lead times
  • demand fluctuations

This allows you to accurately determine when and how much to reorder. Unlike traditional methods, the system adapts to real conditions. If demand increases or decreases, stock levels are adjusted automatically.

How does automatic inventory calculation work?

Odoo analyzes data daily and updates orderpoints.

Main steps:

  1. Sales data is collected.
  2. Average daily demand is calculated.
  3. Demand variability is assessed.
  4. Supplier lead time is factored in.
  5. The desired service level is applied.

The minimum stock level is calculated using the formula:

Min = μLT + Z × σLT

Where:

  • Z — Z-score based on the desired service level.
  • σLT — demand variability during the lead time.
  • μLT — average demand during the lead time.

This means the system not only knows how much you sell, but also accounts for risk. In practice, this helps avoid unexpected stockouts and reduces unnecessary overstocking.

Why is Odoo inventory optimization useful?

  • Lower warehouse costs: automated calculations help reduce excess inventory.
  • Fewer stockouts: service level settings help control risk.
  • Data-driven decisions: replenishment is based on real data, not intuition.
  • Automated operation: the system updates data without manual intervention.

Replenishment dashboard: fast decision-making

Odoo provides a clear overview of inventory status:

  • 🔴 Out of stock
  • 🟠 Critical level
  • 🔵 Excess inventory
  • ⚫ Normal level

One of the most important metrics is Days of Cover, which shows how many days the current inventory will last. This allows managers to quickly understand the situation and take action before actual shortages occur.

Anomaly detection: when the system alerts you to risk

Odoo analyzes min/max changes and detects unusual fluctuations. If the change is too large, the system flags it as an anomaly.

This helps to:

  • identify errors
  • detect changes in demand
  • respond to changing market conditions

This allows you not only to react to problems, but also to anticipate them in advance based on data trends.

Odoo warehouse management dashboard
Example of anomaly detection in the Odoo inventory dashboard.

AI analysis in Odoo

Using artificial intelligence, Odoo can explain anomalies:

  • why demand has changed
  • whether it is a one-time event
  • what actions to take

This is especially useful for larger businesses with complex logistics. AI provides an additional layer of insight that helps teams make faster and more informed decisions.

How to get started?

To enable automated inventory management in Odoo:

  1. Mark products and locations as “Use in Orderpoint”.
  2. Set the analysis period.
  3. Select the service level.
  4. Verify supplier lead times.

After that, the system starts operating automatically. At the beginning, it is recommended to monitor the results and adjust the settings according to your business specifics.

Odoo ERP illustration

Who is it best suited for?

This solution is ideal for:

  • e-commerce
  • wholesale trade
  • manufacturing companies
  • businesses with a large number of SKUs

It is especially useful for fast-growing companies where inventory management becomes a critical operational factor.

Summary

By using Odoo with Statistical Orderpoint functionality, companies can reduce warehouse costs, avoid stock shortages, automate replenishment processes, and make more accurate inventory decisions.

The main benefit is that replenishment planning becomes based on actual demand, supplier lead times, demand variability, and a defined service level instead of manual estimates.

Statistical Orderpoint — User Guide

What this module does

The module automatically calculates and maintains minimum stock levels for each product based on real historical consumption data. Instead of guessing how much safety stock to keep, the system analyses past warehouse movements, accounts for supplier lead times, and sets statistically sound replenishment rules for each product and location independently.

Every change to a min or max level is recorded. Unusual changes are flagged automatically using statistical anomaly detection, and an optional AI explainer can describe why a change looks abnormal.

Initial Setup

Required flags

Before the module can generate orderpoints you must enable three things:

  • Stock location form
    • Field: Use in Orderpoint
    • Description: Marks this location for automatic calculation
  • Product or Product category form
    • Field: Use in Orderpoint
    • Description: Includes this product (or all products in the category) in calculations

Which level (product or category) is active is controlled by Usage Level in Settings.

Settings

Open Inventory > Configuration > Settings and scroll to the Order Points block.

  • Statistical Period (default: 30 days) How many past days of movements to analyse
  • Usage Level (default: Product) Whether flags are read from the product form or the category form
  • Internal moves delay (default: 1 day) Extra lead time added for internal warehouse transfers
  • Service Level (default: 0.95) Target stock availability (0–1). Higher values increase safety stock
  • Default Lead Time (default: 7 days) Fallback lead time when no supplier lead time is available
  • Min/Max anomaly Z-score (default: 2.0) Sensitivity of anomaly detection
  • Anomaly Explainer AI Agent AI agent used to generate explanations
  • Exclude Extreme Demand Days (default: Off) Removes the highest and lowest consumption days before calculations
  • Calculations Debug in Log (default: Off) Enables detailed calculation logging

Service level hierarchy

  1. Product service level (if set)
  2. Category service level
  3. Company default service level

How Orderpoints Are Calculated

The scheduled task runs automatically every night at 03:00.

For each eligible product–location pair:

  1. Retrieves all done outgoing stock moves for the statistical period
  2. Aggregates total daily consumption
  3. Optionally removes extreme days
  4. Calculates mean usage and standard deviation
  5. Determines lead time:
    • Uses supplier lead time if available
    • Otherwise computes from purchase history
    • Falls back to default lead time
  6. Converts service level to a Z-score
  7. Calculates minimum quantity:
Min Qty = Z-score × StdDev(lead-time demand) + Avg(lead-time demand)

Max quantity is initially set equal to Min Qty.

  1. Creates or updates the orderpoint

Note

  • Products with zero consumption remain at minimum = 0 (state: No data)
  • Kit products (phantom BOMs) are skipped

Replenishment Dashboard

Open Inventory > Operations > Replenishment

Stock health colours

  • Red — Out of stock (forecast ≤ 0)
  • Orange — Critical (below minimum threshold)
  • Blue — Overstocked (above maximum threshold)
  • Grey — No data (no consumption yet)
  • Black — OK or snoozed

Days of Cover

Shows how many days of stock remain at the current consumption rate.

Automatic flag

Indicates whether an orderpoint was created automatically.

Min/Max Change History

Navigate to Inventory > Reporting > Min Max Change.

Each record shows:

  • Date and time
  • Product and location
  • Previous and new values
  • Change amount
  • Z-score and anomaly flag

Anomaly Detection

Z-score formula:

Z = (current change − average of past changes) / standard deviation

If the absolute value of Z exceeds the configured threshold, the change is flagged as an anomaly.

Requires at least 10 prior change records for the same product–location pair.

Anomalies dashboard

Open Inventory > Reporting > Min/Max Anomalies.

You can filter by:

  • Date range
  • Product
  • Location
  • Category

Available views:

  • Graph view (trend over time)
  • Pivot view (aggregated breakdown)

AI Anomaly Explainer

Requires Odoo Enterprise with the ai module installed.

Explain a single anomaly

  1. Open an anomaly record
  2. Click Explain with AI
  3. Status becomes Pending
  4. Background cron processes and stores the result

Bulk explanation

  1. Select multiple records
  2. Click Explain with AI
  3. Records are processed in the background

Explanation status values

  • Pending — Waiting for cron
  • Done — Successfully generated
  • Error — Failed, check logs

Configuring the AI agent

Select the agent in:

Inventory > Configuration > Settings > Order Points

Legacy Migration

  • Store migration data in orderpoint.data.migration
  • Set configuration parameter:
migration.stock_migration_date = YYYY-MM-DD

The system blends legacy and new data over time using a decreasing weight.

Triggering the Calculation Manually

  1. Go to Settings > Technical > Scheduled Actions
  2. Find Automatic orderpoints
  3. Click Run Manually

Frequently Asked Questions

Q: Orderpoint not updated? Check that all required flags are enabled and Usage Level matches configuration.

Q: Minimum quantity looks incorrect? Adjust Service Level or enable extreme demand filtering.

Q: No anomalies detected? At least 10 prior records are required.

Q: AI explanation stuck on Pending? Check that the AI module and cron are working.

Q: Max value overwritten? Only happens on initial creation.

Q: Disable automatic management? Disable Use in Orderpoint or remove Automatic flag.

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.