Electronics & PCB · ERP vs Excel
Excel vs ERP for electronics manufacturing: when spreadsheets stop being enough
Many PCB assembly and harness plants run on spreadsheets, and some run well. This is where the sheets start to struggle in an electronics plant, and what changes when the record is made at the station instead.
By Nexfloe · · 6 min read
- Industry:
- Electronics & PCB
- Article type:
- ERP vs Excel
Most electronics plants start with spreadsheets for good reasons. BOMs arrive from engineering as Excel files, purchase works from a shortage sheet, stores keeps a stock sheet, and quality has a workbook for test results. Everybody knows Excel, and it costs nothing extra.
The question is not whether Excel is good or bad. It is at what point the plant needs more than a set of separate files can reliably hold, and in electronics that point tends to come earlier than in other assembly work, because the BOMs are longer and change more often.
Quick answer
Excel works in an electronics plant while BOMs are short, one person owns the plan and customers rarely ask for a trace. It gets hard to rely on when boards carry hundreds of lines, ECNs arrive often, several people edit the same files, shortages are found at kitting and OEMs ask which component lot went into a batch. An ERP with shop-floor recording keeps one live record instead of several copies.
Where Excel works well in an electronics plant
- Quotation costing, where one engineer prices a BOM and nobody else edits it.
- Comparing BOM revisions line by line when an ECN arrives.
- One-off analysis: a defect Pareto from test failures, a supplier price check, a line balance.
- A small plant with a handful of products, one planner and customers who rarely ask for records.
- Reports built from data exported out of a system.
Where do spreadsheets become difficult?
Long BOMs and frequent revisions
A board with 250 lines is manageable in a sheet. Ten boards, each with two or three live revisions and alternates on many lines, is not. When an ECN arrives, every sheet that copies the BOM (shortage, kitting, costing) has to be updated, and one that is missed builds to the old revision.
Shortages found at kitting
Whether an order can start depends on every line: stock, what other orders have taken, part reels still on the line, and open purchase orders. Working that out across sheets is slow, so the short part is usually found when stores tries to pull the kit and the line is already waiting.
Component lots after they leave stores
The stock sheet may record the supplier lot at receipt. Once the reel is on a feeder, or the wire spool on a cutting machine, the sheet has no way of knowing which job it went into. The trace stops at the stores door.
Test results and crimp checks
Functional and continuity test results end up on the tester, on printed sheets or in a workbook. Crimp heights are written on a setup sheet. None of it is tied to the batch, so finding the results for one shipment means searching by date and hoping the dates line up.
Rework
Boards that fail test go to the rework bench, get fixed and go back through. A sheet seldom records the fault, the fix and the re-test against the batch, so nobody can say how many boards were reworked last month, for which fault, or what it cost.
Answering an OEM trace
An OEM trace joins the delivery note to finished lots, component lots, operators and test results. In spreadsheets each of those is in a different file, and some are on paper. SMX Enterprises, a wiring harness maker in Bengaluru, ran its traceability on Excel sheets updated by hand, a day or two behind production, and a trace meant hours of cross-referencing. With lot genealogy built as production happens, the same request now takes under three minutes.
Spreadsheets and ERP compared, task by task
| Task | In spreadsheets | In a manufacturing ERP |
|---|---|---|
| Applying an ECN | Update every sheet that copies the BOM | New revision on the BOM; released orders keep the revision they were built to |
| Checking a kit before release | Compare BOM, stock and purchase sheets line by line | Each line checked against stock by lot and open orders, with the short line named |
| Knowing which lot went into a batch | Not recorded once parts leave stores | Lots issued to the work order and linked to the finished lot |
| Production status | Counts reported after the shift | Counts, rejects and downtime recorded at the station during the shift |
| Test and crimp records | Tester files, setup sheets or a separate workbook | Results on the batch, with the operator and time; a failure holds the batch |
| Rework | Often not recorded | Rework operation on the order, with the fault and the re-test |
| OEM trace | Assembled from several files and registers | One search on the finished lot |
An ERP is an operational system, not a bigger spreadsheet
The difference is where the data comes from. The test register is written up once the batch has already left the bench. A manufacturing ERP with shop-floor recording is filled in as the work happens: stores issues a reel to the order, the operator logs the count at the SMT line, the tester records pass or fail before the batch moves on. Reports are read from those entries, not compiled at month end.
That is also why moving BOMs and purchasing into an office ERP, while leaving the floor on paper, often disappoints. The sheets that hurt most in an electronics plant are the ones about component lots, tests and rework, and an ERP without floor recording leaves them where they are.
When should an electronics manufacturer move from Excel to ERP?
There is no plant size at which Excel must go. The useful test is how often the files fail to give a current answer you can trust. These are the triggers electronics and harness plants most often describe.
- Several people edit the same files. Planning, purchase, stores and quality each keep a copy, and one is always out of date.
- More than one line runs at once. An SMT line, a manual assembly line and a harness section cannot be followed from one sheet.
- ECNs arrive often. Keeping every sheet on the right BOM revision has become somebody's full-time job.
- Shortages are found at kitting. The line waits for a part the sheet said was in stock.
- Component lots cannot be followed. Nobody can say which reel or wire lot went into last week's batch.
- Production updates arrive late. Counts reach the office the next morning, so the plan runs on yesterday's position.
- Test and crimp records are kept by hand. Results sit on paper or on the tester, not with the batch.
- Rework cannot be counted. The rework bench is busy, but its work is not on any order.
- Customers are asking for more. A new OEM wants lot traceability, test records or serial numbers that cannot be produced quickly.
- WIP is unknown. Finding how many boards sit between SMT and test, or at the coating vendor, needs a walk round the floor.
None of these means Excel has failed. They mean the plant has grown past what separate files can hold. Two or three together usually mean the files cost more time than a system would. The guide to implementing ERP in an electronics plant covers what the move involves.
Keeping what works
Your engineers can keep their BOM comparison workbooks. Quotation costing, BOM comparisons and defect analysis can stay in spreadsheets, using exports. What moves is the operational record: orders, BOM revisions, stock by lot, production, test and dispatch. In FleekERP that record sits on the work order, with inventory and lot traceability and quality control on the same lot, and the books stay in Tally or Zoho.
For how component lots, test results and the trace run on one record, see FleekERP for electronics and wiring harness makers.
Frequently asked questions
Can a PCB assembly plant run on Excel?
A small one can, with short BOMs, one planner and customers who rarely ask for records. It gets harder as boards grow to hundreds of lines, ECNs arrive often, several people edit the files and OEMs ask which component lot went into a batch.
Why do component shortages show up so late when planning in Excel?
Because checking an order means comparing every BOM line with stock, other orders' allocations, reels still on the line and open purchase orders across separate sheets. That is slow, so the short part is usually found when stores pulls the kit.
Can test results be kept in a spreadsheet?
They can be stored, but they are rarely tied to the batch or unit. Finding the results for one shipment then means searching by date. In a manufacturing ERP the result is recorded on the batch at the test operation, with the operator and time.
Do we have to stop using Excel after moving to an ERP?
No. Quotation costing, BOM comparisons and defect analysis can stay in Excel using exports. The operational record of orders, revisions, stock by lot, production, test and dispatch moves into the system.