Get a demo

Vendor scorecard reporting

Pull PO and shipment data from your ERP, parse delivery confirmations from email and PDF, and score every supplier on on-time and in-full performance automatically.

Get a demo

The prompt

I want to build a vendor scorecard that pulls PO and shipment data from NetSuite and parses delivery confirmations from email and PDF reports. Can you build me a flow that calculates on-time and in-full rates per vendor, scores each supplier against performance thresholds, and generates a formatted scorecard report?

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with seven steps you can edit:

1. Pull PO and shipment data from the ERP. NetSuite, Fulfil, or whichever ERP holds the order record. PO number, supplier, line items, expected and actual delivery dates.

2. Parse the delivery confirmations. Emails and PDF reports from suppliers and carriers. The AI step extracts confirmed dates, quantities, and any deviation reasons.

3. Match against the PO. Tie each confirmation back to the right PO line by number, then compare expected versus actual.

4. Calculate the metrics. On-time rate, in-full rate, OTIF rate, average days late, quantity variance, fill rate. Per vendor, per category, per period.

5. Score against thresholds. Apply your tier logic. Above 95% is green, 90 to 95 is yellow, below 90 is red. Whatever the procurement team uses.

6. Build the scorecard report. One row per vendor with the score, the underlying metrics, and the trend versus the prior period.

7. Send the package. PDF or sheet to procurement, exception list for the buyer review, and an alert when a key vendor crosses a threshold.

Why teams stop doing this manually

Vendor performance is the kind of data that everyone wants and nobody wants to produce. POs live in the ERP. Shipment confirmations land in three different inboxes. Delivery reports come as PDF attachments with formats that vary by carrier and supplier. The metrics that procurement wants live in the gap between all of those.

The manual version takes an analyst a full week per quarter. Export POs, hunt down confirmations in email, copy fields into a workbook, look up each supplier's contract terms, calculate OTIF, format the score. By the time the deck is finished, the data is a month stale and the meeting it was built for is already running on slides from last quarter.

The work is mostly mechanical. Match shipments to POs, calculate dates, score against thresholds. The judgment is in the threshold and the conversation with the supplier, not in the math. Put the math in a flow and the supplier conversation gets the analyst's full attention.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about your ERP, which inboxes to watch, and how your scoring tiers are defined.

Step 2. Connect your data.

NetSuite or your ERP, the procurement inbox, any supplier portals, and the tier definition table.

Step 3. Run it monthly.

The flow refreshes against the latest POs and confirmations, recalculates every supplier score, and posts the package to procurement before the QBR.

Related prompts

FAQ

Does this work if my delivery confirmations come as PDF attachments instead of structured data?

Yes. The AI step extracts confirmed dates and quantities from PDF and image-based confirmations. Cleaner inputs get cleaner output, but the flow handles supplier-specific formats out of the box.

Can I score against a custom contract term per supplier?

Yes. Each vendor row in the master table carries its own contract terms. The flow scores against the supplier-specific threshold instead of a single org-wide rule.

How does it handle partial shipments?

Each PO line carries its own status. Partial shipments score against fill rate. The line that shipped late counts against on-time. The flow rolls those into the supplier-level score.

What if a supplier disputes the score?

The scorecard links back to the underlying PO and confirmation rows. The buyer sees exactly which lines drove the score and which deliveries the supplier is disputing.

How is this different from a native NetSuite vendor report?

NetSuite reports against what NetSuite has. If your confirmations live in email or PDF, the report misses the deviations. This flow ingests those inputs and lands the truth back in the scorecard.
Walk into the supplier QBR with a score that ties out.
Paste the prompt, point it at your ERP and confirmation inbox, and let the scorecard run on its own.
Start for free