Invent

Invent

Invent

Track

Track

Track

Helping small businesses connect inventory, sales and everyday operations in one system

Helping small businesses connect inventory, sales and everyday operations in one system

InventTrack is a responsive inventory and sales management web application that helps small businesses stay on top of stock, track sales, identify what needs attention, and understand how their business is performing.

InventTrack inventory and sales dashboard

ROLE

Product Designer & Developer

PLATFORM

Responsive Web Application

Mobile & Desktop

VALIDATION

Tested with 2 retail businesses

Pharmacy & Supermarket

EARLY ADOPTION

~6 business owners

Currently using InventTrack

Scope

Product Discovery · UX Strategy · Information Architecture · UI Design · Prototyping · Database Design · AI-Assisted Development · Product Evaluation

Status

Working Product · Early Business Usage

Project Overview

Inventory was only one part of the problem

Managing inventory isn’t just about knowing what’s on the shelf. Every sale affects stock availability, replenishment depends on supplier information, and daily transactions contribute to understanding business performance. For small retail businesses, these activities are connected, but managing them through separate records makes everyday decisions harder.

I owned InventTrack end-to-end, from understanding the operational problem and defining the product strategy to information architecture, UX/UI design, backend architecture, AI-assisted development, and real-world evaluation. The challenge was to translate these interconnected business activities into one accessible, responsive system that simplifies daily operations without introducing unnecessary complexity.

The Problem

Small businesses need more than a record of what’s on the shelf

For small retail businesses, keeping track of inventory is only one part of managing daily operations. Business owners also need to know what has been sold, which products are running low, when to restock, and whether the business is making a profit.

When stock, sales, supplier information, and financial records are managed separately, answering these questions becomes unnecessarily difficult.

A sale recorded without an accompanying stock update can leave inventory records inaccurate. Without clear reorder signals, products requiring attention can be overlooked. And when sales figures require manual calculations, understanding business performance takes additional effort.

The opportunity was not simply to digitise stock records. It was to connect the activities behind everyday retail operations so business owners could spend less time reconciling information and make better-informed decisions.

The design challenge

How might I help small retail businesses manage inventory, sales, and related operations through one connected system without introducing unnecessary complexity?

Discovery & Research

Understanding the operational decisions behind inventory management

I approached discovery by looking beyond how small retail businesses record stock to understand the activities, responsibilities and decisions connected to inventory management.

Managing inventory involves more than maintaining a list of products. Every sale changes stock availability, replenishment requires supplier information, and daily transactions contribute to understanding business performance. When employees are involved, access to information and operational responsibilities also become part of the process.

My goal was to understand these relationships, identify where disconnected workflows could create friction, and determine what a more connected experience needed to support.

Exploring the Operational Workflows

I examined the dependencies between six areas of everyday retail operations: inventory, sales, replenishment, suppliers, reporting and staff access.

Rather than starting with a predetermined feature list, I worked through the questions that would shape the product’s behaviour and information architecture.

• Stock visibility: What information helps a business owner understand available inventory and identify products requiring attention?

• Sales and inventory: What should happen to stock records when an employee records a transaction?

• Replenishment: How can a business identify when stock is approaching a level that requires action?

• Supplier relationships: What information is needed to move from identifying low stock to arranging replenishment?

• Business performance: How can recorded sales and product information contribute to understanding revenue, costs and profitability?

• User responsibilities: Which activities require owner-level oversight, and which should employees be able to perform independently?

Working through these questions exposed an important distinction: the challenge wasn’t simply making individual records easier to manage. It was understanding what needed to happen between them.

For instance, a sale affects both transaction history and available inventory. A low-stock condition creates a potential replenishment decision. And when multiple people use the application, their responsibilities affect what information and actions should be accessible.

These dependencies became the basis for evaluating the product’s structure, workflows and technical requirements.

Supporting the Product Direction with Secondary Research

To examine the broader relevance of structured record-keeping, I also reviewed published research on small-business practices in Nigeria.

