Vendor Portal
Revamp:
ShipGlobal

Transforming a complex vendor portal into an intuitive, efficient, and delightful experience.

Vendor Portal Dashboard

Impact of Revamp

40%

Faster Page
Load Time

74%

Increase in Repeat
Order

12%

Growth in Average
Order Value

About ShipGlobal

"ShipGlobal.in is India's leading cross-border logistics platform, specializing in simplified international shipping for businesses, especially e-commerce sellers, and even individuals. We help them send parcels, documents, and goods from India to over 220 countries worldwide with ease and reliability."

About ShipGlobal Vendor Portal

Vendor Portal Dashboard
Vendor Portal Orders

ShipGlobal Vendor Portal used by 20k+ vendors/exporters or shipping partners to ship their goods/products internationally.

Vendors use this portal to manage their orders efficiently.

Vendors performs verity of task by using this platform like, order creation, pickup scheduling, invoice creation, shipment tracking etc.

More than 600 vendors use this portal on daily basis

More than 45k+ Monthly Shipment Transactions is done by vendors by using this platform

The Problem

The Challenge

Through user interviews, analytics deep-dives, and stakeholder sessions, I identified that the existing vendor portal—though functional—was creating friction in vendor workflows. Data showed high support ticket volumes and low mobile adoption, indicating systemic usability issues affecting business metrics.

Key Pain Points

Confusing Order Status

Vendors struggled to understand order statuses and track shipments effectively

Poor Information Architecture

Critical information was buried, making it difficult to find what they needed quickly

Frustrating UX

Overall user experience caused frustration and reduced vendor satisfaction

Complex Workflows

Too many steps required to complete common tasks, reducing efficiency

Old Interface - Before
Old Interface
Pain Point Analysis
Problem Analysis

Objective

As Product Manager, I defined a clear product strategy: deliver a vendor portal that reduces operational friction, drives mobile adoption, and improves key business metrics—all while ensuring seamless migration from the legacy system. The goal was to create a platform that vendors would actively choose to use, not just tolerate.

Business Requirements

Improve vendor satisfaction and retention by delivering a more intuitive and efficient platform experience. Reducing support tickets, and streamlining order fulfillment.

Product Requirements

Clean dashboard, a simplified shipment booking flow, real-time tracking, and clear billing and invoicing features.

UX Requirements

A clear navigation structure, consistent UI design, and task-focused workflows. experience had to be accessible, provide real-time feedback.

Task Flow Analysis

Current Single Order Creation Flow . .

The existing navigation structure made it difficult for users to access and compare layered functionalities—such as viewing orders, creating new shipments (CSB-IV or CSB-V), entering item details, and comparing shipping costs across different aggregators—leading to confusion and inefficiency in completing key tasks.

Orders
Add Order
Select address
Shipping Address
Compare Price
Place Order
Task Flow Screen 1
Task Flow Screen 2

Current Pickup Request Flow . .

The existing pickup creation page lacked an intuitive flow, making it difficult for users to seamlessly create a new pickup request or generate a manifest, often resulting in errors and delays.

Pickup Flow Screen 1
Pickup Flow Screen 2

Product Discovery & User Research

Product Discovery Approach

Stakeholder Interviews & User Research

Conducted interviews with 5+ vendors and internal teams (support, ops) to understand workflows, pain points, and business impact. Gathered both qualitative insights and quantitative data.

Data Analysis & Benchmarking

Analyzed product metrics (3.2s page load, 15% mobile usage, high bounce rates), reviewed support ticket trends, and benchmarked against competitor platforms to identify improvement opportunities.

Product Questions Explored

  • Why is mobile adoption only 15% when vendors are often on-the-go?
  • What causes the 3.2s page load time and how does it impact business KPIs?
  • Which features drive repeat usage vs. create support burden?
  • How can we measure success beyond "better UX"?

