How to find the late purchase orders that matter in Odoo

What Odoo already gives you

In Odoo Inventory and Purchase, everything you need to judge a late purchase order already exists, spread across views built for different jobs:

• Purchase orders (Purchase > Orders): each line carries an *Expected Arrival* date.
• Receipts (Inventory > Operations > Receipts): incoming transfers with a *Scheduled Date*. The *Late* filter shows the ones whose date has passed.
• The Forecasted report of a product (the *Forecasted* button on the product): on hand, incoming and outgoing quantities in date order.
• Moves History (Inventory > Reporting): every done stock move, which gives you a usage history.
• Reordering rules: the minimum and maximum quantities you set per product and location.

Each one answers part of the question. None of them ranks your late receipts by the stock risk behind them. A past-due purchase order list sorted by date tells you who is late, not who to call first.

The method, step by step

1. List the late receipts

Open Receipts, apply the *Late* filter, group or export by product with vendor, quantity and scheduled date. If your vendors confirm dates, note the orders never confirmed: their date is still your request.

2. Get stock and usage for each product

Take on-hand quantity per product and warehouse. For usage, export Moves History over a fixed window, for example the last 12 weeks, and keep the moves that leave stock for consumption or delivery. Use the same window for every product.

3. Compare days of cover with the real arrival date

Days of cover = on-hand quantity / average daily usage. For each late receipt, take the date you now expect it. Check the product's Forecasted report for another incoming quantity that arrives earlier. If cover runs out before any receipt, the line is a shortage risk.

4. Sort by days of cover, shortest first

Among the shortage risks, the product with the fewest days of cover goes to the top. That is your chase list for today. For each line, write down stock, usage, cover, the expected date and days late: when you call the supplier, you are discussing facts.

Illustrative example, not a customer result

Two lines from the same Late receipts list:

• Line A, gearbox seal kit: 11 days late. 1,200 on hand, usage of about 20 a day: 60 days of cover. Another receipt is scheduled next week.
• Line B, PCB assembly: 2 days late, never confirmed by the vendor. 45 on hand, usage of about 15 a day: 3 days of cover. No other incoming quantity.

Sorted by days late, line A comes first. Sorted by days of cover, line B does, and line B is the one that can stop production this week.

Where the manual method breaks

• It does not scale. Checking the forecast product by product works for ten late lines, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy products make a 12-week average misleading. Flag them rather than trusting the number.
• Dates are only as good as their maintenance. If supplier updates are not entered, the line still carries the original date.
• Days of cover tells you when a product runs out, not which manufacturing order or customer order it affects. Linking the two still needs your planners and your bill of materials.

How WERISCO does it

WERISCO automates the data work behind these steps: it reads every open receipt, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. For a first supply chain audit, it starts from two exports you can pull from Odoo today: on-hand quantity by product and open purchase order lines. The Odoo connector, which reads stock, purchase orders and stock moves through Odoo's external API, is validated in our lab, not yet on a customer database. It reads only; nothing is written back to Odoo, and your team decides what to chase.