The Small Firm Diaries Nigeria study, published in 2023, reported that 26% of the 161 firms in its Nigerian sample used stock-control record-keeping practices.

The study examined small firms in manufacturing, agricultural processing and services across Lagos, Enugu and Kaduna. Retail businesses were not included in the sample, so the finding cannot be treated as a direct measure of record-keeping practices among InventTrack’s target users.

Nevertheless, it provided useful context about the adoption of structured business practices among small Nigerian enterprises.

The finding reinforced the relevance of investigating how digital tools could make operational records more accessible and useful. It also raised a broader product consideration: providing a place to enter information is not necessarily enough. The experience needs to make that information valuable to the business.

This secondary research served as supporting context for the case study, rather than evidence collected from InventTrack users during its initial development.

Research source: Small Firm Diaries Nigeria: Country Data Overview (2023), Section 7, Business Practices, p. 61. National Bureau of Statistics / Financial Access Initiative.

Identifying the Key Operational Patterns

My workflow analysis pointed to four interconnected considerations.

01. Sales and inventory should operate as one workflow

Recording a sale and adjusting the corresponding stock quantity are related activities. Requiring users to complete them separately introduces repetitive work and increases the possibility of inconsistent records.

02. Inventory visibility should support decisions

Knowing how many units remain is useful, but the business also needs to recognise when that quantity requires attention. The challenge was to make stock information actionable without introducing unnecessary complexity.

03. Supplier information should support replenishment

Identifying a product that needs restocking is only part of the task. The information required to contact its supplier should be accessible when the business needs to act.

04. Access should reflect operational responsibility

Business owners require broader visibility and administrative control, while staff need access appropriate to their daily tasks. The application therefore needed to account for different responsibilities within the same business.

These were not four unrelated feature opportunities. They pointed toward a common need: a system where everyday business activities remain connected and information serves more than one purpose.

The discovery process helped me reframe InventTrack’s initial direction.

Instead of approaching the product as a digital inventory register with additional features, I saw an opportunity to design an operational system around the relationships between business activities.

The product needed to reduce repetitive record-keeping, make important information easier to find and interpret, and support decisions across inventory, sales, replenishment and business performance.

It also needed to remain approachable for small businesses without the resources or operational complexity of larger organisations.

The Opportunity

The opportunity was to create a responsive, connected business management experience that could support everyday retail operations without making the work itself more complicated.

This direction became the foundation for defining the product’s scope, prioritising its core capabilities and deciding what the first version needed to deliver.

InventTrack Inventory Management Research Infographic

Product Strategy & Scope

Designing the Smallest Complete Operational System

The discovery process established that InventTrack needed to address more than stock recording. The challenge was deciding which capabilities were essential to supporting everyday business operations and how they should work together.

Inventory management can easily expand into accounting, purchasing, payments, warehouse operations and forecasting. However, introducing a larger feature set wouldn’t necessarily make the first version more useful. I needed to establish a clear product boundary: prioritise the activities small retailers depend on regularly, connect the information behind those activities, and avoid complexity that wasn’t essential to the initial experience.

Defining the Core Product Experience

I organised InventTrack around six connected functional areas, each addressing a specific operational responsibility.

01. Dashboard: Understand the state of the business

The Dashboard provides business owners with an overview of stock availability, sales activity, business performance and items requiring attention. It also offers quick access to frequently performed tasks without requiring users to navigate through several sections.

02. Products: Maintain a reliable inventory record

Products serves as the central source of inventory information, including available quantities, cost and selling prices, reorder thresholds and supplier associations. This information remains connected to sales and restocking activities elsewhere in the application.

03. Sales: Record transactions without duplicating work

Sales recording is connected directly to inventory. Rather than requiring users to record a transaction and manually adjust stock separately, a completed sale updates the corresponding product quantity and contributes to business records.

04. Suppliers: Support replenishment decisions

Supplier management keeps relevant contact information associated with products. This makes supplier details accessible when inventory needs replenishment without expanding the initial scope into automated procurement.

