qty_at_date_widget

Every sale order line in a stock-enabled Odoo carries a small chart icon next to the quantity. That icon is qty_at_date_widget, and it answers the seller's real question at quotation time: will we actually be able to deliver this line on the promised date?

The widget itself stores nothing and takes no options. The server computes the raw ingredients, forecasted quantity at the delivery date, free stock today, the quantity still to deliver, an expected date for incoming stock, and the widget combines them client side into one binary verdict: normal icon or red icon. Clicking it opens a popover with the numbers behind the verdict and a button into the full forecast report.

This is the widget that moves stock checking from a warehouse afterthought to the moment of sale. A salesperson typing a quotation sees red on a line the instant the promise becomes risky, before confirming anything, and the popover's Forecasted Stock and Available rows give the exact shortfall without leaving the order. The View Forecast jump lands in the replenishment picture already filtered to the affected moves, so the fix, a purchase, a transfer, a date change, starts one click from the symptom.

The verdict logic is deliberately stage-aware. On draft quotations it forgives make-to-order products, their stock is expected to be procured, while on confirmed orders it also flags lines whose incoming stock arrives later than the promised date. That distinction is exactly the difference between do not promise this and this promise is now late, and the widget encodes it for free.

How core places it

<field name="qty_delivered"/>
<widget name="qty_at_date_widget" width="20px"/>

From the order line list in sale_stock/views/sale_order_views.xml; the line form dialog places the same element after the unit of measure.

The verdict, as computed in the source

// quotations (draft, sent)
will_be_fulfilled = virtual_available_at_date >= qty_to_deliver
forecasted_issue  = !will_be_fulfilled && !is_mto

// confirmed orders (state == 'sale')
will_be_fulfilled = free_qty_today >= qty_to_deliver
will_be_late      = forecast_expected_date > scheduled_date
forecasted_issue  = !will_be_fulfilled || will_be_late

The 19 release added the piece users had asked for since sale lines learned flexible units: dual-unit display. When the popover opens, the widget now reads the line's UoM and the product's base unit over RPC, converts virtual_available_at_date and free_qty_today through the two factors, and prints the converted figures in a muted second line whenever the units differ. So a line sold in boxes shows the forecast in boxes and, underneath, in the units the warehouse counts. One source quirk: the 19 code fetches the unit's rounding field alongside factor and then never uses it, rounding is hardcoded to one decimal via roundPrecision, and the development branch quietly drops the dead read.

The popover template is stage-aware beyond the icon: quotations for MTO products replace the stock rows with a plain Expected Delivery line, confirmed orders show availability against today's free stock, and the whole popover positions above the icon. The forecast jump passes move_to_match_ids and the line id so the report can highlight exactly the moves belonging to this line, and on 16 it pointed at the old replenishment action, renamed to the forecast action in 17, with 18 fixing the warehouse context key from warehouse to warehouse_id.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. We read both files on the public development branch at the time of writing; the branch is unstable and this page will be re-verified after release.

The development branch splits the concept in two. A new simple_qty_at_date_widget lands in the sale module itself: four dependencies, no stock module needed, icon turns red when forecast at date is below the line's undelivered quantity. The sale_stock widget keeps the full verdict and popover, gains a source TODO to inherit from the simple one, migrates calcData onto computed() reactive state, and drops the unused rounding read. Patches on calcData timing are the ones that will break.