Indo Karya Beton Case Study | Custom ERP — Lenka Studio

Indo Karya Beton

A custom ERP for PT. Indo Karya Beton — one system carrying a precast order from contract to delivery note to invoice.

The IKB Operations contract list — contract number, client, reference, linked sales orders, date, contract value and status

Industry

Precast Concrete Manufacturing

Services

Product Design, UI/UX Design, Custom ERP Development

Platform

Internal Web Application

About the Client

PT. Indo Karya Beton casts precast concrete in Central Java — and sells it by the contract, not by the item.

IKB manufactures PC spun piles and related precast products for contractors working on infrastructure and building projects across Indonesia. The catalogue alone runs to dozens of variants — spun pile in A, AB and B classes, diameters from 400 to 500, wall thicknesses from 75 to 120 — and a single job runs for months. A contract sets a ceiling per product, sales orders draw against that ceiling, the plant produces to spec, trucks deliver in batches against surat jalan, and invoices follow the deliveries. Purchasing runs its own chain in parallel, from purchase request through to freight bills.

The Challenge

The work was spread across spreadsheets, printed books and accounting software that didn't talk to each other. Answering a question as basic as how much of this contract is left? meant adding up sales orders by hand. Deliveries and invoices were reconciled manually, which is exactly where double-billing and missed billing come from. Recorded stock drifted from yard stock. And nothing on the buying side — material, supplier POs, goods receipts — was connected to what the plant had actually committed to produce.

The IKB product catalogue, listing PC spun pile families by spec code with variant count, total stock and status
The Stok module rail beside the product catalogue, listing spun pile variants by class and dimension
The Purchasing module expanded — supplier, material, purchase request, supplier PO, goods receipt, supplier invoice and freight bill

Our Approach

Model the document chain the business already runs on.

We didn't start from an ERP template — we started from IKB's own paperwork. Contract, sales order, proforma, surat jalan, berita acara, tanda terima, invoice, pembayaran: each document knows its parent, so a contract's ceiling draws down on its own as orders and deliveries are entered, and every invoice line traces back to the delivery that earned it. The catalogue is modelled as family plus spec rather than a flat product list, which is how the plant and the contractors both talk about spun pile. Purchasing mirrors the same chain from purchase request to freight bill, so buying and selling finally share a stock figure. The whole interface is in Indonesian, because that is what the team speaks, and command-K search cuts straight to a PO, invoice or surat jalan by number.

The Result

One place to answer “where is this order?”

IKB now runs contracts, sales orders, deliveries, invoicing, stock, purchasing and payroll out of a single system, with role-based access so the owner, the plant and the office each see their own slice. Remaining ceiling per product is visible on the contract itself. Any surat jalan traces back to its sales order and forward to its invoice. New staff are walked through the system by a step-by-step in-app guide rather than by someone's memory, and the interface follows light, dark or system theme — a small thing that matters when half the team works from a plant office and half from a screen at night.

The in-app getting-started guide, tracking setup progress step by step
The light, dark and system theme switcher

Running your operation out of spreadsheets that no longer fit?

We build internal systems around how a business actually works, not around a template. Let's talk about yours.

Get a Free Consultation Get a Free Consultation