replenishment_graph_widget

A reordering rule is two numbers, a minimum and a maximum, and the behavior they produce is a saw tooth: stock falls to the minimum, an order arrives, stock jumps to the maximum, and the cycle repeats. Explaining that from two numbers is hard; showing it is easy.

This widget draws that picture. It takes a JSON payload computed by the server and renders a chart with three lines: a horizontal maximum, a horizontal minimum, and the stock curve between them. The part of the curve that is a projection rather than a record is drawn dashed.

Around the chart, the same payload supplies the figures the dialog prints: quantity on hand, daily demand, average stock, ordering period, lead time and the unit of measure. All of that is decided in Python; the widget only renders.

Reordering parameters are usually set once and then argued about. The curve is what turns that argument into a conversation, because everyone can see what a given minimum and maximum actually produce: how often you would order, how much stock you would carry on average, and how close to zero the trough gets.

The projection matters as much as the history. Buyers do not need to know what stock did last quarter so much as what the current parameters imply, which is why Odoo 19 replaced the older history widget with this forecast-shaped one. If your team learned the old panel, that change is worth pointing out during an upgrade.

The chart is deliberately not interactive. No tooltips, no legend, no zoom. It is there to make a shape obvious, and the precise numbers are printed beside it rather than hidden behind a hover.

The core usage

<field name="json_replenishment_graph" nolabel="1"
       colspan="2" widget="replenishment_graph_widget"/>

No options. The field holds the JSON the server computed for that reordering rule.

The chart part of the payload

{
  "x_axis_vals": ["W1", "W2", "W3"],
  "max_line_vals": [...],
  "min_line_vals": [...],
  "curve_line_vals": [...]
}

Three datasets plus the category labels. The dashed segment is decided from the last x value, not from a flag in the data.

The summary part

{
  "product_uom_name": "Units",
  "qty_on_hand": 120,
  "product_min_qty": 50,
  "product_max_qty": 200,
  "daily_demand": 8,
  "average_stock": 125,
  "ordering_period": 14,
  "lead_time": 5
}

Read by individual getters and printed by the template beside the chart.

Three details in the chart configuration are worth pulling out, because none of them is obvious from the rendered result.

The dashed projection is decided geometrically rather than by a flag. A segment callback compares each segment's first point against the last value on the x axis, and applies a dash pattern when they match. In other words, the dashing starts where the recorded data ends, and the server controls that boundary purely by how it orders the axis values.

The y axis is forced. Rather than letting the chart library choose ticks, the widget injects the minimum and maximum quantities into the tick list before labels are computed, and then a label callback prints a value only if it is one of those two. The axis bounds are padded ten percent beyond each, so the horizontal lines never sit on the frame.

Interaction is switched off deliberately: the legend is hidden and tooltips are disabled. Combined with the point style being suppressed on all three lines, the result reads as a diagram rather than a chart you can interrogate.

One more thing the widget does at startup: it resolves whether the user belongs to the unit of measure group, alongside loading the chart library, so the template can decide whether to print the unit beside the quantities.

The version story is a replacement rather than a rename. Odoo 16 through 18 registered a replenishment history widget in this same file and this same dialog; Odoo 19 removed it and registered this graph widget in its place. Anything referring to the old name will fall back to the field's type widget.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify the page after release.

Same chart, new plumbing. The manual library loading, canvas reference and destroy effect are replaced by a shared chart hook that takes the configuration getter. The scatter configuration itself, including the dash rule, the forced ticks and the disabled tooltips, is unchanged.