Skip to content

Procurement — Preferred Vendor & Category Strategy Registry

Preferred vendor and category strategy entities reduce maverick spend and guide buyers—and buying agents—before PO creation.

Why this is needed

  • Maverick spend ignores preferred suppliers.
  • Category ownership is unclear.
  • Anomaly detection can flag off-strategy purchases.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Preferred list changes need Procurement approval.
historyEnabled true History of strategy changes.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: vendor_preference
displayName: Vendor preference
domain: Procurement
description: Vendor preference
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: pref_code
uniqueConstraints:
  - name: uq_vendor_preference_pref_code
    columns: [pref_code]
columns:
  - name: pref_code
    dataType: string
    nullable: false
    maxLength: 64
  - name: category_code
    dataType: string
    nullable: false
    maxLength: 64
  - name: supplier_code
    dataType: string
    nullable: false
    maxLength: 64
  - name: preference
    dataType: string
    nullable: false
    maxLength: 16
  - name: owner_team
    dataType: string
    nullable: false
    maxLength: 128
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

pref_code category_code supplier_code preference owner_team status
VP-IT-01 IT_HW SUP-2201 preferred Procurement IT active
VP-IT-02 IT_HW SUP-9999 banned Procurement IT active

Benefits for the company

  • Lower maverick spend.
  • Clear category ownership.
  • Agents recommend preferred vendors first.