Sangthong ERP
“A web-based ERP application designed to streamline and simplify business operations.”
Role
UX/UI Design
Tools
Figma
Year
2025
Project Overview
A web-based internal management system for a rain-gutter manufacturing company. The platform supports SKU-based sales, custom product orders, and the issuance of key sales documents such as quotations, billing notes, tax invoices, receipts, deposits, and cash payments.It also includes customer management, inventory control, purchase order creation, and goods receipt tracking,providing a streamlined, end-to-end operational workflow.
Problem
The existing sales and inventory management system has limitations in supporting new products, and most of the management processes are still manual, making tracking and oversight difficult.
Additionally, external systems are used to handle sales documents, but they do not cover all the necessary documentation, resulting in gaps and inefficiencies.
Solution
Implement a centralized, web-based management system that integrates sales, inventory, and document management into a single platform.
This system supports new product additions, automates previously manual processes for better accuracy and efficiency, and consolidates all sales-related documents—including quotations, invoices, receipts, and purchase orders—ensuring complete coverage and streamlined operations across the company.
Flow & Sitemap
Analyze the functional scope of the system, determine all necessary screens and interfaces, and create a comprehensive workflow for generating and processing all payment-related documents.
Components
Designed and organized UI components into a structured library, making them easy to access and reuse throughout the project for a consistent and efficient design process.
User Interface
Pick Products for Sale
allows sellers to select products by category, prepare items for customer orders, and search products by SKU. Users can save orders for later payment, retrieve previously saved orders, and choose to either process immediate payment or issue a quotation on the spot.
Document Generation & Management
enables users to create and manage various sales documents, including quotations, billing statements, tax invoices, receipts, payment records, product deposits, and credit notes. Users can retrieve customer information, past prices, discounts, and credit terms, adjust products and quantities, add notes, calculate totals and taxes, and save or print the completed documents.
Custom Product
allows customers to place custom product orders. Users can enter product details based on predefined product types or available options in the system, or submit detailed design/plan forms directly into the system. Once the order is confirmed, required materials are allocated from the inventory through the backend system to proceed with production.
Customer List
displays all customers who have previously made transactions and allows users to add new customer information. The data is used for generating sales documents, managing discounts, and maintaining customer information in the backend system for future reference.
Backend Management System
allows administrators to manage all core operations, including SKU management, product category management, inventory control, branch management, inter-warehouse transfers, recording price requests, issuing purchase orders (PO), receiving goods from suppliers, customer information management, user permission settings, and tracking system activity through logs.
Project Reflection
What I Learned
this is a company-wide system, it will be relatively large, and some details may be overlooked.It is important to provide a comprehensive summary of system usage so that both the client and developers have a clear and shared understanding. Documentation should include detailed descriptions of each interface’s functions as well as user manuals to ensure the system is delivered completely.
We cannot design the system exactly as the client requests in every aspect due to budget and time constraints. Therefore, feasible solutions within these limits should be identified, and a summary of these decisions should be documented at the time of system delivery.
