Walk into an engineering shop that supplies a Tier-1 and ask the planner what they are making next week. In a pump shop or a fabrication unit you would get an answer based on order book and capacity. Here you get a different answer: they open a spreadsheet that was emailed to them, scroll to the current week, and read out a number that somebody else decided.
That spreadsheet is the release schedule, and it is the single most important document in the building. It is also, in most Indian SME ancillary units, the document that lives furthest from the ERP. The system holds items, stock and invoices. The schedule sits in an inbox, gets copied into a planning sheet by hand, and gets revised on a Friday afternoon by a customer who does not consider that a change of plan.
This piece is about what changes when you take that seriously — the parts of an ERP an auto-ancillary shop genuinely needs beyond the standard kit, the Indian compliance layer that sits on top, and a rollout order that does not fall apart at the first schedule revision. If you want the shorter product-level view, our ERP for auto component and ancillary makers page covers the feature side; this is the operational reasoning behind it.
The order isn’t an order — it’s a schedule
A conventional ERP has a clean mental model. A customer sends a purchase order for a quantity by a date. You plan, you make, you despatch, you invoice against that order, and the order closes. Nearly every system on the market is built around that loop.
Automotive supply does not work that way. Your customer sends a rolling release: a forward view covering weeks or months, in which the nearest period is firm and committed, the middle is planned but revisable, and the far end is a forecast that exists so you can buy long-lead material. Then they send it again next week, with different numbers.
Two failure modes follow, and both are common enough to be predictable. The first is the system that treats every incoming release as a new sales order. Demand accumulates, MRP sees three overlapping orders for the same part in the same month, and you buy for a quantity nobody asked for. The second is the system that overwrites the previous release with the new one. That is arithmetically tidier, and it destroys the only record that matters when a customer says you were told about this quantity in May — because you no longer have the May version.
What you actually need is for the schedule to be a first-class object with a version history: each revision stored, the firm horizon marked, and the difference against the previous revision visible. When a release moves 4,000 pieces from October into September, the planner should be able to see that as a change, not infer it by comparing two spreadsheets.
The firm horizon is not just a planning convenience. It is usually the commercial boundary in your supply agreement — the window in which material committed on the customer’s instruction is recoverable if they cut the quantity. If you cannot demonstrate what the schedule said when you bought, that clause is difficult to invoke. The version history is a commercial record, not an audit nicety.
Six things a generic ERP gets wrong here
Most of what an auto-ancillary unit needs is ordinary manufacturing software. These six are where the generic product runs out.
1. Planning that consumes a schedule, not an order
MRP has to explode the release through your multi-level BOM and net it against everything already committed — finished stock, work in progress, material sitting at a job worker, and open purchase orders — then re-run when the release is revised. The re-run is the hard part. A system that plans well once but requires a planner to manually reconcile after every revision will get abandoned, because revisions are weekly and the reconciliation is the job you were trying to remove.
2. Lot genealogy in both directions
Almost every ERP claims traceability. In practice most implement the backward direction: given a despatched part, show me where it came from. That answers an auditor’s question. It does not answer the expensive one.
The expensive question is forward: a heat number has been flagged, or a plating batch has failed adhesion testing — which finished parts contain it, and which of my customers already have them? The answer determines whether you sort 300 pieces at your own gate or send a team to a customer plant to sort 30,000. A system that cannot walk the genealogy forward leaves you guessing, and guessing in that situation always means over-scoping the containment.
3. Rejection and rework as a reported number
Your customer measures you in parts per million defective, and asks for the figure. If rejection is recorded on inspection registers at the machine and totalled monthly by someone with a calculator, three things happen: the number is late, it cannot be broken down by cause, and it quietly excludes whatever was reworked and passed — which is precisely the cost you most need to see.
Rejection has to be captured at the operation, with a reason code, against the lot. Then PPM by part, by customer and by cause is a report you run, and rework cost stops being invisible.
4. Costing that starts from weight
A machined component begins life as bar, forging or casting bought by weight and ends as a piece sold by number. Between the two sits turning scrap, and scrap has a recovery value that belongs in the part cost. Shops that cost purely on issued weight overstate their cost; shops that ignore process yield understate it. Both quote badly.
The system needs the conversion — input weight, expected yield, scrap recovery — sitting in the routing rather than in the estimator’s head. Our guide to metal weight calculation covers the arithmetic, and the weight calculator is the quick version.
5. Job work treated as your stock, elsewhere
Heat treatment, plating, grinding, induction hardening: material leaves your premises, stays yours, and comes back changed and usually short. Two things break in a spreadsheet. Planning cannot see the material, so it gets ordered again. And process loss — 1,000 pieces out, 986 back — is absorbed silently instead of being measured against a norm you agreed with the processor.
Under GST this is also a filing obligation. Goods sent for job work move on a delivery challan, are expected back within the prescribed period, and the quantities have to reconcile for the ITC-04 return. Our job work and ITC-04 explainer covers the compliance mechanics in full.
6. Customer-owned tooling that isn’t yours
Dies, fixtures and gauges supplied or funded by your customer sit in your plant but are frequently not your asset. They still need a record: where the tool is, how many shots or pieces it has run, when it was last refurbished, and who owns it. Most SME ERP implementations either capitalise these by accident or keep them nowhere at all — and then cannot answer the tooling section of a customer audit.
Supplying an OEM on spreadsheets?
OEMup is a manufacturing ERP built for Indian SMEs — schedule-driven planning, multi-level BOM and MRP, lot and serial traceability, rejection and rework tracking, job-work despatch, GST e-invoice and e-way bill, inventory, HRMS and accounting in one system.
Book a Demo →What “traceability” means when your customer audits you
Traceability is the word that gets used most loosely in this segment, so it is worth being concrete about what has to exist.
Identity is created at the gate, not in the quality department. When material is received, the supplier’s lot, heat or batch number has to be recorded against that receipt — because from that moment on, everything downstream can only reference an identity that already exists. This is the single most common reason traceability projects fail after the fact: the shop wants to add trace in year two, and discovers that eighteen months of receipts have no lot identity to trace to.
From there, the chain is: receipt lot → issue to a manufacturing order → operations, machine and operator → inspection result → job-work batch out and back → finished lot → despatch document → customer. Each link has to be a record the system creates as a by-product of normal work. If any link requires someone to remember to write something down separately, that link will be the broken one when it is tested.
No ERP makes a factory IATF 16949 compliant. Certification is about a quality management system, its documented processes and its evidence. What software changes is the cost of producing evidence: a trace report you can generate on demand versus three days of somebody cross-referencing registers before an audit. Treat any vendor claiming their product makes you compliant as a vendor who has not read the standard.
Generic ERP vs what an ancillary shop needs
| Requirement | Typical generic ERP | What an auto-ancillary unit needs |
|---|---|---|
| Customer demand | Discrete sales order, closed on despatch | Versioned rolling release with a firm horizon and revision history |
| Replanning | Manual re-run, planner reconciles by hand | MRP re-nets automatically when the release changes |
| Traceability | Backward trace from a despatch, if lots are enabled | Forward and backward genealogy, including job-work batches |
| Quality | Rejection recorded as a stock adjustment | Rejection and rework by operation and reason code, PPM by part and customer |
| Costing | Standard cost per piece | Weight-in, yield, scrap recovery, rework cost in the part cost |
| Job work | Stock written off on despatch, or ignored | Your stock at a processor’s premises, challan-reconciled for ITC-04 |
| Tooling | Fixed asset or nothing | Customer-owned tool register with usage and refurbishment history |
| Despatch | Invoice | Invoice plus e-invoice IRN and e-way bill, tied to the traced lot |
The India-specific layer
On top of all of that sits compliance that a globally-designed ERP will handle awkwardly or not at all.
E-invoicing and e-way bills on every despatch. Automotive supply is high-frequency — often daily or several times a week to the same customer plant. That turns e-invoice generation and e-way bill creation from an occasional task into a routine one, and any friction in it is multiplied by despatch frequency. It needs to happen from the despatch document, not as a separate portal visit. Our e-invoice guide walks through the mechanics.
ITC-04 and the job-work clock. Material sent out for processing has to come back within the prescribed period, and the movement has to be reportable. In a shop where half the part numbers go out for heat treatment or plating, this is not a quarterly clerical task — it is a stock control problem that happens to have a filing deadline attached.
Section 43B(h) and your own suppliers. Ancillary units sit in the middle: paid on the OEM’s terms, buying from smaller vendors who are frequently MSME-registered. The 45-day payment rule applies to what you owe them regardless of when you get paid, so MSME status has to be captured against the vendor and visible when payments are planned. See our explainer on the 45-day rule for the consequences of finding out at year end.
Shift-based payroll. Two- and three-shift operation with overtime is normal in this segment, and attendance feeding payroll directly matters more than in a single-shift shop. Our factory payroll guide covers PF, ESI and the attendance side.
Five mistakes worth avoiding
Mistake 1 — Modelling releases as purchase orders
The most consequential design decision, and it is usually made by accident during implementation because the ERP has a sales order screen and the schedule has to go somewhere. Every revision then either duplicates demand or erases history.
Instead: insist on a delivery schedule object with revisions, a firm horizon, and a visible diff against the previous version.Mistake 2 — Turning on lot tracking “later”
Lot identity is created at goods receipt. Deferring it to phase two means that when phase two arrives, there is nothing to trace — the receipts that would have carried the identity are already history.
Instead: capture supplier lot, heat or batch at receipt from day one, even before the quality workflow is configured.Mistake 3 — Letting job-work stock leave the books
If material despatched to a processor disappears from stock, planning re-orders it and your physical verification never reconciles. If it stays at full quantity with no process-loss handling, the shortfall surfaces as an unexplained adjustment months later.
Instead: hold it as your stock at the processor’s location, with expected return quantity and an agreed loss norm.Mistake 4 — Measuring rejection only at final inspection
Rejection found at final inspection has already absorbed every operation’s cost. Recording it only there tells you the PPM but not where the money went, and makes it impossible to distinguish a machining problem from a raw material one.
Instead: capture rejection at the operation, with a reason code, so cost and cause are attached to the same record.Mistake 5 — Building BOMs for every part before going live
An ancillary shop with 400 part numbers usually ships most of its volume on 40 of them. Attempting a complete BOM master before go-live is how implementations stall for a year, by which time the schedule format has changed anyway.
Instead: build accurate BOMs for the parts carrying your volume, go live on those, and extend. See our multi-level BOM guide for how to structure them.A rollout order that survives the next revision
The sequence matters more than the timeline, because each step depends on the one before being reliable.
Lot identity at goods receipt
Before anything else, and regardless of what else is configured. Record the supplier lot, heat or batch on every incoming receipt. This is cheap on day one and impossible to backfill.
Item and BOM masters for the parts that carry your volume
Including bought-out items and the job-work stages, because a BOM that omits the plating step will produce an MRP plan that omits the plating lead time. Accuracy on 40 part numbers beats coverage on 400.
One customer’s schedule, versioned
Load a single OEM or Tier-1 customer’s current release and then run the next revision through the system. The revision is the test. If the second release is painful to load, you have found the problem while it still affects one customer.
MRP against that schedule, in parallel first
Let MRP net the release against stock, work in progress, material at job workers and open purchase orders — then compare its buy list against what your planner would have bought, for two cycles, before anyone acts on it. Disagreements in that window are almost always master data errors worth finding.
Rejection capture on the floor
Move rejection and rework recording to the operation where it happens. PPM by part and customer becomes a report at this point, and the monthly reconstruction from inspection registers stops.
Job work into the same stock ledger
Last, because it depends on lot identity and BOM stages already being right. Once material at processors is visible to planning and reconcilable against challans, the ITC-04 return becomes an export rather than an exercise.
When you don’t need most of this
Worth stating plainly. If you supply the aftermarket rather than an OEM line, sell against discrete purchase orders, and are not asked for lot traceability or PPM reporting, then you are running an ordinary engineering job shop and most of this article is overhead you can skip. What you need is a standard manufacturing ERP — BOM, MRP, stock, costing, GST — and our MRP explainer is a better starting point.
The moment it changes is when your first customer sends a schedule instead of an order, or asks for a trace report. Both tend to arrive with the first serious OEM or Tier-1 relationship, and both tend to arrive with less notice than you would like. The shops that handle it well are usually the ones that had lot identity at goods receipt before anybody asked for it.
The bottom line
What makes auto-component manufacturing distinct is not the parts. It is that the planning calendar, the quality evidence and the payment terms are all set outside your building, and your systems have to absorb that without a person in the middle reconciling spreadsheets.
Practically, that comes down to a short list. The customer’s schedule lives in the system, with its history. Planning re-runs when the schedule moves. Every lot can be traced in both directions. Rejection is captured where it happens. Material at a job worker is still your material. And the compliance layer — e-invoice, e-way bill, ITC-04, MSME payment terms — falls out of the transactions instead of being assembled afterwards.
Get those, and the weekly release revision becomes a recalculation instead of a crisis.
FAQ
What ERP features do auto component manufacturers actually need?
Beyond standard manufacturing ERP: schedule-driven planning rather than order-driven, MRP that re-plans on schedule revision, forward and backward lot genealogy, rejection and rework capture by operation with PPM reporting, job-work tracking reconcilable for ITC-04, and a customer-owned tooling register.
Why does a purchase-order-based ERP struggle with OEM schedules?
Because a release is not an order. Modelled as repeated orders it duplicates demand and MRP over-buys; modelled as an overwrite it loses the record of what was committed when. The schedule needs to be a versioned object with a firm horizon.
What does traceability actually mean for an auto component supplier?
Both directions. Backward, from a despatched part to its material lot, operations and inspections. Forward, from a suspect heat or plating batch to every finished part and customer despatch containing it. The forward direction decides how wide a containment has to be, and it is the one most systems cannot do.
How should heat treatment and plating job work be handled?
As your stock at the processor’s premises. It moves on a delivery challan under the GST job-work provisions, is expected back within the prescribed period, and despatched versus received quantities have to reconcile for ITC-04 — with process loss measured against an agreed norm rather than absorbed silently.
Does an ERP make you IATF 16949 compliant?
No. Certification covers a quality management system, its processes and its evidence. An ERP lowers the cost of producing that evidence by making records a by-product of normal work, so a trace report can be generated rather than reconstructed. It does not substitute for the system itself.
Should a small ancillary unit start with ERP or with quality software?
Start with material and lot control, because traceability cannot be added retrospectively — identity is created at goods receipt. Then schedule-driven planning, then rejection and PPM reporting, which depends on the first two being reliable.
How long does an ERP rollout take in an auto component shop?
It depends far more on master data readiness than on software. The sequence in this article is roughly a three- to four-month arc for a single-plant SME that limits initial BOM scope to its high-volume parts. Attempting a complete BOM master before go-live is the most reliable way to turn that into a year.
Related reading
- ERP for Auto Component & Ancillary Makers — the product view of everything above
- Job Work and ITC-04 — the compliance mechanics for heat treatment, plating and grinding
- Multi-Level BOM: The Complete Guide — how to structure BOMs that MRP can actually explode
- MRP Explained for Indian Manufacturers — the planning engine behind schedule-driven buying
- MSME 43B(h) and the 45-Day Payment Rule — what you owe your own vendors
- 5 Things Tally Cannot Do That a Manufacturing ERP Can