Headless project rescue

fixing what others left broken

We helped a struggling headless e-commerce project move from instability to a reliable, scalable platform, fixing what others broke.

About the project

The client approached us to take over an ongoing e-commerce project built on a headless, modular architecture.

Medusa.js

For backend product and order management

Next.js

For frontend and landing pages

Strapi CMS

For whole content management

Despite over 2,500 development hours already invested by a previous agency, the system was far from ready for everyday business operations. The platform suffered from failed transactions, broken product data, malfunctioning integrations, and lacked even basic deployment and documentation processes.

With customers impacted and business at risk, the client needed immediate technical stabilization, fast. They needed a partner who could stabilize the system, restore control over environments, and give the platform a reliable foundation for future growth.

The challange

When we stepped in, the situation was urgent.

The previous agency put in over 2,500 development hours a year, and yet the store was struggling with serious issues.

.

Broken key functionalities

Product feeds, vouchers, shipping methods

Critical checkout failures

500 errors on Product Pages

Hard-coded logic

For every product variants

No proper documentation

Missing configuration files, no working local or staging environment

Validation issues

In forms - every field validated incorrectly

Synchronization problems

Between PCMarket ERP and Medusa database

Missing Git commits

For production changes

Unstable SSR*

*Server-Side Rendering on the frontend

Instagram feed

Was broken with multiple uploads

The frontend and backend were misaligned, the infrastructure was chaotic, and basic maintenance tasks were risky.

The store was barely holding together, with bugs affecting real customer experiences.

Our solution

We approached the project systematically, treating it as a full rescue operation.

First – takeover and stabilization

Within the first 50 hours, our development and DevOps team:

All of this was done without any initial project documentation, no .env files, no README, and no working staging setup – purely based on code inspection and recovery best practices.

This allowed us to stabilize the most urgent issues without putting the live store at risk.

Technologies we used

  • Frontend

    Next.js 14 (with SSR/ISR), React, TailwindCSS, Formik

  • Backend

    Medusa.js (Node.js), TypeORM, REST API integrations

  • CMS

    Strapi v4 with customized rich text editor (CKEditor 5)

  • Databases

    PostgreSQL (separate for Medusa and Strapi)

  • Integrations

    •   PCMarket (ERP) for product and stock synchronization
    •   Autopay for payment processing
    •   Apaczka for logistics (shipment labels, pickup point maps)

  • Infrastructure

    •   Vercel for frontend builds and deployments
    •   Digital Ocean VPS for backend services (Docker-based deployment)
    •   EasyPanel for server management and deployments

Project in numbers

We used a Kanban project management approach, with weekly updates and close collaboration with the NFC Wear team to ensure fast delivery and clear communication.

0 h+

Spent by the previous agency (before takeover)

0 h

for full project takeover and first fixes

0 h+

Spent to stabilize the platform

0 +

Tasks completed during rescue and optimization

0 +

Products synchronized from external ERP (PCMarket)

The outcome

After a few months of intensive work, the project landscape changed completely:

Stabilized production store

ready for ongoing operations

Fully working staging environment

synchronized with production

Reliable CI/CD pipelines

making deployments faster and safer

Fixed critical bugs

affecting customer experience and revenue

Clear project structure

enabling easier maintenance and future development

Most importantly, the client now has full control over their platform, with significantly reduced operational risk compared to the chaotic state we inherited.

Comment from the expert:
In the same amount of time (~300 hours), the client could have replatformed entirely to a clean Shopware 6 setup, with a fully working store and significantly more modern features. However, stabilizing the current system was necessary first due to operational risks.

We deliver results where others fail.
If you’re looking for a partner who can stabilize, optimize,
and grow your system – let’s discuss your needs.