05. Reports: Turn recorded activity into business visibility

Reporting brings together sales, revenue, costs and gross profit, allowing owners to monitor performance without manually compiling figures from disconnected records.

06. Staff: Support shared operational responsibilities

InventTrack accommodates businesses where employees participate in sales and inventory management. I introduced owner and staff access to support daily operations while maintaining the distinction between employee responsibilities and owner-level oversight.

InventTrack product scope connecting dashboard, products, sales, suppliers, reports and staff

Prioritising Connected Workflows Over Feature Volume

These six areas weren’t selected simply to create a comprehensive navigation menu. Their value comes from how they work together. A sale affects inventory, inventory quantities determine low-stock conditions, supplier information supports replenishment, transaction data contributes to reporting, and users interact with these workflows according to their responsibilities.

This shaped a central product decision:

InventTrack would operate as one connected business system rather than a collection of independent features.

It also influenced the technical architecture. Products, transactions, suppliers and users needed database relationships that supported consistent behaviour across the application. Establishing these connections took priority over introducing more advanced capabilities.

Managing the Initial Scope

Building InventTrack independently meant balancing product ambition with implementation complexity. I prioritised a functional system for recording and managing inventory, completing sales, tracking stock changes, accessing supplier information, reviewing business performance and supporting staff access. The experience also needed to work across mobile and desktop through a responsive web application.

Some capabilities remained outside the initial implementation. Product search was not included, although subsequent feedback revealed its importance as product inventories grow. Multi-outlet management was also excluded, since supporting multiple locations introduces additional requirements for outlet-specific inventory, staff assignments, permissions and reporting.

These omissions became opportunities for future development rather than reasons to delay establishing the core operational experience. The priority was to build a reliable foundation that could be evaluated with real businesses and expanded based on their needs.

Establishing the Product Foundation

The result was a clearly defined initial product with connected workflows, role-aware access and responsive interfaces. This provided the foundation for translating the product strategy into information architecture, interface design and technical implementation.

More importantly, it allowed me to evaluate a working application with real businesses and use their feedback to inform subsequent development.

Information Architecture

Organising the Product Around Everyday Business Tasks

With the product scope established, my next challenge was translating six connected operational areas into an application structure that business owners and staff could understand and use efficiently.

I organised InventTrack around the activities users would return to regularly: monitoring business performance, managing products, recording sales, accessing supplier information, reviewing reports and managing staff. Rather than introducing multiple levels of navigation, I prioritised direct access to the core areas of the application.

The primary navigation was structured around Dashboard, Products, Sales, Suppliers, Reports, Staff and Profile, creating a predictable environment where users could identify the relevant area without navigating through unrelated features.

InventTrack application sitemap showing authentication, workspace, primary navigation and task entry points

Connecting Navigation to Business Workflows

A clear navigation structure was only one part of the challenge. The system also needed to support how users move between related activities.

For example, a business owner might notice a low-stock alert on the Dashboard, open the relevant product record to check its quantity and reorder threshold, then use the associated supplier information to plan replenishment.

Similarly, recording a sale should update inventory and contribute to reporting without requiring the user to visit those sections and repeat the same work.

These scenarios informed two complementary decisions: keep navigation straightforward for users while ensuring related business records remain connected behind the interface.

This separation was important. Users needed to understand where to perform a task, but they shouldn’t have to understand the application’s underlying data relationships to complete it.

Mapping the Low-Stock Replenishment Flow

One of the workflows I considered when structuring InventTrack was how a business owner moves from identifying a stock issue to deciding what to do about it.

A low-stock alert is useful only if the owner can find the information needed to act. I mapped the journey from noticing an alert on the Dashboard to reviewing the affected product’s quantity and reorder threshold, then locating the supplier information needed for replenishment.

The flow follows four stages:

Identify low stock → Review inventory → Locate supplier → Plan replenishment

This helped me evaluate whether the application’s navigation supported a complete business task rather than leaving users to piece together information from disconnected sections.

