All work
Personal projectB2B SaaS2025

IMS · Inventory Management.

IMS is a partner-store inventory dashboard concept — designed for general store owners who need to see stock health, manage products, and act on them without an analyst’s mindset. Built around one principle: the most important state should be visible before any interaction.

Role
Product Designer · self-initiated
Duration
Concept project
Team
Solo
Platform
Web · partner-store dashboard
ims · screens
01Inventory overview

A four-card snapshot — total · in stock · low stock · out of stock — answers ‘how’s the shop today?’ before any clicking.

02Single canonical table

Brand · Quantity · Status · Selling Price · MRP · Actions — one table, soft status pills, generous spacing.

03Sort by category

Personal Care, Snacks, Beverages, Dairy — a single dropdown narrows the table without any extra navigation.

04Per-row actions

Update Quantity and View Details live where the data lives — no detours into separate edit screens.

05Sort by status

All status · In stock · Low stock · Out of stock — the urgent rows are one click away.

Project Overview

The context.

  • 01

    Partner stores often track inventory across paper notebooks, WhatsApp and spreadsheets — making stock health invisible until a customer asks for a missing item.

  • 02

    Owners need to evaluate stock state, search by product, filter by category and status, and act on individual rows — without context-switching.

Design goals

What we set out to achieve.

01

Stock-state at a glance

Surface total · in stock · low stock · out of stock as the first thing any owner sees on opening the dashboard.

02

Find anything in seconds

Search and three independent sort axes (category, status, brand) work together so the right row is one click away.

03

Act, don’t navigate

Per-row actions like Update Quantity and View Details live where the data lives — no detours into separate edit screens.

04

Friendly density

The grid stays calm even with dozens of rows — generous spacing, soft status pills, and a palette that telegraphs urgency without alarm.

Process

How I worked through it.

01

Mapped the operator’s day

Designed for a busy store owner — not a back-office operator. The dashboard had to win in 6 seconds before they got pulled away by a customer.

02

Designed the four-card snapshot

Total products · In Stock · Low Stock · Out of Stock as a first-row summary — colour-coded so the urgent number is also the most visible.

03

Built one canonical table

Product name, SKU, brand, quantity, status, selling price, MRP, actions — every column earns its place. No tabs, no sub-views — one table, sortable on the columns that matter.

04

Surfaced actions where the data lives

An overflow menu per row keeps the table calm but makes Update Quantity and View Details a single click away — no modal-stacks to recover from.

Outcome

The outcome.

A clean, scannable inventory dashboard that any store owner can navigate without training — stock states, search, multi-axis sorting and per-row actions in one screen.

01
Stock-state snapshot above the fold
02
Multi-axis sorting (category · status · brand)
03
Per-row Update / View actions
04
Owner-first, training-free UI
Learnings

What I’d carry into the next one.

  • Operators don’t read tables — they scan for the colour they’re worried about. Design for the scan, not for completeness.

  • Defaults beat configurability for non-technical users. The dashboard should already be sorted the way they’d have sorted it.

  • A single, canonical table almost always beats three small ones — context-switching is the real cost.