Skip to content
Industry reportsAll articles

Manufacturing ERP Software: Modules, ISA-95 & 2026 ERP Cost

Manufacturing ERP is the system of record that ties planning, the shop floor, inventory, and costing together. Here are the modules, how it integrates with MES and machines, discrete vs process differences, and when to build instead of buy.

Artem Zaitsev
Artem ZaitsevCTO · Idealogic
Author: Artem ZaitsevPublished: Updated: Reading time: 22 minHow we write →
On this page
Idealogic guide to how manufacturing ERP works and how it is built

Manufacturing ERP software is the system of record that ties a plant's planning, shop floor, inventory, and costing into one set of numbers. It carries the finance, sales, and purchasing that any business runs on, and adds the parts a factory needs: the bill of materials, the routings, the material plan, shop-floor costing, lot traceability, and quality. When it works, everyone is arguing from the same data. When it doesn't, the warehouse, the planners, and finance each keep their own version and none of them agree.

If you're evaluating ERP for manufacturing, the build-or-buy question comes before the vendor shortlist, and that's the decision this article is written for. It walks the modules and how they connect, then spends most of its time on how the ERP integrates with the execution layer and the machines below it, which vendor pages rarely cover. That integration layer, governed by ISA-95, causes more trouble on manufacturing ERP projects than the choice of suite.

The short version

  • Manufacturing ERP is the system of record that ties planning, the shop floor, inventory, and costing to one set of numbers, adding the bill of materials, routings, MRP, costing, traceability, and quality that a generic ERP has no concept of.
  • The category splits into discrete and process manufacturing: discrete tracks countable units built from a bill of materials and routing, process tracks materials mixed by a formula in batches with yield, potency, and shelf life, and many real plants run both as mixed-mode.
  • The hardest and most-skipped piece is the MES-to-ERP integration, the ISA-95 (IEC 62264) level 3 to level 4 interface where the ERP sends work orders down and the execution system sends confirmations, actuals, and genealogy back up.
  • Buy and configure a standard suite where your processes match the industry norm, and build custom only for the differentiating core; most plants land on a hybrid of a standard ERP backbone with custom execution and machine-data layers.
  • Cost and timeline scale with scope, from $18K for an MRP architecture sprint and $45K to $85K for a shop-floor B2MML sidecar up to $170K to $340K+ for multi-entity platforms. Panorama Consulting's 2015 ERP Report put the average ERP implementation at 15.7 months.
  • Implementations fail on data, scope, and people far more than on software: dirty bills of materials and routings, over-customization, and weak change management are the recurring causes.

What manufacturing ERP actually is

Enterprise resource planning is a suite of modules sharing one database, so a number entered once (a received quantity, a confirmed operation) updates everywhere instead of being re-keyed into separate systems. The category has a manufacturing pedigree: ERP grew directly out of material requirements planning and its successor MRP II, and its supply-chain process model maps onto the classic SCOR model from ASCM (Plan, Source, Make, Deliver, Return, and Enable). The current SCOR Digital Standard reorganizes those into Orchestrate, Plan, Order, Source, Transform, Fulfill, and Return. That lineage is why a generic ERP and a manufacturing ERP are not the same product wearing different labels.

A manufacturing ERP is the suite plus the modules a plant cannot run without: the bill of materials that says what a product is made of, the routings that say how it is built, an MRP engine, work-order and shop-floor costing, lot and serial traceability, quality management, and B2B supply-chain messaging such as ASC X12 EDI 830 planning schedules and 856 advance ship notices. A distribution-focused ERP can take an order, hold stock, and invoice, but it has no concept of a routing or a yield. The manufacturing question is whether the suite can model how your product is built, and keep inventory, cost, and order status honest as work moves across the floor.

It also helps to say what an ERP is not. It isn't the execution layer that runs the floor in real time, nor the controls that hold a machine to its setpoints. Suites like SAP, Oracle, or NetSuite are broad by design, and the temptation is to stretch one to cover everything; the plants that stay sane keep the ERP as the financial and planning backbone and let purpose-built layers handle execution and machine data.

The modules of a manufacturing ERP, and how they connect

A manufacturing ERP is easier to understand as a chain than as a feature list. Each module hands data to the next: a bill of materials feeds the material plan, the plan releases orders, orders run on the floor and report back, the confirmations feed costing and inventory, and quality can stop the flow at any point.

