All projects

YENKO – ADMIN PORTAL

One command centre for a last-mile delivery operation.

Client
Yenko Logistics
Service provided
Web app – Admin dashboard
Duration
2 weeks
Year
2025
Tools
Figma
Platform
Web (desktop, 1440)
View prototype
Yenko – Admin portal: One command centre for a last-mile delivery operation

BACKGROUND & CONTEXT

  • The Yenko apps create a lot of moving parts: deliveries in progress, new couriers to verify, payments held until drop-off, and people asking for help.
  • Without one view, operations staff chase each of these in a different tool and find problems after customers do.
  • Courier verification (ID, licence, vehicle documents) is a trust problem as much as an admin task.

TARGET USERS

  • Operations managers: watching live deliveries and completion rate, deciding where to step in

  • Compliance staff: reviewing courier documents, deciding to approve or suspend

  • Finance and support agents: tracing a payment or answering a customer or courier, deciding on refunds

THE GOAL

Give a small operations team one place to see what is moving, who is waiting for approval, where the money is, and who needs help.

MY PROCESS

  1. Ops workflow mapping
  2. Information architecture
  3. Wireframes
  4. UI
  5. Prototype

KEY DECISIONS

  1. Headline numbers first, detail one click away: ongoing deliveries, active couriers, revenue in GHS, completion rate
  2. One pattern for every module: KPI cards, a searchable table, then a full detail page
  3. Courier approval as a queue with the documents beside Approve and Suspend
  4. The same status steps the customer sees in the app, so support and customers talk about the same thing
  5. Payments shown with an escrow step: Initiated → Pending in escrow → Completed

THE SOLUTION

  • Dashboard: four headline numbers, the latest ongoing deliveries and recently approved couriers.
  • Approvals: a review queue with Pending, Approved and Rejected states, and a detail page for ID, licence and vehicle documents.
  • Money: transactions by method (Mobile Money, card, cash) with an escrow timeline, refunds and printable receipts.
  • Support and analytics: two-pane chat with role badges, and charts for revenue, delivery outcomes, peak hours and top riders, exportable as PDF.

KEY FEATURES

  1. Analytics summary in GHS
  2. Courier approval queue
  3. Deliveries table & detail
  4. Transactions with escrow
  5. Two-pane support chat
  6. Settings with 2FA

DESIGN SYSTEM & ACCESSIBILITY

  • Table, filter, status chip and detail-page patterns reused across all eight sidebar modules.
  • Status chips pair a text label with a tint, so Pending, Approved and Failed read without colour.
  • Next round: the amber 'Pending' chip and grey table headers fall below AA, and the sidebar background should stretch on long pages.
View gallery (11 images)Hide gallery
Sitemap of the Yenko admin: eight sidebar modules each with a table and detail page(opens full size in a new tab)
Eight modules, one pattern: a table you can search, and a page for each record.
Admin dashboard with ongoing deliveries, active delivery services, total revenue in GHS and completion rate(opens full size in a new tab)
Four numbers, then the deliveries behind them.
Analytics page with revenue trend, delivery breakdown donut, peak order hours and top riders(opens full size in a new tab)
Analytics answers the questions ops actually asks: when are we busiest, and who carries the load?
Approvals queue table with pending, approved and rejected courier applications(opens full size in a new tab)
Courier verification as a queue, not a pile of forms.
Courier approval detail with ID, licence and vehicle documents and Approve and Suspend buttons(opens full size in a new tab)
Documents sit next to the decision.
Transactions page with revenue, net income, payouts and a table of Mobile Money, card and cash payments(opens full size in a new tab)
Money in, money out, by method.
Transaction detail showing Mobile Money to Yenko Wallet with an Initiated, Pending in escrow, Completed timeline(opens full size in a new tab)
Payments are held until delivery, and the timeline says so.
Delivery detail with sender, courier and recipient and a status stepper(opens full size in a new tab)
The same stages the customer sees in the app.
Two-pane support chat with Customer and Delivery Service role badges(opens full size in a new tab)
Support knows who it's talking to before it replies.
Contrast checks for the admin's status chips and table text(opens full size in a new tab)
Labels make status readable without colour; the amber chip is the one to fix.
Admin login screen beside the Yenko mobile app(opens full size in a new tab)
The admin login shows the app it runs, tying the two products together.

BY THE NUMBERS

Dashboard for deliveries, money and support
1
From any headline number to the detail
1 click
On every payment, held until drop-off
Escrow

OUTCOME

  • Every operational question has an address: deliveries, approvals, money, users, support and settings.
  • Admins see the same delivery stages as customers and couriers, which makes support conversations shorter.
  • Escrow, refunds and suspensions are visible actions, not database edits.

What I learned

In data-dense tools, one pattern repeated beats eight clever ones.

View prototype