The data model is yours to define
Conditionality does not force you into a fixed schema. You get a head-start from industry templates, then shape the data model around your own definitions - so what we capture matches how your business actually thinks, and maps cleanly into the systems you already run.
Capturing a commercial agreement well is not one trick. Conditionality combines several technologies - language models that read messy source content, a typed schema engine, deterministic validation, and source-level provenance - into a single structured data model that you define, own, and keep. That model, not any single step, is what holds its value across a year of an agreement and its amendments.
- Typed fields you define, with the options and validation you control
- A schema that constrains every capture, so records come out comparable
- A data model that is yours, versioned and audited as it changes
- Captured data that persists as a tracked record: the condition ledger
- Every value traced back to its exact source quote
- Every field mappable into the systems you already run
That is the difference between an answer you read once and a system of record you can plan, track, and integrate against.
Pick an industry template - grocery, foodservice, DIY - and begin with a sensible set of fields on day one instead of a blank schema.
Add the facts that matter to your business. Your definitions live in the same data model as the template, with the types, options, and validation you control.
Point each field at the matching column in your ERP, BI, or planning tool, so the structured data integrates with whatever you already run.
| Field | Type | Options / validation | Source |
|---|---|---|---|
| Promo mechanic | Select | TPR · Multibuy · Display · Feature | Grocery template |
| Rebate basis | Select | Net invoiced · Gross · Volume | Grocery template |
| Rebate rate | Percent | 0-100, 2 decimals | Grocery template |
| Funding split | Percent | Supplier / retailer share | Grocery template |
| Valid from / to | Date range | Required | Grocery template |
| Buying group | Select | Your option list | Your definition |
| Category role | Select | Traffic · Profit · Image | Your definition |
| Internal SKU | Text | Pattern AM-#### | Your definition |
| ERP material no. | Text | SAP MATNR | Mapped: SAP S/4HANA |
| Customer hierarchy | Text | SAP KNVH node | Mapped: SAP S/4HANA |
Template fields give you the head-start; your own fields sit right beside them with their own types and validation; and any field can be mapped to a column in an external system.
Define a field once and it joins your schema, applying to every future capture. Industry templates fill these in for you to start.
Because every field is part of one model you control, the captured data can map to and integrate with any system you require - ERP, BI, trade-planning, or an enterprise data platform - rather than living in yet another silo.