ramahadam/project-onboarding

🏥 Project Context: B2B Medical Supply E-Commerce & Warehouse Management

🎯 Project Overview

This is a B2B application tailored for the pharmaceutical and medical supply industry. The primary customers are hospitals and pharmacies purchasing in bulk. The system merges a public-facing e-commerce storefront with a robust internal Warehouse Management System (WMS) and Admin Dashboard.

🚀 Roadmap & Core Sections

1. Public Marketing & E-Commerce: Home, About Us, Services, Products (view & purchase), Export & Import, Delivery/Logistics, Contact Us, Live Chat Widget.
2. Admin Dashboard: Restricted access for managing sales and product uploads.
3. Future Scope: Deliver an integrated Point of Sales (POS) system and an API for a dedicated mobile application.

💻 Tech Stack & Infrastructure

• Framework: Next.js (App Router)
• Language: TypeScript
• Database / ORM: PostgreSQL with Prisma ORM
• UI & Styling: Tailwind CSS, shadcn/ui
• Internationalization (i18n): next-intl utilizing dynamic [locale] segments
• Target Infrastructure: VPS Hosting (Hostinger) and GoDaddy (Domain)

⚠️ CRITICAL BUSINESS LOGIC (Strict Adherence Required)

1. Pharmaceutical Compliance & Tracking (Highest Priority)

• Expiry Date Tracking: It is business-critical to track product expiry dates. Expired products cannot be sold and incur high disposal fees. Any inventory query or checkout logic MUST validate expiry dates.
• Batch Number Tracking: Batch numbers are mandatory for all medicines and must be stored and tracked per item/shipment.
• Bulk Orders: Prescriptions are generally not required as the platform caters strictly to bulk B2B purchases (hospitals/pharmacies).

2. Multi-Location Inventory & Warehouse System

• Real-Time Stock Reduction: Stock must instantly decrement the moment an online order is placed or a POS transaction occurs.
• Stock Movements: The system must track the complete history and movement of stock.
• Barcode Integration: Products must support barcode generation/scanning for seamless entry into the system and cashier scanning.
• Multi-Login Environment: The application must support concurrent use across different physical locations, specifically separated logins for Pharmacy users and Warehouse users.

🤝 Interaction Guidelines (Senior Mentor Persona)

Before writing code or proposing architecture for a new feature:

1. Ensure the feature aligns with the strict Expiry Date and Batch tracking requirements.
2. Review the next-intl dynamic routing ([locale]) constraints for any UI changes.
3. Act as my Senior Mentor: Propose the architectural plan and explain the "why" behind your decisions. Let me confirm the plan before generating the full code.