What Tenoro reads and ranks
Tenoro ingests exceptions from your connected systems, computes downstream impact, and surfaces a single ranked queue. Here is what it covers.
Four exception families, one ranked queue
Each exception family carries different downstream signals. Tenoro reads signal patterns across all four and folds them into a single priority score.
Shipment delays
- ETA variance from carrier feeds
- Origin departure hold duration
- Customer delivery commitment date proximity
- Downstream order count at risk
Purchase order exceptions
- PO confirmation lag from supplier
- Partial receipt percentage
- Approval workflow hold duration
- Linked production or fulfillment orders
Inventory shortfalls
- Stock-on-hand versus committed quantity gap
- Reorder point breach timing
- Open sales orders dependent on this SKU
- Replenishment lead time versus need date
Carrier alerts
- Carrier reliability history for this lane
- In-transit status gap duration
- Delivery attempt failure count
- Last-mile commitment proximity
How the priority score is built
Each exception receives a score from 0 to 100 based on weighted signals. The weights reflect real-world impact, not exception source or arrival time.
From raw exception to ranked item
A stockout exception arriving in an ERP queue, and how Tenoro traces it to a delivery commitment and places it in the ranked list.
- 1 Tenoro reads the inventory shortfall from the WMS: stock on hand is 12 units, committed quantity across open orders is 47 units. Reorder lead time is 9 days.
- 2 Cross-referencing the OMS, Tenoro finds 3 customer orders containing this SKU, with the earliest delivery commitment in 5 days. The lead time does not cover the gap.
- 3 Tenoro traces whether a pending PO covers this SKU. PO-48821 is confirmed but delayed 6 days by the supplier. The buffer is gone.
- 4 The combined signal: stock gap, commitment breach in 5 days, no PO coverage. Tenoro computes a priority score of 87 and places this exception at position 1 in the queue.
- 5 The analyst opens their queue, sees the exception at the top with the cascade trace visible, and contacts the supplier directly. All context is on one screen.
What Tenoro does not cover
Clarity about scope is part of the product. Tenoro does not try to be a full supply chain visibility platform.
Customs and compliance exceptions
Trade compliance, import duty holds, and customs release exceptions require specialist knowledge of per-jurisdiction regulatory rules. Tenoro does not attempt to rank these.
Quality and returns exceptions
Product quality failures, return merchandise authorizations, and inspection holds are workflow exceptions that sit outside supply chain exception mechanics. Out of scope by design.
Financial approval exceptions
Invoice disputes, payment authorization holds, and credit limit flags are finance-domain exceptions. They may block orders but Tenoro does not ingest or rank them independently.
See Tenoro score your actual exceptions
Early-access onboarding includes a live session where we connect one integration and walk through a real ranked queue together.