```json { "title": "Shop-Floor Production Tracking for Engineering & Auto Component Units Using ERPNext", "url": "https://aavatto.com/blog/production-planning-software-engineering-manufacturing-erpnext/", "datePublished": "2026-10-21", "dateModified": "2026-10-21", "language": "en-US", "description": "Production planning software for engineering manufacturing, tied to shop-floor tracking in ERPNext. A practical guide for auto component SMEs.", "author": "Aavatto", "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support" } ``` # Shop-Floor Production Tracking for Engineering & Auto Component Units Using ERPNext If you run an auto component or engineering unit, the plan in the office and the reality on the floor rarely match by Wednesday. Production planning software for engineering manufacturing is only useful if it closes that gap: the schedule drives the floor, and what happens on the floor updates the schedule. **Short answer:** Production planning software for engineering manufacturing turns customer orders into work orders, material requirements and machine loads, then tracks each operation on the shop floor as it happens. In ERPNext, that loop runs through the Production Plan, Work Orders and Job Cards, so the plan and the floor share one record. This guide explains how that loop works, how much tracking an SME actually needs, and where outside job work tends to break it. ## What production planning software for engineering manufacturing actually has to do Generic planning tools assume a simple flow: order in, make product, ship. Auto and engineering component units don't work that way. A few things make them harder: Multi-level BOMs A finished bracket or shaft assembly depends on machined sub-parts, bought-out items and sometimes castings or forgings. Each level has its own lead time. Long routings One part may pass through turning, milling, drilling, deburring, heat treatment, grinding and inspection. A delay at any operation pushes everything after it. Job work in the middle of the routing Plating, heat treatment or powder coating often happens at a vendor's premises, then the part comes back for further operations. Changing customer schedules Tier-1 and OEM customers revise delivery schedules often, and the plan has to absorb those revisions without starting over. Rejection and rework Parts that fail inspection need to be recorded against the operation where they failed, not just written off at the end. So the software's job is two-way. Planning pushes work down to the floor. Tracking pulls actual progress, time and rejections back up so the next plan starts from reality. ## How the plan-to-floor loop runs in ERPNext ERPNext handles this with a chain of linked records. Each one does a specific job, and the value comes from them being connected. StageERPNext recordWhat it does on the floorDemandSales Order or Material RequestCaptures what the customer needs and by whenPlanningProduction PlanExplodes the BOM, lists sub-assemblies, raises Work Orders and material requestsProcess definitionBOM with Operations, Routing, WorkstationDefines which operations happen, in what order, on which machine group, at what hourly costExecutionWork OrderAuthorises production of a quantity and reserves materialOperation trackingJob CardOne per operation: operator, time logs, completed quantity, process lossQualityQuality InspectionRecords in-process or final inspection against a templateStoppagesDowntime EntryRecords machine downtime and the reasonStock movementStock EntryMoves material to WIP and books finished goods The Job Card is where shop floor tracking actually happens. When an operator starts and stops an operation, the time log records it. When they finish, they enter the good quantity and any loss. That single record feeds cost (actual time × workstation rate), progress (which operation the order is on) and quality (where rejections happened). ## How granular should shop-floor tracking be? This is the question most implementations get wrong, usually by tracking too much too soon. A small machining unit does not need the same data as an OEM plant. Pick the level that matches the decisions you actually make. LevelWhat you recordGood forCost of doing it1. Order-levelWork Order started and completed, total quantityKnowing which orders are lateVery low; supervisor updates once a shift2. Operation-levelJob Card per operation with completed and rejected quantityFinding bottleneck operations, rejection by operation, WIP by stageModerate; someone must close each Job Card3. Operator/machine-levelStart/stop time logs per operator, downtime reasonsTrue cost per part, machine utilisation, operator efficiencyHigh; needs discipline, a floor terminal or scanning, and ideally machine data Most auto component SMEs get the biggest return from moving from Level 1 to Level 2. That's where production tracking for auto components starts answering the questions owners ask every day: where is this order, which operation is holding it, and where are we losing parts. Level 3 is worth it on your bottleneck machines, the CNCs or grinders that limit output, but rarely across the whole floor on day one. If operators are asked to log time on every operation before the habit exists, the data becomes fiction within weeks and people stop trusting the system. *If you're unsure which level your floor is ready for, that's a useful first conversation to have before configuring anything.* ## Where job work breaks the tracking chain Outside processing is where many engineering units lose visibility. A batch of machined parts goes out for plating on Monday. On Thursday, the customer calls, and nobody can say how many are at the vendor, how many came back, or how many were rejected there. ERPNext handles subcontracting through Subcontracting Orders and Subcontracting Receipts, which track material sent to the vendor and finished quantity received back. The gap appears when job work sits *in the middle* of a routing. The part leaves after operation 4 and returns for operations 5 to 7. Getting that right usually means designing the BOM structure deliberately, often treating the pre-job-work part as its own item, so the outgoing and returning stock is traceable. It's a design decision made during implementation, not a setting you switch on later. Units that skip it end up tracking vendor WIP in a spreadsheet next to the ERP, which defeats the purpose. ## Native ERPNext vs. what usually needs a custom layer Being clear about this upfront saves a lot of frustration later. ### Handled natively in ERPNext: Multi-level BOMs with operations and routings Production Plans that explode sub-assemblies and raise Work Orders Job Cards with time logs, completed quantity and process loss Workstation hourly costing and capacity planning against working hours Quality Inspection templates, including in-process checks Downtime Entry with reasons Subcontracting Orders and Receipts Batch and serial number tracking ### Usually needs configuration or a custom Frappe layer: A simplified shop-floor screen, so operators see only their Job Cards with large start/stop buttons, rather than the full desk interface Barcode or QR scanning of a printed traveller card to open the right Job Card Rejection reason codes and rework loops that match your specific inspection practice Capturing machine signals (cycle counts, run/idle status) automatically, which needs hardware and integration work Customer schedule imports from OEM portals in their specific formats None of the custom items are unusual for a Frappe team to build, and building them as a separate app keeps them clear of the core so upgrades stay manageable. They do add scope, so it's better to decide which ones you actually need than to assume all of them. ## A practical rollout sequence Clean up BOMs and routings first If operations, sequence and workstations aren't defined correctly, every Job Card downstream is wrong. Define workstations honestly Group machines the way you actually plan them, with realistic working hours and hourly rates. Start at Level 2 on one product family Get Job Cards closed consistently for a few weeks before extending. Add in-process quality checks at known problem operations not everywhere. Design job-work flows into the BOM especially for mid-routing processes. Add Level 3 time tracking on bottleneck machines once Level 2 data is trusted. Only then consider machine integration when you know which signals you'd actually act on. ## Frequently Asked Questions [Is ERPNext enough, or do we need a separate MES?](#collapse-8691) For most engineering and auto component SMEs, ERPNext's Work Orders, Job Cards and quality records cover what a basic MES would do. A dedicated MES becomes relevant when you need high-frequency machine data, detailed OEE analytics or regulated traceability at a depth your customers audit directly. [Does ERPNext do finite capacity scheduling?](#collapse-8692) Partly. ERPNext's capacity planning schedules operations against workstation working hours and flags overlaps. It is not an advanced planning and scheduling (APS) optimiser that re-sequences the whole floor automatically. Many SMEs find it sufficient; units with very complex constraints sometimes add custom scheduling logic. [Will operators without computer experience actually use it?](#collapse-8693) They will if the screen is simple. The standard interface is built for office users. A stripped-down floor view with scanning and large buttons makes a big difference, and it's usually one of the first customisations worth doing. [How long does it take to set up shop floor tracking?](#collapse-8694) There's no single timeline. It depends mostly on how clean your BOMs and routings are today, how many product families you have, and how much job work sits mid-routing. A phased start on one product family is usually faster than trying to go live across the floor at once. ## Where to go from here If your plan and your shop floor are still running on separate spreadsheets, the first step isn't software selection. It's deciding how much tracking your floor can realistically sustain and where job work sits in your routings. We're happy to go through that with you. [Book a free ERPNext consultation](/services/tailored-erpnext-implementation/) and we'll look at your current BOM structure, routing and tracking level, and outline what a practical ERPNext setup would involve, including what would need a custom layer. You can also browse our [case studies](/case-studies/) to see how we've approached manufacturing implementations.