1. Business Purpose Build a “Management OS” for a cosmetics trading business. Purpose: Unify all daily business operations into one operational platform so that after login, the owner can instantly understand: What must be done today Financial status Order progress Cash flow risks Sales opportunities This system acts as a decision-making dashboard, not just software. 2. Business Goal Replace fragmented workflows currently handled by: Multiple Excel files Email communication Manual trade documentation Separate inventory tracking Manual financial monitoring Target outcome: One connected workflow from: Lead → Order → Procurement → Shipment → Payment → Accounting 3. Important Architectural Direction The client mentioned Zoho during discussion. Meaning: The expectation is likely NOT building everything from scratch, but: A system that either: integrates with Zoho ecosystem, or extends Zoho as the operational backbone. So the project direction becomes: Custom Business Layer Zoho services Automation rather than full standalone ERP development. 4. Expected Role of Zoho Zoho can serve as base infrastructure for: CRM Database Workflow automation User management Basic reporting Possible mapping: Zoho CRM Customer / Lead management Zoho Creator Custom business app (Order / Inventory / Workflow) Zoho Books Accounting linkage Zoho Flow Automation between services Zoho WorkDrive Document storage 5. System Concept Central idea: Order-based management. Everything connects to an Order: Customer Products Suppliers Inventory Documents Payments Timeline Example: One Order contains: Quotation → Purchase → Invoice → Shipment → Payment → Archive. 6. Core Functional Requirements 6.1 Data Integration & Cleansing Input: 10,000+ product data 9 supplier Excel formats product images Requirement: Developer consolidates all data using JAN code as key. Output: Unified product master usable inside system. Business purpose: Prevent pricing mistakes and duplication. 6.2 Dashboard (Most Important Screen) Login screen must immediately show: Operational alerts Example: invoices not issued unpaid orders supplier replies pending Cash flow overview Incoming vs outgoing payments Management simulator Change expenses → profit recalculated instantly Quick actions Upload order Generate documents Run AI tools Goal: Owner understands business condition in seconds. 6.3 Automatic Sales (Apollo Integration) Functions: Sync leads from Apollo Send follow-up emails automatically Stop sequence when reply detected Log all automated actions Purpose: Create “digital employee” performing sales automatically. 6.4 Order Management System manages work per Order. Includes: Quote Supplier response Order confirmation Shipment Payment tracking Customer history view required. 6.5 Procurement & Inventory When order confirmed: System checks stock. If shortage: Generate purchase order automatically. Supports: Split purchasing across suppliers. 6.6 Trade Compliance Required for EU / US export. System must manage: INCI ingredient names HS codes Logic priority: Internal dictionary → External DB → AI assistance. 6.7 Trade Documents One-click generation: Commercial Invoice Packing List Auto-calculated: Cartons Weight CBM Exchange rate must be manually locked per quotation. 6.8 Payment & Cash Tracking Support installment payments. Example: 30% deposit 70% balance System auto-creates payment tasks. Status visualization: Unissued / Waiting / Completed. 6.9 AI Proposal Creation Button generates: Product proposal PPT automatically. Layout: 4-direction product images INCI table Packaging specs. 6.10 Document Archive All generated documents automatically saved. Search by: Order Customer Date. 6.11 Permission Control Three roles: Admin Office staff Warehouse Financial information must be hidden from non-admin users. 6.12 Traceability (Lot Management) Requirement: Track: Lot number Warehouse entry Shipment destination Purpose: Recall traceability. NOT manufacturing date decoding. 7. Development Approach Two-step development. Step 1: Data foundation + prototype + core workflow. Step 2: Full automation + AI + financial + operational completion. 8. Correct Technical Interpretation Client expectation is closer to: Business System Configuration Custom Logic Development Integration Engineering NOT pure custom infrastructure engineering. So likely stack direction: Zoho platform as base Custom backend logic where necessary Automation scripts AI integrations Dashboard customization 9. What This Project Actually Is Practically: Zoho-centered Trade Management OS with heavy customization and automation.