About the project
MyBenefit is part of the European Benefit Systems Group, the creator of Poland’s most popular employee benefits platform. The company serves thousands of partners and operates the country’s largest cafeteria platform in terms of available benefits.
The cafeteria system is a digital platform where employees exchange points granted by their employer for specific benefits, including sports, culture, recreation, and leisure activities. The cafeteria platform is the company’s core business module and serves as the foundation of the entire MyBenefit ecosystem.
fireup.pro joined the project in cooperation with Avra, taking responsibility for four key platform modules.
Reactivation of the corporate events settlement module
Subscription benefits microservice implementation
Cinema migration
Subscription management module
Customer experience
The people at fireup.pro are professionals in terms of maturity, expertise, and work culture. Working with them is a genuine pleasure. I appreciate their transparency, communication skills, and willingness to take on challenges in new projects.
Paweł Czaja
Product Owner, MyBenefit
From challenge
Key Challenges
Reactivating a frozen project for a strategic client
Reactivating a frozen project for a strategic client
A cafeteria module developed for one of MyBenefit’s largest clients had been inactive for some time. Reactivating it required restoring the system state, analyzing new requirements, and redesigning the business logic without disrupting the operation of the rest of the platform. Direct on-site analysis and grooming sessions at the client’s headquarters helped define requirements precisely and shorten the feedback loop between the technical team and business stakeholders.
Mission-critical point settlement system - zero margin for error
Mission-critical point settlement system - zero margin for error
The MOŚC microservice handled recurring point allocation, settlement, and reset processes for both companies and individual employees. Since the entire cafeteria platform relied on this logic, any error in rounding, cycle resets, or limit handling could result in real financial losses for employers and employees, making absolute accuracy essential.
Cinema migration
Cinema migration
External module integration, geolocation and a unified user journey. Cinema ticket purchases were previously handled through an external module. The goal of the migration was to fully integrate this functionality into the cafeteria platform and standardize it across both business logic and user experience. This required designing a new data structure, integrating geolocation capabilities, and aligning the purchasing flow with the standards used throughout the rest of the platform.
Administrative panel for managing benefits across employee groups and departments
Administrative panel for managing benefits across employee groups and departments
Assigning benefits to employee groups required not only backend business logic but also clear and intuitive data presentation for administrators. This involved separating the read and write stacks and optimizing queries for specific administrative views.
Key functional and non-functional requirements
Functional
- Cafeteria module reactivation: restoring a fully operational system state, supporting new requirements, implementing business logic, testing, and user training.
- MOŚC Microservice: support for recurring cycles, subscriptions, and payment processing within the Sports Cafeteria Module.
- Cinema Migration: redesigning the data structure, integrating geolocation services, and standardizing the purchasing journey across both business logic and user interface.
- Subscription Module: mapping benefits across employee groups, providing graphical visualization for administrators, and optimizing frontend queries.
Non-Functional
- Point Settlement Reliability: cycle and reset logic had to operate deterministically, with no room for edge-case failures.
- API-Level Testability: every critical endpoint was continuously validated through automated testing throughout the project lifecycle.
- Separation of Responsibilities: a clear distinction between read and write stacks within the subscription module.
Through the solution
Through the solution
Cafeteria module - reactivation
The team took over the project in a dormant state and carried out its full reactivation, including system restoration, requirements analysis, business logic design, implementation, and testing. Automated tests were executed throughout the entire process, and the project concluded with training sessions for key client-side users.
MOŚC - sports subscription microservice
A dedicated microservice was developed to handle recurring subscription payments within the Sports Cafeteria Module. Built on Axon Framework, the solution ensured scalability and data consistency, while automated API tests validated point allocation, reset processes, and edge-case handling.
Cinema migration
A new data structure was designed, geolocation services were integrated, and the cinema ticket purchasing journey was standardized across the platform. The work covered both backend (Java/Spring, data migration) and frontend (ReactJS/AngularJS) development, while end-to-end tests verified cinema listings and the completeness of the purchasing flow.
Subscription module - benefit mapping
A benefit mapping module was implemented to assign benefits to employee groups and provide administrators with a clear graphical overview. The backend was designed with separate read and write stacks, while the frontend focused on efficient data presentation and query optimization for specific administrative views.
To the success
Technological outcomes
A fully reactivated and operational cafeteria module for a key platform client, ready for future development.
An event-driven MOŚC microservice, built on Axon Framework, successfully deployed to support recurring subscription payments.
A migrated and standardized cinema ticket purchasing journey with integrated geolocation support.
A subscription module with separated read and write stacks, designed to support multiple employee groups at scale.
Pokrycie kluczowych endpointów testami automatycznymi REST API przez cały czas trwania projektu
Project team
Kamil
Senior QA Engineer
Tech stack
Java
Kotlin
Spring
Groovy
Hibernate
Tomcat
ReactJS
AngularJS
JavaScript
Selenium
Docker
Your success is our success
See how we can build a technological advantage for your company together.
We have a team that truly knows its stuff — we'll help you find a solution that works.
Conclusions & recommendations
Reactivation requires more than good code
Restoring a dormant project requires rebuilding the business context and understanding the intent behind the original requirements, not just reviving the codebase. Close collaboration with the Product Owner from day one is essential to ensure the project remains sustainable and does not become dormant again.
Critical business logic requires API-level testing
In a system where point calculation errors can result in real financial losses, unit tests alone are not sufficient. Validating edge cases such as rounding, limits, and reset scenarios directly through REST API endpoints, alongside implementation, proved to be the most effective safeguard.
Migration is an opportunity for architectural improvement
The cinema migration was more than a simple data transfer. Standardizing the purchasing journey and introducing geolocation improved the quality and consistency of the entire platform, not just the migrated module.
Read/Write stack separation as a foundation for scalability
In the subscription module, a clear separation between read and write responsibilities reduced system complexity and enabled independent frontend optimization without risking regressions in the core business logic.
