MegaStark β Renovation Workflow Platform
MegaStark connects a German-language customer website and account with an ERP for renovation services and bespoke bathroom products. Measurement requests, orders and materials have dedicated interfaces.
Project Goal
Bring customer enquiries and the operational work behind a renovation into one system: collect measurement requests, organise orders, maintain the material catalogue and coordinate specialist roles.
Solution and Architecture
A Next.js website introduces services and gives customers access to their requests and orders. A separate React ERP serves managers, contractors, estimators, draftsmen and production staff. The NestJS API and PostgreSQL database model the workflow from measurement to fulfilment; Prisma manages relational data and Socket.IO supports chat. Source modules also cover drawings, materials documents, photo reports and acceptance protocols. A separate Next.js landing introduces tiling services. The case documents the web platform; the phone view is responsive web access.
Inside MegaStark
Original screens from the local portal and ERP, connected to an isolated API and a small fictional dataset.
Screens use fictional customers, catalogue entries, requests and linked orders in a separate local database. No production database was copied. Email, SMS, WhatsApp, analytics, payments and external service actions are disabled or blocked. Example statuses and prices are demonstration data. Payment processing, supplier exchange, calendar synchronisation and the complete fulfilment lifecycle were not verified.
Advantages
- π Keep enquiries organised β measurement requests show the customer, category and current status.
- 𧱠Maintain a shared catalogue β articles group material information, units and prices.
- π οΈ Coordinate specialist work β the source separates manager, contractor, estimator, draftsman and producer roles.
- π Keep order documents in context β dedicated workflows cover drawings, material files and acceptance protocols.
- π± Follow requests on a phone β the customer account has a responsive web interface.
- π¨ Explore bathroom finishes β Freedom 120 previews available material combinations before an order request.
Technologies
Verified in the project source: Next.js 14, React 18 and TypeScript for the customer portal; React, Vite, Tailwind CSS and Redux Toolkit for the ERP; NestJS, Prisma, PostgreSQL and Socket.IO for the API and data layer. Source integrations include calendars, supplier exchange and payments; their presence does not establish that they were verified in this demonstration.
Developing a renovation platform with a customer portal and ERP
MegaStark illustrates how public service pages, customer access and operational interfaces can share a structured backend without forcing every participant into the same screen.
Visual configuration before an order
The Freedom 120 configurator provides separate choices for the vanity unit, wall and floor. Material filters organise the available finishes and the preview changes to a prepared render for the selection. This is a render-based web configurator, rather than a claim of a real-time 3D engine. The case shows its real interface and the selected Agate Blue Velvet finish.
From a measurement enquiry to an order
Renovation work starts with information about the property and required service. MegaStark separates the measurement request from the subsequent order, so customer details, categories and processing stages retain their own context. The local demonstration shows both types of records and their relationship.
Materials and specialist roles in the same architecture
A renovation platform needs more than a contact form. The source contains articles, units, material sets, drawings and roles for the people involved in delivery. A React ERP handles operational views while the Next.js portal gives customers a separate interface. The NestJS API models the shared records in PostgreSQL through Prisma.
What the case demonstrates
The screenshots document real local screens with fictional data. They show measurement requests, a material catalogue and customer access, without claiming measured time savings or commercial growth. Related web application and business system cases provide further examples; our services page describes how to discuss a similar project.