KongaPay Inventory

Stock and sales for small businesses, from the POS terminal to the phone, the laptop and Konga’s own team

KongaPay merchants took payments on a POS terminal, but their stock lived in notebooks and spreadsheets. I designed Inventory from 0 to 1: the product thinking, the user flows and the screens for the POS terminal, the merchant app, the merchant web and an admin console for KongaPay’s team.

Merchant web inventory dashboard: total inventory value, sales trend, inventory distribution and alerts
POS terminal inventory home: search or scan, total sales today, stock cards, recent activity and Start New Sale
Merchant app inventory dashboard: total inventory value, stock cards and a sales trend
My roleProduct designer

Product thinking, user flows, UX and UI

TimelineAbout 2 months

of design, from brief to handoff

Worked withCEO, VP of Technology, product manager

and finance, compliance, marketing and developers

Built byAn external agency

on an accelerated schedule, using the KongaPay design system

PlatformsPOS, iOS, Android and web

POS terminal, merchant app for iOS and Android, merchant web

For KongaAn admin console

for KongaPay’s own team

The opportunity

“We want to add inventory management to the POS features.”

The whole brief, from KongaPay’s VP of Technology on a Thursday evening

KongaPay wanted Inventory to serve SMEs and MSMEs: the merchants already taking payments on its terminals, and the small businesses it wanted to win next. The business wanted to be first to market, ship quickly and learn from live merchants, and an external agency was lined up to build it on an accelerated schedule.

There was no requirements document and no research budget. The audience was also much wider than the merchants KongaPay already knew. So before defining the experience, I needed a clear picture of who these businesses were and how they actually sold.

Next chapter: Researchwho sells on a KongaPay terminal

Research

Serving SMEs and MSMEs meant designing for businesses KongaPay hadn’t met yet. Without time or budget for interviews, I built the picture from published data and from the people around the review table. Three findings shaped the first flow.

39.6MMSMEs in Nigeria, 96.9% of them micro businesses

What it meant: design for the one-person shop. No inventory manager, no laptop, no clean product catalogue. The first screen has to make sense on its own.

Micro businesses 96.9%Small and medium 3.1%
88% vs 14%use smartphones in the business, but few use specialised software

What it meant: phone first, with most fields optional. For most merchants this would be their first inventory software, on a small screen.

At the tillnot at a desk

What it meant: on the terminal, scanning, search and Start New Sale go up front.

What most tools assume
  • A stock-take at a desk
  • Counting in batches
  • A laptop and a catalogue
Our merchant
  • Standing at a counter
  • A customer waiting
  • One sale at a time on a terminal

The MSME count is the National Bureau of Statistics figure of 39,654,385 for 2020, as cited in the PwC MSME Survey 2024. Tool use comes from the same PwC survey of Nigerian MSMEs.

Who I designed for

The brief named one device, but the research pointed to three kinds of people, each in a different place when they deal with stock. That decided which surface does which job.

POS terminal inventory home

The owner at the counter

Runs a small shop, often alone.

  • Sell fast, with a customer waiting
  • Know what’s running low
POS terminal and merchant app
Merchant web CSV preview

Whoever keeps the books

An accountant, or a merchant with hundreds of items.

  • Sell fast, with a customer waiting
  • Know what’s running low
Merchant web
Admin low stock alert list

KongaPay’s own team

Operations, finance, compliance and marketing.

  • Sell fast, with a customer waiting
  • Know what’s running low
Admin console
Next chapter: Product decisionssix bets, written down

Product decisions

Without interviews, every feature rested on a belief about merchants. I wrote each one down with the design response and the signal that would show whether it was right after launch.

The first-visit screen listing what the tool does

Our target audience of merchants have never used inventory software

Design: a first screen that explains the tool in 4 short lines, with one button to add the first item.

What would show it worked: new merchants add an item on day one.

CSV preview with row 2 marked Invalid

Many merchants already keep stock in a spreadsheet

Design: CSV upload with a template, a preview, and errors named by row.

What would show it worked: most first stock arrives by CSV, with few failed rows.

POS basket lines with quantity steppers and stock labels

Stock only stays true if the sale happens on the terminal

Design: selling inside inventory, so scan, basket, pay and receipt all move the count.

What would show it worked: most terminal sales carry items, not just an amount.

Basket line with the new unit price and the old price struck through

At the counter, prices get negotiated

Design: an editable unit price that keeps the old price on record.

What would show it worked: price edits are common, and margins in reports match reality.