I kept replenishment planning within the scope of the initial product. InventTrack provides stock visibility and supplier information, but it does not currently automate purchase orders or supplier communication.

The design decision was to make the path from identifying a stock issue to taking the next step clear, without introducing purchasing functionality the product wasn’t built to support.

Low-stock replenishment flow from dashboard alert through product review and supplier details to external supplier contact

Designing for Different Access Levels

The application also needed to accommodate two user roles: Business Owner and Staff.

Owners require broader visibility into business performance and administrative controls, including staff management. Staff members need access to permitted operational tasks without automatically receiving the same level of control.

I accounted for these differences when structuring the experience, ensuring that access reflected responsibility while keeping the application’s overall organisation familiar.

This prevented role-based access from becoming a separate, disconnected experience and established a foundation for managing permissions within the product.

InventTrack product user flow showing sign-in, role-based destinations and available tasks for business owners and staff

Keeping the Experience Accessible Across Devices

InventTrack was designed as a responsive web application, so the structure also needed to work across desktop and mobile screens.

The aim was to preserve access to core tasks as the available screen space changed, rather than forcing users to follow different workflows depending on their device.

This meant considering how navigation, operational information and task entry points could remain understandable across screen sizes.

The Design Decision

I chose a relatively shallow, task-oriented structure supported by connected data relationships and role-aware access.

The result was an application where users could locate the functions they needed, move between related activities and complete everyday operations without having to manage the complexity of the system themselves.

The principle was simple: make the product easy to move through, while allowing the underlying system to handle the relationships between business activities.

Designing the Core Workflows

Making Everyday Inventory Operations Work Together

With the product structure established, I focused on translating the core business activities into interactions that were straightforward to complete and consistent across the application.

The challenge was ensuring that users could perform familiar tasks, such as recording a sale, updating stock or reviewing a product, without having to manually reconcile information elsewhere in the system.

I designed these workflows around a central principle: one completed action should update the relevant business records without creating additional work for the user.

Recording a Sale: Connecting Transactions to Inventory

Recording a sale was one of the most important workflows because it directly affects both inventory accuracy and business reporting.

I designed the experience to let users select a product, enter the quantity being sold, review the calculated transaction amount and record the sale. Once the transaction is recorded, InventTrack automatically deducts the quantity sold from the available stock and saves the transaction in sales history.

This removed the need to record the sale in one section and manually update the inventory in another.

The interaction also needed to make essential information accessible during the task. Users should be able to identify the product they are selling, specify the quantity and understand the transaction amount before completing it.

The design decision was to keep sale recording focused on the transaction while allowing the system to handle the connected inventory update.

InventTrack filled Record a Sale form

Managing Products: Balancing Operational Detail with Clarity

The Products area serves as the main inventory record, where users can view and manage the information needed for everyday stock decisions.

Each product includes its name, description, available quantity, cost price, selling price, reorder threshold and associated supplier.

I needed to organise this information so users could scan their inventory while still having access to the details required to manage individual products.

The experience supports adding new products, editing existing records, removing products and exporting inventory information. These operations were designed around the same product structure, helping maintain consistency between the inventory list and individual record-management tasks.

An important consideration was the amount of information presented at once. Product quantities, prices and stock conditions all matter, but giving every field equal visual prominence would make the interface harder to scan.

I therefore prioritised clear product identification, stock visibility and recognisable actions, with supporting information organised around those tasks.

InventTrack inventory products, quantities, prices and reorder thresholds

Designing the Low-Stock System: From Quantity to Actionable Status

A product’s available quantity tells the business what remains, but it doesn’t necessarily indicate whether that quantity requires attention.

I introduced reorder thresholds to help businesses define the stock level at which replenishment should become a priority.

When creating or editing a product, users can specify its reorder threshold. InventTrack compares that value with the available quantity and identifies the product as low stock when the threshold is reached or crossed.

Current stock ≤ Reorder threshold → Low-stock status

