Do you need an ERP to run a job shop?
The question usually arrives after a quoting mistake or a missed delivery. An ERP is one answer. It is rarely the first one worth paying for.
The short answer
5 things that decide this
- 01Most job shops under about 100 people do not need an ERP. The pain that sends them ERP shopping lives in three places: scheduling, shop-floor travelers and job costing.
- 02Roughly half of manufacturers still run spreadsheets or paper alongside their main system, according to Weever's manufacturing research. Buying a bigger system has not removed the spreadsheets. It moved them.
- 03An ERP earns its keep when you need consolidated financials across sites, formal MRP for deep bills of material, or customer mandates like EDI that smaller tools cannot meet.
- 04Job shop ERP implementations regularly run six to twelve months with outside consultants before the first useful screen, a pattern fabrication forums document in detail and Eziil's industry writing confirms.
- 05The cheaper path is to digitise the three documents your shop already trusts: the quote, the traveler and the schedule board. Keep QuickBooks for the ledger.
The pain has three names, and none of them is ERP
Ask the owner of a 30-person machine shop why they want an ERP and you get concrete answers. Nobody knows which jobs are on the floor right now. Quotes get built from memory instead of from what the last similar job actually cost. A traveler goes missing and a rush order sits behind three jobs that could have waited.
None of those problems needs purchasing modules, HR modules or a new general ledger. They need a live schedule everyone can see, work orders that capture time at each station, and cost data that flows back into the next quote. That is a much smaller build than an ERP, and it is the part an ERP does worst out of the box.
Signals you need an ERP, and signals you do not
| Your situation | ERP? | Why |
|---|---|---|
| One site, under ~100 people, QuickBooks ledger works | No. | Your gaps are scheduling, travelers and costing. Those are point systems, not a platform. |
| Quotes built from gut feel, margins unknown until year end | No. | Job costing needs captured floor time, not a finance suite. |
| Multiple plants that must close books together | Yes, or getting close. | Consolidated financials across sites is genuine ERP territory. |
| Deep multi-level BOMs with purchased sub-assemblies | Probably. | Formal MRP is the one thing spreadsheets and light tools cannot fake for long. |
| A customer mandates EDI or flow-down quality records | Sometimes. | The mandate can also be met with targeted integration work at a fraction of the footprint. |
Digitise the documents the shop already trusts
A job shop already has a working system. It is written on paper travelers and a whiteboard, and one person in the office holds it together. The move that pays fastest is not replacing that system. It is giving it a database: the traveler becomes a digital work order, the whiteboard becomes a schedule board every station can see, and the times people already write down become job costs.
Built this way, the shop keeps QuickBooks, keeps its process, and gets live answers to the two questions that started the ERP conversation: where is every job, and what did the last one really cost. If a genuine ERP need arrives later, you walk into that project with clean structured data instead of shoeboxes, which is the single biggest predictor of a sane implementation.
- 01Start with one cell or one product line, not the whole floor.
- 02Capture time where work already stops: at the station, on a tablet, in seconds.
- 03Feed actual costs back into quoting within the same month you start capturing them.
What shop owners ask next
01What does a job shop actually need instead of an ERP?+
Three connected pieces: a live schedule board, digital travelers that capture time per station, and job costing that feeds the next quote. Keep your existing accounting system as the ledger. This covers the daily pain at a fraction of an ERP's footprint.
02When does an ERP become unavoidable?+
Multi-site financial consolidation, formal MRP for deep bills of material, and hard customer mandates such as EDI are the honest triggers. If none of those applies, the ERP conversation is usually a scheduling and costing conversation wearing a bigger badge.
03Can we connect a custom shop-floor system to QuickBooks?+
Yes, and that is the standard shape of this build. Job costs, invoices and purchase data sync to the ledger while the floor runs on screens designed for your travelers. The accounting system stays the system of record for money.
04We already bought an ERP and the floor ignores it. Now what?+
This is common, and the fix is rarely ripping it out. A thin layer that captures floor data in the way your operators already work, then writes clean records back to the ERP, recovers most of the value. The ERP keeps the books while the floor finally gets screens built for it.
Related
- Manufacturing software development →What we build for plants and job shops, and the constraints that shape it.
- Manufacturing work →Plant telemetry and floor systems we have shipped.
- Build vs buy software →The decision framework, applied honestly to both sides.
- Custom software development →Software built for one business and kept running after launch.
