ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Services

An ERP sized for the business that runs it.

Sales, point of sale, multi-warehouse inventory, purchasing, and accounting in one system — built for village enterprises and small businesses that neither need nor can afford enterprise-scale ERP.

ERP for Village Enterprises & Small Business

Most small businesses stall at the same point: sales recorded in one place, stock in another, and the books reassembled at month end from a pile of receipts. While turnover is small, that works. Add a second warehouse, a third employee, or marketplace sales, and the numbers stop agreeing with nobody able to say where the gap is.

An ERP at this scale exists to close that gap: one sale simultaneously reduces stock, records the receivable, and forms its journal entry. No double entry by hand, so no two departments can hold different numbers.

Jadiin.online runs this pattern in production across roughly 75 data models: sales, POS, an online store, purchasing, multi-warehouse stock with batch and serial tracking, full accounting, payroll, and assets. Payments use an interchangeable gateway layer — six are supported, chosen by whichever costs that business least.

Scope

What the work covers.

Sales & point of sale

Quotations, sales orders, invoices, delivery orders, and cashier transactions. An online store with catalogue, cart, checkout, customer accounts, and order history where it is actually needed.

Stock & warehouses

Inventory per warehouse with a stock movement recorded for every transaction, staged inter-warehouse transfers, batch and expiry tracking, barcodes, and label printing.

Purchasing & suppliers

Purchase orders with approval, goods receipt, payables, and transaction history per supplier.

Accounting

Chart of accounts, journals, posting, period locking, profit and loss, cash flow, general ledger, bank reconciliation, budgets, cost centres, and tax reporting.

Payments

An interchangeable gateway layer: Midtrans, Xendit, Doku, Tripay, Faspay, and Nicepay. Including manual transfer evidence with admin verification where customers are not used to paying online.

Reporting & profit sharing

Sales, inventory, daily profit, and product analytics. For village enterprises: cash books, monthly reports, accountability reports, work programmes, and profit-sharing calculations.

Evidence

Systems already running.

Not mockups — every one of these was built, handed over, and is used daily.

How it works

From first conversation to handover.

  1. 1

    Look at the books as they are

    The spreadsheet, cash book, or notes in use are the best starting point. They show what is genuinely recorded and what has been skipped.

  2. 2

    Decide what is switched on

    A full ERP is rarely needed on day one. Better to turn on what helps now and leave the rest for later.

  3. 3

    Build in stages

    Sales and stock usually come first because they are used daily; accounting follows once transaction data flows correctly.

  4. 4

    Opening balances

    Opening stock, cash, receivables, and payables are entered carefully. A mistake here is carried forever.

  5. 5

    Handover & support

    Cashier and admin training on their own data, then support through the first month-end close.

Common questions

What people usually ask.

Does the ERP have to be complete from the start?

No, and it is better if it is not. Switching everything on at a business not yet used to recording things is how systems get abandoned. Usually sales and stock first, accounting once the transaction flow is clean.

Does it work for a village enterprise with several business units?

Yes. The pattern of one entity with units beneath it is something I have built for a regency-wide village enterprise portal, with per-unit cash books, monthly reports, accountability reports, work programmes, and profit sharing.

What about marketplace sales?

Orders from multiple stores and platforms can be consolidated into one operational flow — that is what Growujil does, including pickups, shipping, returns, and receipt summaries by courier and platform.

Which payment gateway should we use?

It depends on per-transaction cost and what your customers actually use. Because the gateway layer is interchangeable, switching provider later does not mean rewriting the payment flow.

Services

Other services

Contact

Tell me what you need to build.

Tell me about the system you need to build, the people who will use it, and the work it has to support. WhatsApp is fastest; I reply to every message.

Based in Purwokerto, Central Java. Working with clients across Indonesia, remote or on site.

Start a project today.

Send a short brief and I’ll come back with scope, approach, and an honest timeline.