Skip to content

PRD: Product Management System (Product Master)

1. Goal & Overview

The Product Management module is the "Scientific Heart" of Pebble IQ. It manages technical specifications, complex synonyms for buyers/suppliers, and document compliance (COA/MSDS) to ensure precise matching between supplier offerings and customer requirements.


2. Technical Data Points

The following technical fields are mandatory for the Product Master:

Field Description
Common Name The standard industry name used internally.
Short Name Abbreviated name for reports and small-form displays.
IUPAC Name Formal chemical nomenclature.
Density Specific gravity or density of the product.
E Code International additive/technical identifier.

3. Synonym & Search Logic

The system must handle multiple synonyms that can differ between suppliers and customers.

  • Synonym Mapping: All synonyms must be tagged to specific Customers or Suppliers.
  • UI Distinction: In search results and product screens, synonyms must be clearly labeled (e.g., "Synonym: Zinc Dust" vs "Common Name: Zinc Oxide").
  • Searchability: The global search bar must support lookups via synonyms, common names, and short names.

4. Documentation & Compliance (COA/MSDS)

A. Tagged Attachments

Attachments are not just files; they are linked to specific Supplier + Product combinations. - Example: A COA for "Zinc Dust" provided by "Avra Science" is tagged specifically to that pairing. - Standard COA: A "Standard COA" reference must be maintained for entire Product Families.

B. In-Line Specifications

The following documents must be attached as line items: - COA (Certificate of Analysis) - requires Expiry Date tracking. - MSDS (Material Safety Data Sheet). - MOA (Method of Analysis). - Specifications Sheet.

C. Visual Assets (Tabs)

A dedicated tab for visual documentation including: - Product Photos. - Packing Photos (Bags/Drums). - Label Photos.


5. Relationships & Tagging

A. Industry & Category

  • Industry Masters: A central registry of industries (e.g., Rubber, Pharma, Paints).
  • Campaign Logic: Campaigns are run based on Product Categories and Industries.
  • End Product Tagging: Products must be tagged to the end products they help create (e.g., Zinc Oxide tagged to "Automotive Tires").

B. The Integration Triad

All records must be searchable via the triad: Customer ↔ Industry ↔ Product ↔ Our Company (Entity).


6. Business Decision Logic

The system assists in evaluating the viability of leads based on four variables: Product Strength, Buyer Seriousness, Supplier Availability, and Margin.

Case 1: Discard & Escalate

  • Conditions: Product is not strong, Buyer is not serious, Supplier is not available, Margin is low/absent.
  • Workflow: Discard the lead.
  • Action: Automated email notification to HOD/Management for approval of discard.

Case 2: Database Enrichment & Soft Follow-up

  • Conditions: Product is not strong, BUT Buyer is serious; Supplier unavailable, Margin low.
  • Workflow: Add buyer details to the CRM for future potential.
  • Action: Automatically send our Company Brochure to the buyer for other products.

7. Operational Controls

  • Supplier-Grade Tagging: Multiple suppliers can be tagged to a single product Grade.
  • Draft Reports: A dedicated view/report for masters that have been created but not yet sent for approval.
  • Mass Mailing: Direct reports tool to send attachments to suppliers/customers via automated mail.

← Back to Use Cases | View MDM PRD