Redesign of the Exmail personal account

Exmail is a logistics company with its own personal account for private and corporate clients.
The product is about 10 years old at the time of the redesign launch.

The personal account was used at the same time:

• B2C clients
• B2B companies
• operators
• users with different roles and access levels

The system worked stably, but:

• the interface is outdated
• Navigation has become overloaded
• complex tables and filters made the job more difficult.
• new users took a long time to adapt
• the product did not visually match the current market level

At the same time, the backend was:

• built on the old architecture
• without documentation
• with a lot of legacy logic

The goal is to completely redesign the UX/UI of the personal account and integrate the new interface into the existing backend system without rewriting it.

This was not a «cosmetic update», but a complete redesign of the interface logic.

• complete redesign of your personal account
• about 30 screens
• desktop + mobile version
• multiple user roles
• differentiation of access rights
• complex tables with filters
• mass actions
• working with financial data
• statuses, calculations, logic of shipments

Main objectives:

• prepare the product for scaling
• update the visual image of the system
• simplify the perception of complex logic
• reduce cognitive load
• make the product understandable without learning

There are no before/after metrics, but the difference in convenience and readability became apparent already at the testing stage.

Audit. Since no UX research was conducted, the work began with a deep revision of the current interface.:

• analyzing user scenarios
• identification of overload points
• analyzing the logic of roles and rights
• parsing tables and filtering
• navigation map

The main problem is not the visual, but the architecture of the interaction.

UX design. What have we done:

• redesigned the information architecture
• simplified the menu structure
• we have built a hierarchy of data
• redesigned the logic of the tables
• redesigned scenarios of mass actions
• we have brought the interface to uniform patterns

The key principle is that the user must understand the system without instructions.

UI design. A new visual layer has been created:

• modern typography
• a clear hierarchy of accents
• system color model
• unified states of elements (hover / active / disabled)
• visual separation of roles and statuses

The interface has become calm, structured and predictable.

Frontend is implemented in vanilla JavaScript.

The backend has not been corresponded with.
The new interface has been integrated into the existing system.

The main difficulties:

• lack of documentation
• outdated architecture
• unstable logic of the old API
• the need to preserve all business logic
• inability to stop the service

The work was carried out carefully — without changing the server side, only integration.

Tables. There were many in the system:

• complex filters
• sorts
• mass actions
• statuses
• financial calculations

It was necessary to simplify the interface without simplifying the logic itself.

Integration with the old API. Due to lack of documentation:

• some of the logic had to be restored by code
• the behavior of some methods was unpredictable
• testing of each scenario was required

Agreement. The redesign affected a key customer experience tool.
Any change required careful coordination and argumentation.

Before:

• overloaded navigation
• low data readability
• Visual chaos
• high entry threshold

After:

• logical structure
• predictable interface behavior
• simplified scenarios
• clear statuses and actions
• modern visual language

The project has become an example of how a 10-year-old system can be upgraded without radically redesigning the architecture.

• the UX/UI of your personal account has been completely updated
• About 30 screens have been redesigned
• implemented an adaptive version
• integration into legacy-backend without rewriting it
• the product is ready to scale

It’s not just a redesign.

This:

• reworking the logic of a complex B2B/B2C tool
• interface modernization under legacy conditions
• working with roles, rights, and complex tables
• integration of the new frontend into the old architecture

We haven’t rewrote the system. We’ve made it clear.