Inventra
Inventra
Inventra
Inventra
Inventry Management App
Inventry Management App
Inventry Management App
Inventry Management App
The Brief
The Brief
Retail operations don't stay simple as they scale.
Retail operations don't stay simple as they scale.
Urban Rain, an Australian retail brand, needed a centralized platform to manage inventory, employees, and stores across multiple locations. As a brand grows past one or two stores, the tools that worked for a single location stop working — and the business needed one connected system rather than a patchwork of spreadsheets and manual processes.
The project came in as a requirements-driven brief via Jira. My job was to take those business requirements, understand them in the context of Australian retail operations, and translate them into a product architecture that could actually hold up across three very different user roles: Admins, Managers, and Employees.
Urban Rain, an Australian retail brand, needed a centralized platform to manage inventory, employees, and stores across multiple locations. As a brand grows past one or two stores, the tools that worked for a single location stop working — and the business needed one connected system rather than a patchwork of spreadsheets and manual processes.
The project came in as a requirements-driven brief via Jira. My job was to take those business requirements, understand them in the context of Australian retail operations, and translate them into a product architecture that could actually hold up across three very different user roles: Admins, Managers, and Employees.
Key Decisions
Key Decisions
Key Decisions
Key Decisions
Points as feedback, not a separate program. Every product tag (Organic, Recycled, Tencel) carries a points value shown at the point of decision, not after checkout.
A tiered journey, not a flat leaderboard. Seed → Sprout → Forest gives points a sense of progression, similar to how streaks work in habit apps.
Impact made tangible. CO2 saved and trees planted are shown in real units at checkout, not abstract scores — so the reward feels connected to something real.
Points as feedback, not a separate program. Every product tag (Organic, Recycled, Tencel) carries a points value shown at the point of decision, not after checkout.
A tiered journey, not a flat leaderboard. Seed → Sprout → Forest gives points a sense of progression, similar to how streaks work in habit apps.
Impact made tangible. CO2 saved and trees planted are shown in real units at checkout, not abstract scores — so the reward feels connected to something real.
The Approach
The Approach
I designed around roles, not one universal screen.
I designed around roles, not one universal screen.
I designed around roles, not one universal screen.
Once I understood the requirements, I researched inventory management patterns and mapped them against how Urban Rain's organization actually worked — one brand, many stores, three tiers of responsibility. That mapping shaped the product strategy:
Once I understood the requirements, I researched inventory management patterns and mapped them against how Urban Rain's organization actually worked — one brand, many stores, three tiers of responsibility. That mapping shaped the product strategy:
Centralized visibility, independent store management — a role-based hierarchy with both organization-wide and store-level access.
Distinct needs per role — dedicated experiences for Admins, Managers, and Employees instead of one generic view.
Store-first inventory — the same product exists across multiple locations, so inventory is organized around individual stores rather than a single global catalogue.
Shop-floor speed — employees need to complete tasks fast on the floor, so the interface prioritizes quick actions and glanceable information over dense data.
Built to scale — a modular architecture using reusable patterns, so the system can grow as the business adds stores.
01
Admin
a national view across all stores, inventory, and employees, built for strategic oversight and system-wide control.
02
Manager
visibility into one or several assigned stores, with tools for inventory management, team oversight, and performance tracking.
03
Employee
a single-store view focused on stock updates, sales entries, and request actions, stripped down for speed and clarity above everything else.
Visual Direction
Visual Direction
Something made for all age groups
Something made for all age groups
Something made for all age groups
Inventra needed to feel like an operational tool — something a store employee could glance at mid-shift and a regional admin could rely on for reporting, without either one feeling like a compromise. The system was built component-first: reusable cards, list patterns, and quick-action modules that could be recombined across all three role experiences rather than designed as one-off screens per role.
Inventra needed to feel like an operational tool — something a store employee could glance at mid-shift and a regional admin could rely on for reporting, without either one feeling like a compromise. The system was built component-first: reusable cards, list patterns, and quick-action modules that could be recombined across all three role experiences rather than designed as one-off screens per role.
Key Flows
Key Flows
Role Based Dashboards
Role Based Dashboards
Role Based Dashboards
Each role — Admin, Manager, Employee — opens into a dashboard scoped to what they're responsible for: national data, assigned stores, or a single store's daily operations.
Each role — Admin, Manager, Employee — opens into a dashboard scoped to what they're responsible for: national data, assigned stores, or a single store's daily operations.
Key Features
Key Features
Key Features
The core feature set covers inventory tracking, employee management, and store-level operations, surfaced differently depending on the role viewing them — from national-level reporting down to single-store quick actions.
The core feature set covers inventory tracking, employee management, and store-level operations, surfaced differently depending on the role viewing them — from national-level reporting down to single-store quick actions.
What I learned
Scalability has to be designed in from day one, not bolted on later.
Scalability has to be designed in from day one, not bolted on later.
The platform was built to grow with the business, through a flexible role hierarchy, expandable product categories, multi-store support, reusable components, and consistent interaction patterns across every screen. Working from a requirements-driven brief taught me a different kind of design discipline than a self-directed concept does — translating business requirements and Jira tickets into a coherent, scalable product architecture meant constantly checking that decisions made for one role wouldn't create friction for another.
Designing for three distinct roles inside one system also reinforced that "simple" isn't one thing — it's different for an admin scanning national data than it is for an employee mid-shift on the store floor.
The platform was built to grow with the business, through a flexible role hierarchy, expandable product categories, multi-store support, reusable components, and consistent interaction patterns across every screen. Working from a requirements-driven brief taught me a different kind of design discipline than a self-directed concept does — translating business requirements and Jira tickets into a coherent, scalable product architecture meant constantly checking that decisions made for one role wouldn't create friction for another.
Designing for three distinct roles inside one system also reinforced that "simple" isn't one thing — it's different for an admin scanning national data than it is for an employee mid-shift on the store floor.
lets
design
something meaningful…
lets
design
something meaningful…
© 2026 All Rights Reserved
PARVVV
lets
design
something meaningful…
© 2026 All Rights Reserved
PARVVV
lets
design
something meaningful…