MC
ENIT
E-commerce / Back-office gestionale2025–2026

Piattaforma e-commerce

I worked on this project as a Full Stack Developer, following the entire development of the platform: from the initial database and backend design to the implementation of the Angular interfaces. The project included both a management area for products, categories, customers, inventory, media, prices, price lists, users and permissions, and a customer-facing e-commerce section with product catalog and cart.

Anonymized case study

Company project with a private repository and no shareable screenshots. The content describes responsibilities, features and technical choices without exposing sensitive data.

Anonymized e-commerce platform architectureDiagram with Angular back-office, Angular storefront, ASP.NET 8 API and persistence systems.Architecture overviewAnonymized structure for back-office, customer frontend, API and data persistence.Angular 18Back-officeAngular 18E-commerce frontendASP.NET 8 APIApplication backendDomain logicPostgreSQLMongoDBElasticsearchPrivate company project represented as a non-sensitive technical diagram.

Overview

This project was created to build a proprietary platform for managing an e-commerce business in a more structured way. It was not just about creating a product storefront, but also about building everything needed behind the scenes: catalog, inventory, customers, price lists, media, users, roles and permissions. I handled the end-to-end development, working on both the backend and the frontend interfaces.

Context

The project was developed in a professional context for a company. Since the platform is not public, the repository is private and no shareable screenshots are available, I present it as an anonymized technical case study. The goal here is not to showcase the final product visually, but to describe my responsibilities, the implemented features and the technical decisions involved in the development.

Problem

An e-commerce platform is not only about the product page visible to customers. The most complex part is often the internal one: organizing the catalog, updating prices and price lists, managing inventory, associating media with products, controlling user access and enabling fast searches across large amounts of data. The challenge was to create a single system that made these workflows more organized and manageable.

Objective

The goal was to build a solid foundation for a complete e-commerce platform: a backend capable of handling different types of logic and data, a coherently designed database and a frontend usable by both internal operators and end customers. The result had to be practical, modular and flexible enough to support the evolution of the project over time.

Solution

I started by designing the data structure and backend architecture, defining how the main information in the system should be organized. The ASP.NET 8 backend was connected to different persistence technologies depending on the type of data to manage: PostgreSQL for more structured entities, MongoDB for more flexible data and Elasticsearch for search and advanced filtering. On the frontend, I built both the back-office management area and the customer-facing e-commerce section using Angular 18, Bootstrap and Angular Material.

Main features

  • Product catalog with category, media and commercial information management
  • Customer management and data related to e-commerce operations
  • Inventory, price and price list management
  • User system with customizable roles and permissions
  • Filters and advanced search powered by Elasticsearch
  • Administrative back-office for internal operators
  • Customer-facing e-commerce page with product catalog and cart

My role

  • Architecture: initial design of the database, backend and organization of the main data structures.
  • Backend: development with ASP.NET 8 and integration with PostgreSQL, MongoDB and Elasticsearch.
  • Frontend: implementation of the management back-office and the customer-facing e-commerce area with Angular 18.
  • Management modules: implementation of products, categories, customers, inventory, media, prices and price lists.
  • Access control: creation of the user system with customizable roles and permissions.
  • Search: development of filters and advanced search to make information easier to retrieve.

Technical choices

  • The architecture was designed by separating the back-office, customer-facing area, application backend and persistence layers, keeping internal workflows distinct from end-user flows.
  • PostgreSQL was used for the more relational entities of the domain, such as products, categories, customers, price lists, users, roles and permissions.
  • MongoDB made it possible to handle more flexible information, useful when some data did not require a rigid schema.
  • Elasticsearch was integrated to support filters and advanced search, improving information retrieval within the catalog.
  • Angular 18 made it possible to build modular interfaces for both the back-office and the customer-facing e-commerce section.
  • The role and permission system was designed to be customizable, avoiding a rigid model based only on administrator and standard user roles.

Outcome

The project resulted in a complete application foundation for managing catalog, customers, inventory, price lists, users, permissions, search and cart from a single system. The main value was connecting data architecture, backend, back-office and e-commerce frontend into one coherent platform.

Want to turn a complex idea into a solid product?

Tell me about the goals, constraints and main workflows. I will help you design a clear, scalable technical foundation ready to grow.

Talk about the project