On this page
- The short answer
- How you actually manufacture
- What triggers production
- Map the plan-to-produce lifecycle
- What makes manufacturing different
- Can a generic ERP work?
- The product: BOM or formula
- The work: routing and operations
- PLAN THE WORK
- Can this job actually start?
- Material requirement
- Capacity that changes the plan
- Release an executable order
- FOLLOW THE PRODUCTION RECORD
- Make WIP visible
- Move WIP without losing context
- STANDARD TIME ≠ ACTUAL TIME
- CAPTURE THE ACTUAL
- Expected vs actual material
- Output is not one quantity
- Planned vs actual output
- Yield from the real record
- Quality as an operating gate
- In-process rejection
- Rework preserves history
- Semi-finished and sub-assembly
- Batch or lot identity
- Job work inside the record
- Outside-processing cost
- Finished-goods receipt
- EXPECTED COST ≠ ACTUAL COST
- The overhead model
- EXPLAIN THE VARIANCE
- Commercial analysis
- Multi-plant production
- Barcode and scanning
- ERP, MES and connected systems
- The difficult scenarios
- Standard or custom?
- Red flags
- Evaluation record
- What customer proof?
- Evidence: Re-feel
- Evidence: Ambika Foods
- Evidence: ARCL
- How exactllyERP fits
- Checklist
- Go Deeper
One company may produce standard products to forecast. Another may manufacture only against confirmed customer orders. Some use discrete assemblies, some use batch or formula-based production, some work through job-shop or engineer-to-order processes, and many combine more than one model across different product families.
That is why an ERP should not be judged simply by asking whether it supports BOMs, production orders or costing.
The buyer needs to know whether the system can connect what the business intends to make with the material, capacity and process required to make it — and then capture what actually happened so management can explain the difference.
The useful question is not “Does your ERP support manufacturing?”
It is “Can you show us what we planned to make, whether the material and capacity were actually available, what we really consumed and produced, and why the final cost or output differed from plan?”
The short answer
A manufacturing company should evaluate ERP by following the complete production record.
A useful generic chain is:
- demand / customer order / forecast
- production requirement
- BOM / formula
- routing / operations
- material requirement
- capacity requirement
- production / work order
- material issue
- shop-floor execution / WIP
- actual machine and labour time
- actual consumption
- output / rejection / rework / scrap / by-product where applicable
- quality decision
- finished or semi-finished inventory
- actual production cost
- variance
- fulfilment / dispatch
Not every manufacturer uses every stage, and not every company uses these exact document names.
The important test is whether the proposed ERP can connect:
A module checklist alone cannot prove that.
First identify how you actually manufacture
Before comparing ERP vendors, define the production model or combination of models you actually use.
Possible operating models include:
These categories can overlap.
A company may make one product family to stock and another only against customer demand.
A plant may use discrete assembly in one area and batch or formula logic in another.
Do not force the whole business into one manufacturing label merely because the ERP vendor prefers one model.
Ask:
What actually triggers production in our business, and what production record must remain connected from planning through completion?
That answer should shape the evaluation.
Decide what triggers production
Production may begin because of:
The trigger matters because it changes how the ERP should relate demand, material, capacity and fulfilment.
A make-to-stock manufacturer may plan against expected demand.
A make-to-order manufacturer may need the production requirement connected directly to the customer order.
An engineer-to-order business may not know the complete production definition until engineering work is complete.
The buyer should therefore ask:
Show us what creates the production requirement in our business — not merely how a user manually creates a work order.
Confirmed exactllyERP capability includes production/work order generation from sales-order demand where required and from forecast/replenishment demand where required.
The buyer should still demonstrate the exact trigger and approval logic used by the plant.
Map the plan-to-produce lifecycle before choosing software
Do not begin with the ERP menu.
Begin with the real operating lifecycle.
At minimum, map the stages that apply to the business:
Then ask:
At which points can quantity, material, time, quality, cost or production status change?
Those are the points the ERP evaluation must test.
What makes Manufacturing ERP requirements different?
Manufacturing companies still need ordinary ERP capabilities:
The difference is in how these transactions connect to the production record that created them.
A material issue is not only an inventory transaction.
A labour entry is not only a time record.
A machine hour is not only a capacity figure.
A quality failure is not only a test result.
A job-work receipt is not only a purchase or stores transaction.
A finished-goods receipt is not only an inventory increase.
Each is part of the explanation of what the production order actually consumed, did, produced and cost.
So the buyer should not ask only whether the ERP has production, stores, quality and costing modules.
Ask whether the same production truth survives across them.
Can a generic ERP still be right for a manufacturer?
Yes.
A manufacturer should not choose industry-specific software merely because it carries a manufacturing label.
Some manufacturers have straightforward production models.
Some use specialist MES, machine-monitoring, planning, quality or maintenance systems around a broader ERP.
Some generic platforms may support the required manufacturing model through configuration, extensions or connected applications.
The decision should depend on what the critical workflows require.
Ask:
Which manufacturing concepts must the ERP understand directly?
Which can be configured?
Which should remain in MES, machine, quality or specialist systems?
Which require development or integration?
The label matters less than the evidence.
A claim of manufacturing depth should make the demonstration more demanding, not less.
Define the product: BOM or formula
The production definition should describe what material is expected to go into the product.
Depending on the business, this may involve:
Confirmed exactllyERP capability includes:
The buyer should test:
Which BOM or formula is valid for this production order, and how do we know we are using the correct version?
Do not accept a demonstration where the product structure exists but version, revision or effective use is unclear.
Define the work: routing and operations
what should be consumed
how the product should be made
The manufacturing definition may also need:
Confirmed exactllyERP capability includes:
The buyer should ask:
Can the system show what work should occur, in what sequence, using which resource and expected time?
A strong BOM does not compensate for weak operation control.
PLAN THE WORK
Production planning should answer more than:
“How much should we make?”
Depending on the plant, it may need to determine:
Confirmed exactllyERP capability includes MRP planning from demand/BOM while considering stock and pending quantities.
It also includes material requirement explosion automatically from BOM during planning/release.
The buyer should test:
Can the system translate demand into an executable production requirement rather than only a target quantity?
Can this job actually start?
A planned order is not necessarily a releasable order.
Before production starts, the business may need to know:
- Is the required material available?
- What is short?
- What is already on purchase order?
- What is expected from another production order?
- What capacity is available?
- Which machine/process is constrained?
- Which work centre is overloaded?
- Is the required manpower/resource available?
- What due date is at risk?
Confirmed exactllyERP capability includes:
The useful buyer question is:
Before we release production, can the ERP tell us what prevents this job from being executed as planned?
That is much more useful than a simple “production order created” message.
Material requirement should come from the production definition
The ERP should not make production planners rebuild BOM demand in spreadsheets.
Confirmed exactllyERP capability includes automatic material requirement explosion from BOM.
The buyer should test:
If the planned quantity changes, what happens to material requirement?
If the BOM/version changes, what happens to the requirement?
If stock already exists, what still needs to be procured or produced?
If supply is pending, how does the plan recognise it?
The material plan should remain connected to the production requirement.
Capacity should be specific enough to change the plan
Capacity cannot be useful if it is only a static number on a machine master.
Confirmed exactllyERP capability includes capacity planning at machine/process level.
The buyer should test a real constraint.
Take a production requirement that exceeds available capacity and show what the system does with the schedule or production decision.
Depending on the business, capacity may need to consider:
Do not assume every manufacturer requires minute-by-minute finite scheduling.
The evaluation should match the real planning need.
Release a production order that operations can actually execute
A production or work order should carry enough context to become an operational instruction.
Confirmed exactllyERP capability includes:
The buyer should ask:
What exactly becomes fixed when the work order is released?
Potentially:
The exact control should match the business.
FOLLOW THE PRODUCTION RECORD
This is one of the strongest tests in a Manufacturing ERP evaluation.
A possible production chain is:
- production requirement
- production/work order
- material issue
- operation 1
- WIP transfer
- operation 2
- actual time
- actual consumption
- quality decision
- output / rework / rejection / scrap
- finished-goods receipt
- actual cost
- variance
The exact stages differ.
The principle does not:
Can the ERP preserve one understandable production record from release through output and cost?
Production should not disappear into separate departmental records once material leaves stores.
Make WIP visible
Between raw-material issue and finished-goods receipt, value and material exist somewhere.
The buyer should be able to ask:
- What production is in progress right now?
- Which work order does it belong to?
- Which operation or stage has it reached?
- Which work centre or process currently holds it?
- What material or semi-finished output exists?
Confirmed exactllyERP capability includes:
WIP should be an operating state, not merely an accounting balance.
Move WIP without losing production context
A product may pass through several work centres or process stages.
Confirmed exactllyERP capability includes transfer of WIP/material between work centres/process stages.
The buyer should test:
When WIP moves from one operation or work centre to another, does the production identity remain intact?
The transfer should preserve:
Do not accept a workflow where each department recreates the production history.
STANDARD TIME ≠ ACTUAL TIME
Standard time
The routing tells the business what time an operation is expected to require.
Actual time
Execution tells the business what time it actually took.
Confirmed exactllyERP capability includes:
The buyer should ask:
Which operation took longer or shorter than expected, and where does that difference become visible?
The difference may affect:
Do not let the vendor demonstrate only standard routing times.
CAPTURE THE ACTUAL
A manufacturing system becomes useful when it records what actually happened.
Depending on the operation, actual execution may include:
Confirmed exactllyERP capability includes these operating records across material, time, output and production status.
The buyer should ask:
Which production facts are entered from the shop floor, which are derived automatically, and which are still reconstructed later?
The fewer critical production facts that depend on month-end reconstruction, the stronger the operating record.
Compare expected material with actual consumption
The BOM tells the business what material should be consumed.
The production record should show what was actually consumed.
Confirmed exactllyERP capability includes:
The buyer should ask:
Can we compare expected material consumption with actual consumption for this work order and explain the difference?
Over-consumption should not become an unexplained inventory adjustment.
Under-consumption should not disappear either.
The production record should preserve the reason where the business requires it.
Production output is not always one quantity
A production order may create more than one outcome.
Depending on the manufacturing model, output may include:
Confirmed exactllyERP capability includes output classification for usable, rework, scrap, by-product and yield-related production outcomes.
The buyer should ask:
Can the system explain what happened to the entire production quantity rather than recording only the good output?
Do not force every manufacturer to use every category.
Planned quantity and actual output should remain comparable
Confirmed exactllyERP capability includes planned production quantity versus actual output comparison.
The buyer should test:
If we planned 100 units and did not receive 100 usable units, where is the difference explained?
The answer may involve:
The exact categories depend on the operation.
The important point is that the difference should be explainable.
Yield should come from the real production record
Confirmed exactllyERP capability includes yield comparison from expected/BOM output versus actual production.
But there is no universal manufacturing yield formula.
For one operation, yield may mean usable output relative to expected output.
For another, it may involve material conversion.
For another, yield may not be the right KPI at all.
Ask:
Which yield matters in our production model, and can the ERP calculate it from the actual production record?
Do not introduce generic industry yield targets.
Quality should act as an operating gate
Manufacturing quality can occur at different stages.
Depending on the business, inspection may happen:
Confirmed exactllyERP capability includes quality hold/release affecting production or stock workflow and in-process rejection recording by operation/stage.
Ambika Foods also provides customer-specific evidence of item-specific incoming quality parameters and actual values recorded at receipt.
The buyer should ask:
Show us a quality failure and what it prevents from happening next.
A quality result is operational only if it changes what can be issued, processed, transferred, received or dispatched according to the business rule.
Record in-process rejection where it actually occurs
Confirmed exactllyERP capability includes in-process rejection recording by operation/stage.
That matters because a rejection discovered at operation 2 should not look identical to a rejection discovered at final inspection.
The buyer should ask:
Can we identify where the rejection occurred, what quantity was affected and what happened next?
Possible next states may include:
Do not assume every manufacturer uses the same disposition categories.
Rework should preserve the original production history
Confirmed exactllyERP capability includes rework through:
The buyer should test:
If output fails and is reworked, can we still see the original work order and the additional material, time and cost caused by rework?
Rework should not make the original production history disappear.
Otherwise the finished item may look normal while its real production cost and exception history are lost.
Keep semi-finished and sub-assembly production visible
Many manufacturers do not move directly from raw material to finished goods.
Confirmed exactllyERP capability includes:
The buyer should be able to ask:
What semi-finished material exists right now, which work order created it, where is it, and what production requirement will consume it next?
This is especially important when sub-assemblies are produced ahead of final assembly or shared across several finished products.
Keep batch or lot identity where the production model requires it
Not every manufacturer needs batch or lot traceability.
But where the product or process requires it, confirmed exactllyERP capability includes batch/lot traceability across relevant production and inventory stages.
The buyer should ask:
At which point is batch or lot identity created or inherited, and how far must it remain visible?
The Manufacturing guide should not turn this into a full Chemical or food traceability guide.
Those verticals may require much deeper treatment later.
Here, the point is simply that production identity must remain available where the manufacturing model requires it.
Keep job work inside the production record
Manufacturing often crosses the factory boundary.
Confirmed exactllyERP capability includes:
The buyer should ask:
When material leaves our plant for an outside process, can we still answer what was sent, what remains outstanding, what returned, what process occurred and what it cost?
Job work should not become a separate manual register that breaks the production history.
Make outside-processing cost part of the job
If a subcontract operation is required to complete production, its cost belongs to the production economics.
Confirmed exactllyERP capability includes job-work processing cost in production costing.
The buyer should test:
When outside processing is completed, where does the cost appear in the production order and actual finished cost?
A payable that exists only in finance but is not connected to production can weaken actual-cost analysis.
Receive finished goods against the production that created them
Confirmed exactllyERP capability includes finished-goods receipt against the originating production/work order.
The buyer should ask:
Which production order created this finished stock?
The receipt should preserve enough context to understand:
Finished stock should not appear as if it materialised independently of production.
EXPECTED COST ≠ ACTUAL COST
Expected cost
The manufacturing definition provides an expectation.
Actual cost
The production record provides reality.
Confirmed exactllyERP capability includes:
The buyer should ask:
Can management explain why this production order cost what it did using the material, time, output and overhead records that created the cost?
The useful comparison is not merely:
- standard cost
- vs
- actual cost
It is:
which operating differences caused the cost difference?
Include the overhead model that actually applies
Confirmed exactllyERP capability includes overhead treatment using methods such as:
where applicable.
Do not assume one universal overhead method.
The buyer should ask:
Which overheads should follow this production order, and what operational basis allocates them?
A costing model is useful only if finance and production agree on what the calculation represents.
EXPLAIN THE VARIANCE
Variance is not useful merely because the ERP prints a number.
The buyer should be able to understand whether the difference arose from:
Confirmed exactllyERP capability includes standard-versus-actual costing and variance.
The buyer should ask:
Can we trace the variance back to the production events that caused it?
That is the third part of the Manufacturing signature:
PLAN THE WORK. CAPTURE THE ACTUAL. EXPLAIN THE VARIANCE.
Connect actual production cost to commercial analysis where required
Confirmed exactllyERP capability includes sales-order/customer-order margin using actual production cost where required.
This can be useful in make-to-order, contract or customer-specific production environments.
But do not assume every manufacturer measures profitability at sales-order level.
The buyer should ask:
Where does actual production cost need to influence customer, order, product or management profitability analysis in our business?
The costing model should match the commercial model.
Multi-plant production should not fragment the production truth
Confirmed exactllyERP capability includes multi-plant production operations and multi-location raw material/WIP/finished-goods inventory.
The buyer should test:
- which plant owns the production order;
- where raw material is held;
- where WIP moves;
- which plant/process produces the semi-finished item;
- where finished goods are received;
- whether inter-location movement preserves production context.
Ask:
Can management see the complete manufacturing position without reconciling separate plant spreadsheets?
Multi-location is useful only if the production record remains coherent.
Barcode and scanning should support the workflow, not define it
Confirmed exactllyERP capability includes barcode/scanning support for relevant production and inventory workflows.
The buyer should not evaluate scanning in isolation.
Ask:
Which manual identification or movement step are we trying to control with scanning?
Possible uses may include:
Do not assume every plant needs barcode scanning everywhere.
The business process should determine the technology.
Decide what belongs in ERP, MES and connected systems
Not every shop-floor capability must live inside ERP.
A manufacturing environment may include:
The buyer should ask:
Which system owns the production order?
Which system owns machine events?
Which system owns actual labour/time?
Which system owns quality status?
Which information must return to ERP for costing and fulfilment?
What happens when the interface fails?
The aim is not to force every capability into one application.
The aim is to preserve one trustworthy operating record.
Make the vendor demonstrate the difficult manufacturing scenarios
Do not allow the Manufacturing ERP demonstration to become a tour of BOM, production-order and costing screens.
Give every shortlisted vendor the same difficult scenarios.
The point is not that every ERP should navigate identically.
The point is that every vendor should prove the same business outcome.
Record what is standard, configured, extended or custom
After every important manufacturing scenario, classify how the proposed result is delivered.
The proposed product supports the requirement as part of its normal capability.
The result depends on settings, masters, workflow or configurable behaviour.
Another application, MES, specialist system or integration forms part of the solution.
Development is required specifically for the requirement.
The claim remains proposed until evidence is provided.
None of these labels is automatically good or bad.
The buyer needs to know what will actually have to exist in production to reproduce the demonstration.
Manufacturing ERP red flags
The demo begins by manually creating a work order
The vendor has not shown how real demand creates production.
BOM is demonstrated but routing is not
The system knows what material is required but not necessarily how work is performed.
Material requirement ignores current stock or pending supply
The shortage picture may be misleading.
Capacity exists only as a static master value
The production plan may not actually use resource constraints.
Work order is released even though material or capacity is unavailable
The plan is administrative rather than executable.
WIP disappears after material issue
Management cannot identify what is in process or where it is.
Standard time exists but actual time is not captured
The business cannot explain operation-level time variance.
Actual material consumption is not compared with BOM expectation
Over- or under-consumption becomes invisible.
All non-good production output is called scrap
Rework, rejection, by-product and retained WIP may be lost.
Planned quantity and actual output do not reconcile
Production completion cannot be explained.
Quality results do not change stock or production status
Quality is reporting rather than operational control.
Rework creates a disconnected production record
The original manufacturing history and additional cost disappear.
Job work is managed in spreadsheets
Outside processing breaks the production record.
Job-work cost remains only in accounts payable
Actual production cost becomes incomplete.
Finished goods are received without originating production context
Inventory is disconnected from manufacturing history.
“Actual cost” is really the standard cost reposted
The system cannot explain what production actually cost.
Variance is shown as a number without operating cause
Management knows that performance differed but not why.
Multi-plant production requires manual consolidation
The manufacturing position is fragmented.
Barcode scanning is demonstrated as technology rather than workflow control
The tool is being shown without proving what operational problem it solves.
Customer proof is only a manufacturing logo
The reference does not reduce uncertainty about planning, execution, costing or variance.
A practical Manufacturing ERP evaluation record
For each critical manufacturing workflow, record the evidence.
| Evaluation area | What the buyer should establish |
|---|---|
| Manufacturing model | What triggers production and which production mode applies |
| Demand trigger | How forecast/customer order/replenishment becomes production demand |
| BOM / formula | Which product structure is valid |
| BOM version | How revisions/effective versions are controlled |
| Sub-assemblies | How multi-level structures and semi-finished production work |
| Routing / operations | How process sequence and standard time are defined |
| Work centre / machine | Which resource performs each operation |
| Skill / labour | How required labour/skill maps to production |
| Material planning | How BOM demand becomes material requirement |
| Current stock | How available inventory affects the requirement |
| Pending supply | How purchase/production supply affects shortage |
| Shortage | What prevents release |
| Capacity | How machine/process capacity affects plan |
| Production release | What becomes fixed when work starts |
| Material issue | How consumption is linked to work order |
| Material return | How excess/unused material is returned |
| Additional material | How extra consumption is recorded |
| WIP | Where production is now |
| WIP transfer | How production moves between work centres/stages |
| Standard time | What operation time was expected |
| Actual time | What machine/labour time actually occurred |
| Planned output | What production quantity was expected |
| Actual output | What was actually produced |
| Rejection | Where and why output/material failed |
| Rework | How additional work preserves original history |
| Scrap | How genuine scrap is classified |
| By-product | How applicable secondary output is recorded |
| Yield | How expected vs actual output is compared |
| Quality | How hold/release affects workflow |
| Batch / lot | How identity is preserved where required |
| Semi-finished inventory | How sub-assembly/WIP stock remains visible |
| Job work | What is sent, outstanding and returned |
| Job-work cost | How outside processing enters production cost |
| Finished-goods receipt | Which production order created the stock |
| Standard cost | How expected production cost is determined |
| Actual cost | How real production cost is accumulated |
| Unit cost | How actual cost per finished unit is derived where applicable |
| Overhead | Which allocation basis applies |
| Variance | Which operational cause explains the difference |
| Order/customer margin | How actual production cost is used where required |
| Multi-plant | How production operates across plants |
| Multi-location | How raw material/WIP/finished inventory remains visible |
| Barcode/scanning | Which workflow control it supports |
| Systems boundary | ERP/MES/quality/maintenance/HRMS ownership |
| Delivery method | Standard / configuration / extension / custom / not demonstrated |
| Follow-up | What evidence remains unresolved |
Do not turn this into a percentage score.
One unresolved critical planning, production-control or costing requirement can matter more than many minor feature matches.
What customer proof should a Manufacturing ERP vendor provide?
A useful customer reference is not simply another company that manufactures products.
Ask for proof closest to the uncertainty you are trying to remove.
If your concern is production planning, ask:
Which customer uses the ERP to translate demand into raw-material requirement and production planning?
If your concern is shop-floor execution, ask:
Which customer uses work centres, work orders, material issue, production entries and WIP/process transfers in the ERP?
If your concern is quality, ask:
Which customer records product/material-specific quality controls inside the operating workflow?
If your concern is job work, ask:
Which customer sends production material outside and keeps the outside process connected to the manufacturing record?
If your concern is costing, ask:
Which customer uses production costing and management reporting rather than reconstructing manufacturing economics separately?
Customer evidence should validate the difficult workflow.
Not decorate the proposal.
Relevant operating evidence: Re-feel
Re-feel provides useful evidence for manufacturing planning at operational scale.
Its Exactlly environment includes:
- raw-material requirement analysis;
- production planning;
- manpower allocation;
- operation across a product environment with more than 50,000 SKUs.
The strongest value of this proof is not the SKU count by itself.
The relevant evidence is that production planning, material requirement and manpower allocation are connected in the operating system.
That supports the buyer question:
Can demand become a material and production plan that operations can actually use?
Re-feel should therefore be read as planning evidence, not as a generic manufacturing logo.
Relevant operating evidence: Ambika Foods
Ambika Foods provides deeper plant-execution evidence.
Its confirmed Exactlly environment includes:
- process masters;
- work centres;
- resources and skills;
- BOM / production formulation;
- production orders / work orders;
- material issue;
- production entries;
- work-centre transfers;
- exception transactions;
- item-specific incoming quality parameters and actual values;
- batch management;
- job work;
- multiple warehouses.
The value of this evidence is the connected plant record.
The buyer can see how product definition, production instruction, material movement, work-centre activity, quality, batch control, job work and warehouse operations can belong to the same manufacturing environment.
This supports the central Manufacturing principle:
PLAN THE WORK. CAPTURE THE ACTUAL.
The buyer should still require the vendor to demonstrate the buyer’s own production route.
Customer proof supplements the demonstration.
It does not replace it.
Relevant operating evidence: ARCL
ARCL provides selective corroboration for manufacturing costing, finance and management reporting.
That evidence is useful here because the Manufacturing Buyer Guide must connect production activity to actual cost and management visibility.
ARCL should not be treated as the central manufacturing-process proof in this guide.
Its deeper chemical-production context belongs more appropriately in a future Chemical ERP Buyer Guide.
The relevant Manufacturing lesson is:
Production costing is more useful when the manufacturing record, finance and management reporting remain connected.
How exactllyERP fits into this evaluation
exactllyERP should be evaluated against the same difficult Manufacturing scenarios.
Do not ask Exactlly only:
“Do you have Manufacturing ERP?”
Bring the actual production model.
Include:
- demand trigger;
- make-to-stock / make-to-order / other production strategy;
- product/BOM/formula structure;
- BOM versions/revisions;
- sub-assemblies;
- routings/operations;
- work centres;
- machines/processes;
- standard times;
- manpower/skills;
- material-planning logic;
- pending supply;
- shortage rules;
- capacity constraints;
- work-order release;
- material issue/return;
- WIP stages;
- actual machine/labour time;
- actual material consumption;
- output classifications;
- yield;
- quality;
- rework;
- job work;
- costing;
- overhead rules;
- plants/locations;
- barcode/scanning;
- MES or other connected systems.
Confirmed exactllyERP Manufacturing capabilities
Confirmed current Manufacturing capability includes:
- MRP planning from demand/BOM with stock and pending quantities;
- multi-level BOM with sub-assemblies;
- BOM version/revision history;
- separate BOM/formula by product or variant where required;
- production/work order generation from sales-order demand where required;
- production/work order generation from forecast/replenishment demand where required;
- automatic material-requirement explosion from BOM during planning/release;
- material-shortage visibility before production release;
- pending purchase/supply considered in production material availability;
- routing/operations with standard time;
- machine/work-centre masters linked to production routing/operations;
- capacity planning;
- machine/process-level capacity planning;
- production manpower/resource allocation planning;
- skill/labour resource mapping to work centre/process where required;
- stage/operation-wise WIP tracking;
- current production/work-order stage/status visibility;
- WIP/material transfer between work centres/process stages;
- planned production quantity versus actual output comparison;
- material issue against production/work order;
- material return/excess return against production/work order;
- additional/ad-hoc material issue or consumption adjustment against production where required;
- actual machine/process time capture;
- labour/time capture;
- operation-wise timesheet entry;
- in-process rejection recording by operation/stage;
- quality hold/release affecting production or stock workflow;
- rework through the same work order or a linked rework work order where appropriate;
- finished-goods receipt against the originating production/work order;
- semi-finished/sub-assembly production and inventory;
- job-work material issue, outstanding quantity and return reconciliation;
- job-work processing cost included in production costing;
- production costing by work order/production order;
- standard cost from BOM/routing or maintained separately;
- actual production cost;
- actual cost per finished unit where applicable;
- standard-versus-actual costing and variance;
- output classification including usable output, rework, scrap, by-product and yield-related outcomes where applicable;
- yield comparison from expected/BOM output versus actual;
- overhead allocation through fixed amount, percentage, machine-hour, labour-hour and operation-wise methods where applicable;
- sales-order/customer-order margin using actual production cost where required;
- batch/lot traceability where applicable;
- multi-plant production operations;
- multi-location raw material/WIP/finished-goods inventory;
- barcode/scanning support for relevant production/inventory workflows.
These capabilities should still be demonstrated against the buyer’s actual manufacturing model.
The relevant questions remain:
What are we supposed to make — and when?
Can material, capacity and process actually support that plan?
What did we actually consume, do, produce and cost?
Why did actual performance differ from expectation?
The right implementation is the one that can answer those questions from the production record itself.
Manufacturing ERP Evaluation Checklist
Manufacturing model
Product definition
Routing / operations
Demand / planning
Capacity
Production release
Material issue / return
WIP
Time / labour
Output
Quality
Rework
Job work / subcontracting
Finished-goods receipt
Costing
Variance
Commercial analysis
Multi-plant / multi-location
Barcode / scanning
Integration / coexistence
Vendor evidence
The buyer is evaluating the ERP as an operating system for the real production lifecycle rather than as a list of manufacturing modules.