Domain catalogue Parties

Distributors and channel partners

Resellers, distributors and agents as one party record with their territories, tiers, agreements and the sell-through data that measures them.

SOURCES, READ IN PLACESalesforceCRMSAP S/4HANAERPOracle Fusion CloudERPSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN DISTRIBUTORS AND CHANNEL PARTNERSDistributors and channel partnersone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the distributors and channel partners record comes from, how it is assembled, and who reads it. Other systems have their own page.
4 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 a distributor is a customer in the ERP, a partner account in the CRM and a row in the rebate spreadsheet, and the rebate is paid on the spreadsheet's numbers.

With Lima the channel partners are read where they live, matched on partner id and legal entity (golden customer), assembled field by field and published as one golden record per real distributors, with every source key underneath. Orders, sell-through reports, accruals and payments for the partner, by programme 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.

Identitylegal entity (golden customer), partner type, tier, since
wins: CRM and ERP
Coverageterritories, product lines, exclusivity, valid dates
wins: channel management
Agreementsrebate and discount programmes, targets, validity
wins: finance and channel
Performancesell-in, sell-through, inventory reports, attainment
wins: derived from transactions
How records match

The keys, in order

partner idlegal entity (golden customer)

A channel partner is a role on a golden customer, so orders, credit and rebates meet on one record.

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
Programmeprogramme → tier → partner
Territoryregion → country → partner

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
Columntier is in the programme's list
valid-to is after valid-from
Rowan exclusive territory has exactly one partner
a partner with a rebate agreement reports sell-through
Businessrebate accruals equal the programme's rules applied to sell-in and sell-through
attainment by region equals the sum of its partners
no partner holds two conflicting exclusivities
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Sell-in ordersERP sales orders
Sell-through and inventorypartner reports
Rebate accruals and paymentsfinance
sell-in and sell-through by monthattainment vs targetrebates accruedinventory weeks at partner

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens orders, sell-through reports, accruals and payments for the partner, by programme.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Rebate terms visible to channel management and finance; territories to sales; the partner sees its own record on the portal. 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/partner/lookup
{
  "customer": "C-00842"
}
response
200 OK
{
  "partner_id": "PT-0331",
  "tier": "gold",
  "territories": [
    "US-West"
  ],
  "programmes": 2,
  "attainment_ytd": 0.87
}

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 high-tech vendor paid rebates on partner-reported numbers reconciled by hand. With sell-in from the ERP and sell-through reports on one partner record, accruals became a rule, and the quarter-end dispute list shrank from 40 partners to 3.

illustrative scenario · Distributors and channel partners
Terms on this page

Sell-throughWhat a partner sold onward, as reported by the partner.
Rebate programmeRules that pay a partner back a share of purchases against targets.
ExclusivityA territory or product line assigned to one partner only.
Golden recordThe one record for a real distributors, 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; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

High-tech and semiconductor, Consumer goods, 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.