Key Product Insights

  • Performance bottleneck: 3.2s page load time was causing 23% drop-off in first session, directly impacting vendor activation and retention.
  • Mobile gap: Only 15% mobile usage despite 60% of vendors managing shipments on-the-go, indicating mobile experience was blocking adoption.
  • Information architecture issues: Critical features like tracking and order creation buried 3+ clicks deep, increasing support tickets and reducing engagement.
  • Business impact: Poor UX was directly correlated with lower order frequency, higher support costs, and vendor churn—quantifiable business problems requiring product solutions.

Product Strategy & Problem Framing

Based on research insights and data analysis, I reframed the problem from "vendors don't like the UI" to "product performance and experience gaps are blocking business growth." This shift focused the team on measurable outcomes: faster load times, mobile adoption, and vendor engagement.

Wireframe 1
Wireframe 2
Wireframe 3
Wireframe 4

Product Opportunity Statement

"Deliver a high-performance, mobile-first vendor portal that reduces page load time by 40%, increases mobile usage to 55%, and boosts engagement by 55%—ultimately driving vendor retention and platform growth."

The existing ShipGlobal vendor portal:

  • Overwhelms new users with an unclear, documentation-heavy onboarding process.
  • Lacks streamlined flows for frequent tasks like creating repeat shipments.
  • Has poor information hierarchy, making it hard for vendors to find key actions like tracking

Benchmarking

Delhivery

Delhivery Screenshot 1
Delhivery Screenshot 2
Delhivery Screenshot 3
Delhivery Screenshot 4
Delhivery Screenshot 5

Others

Others Screenshot 1
Others Screenshot 2
Others Screenshot 3
Others Screenshot 4
Others Screenshot 5
Others Screenshot 6

Shiprocket

Shiprocket Screenshot 1
Shiprocket Screenshot 2
Shiprocket Screenshot 3
Shiprocket Screenshot 4
Shiprocket Screenshot 5
Shiprocket Screenshot 6
Shiprocket Screenshot 7
Shiprocket Screenshot 8
Shiprocket Screenshot 9
Shiprocket Screenshot 10

Design Directions

1. Redesign Around Core Workflows

Rebuild the experience by mapping and simplifying the most critical vendor tasks: booking a shipment, tracking parcels, downloading invoices, and resolving issues. Introduce guided, step-by-step flows with clear CTAs.

Design Workflow Iterations

2. Implement a Design Standard

Develop a consistent design language using reusable components and a modern visual hierarchy. This not only solves UI inconsistency but also allows faster scaling, better accessibility, and easier onboarding for new users.

Design Standard Guidelines

Final Designs

Final Designs - Order Listings
Final Designs - Order Management

Final Create order and view order design

Create Order Design
View Order Design
Order Success Design

Project Details

My Role
Senior Developer
Duration
3 Months (Jan - Mar 2025)
Team
1 Designer, 4 Developers, 1 BA
Tools
Figma, Confluence, Jira, GitHub

Impact of the Revamp

Post 6 months launch

Metric Before After Outcome
Page Load Time 3.2 seconds 1.9 seconds (40% faster) React-based architecture with optimized API calls and lazy loading
Mobile Usage 15% of total traffic 55% of total traffic (267% growth) Mobile-first responsive design enabling on-the-go order management
User Engagement Baseline engagement metrics 55% increase Streamlined flows, better information architecture, and intuitive navigation
Support Ticket Volume High (daily vendor complaints) 60% Reduction Improved flow and overall navigation, reduced confusion
Repeat Order Avg. 2.4 per vendor/month 74% Increase Easier re-shipment, clone order creation
Avg. Order Value 700 rs 12% Growth Clear pricing visibility and better shipment tracking

Product Management Learnings

Metrics Define Success

Setting clear, measurable goals (40% faster load, 55% mobile usage) aligned stakeholders and gave the team tangible targets. Without numbers, "better UX" would have been subjective.

Problem Framing > Solution Jumping

Reframing the problem from "bad UI" to "performance blocking growth" helped us focus on business impact, not just aesthetics. Product thinking starts with the right problem statement.

Cross-Functional Collaboration

Working closely with engineering, design, and support teams—plus setting up proper testing infrastructure—was critical. Product managers orchestrate, they don't dictate.

Thank you for viewing!

Lets connect & Discuss