DemandFlow Support Centre

VEN: Vendor

A vendor or supplier organisation providing goods or services, with financial terms, compliance, and performance tracking.

Entity properties

Use cases

A vendor or supplier organisation providing goods or services, with financial terms, compliance, and performance tracking.

VEN is the supply-side counterpart to CLIENT. It represents external organisations from which the business procures goods and services. The entity is structured around a full vendor lifecycle: onboarding (status field with onboarding state), financial management (payment terms, banking details, credit limits, spend tracking), compliance (business licenses, insurance, certifications including ISO, SOX, PCI, GDPR, and diversity classifications), and performance governance (quality/delivery scores, review dates, price competitiveness ratings). VEN links to PO (purchase orders) via a SUB|VEN|PO comboKey on the Purchase Orders panel, providing a consolidated view of all procurement activity with a vendor. The master agreement fields support long-term contract management. The vendor category classification (technology, facilities, manufacturing, etc.) enables spend analysis by category. Performance scoring with numeric quality and delivery scores plus a 5-point overall rating supports formal vendor review processes. The Documents panel stores contracts, certificates, and other compliance documentation.

Fields

Because this entity extends COM, some fields may actually be stored on the linked base record rather than on this record directly. See Entity Extension.

Basics

Primary contact

Address

Terms

Accounts

Policies & compliance

Supplier governance

Contracts

Additional Information

Attachments and additional panels

• File attachment on documents. Allowed types: *.
• Additional panels: map.

Relationships

• Lookups: df_extendObject points at a COM record; accountManager points at a PPL record.
• Extends: this entity extends COM. See Entity Extension.
• Related lists: PO via comboKey (format: SUB|VEN|PO).

Creating a Vendor via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "VEN",
  "level":    3500,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "status": "active",
  "description": "Example text",
  "email": "user@example.com"
}

Listing Vendors

GET /v1/entities/VEN/SUB

See also

• The DemandFlow Object Model
• System Fields
• comboKey: Hierarchical Relationships
• Entity Extension