Custom ERP Development in Bangladesh

The practice

We start from how you already work, not from a module list.

Every business has a handful of rules that are not written down anywhere. How a jute mill values a batch that came off the line under weight. How a bookshop prices a used textbook taken in exchange. How an event company bills a shoot that ran two days longer than the contract. Those rules are the business. They are also the first thing a packaged ERP asks you to abandon.

So we do not begin with software. We begin in the office, with the people who keep the registers, and we write down what actually happens — including the steps nobody admits to in a meeting. That document is the specification. The ERP is built to match it, and where a rule is genuinely wrong we say so before we encode it, rather than after.

The result is a system that the people who use it recognise on the first day, because the screens are named for the things they already say out loud. Adoption stops being a training problem. That is the whole argument for building rather than buying, and it is why we have never shipped the same ERP twice.

What it is Custom ERP, built per business
Built from Mirpur, Dhaka, Bangladesh
How we start On site, with the people who keep the records
After go-live We stay on the system for years

Industries we have built ERP for

Jute manufacturing
Apparel & textiles
Book retail & exchange
Photography & event management
Hospital cardiology
Healthcare platforms
Wholesale & distribution
Field service

Why custom

What a packaged ERP costs you here.

Off-the-shelf ERP is the right answer for plenty of companies. It stops being the right answer at the point where the licence fee is the smallest number in the project, and these are the four reasons that happens.

The configuration becomes the project

A package that fits eighty per cent of a business still needs the other twenty per cent bent into shape. That work is usually larger, slower and more fragile than building the twenty per cent properly in the first place.

Staff go back to the register

If the screen does not match the job, people keep a private notebook and enter the system later, or not at all. Within a quarter the ERP holds a tidy version of events and the real numbers live somewhere else.

The cost never stops

Per-seat licensing in foreign currency, paid annually, for modules a mill in Rajbari will never open. A system you own has a build cost and a support cost, both of which you can see.

Your data is not yours to query

When the report you need is not one of the four hundred that shipped, you are back to exporting to Excel. A system we build runs on a schema you hold, on infrastructure you control.

What we build

One core, then the modules your business actually runs on.

Every ERP we deliver has the same spine: master data, permissions, approvals and an audit trail. What sits on top of that spine is different every time, and is decided by what the business does rather than by what we have built before.

The core — in every system we build

The parts that are not negotiable, because without them an ERP becomes an expensive way to store data that nobody trusts.

Master data

One record for a customer, a supplier, an item, an employee, a branch. Everything else in the system points at these rather than repeating them.

Roles & permissions

Who may see a cost price, who may approve a purchase, who may reopen a closed month — enforced by the system, not by an understanding between colleagues.

Approvals & workflow

The chain a document travels before it counts: raised, checked, approved, posted. Each step stamped with a person and a time.

Audit trail

Every change to a figure kept with its old value, its new value and who made it. Questions about last quarter get answered from the system.

Reports & exports

The reports the business asks for, plus Excel and PDF from every list on screen, so nobody has to ask us for a one-off extract.

Documents & attachments

Challans, invoices, contracts and photographs filed against the transaction they belong to instead of in a shared drive.

Operations — the modules that move goods and work

Chosen per client. A jute mill and a bookshop share perhaps a third of this list, and the third they share does not behave the same way.

Inventory & warehouse

Stock by location, batch and unit, with receipts, issues, transfers, adjustments and a physical count that reconciles rather than overwrites.

Purchase & procurement

Requisition, quotation comparison, purchase order, goods received note and the three-way match against the supplier bill.

Sales & orders

Quotation to order to delivery to invoice, with customer pricing, discount rules and credit limits applied where the order is taken.

Production & jobs

Bills of material, work orders, batch output, wastage and the per-unit cost that falls out of the run — for a mill floor or for a photography job.

Delivery & logistics

Dispatch, challans, vehicle and rider assignment, proof of delivery, and returns that go back into stock at the right value.

CRM & after-sales

Leads, follow-ups, complaints and service visits held against the customer record, so the history is there when they call.

Money and people

The half of an ERP that the owner reads. It is built last and specified first, because everything upstream has to post into it correctly.

Accounts & general ledger

Chart of accounts, vouchers, journals, trial balance and the statements, with entries posted automatically by the transactions that caused them.

Billing & receivables

Invoices, ageing, collections and customer statements, so an overdue account is visible before it is a problem.

Payments & payables

Supplier bills, payment scheduling, cash and bank books, and reconciliation against the bank statement.

HR & attendance

Employee master, leave, shifts and attendance captured once, from a device or a register, and read straight by payroll.

Payroll

Salary structures, overtime, deductions, advances and a monthly run that can be reversed and reprocessed instead of edited.

Costing & profitability

