Modernize & Scale Next.js E-Commerce Platform

I have a few questions.
1. Is the current platform already built with Next.js v14, NestJS, PostgreSQL, and Auth.js, or is part of the stack still legacy?
2. What are the biggest current problems: slow performance, messy code, broken checkout, poor API structure, database issues, or security concerns?
3. Is this a live production store with active users/orders, or still in staging?
4. Do you have documentation for the current APIs, database schema, and payment flow?

A few questions to scope this accurately:
1. What does the current legacy stack look like, and what's the biggest pain point right now?
2. Is this a full refactor or selective modernization of specific modules?
3. What's your timeline expectation for Phase 1?

Hi Max, could you confirm which priority flow should be modernised first: account, checkout, order, or payment, and whether Stripe/Auth.js work should be included in that first milestone?

Hi Max,

Thanks for the invite.

1. Is the platform already in production with active users/orders?

2. What is your deployment infrastructure?

3. Is Stripe already partially integrated?

I’d be happy to review the existing repository and provide a more accurate roadmap, timeline, and phased implementation plan.

Best Regards.

*** Quick questions:

– Is the current system already using a monorepo structure or separate frontend/backend repos?
– Should we prioritize refactoring first or run migration and feature development in parallel?

Hello Mr. Max K,

Are you mainly looking to improve scalability, performance, or maintainability first in the current Next.js/NestJS architecture?

1. Before restructuring the legacy codebase, do you already have specific performance bottlenecks or scalability pain points identified within the current platform, or should the modernization process begin with a full architectural and performance audit first?


2. For the Stripe integration layer, will the platform primarily support one-time purchases, subscriptions, or a hybrid billing model with future scalability for multi-plan and usage-based payment flows?


3. As the platform scales, would you prefer the refactoring strategy to prioritize maintaining backward compatibility with existing workflows first, or are you open to restructuring core modules more aggressively for long-term scalability and maintainability?

Hi Max, One thing I’d like to understand is whether the current pain point is mainly scalability/performance under load or technical debt slowing development, and whether you already have CI/CD + testing pipelines in place or want that improved as part of the modernization process?