WASBANAWASBANAWASBANA

Distribution Operations · CASE STUDY

From spreadsheet-based distribution workflows to a structured transaction system.

NJS is a management system for an electronics distribution business. It was shaped around operational workflows that previously relied heavily on spreadsheets, bringing master data, purchasing, sales, stock checks, invoices, payments, and reporting into one system.

Project Type
Business System
Focus
Distribution Operations
Demo
No public demo available
NJS operational dashboard: purchase order, sales order, delivery, stock, stock value summaries, and the overdue customer invoice list.

OVERVIEW

Business Context

Distribution operations involve connected transactions: a purchase order affects incoming goods, sales affect delivery and stock, and invoices with partial payments need to stay connected to their original transaction.

The Challenge

The prior Excel-based workflow struggled with access roles, item tracking, stock checking, duplicated data, and consistent transaction reporting.

SYSTEM

What was designed and built.

Master Data

  • Users
  • Customers
  • Positions
  • Departments
  • Products
  • Brands
  • Suppliers
  • VAT
  • Company profile

Purchase

  • Purchase order
  • Partial inbound
  • Invoice
  • Partial payment

Sales

  • Sales order
  • Delivery
  • Invoice
  • Return
  • Partial payment

Reporting / Operational Visibility

  • Transaction reporting
  • Item / stock visibility
  • Consistent data across workflows

Main Workflow

Purchase

  1. Purchase order
  2. Partial inbound
  3. Invoice
  4. Partial payment

Sales

  1. Sales order
  2. Delivery
  3. Invoice
  4. Return / payment

Shared data

  1. Product
  2. Customer
  3. Supplier
  4. Stock
  5. Reporting

GALLERY

More of the system.

Purchase invoice list with a payment dialog: total billed, remaining balance, payment amount, date, and payment type.
Partial payments are recorded against the invoice, so the remaining balance stays tied to its original purchase.
Sales delivery checker list: delivery order codes, linked sales order numbers, employee, address, and separate admin and checker statuses.
Delivery passes two separate approvals — admin and checker — before it is treated as done.
Stock value page: normal and damaged stock totals, their values, grand total, brand and type filters, and a per-item valuation table.
Stock is read as inventory value — normal against damaged — not just as a quantity on hand.

WHAT THIS CASE DEMONSTRATES

Capability shown by this project.

  • Workflow mapping
  • Transactional system design
  • Data relationships across modules
  • Operational visibility beyond CRUD forms