2025Seoul OasisWeb + Mobile

Enterprise ERP & Sales Force Automation Platform

A web ERP and a mobile sales app designed as one ecosystem, so an order placed in the field reaches the warehouse and finance in seconds.

ERP dashboard on desktop with the SFA app on a phone
Overview

Two products, designed as one business.

This project connected two products into one business: a web-based ERP that runs internal operations, and a mobile Sales Force Automation (SFA) app that puts the same operational intelligence into the hands of field sales reps. Instead of designing them as separate tools, I approached them as one ecosystem — a rep's order placed at a customer's door should be visible to a warehouse manager and a finance controller within seconds, not by end of day.

My role
  • Stakeholder research
  • Information architecture
  • User flows
  • Wireframes
  • High-fidelity UI
  • Design system
  • Prototyping
  • Developer handoff
Core problem

A patchwork of tools that didn’t talk to each other.

The organization was running on multiple disconnected third-party systems layered on top of manual processes — separate tools for sales, inventory, accounting, and customer management. Field sales reps recorded orders by hand, then re-entered them later, which meant delays, duplicate data entry, inventory mismatches, and management flying blind on what was actually happening outside the office.

Goal

Replace the patchwork with one connected ecosystem — a web ERP for internal operations and a mobile SFA app for the field — sharing the same real-time data, so every department is working off the same picture.

Research highlights

What every team told us.

I met stakeholders across sales, warehouse, finance and management to understand how each team actually worked. These findings came up again and again, and shaped most of the decisions that followed.
01

Speed in the field is non-negotiable.

Reps needed to place an order in minutes, standing in front of a customer — not after driving back to the office.

02

Visibility beats reporting.

Managers didn't want another report; they wanted to see field activity as it happened.

03

Reconciliation was eating finance's week.

Manual matching of records across systems was the single biggest time sink for finance.

04

Stock data had to be trustworthy.

Warehouse teams needed one accurate number, not three conflicting ones.

05

Executives wanted answers, not spreadsheets.

A dashboard that surfaced insight, not just data.

Design process

From discovery to developer handoff.

01Discover
02Research
03Information Architecture
04User Flows
05Low-Fidelity Wireframes
06High-Fidelity UI
07Interactive Prototypes
08Usability Testing
09Iterate
10Developer Handoff

A single, shared design system carried color, typography, grid, and components across both the web and mobile products — buttons, cards, tables, forms, modals, status indicators, and charts — so the experience felt like one product family, not two separately built apps, while also speeding up development.

Shared design system across web and mobile
The solution

Two products, one ecosystem.

ERP and SFA screens
ERP · Web

Runs the business

  • AI Dashboard
  • CRM
  • Sales
  • Purchase
  • Inventory / Warehouse
  • Accounting
  • HRMS
  • Payroll
  • Assets
  • Approvals
  • Reports
  • Admin

The dashboard surfaces AI-driven insights — trends, anomalies, and forecasts — so executives get a head start on decisions instead of a pile of spreadsheets to interpret themselves.

SFA · Mobile

Runs the field

  • Visit planning
  • GPS check-in
  • Route optimization
  • Order taking
  • Live stock
  • Collections
  • Customer history
  • Promotions
  • Offline mode + sync

Access is role-based across Warehouse Gatekeeper, Manager, and Sales Person — each sees a tailored view built around their day, not a one-size-fits-all app.

The core loop
  1. 1Rep checks inat a customer site
  2. 2Places an orderon the spot, in the SFA app
  3. 3Syncs to the ERPin real time
  4. 4Seen livemanager sees the order, warehouse sees updated stock

What used to be a next-day report becomes a real-time event.

Key UX decisions

Six decisions, each tied to a real constraint.

AreaDecisionWhy it mattered
ERP DashboardAI-driven insights, KPI cards, live activity feedTurned raw data into decisions executives could act on immediately
ERP FormsStep-by-step sections, auto-save, validationReduced errors and abandonment on long, complex entries
ERP TablesSticky headers, advanced filters, bulk actions, exportMade heavy operational data actually usable at scale
SFA InteractionsOne-handed use, large touch targetsReps use the app while standing, walking, holding products
SFA ConnectivityOffline-first with auto-syncField areas often had poor signal — the app couldn't stop working
SFA AccessRole-based views for Gatekeeper, Manager, Sales PersonEach role sees only what's relevant to their job, not a generic dashboard
Business impact

What changed for the business.

Executives moved from raw reports to AI-generated insights and forecasts
Faster order processing and less manual data entry
More accurate, trustworthy inventory data across warehouse and sales
Real-time visibility into field sales activity for managers
Faster approval cycles with clear status tracking
Significantly reduced manual reconciliation time for finance
One consistent experience across desktop and mobile — no relearning between platforms
Key takeaway
Enterprise complexity and usability aren’t in conflict when research stays continuous and the design system is shared.

Connecting ERP and SFA into a single ecosystem — instead of treating them as separate products — turned scattered, delayed, third-party-fragmented data into one real-time, organization-wide view. That’s the difference between a tool people tolerate and a system they actually run their business on.

Final screens

The finished product.

Final ERP and SFA screens