Delete Item sheet offering Disable Item first

Merchants need to retire items without losing history

Design: Disable offered first whenever someone tries to delete.

What would show it worked: disables outnumber deletes.

Low stock alert and reorder fields with helper text

A low stock warning only helps if someone acts on it

Design: alert and reorder levels the merchant sets, plus nudges from KongaPay’s team.

What would show it worked: restocks follow alerts.

Three rules I used for designing without user interviews

Make every assumption visible

If we were going to learn from live merchants, every decision had to state the belief behind it, so we’d know exactly what to measure after launch. That’s where the six bets came from.

Build on what the agency already knows

Every screen uses the existing KongaPay design system: its type, colour, buttons, forms and sheets. The agency could build fast, and a new pattern had to earn its place.

Leave doors open

Anything we weren’t sure about, like branches and product variations, went in as an optional field rather than a new screen. Easy to grow if merchants use it, easy to remove if they don’t.

Next chapter: The user flowone record, four ways in

The user flow

The brief said POS. But a merchant also checks stock on her phone, her accountant uploads sheets on a laptop, and KongaPay’s team watches the whole network. I mapped the first user flow with a few rough wireframes and got all internal stakeholders in the room so the big questions came up before anything was polished.

Each surface got the jobs that fit where it’s used, and all of them read from and write to one inventory record.

The user flow Zoom 50%

One item, followed across the four surfaces

Because every surface works from the same record, a change in one place shows up everywhere else without anyone re-entering it.

Item Added Successfully on the merchant app
Added on the phone. Stock goes in from the merchant app, one item or a whole sheet.
Card payment receipt on the POS terminal
Sold at the till. The cashier scans, sells, and the receipt moves the count.
Inventory history on the merchant web
Checked on the web. Every stock change lands in history.
Low stock alert list in the admin console
Seen by KongaPay. Merchants below their alert level show up for the ops team to act on.

one inventory record. Added on the phone. adds stock. Sold at the till. deducts on sale. Checked on the web. logs every change. Seen by KongaPay. flags low stock

Some of the questions that changed the flow

Sharing the flow early made room for questions in review. Each of these changed the product, not just a screen, and each one leads to the chapter it shaped.

“Is delete the same as disable?”

It was, in my first flow. Now an item can leave the shelf and keep its history.

The merchant app

“I didn’t see the checkout flow for the POS.”

Selling moved inside inventory, on the terminal where the sale happens.

The POS terminal

“Will merchants get a web version”

Inventory got its own web workspace for bulk work.

The merchant web

“Does POS checkout accommodate haggling?”

Now when the customer asks for a discount, the cashier edits the unit price.

The POS terminal

“How do we handle variants”

Now, merchants can enter stock variations. One product in different sizes or colours

The merchant app

“How is tax added on inventory stock?”

Inventory upload got its tax and tax rate entry point.

The merchant web

The merchant app

Getting stock in

An inventory tool is empty on day one, and an empty tool is easy to abandon. Since our assumption was that our target merchants had never used inventory software, and many already kept stock in a spreadsheet or a notebook. If adding stock felt like work, nothing else in the product would get used.

First visit: Your Inventory, Smarter and Simpler, with 4 short benefits and Add New Inventory
First visit. The tool explained in 4 lines, with one button.
Empty dashboard: No Items Yet, with one Add New Inventory button
2nd visit: Nothing in it yet. The empty state points to one action.
Filled dashboard: total inventory value, stock cards and a sales trend
Once stock is in. Value first, then counts, alerts and sales.

Three ways in, one review before saving

Stock arrives as a box with a supplier receipt, as one-off items, or as a spreadsheet kept for years. So Add New Inventory opens three options: scan a receipt, add manually, or upload a CSV.

Every route ends the same way. Before anything saves, the merchant sees a summary of what she is adding.

Add New Inventory sheet with three options: Scan receipt, Add manually, Upload CSV
Every route starts here.
Add New Item step 1 of 3
What it is. Only the item type and name are required.
Add New Item step 2 of 3: prices, tax, low stock alert and reorder point
Price and alerts. Helper text says what each number will do.
Add New Item step 3 of 3: review before saving
Review. Every field, before anything saves.
Item Added Successfully, with Add Another Item and Done
Added. Adding another item is the likely next step, so it comes first.

Products sold in different sizes or colours go in as variations of one item, so the merchant isn’t creating the same product five times.

