Back to Home

CASE STUDY

Digitising a company’s entire operation from scratch

By Karaca FileSecurity netting and industrial textile manufacturing
My role
Lead Fullstack Developer
Period
April 2026 — ongoing
Scope
B2B commerce platform + Micro ERP

The situation

Sales and operations ran on separate tracks. Orders arrived by phone and WhatsApp, stock was tracked in hand-kept spreadsheets, and invoices were prepared somewhere else entirely.

The real cost of that setup was not mistakes but repetition: the same information was typed into three different places. Finding out where an order stood meant asking two or three people.

An off-the-shelf store or a boxed ERP did not fit the trade. Security netting is sold by square metre, weave type and custom dimensions — standard product-and-variant logic does not describe that.

Approach

01

I learned the process before writing code

The first job was following a single order all the way through the company. Which step waits on whom, where information gets lost. Most of the technical decisions came out of that map.

02

One flow, not two systems bolted together

Commerce and ERP are usually separate products with an integration layer between them. Here I designed both to face each other from the start: an order placed in the store is a record the ERP is already expecting.

03

No compromise where the trade is specific

Proforma invoicing, custom-dimension pricing and wholesale tiers are either missing from ready-made tools or awkwardly bolted on. Rather than force them into a generic shape, I wrote them as their own modules.

04

A system someone else can take over

The people using it are not developers. I built every screen on the assumption that someone would sit down at it for the first time without training; anywhere that needs explaining is a design failure.

Outcome

  • Orders, stock, accounts and invoicing live in one panel. The same information is no longer entered by hand in several places.
  • Everyone sees their own work: separate panels for the owner, accounting, field staff and online sales.
  • Invoices, account statements and reference documents come out of the system itself rather than a separate program.
  • Barcode and QR scanning works in the warehouse, so stock counts and movements need no manual entry.
  • An order placed online lands directly in the panel and notifies the right person immediately.
  • Spreadsheet-and-paper tracking has moved into the system; the status of an order is visible from one place.

Scale of the system

31

Data tables

4

Role-specific panels

5 months

Active development since first release

What the system covers

Order managementWarehouse and stockCustomer accountsInvoicingFinancial ledgerCash and expensesSupplier trackingStaff and field workSupport ticketsOnline order flow

The figures above describe the scale of the system; no before-and-after measurement of business results has been taken yet. Instrumentation for volume going through the system is being set up, and numbers will be added here once they exist.

Why there are no screenshots

The ERP holds the company’s internal operations, customer records and pricing, and falls under a non-disclosure agreement. This page describes what the system does; it does not share screens or code. I am happy to talk through the design in a conversation.

View the Store

Have something similar?

If your operation is scattered across tools that were never built for your trade, let’s talk.

Get in Touch