> ## Documentation Index
> Fetch the complete documentation index at: https://agents.concierca.ch/llms.txt
> Use this file to discover all available pages before exploring further.

# Procurement Config

> Per-tenant procurement configuration: demand weights, cutoffs, seasonality. Edit via agent or admin.

## 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](/for-agents/data-model/product-demand) and the [Procurement Queue](/for-agents/data-model/procurement-queue) compute — edit deliberately, via an admin or the procurement agent.

## How it gets data

No ingest endpoint. Rows are edited in the app (Data → Procurement Config) or over MCP with `data_row_update` / `data_row_create`. Both `key` and `value` are writable; `description` is maintained with the schema.

## 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 |

<Note>
  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.
</Note>

## Query it

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