It starts with master data. The bill of materials is the recipe of components and quantities; the routing is the ordered list of operations and the work centers that run them, with setup and run times. Get these wrong and every downstream number is wrong. From the BOM and routing, MRP explodes demand into dated buy-and-make proposals, and scheduling turns that infinite-capacity proposal into a finite, executable sequence. The chain then reaches the floor and returns: shop-floor control confirms operations and feeds costing, which absorbs actual labor, material, and manufacturing overhead into work-in-process and finished goods under FASB ASC 330, the US GAAP inventory standard (IFRS plants use IAS 2), and books variances against standard. Inventory updates as material is consumed and goods received (a discipline we cover in manufacturing inventory software), and quality management aligned with ISO 9001, whose 2026 edition replaced ISO 9001:2015 in September 2026, can hold an order or quarantine a lot before it moves on (our quality management software guide has the detail). The table below sets out what each module owns and hands downstream.

ModuleWhat it ownsWhat it hands downstream
Bill of materialsWhat a product is made of, by component and quantityMaterial structure to MRP and costing
RoutingOrdered operations and the work centers that run themCapacity demand to scheduling, steps to the floor
MRPMaterial requirements from BOM, inventory, and lead timesDated buy and make proposals
SchedulingReleased work sequenced against finite capacityAn executable order sequence to the floor
Shop-floor controlLive status as operations are confirmedConfirmations and actuals to costing and inventory
CostingActual labor, material, and overhead versus standardVariances to finance
InventoryStock balances and finished-goods receiptsOn-hand positions back to MRP
Quality managementInspections, holds, and non-conformancesDisposition that gates material movement

Discrete vs process manufacturing ERP

The deepest split in the category is how the product is defined, which matters more than vendor or industry. It sorts plants into discrete and process worlds with different data models. Picking a suite built for the wrong one is a common and expensive mistake, because a suite built for the other world can't represent the thing you make.

Discrete manufacturing builds distinct, countable units from a bill of materials and a routing: pumps, circuit boards, vehicles, aircraft parts. The model thinks in part numbers, assemblies, and often serial numbers, and the central questions are which components went into which unit and which operations it passed through.

Process manufacturing mixes or transforms materials by a formula or recipe: food, chemicals, pharmaceuticals, paint. Here the model has to carry realities a discrete model has no slot for. Catch-weight items are priced and stocked by actual weight rather than a fixed each, so a single "case" varies. A single run yields co-products and by-products, not one clean output. Yield is planned and variable rather than assumed at 100 percent. And batch and lot traceability, with potency and shelf life as first-class attributes, is central and often a regulatory requirement. NIST's smart manufacturing program covers the integrated planning and control systems that sit on top of this model.

DimensionDiscrete manufacturingProcess manufacturing
Product defined byA bill of materials and routingA formula or recipe
Unit of outputCountable units, part numbers, serialsBatches measured by weight or volume
Central attributesWhich components and operations went into each unitYield, potency, shelf life, co-products and by-products
TraceabilitySerial and part genealogyBatch and lot genealogy, often a regulatory requirement
Typical industriesPumps, circuit boards, vehicles, aircraft partsFood, chemicals, pharmaceuticals, paint

Mixed-mode plants that run both models

The practical complication is mixed-mode: plants that make material in batches and then pack it as discrete units, such as a beverage maker that brews by recipe and yield, then fills and cases countable SKUs. One suite has to hold both worlds, and the seam between them, where a batch becomes a set of discrete units carrying that batch's genealogy forward, is where packaged data models strain and a custom layer often earns its place.

Where MRP fits, and where it stops

MRP (material requirements planning) is the calculation that explodes the bill of materials against inventory, open orders, and lead times, then proposes what to buy and what to make. It's a module inside the manufacturing ERP, not an alternative to it, and that relationship trips up more evaluations than it should. MRP came first, grew into MRP II in the 1980s by adding capacity and cost, and was absorbed into ERP in the 1990s, which is why nearly every ERP ships an MRP engine in the box. Where it stops matters just as much: classic MRP assumes infinite capacity, plans in buckets rather than a runnable sequence, and is only as good as the floor feedback it reads, so a nightly run on stale stock replans yesterday's plant. Closing those gaps is the work of finite scheduling and advanced planning, which we treat fully in our production planning software breakdown rather than rehashing here.

