How to Configure Supplier Scorecard Weights

One weight set does not fit every buying strategy

Import-heavy buyers care more about on-time delivery; commodity buyers care more about price stability.

A fixed floor of 60 may be too soft or too harsh for a company’s quality bar.

Changing policy without recalculating leaves historical months scored under old weights.

Why this happens

• Defaults never reviewed after go-live.
• Weights saved that do not sum to 100.
• Floor changed on Health Dashboard expectations without updating settings.
• No recalculate after a weight change for the current review month.

Biznsbook addresses this through scorecard weight config, score floor, recalculate after weight change when the Inventory module is licensed — GRN, purchase order, and return-to-vendor history feed monthly snapshots without a second data entry path.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Configure Supplier Scorecard Weights

Built for buyers and inventory leads who need one supplier performance score before converting requisitions to purchase orders in Biznsbook.

1. Open scorecard settings. From the ranking page, choose Settings, or go to /inventory/supplier-scorecard/settings.
2. Set the four weights. Enter On-time, Variance, RTV, and Price stability percentages. The form shows a live sum — it must equal 100.
3. Set the score floor. Choose the OverallScore below which suppliers count as at-risk on ranking and the Health Dashboard KPI.
4. Save. Persist weights and floor for the company (one weight config row per company).
5. Recalculate affected months. Return to ranking and Recalculate the months you need under the new weights so OverallScore updates.
6. Verify at-risk count. Open Inventory Health Dashboard and confirm “Suppliers below threshold” matches the new floor.
7. Communicate to buyers. Share which component matters most so PO badges are interpreted correctly.

Review results after the first full monthly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Defaults never reviewed after go-live. Repeating this each month usually shows up first in purchase reliability and replenishment decisions.
• Mistake 2: Weights saved that do not sum to 100. Repeating this each month usually shows up first in purchase reliability and replenishment decisions.
• Mistake 3: Floor changed on Health Dashboard expectations without updating settings. Repeating this each month usually shows up first in purchase reliability and replenishment decisions.
• Mistake 4: No recalculate after a weight change for the current review month. Repeating this each month usually shows up first in purchase reliability and replenishment decisions.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

• Open scorecard settings — From the ranking page, choose Settings, or go to /inventory/supplier-scorecard/settings.
• Set the four weights — Enter On-time, Variance, RTV, and Price stability percentages.
• Set the score floor — Choose the OverallScore below which suppliers count as at-risk on ranking and the Health Dashboard KPI.
• Save — Persist weights and floor for the company (one weight config row per company).
• Recalculate affected months — Return to ranking and Recalculate the months you need under the new weights so OverallScore updates.

Teams that keep expected delivery dates on POs and post true return-to-vendor notes get trustworthy on-time and RTV components every month.

How Biznsbook supports this workflow

scorecard weight config is documented in Biznsbook Inventory & Purchase capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

score floor is documented in Biznsbook Inventory & Purchase capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

recalculate after weight change is documented in Biznsbook Inventory & Purchase capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

Scorecard ranking, settings, and exports are permission-separated so buyers view scores while inventory managers own weights and recalculation.

Suggested implementation timeline

1. Week 1: Document current process gaps and configure scorecard weight config with finance owner sign-off.
2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
5. Ongoing: Monthly review using weight change tip and leadership dashboard.

Related guides and help articles

Help Center: creating a GRN, three-way match, supplier scorecards.

Modules: inventory guides hub, Purchase.

Choosing a weight policy

Default weights (40 on-time / 25 variance / 20 RTV / 15 price stability) fit distributors who care most about delivery reliability. Raise price stability when commodity unit costs swing week to week. Raise RTV when returns drive scrap or production shortages. Raise on-time before peak season so chronic late vendors fall in the ranking.

Keep one company-wide policy so rankings stay comparable across buyers. Changing weights mid-month without recalculating leaves historical snapshots on the old formula — recalculate the months you still use in reviews.

Document the effective month in your purchasing SOP whenever weights change. Auditors and new buyers should know which OverallScore formula applied to each snapshot month without asking the implementer who edited settings.

Score floor and health dashboard

The score floor (default 60) drives the at-risk filter on the ranking page and the Inventory Health Dashboard count of suppliers below threshold. Lower the floor only when you intentionally widen the watch list; raise it when quality standards tighten.

After saving, open Health Dashboard and confirm the KPI matches the filtered ranking so operations and purchasing see the same risk count. A mismatch usually means snapshots are stale — recalculate the latest month after the floor change.

Governance and permissions

Only Inventory.Manage users (and Company Admins) can edit weights and the floor. Buyers with Inventory.ViewReports can still open ranking, detail, badge APIs, and Excel export so day-to-day sourcing is not blocked.

Treat weight changes like a costing policy change: announce them, recalculate the review month, and leave Hangfire to apply the new policy on the next first-of-month run.

Metrics to track monthly

• Suppliers with a scorecard snapshot for the prior month
• At-risk suppliers below the configured floor
• POs created after reviewing the supplier score badge
• Months recalculated after weight changes
• Scorecard Excel exports attached to supplier reviews

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook scorecard weight config and related capabilities.

Weight change tip

Change weights at month boundary, recalculate the prior month once, then leave the Hangfire job to apply the policy going forward. Document weight changes in your purchasing SOP with the effective month so auditors know which OverallScore formula applied to each snapshot.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

How this differs by industry