Skip to content
    Supply Chain Analytics

    Performance reporting your team actually trusts.

    End-to-end KPIs across your ERP, TMS, and WMS — with proactive issue prioritization that surfaces what's costing you margin before the next dashboard refresh.

    • Live KPIs across order, shipment, and inventory data
    • Drill from a metric to its root cause in one view
    • Anomalies surfaced before they hit the QBR deck
    Performancelast 30d
    Live
    OTIF
    94.2%+2.1
    Lead time
    11.4d−0.6
    Exception MTTR
    3.8h−1.2
    Freight cost/unit
    $2.41+0.08
    6 sources reconciled

    Trusted by

    MatalcoDLAOIA GlobalIllyKingsdownLevitt SafetySquareInstoreDBWMatalcoDLAOIA GlobalIllyKingsdownLevitt SafetySquareInstoreDBW
    25+
    Pre-built KPIs
    < 90d
    To first reporting
    Real-time
    Anomaly detection
    Drill-to-root
    Every metric
    Under the hood

    The reporting layer your stack was missing

    Performance · last 30dLive
    OTIF+2.1
    94.2%
    Lead time−0.6
    11.4d
    Exception MTTR−1.2
    3.8h
    Freight $/unit+0.08
    $2.41
    OTIF (parcel)+0.9
    97.8%
    Dwell time−0.4
    1.2d

    The KPIs your team should already have

    Pre-built and wired to the operational data — not a six-month BI build.

    Drill to root cause5 levels
    1
    Network OTIF94.2%
    2
    MX region87.4%
    3
    Carrier C-0478.1%
    4
    Lane MX→US-TX71.2%
    5
    Customs hold (root)

    From KPI to root cause in one view

    Click a metric. Drill all the way down. No second tool.

    Anomaly streamlive
    [09:42:08]lane.MX-US.OTIFdrift −4.8σ
    [09:42:33]carrier.C-04.ETAvariance ↑
    [09:44:12]dc.04.dwelltrending up
    [09:48:21]promo.SKU-A.OOSpredicted risk
    [09:51:08]lane.EU-NA.OTIFback in range
    [09:52:30]anomaly.detectormodel retrained

    Metrics surface themselves

    Anomaly detection trained on your operational baseline. Not generic thresholds.

    Freight cost by lane · MTD$465k total
    US East → US West$148k
    MX → US Central$129k
    EU → NA Atlantic$84k
    APAC → US West$66k
    CA → US$38k

    Cost distribution your team can defend

    Reconciled across carriers, lanes, and modes — no manual spreadsheet roll-up.

    The shift

    From monthly PDFs to live operational reporting

    What changes when the reporting layer is wired directly to the data your team owns.

    Today
    PDFs and spreadsheets
    • Static reports, monthly cadence

      PDF decks and spreadsheets compiled by hand. By the time the QBR happens, the data is already a quarter old.

    • Can't drill from a KPI

      A metric is a number — not an answer. Drilling to the specific region, carrier, lane, or shipment means a second tool and a different team.

    • Anomalies missed until the QBR

      Drifts and trends go unnoticed because nobody's watching every metric. The first signal is usually a customer complaint or a margin miss.

    • Finance and ops disagree at month-end

      Reconciliation is a three-person spreadsheet exercise that takes a week. Different teams cite different numbers from different sources.

    With Orkestra
    Live operational reporting
    • Live KPIs, refreshed continuously

      Performance updates as the operational data arrives. The QBR view is the same view the team works from daily.

    • Drill to root cause in one click

      From network OTIF to the specific PO line in the same view. The metric and the explanation live together.

    • Anomalies surface in real time

      Detection models trained on your operational baseline. The metric flags itself when something meaningful moves — your team isn't hunting.

    • One data layer everyone reads from

      Same definitions, same source data, same drill paths. Month-end stops being a reconciliation project.

    FAQ

    Questions we get on every call

    Book your call

    Performance you can defend in the next QBR.

    30 minutes. We walk through a sample KPI tree on operational data like yours, show how a metric drills to root cause, and demonstrate anomaly detection on the metrics your team owns.