managing products and suppliers manually leads to duplicate records, inconsistent data, and no clear relationship between which supplier provides which products. a structured system with enforced relationships solves this.

a laravel mvc web application for managing products and their suppliers with a one-to-many relationship — one supplier can have many products, each product belongs to exactly one supplier. full crud on both entities, eloquent orm for relationships, blade templates for the ui.

chose laravel for its clean mvc separation, eloquent's readable relationship syntax, and blade's template reuse — all of which keep the codebase maintainable even as it grows. used database migrations for version-controlled schema changes rather than manual sql.

demonstrates proper mvc architecture, relational database design with enforced foreign keys, and clean backend development practices — the kind of foundation that scales to larger systems.