Supplier OTIF & Split Receipt Scorecard

Measure actual supplier on-time in-full (OTIF) performance from purchase-order lines and cumulative accepted receipts. The Actor turns normalized exports into one reproducible supplier scorecard, line-level evidence and an exception queue.

What it calculates

• cumulative accepted quantity across split receipts;
• the date each order line first reached the in-full threshold;
• on-time, in-full and OTIF status for every due order line;
• supplier and overall OTIF percentages;
• quantity fill rate, late accepted quantity and overdue quantity;
• unmatched, future-dated, SKU-mismatched, unit-mismatched and over-receipt exceptions;
• supplier performance against your explicit OTIF target.

Each due order line has equal weight in the OTIF percentage. Order lines whose due cutoff is after asOfDate are NOT_DUE and excluded from the denominator.

Input

caseJson contains:

• snapshotId: an opaque reference for this supplied snapshot;
• asOfDate: the last included date in YYYY-MM-DD form;
• coverageConfirmed: true only when the order and accepted-receipt exports are complete for the scope;
• orderLines: 1–1,000 exact order lines;
• receipts: 0–2,000 accepted receipt rows, including partial receipts;
• policy: lateToleranceDays, quantityTolerance, and targetOtifPercent.

Order lines require supplierId, poId, lineId, sku, unit, orderedQuantity and requiredDeliveryDate. Receipts require the same exact business identity plus unique receiptId, acceptedQuantity and receiptDate.

Quantities and percentage thresholds are plain decimal strings. Identifiers are case- and whitespace-sensitive and preserve leading zeros. The Actor never performs fuzzy matching or unit conversion.

Method

• Due denominator: exact order lines whose required date plus allowed late-tolerance days is on or before asOfDate.
• On time: compatible cumulative accepted quantity reaches ordered quantity minus tolerance by the due cutoff.
• In full: compatible accepted quantity through asOfDate reaches the same threshold.
• OTIF: the due line is both on time and in full.

This explicit rule avoids hiding a late final split behind an earlier partial delivery. It also keeps not-yet-due lines out of the denominator.

Statuses

• TARGET_MET_WITHIN_SUPPLIED_SCOPE: no exception and every supplier with due lines meets the supplied target.
• BELOW_TARGET_OR_EXCEPTIONS: at least one review finding or below-target supplier.
• INCOMPLETE_REVIEW: coverage was not confirmed.

supplierPerformanceApproved is always false. The Actor does not approve, penalize, contact or modify a supplier or purchase order.

Pricing

$0.05 per completed report ($50 per 1,000 reports). Reports with below-target results, exceptions or incomplete coverage are still completed reports. Malformed inputs fail before a report is produced or charged. Use an Apify maximum-charge limit to cap a run.

Data and safety

The Actor makes no network requests and uses no AI, OCR, ERP credentials or paid external API. Processing occurs inside the Apify run. Results remain in the user's Apify storage subject to its retention settings. Use opaque business identifiers and omit supplier contacts, employee names, addresses, banking data and unrelated fields.

Scope difference

This product scores actual accepted receipts against required order dates. It does not review future supplier promises, compare invoices and prices, or change purchase orders.

Reference basis

• ASCM SCOR separates perfect supplier order fulfillment into delivery performance and in-full measures: https://scor.ascm.org/performance/reliability/RL.3.1
• Infor defines inbound OTIF as purchase-order receipts delivered on time with the scheduled quantity: https://docs.infor.com/lncs/latest/en-us/lncslib/ln_industry_content_user_guide/njd1742535354522.html
• UK procurement guidance uses on-time-in-full as an example measurable supplier KPI: https://www.gov.uk/government/publications/the-official-procurement-act-2023-e-learning/module-9-contract-governance