LMS
LMS is an internal platform for submitting and managing price requests and supporting documents for purchase requests and purchase orders across various item types and categories. The platform supports multiple user roles and complex workflows, with approval processes involving higher-level users.
Domain
Pricing Management
Time
2026
Role
Product Designer
My responsibility
-
Designed interfaces for end users and business coordinators (admins).
-
Created interactive prototypes to demonstrate complex workflows and approval processes.
Project Overview
LMS supports two main workflows: Internal Price Approval and Customer Submission.
1. Internal Price Approval
-
Users submit price requests for purchase requests and purchase orders.
-
Each request can contain multiple items, but all items must belong to the same item type and category.
-
Users can also upload supporting documents. The required document types depend on the item's category, price-setting method, and document requirements defined for each request.
-
Once submitted, the request goes through a series of approvals by higher-level users until it receives final internal approval.
2. Customer Submission
-
After internal approval, the request moves to the customer submission stage.
-
Users prepare a Cover Note (summary table of the request) and a HOTO file containing multiple Cover Notes.
-
The customer approval process takes place outside the platform. Users track and update the workflow status in LMS as the request progresses through customer approval.
-
Once the customer grants final approval, the approved price and its validity period are recorded in the system. This information serves as the reference for comparing future price requests.
About the Users
There are 5 user roles on the platform, each with different access permissions and responsibilities.
-
Create requests and upload supporting documents, with certain fields hidden based on the Requestor's access permissions.
-
Edit requests that have been rejected by the Centre Representative.
My Work Process
-
Requirement Analysis: Reviewed business requirements provided by the BA and clarified any ambiguities to ensure a clear understanding of the expected functionality.
-
UI/UX Design: Designed and reviewed interfaces with the client to ensure usability, ease of use, and alignment with business requirements.
-
Backlog Refinement: Supported the BA during backlog refinement by clarifying design specifications and component behaviors.
-
Design Iteration: Refined designs based on developers' feedback, considering technical constraints and suggestions for feature improvements.
-
Problem-solving & Collaboration: Proactively raised and discussed development challenges with the team to identify suitable solutions.
-
QA & Validation: Collaborated with QA/QC teams to verify UI implementation and ensure user flows accurately reflected the design specifications.
Internal Price Approval
Manage all price-setting requests across the platform, including creating, viewing, updating, and approving or rejecting requests at all user levels. By leveraging the company's Fabric Design System, I ensured design consistency across products while streamlining the development process through reusable components.
Price Setting Requests list
View the status of all requests, including Internal and Customer statuses. Users can hover over the counter next to the MPN/NSN to view detailed information.
The Requests list table contains multiple columns, so the first two columns remain frozen when users scroll horizontally, keeping key information visible at all times.
Create New Request
CHALLENGES
Each request contains multiple items. The Requestor or Centre Representative must provide detailed information for each item. Some information is shared across all items, such as item type, category, material group, platform, price group, and selected document types. Other information varies from item to item. Supporting documents are also required based on each item's category, price-setting method, and the document requirements defined for the request.
SOLUTIONS
To improve information organization and simplify the request creation process, I grouped the fields into four tabs: General Information, Material Information, Supporting Documents, and Approval Details.
1. General Information:
Contains information that applies to all items within the request.
2. Material Information:
Allows users to add or remove items within a request (up to 50 items) and provide detailed information for each item.
3. Supporting Documents:
Provides drag-and-drop upload areas for the documents required for the request.
4. Approval Details:
Allows users to select approvers. The system automatically selects the default approvers, which users can change if needed.
Request Details
After creating and submitting a request, users can view all its details on the Request Details page. Depending on the request status and their assigned role, users can take actions such as editing, approving or rejecting the request, subject to their permission level.
Comment on item details
Depending on the request status and user permissions, users can click the Comment button in the Item Details table to add comments to individual cells. This helps other users involved in the request understand exactly which fields need to be corrected when a request is rejected. Clicking on a cell opens a side panel where users can add and save their comments.
Once saved, commented cells are marked with an orange dot for easy identification, while the corresponding column header displays a counter showing the total number of cells with comments.
Users can click on any commented cell to view its comments in the side panel or click View All in the Comments section below the table to view all comments across the entire table.
Customer Submission
Manage and Generate Cover Note
Once a request is approved through the internal approval workflow, a new Customer Submission tab becomes available on the Request Details page.
Only users with the Price Controller role are permitted to generate and export the Cover Note, which is then sent to the customer for review and approval.
.png)
Manage and Generate HOTO File
The Price Controller can add the exported Cover Note to the HOTO file, save the file, and export the completed HOTO file to send to the customer.
Update Customer Submission status for each request
After the Cover Note is exported and downloaded, the workflow continues outside the platform. The Price Controller updates the Customer Submission status based on customer feedback, and all status changes are recorded in the system for tracking and auditing purposes.
Upon customer approval, the approved price and its validity period are saved in the system.
