Designing the B2B client cabinet for a parcel delivery platform at scale

Ozon Rocket was a startup running inside Russia's largest e-commerce infrastructure. The product served B2B clients — businesses shipping parcels through Ozon's 19,000+ pickup point network processing roughly 2M parcels per day. As the sole designer, I owned the interfaces across the full application: client cabinet, administration panel, and the public website.

The team structure was a startup-within-enterprise model — two PMs, six engineers, two BAs — which meant high autonomy but real pressure to move fast and stay aligned with Ozon's wider design system rollout happening in parallel.

• Designed two core modules from scratch: the B2B client cabinet and the online registration flow — both shipped to production.
• Proposed and documented a Figma + Confluence workflow for design review and developer handoff — reduced back-and-forth and sped up the release cycle.
• Implemented Ozon's unified design system as part of a company-wide initiative across all internal products.
• Participated in two major cross-team UX research studies; conducted weekly user interviews and collected feedback before major releases.
• Led UX role in the full website redesign — ran moderated usability testing, reviewed layouts from the UI team, and conducted design QA on every frontend ticket before release.
• Built an administration panel for managing user accounts in close collaboration with backend developers.

Ozon Rocket initiated a website redesign to become the leading logistics operator in Russia. Less than 3% of users completed registration on the site, and the support center was overloaded with requests — both symptoms of a site that failed to communicate value or guide users to action.

• Less than 3% of users completed registration on the website.
• The support center experienced a high volume of avoidable requests.

• Understand how the target audience perceived the landing page.
• Identify what users noticed first and what they missed entirely.
• Determine whether there was enough information to make a decision to sign up.
• Evaluate how convenient it was to search for key information like pricing and integration.

User research. I conducted interviews with 7 potential users. The key insight: easy API and CMS integration was the primary criterion for switching to a new logistics service — and its absence was also the main blocker for moving forward. This directly shaped the decision to add a dedicated integration instructions page.

Prototype. After identifying the issues, I created wireframes and shared them across Product, Marketing, Engineering, and with users. Wireframing let the team align on structure and flow before investing in high-fidelity work — and surfaced several layout assumptions that turned out to be wrong early, not late.

Validating the designs. As part of the UX team, I ran moderated usability testing sessions with primary users. Participants navigated the prototype while I observed. The sessions confirmed that navigation had become clearer and users could find pricing and integration information without resorting to support.

Finishing layouts. I reviewed high-fidelity layouts from the UI team against user goals and provided structured feedback. Working with the frontend team, I specified interactions not captured in static mockups. I then ran a UX review on every implemented ticket before it went live — a step that caught real discrepancies that would have shipped otherwise.