The job of this console
Keep the vendor master accurate, then use aggregates to see bids and purchase orders already linked. Create commercial documents on Sales / Finance, not as rows invented here.
Admin · Procurement
Vendor Register
Master vendors plus BidRequest and PurchaseOrder aggregates — not a shadow vendor ledger.
Scroll to Flowcharts. Scenario: Review vendor PO coverage.
Procurement master
Vendors plus the bids and POs already on them
The vendor register is master vendors with BidRequest and PurchaseOrder aggregates — not a shadow vendor ledger beside finance.
Admin → Vendors (deep link)
Route
/admin/vendors
HR Admin · Org Admin · Finance operators with access
Seat at the table
Administrators maintaining the master. Buyers work bids and POs on their finance screens. Employees do not maintain vendors.
The working rhythm
Search a vendor, confirm legal name and status, follow aggregates into bid or PO lists, correct the master if the name is wrong.
Moments that bring you here
A new supplier before the first PO. Duplicate vendor names breaking reports. After a Salesforce import of POs. When a vendor should be inactive but still appears on new bids.
ⓘ
PO and bid stay canonical
This register does not replace PurchaseOrder or BidRequest. Aggregates are counts and links, not a second contract store.
Flowcharts
1 — Inspect a vendor
Open the register, select a vendor, then follow linked bids and POs.
flowchart TD
A[Open Vendors] --> B[Scan register]
B --> C[Open a vendor]
C --> D[Review bids / POs]
D --> E[Jump to Sales / Finance]
- 1Open VendorsAdmin → Vendors (deep link).
- 2Select a rowMaster record plus aggregates.
- 3Follow contractsPurchase orders remain the financial source of truth.
Overview
Vendor master is a register over existing BidRequest and PurchaseOrder data. Do not invent a second vendor truth table.
How to use
1. Edit master carefully
Name and identifiers feed PO matching.
2. POs stay in Sales/Finance
This page aggregates; it does not replace Purchase Orders.