← Back to portfolio
Enterprise · Operations · TMS · Live

A terminal management experience built around the operational journey.

Designing the interface for POS terminal requests, merchant validation, request tracking, fault management and reporting — connecting creation, review, monitoring and resolution in one workspace.

ProductTerminal Management System
ContextLotus Bank
RoleUI / UX Designer
FocusWorkflows · Tables · Tracking · States
Live · request link ↗Back to selected work
Terminal Management System sign-in
01 — Challenge

Turn a chain of operational tasks into a traceable workflow.

Terminal operations are not one-step transactions. A request can move through merchant details, validation, review, approval, fulfilment and ongoing issue resolution.

The interface needed to keep status visible while giving teams enough context to act quickly — without forcing them to jump between disconnected screens.

02 — My contribution

Design the workflow from request creation to resolution.

I designed the core TMS journeys shown in the supplied screens, covering the request and tracking lifecycle as well as operational fault handling.

POS terminal requestsCapture merchant details and submit new terminal requests with a focused multi-step flow.
Merchant validationKeep validation and merchant context visible before a request progresses.
Request trackingMake request status, metadata and history scannable for operations teams.
Fault managementSurface fault records, current state and the actions needed to resolve them.
Operational reportingSupport table-based monitoring and higher-level performance views.
Responsive thinkingAccount for narrower operational views while preserving the important information hierarchy.
03 — UX decisions

Make operational status the interface’s organising principle.

Keep status close to context

Status labels sit alongside request details so users can understand what needs attention without opening multiple records.

Separate create and monitor

Request creation uses a guided form while list and tracking views are optimised for scanning and triage.

Design for fast comparison

Tables, filters and compact metadata let teams compare multiple requests or faults at a glance.

Show the next action

Primary controls are placed near the information that explains why the action is relevant.

04 — Screens

The TMS story, arranged as a workflow.

New POS terminal request
Start a request — a clear operational entry point for new POS terminal requests.
POS terminal request details
Merchant and request context.
POS terminal request validation
Validation step before submission.
Fault management list
Fault management — scan multiple issues by status and operational context.
Fault detail
Fault detail and next-step action.
Fault resolution action
Resolution path within the record.
All requests
All requests — a central list for operational monitoring.
Request tracking overview
Request tracking overview.
Request tracking status
Request status and action states.
TMS reporting and analytics
Reporting and analytics — move from individual records to operational visibility.
05 — Outcome

A coherent operational loop.

The supplied screens demonstrate a complete product narrative: sign in, create a request, validate merchant information, track progress, manage faults and review operational data.

The strongest outcome is the continuity between those states. Instead of treating each screen as a separate tool, the interface gives the team a shared model of what is happening, where a request stands and what needs to happen next.