The MES-to-ERP integration layer

The MES-to-ERP interface is the Level 3 to Level 4 boundary of ISA-95, where the ERP's plan meets the system that runs the floor. An ERP plans and a manufacturing execution system executes: two systems with two data models, and the value lives in the contract between them. That contract is defined by ISA-95, published jointly as IEC 62264 by the International Society of Automation and implemented in XML schemas through MESA International's B2MML (Business To Manufacturing Markup Language). If you're scoping an integration, treat it as the reference, because it turns a vague handoff into a documented interface.

ISA-95's level hierarchy, usually drawn as the Purdue model, stacks systems from the physical process up to the business. Level 0 is the process itself, metal forming or a reaction running. Level 1 is sensing and actuation: thermocouples, drives, proximity switches. Level 2 is control: PLCs and local supervisory control (HMI and SCADA) holding the machine to setpoints in milliseconds to seconds. Level 3 is where the MES lives, thinking in work orders, operations, shifts, and lots. Level 4 is the ERP, thinking in days, weeks, and money. The documented MES-to-ERP boundary is the level 3 to level 4 interface, segmented across an industrial demilitarized zone (IDMZ) as recommended in NIST SP 800-82 Rev. 3, the operational technology security guide. Naming the boundary this precisely tells you which integration you're building.

What crosses that interface is a two-way exchange. Downward, the ERP sends what the floor needs to act: released work orders, the materials each consumes, and the routing to follow. Upward, the MES returns what planning and finance need to stay honest: confirmations that an operation finished, actual produced and scrapped quantities, and the material genealogy linking input lots to finished units. When this flow works, the ERP's inventory, costing, and order status reflect the floor in near real time. Bolt shop-floor data entry onto ERP screens built for office work instead, and the record is out of date by mid-morning. We cover the execution side of this boundary in what an MES does; from the ERP side, the discipline is to define the contract explicitly rather than by accident.

The MES-to-ERP integration is the documented level 3 to level 4 interface in the ISA-95 hierarchy
LevelSystemWhat lives thereAt the boundary
Level 4ERPOrders, MRP, costing, finance, master scheduleSends work orders, materials, routings down
Level 3MESDispatching, operator screens, quality, genealogyThe MES-to-ERP interface (L3 to L4)
Level 2PLC, local HMI and SCADAReal-time control, setpoints, alarmsFeeds machine counts and states up to MES
Level 1Sensors, actuatorsMeasurement and actuation on the equipmentWired into the process
Level 0Physical processThe actual making of the productThe thing every level above describes

Connecting ERP to the shop floor, PLCs, and PLM

Below the MES sits the equipment itself, and connecting it cleanly is the other half of the integration story. The standard protocol for reading machine data is OPC-UA, maintained by the OPC Foundation and also published as IEC 62541. It gives a vendor-neutral, secure way to read counts, states, and process values from PLCs, and a well-built MES within a smart factory uses it (or a protocol adapter where a machine predates it) to capture downtime, production data, OEE availability and performance metrics, and telemetry for predictive maintenance software automatically. The data path is layered: PLCs talk to the MES, the MES aggregates into work-order context, and only meaningful results post up to the ERP, which should never poll a PLC directly.

The other connection that matters runs to engineering. A product is designed in CAD and managed in PLM software (product lifecycle management), where the bill of materials originates before it reaches the ERP. Keeping the engineering BOM and the manufacturing BOM in sync is a real integration, not a copy-paste, because the two are organized differently: engineering thinks in design intent, manufacturing in how the thing is built and stocked. Engineering change orders (often paired with engineering change notices) are where this is tested: when a part is revised, the change has to propagate to the manufacturing BOM, open work orders, and material on hand, with effectivity dates saying which revision applies from when. Done loosely, the floor builds the old revision from a stale BOM while the new drawing sits in PLM, and the gap surfaces as a quality escape. This CAD-and-PLM-to-ERP sync is one of the quieter places a custom integration layer pays for itself.

Building the integration layer between ERP, MES, and the floor?
We design the ISA-95 boundary and the OPC-UA connections so work orders flow down and confirmations, actuals, and genealogy flow back up, without bolting shop-floor data entry onto ERP screens.
Scope the integration build

Build, configure, or buy ERP for manufacturing

