AArvindExecutive Cockpit

Customer Master · Golden Record

The single view of the customer the legacy mills never had — the same brand account, mastered across SAP and every legacy mill system, resolved into one.

Arvind Limited · FY26 (Mar'26, actuals)
Among the world's largest denim makers
25,800 employees · 12+ plants & units · 30 export markets
Executive read· the answer, then the moves

24 fragmented records across 7 source masters resolve to 10 golden records — a 58% duplicate rate collapsed on merge. Reconcile the 7 customers with conflicting payment terms to stop cash leakage and unlock the 9 cross-division accounts.

10 of 24 records resolved to golden · 14 duplicates collapsed · 7 term conflicts open

Do now — ranked by urgency
  1. 1
    Reconcile 7 customers with conflicting payment termsAct now
    Why it matters

    The same buyer sits on Net 30 in one brand and Net 60 in another across 7 accounts — direct cash leakage and credit risk a single master removes.

    What's driving it
    • 7 customers carry conflicting terms
    • 58% duplicate rate across 7 systems
    FYI
    • Conflicts surfaced to credit and sales
    • Total exposure netted across brands
  2. 2
    Collapse the 14 remaining duplicate recordsWatch
    Why it matters

    24 raw records reduce to 10 golden — finishing survivorship gives every team one account, one team, one set of terms.

    What's driving it
    • 14 duplicates collapsed on merge (58%)
    • 24 records across 7 source masters
    FYI
    • Match → merge → survive → reconcile
    • Borderline matches queued for a steward
  3. 3
    Activate 9 cross-division customers for cross-sellOpportunity
    Why it matters

    9 golden records are already served by ≥2 divisions — the resolved master is the sell-up-the-chain base no single mill system could see alone.

    What's driving it
    • 9 customers served by ≥2 divisions
    • 10 golden records mastered
    FYI

    Golden record is the join key for Customer 360 and Cash 360

🌱 Sustainability & circularityStep 6 of 7 · resolve the golden record (MDM)Transformation 360Order / Quoting 360All journeys
🌐 Enterprise 360 modules· on Customer MasterBrowse all 31 views ▾
● LiveBuilt forSales / Key Accounts· one account, one teamCredit / Finance· one set of terms & exposureData / MDM· dedupe & survivorship

Each division and legacy mill kept its own customer list, so Levi Strauss, GAP and H&M each exist several times across the systems — with different names, IDs and even payment terms. Until they're resolved, no one can see the true relationship, total exposure, or cross-sell base. This is the golden record AI builds on top of the mesh.

Data backing: customer_source (SAP + legacy mill CRM fragments) · entity resolution · survivorship rules
7
Source masters
SAP + legacy mill CRMs
24
Raw customer records
across all systems
10
Golden records
after AI resolution
58%
Duplicate rate
collapsed on merge
9
Cross-division customers
served by ≥2 divisions
7 customers carry conflicting payment terms across systems — the same buyer on Net 30 in one brand and Net 60 in another. That's direct cash leakage and credit risk a single master removes.
One customer, every system

Pick a customer → see its fragments merged

The ★ master survives; the rest merge with a match confidence. Conflicting terms are flagged in red.

Customers · # source records
★ Golden record

Levi Strauss & Co.

resolved from 4 source records · master = Arvind CRM (Salesforce)
Consolidated AR
₹344 Cr
Survivorship terms
Net 60
Sources merged
4
Term conflict
Yes — review
Match confidence
94%
Source records merged into the golden record
Source systemName as storedIDTermsARMatch
Arvind CRM (Salesforce)Levi Strauss & Co.ACCT-10231Net 60₹120 Crmaster
0Denim mill legacy (ERP)Levi StraussDEN-4471Net 90₹88 Cr96%
0Garments MESLevi'sGAR-2208Net 60₹72 Cr92%
0Export docs (LC)Levi Strauss & Co (US)EXP-882LC at sight₹64 Cr88%

Conflict: payment terms differ across systems (Net 60 vs Net 90 vs LC at sight). Survivorship keeps the master's Net 60; the others are flagged for credit to reconcile — exactly the kind of leakage a single view removes.

Cross-division signal: Levi Strauss & Co. is served across 4 Arvind divisions / systems. That's a relationship to coordinate (one account team, one set of terms) — and a sell-up-the-chain base already inside the house.

How AI builds the golden record

Match → merge → survive → reconcile

1 · Match

Fuzzy + LLM matching on name, address and tax ID links 'Levi Strauss & Co.', 'Levi Strauss' and "Levi's" to one entity — with a confidence score, not a blind merge.

2 · Merge

Records above the confidence threshold collapse into one; borderline matches are queued for a human steward.

3 · Survive

Survivorship rules pick the winning value field-by-field (most-recent, most-complete, or the governed source) to form the golden record.

4 · Reconcile

Conflicts — different terms, duplicate AR — are surfaced to credit and sales, and total exposure is netted across the brands.

The golden record is the join key for everything else: it lets Customer 360 show one account, Cash 360 net one exposure, and the cross-sell engine see that a customer already buys from two divisions — the same entity-resolution layer that powers the plant-grain and order/quoting views.