Skip to content

Learn

Research Records and Reviews

Common customers: test cross-holding demand dependence

A portfolio can hold several suppliers that depend on one end customer. The companies may appear diversified by industry while sharing a demand decision. Build the customer map only where identity or common control is supported, and preserve anonymous concentration disclosures as unknown rather than guessing the customer from market rumors.

Read concentration disclosure within its scope

IFRS 8 includes major-customer disclosures alongside segment and geographic information. The existence of a concentration disclosure does not guarantee that a customer’s name is public. Inspect the applicable accounting framework and the actual issuer note before assuming that a threshold reveals a complete customer list.

Record whether the customer is a direct purchaser, distributor, platform or end user. Two firms selling to the same distributor may reach different underlying demand populations. Conversely, separately named subsidiaries can belong to one customer group. Establish the relationship with primary evidence rather than matching similar names alone.

Hypothetical common demand node

Assume a portfolio holds 12% in Supplier Clay, 8% in Supplier Flint and 10% in Supplier Moss. Clay discloses that Customer Harbor accounts for 30% of revenue. Flint identifies Harbor at 20%. Moss reports an unnamed customer at 25%, with no reliable identity evidence.

Customer-dependence worksheetHolding weightCustomer revenue shareMapped contribution
Clay / verified Harbor12%30%3.6%
Flint / verified Harbor8%20%1.6%
Moss / anonymous customer10%25%2.5%, unresolved identity

The verified Harbor-linked proxy is 5.2% of portfolio weight. The 2.5% anonymous contribution remains a separate concentration question. Adding it to Harbor would turn an unsupported identity assumption into a precise-looking exposure number. Omitting it entirely would hide a known dependence whose identity is uncertain.

Distinguish sales dependence from loss sensitivity

The holding-weighted revenue-share proxy is not a predicted portfolio loss. A customer can reduce one product line while maintaining another; suppliers can replace demand at different speeds. Revenue exposure also differs from profit exposure because margins and fixed costs vary.

Suppose Harbor reduces equipment purchases but continues maintenance spending. Clay’s equipment revenue and Flint’s service revenue may react differently. Add the supplied product, contract duration, purchase commitment and replacement-customer evidence. A customer name alone is not enough to establish identical operating effects.

Check the chain of demand

If Flint sells a component to Clay, which sells the finished product to Harbor, distinguish direct from indirect dependence. The two reported revenues describe different stages of the same demand chain. They should not be summed and called Harbor’s final spending without removing intermediate transactions.

Also check the reporting period. An acquired business or changed customer mix can make last year’s concentration a poor description of current activity. Use the disclosed date and identify any more recent contract evidence instead of silently treating the percentage as live.

The next review should verify whether the customer relationship persists, whether revenue concentration changes and whether the relevant product demand is actually affected. The final table should separate verified common customers, anonymous concentrations and inferred downstream links. This workflow prioritizes operating research and does not recommend position changes or claim that a named customer’s decision determines future security prices.

FAQ

Can an unnamed top customer be identified from industry commentary?

Treat commentary as a lead, not confirmation. Keep the customer anonymous until reliable primary evidence establishes the link.

Does matching customer share imply matching profit sensitivity?

No. Product margins, contract terms, costs and replacement opportunities differ. The revenue map is only an initial dependence measure.