With the architecture clear, the decision is which parts to buy, which to configure, and which to build, and a vendor can't give you a neutral answer. Start from one question: where does your competitive differentiation live? The parts of production that look like everyone else's are the parts a standard suite already models well; the parts that make you distinctive are the ones no package will fit.

Buying and configuring a standard suite is the right default for the common ground. If your costing, order flow, and inventory work like the industry norm, a mature ERP gives you functionality that's already built and tested, plus a maintained upgrade path. The discipline is to stay as close to vanilla as the business allows, because every step away is a step you re-test forever.

Building custom wins for the differentiating core: an unusual costing method, a quality workflow that fits no standard model, the mixed-mode genealogy that packaged data models handle badly. When the list of "the suite almost does this" workarounds becomes the implementation, you are already paying for custom software. The total cost of ownership has to count the recurring tax of heavy customization, not just the license, because that tax is paid at every upgrade.

Match the approach to where your differentiation lives, not to a vendor's preference
ApproachWhat you ownBest when
Buy a standard suiteConfiguration only; the vendor owns the code and roadmapYour processes match the industry norm closely
Configure a standard suiteParameters, workflows, and data mapping on a maintained coreCommon ground dominates and customization stays light
Build customThe full codebase and the differentiating logicA core process is your advantage and fits no package
Hybrid backbone plus layersA standard ERP for finance and orders, custom for executionYou need both a maintained core and a specialized edge

The pattern most manufacturers land on is the hybrid: keep a standard ERP as the financial and order backbone, and build the specialized planning, execution, or machine-data layers around it, integrated at the ISA-95 boundary. That is the shape of work we do in our custom software development and product development practices. HaulBreeze, our own supply-chain platform, and the Conveya transportation-management rebuild are both layers engineered around existing systems of record rather than replacements; and AirpartChain anchors aircraft-part records to a tamper-evident ledger, a traceability problem with the same shape as manufacturing genealogy. Idealogic does not sell a packaged ERP; we build the layers and integrations that make one fit a plant that does not run like the template.

Why manufacturing ERP implementations fail

Manufacturing ERP projects have a reputation for going badly, and the causes are consistent. The software is rarely the problem. Data, scope, and people are, in roughly that order of frequency.

Dirty master data is the first and most common cause. The bills of materials, routings, and inventory balances carried in the old system rarely match how the floor actually builds and stocks the product. A routing that says 12 minutes when the operation takes 19, an on-hand of 600 when the shelf holds 480, a BOM missing the consumable nobody recorded: feed these into a new system and it computes confidently wrong answers, and the floor stops trusting it by month two. The BOM and routing migration is the unglamorous work that decides the outcome.

Over-customization is the second. Every modification away from the standard suite adds build cost now and a regression-test burden at every upgrade, until a plant is too afraid of breaking its customizations to upgrade at all. The counter-discipline is vanilla-first: adopt the standard process unless the business genuinely competes on doing it differently. Weak change management is the third: a system rolled out without training the operators who live in it, or consulting them on the screens, gets routed around, and the new ERP runs in parallel with the spreadsheets it was meant to retire.

The numbers back the caution, though the best-known ones are old. Panorama Consulting's 2015 ERP Report found 58 percent of projects over budget, 65 percent over schedule, and 53 percent of organizations realizing less than half of the benefits they expected. Treat those as a historical baseline, since we couldn't confirm a comparable recent set.

Panorama figures come from its 2015 ERP Report, so read them as a historical baseline that argues for tight scope and clean data
MetricValueSource
Average implementation time15.7 monthsPanorama Consulting 2015 ERP Report
Projects over budget58 percentPanorama Consulting 2015 ERP Report
Projects over schedule65 percentPanorama Consulting 2015 ERP Report
Organizations realizing under half of expected benefits53 percentPanorama Consulting 2015 ERP Report

ERP Software Development Cost in 2026: Custom Modular ERP vs SAP & NetSuite

To compare ERP software development cost in 2026, separate custom engineering spend from the three-year licensing plus systems-integrator (SI) footprint of a commercial suite. Whether you engage a senior Central and Eastern European (CEE) engineering squad at $75/hr or a US agency at $165/hr, custom ERP development cost scales mainly with multi-level BOM depth, mixed-mode yield logic, and ISA-95 shop-floor connectivity.

