Domain catalogue Products

Price lists and conditions

Prices, discounts and surcharges as governed master data with validity, scale and precedence, tied to golden products and customers.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSalesforceCRMSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN PRICE LISTS AND CONDITIONSPrice lists and conditionsone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the price lists and conditions record comes from, how it is assembled, and who reads it. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

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.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Conditiontype, key combination (customer, product, plant, channel), amount, currency, unit, scale
wins: ERP pricing tables
Validityvalid-from and valid-to, version, approval
wins: ERP and approvals
Precedenceaccess sequence: which condition wins when several apply
wins: pricing procedure
Ownershipowner, approver, reason for change
wins: stewards and workflow
How records match

The keys, in order

condition type + key combination + validityprice list code

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.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Price listlist → customer group → customer
Productfamily → 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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columnamount 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
Rowa customer-specific price references an active customer and an active product
a scale has ascending quantities
a promotion has an approver
Businessno 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
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Quotes and ordersCPQ and ERP
Invoiced pricesbilling documents
Promotions redeemedweb shop
realised price vs listdiscount depth by tiermargin by product familyconditions expiring next month

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.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

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.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/price/resolve
{
  "customer": "C-00842",
  "product": "M-1183920",
  "date": "2026-10-01",
  "qty": 5000
}
response
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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

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.

illustrative scenario · Price lists and conditions
Terms on this page

ConditionOne pricing element: a price, discount, surcharge or tax, with the keys that select it.
Access sequenceThe order in which condition keys are tried until one is found.
ScaleQuantity or value steps with a different amount at each step.
Golden recordThe one record for a real price lists, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 5 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Consumer goods, High-tech and semiconductor, Industrial manufacturing. The industry pages show the domains each starts with.

See your first domain built on your data

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.