PRD: Master Data Management System¶

1. Goal & Overview¶

The Master Data Management (MDM) system is the foundational registry for all entities in Pebble Orchestrator. It enforces a strict multi-level promotion hierarchy (Prelead → Prospect → Customer) to ensure data quality and compliance before records are pushed to the ERP.

2. Master Data Hierarchy & Lifecycle¶

Level	Identifier	Mandatory Fields	Usage Restriction	Transition Trigger
Prelead Master	Prelead No.	Account Name	Restricted to Lead Ingestion only.	Manual or AI identification.
Prospect Master	Prospect No.	Legal Status, GST, PAN, CIN	Allowed for Enquiry & Quotation screens.	Successful Identity Validation.
Customer Master	Customer No.	Delivery Address, GST (Mandatory)	Allowed for Orders & ERP Sync.	Receipt of Order.

A. Validation Gates¶

Identity Verification:
- GST Search: GST Portal
- CIN Search: MCA Portal
Deduplication Rule: Duplicates are detected and blocked based on CIN Number at the Prospect level.

B. Transition Logic¶

Prelead → Prospect: Occurs when basic account details are enriched with valid corporate identifiers (GST/PAN/CIN).
Prospect → Customer: Occurs automatically when a Prospect record is linked to a confirmed Sales Order.
ERP Push: Only Customer Master records are synchronized with Tally Prime.

3. Advanced Sourcing & Grading¶

The system manages complex product-supplier relationships through a unified grading interface.

Grade Management Screen: A single interface to maintain all available product grades.
Tagging: Enables tagging Products and Suppliers to specific grades.
Grade Types: Support for distinct Buying Grades and Selling Grades.
Pricing Enforcement: Products tagged with "Frequent Fluctuation" in the Master are locked to Spot Pricing only in the Costing/Quotation modules.

4. Contact Intelligence¶

CC-Address Capture: When processing emails, any unknown contacts found in the CC field are automatically extracted and added as secondary contacts under the corresponding Company Master.

5. Mermaid Workflow: Master Data Promotion¶

graph TD
    subgraph L1["Level 1: Prelead"]
        P1[Create Prelead No.] --> P2[Mandatory: Account Name]
        P2 --> P3{Validate identity?}
    end

    subgraph L2["Level 2: Prospect"]
        P3 -- Validated --> PR[Generate Prospect No.]
        PR --> PR2[Fields: CIN/PAN/GST/Legal Status]
        PR2 --> PR3[Check Dedup via CIN]
        PR3 --> PR4[Usage: Enquiry & Quotation]
    end

    subgraph L3["Level 3: Customer"]
        PR4 --> O[Order Received]
        O --> CST[Generate Customer No.]
        CST --> CST2[Mandatory: Delivery Address]
        CST2 --> TALLY[Push to Tally ERP]
    end

← Back to Use Cases | View Platform Orchestration Lifecycle