Intelligent ERP

What does that part actually cost you?

In this article

Nori.mx6 min read

Cost of the partStandard set two years agoMaterialpurchasing, invoiced?Laborplanned 4 h, ran 6Scrapnotebook, end of shiftMONTH CLOSE15days laterthree people, on a weekend

One question, and it is worth answering out loud: can you say what a part you ran last week cost you — material, labor and scrap included — without asking anyone?

Almost nobody can. What usually exists is a number, called standard cost, set two years ago when that program was first quoted. Since then material went up, the exchange rate moved, a shift was added and the part was redesigned once.

You are still quoting from that number. It is not an accounting error. It is that nobody has a way to update it without stopping for a week.

Standard cost ages and nobody notices

A standard cost is not a bad thing. It is a useful tool: it freezes a number so you can compare and plan. The problem is that it ages quietly.

The sign that yours has expired is not in the books, it is in the meetings. If at month-end the real margin keeps coming in below plan and the explanation is always “we burned more material than we should have,” what you are looking at is not a variance. It is a standard that no longer describes your operation.

And because you quote from the standard, every new part gets quoted with the error baked in.

The three pieces nobody adds up

A part’s cost lives in three different places and they almost never meet.

Material is usually the one that is right, because purchasing owns it and there are invoices. Even so, freight, duty and the cost of that material sitting in the warehouse for three months tend to escape.

Labor is where the trouble starts. It is nearly always calculated from how long the job should take, not how long it took. If the line ran six hours instead of four, somebody paid for those two hours, but they do not show up in that part’s cost.

Scrap hides the best, and it gets the next section to itself.

As long as the three live in separate spreadsheets — purchasing in one, production in another, accounting in its own — real cost does not exist. Three approximations exist, they never agree, and each department defends its own.

Scrap is where the money is

Ask where waste gets recorded and who records it.

The answer is usually that the supervisor writes it in a notebook at the end of the shift, from memory, and somebody keys it in later if there is time. That is not data. That is a recollection.

And scrap is not only the piece that got thrown away. It is the material burned setting up the run, the rework that occupied two people for half an hour, and the part that shipped and came back. If those three are not recorded as they happen, they can never be costed, because three days later nobody remembers.

Here is the link to the floor: a production number captured by hand at the end of a shift is useless for costing, no matter where it ends up. That is what we covered in what has to be ready before you connect a machine. Real cost is one of the stronger reasons to do it.

The close that takes fifteen days

Another way to measure the same thing without talking about cost at all: how many days after month-end do you have firm numbers, and how many people worked the weekend to get there?

If the answer is fifteen days and three people, the problem is not those three people’s effort. It is that the systems do not talk and somebody is reconciling them by hand, month after month. That work leaves nothing behind: next month it has to be done again, identically.

And there is a worse cost than the hours. A number that arrives on the fifteenth is no longer useful for deciding. It is useful for explaining.

The indispensable spreadsheet

Count how many spreadsheets are essential to operating, and of those how many have a single owner who, if they are out sick for two weeks, nobody else knows how to update.

There are usually between three and eight. One does costing, one tracks a program, one assembles the report management asks for. They work. They have worked for years. And they are exactly the same exposure as the system nobody documented, only portable: they live on one laptop, they have no backup, and nobody knows how they work inside.

They do not have to be removed all at once. They have to be known — which ones they are and who holds them up — and that inventory takes one morning.

The agreement to make before buying anything

This is the requirement that decides whether an ERP will work, and it is not technical.

Management has to accept in advance that the system’s number is the official number, even if for the first few months it looks worse than the usual spreadsheet.

It will look worse. Once you start recording scrap properly, margin will drop. Not because you got worse, but because you were not counting it before. If at that moment management goes back to the spreadsheet because “that one gives the number we expected,” the project is already over even though the system is still running. You will have two truths, and people will keep using whichever one suits them.

There is a second, shorter agreement: every number needs an owner. Who answers for inventory, who for cost, who for collections. A number without an owner does not get fixed by software.

What you can measure this week

Three things, with what you already have, and all three say more than a demo:

  • Take five parts you ran last month and cost them by hand, completely. Compare against standard. The average gap is your margin of error when quoting.
  • Ask management and production how many pieces were produced last month. If the two numbers differ, write down where each one came from. That is your list of systems that do not talk.
  • Follow one order and count how many times the same data gets typed before it is invoiced. That number is the cost of disconnected systems, and it is the same one that breaks the delivery date you promised.

Where a system belongs, and where it does not

With scrap recorded where it happens and the official-number agreement made, a properly implemented ERP makes real cost exist without anyone assembling it: material comes in from purchasing, time from the floor, scrap from where it is produced, and a part has a cost the same day it is run.

That floor time now has a second reason to be recorded properly: from January 2027 the workday has to be recorded electronically by law, so the data you are missing for costing is the same data the authority will ask for.

What it does not do is change the answer. If your part loses money, the ERP will tell you sooner and in more detail, and that is where its job ends. What comes next — renegotiate, redesign, or stop quoting that kind of part — is a business decision, and it is the one that actually matters.

One last crossover that almost always shows up alongside: if you quote late because costing depends on one person, the problem you see in quotes that never get followed up starts here, not in sales.

Related service

Intelligent ERP

One system that runs your whole company, with intelligence built in.

See the service

Articles on this service

Five years from the tax returnArt. 30, Fiscal Code2026202720282029203020312032saletax returnstill retrievableArchive, no system neededCSVPDFXMLA 3-year-old invoicefound in 5 minutes

Intelligent ERP

New system? The old one stays for five years

Mexico's tax code requires keeping accounting records for five years, and your old system is part of them. What to keep, how, and why switching it off falls short.

5 min read

ERPowns:Closes the monthPart catalogPurchase orderCostFinancialsSame countERP900Scanner880Which one wins?FLOORowns:Runs the minuteLocationScanDowntime reasonOperatorExact time

Intelligent ERP

When the corporate ERP does not reach the floor

You have SAP and the warehouse still runs on a spreadsheet. The problem is rarely the ERP. It is the last fifteen meters of the operation.

7 min read