Add New Item with multiple variations
One product. Name it once, as an item with variations.
Variant attributes: size and colour, each with its own quantity and prices
Its variations. Sizes or colours, each with its own stock and price.
Review of an item with multiple variations
One review. Each variant listed, before saving.

When the spreadsheet has mistakes

A merchant uploading her old stock list is trusting us with years of work, and a sheet kept by hand will have mistakes in it. Errors are named by row, with what to fix, so one bad row never sinks the whole upload.

Upload Inventory CSV: choose a file, with a sample template
Template. Start from the sample CSV.
Inventory preview with row 2 marked Invalid and 1 Error Found
Preview. The bad row, named, before anything saves.
View All or Edit Upload: every row from the sheet
View all. Every row from the sheet, to check or edit before saving.
Upload Successful with the upload summary
Summary. What went in, what didn’t, and the value added.
Inventory preview table with row 2 highlighted as Invalid
The bad row, in place.
1 Error Found: Row 2, invalid SKU format
Named by row, with the fix.
Re-upload and Upload Anyway
Fix the file, or keep the good rows.

Retiring an item without losing its history

“Is delete the same as disable?”

In my first flow it was. The question made me look at what deleting really does. If a merchant deletes an item she has sold, last month’s receipts and finance’s reports lose their story.

So I split the two. Disable takes an item off the shelf, keeps its history, and can be turned back on. Delete still exists, but its confirmation offers Disable first.

Delete Item sheet offering Disable Item before Delete Item
Delete asks first. The sheet offers Disable before Delete.
All inventory list with a confirmation that the item was disabled
Off the shelf. The item stays in the list, marked Disabled.
Details of a disabled item with an Enable Item button
Back any time. Its history is intact, and it can be enabled again.

The POS terminal

Selling at the till

“I didn’t see the checkout flow for the POS.”

I had scoped inventory as stockkeeping: add items, track them, and get alerts. But stakeholders wanted it as a till. If the sale happens somewhere else, the count drifts and merchants stop trusting it. So selling moved inside inventory on the terminal where the sale happens.

That changed the terminal’s home screen. Earlier wireframes led with a list of stock. The version we handed off works like a till: search or scan at the top, the day’s sales, stock cards, and one list of recent activity where a sale and the low stock alert it causes sit together.

POS terminal home: search or scan, total sales today, stock cards, recent activity and Start New Sale
  • Add entry point for scanning items
  • Total items, low stock, out of stock and transactions cards are clickable
  • Recent activities should display all sales transactions, and stock update alerts (low stock, out of stock, in stock)
  • Add entry point for checkout process

Scan to receipt

Here’s the scenario I designed for. A customer wants one iPhone and four MacBooks, then asks for a discount. Every line shows its stock status, the cashier can change a price, and the old price stays on record.

Start New Sale search with suggestions
Search. A name or SKU. The scanner sits in the same bar.
Scan Item: the terminal camera with a barcode frame
Scan. Point the terminal camera at the barcode.
Basket with iPhone 14 Pro and four MacBook Air M2, marked Low stock
Basket. Low stock shows before the cashier promises four.
Edit Unit Price sheet with a number pad
Haggle. The customer asks for a discount, so the cashier edits the price.
Basket line with the new unit price and the old price struck through
On record. The new price shows, and the old one stays on record.
Invoice summary with subtotal, tax, total and payment methods
Invoice. Subtotal, tax and total, then card, transfer or cash.
Enter Card PIN for the full amount
PIN. The customer enters their card PIN.
Payment success with Print Receipt
Receipt. The receipt prints, and the count moves.
Next chapter: The merchant webtables, drawers and history

The merchant web

A workspace built for bulk work

“Will merchants get a web version?”

Our assumption was that merchants with hundreds of items and accountants who keep their books, do the heavy work on a laptop. Inventory got its own web workspace inside the existing merchant dashboard.

Tables replace cards. Adding stock happens in a drawer, so the page stays in view, and the steps, fields and helper text match the app, so nobody learns the tool twice.

Merchant web with the Add New Item drawer open, step 1

What it is. The drawer slides in over the page you were on. Single item, or one with variations.

The same upload, with room for a wide table

On a laptop the merchant can see every column of her sheet at once. Errors are still named by row, and if she chooses to go ahead, only the valid rows go in.

CSV inventory preview with invalid rows highlighted and the errors listed underneath
Upload Inventory CSV drawer
Upload. The same template as the app.
Upload with Invalid Items? 4 skipped, 12 added
Partial upload. Skip the bad rows, keep the good ones, and say how many of each.
Upload Successful with the upload summary
Summary. Added, failed and the total value, in one place.

