In this guide 6 sections
Industry specific software is built around the records one trade keeps, such as a garage job card or a bed ledger. A generic ERP handles items, invoices and ledgers well. It has no place for those records. You end up bending the trade into fields never meant for it.
What a generic ERP is built around
A general ERP starts from three things: an item, a party and an invoice. Stock moves in and out, a bill is raised, a ledger is posted, and at month end the owner reads a profit figure that matches the shelf. That is a trader’s whole story.
Many trades are different. A clinic sells a consultation, not a stocked item. A hostel sells a bed for a month, not a product off a shelf. The ERP can still print an invoice for either one, but the thing being sold has no home inside it, so staff invent one.
Three trades, three records an invoice system cannot hold
Take a garage. The centre of its day is the job card. It carries the registration number, the odometer reading, the complaint in the customer’s own words, the mechanic assigned, the parts fitted and a promised delivery time. An ERP has no such thing, so owners squeeze it into a free-text remarks box.
Take a paying guest house. The core record is the bed ledger, listing which bed, which tenant, the joining date, the deposit held, the rent due date and any notice given. Rent is a recurring claim against a bed. Vacancy is the report the owner reads each morning.
Take a chit fund. Every group has a fixed number of members, a monthly instalment, an auction, a discount bid and a dividend share. A generic ledger cannot even tell you who has already won the pot.
- Garage: job card, vehicle history, parts used, labour hours
- PG: bed ledger, deposit, notice period, vacancy
- Chit fund: group, auction month, bid, dividend, prized subscriber
- Clinic: patient visit, prescription, follow-up date
What a product built around the trade already holds
The records arrive in place. The garage version opens a job card from the registration number and shows the last three visits of that vehicle. Parts and labour then roll into the final invoice without anyone retyping a line.
Statuses come along too. A job card moves from booked to inspected, approved, in work, ready and delivered, and a bed is vacant, reserved, occupied or on notice. Your staff already say these words. Training is short.
Rules sit inside as well. A chit auction closes at a set hour, the winning bid fixes the dividend and the pot is released only after a surety is on file. Nobody has to build any of it.
Where the gap shows up in daily work
The first sign is a side spreadsheet. Someone keeps the real bed list in Excel because the ERP cannot show it, and a second person keeps vehicle history in a notebook. The ERP now holds half the truth.
The second sign is the monthly matching day. Two people compare the sheet to the system line by line, find small differences and argue over which one is right. The owner stops trusting either number.
The third sign is the report nobody can produce. Which rooms stayed empty longest? Which mechanic’s jobs get reopened most often? A system without the records cannot say.
- A side spreadsheet that staff update first
- Free-text remarks used as a database
- A day each month lost to matching two sources
- Reports that someone must build by hand
How to decide if you need one
Write down the five documents your staff handle every day, and the statuses each one passes through, then have the vendor open every document on screen. Faked in a note field? Weak fit.
A generic ERP is still the right call when your trade really is buying and selling items on simple terms. Do not buy a trade product only because it carries your trade’s name. Check the documents first and the label second.
Record gap worksheet
A worksheet with four columns. They name the document your staff handle, the statuses it passes through and where it is kept today. The last column says whether the system under review holds it natively, through a note field or not at all. Add one row per weekly report.
Open a blank worksheet to printQuestions owners ask
Is industry specific software always costlier than an ERP?
Not always. Ask each vendor for the full list of what is included and what needs custom work. A cheap ERP that takes months of adaptation can cost more in the end than a product that already holds your records.
Can a generic ERP be customised to hold a job card?
Yes, with development effort. A developer can add a job card form, its statuses and its reports. You then own that custom code, and every upgrade must keep it working.
What if my business spans two trades?
List the records from each trade and check which product covers the larger share. Some vendors let you add a second module. Others suit a single trade only.
Do I lose accounting features with a trade product?
Usually not. Most trade products post to a ledger or export to your accounting package. Confirm how invoice, receipt and payment entries reach your books before you sign.