Generating Custom Reports for Dealer Performance

Custom reports can be generated from the Analytics module by selecting the relevant data range and metric — such as vendor delivery performance, auction savings, or gate rejection trends — and exporting the results for internal review or sharing with stakeholders.

Common, high-value report use-cases:

1. Monthly vendor scorecards — combining delivery time, rejection percentage, and pricing trend for each active vendor, useful for quarterly business reviews with key suppliers.
2. Auction performance summaries — comparing savings achieved (vs. benchmark) across different auction types used over a period, helping refine which auction format to favor going forward.
3. Gate/Store rejection trend reports — tracking rejection rates over time by vendor or material category, useful for quality audits and vendor accountability conversations.
4. Visitor and complaint volume reports — summarizing facility traffic and issue volume for operational and service-quality reviews.
5. PR-to-PO cycle time reports — measuring how efficiently your procurement process is running, useful for identifying and addressing internal process bottlenecks.

Step-by-step: generating a report (typical flow)

1. Open the Analytics module.
2. Select the report type or metric category you need (e.g., vendor performance, auction savings, gate rejection trends).
3. Set your desired date range or filter criteria (specific vendor, plant, or material category, if supported).
4. Generate the report view — reviewing charts, tables, or summary cards depending on the report type.
5. Use the export/download option, if available, to save the report for offline sharing or record-keeping.

Practical tip — pairing reports with action: Reports are most valuable when tied directly to a decision. For example, pair a vendor scorecard report with your Sourcing List review — vendors consistently underperforming across delivery time and rejection rate in the report are strong candidates for review, deprioritization, or removal before their next RFQ inclusion, rather than being reassigned automatically out of habit.

A sample monthly reporting routine for a procurement team:

• Week 1: Generate a vendor scorecard report for the previous month, flag any vendor with rejection rate above your internal threshold.
• Week 2: Review auction performance summaries to confirm which auction type delivered the best savings, and apply that learning to upcoming auctions.
• Week 3: Pull a PR-to-PO cycle time report to identify any internal bottlenecks (e.g., requisitions sitting too long in "Pending Vendor Assignment").
• Week 4: Review complaint volume trends alongside Gate/Store rejection data to spot any emerging vendor-specific patterns before the next quarterly business review.

Frequently Asked Questions

Can reports be scheduled to generate automatically on a recurring basis? 

This depends on your specific portal configuration — check with your admin team whether scheduled/recurring reports are enabled for your organization.

What file formats are typically supported for exported reports?

 Common formats include Excel/CSV for tabular data and PDF for formatted summary reports, though this can vary by specific report type.

Can I generate a report for a single vendor rather than an entire category? 

Yes, most analytics tools support filtering down to a single vendor when you need a focused performance review, such as ahead of a renewal or negotiation discussion.

Who typically has permission to generate and export reports? 

This is usually restricted to management, purchase heads, and admin roles, consistent with the broader access restrictions on the Analytics module itself.

How far back can historical data typically be pulled into a report? 

This depends on your organization's data retention settings, but the system is generally designed to preserve historical records for meaningful trend analysis rather than short-term-only data.

Can reports combine data from multiple modules, like Auction savings and Gate rejection rates together? 

Yes — since Analytics is designed to consolidate data across modules, cross-module reports (e.g., correlating auction type chosen with downstream gate/store rejection rates) are a key part of its value over checking each module separately.