A custom ERP is built around the workflow that makes a business different: hire periods for a rental firm, job costs for a contractor, intercompany trades for a trading house. The ten examples below are illustrative composites, not client case studies. Each shows the core workflow, the modules usually built, the integrations kept, and why a packaged ERP tends to struggle.
Use them to recognise your own operation. Most organisations will see themselves in one or two and borrow ideas from several. If you do, our custom ERP software page explains how such a system is scoped and built in phases; groups with several companies should also look at enterprise resource planning for groups.
What do custom ERP systems have in common?
They share a finance core and differ in the operational centre. Almost every example below has ledgers, receivables, payables, purchasing and reporting. The difference is the one or two modules where the business makes or loses money, and those are what justify a custom build.
A pattern repeats: keep proven products for commodity functions (payroll, sometimes the ledger), build the distinctive operation, and connect the two cleanly.
1. Wholesale distributor
Core workflow: customer-specific price lists, rebates, multi-warehouse stock, picking and delivery routes.
Modules built: order management with pricing rules, warehouse stock by location and batch, pick-pack-dispatch, delivery scheduling, rebate accruals.
Kept and integrated: accounting package, e-commerce storefront, courier services.
Why packages struggled: layered pricing and rebate agreements that differ per customer group. See our guide to ERP for distribution companies.
2. Small manufacturer
Core workflow: make-to-order production with bills of materials, routings and batch traceability.
Modules built: BOMs and routings, production orders, shop-floor time capture, batch tracking from raw material to dispatch, costing.
Kept and integrated: accounting package, payroll, label printers.
Why packages struggled: variant-heavy products and a costing method finance wanted to keep. Our manufacturing ERP software page covers this sector.
3. Construction contractor
Core workflow: cost and revenue tracked by job, phase and variation, with valuations and retentions.
Modules built: job costing, subcontractor orders, valuations and applications for payment, retention tracking, site timesheets on mobile.
Kept and integrated: accounting package, payroll, document storage.
Why packages struggled: general ERPs treat projects as a side module; the contractor's whole business is the project.
4. Multi-site clinic group
Core workflow: central purchasing and finance with site-level stock of consumables and practitioner scheduling.
Modules built: central procurement with site requisitions, consumable stock per site, practitioner time and commission, management reporting by site.
Kept and integrated: the clinical or patient record system, which stays separate; accounting; payroll.
Why packages struggled: the operational record was clinical, not commercial, and the group needed ERP to sit beside it, not replace it.
5. School group
Core workflow: fee billing, instalments and discounts across several campuses, with central purchasing.
Modules built: fee schedules, instalment plans, sibling and staff discounts, campus-level budgets, central procurement, approval chains.
Kept and integrated: the student information system, payment gateway, accounting.
Why packages struggled: fee rules and discounts unique to each school, and campus budgets controlled centrally.
6. Trading house
Core workflow: buying and selling goods across several entities and currencies, with shipments, landed costs and letters of credit.
Modules built: shipment tracking, landed cost allocation, intercompany trades with automatic mirror entries, multi-currency margin reporting, bilingual documents where needed.
Kept and integrated: banks, freight forwarders' updates, accounting per entity.
Why packages struggled: intercompany volume and margin-by-shipment reporting. Intercompany controls and eliminations need designing up front.
7. Equipment rental company
Core workflow: assets out on hire by serial number, by day or week, with deposits, damage checks and maintenance windows.
Modules built: availability calendar, hire contracts, check-out and check-in with photos, damage charging, maintenance scheduling, utilisation reporting.
Kept and integrated: accounting, payment gateway, telematics where fitted.
Why packages struggled: most ERPs sell stock once; rental firms sell time on the same asset repeatedly.
8. Logistics operator
Core workflow: consignments, vehicles, drivers and proof of delivery, with costs and revenue per trip.
Modules built: booking and consignment management, trip planning, driver mobile app with proof of delivery, fuel and vehicle costs, customer billing per consignment.
Kept and integrated: accounting, tracking devices, customer portals.
Why packages struggled: revenue and cost per trip rather than per item sold.
9. Franchise network
Core workflow: franchisor supplying stock and services to independently owned outlets, with royalties and performance reporting.
Modules built: franchisee ordering portal, royalty calculation, outlet performance dashboards, central supply and stock.
Kept and integrated: outlets' point-of-sale systems, accounting.
Why packages struggled: the franchisor needs a view across businesses it does not own, with strict separation of each franchisee's data.
10. NGO or charity
Core workflow: grants and donor funds tracked by project, with restrictions on how each fund can be spent.
Modules built: fund and grant tracking, project budgets, procurement with donor-specific approval rules, donor reporting packs.
Kept and integrated: accounting, donor CRM, payroll.
Why packages struggled: restricted-fund rules and donor report formats that differ per funder.
How do these examples compare?
| Example | Distinctive module | Usually kept as a package | Hardest integration |
|---|---|---|---|
| Distributor | Pricing and rebates | Accounting | E-commerce orders |
| Manufacturer | Production and traceability | Accounting, payroll | Shop-floor capture |
| Contractor | Job costing and valuations | Accounting, payroll | Site timesheets |
| Clinic group | Site procurement and stock | Clinical system | Clinical system boundary |
| School group | Fees and instalments | Student information system | Payment gateway |
| Trading house | Shipments and intercompany | Accounting per entity | Banks |
| Rental company | Asset availability and hire | Accounting | Telematics |
| Logistics | Trips and proof of delivery | Accounting | Tracking devices |
| Franchise | Franchisee portal and royalties | Outlet POS | Outlet POS data |
| NGO | Restricted funds | Accounting, CRM | Donor reporting |
What patterns can you borrow from these examples?
Even if your business is not on the list, five patterns recur and are worth copying:
- Model the thing you actually sell. A rental firm sells time on an asset, a contractor sells progress on a job, a logistics operator sells a trip. When the core record matches what you sell, reporting by margin follows naturally.
- Keep commodity functions in packages. Payroll, and often the general ledger, are mature products. Integrating with them is usually cheaper and safer than rebuilding them.
- Put the portal on the same data. Distributors, franchisors and school groups gain most when customers, franchisees or parents see the same records staff see, not a copy.
- Make approvals configurable. Limits, approvers and delegation change as organisations grow. Store them as settings administrators can change.
- Design for entities early. A second company, branch or country is much easier to add when the data model expected it from the start.
Which features change by market?
The workflows above are similar across countries; the documents, taxes and languages around them are not. Typical differences:
| Market | Features that often need attention |
|---|---|
| UK | Digital links to the product that files VAT returns under Making Tax Digital; integration with payroll software that reports to HMRC; bank payment files |
| UAE and Gulf | Arabic and English documents, right-to-left layouts, several entities and currencies, VAT-ready invoices and readiness for electronic invoicing |
| US | Sales tax that varies by state and locality, often handled by a specialist tax service; multi-state entities; integration with US payroll providers |
Treat this as a checklist of questions, not as tax advice. Rates, thresholds and filing rules change, so confirm current requirements with your advisers and the relevant tax authority, and make sure tax codes and document formats are configuration rather than hard-coded values.
Which modules do these systems build first?
Most start with the distinctive module plus whatever it needs to produce trustworthy numbers. A rental firm starts with availability and hire contracts; a contractor starts with job costing. Finance integration usually comes in the first phase so management can trust the output from day one. Our guide to which ERP modules to implement first explains the sequencing.
How do you turn an example into a plan?
Use this checklist to translate a relevant example into your own scope:
- Name the workflow where you make or lose money
- List the records it depends on (assets, jobs, shipments, funds)
- List what you will keep as packaged software, and why
- Map every integration, including direction and frequency
- Identify the two or three modules that would prove the system works
- Note the reports management needs from day one
- Decide who owns process decisions in the business
When is a custom ERP not the answer for these businesses?
A custom ERP is not the answer when a mature sector package already fits. Several of the sectors above have specialist products, and some organisations will be well served by them. It is also not the answer when the distinctive workflow is small enough to sit in a simple app beside a standard ERP. Compare honestly; our explainer on bespoke ERP covers when to avoid going bespoke.
How to start
Pick the example closest to you and rewrite it with your own processes, systems and reports. Our software requirements brief template turns that into a brief a supplier can quote against. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, usually the distinctive module and its finance link. Discuss the project when you have your draft.