Sales & Procurement System

What it was

A full sales-procurement system for export clients—quote, order, purchase, ship—folded out of email, sheets, and chat.

I owned the full loop: business mapping, solution design, development, launch, and day-to-day ops.

What was stuck

Export ops ran on memory and scattered records. Revisions and purchase status were hard to trace; as volume grew, information fragmentation broke first—not headcount.

What I did

Master data first: unified customer and supplier records—no three spellings for one vendor.
Quote management: inquiry, quote, and revisions with version history.
Order–purchase linkage: sales orders drive procurement—one ledger, not two.
Shipment and documents: status and paperwork in one system.
Permissions and reconciliation: role-based access, traceable documents.

Flow

Master data

Unified customer, supplier, and product records—one thing, one spelling.

Inquiry → quote

Quotes with version history—every revision visible.

Order → purchase

Sales orders drive procurement—no parallel books.

Ship & reconcile

Shipment, documents, and reconciliation in one loop—errors are locatable.

Outcomes

Running stably in real export businesses for daily sales-procurement work.
From spreadsheets to system: enter once, find everywhere.

What independent delivery means

At big companies the method scaled to large teams; independently I compress the same method into one person—mapping through conversation, design as a path diagram, build aligned to the path, ops by me.

Clients get full methodology delivery compressed into one accountable loop—not a side project.

How I saw it: Lock the path first, then grow features

Appendix

Independent product work—one person from mapping to ops.