Custom ERP software for your operations

An ERP is a set of modules that share the same records. A purchase updates stock, stock movements update the ledger, and payroll posts to the same accounts the finance team closes each month. The value comes from those links, not from any single screen.

These are the modules I scope most often, and how they depend on each other:

• Accounting: chart of accounts, journals, general ledger, payables and receivables. Every other module posts here.
• Procurement: purchase requests, approvals, purchase orders and supplier records.
• Inventory and warehousing: goods receipt, stock levels, transfers between locations and valuation.
• HRM and payroll: employee records, attendance, leave and payroll runs that post salary costs to accounts.
• CRM: leads, customers and sales activity linked to invoicing.
• Operations modules specific to your business, such as POS, bookings, shipments or memberships.

Packaged ERPs work well when your processes match the way the software expects you to work. They get expensive and awkward when your core operation is unusual: a club that also runs restaurants and rooms, or a courier business where the shipment, not the invoice, is the central record. In those cases the package is bent around your business with customisation that is hard to maintain.

A custom ERP is built around your central record and your approval rules, and you own the code. The trade-off is that it is designed and built for you, so it needs a clear scope. If a standard package fits most of your needs, I will tell you that during scoping.

The Membership Club & Restaurant ERP connects membership and subscriptions, rooms and events, POS and kitchen, recipes and inventory, procurement, warehousing, HRM, payroll and the general ledger. A cargo and courier ERP I built centres on shipment booking, terminal operations, dispatch, rider workflows, proof of delivery and audit trails. Both case studies show how operations modules feed one set of records.

The Enterprise Business ERP on the work page is a product concept for multi-company management, HRM, CRM, procurement, inventory and accounting. It shows how I would structure a modular platform; it is not a delivered system.

Most ERP risk sits in the data you already have: opening balances, item masters, supplier lists, employee records and open orders. Migration is scoped as its own piece of work, with a test import, a reconciliation against your old figures and a final cut-over.

Phases usually start with accounting and the module causing the most pain, then extend outwards. Each phase has a written scope and a fixed price and goes live before the next one starts.