Procurement Config

What it is

Per-tenant procurement configuration — the tuning knobs behind the demand and ordering math: demand-window weights, cutoffs, seasonality damping, watch factors, the family-derivation rule, and similar. One row per config key, with a JSON value and a plain-text description explaining what the key controls (shown next to the value in the app).

Changes here shift what Product Demand and the Procurement Queue compute — edit deliberately, via an admin or the procurement agent.

Fields

Field	Label	Type	Writable	Description
`id`	ID	text	read-only	Internal row id
`key`	Config Key	text	✓	Config key name (e.g. demand weights, cutoff days, family rule)
`value`	Value	json	✓	The configured value (JSON — number, string, or object)
`updated_at`	Updated	datetime	read-only	Last change
`description`	Description	text	read-only	Plain-text explanation of what this key controls; shown next to the value

Like every workspace table, the config also carries the system columns tenant_id, workspace_id, and created_at — set automatically. Keys are unique per tenant.

{ "method": "tools/call", "params": { "name": "data_query", "arguments": { "view_slug": "procurement_config", "select_fields": ["key", "value", "description"], "limit": 100 } } }

AI Operating Guide

Vertical Intelligence

Getting Started

Governance

Resources

Sales & Commerce

Procurement

Marketing & Outreach

What it is

How it gets data

Fields

Query it

​What it is

​How it gets data

​Fields

​Query it

What it is

How it gets data

Fields

Query it