Case study
Suitsupply
Demandware modernization and a React/Redux customer-account experience connected to SFCC through OCAPI.
My role: SFCC developer · Westum
suitsupply.comThe challenge
An established commerce platform has to evolve while customers continue using it. At Suitsupply, the work included modernizing legacy Demandware functionality and building an API-connected customer-account experience.
My role
I worked on Suitsupply through Westum, contributing storefront modernization, customer-account development, and coordinated release delivery.
Modernizing the application
I migrated pipeline-based Demandware functionality to JavaScript Controllers and contemporary SFCC extension patterns. This moved application behavior into code that could be developed and maintained alongside the wider storefront.
A React customer-account experience
I built a React/Redux My Account frontend powered by OCAPI. It covered authentication, customer details, addresses, preferences, and order-management functionality.
This connected an interactive frontend to SFCC customer and order data, with account behavior spanning both the interface and commerce APIs.
Working across delivery teams
I contributed to a release-train model that allowed multiple squads to deliver commerce changes through coordinated increments. That work complemented implementation by addressing how parallel changes reached the storefront.
What the work enabled
- Customer-account functionality delivered through a React/Redux interface and SFCC APIs.
- Legacy pipeline behavior migrated to JavaScript Controllers.
- Coordinated delivery of changes from multiple squads.
The project connects two recurring parts of my work: improving existing commerce code and building customer experiences around platform APIs.
Next step
Have a similar problem?
If your team needs similar SFCC experience, let’s discuss a contract engagement.