2026 Manufacturing ERP Scope TierDelivery WindowCEE Senior Squad ($75/hr)US Domestic Agency ($165/hr)Included Planning, Costing & Shop-Floor Scope
MRP & Shop-Floor Architecture Sprint2 to 3 weeksFrom $18,000 ($18k to $28k)$40,000 to $62,000Multi-level BOM & routing audit, ISA-95 L3/L4 data contract, standard-vs-actual costing model, phased rollout estimate
Custom Shop-Floor / B2MML Sidecar on Existing ERP8 to 12 weeks$45,000 to $85,000$100,000 to $185,000Idempotent B2MML / REST work-order dispatch, scan-verified WIP consumption, barcode backflush queue, SAP/NetSuite/Dynamics sync
Modular Custom Manufacturing ERP Core4 to 6 months$85,000 to $165,000$185,000 to $365,000Versioned mBOM & ECO effectivity, finite routing schedules, MRP net-requirements engine, lot/serial inventory, WIP variance ledger
Mixed-Mode Batch + Discrete ERP & Genealogy5 to 8 months$135,000 to $240,000$295,000 to $525,000Formula potency & variable-yield scaling, catch-weight UOMs, tank-to-SKU lot genealogy, inline ISO 9001 quality holds & NCR workflows
Multi-Entity Discrete/Process ERP with WMS & Cost Accounting7 to 12 months$170,000 to $340,000+$375,000 to $750,000+Multi-plant intercompany transfers, bin-level RF warehouse execution, ASC X12 EDI 830/856, FASB ASC 330 actual & standard cost rollups

Manufacturing ERP software cost: three-year TCO of custom vs SAP S/4HANA and NetSuite

Commercial ERP quotes often look modest until named-user seats, shop-floor terminal licenses, sandbox fees, and SI customization hours compound over 36 months. The ranges below are our planning estimates, not vendor quotes, because SAP and Oracle negotiate pricing deal by deal:

  • SAP S/4HANA Cloud or Oracle NetSuite Manufacturing (100 users + 60 floor operators): Full-access and shop-floor user subscriptions, manufacturing/WMS add-on packs, and EDI modules can run $120,000 to $290,000/year, while SI implementation, SuiteScript or ABAP extensions, and dirty-BOM migration add $220,000 to $650,000. That puts 3-year TCO at $580,000 to $1,520,000+, with ongoing regression testing at every semi-annual vendor release.
  • Hybrid Sidecar or Modular Custom ERP (Senior CEE Squad at $75/hr): Keeping a lightweight accounting ledger in place while building a $45,000 to $85,000 B2MML shop-floor sidecar, or deploying an $85,000 to $165,000 modular custom manufacturing ERP core with $18,000 to $32,000/year in cloud hosting and SLA maintenance, holds 3-year TCO to $99,000 to $181,000 for a B2MML sidecar or $139,000 to $261,000 for a modular custom ERP core, with $0 per-seat licensing across unlimited floor terminals.

For broader multi-module benchmarks across engineering roles and delivery regions, see our breakdown of custom software development cost alongside our deep dive into MES software and ISA-95 execution, plus Airbyte vs Fivetran when replicating NetSuite, SAP, and shop-floor PostgreSQL tables into analytical warehouses.

Implementation timelines and how to compress rollout risk

Cost and timeline both scale with scope, plant count, and customization, so any single figure misleads without that context. Across both commercial and custom builds, the variables that move the budget are the count of sites, the modules in play, the depth of process-specific logic, and the integration work to the MES and shop floor, which is routinely underestimated because it stays invisible on vendor feature checklists.

On timeline, Panorama Consulting's 2015 ERP Report put the average implementation at 15.7 months. A focused first phase, one site or even one line with core execution, takes less; a full multi-plant rollout takes more, because each new area adds its own routings, equipment interfaces, and edge cases the pilot never met. As the failure section argued, the schedule risk sits in master data and integration far more often than in the software.

The way to compress both numbers is to scope tightly and pilot on one line before replicating, fixing the data and proving the integration where it is still cheap. That is how our custom software development squad approaches industrial platforms: start at the boundary that hurts most, build the layer that solves it, integrate it to the system of record, and expand from a working foothold. If you're weighing manufacturing ERP software, or more likely the custom layers and integrations around one, our manufacturing team scopes these from the floor and the data outward, not from the feature matrix in.

