---
title: "Supplier OTIF Scorecards: Measurement Rules, Tolerance Windows, and Review Cadence"
description: "How to build a supplier OTIF scorecard that holds up in a review: date basis, tolerance windows by commodity, the ERP data gap, metric weights, and review cadence."
image: https://tryleverage.ai/hubfs/blog-covers/cover-supplier-otif-scorecards-measurement-rules-tolerance-windows-review-cadence.png
---

[Skip to main content](https://tryleverage.ai/blog/pf/supplier-otif-scorecards-measurement-rules-tolerance-windows-review-cadence#main-content)

[![Leverage powered by Order.co](https://tryleverage.ai/hubfs/leverage-powered-by-order-co-white.svg) ![Leverage powered by Order.co](https://tryleverage.ai/hubfs/leverage-powered-by-order-co-white.svg) ![Leverage powered by Order.co](https://tryleverage.ai/hubfs/leverage-powered-by-order-co-white.svg) ![Leverage powered by Order.co](https://tryleverage.ai/hubfs/leverage-powered-by-order-co-white.svg)](https://tryleverage.ai)

- Show submenu for Platform Platform 
  
    - [CONNECT: Integrations](https://tryleverage.ai/integrations)
    - [PARSE: Document Parsing](https://tryleverage.ai/document-parsing)
    - [MEASURE: Supplier Performance](https://tryleverage.ai/supplier-performance)
    - [PAY: Trade Finance](https://tryleverage.ai/payments)
    - [ENGAGE: PO Automation](https://tryleverage.ai/purchase-order-automation)
    - [TRACK: Shipments](https://tryleverage.ai/shipment-tracking)
    - [COPILOT: AI Agents](https://tryleverage.ai/artificial-intelligence)
- Show submenu for Case Studies Case Studies 
  
    - [Manufacturing](https://tryleverage.ai/case-study-manufacturing)
    - [Distribution](https://tryleverage.ai/case-study-distribution)
    - [Pharma & Biotechnology](https://tryleverage.ai/case-study-pharma-biotechnology)
    - [Food Production](https://tryleverage.ai/case-study-food-production)
    - [Furniture](https://tryleverage.ai/case-study-furniture)
    - [Supplements](https://tryleverage.ai/case-study-supplements-manufacturing)
    - [Packaging](https://tryleverage.ai/case-study-packaging-manufacturing)
    - [Automotive Parts Distributor](https://tryleverage.ai/case-study-auto-parts-distributor)
    - [Commercial Equipment](https://tryleverage.ai/case-study-commercial-equipment)
    - [Wood Processing Equipment](https://tryleverage.ai/case-study-wood-processing-equipment)
- Show submenu for Company Company 
  
    - [Our Story](https://tryleverage.ai/our-story)
    - [Podcast](https://tryleverage.ai/podcast)
    - [Blog](https://tryleverage.ai/blog)
    - [Careers](https://tryleverage.ai/careers)
    - [Partners](https://tryleverage.ai/partners)
    - [Contact Us](https://tryleverage.ai/contact)

Open main navigation

Close main navigation

- Show submenu for Platform Platform 
  
    - Platform
    - [CONNECT: Integrations](https://tryleverage.ai/integrations)
    - [PARSE: Document Parsing](https://tryleverage.ai/document-parsing)
    - [MEASURE: Supplier Performance](https://tryleverage.ai/supplier-performance)
    - [PAY: Trade Finance](https://tryleverage.ai/payments)
    - [ENGAGE: PO Automation](https://tryleverage.ai/purchase-order-automation)
    - [TRACK: Shipments](https://tryleverage.ai/shipment-tracking)
    - [COPILOT: AI Agents](https://tryleverage.ai/artificial-intelligence)
- Show submenu for Case Studies Case Studies 
  
    - Case Studies
    - [Manufacturing](https://tryleverage.ai/case-study-manufacturing)
    - [Distribution](https://tryleverage.ai/case-study-distribution)
    - [Pharma & Biotechnology](https://tryleverage.ai/case-study-pharma-biotechnology)
    - [Food Production](https://tryleverage.ai/case-study-food-production)
    - [Furniture](https://tryleverage.ai/case-study-furniture)
    - [Supplements](https://tryleverage.ai/case-study-supplements-manufacturing)
    - [Packaging](https://tryleverage.ai/case-study-packaging-manufacturing)
    - [Automotive Parts Distributor](https://tryleverage.ai/case-study-auto-parts-distributor)
    - [Commercial Equipment](https://tryleverage.ai/case-study-commercial-equipment)
    - [Wood Processing Equipment](https://tryleverage.ai/case-study-wood-processing-equipment)
- Show submenu for Company Company 
  
    - Company
    - [Our Story](https://tryleverage.ai/our-story)
    - [Podcast](https://tryleverage.ai/podcast)
    - [Blog](https://tryleverage.ai/blog)
    - [Careers](https://tryleverage.ai/careers)
    - [Partners](https://tryleverage.ai/partners)
    - [Contact Us](https://tryleverage.ai/contact)
- [Login](https://app.lvrg.ai/signin)
  
  [Request Demo](https://tryleverage.ai/request-a-demo)

[Login](https://app.lvrg.ai/signin)

[Request Demo](https://tryleverage.ai/request-a-demo)

# Supplier OTIF Scorecards: Measurement Rules, Tolerance Windows, and Review Cadence

![Michael Ciavarella](https://tryleverage.ai/hs-fs/hubfs/1684949656189.jpeg?width=40&height=40&name=1684949656189.jpeg)

By [Michael Ciavarella](https://tryleverage.ai/blog/author/michael-ciavarella) · Nov 18, 2026, 5:12:15 AM

🎧 Listen to this article (15 min)

Your browser does not support the audio element.

**Supplier OTIF (on-time, in-full) is a measurement of how reliably a supplier delivers the right quantity on the agreed date. A credible scorecard needs three things your ERP does not provide on its own: a defined date basis (promise date, not the original requested date), an explicit tolerance window in days and units, and a confirmed acknowledgement captured at the time of commitment. Without those three, OTIF numbers are opinions, and suppliers will dispute them.**

Most mid-market manufacturers and distributors already run some version of a supplier scorecard. Very few of them trust it. The number gets published, procurement sends it to the supplier, the supplier replies that the date changed in an email three months ago, and the conversation dies there. That is not a measurement problem. It is a data capture problem that happens upstream of the scorecard.

This is a practical guide to building OTIF measurement that holds up in a supplier review: how to define the rules, where the data actually lives, what to put in the scorecard, and how often to run the review so the number changes behavior instead of generating argument.

## What OTIF Actually Measures, and Where Scorecards Break

OTIF is a compound metric. A line is on-time if it arrives inside the agreed date window. It is in-full if the received quantity matches the ordered quantity inside the agreed quantity tolerance. A line scores only if both conditions are true. That compounding is why OTIF always reads lower than either component measured alone, and why teams new to the metric are frequently surprised by their first result.

Four definition choices determine whether your number is defensible:

**Date basis.** Is the measurement against the original requested date on the purchase order, the supplier's acknowledged promise date, or the most recent revised date? Measuring against the requested date produces a punishing number that suppliers will reject as unfair. Measuring against the latest revised date produces a flattering number that hides every schedule slip. The defensible middle is the first acknowledged promise date, with revisions tracked separately as a schedule stability metric.

**Event basis.** Ship date or receipt date? Ship date measures the supplier. Receipt date measures the supplier plus the carrier plus your dock. If you buy a lot of freight-on-board-origin material, scoring on receipt date charges suppliers for transit variability they do not control. Pick one, write it down, and apply it uniformly.

**Line versus order.** A multi-line purchase order where nine lines arrive on time and one line is a week late is either 90 percent or 0 percent depending on the rule. Line-level scoring is more useful operationally. Order-level scoring is more useful when a partial shipment blocks a build regardless of how many lines came in.

**Early delivery treatment.** Early is not automatically good. Material arriving three weeks ahead of need consumes floor space and working capital. Most mature programs score early arrivals outside the tolerance window as a miss, same as late. That single rule change usually drops a first OTIF reading by several points and surfaces suppliers who have been padding lead times.

According to Gartner, 50% of purchase order lines undergo changes after issuance, making real-time supplier visibility a procurement priority. That statistic is the entire reason the date-basis question matters. If half your lines move after issuance and you are not capturing the acknowledgement and the revision separately, your scorecard is measuring paperwork drift, not supplier performance.

## Setting Tolerance Windows That Match How Your Plant Runs

A tolerance window is the band around the promise date and ordered quantity inside which a delivery counts as a hit. Blanket windows applied across every commodity are the most common scorecard design error. A three-day window is generous for a local fastener distributor and brutally tight for an overseas casting with a twelve-week lead time.

Segment the window by commodity class and lead time. A workable starting structure:

| Commodity class | Typical lead time | Date tolerance | Quantity tolerance | Early arrival rule |
| --- | --- | --- | --- | --- |
| Consumables and MRO | Under 2 weeks | 0 days early / +2 days late | +/- 5% | Score as miss beyond 2 days early |
| Standard purchased parts | 2 to 6 weeks | -2 / +2 days | +/- 5% | Score as miss beyond 3 days early |
| Custom fabrication | 6 to 12 weeks | -3 / +5 days | +/- 2% | Score as miss beyond 5 days early |
| Long-lead castings and forgings | 12 weeks plus | -5 / +10 days | +/- 2% | Allowed, flag for inventory review |
| Bulk and commodity material | Varies | -3 / +3 days | +/- 10% | Allowed within quantity tolerance |

Two rules make this structure work in practice. First, the supplier has to see the window before the measurement period starts. A tolerance published after the fact is a trap, and suppliers treat it that way. Second, the window belongs to the commodity, not the supplier. If one supplier gets a wider window than another on the same part class, the scorecard stops being comparable and the whole program loses credibility.

Quantity tolerance deserves its own decision on partial receipts. If a supplier ships 80 percent of the line on the promise date and the balance nine days later, most teams score the line as a miss on the first receipt and do not re-score it. That is the right call for production planning, but you want the partial captured as a distinct failure mode, because short-shipping and late-shipping have different root causes and different fixes.

## The Data Problem: Why ERP Receipt Records Are Not Enough

Here is where OTIF programs stall. The receipt side of the equation is clean. Your ERP knows exactly what arrived, when, and in what quantity. Goods receipt records in Microsoft Dynamics 365, SAP, Oracle NetSuite, Epicor, and Infor are all reliable for that half.

The commitment side is the problem. The acknowledged promise date usually never enters the ERP at all. It lives in an email thread, a PDF order confirmation, or a verbal update a buyer took on a call and never wrote down. When the scorecard pulls from the ERP, the only date available is the requested date, so the system measures against a date the supplier never agreed to.

A Deloitte supply chain study found that 70% of supply chain disruptions originate before materials leave the supplier's facility. Those are precisely the events that never reach the ERP: the line that slipped two weeks at acknowledgement, the partial allocation, the raw material shortage the supplier flagged in week three. Your receipt data captures the outcome and none of the signal.

The fields a credible scorecard needs, and where they typically come from:

| Field | Source today | ERP native? | Scorecard use |
| --- | --- | --- | --- |
| PO line requested date | ERP | Yes | Baseline, not the scoring date |
| Acknowledged promise date | Supplier email or PDF confirmation | Rarely | Primary scoring date |
| Acknowledgement timestamp | Email metadata | No | Responsiveness metric |
| Revised promise dates | Email thread | No | Schedule stability metric |
| Ship confirmation and tracking | Supplier email or carrier portal | Sometimes | Ship-basis OTIF, in-transit visibility |
| Receipt date and quantity | ERP goods receipt | Yes | Delivery outcome |
| Short-ship or partial flag | ERP receipt line | Yes | In-full component |

Three of the seven fields that matter most are sitting in a buyer's inbox. That is the gap. Teams that solve it do one of two things: they force every supplier onto a portal and accept the adoption problem that follows, or they capture the commitment data where it already happens, in email, and write it back to the ERP automatically. We cover the tradeoff between those paths in detail in our comparison of [ERP-agnostic PO automation versus built-in ERP modules](https://tryleverage.ai/blog/pf/erp-agnostic-po-automation-vs-built-in-erp-modules), and the specific data-completeness failure in [supplier OTIF tracking when ERP data is incomplete](https://tryleverage.ai/blog/pf/supplier-otif-tracking-erp-incomplete-data-1).

For teams running Microsoft Dynamics 365, whether Business Central, Finance and Supply Chain, or Navision, Leverage AI integrates directly with your existing ERP environment to automate supplier PO confirmations, flag exceptions in real time, and surface OTIF data without custom development or ERP modification. The practical effect on the scorecard is that the acknowledged promise date exists as a structured field instead of a memory. More on that path in our guide to [Dynamics 365 procurement automation and PO visibility](https://tryleverage.ai/blog/pf/dynamics-365-procurement-automation-po-visibility).

## What Belongs on the Scorecard

OTIF alone is too blunt to drive a supplier conversation. A supplier at 78 percent needs to know which failure mode is costing them. A five-metric scorecard with explicit weights gives the review a structure:

| Metric | Definition | Weight | Target | Escalation threshold |
| --- | --- | --- | --- | --- |
| OTIF | Lines on time and in full, inside tolerance | 40% | 95% | Below 85% for 2 consecutive months |
| Acknowledgement rate | PO lines confirmed within 48 hours of issue | 20% | 98% | Below 90% in any month |
| Schedule stability | Lines with zero promise-date revisions after acknowledgement | 20% | 90% | Below 75% in any month |
| Quantity accuracy | Lines received in full on first receipt | 10% | 98% | Below 92% for 2 consecutive months |
| Exception response time | Median hours to respond to a flagged exception | 10% | Under 24 hours | Above 72 hours median |

The acknowledgement rate is the metric most teams skip and the one that predicts the rest. A supplier who confirms every line inside two days is a supplier whose internal planning is working. A supplier who acknowledges 60 percent of lines is telling you something about their order desk long before the delivery misses show up. Treat it as a leading indicator, not an administrative nicety.

Schedule stability is the second underused metric. A supplier can hit 95 percent OTIF while revising the promise date on half their lines, because they keep moving the goalposts and you keep accepting the move. Measuring revisions separately exposes that pattern without turning the OTIF number into a fight.

Aberdeen Group research shows that automated PO tracking reduces operational costs by up to 30% for mid-market manufacturers. Most of that reduction comes out of the time buyers spend reconstructing this data by hand for quarterly reviews. If three people spend two days a quarter rebuilding a scorecard from email archives, the scorecard is costing more than it returns.

## Review Cadence That Actually Changes Behavior

Quarterly business reviews are too slow to correct a drifting supplier. By the time a Q3 review flags a trend that started in July, you have absorbed three months of expedite freight and short builds. Run the cadence at three levels.

**Weekly, internal only.** Buyers review exception queues and the acknowledgement backlog. No supplier contact unless a line is at risk. This is operational triage, not performance management. Our [PO exception management checklist](https://tryleverage.ai/blog/pf/po-exception-management-checklist) covers how to structure that queue.

**Monthly, supplier-facing, top suppliers only.** A one-page scorecard emailed to the supplier's account manager with the five metrics, the trend line, and one specific ask. Not a meeting. Most suppliers will not need one. The discipline of publishing the number monthly does most of the work, because it removes the surprise from the quarterly conversation.

**Quarterly, full review, scored suppliers in the bottom quartile.** This is where corrective action plans and sourcing consequences live. Bring line-level evidence: the PO, the acknowledgement timestamp, the revision history, the receipt. A supplier cannot dispute a date they confirmed in writing, which is exactly why the acknowledgement capture matters more than the scorecard template.

One rule for the monthly send: publish to the supplier even when the number is good. Scorecards that only appear when there is a problem get read as punishment and generate defensiveness. Scorecards that arrive every month become a shared operating fact.

## What to Automate First

If you are building this from a standing start, sequence it so you get a credible number before you build the reporting layer.

First, capture acknowledgements as structured data. Every PO line gets a confirmed promise date and a timestamp, pulled from whatever the supplier already sends. This is the single highest-leverage step, because it converts the scoring date from an assumption into a record. IDC projects that 60% of enterprise procurement teams will transition to AI-powered automation by 2025, and acknowledgement parsing is the most common first use case for exactly this reason.

Second, write the acknowledged date back to the ERP as a distinct field from the requested date. If the two dates collapse into one, the schedule stability metric is impossible to compute.

Third, define and publish tolerance windows by commodity class before you publish a single score. Give suppliers the rules first.

Fourth, automate the monthly scorecard generation. A scorecard that requires manual assembly will not survive a busy quarter, and an intermittent scorecard is worse than none because suppliers learn to wait it out.

Fifth, connect the exception queue to the scorecard so that the weekly operational work and the monthly performance number come from the same data. If the buyers' exception list and the scorecard disagree, nobody trusts either one. If you need to build the internal case for that investment, our [PO tracking automation ROI model](https://tryleverage.ai/blog/pf/po-tracking-automation-roi-model) walks through the inputs, and the [Leverage AI product overview](https://tryleverage.ai/product) covers how the capture and write-back work against an existing ERP.

According to McKinsey, companies with mature supply chain visibility capabilities outperform peers by 15-20% on OTIF metrics. The gap is rarely supplier quality. It is whether the buying organization captured the commitment data well enough to manage against it.

## Frequently Asked Questions

### Should OTIF be measured on ship date or delivery date?

Ship date measures supplier performance in isolation. Delivery date measures the end-to-end result including carrier performance. If you control the freight, measure on ship date and manage carriers separately. If the supplier controls freight on a delivered basis, measure on receipt date. The one thing you cannot do is mix the two inside the same scorecard, because the resulting number is not comparable across suppliers.

### What is a realistic OTIF target for a mid-market manufacturer?

Most mid-market programs start somewhere between 70 and 85 percent once early arrivals are scored as misses, and reach the low 90s within two to three quarters of consistent monthly review. A 95 percent target is reasonable as a published goal. Treating anything below 95 as a failure in month one tends to break supplier buy-in before the program gets traction.

### How do we handle suppliers who dispute the OTIF number?

Disputes are almost always about the date basis, not the arithmetic. If you can produce the acknowledgement with a timestamp, the dispute ends in one email. If you cannot, the supplier is probably right to push back. This is why the acknowledgement capture step comes before the scorecard build, not after.

### Can we run OTIF scorecards without a supplier portal?

Yes, and for most mid-market supplier bases you should. Portal adoption below roughly 40 percent of your supplier count produces a scorecard that only covers your most cooperative suppliers, which is the opposite of what you need. Capturing commitments from the email and PDF confirmations suppliers already send avoids the adoption problem entirely.

### Does OTIF work for blanket orders and releases?

Score at the release level, not the blanket level. The blanket is a commercial agreement with no delivery event attached. Each release carries its own promise date and quantity, and that is the unit the supplier is actually committing to.

### Which ERP systems support OTIF measurement natively?

Microsoft Dynamics 365, SAP, Oracle NetSuite, Epicor, and Infor all store receipt data capable of supporting the delivery half of the calculation. None of them capture the acknowledged promise date reliably unless the supplier submits it through a structured channel, which is why the measurement gap is consistent across ERP platforms rather than specific to one.

## Related Reading

- [Supplier OTIF tracking when ERP data is incomplete](https://tryleverage.ai/blog/pf/supplier-otif-tracking-erp-incomplete-data-1)
- [PO exception management checklist](https://tryleverage.ai/blog/pf/po-exception-management-checklist)
- [Dynamics 365 procurement automation and PO visibility](https://tryleverage.ai/blog/pf/dynamics-365-procurement-automation-po-visibility)
- [ERP-agnostic PO automation versus built-in ERP modules](https://tryleverage.ai/blog/pf/erp-agnostic-po-automation-vs-built-in-erp-modules)
- [PO tracking automation ROI model](https://tryleverage.ai/blog/pf/po-tracking-automation-roi-model)

![Michael Ciavarella](https://tryleverage.ai/hs-fs/hubfs/1684949656189.jpeg?width=72&height=72&name=1684949656189.jpeg)

About Michael Ciavarella

Michael Vincent Ciavarella is a Director of Operations focused on modernizing old-school industries like logistics and manufacturing. He writes about simplifying messy workflows, introducing practical technology, and making change actually stick with the teams who use it every day.

[Website](https://www.tryleverage.ai)[LinkedIn](https://www.linkedin.com/in/michaelvincentciavarella/)

## Related Articles

##### [![Proving PO Automation ROI After Go-Live: Baselines, Metrics, and the 90-Day Review](https://tryleverage.ai/hs-fs/hubfs/blog-covers/cover-po-automation-roi-after-go-live-baselines-metrics-90-day-review.png?width=520&height=294&name=cover-po-automation-roi-after-go-live-baselines-metrics-90-day-review.png) Automation • Nov 9, 2026 Proving PO Automation ROI After Go-Live: Baselines, Metrics, and the 90-Day Review 9 min read](https://tryleverage.ai/blog/pf/po-automation-roi-after-go-live-baselines-metrics-90-day-review)

##### [![New Product Feature: Bulk Accept or Reject Purchase Orders](https://tryleverage.ai/hs-fs/hubfs/Untitled3-1.png?width=520&height=294&name=Untitled3-1.png) Supply Chain • Feb 28, 2024 New Product Feature: Bulk Accept or Reject Purchase Orders 2 min read](https://tryleverage.ai/blog/bulk-accept-reject-pos)

### See Leverage in Action

Stop chasing suppliers by email. Get real-time PO tracking and delivery visibility for your entire supply chain.

[Request a Demo](https://tryleverage.ai/request-a-demo)

#### Works with your ERP

Epicor, Infor, SAP, NetSuite, Microsoft Dynamics, and more. No EDI or supplier portal required.

[![Leverage powered by Order.co](https://tryleverage.ai/hubfs/leverage-powered-by-order-co-dark.svg)](https://tryleverage.ai)

Leverage AI delivers an end-to-end supply chain visibility platform powered by artificial intelligence that enables teams to ensure on-time delivery, in-full completion, within-budget costs, and high-quality standards.

Copyright © 2026 LVRG, Inc.

- Platform 
    - [CONNECT: Integrations](https://tryleverage.ai/integrations)
    - [PARSE: Document Parsing](https://tryleverage.ai/document-parsing)
    - [MEASURE: Supplier Performance](https://tryleverage.ai/supplier-performance)
    - [PAY: Trade Finance](https://tryleverage.ai/payments)
    - [ENGAGE: PO Automation](https://tryleverage.ai/purchase-order-automation)
    - [TRACK: Shipments](https://tryleverage.ai/shipment-tracking)
    - [COPILOT: AI Agents](https://tryleverage.ai/artificial-intelligence)
- Case Studies 
    - [Manufacturing](https://tryleverage.ai/case-study-manufacturing)
    - [Distribution](https://tryleverage.ai/case-study-distribution)
    - [Pharma & Biotechnology](https://tryleverage.ai/case-study-pharma-biotechnology)
    - [Food Production](https://tryleverage.ai/case-study-food-production)
    - [Furniture](https://tryleverage.ai/case-study-furniture)
    - [Supplements](https://tryleverage.ai/case-study-supplements-manufacturing)
    - [Packaging](https://tryleverage.ai/case-study-packaging-manufacturing)
    - [Automative Parts Distributor](https://tryleverage.ai/case-study-auto-parts-distributor)
    - [Commercial Equipment](https://tryleverage.ai/case-study-commercial-equipment)
    - [Wood Processing Equipment](https://tryleverage.ai/case-study-wood-processing-equipment)
- Resources 
    - [Security & Trust](https://tryleverage.ai/security)
    - [Terms of Service](https://tryleverage.ai/terms)
    - [Privacy Policy](https://tryleverage.ai/privacy)
    - [Vulnerability Disclosure Policy](https://tryleverage.ai/vdp)
- Company 
    - [Our Story](https://tryleverage.ai/our-story)
    - [Podcast](https://tryleverage.ai/podcast)
    - [Blog](https://tryleverage.ai/blog)
    - [Careers](https://tryleverage.ai/careers)
    - [Partners](https://tryleverage.ai/partners)
    - [Contact Us](https://tryleverage.ai/contact)

- <https://www.facebook.com/lvrginc/>
- <https://twitter.com/TryLeverage>
- <https://www.linkedin.com/company/lvrginc>

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Michael Ciavarella",
    "url" : "https://tryleverage.ai/blog/author/michael-ciavarella"
  },
  "datePublished" : "2026-11-18T10:12:15.000Z",
  "headline" : "Supplier OTIF Scorecards: Measurement Rules, Tolerance Windows, and Review Cadence",
  "image" : [ "https://tryleverage.ai/hubfs/blog-covers/cover-supplier-otif-scorecards-measurement-rules-tolerance-windows-review-cadence.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://tryleverage.ai/blog/pf/supplier-otif-scorecards-measurement-rules-tolerance-windows-review-cadence",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://tryleverage.ai/hubfs/Logo%20+%20Name%20Dark.png"
    },
    "name" : "Leverage AI"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "Organization",
  "contactPoint" : {
    "@type" : "ContactPoint",
    "contactType" : "sales",
    "telephone" : "+1-929-470-3086"
  },
  "description" : "AI-powered purchase order automation and supplier performance platform for manufacturers and distributors.",
  "logo" : "https://tryleverage.ai/hubfs/leverage-logo-dark.png",
  "name" : "Leverage AI",
  "url" : "https://tryleverage.ai"
}
```