What a batch, a job, a branch or a product line actually earned once its own costs are carried against it.

Client projects

Six ERP systems, in the order they were built.

Each of these started the same way and ended somewhere different. The dates are the working life of the engagement, not the length of the build.

2018

NorthKing — photography & event management

Our first ERP. An event company whose product is a day that cannot be repeated: bookings, crew and equipment assignment, shoot scheduling, post-production hand-offs, client deliverables and billing against a package that almost always changed after signing. Job costing was the point — until then nobody knew which kind of event actually made money.
2018 – 2024

Booktionary — book retail, exchange & fulfilment

Six years on one system for a bookshop founded by AUST students in 2015 and now selling across Bangladesh. A catalogue of thousands of titles with publishers, authors, editions and bindings; stock across formats; the used-book exchange that makes the business distinctive, with its own valuation and grading rules; orders, delivery, returns and the accounts underneath. Built and extended continuously until 2024.
2019 – 2021

Dekko Isho Group — apparel manufacturing

An ERP for one of the larger apparel groups in the country, where a single style order runs through cutting, sewing and finishing across lines and shifts. Materials and trims against the bill of material, work-in-progress by process, wastage, output by line, store issues and the costing that tells management what an order earned once it shipped.
2021 – 2023

Rajbari Jute Mill — jute manufacturing

Raw jute is bought by grade and by bale, loses weight to moisture, and comes out of the mill as goods that have to be costed back to the batch that produced them. The system covers procurement and grading, godown stock, batch production and output, wastage, sales and dispatch, and a ledger that reflects what the mill actually made rather than what was budgeted.
2021 – 2023

United Hospital — cardiology department

A clinical records system for a heart failure department, built around the workflow rather than around the paperwork: patient registration and history, NYHA staging, investigations and ECG and echo results, prescriptions with comparison and approval between consultant and paramedic, scheduled follow-up calls with reminders, and over fifty reports covering demographics, medication and outcomes. Five user roles, each seeing only what its role should.
2025 – running

MediKing — healthcare platform

In build now. A platform connecting patients with doctors, hospitals and diagnostic labs across all sixty-four districts: doctor and chamber profiles by specialty and location, appointment booking, video consultation, prescription and health record storage, lab test booking and separate registration paths for patients, doctors and hospitals — with the settlement and reporting back office behind it.

How they are built

Chosen so somebody else could maintain it.

We support these systems for years, and in a few cases we will not be the last people to touch them. So the stack is deliberately ordinary, the schema is normalised, and the rules that change are data rather than code.

Application

PHP
Laravel
Blade
REST APIs
Queued jobs

Data

MySQL
Normalised schema
Transactional posting
Audit tables
Scheduled backups

Interface

Bootstrap
jQuery
React
Barcode & label printing
Excel & PDF export

Controls

Role-based access
Approval chains
Change log
Period locking

Rules live in configuration

Rates, grades, discount bands, approval limits and costing formulas are data an administrator can change. A policy decision should not need a release.

Nothing is corrected by overwriting

A wrong posting is reversed by a document that says so. Stock counts, payroll runs and journals are versioned, so the history stays honest.

Every figure traces back

Any number on a report opens into the transactions that produced it, and those open into the person and the moment they were entered.

What clients get

One system that agrees with itself.

The registers go away
Stock, sales, production and payroll stop being four separate records kept by four people who each believe theirs is the right one.
Staff recognise the screens
Because the system is named for the work, training is short and the private notebook does not survive the first month.
Costing becomes a fact
What a batch, an order or a job earned is produced by the system from its own data, not assembled at month end from memory and a spreadsheet.
You own the software
The source, the schema and the server are yours. No per-seat licence in foreign currency, and no renewal that decides your budget for you.
It keeps changing with you
New branch, new product line, new statutory report — the system is extended rather than worked around. Six years on one of these is not unusual for us.
Questions get answered
When an owner, an auditor or a customer asks how a figure was arrived at, the trail is on screen in a few clicks.

After go-live

The build is the short part.

An ERP earns its cost in the years after it is delivered, which is why we stay on them. Booktionary ran with us for six years, Catalyst Chem is under contract with us until 2027, and MediKing is in active build now. Handover is the point where the relationship starts, not where it ends.

See our ready-made systems

Change requests New requirements specified, built, tested and released against the running system.
Upkeep & security Framework and server updates, backups that are checked, and fixes that do not wait for a release window.
Someone who knows it Support from people who built the system, available around the closes and the month ends that matter.

Outgrown your spreadsheets and your package? Tell us what your business does that the software you looked at could not handle. We will tell you honestly whether it needs a custom ERP, what that would take, and what it would cost.

Talk to us about it +880 1327-422480

An ERP is the shape of your business, written down.