I designed the status to appear within the Products area and on the Dashboard, allowing users to recognise products requiring attention without reviewing every inventory record individually.

This was a deliberate trade-off. Instead of introducing inventory forecasting or automated purchasing, I focused on a simple, configurable rule that small businesses could understand and apply to different products.

The result was a stock-management experience that did more than display quantities. It helped users identify when those quantities required action.

InventTrack dashboard with low-stock alert annotation

Designing for Consistent System Feedback

A connected workflow should not leave users uncertain about whether an action has affected the application.

For InventTrack, this meant ensuring that the information presented across different sections reflected the same underlying business activity.

Recording a sale changes the inventory quantity. Adding stock increases the available quantity. Changes in stock can affect low-stock status, while recorded transactions contribute to sales history and reporting.

These relationships informed how I designed the experience: users interact with the relevant task, while the application maintains the connected information needed elsewhere.

This was particularly important because the product was intended to replace fragmented record-keeping, not reproduce it in a digital interface.

The goal was to make operational tasks feel independent enough to complete easily, but connected enough that users wouldn’t need to repeat their work.

Users, Roles & Access Control

Supporting Businesses Operated by More Than One Person

InventTrack needed to work for businesses where owners oversee operations while employees handle everyday activities such as recording sales, managing products and maintaining supplier information.

This introduced an important product-design consideration: different users may work with the same business records without requiring the same level of access or control.

I designed InventTrack around two user roles, Business Owner and Staff, with access reflecting their responsibilities within the business.

Defining Access by Responsibility

Business Owner: Operational Oversight and Administration

The Business Owner has access to the full operational experience, including Dashboard, Products, Sales, Suppliers, Reports, Staff Management and Profile.

Beyond managing everyday activities, owners can review business performance and manage the employees who have access to the application.

Staff: Access to Daily Operational Tasks

Staff members have access to Dashboard, Products, Sales, Suppliers and Profile.

Their experience supports the activities required to run daily operations without exposing owner-level functions such as business reporting and staff administration.

The objective was to maintain a consistent product experience while ensuring that available functions reflected each user’s responsibilities.

Business owner and staff member permissions in InventTrack

Making Staff Management Part of the Owner’s Experience

Rather than requiring employees to manage business-level account administration themselves, I designed staff management as an owner-controlled function.

Business owners can add staff members and provide them with the credentials required to access InventTrack. Once authenticated, employees enter the application through their own staff experience.

This distinction influenced both the interface and the application’s authentication and access structure. It meant considering not only how a staff member enters the system, but also which destinations and actions should be available after login.

Balancing Access, Simplicity and Control

I chose a two-role structure for the initial release instead of introducing multiple permission groups and complex administrative settings.

This provided a manageable foundation for the businesses InventTrack was designed to support while preserving an important separation between everyday operational activities and owner-level oversight.

As the product expands toward multi-outlet management, this structure will need to accommodate additional considerations, including outlet-specific staff assignments and access.

For the initial version, the priority was clear: support collaborative business operations without giving every user unrestricted access to the entire application.

Business Visibility & Reporting

Turning Daily Transactions into Business Insights

Beyond managing stock and recording sales, I wanted InventTrack to help business owners understand how their businesses were performing.

I designed the Dashboard to provide an overview of key operational information, including revenue, inventory value, low-stock alerts and recent sales. The Reports section gives owners a more detailed view of sales and profitability, bringing information generated from everyday transactions into one place.

Rather than requiring owners to calculate figures manually or compare disconnected records, InventTrack uses recorded business activity to provide a clearer picture of performance.

InventTrack dashboard showing stock value, revenue, sales trend and reorder alerts
InventTrack profit report showing revenue, costs, margins and transactions

Visual Language & Interface Design

InventTrack needed to present stock quantities, product records, transactions and financial information without overwhelming users. I established a consistent visual language using a dark interface, clear typography, restrained colour and structured layouts to make operational information easier to scan.

I used Clash Grotesk for prominent headings, Archivo for interface text.

