ERP for curtain studio

About the Project

For a curtain workshop supplying various home furnishing stores and interior retailers, including several well-known retail chains, a custom ERP system was developed to support the entire order, production,, facturation and shipping process. The system is used across multiple workshops, including locations in Poland.

The platform supports the full flow from order processing to physical production. Orders are placed or retrieved from customers and automatically translated into production tickets, which are used by cutting machines to precisely cut fabrics. The individual components are then assembled by employees into the final product. The system supports virtually all common types and sizes of curtains, including custom-made configurations, and therefore forms the digital backbone of the production process.

My Role

After the departure of the senior developer, I took over the technical ownership of this project. Since then, I have been responsible for maintaining, further developing, and safeguarding the continuity of the ERP system. This involves not only resolving incidents, but also ensuring that a business-critical application — directly impacting production and delivery — remains technically sound and future-proof.

My responsibilities include:

• Implementing functional enhancements and technical improvements

• Analyzing and resolving production issues and process optimizations

• Structured dependency and version management, including updates of .NET, NuGet, and Node packages

• Maintenance and optimization of the Linux server environment and Docker configuration

• Migration and modernization of the CI/CD pipeline from Bitbucket to GitLab

• Setting up, monitoring, and improving build and release processes

Reflection

This project highlights that software development is not only about building new features. In a production environment, stability, clarity, and reliability are essential — especially when multiple locations depend on the same system. Continuously managing dependencies, modernizing tooling, and introducing changes in a controlled manner are just as important as developing new functionality.