creative
unveiling the soul webdesign label & industry publishing & content
operations
jira salesforce odoo erpnext onbase process design
about say hi
← operations rakamakafon — vinyl pressing · 2026 →

erpnext order processing.

no software before process. mapped how orders actually move through the plant, then made the tool match.

erpnextfrappe cloudsql dashboardsprocess design
the goal

objective

As Operations Director, I own how orders move through the plant — and when I started, there was no single place you could trust. File readiness was unclear, and sales and the floor weren't always clear on who owned what.

phase 1 live & expanding — the operating system for the business
my part

what i did

  • Process first — sat with sales and production, mapped how things actually ran, and locked the rules that mattered: what triggers an order to go live, what pauses it, who owns quality at intake, how a deal becomes a tracked job.
  • Platform decision — wrote requirements, scored platforms against a tight budget, and chose ERPNext on Frappe Cloud — a system we could grow into without pretending to be an enterprise IT team.
  • Hands-on build — configuring the order workflow, automating status alerts and timeline tracking, stripping forms to what the team will actually use daily, and keeping a clean build backlog.
the result

outcomes

  • Process design and platform decision complete.
  • Phase 1 live and expanding.
  • Next: reactive timeline controls, file upload automation, then deeper quoting and production tracking.