Blue provides emphasis for primary actions, while amber identifies low-stock conditions and green communicates positive states. Consistent tables, cards, forms and navigation patterns help users recognise familiar interactions across the application.

InventTrack typography specimens showing Clash Grotesk headings and Archivo interface text
InventTrack foundation colours, primary actions, stock states and product table patterns
InventTrack desktop and mobile dashboard comparison

Desktop and Mobile Interface Comparison

As a responsive web application, InventTrack also needed to work across desktop and mobile browsers. I adapted layouts and information presentation for different screen sizes while maintaining access to the same core workflows.

From Design to Technical Implementation

I didn’t stop at designing InventTrack. I built the application.

InventTrack was an opportunity to work across product design and implementation.

I wanted to move beyond high-fidelity screens and create a working application where the relationships between inventory, sales, suppliers, reporting and user access actually functioned.

I used an AI-assisted development workflow to translate the designs and product requirements into a responsive web application.

This involved working with interface design, database structure, authentication, connected data, implementation, testing and deployment.

Building the backend with Supabase

I used Supabase to configure the application’s backend, including authentication and the database supporting its operational workflows.

I worked on the database schema and established relationships between the information required by different areas of the product.

Products needed to be associated with relevant supplier records.

Sales needed to reference the products involved in each transaction.

Inventory quantities needed to respond to sales and restocking activity.

And recorded business information needed to remain available for the reporting experience.

This meant thinking about more than the individual screens.

I had to account for how data was structured, how records related to one another and how changes in one workflow affected information elsewhere in the system.

InventTrack Supabase database schema showing relationships between products, sales, suppliers, businesses, memberships and authenticated users

Authentication and user access

I also worked on authentication using Supabase.

The application needed a way for users to access their business environment while supporting the distinction between owner and staff responsibilities.

This connected backend configuration to a central product-design decision: different people using the same system should not automatically receive identical access.

Authentication, account access and the application’s role-aware experience therefore formed part of the technical implementation, not just the interface design.

Implementing connected application behaviour

One of the most important technical requirements was making operational actions produce the expected changes.

Recording a sale needed to update the corresponding stock quantity.

Restocking needed to increase available inventory.

Low-stock conditions needed to respond to quantities and reorder thresholds.

And reporting needed to reflect recorded business activity.

These relationships had to work in the running application, not simply be illustrated in the prototype.

Working through them helped me connect the product’s interaction design with its underlying data structure and implementation.

My AI-assisted development workflow

I used Figma for product discovery, research organisation, interface drafting and design development.

Figma AI supported parts of the UI creation and exploration process.

I used ChatGPT and Claude to support product reasoning, technical planning, application structuring, implementation problem-solving and iteration.

The application itself was developed through an AI-assisted coding approach, often referred to as vibe coding.

My role was to define the product requirements, direct the development process, configure the backend, work through implementation problems and evaluate whether the resulting application behaved as intended.

Using AI-assisted development did not remove the need to make product and technical decisions.

It allowed me to move between defining the experience and implementing it while taking responsibility for the resulting product.

GitHub, deployment and testing

I used GitHub for the project’s source-code workflow and deployed InventTrack to Netlify.

The deployment provided a working environment where the application could be accessed outside Figma.

This made it possible to test InventTrack with real businesses, observe the product in use and continue refining it beyond the original academic project.

It also provided a live application for the small-business owners who began using the product.

Tools & Technologies

Product Design

Figma · Figma AI

Research, Planning & Problem-Solving

Figma · ChatGPT · Claude

Development Approach

AI-Assisted Coding / Vibe Coding

Backend, Database & Authentication

Supabase

Version Control

GitHub

Hosting & Deployment

Netlify

Testing, Validation & Iteration

Testing InventTrack in Real Business Environments

After developing InventTrack into a working application, I tested it with two retail businesses: a pharmacy and a supermarket. Although both manage physical inventory, their product ranges and operational routines differ, providing an opportunity to evaluate how the application supported different retail contexts.