Need the layer a packaged ERP cannot give you? We build it
We engineer custom shop-floor B2MML sidecars, modular MRP and lot-genealogy cores, and clean SAP or NetSuite integrations on fixed milestones.
Scope a manufacturing build with us

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Artem Zaitsev
Artem ZaitsevCTO · Idealogic Development OÜ

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.

Frequently asked questions

  • Manufacturing ERP software is the system of record that runs a manufacturer's business and production together. Beyond general finance, sales, and purchasing, it adds bills of materials, routings, material requirements planning (MRP), shop-floor costing, lot and serial traceability, and quality management. Because ERP evolved out of MRP and MRP II, the calculation that balances material and capacity sits at its core, keeping inventory, costs, and order status synchronized across the floor.

  • Discrete manufacturing ERP models countable units assembled from a bill of materials and routing steps, tracking part numbers, sub-assemblies, and serial numbers. Process manufacturing ERP models materials mixed or transformed by a formula or recipe, tracking batches, variable yield, potency, shelf life, catch-weight pricing, and co-products or by-products. Many plants operate in mixed mode, compounding bulk batches before filling discrete SKUs, which often requires a custom genealogy bridge between both models.

  • The standard integration architecture follows ISA-95 (IEC 62264), which places the ERP at Level 4 and the manufacturing execution system (MES) at Level 3. Across that boundary, often serialized via B2MML, the ERP sends released work orders, BOMs, and routings down, while the MES returns operation confirmations, actual produced and scrapped quantities, and lot genealogy up. Below Level 3, the MES reads PLC counts and machine states over OPC-UA.

  • In 2026, custom ERP software development cost with a senior Central and Eastern European engineering team at $75 per hour starts from $18,000 for an MRP and shop-floor architecture sprint. A custom shop-floor and B2MML sidecar layered onto an existing ERP runs $45,000 to $85,000, a modular custom manufacturing ERP core $85,000 to $165,000, a mixed-mode batch and discrete ERP with genealogy $135,000 to $240,000, and a multi-entity discrete or process ERP with WMS and ASC 330 cost accounting $170,000 to $340,000+. The same builds at a US agency rate of $165 per hour run about 2.1x to 2.3x those budgets.

  • What you pay for manufacturing ERP software depends on plant count, commercial licensing versus custom code, and how deep the shop-floor integration goes. Focused custom sidecar layers start around $45,000 and modular custom cores around $85,000. Multi-plant commercial suites such as SAP S/4HANA or NetSuite, with systems-integrator customization, frequently reach $0.5 million to $1.5 million or more over three years on our planning estimates. On timeline, Panorama Consulting's 2015 ERP Report put the average implementation at 15.7 months. BOM cleansing and Level 3 to Level 4 integration are what usually stretch the schedule.

  • Manufacturing ERP projects fail on data, scope, and change management far more often than on software defects. Inaccurate bills of materials, outdated routing cycle times, and unverified inventory balances make the MRP engine compute wrong plans from day one. Heavy custom code inside the ERP core creates upgrade lock-in, and weak operator training sends teams back to spreadsheets. The overruns are well documented: Panorama Consulting's 2015 ERP Report found 58 percent of projects over budget and 65 percent over schedule.

  • Buy and configure a standard ERP suite when your finance, purchasing, and order workflows match industry norms, keeping the core as close to vanilla as possible. Build custom software for the shop-floor processes that create competitive differentiation, such as mixed-mode batch-to-discrete genealogy, specialized costing, or automated machine integration. Most manufacturers succeed with a hybrid architecture: a commercial ERP backbone paired with custom execution and integration layers at the ISA-95 boundary.

  • Products are designed in CAD and governed in product lifecycle management (PLM), which owns the as-designed engineering BOM (eBOM). When an engineering change order (ECO) is approved, the integration layer transforms and releases the updated manufacturing BOM (mBOM) and routing revisions into the ERP with explicit effectivity dates or lot cutovers. Automating this handoff prevents the shop floor from building obsolete revisions or purchasing discontinued components.

  • Under FASB ASC 330, the US GAAP inventory standard (IFRS plants use IAS 2), manufacturing ERP values products by rolling up direct materials from the BOM plus direct labor and manufacturing overhead absorbed along routing operations. Standard costing sets target rates in advance and books differences in material usage, purchase price, or labor efficiency as variances, and those standards have to approximate actual cost and be reviewed regularly. Actual costing tracks the exact cost of consumed lots and logged floor hours, providing lot-level margin visibility across completed production orders.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.