EasySauda
EasySauda
Designed a B2B distribution platform from scratch —
18 desktop + 14 mobile modules, 150+ screens, 3 user roles,
shipped to dev in 4 months.
Role: UX/UI Designer
Product type: B2B distribution platform
Platform: Desktop + mobile
Country: Kazakhstan
Year: June-Sep, 2025
All interface screenshots have been translated from Russian
(the original product language) into English for portfolio purposes.
Context & My Role
EasySauda is a B2B platform that automates the distribution chain between suppliers and retail outlets. Distributors manage orders, client bases, and analytics through
a desktop interface. Retail outlets — stores and kiosks — browse supplier catalogs, place orders, and manage returns through a mobile app that functions as a marketplace. The administrator configures the system, managing users, roles,
and access. Three user roles, two platforms, one ecosystem.
I joined the project with a finished logo, a defined color palette, and rough draft mockups of the first four modules already in place. My role was to bring structure
to what existed, design the remaining modules from scratch, and deliver everything
to developers in production-ready condition.
EasySauda is a B2B platform that automates the distribution chain between suppliers and retail outlets. Distributors manage orders, client bases, and analytics through
a desktop interface. Retail outlets — stores and kiosks — browse supplier catalogs, place orders, and manage returns through a mobile app that functions as a marketplace. The administrator configures the system, managing users, roles,
and access. Three user roles, two platforms, one ecosystem.
I joined the project with a finished logo, a defined color palette, and rough draft mockups of the first four modules already in place. My role was to bring structure
to what existed, design the remaining modules from scratch, and deliver everything
to developers in production-ready condition.
In total: 18 desktop modules + 14 mobile modules, 150+ screens.
I worked as the sole designer within the client's cross-functional team:
project manager, business analyst, and developer.
In total: 18 desktop modules + 14 mobile modules,
150+ screens.
I worked as the sole designer within the client's cross-functional team:
project manager, business analyst, and developer.
The challange
No system
The existing draft mockups had no shared component logic — inconsistent spacing, button states, and table patterns across screens. Before moving forward, a unified system had to be established.
The existing draft mockups had no shared component logic — inconsistent spacing, button states, and table patterns across screens. Before moving forward, a unified system had to be established.
Tight timeline
Each completed module shipped directly to development — an iterative process with no room to pause and revisit. Spending weeks building a custom UI kit from scratch wasn't an option.
Each completed module shipped directly to development — an iterative process with no room to pause and revisit. Spending weeks building a custom UI kit from scratch wasn't an option.
Different audiences.
The distributor works with dense tables and analytics at a desktop. The retail outlet manager places orders from a phone, often on the go. A single UX approach didn't serve both.
Before each module
I studied how similar functions worked in the old system —
to understand user expectations.
My approach
Buy a UI kit, don't build one.
I proposed purchasing a ready-made Figma library based on it and adapting it
to the project's visual identity — color tokens, typography, and key components.
This saved approximately 2–3 weeks of UI Kit construction time and gave us a shared component vocabulary with developers from day one — eliminating the 'design says one thing, dev builds another' problem.
I proposed purchasing a ready-made Figma library based on it and adapting it
to the project's visual identity — color tokens, typography, and key components.
This saved approximately 2–3 weeks of UI Kit construction time and gave us a shared component vocabulary with developers from day one — eliminating the 'design says one thing, dev builds another' problem.
Module-by-module iterations.
One module at a time — from concept to final screens — was handed off to development before the next one began. All revisions were tracked in Google Docs per iteration. This eliminated the "which version is final?" question and kept the whole team aligned.
One module at a time — from concept to final screens — was handed off to development before the next one began. All revisions were tracked in Google Docs per iteration. This eliminated the "which version is final?" question and kept the whole team aligned.
Process: Five Key Modules
Order management (desktop)
The core module for the distributor — the full flow of incoming orders from retail outlets: statuses, details, change history, and internal communication.
The analyst's original proposal was a kanban board only. I suggested adding a table view alongside it, because distributors work with high order volumes and need to scan, filter, and sort data quickly. Kanban works well for tracking progress; a table works better for managing a stream of data. Both views were implemented with a toggle between them.
The order detail card opens without leaving the list — the distributor keeps context and can move between orders without losing their place.
SIC (Social Identification Card) is a citizen's record in the system, linked to their national ID (IIN). The module covers the full lifecycle: registration, editing, deregistration upon death, emigration abroad, ID deletion, and ID restoration.
I structured the module around IIN search as the entry point — one field, one click, and the operator sees the full citizen profile with all available actions. Destructive operations (death registration, deletion) require a separate confirmation step with an explicit description of consequences.
Analytics (desktop)
The dashboard gives the distributor answers to key business questions in under 30 seconds: client base size, fulfilled orders, average order value, sales dynamics, and top performers by product, category, and client. Every block is clickable and leads to a detail page with filters by period, client type, category, and individual buyer.
The main design challenge was balancing density with readability — not a dashboard for its own sake, but a screen with a clear data hierarchy that earns its space.
A module for tracking all system changes — who changed what and when. Audit is a control and investigation tool, not a daily working screen.
I focused on a filter system: by date, user, event type, and object.
The results table was built on "most important visible immediately" — date, action, executor — without opening each record. Details expand on click.
Role management (desktop)
The distributor creates team members with different access levels — a sales manager sees one set of features, a warehouse staff member sees another, an admin sees everything.
The employee list shows status (active / inactive), role, and contact details. The permissions matrix is a table where rows are system sections and columns are roles. Together, the two screens allow managing both people and access rights without unnecessary navigation back and forth.
The distributor creates team members with different access levels — a sales manager sees one set of features, a warehouse staff member sees another, an admin sees everything.
The employee list shows status (active / inactive), role, and contact details. The permissions matrix is a table where rows are system sections and columns are roles. Together, the two screens allow managing both people and access rights without unnecessary navigation back and forth.
Catalog and marketplace (mobile)
The mobile app for retail outlets works as a marketplace: the catalog is organized by category, supplier, and brand. Users can search for specific products, filter by supplier, price, and rating, and compare terms from multiple suppliers directly on the product card.
The product card surfaces offers from several suppliers at once — with delivery terms, ratings, and reviews — so the retail manager can make a decision without extra calls or tab-switching.
The mobile app for retail outlets works as a marketplace: the catalog is organized by category, supplier, and brand. Users can search for specific products, filter by supplier, price, and rating, and compare terms from multiple suppliers directly on the product card.
The product card surfaces offers from several suppliers at once — with delivery terms, ratings, and reviews — so the retail manager can make a decision without extra calls or tab-switching.
Cart and checkout (mobile)
The final step in the retail outlet's user journey. I designed all the states the screen realistically encounters in use: a cart meeting the minimum order, a cart with a minimum order warning, a checkout screen where delivery date and payment method can be changed inline via a bottom sheet — without leaving the page.
The confirmation screen shows the full order summary. The "Thank you" screen invites the user to rate the checkout experience — not just a flow endpoint, but a built-in feedback moment.
The final step in the retail outlet's user journey. I designed all the states the screen realistically encounters in use: a cart meeting the minimum order, a cart with a minimum order warning, a checkout screen where delivery date and payment method can be changed inline via a bottom sheet — without leaving the page.
The confirmation screen shows the full order summary. The "Thank you" screen invites the user to rate the checkout experience — not just a flow endpoint, but a built-in feedback moment.
Results and Reflection
What shipped: 18 desktop modules + 14 mobile modules across 3 user roles (distributor, retail outlet, administrator). 150+ screens. Full design system adapted from a commercial Figma library.
Who it serves: B2B distributors and retail outlet managers — daily operational users who need speed, not beauty.
Observed impact: Platform entered final launch phase. Development team reported no major design revision requests during build — a direct result
of the module-by-module delivery approach.
What I'd do differently: Introduce a shared changelog inside Figma earlier.
We used Google Docs for tracking, which created friction during review cycles — a lesson I'd apply immediately on the next project.
What shipped: 18 desktop modules + 14 mobile modules across 3 user roles (distributor, retail outlet, administrator). 150+ screens. Full design system adapted from a commercial Figma library.
Who it serves: B2B distributors and retail outlet managers — daily operational users who need speed, not beauty.
Observed impact: Platform entered final launch phase. Development team reported no major design revision requests during build — a direct result
of the module-by-module delivery approach.
What I'd do differently: Introduce a shared changelog inside Figma earlier.
We used Google Docs for tracking, which created friction during review cycles — a lesson I'd apply immediately on the next project.