Once stock is in

The dashboard leads with value, then the trend, the mix of stock and the alerts. History, sales, reports and users each get a full table.

Merchant web inventory dashboard
Inventory history table
History. Every item and change. Disabled items stay, marked Inactive.
Sales history by branch and purchase type
Sales. Transactions by branch and purchase type.
Reports: sales, top selling items, categories and stock status
Reports. Sales, profit, taxes and stock status.
Users table with roles and branches
Users. Everyone who touches the stock.

A merchant with staff can bring her team in. Each person gets a role and for merchants with multiple locations, a branch.

Add New User drawer: role, name, email and branch
Invite. A role and a branch for each person.
Enter your 4-digit PIN to confirm
Confirm. Adding someone who can touch the stock asks for your PIN.

The admin console

Watching the network

Finance, compliance and marketing each asked what KongaPay would see. The console shows the network: who is about to run out, which terminals have gone quiet, and who changed what.

From a low stock alert to a nudge

A low stock warning only helps if someone acts on it. Ops can see every merchant below their alert level, with the value at risk, and send them a nudge in three steps.

Admin overview: active merchants, sales, inventory value, pending verifications, trends

Overview. Active merchants, sales, inventory value and pending verifications, then the sales trend and top performers.

Merchants and terminals

Every merchant with their status and activity, and every terminal with whether it’s online, in one place for the team that supports them.

User management: every merchant with type, contact, branches and status
Merchants. Every merchant, with branches, status and pending verification.
Settings and controls, POS device usage
Devices. Which terminals are online, offline or idle.
Next chapter: Delivery and reflectionbuilding it with the agency

Delivery and reflection

Building it with an agency, on an accelerated schedule

An external agency built Inventory, and KongaPay wanted to be first to market, so the schedule was tight from the start. That shaped how I worked as much as what I designed: every decision had to be clear enough for the agency to build from fast.

Several rounds of testing the staging build ensured that the implementation actually matched the defined user experience.

About 8 weeks of design, from brief to handoff

New pieces, built on the KongaPay design system

I kept the system’s type, magenta, black primary buttons, forms and sheets, and added a few inventory pieces that behave the same on all four surfaces.

Stat cards

Transactions57
Total Items1,234
Low Stock45
Out of Stock12

Each card is tappable and leads to the items behind the number, on every surface.

Stock status

In stockLow stockOut of stockDisabled

Colour and words together, so nobody has to remember what yellow means. Disabled is grey on purpose, because it isn’t a warning.

Activity row

#KP20250013 items sold · 10:23 AM
₦151,200
MacBook Air M2SKU: MBA-M2-512
2 unitsLow stock
Wireless EarbudsSKU: IP14-PRO-222
Out of stock

Sales and stock changes share one row, so a sale and the alert it triggers sit side by side.

Step header

Add New Item Step 1 of 3
Low stock alert
0
You’ll receive alerts when stock falls below this number

Three steps, always visible, on the phone and in the web drawer. Helper text says what each number will do.

Destructive action sheet

Delete Item

Are you sure you want to delete this item? You can disable this item instead of deleting the item

Disable ItemDelete Item

Any action that loses history offers the reversible option first.

What was delivered

The agency built from the files, and Inventory went live for KongaPay merchants. A one-line brief about the POS became one inventory record behind four surfaces: selling on the terminal, adding and managing stock on the phone, bulk work on the web, and a view of the whole network for KongaPay’s team.

There’s no post-launch usage data for me to share. The research shaped who we designed for, and the six bets say what should be measured. If I had stayed at Konga longer after launch, I would have:

  • Tracked the six bets against real use in the first 90 days, starting with how many new merchants add an item on day one and how much stock arrives by CSV.
  • Spent a busy afternoon beside a cashier on a KongaPay terminal, watching where the sale slows down.
  • Reviewed the alert data with KongaPay’s ops team to see which nudges led to restocks, and tuned the default alert and reorder levels from that.

Looking back

The best reviews were questions. Sharing a rough flow early is what made room for meaningful questions.

Without interviews, the bets were the research I could act on. Writing each one with its signal turned guesses into things the team could check after launch.

Get in touch

Email me

Open to design roles. I’m in Lagos, and my hours match the UK and Europe, with a few hours of overlap with the US.

You made it this far! Want to feed a giraffe, or help feed a baby elephant?