OTIF Delivery Performance Analysis

The promised date

On-Time is judged against a single Promised Date (otif_target_date). For each delivery the app takes the first of these that is set:

1. the linked sale order's commitment date;

2. the delivery's Deadline (date_deadline);

3. the delivery's Scheduled Date (scheduled_date).

Scheduled Date is always present, so a delivery is never left without a promised date. For a meaningful On-Time figure, though, set a real customer commitment: enable Sales > Configuration > Settings > Delivery Date, then fill the commitment date on the sale order (under Other Info). It then flows through to the delivery and drives the metric.

What is measured

A delivery counts toward OTIF (otif_measured) only when all of the following hold, so each order's primary shipment is scored exactly once:

• its operation type is outgoing;

• its status is Done (validated);

• it is not itself a backorder of an earlier transfer.

On those deliveries the app sets On Time (date_done on or before the Promised Date), In Full (the transfer left no backorder behind), OTIF (both) and Delay (days) (days late, 0 when on time). Each flag is mirrored by a 0–100 score averaged by the graph and pivot, so a group average reads directly as a percentage. Fields recompute when the state, dates, backorder links or the order's commitment date change.

Access

The report reads standard stock.picking records, so it honours your existing delivery access rights and multi-company rules. The Inventory menu is open to Inventory users; the mirror under Sales is limited to the Salesperson group (sales_team.group_sale_salesman).

Opening the dashboard

Two menus point at the same report:

• Inventory > Reporting > Delivery Performance (OTIF)

• Sales > Reporting > Delivery Performance (OTIF)

It opens filtered to measured deliveries only, so drafts, receipts, internal transfers and backorder shipments never dilute the numbers. Three views are available from the switcher.

• Graph — a bar chart of the OTIF Rate by delivery month. A bar at 90 means 90% of that month's measured deliveries were on time and complete.

• Pivot — Customer on rows, Delivery Month on columns, with OTIF, On-Time and In-Full rates as measures. This is where you diagnose why OTIF moved: high In-Full but low On-Time means you ship complete but late.

• List — one line per delivery: reference, customer, source order, Promised Date, actual date, the On-Time / In-Full / OTIF toggles and Delay in days. Rows are colour-coded (green OTIF, red late, orange on-time-but-short) and read-only.

The search bar offers OTIF, Late and Short (not in full) filters, a This Year period filter, and Group By Customer or Delivery Month.

Worked example

You ship Deco Addict five June orders: four on time and complete, one two days late. In the pivot, June for Deco Addict shows On-Time 80%, In-Full 100% and OTIF 80%. Grouping the list by Customer with the Late filter surfaces the single slipping delivery, its Delay column reading 2.

The report is empty ("No deliveries to score yet")

Cause. Only completed outgoing transfers are scored. If none is validated to Done, or the only outgoing transfers are backorders, the population is empty.

Diagnosis. In Inventory > Operations > Deliveries, confirm you have Done transfers that are not themselves backorders.

Resolution. Validate outgoing deliveries; scores appear immediately.

OTIF looks unrealistically high (near 100%)

Cause. No commitment dates are set, so On-Time is judged against the delivery's own Scheduled Date — which it almost always meets, inflating the rate.

Diagnosis. In the list, compare the Promised Date with the order's commitment date. If it matches the internal scheduled date, commitments are missing.

Resolution. Enable Delivery Date in Sales > Configuration > Settings and populate commitment dates. New deliveries are then scored against the date the customer agreed to.

A partial delivery is flagged "not in full"

Cause. The transfer shipped short and spawned a backorder, so the order was not fully shipped on that transfer — this fails In-Full by design.

Diagnosis. Open the delivery and check its linked back orders.

Resolution. No fix needed — the flag is correct. Ship complete in one transfer to improve the rate. The follow-up backorder shipment is excluded from the measured population, so it does not double-count.

A validated delivery shows the wrong flag or date

Cause. The OTIF fields are stored computed values; they recompute when the state, dates, backorder links or the order's commitment date change.

Diagnosis. Confirm the delivery's Done date and the order's commitment date, and that the delivery is not a backorder.

Resolution. Correct the underlying date; the score recomputes automatically. If a bulk historical correction does not refresh, re-save one affected delivery to force it.

Patch upgrades (same series, e.g. 18.0.1.0.0 → later)

1. Back up your database and filestore first.

2. Replace the module folder with the newer build.

3. Restart Odoo with the module updated:

   ./odoo-bin -c your.conf -u bambooforge_otif -d your_db

4. Odoo applies any schema/data changes automatically. Your existing records and configuration are preserved.

Cross-version migration (e.g. Odoo 17 → 18)

Upgrading Odoo itself is a database migration handled by Odoo's standard upgrade tooling. When you migrate the database to the next Odoo series, install the matching build of this module for that series. Data created by this module carries over with the database migration.

What is removed

• The fields, views and analysis definitions this module added.

• The menus, actions, views and reports this module installed.

What is preserved

• Your standard Odoo data (partners, products, sales, invoices, inventory moves) is not deleted — this module only reads and annotates it; the underlying records stay.

• Attachments and chatter messages on standard records are kept.

As always, take a database backup before uninstalling in production.

18.0.1.0.0

Current release for Odoo 18.0. This build includes:

• Measure your On-Time In-Full (OTIF) delivery performance. See, per customer and per period, how often you delivered on time and complete.

• The supply-chain KPI your customers judge you by.

Feature additions and fixes ship as new builds on the Odoo Apps store; this page and the module's version reflect the current published release. Always keep the build matched to your Odoo series (see Upgrading & version compatibility).