Prices, discounts and surcharges as governed master data with validity, scale and precedence, tied to golden products and customers.
Today list prices live in the ERP, customer-specific prices in a CPQ tool, promotions in a spreadsheet and the web shop caches all three; a quote picks the wrong one.
With Lima the price conditions are read where they live, matched on condition type + key combination + validity and price list code, assembled field by field and published as one golden record per real price lists, with every source key underneath. The quotes and orders where a condition applied, and the invoiced price beside it are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Keys resolve to golden customers and products first, so a price for a merged customer applies to every source key.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Price list | list → customer group → customer |
| Product | family → product for scale discounts |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | amount is positive for a price and may be negative only for a discount currency is in the code list valid-to is after valid-from |
| Row | a customer-specific price references an active customer and an active product a scale has ascending quantities a promotion has an approver |
| Business | no two conditions of the same type overlap for the same key a discount stays inside the approved band for its customer tier the margin at the winning price stays above the family floor |
| Transactions in the bed | Read from |
|---|---|
| Quotes and orders | CPQ and ERP |
| Invoiced prices | billing documents |
| Promotions redeemed | web shop |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the quotes and orders where a condition applied, and the invoiced price beside it.
Cost floors visible to pricing and finance only; conditions editable by pricing with approval; sales reads the winning price. The twelve layers apply on every door; see security.
POST /api/v1/golden/price/resolve
{
"customer": "C-00842",
"product": "M-1183920",
"date": "2026-10-01",
"qty": 5000
}200 OK
{
"condition": "ZPR0 · scale 5,000",
"price": 0.0182,
"currency": "EUR",
"unit": "1",
"valid_to": "2026-12-31",
"margin_check": "pass"
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Condition headers and items read from KONH · KONP.
Open the SAP S/4HANA page →Price lists read from QP_PRICE_LISTS · QP_PRICE_LIST_ITEMS (REST: priceLists).
Open the Oracle Fusion Cloud page →Price books and entries read from Pricebook2 · PricebookEntry.
Open the Salesforce page →Condition read from CONFORMED.PRICE_CONDITION.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A components distributor governed 380,000 price conditions across two ERPs and a CPQ tool. Overlapping conditions for the same customer and product dropped to zero, and quotes stopped undercutting the approved floor.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 5 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Consumer goods, High-tech and semiconductor, Industrial manufacturing. The industry pages show the domains each starts with.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.