The evaluation focused on understanding how businesses responded to the existing features, which capabilities they found useful, and what was missing from their daily workflows.

What Businesses Valued

Both businesses responded positively to having electronic stock records, allowing them to manage product information digitally rather than relying entirely on manual records.

Automatic stock adjustments stood out as particularly useful. Recording a sale reduced the available inventory quantity, while adding stock increased it. This eliminated the need to manually reconcile stock quantities after each transaction.

They also appreciated automatic sales and profit calculations, which made financial information accessible without manually calculating figures, alongside staff management functionality for businesses where multiple people handle operations.

These responses reinforced the value of connecting inventory, transactions and business information within one application.

What the Feedback Revealed

The evaluation also identified two important gaps in the first release.

1. Product search: Businesses wanted a faster way to locate specific products. As inventory grows, relying on manual browsing becomes less practical. Product search was therefore identified as a priority for the next version.

2. Multi-outlet management: Businesses also expressed a need to manage multiple shop locations within one application. Supporting this would require outlet-specific inventory records, staff assignments and appropriate access controls.

These requests revealed opportunities to expand InventTrack beyond its initial single-business operational structure.

How the Feedback Shaped the Roadmap

The evaluation confirmed that InventTrack’s connected workflows addressed useful operational needs, particularly automatic inventory updates and calculated business information.

It also helped me distinguish between improvements that could strengthen the existing experience and larger capabilities that would require changes to the product’s underlying structure.

Rather than expanding the first release immediately, I used the feedback to inform future priorities, beginning with product search and exploring how multi-outlet inventory and staff access could be supported.

InventTrack mobile application interface overview
InventTrack desktop dashboard, recording sales and managing products
InventTrack desktop suppliers, sales, reports and staff management

Outcome & Early Adoption

From a postgraduate project to a product small businesses are using

InventTrack began as my postgraduate Information Technology project.

But after designing, building and evaluating the application, I decided to continue developing it beyond the academic requirement.

The initial evaluation with a pharmacy and supermarket demonstrated interest in electronic stock-keeping, automatic inventory adjustments and connected business reporting.

Since then, approximately six small-business owners have begun using InventTrack.

This marked an important shift in the project.

It was no longer only a product I had designed to demonstrate an idea. It was a working application being used in actual small-business operations.

Key outcomes

2 businesses

Participated in the initial product evaluation.

~6 small-business owners

Currently using the application.

1 connected application

Supporting inventory, sales, suppliers, reporting and staff access.

What this means

The initial version established a working operational system and attracted early users outside its original academic context.

The feedback also provided a practical basis for deciding what should come next.

I have not yet measured reductions in stock errors, operating costs or task completion times, so I am not attributing numerical efficiency improvements to the product.

The demonstrated outcomes are a functioning application, positive early feedback, real-business usage and an evidence-informed direction for continued development.

Outcomes & Learnings

InventTrack moved beyond a postgraduate project into a working inventory and sales management application, designed and developed from concept to deployment.

I tested the product with a pharmacy and a supermarket, where users responded positively to electronic stock records, automatic inventory deductions when sales were recorded, sales and profit calculations, and staff functionality. The application has since reached approximately six small business owners.

The feedback also exposed opportunities I hadn’t addressed in the initial release. Users requested product search and multi-outlet management with staff assigned to specific locations. These became priorities for future development rather than features added prematurely to the first version.

What I Learned

Building InventTrack strengthened my understanding of product design beyond the interface. Working across UX, database relationships, authentication and implementation made me more deliberate about how design decisions translate into working product behaviour.

It also reinforced a principle I’ll carry into future projects: a useful product isn’t defined by how many features it offers, but by how reliably its core workflows solve the problems users face.

What’s Next

My next priorities are improving product discovery through search, exploring multi-outlet inventory management, refining the mobile experience, and preparing a dedicated website and onboarding experience for a broader launch.

Create a free website with Framer, the website builder loved by startups, designers and agencies.