The Number Is Right. The Diagnosis May Not Be.

SAI White Paper Series
The Number Is Right. The Diagnosis May Not Be.
Why a high cost-of-goods percentage does not tell you what is actually governing it
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
Publication Identity
Original Publication: June 2026
Current Revision: September 2026
Version: 1.0
Classification: Financial Performance · Cost Structure · Diagnostic Reasoning
Publication Identifier: SAI-SCBC-19
Subject: Cost of Goods Sold · Margin · Financial Analysis · Cost Structure · Diagnostic Reasoning · Constraint Identification
Primary Audience: Business Owners · Executives · CFOs · Accountants · Advisors · Consultants · Business Educators
SAI Discipline Stage: IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Evidence Orientation: Practitioner Observation · Conceptual Diagnostic Illustration · External Scholarship · SAI Proposition
Executive Abstract
The cost-of-goods percentage is high. The accountant sees it. The owner sees it. The income statement records it accurately. The margin is weaker than it should be.
So management starts looking for an answer: supplier pricing, purchasing discipline, material cost, labor efficiency, product mix, waste, freight.
All are reasonable places to investigate.
But the COGS line itself does not tell management which explanation is correct.
The number tells you what happened. It does not, by itself, tell you why.
A high cost-of-goods percentage may reflect unfavorable supplier economics. It may reflect product mix, scrap, rework, labor inefficiency, design choices, fulfillment practices, pricing architecture, organizational authority, or strategic decisions made somewhere else in the business.
And sometimes the cost structure is exactly where management should focus. Sometimes it is not.
The diagnostic task is therefore not to distrust the financial statement. It is to avoid asking the financial statement to answer a question it was not designed to answer.
A correct financial number is evidence. It is not automatically a causal explanation.
Measurement is not diagnosis.
That distinction is the subject of this paper.
The Central Proposition
A financial statement can identify where performance is weak without establishing why it is weak. A high cost-of-goods percentage may reflect supplier economics, product mix, process inefficiency, quality loss, labor content, pricing architecture, organizational design, strategic choices, or another condition. Diagnostic discipline requires separating the number from the explanation, testing competing causes, and determining which condition deserves priority before prescribing corrective action.
Why This Paper Matters
Cost of goods is one of the most visible lines on an income statement. It directly affects gross margin. When it rises, management feels the result quickly.
That visibility creates a natural temptation:
The number moved, so the cause must be located close to the number.
Sometimes that is true.
If material cost increased because a supplier raised prices, the cause may be direct. If freight increased because shipping rates changed, the explanation may be straightforward. If labor content rose because production time increased, the operating cause may be visible.
But business results often have several plausible explanations. A high COGS number can be produced inside purchasing, outside purchasing, upstream in product design, downstream in fulfillment, or elsewhere in the organization entirely.
A financial line item can locate the symptom without locating the cause.
That is why good financial management and good diagnosis are related—but not identical—disciplines.
The Accountant Is Not the Problem
A serious paper on financial diagnosis should not imply that accountants merely “see the number” while someone else understands the business. That would be inaccurate.
A capable accountant, controller, CFO, or financial advisor may analyze product mix, contribution margin, purchasing patterns, labor efficiency, inventory, freight, waste, overhead allocation, customer profitability, and cost trends. They may participate directly in root-cause analysis.
The distinction is not between accountants and diagnosticians. It is between financial reporting and causal explanation.
Financial reporting asks:
What happened financially?
Diagnosis asks:
What condition is producing the result, what alternatives remain plausible, and what deserves priority?
The number can be precise even when the explanation is still open.
That distinction protects both disciplines.
Five Different Reasons COGS Can Be High
1. The Supplier Economics Really Are the Problem
Sometimes the most obvious explanation is correct.
The supplier raised prices. Purchasing volume no longer matches the terms. Freight economics changed. Alternative suppliers exist at materially better cost. The business may simply have failed to renegotiate.
In those cases, supplier economics may genuinely deserve priority. There is no diagnostic virtue in rejecting the obvious merely because a deeper explanation is possible.
Sometimes the supplier really is the problem.
The diagnostic requirement is simply to establish that conclusion with evidence rather than assume it from the COGS line alone.
2. Product Mix Is Driving the Number
A business can become less profitable without any supplier increasing prices. The product mix may change.
Higher-cost products may represent a larger share of revenue. Lower-margin customers may grow faster. Sales incentives may favor volume over contribution. Discounting may change unit economics.
A company may report that “COGS is rising” when the underlying issue is that it is selling a different economic mix than it sold before.
The cost percentage can change because the business changed what it sells—not what it pays.
That changes the diagnostic question. Supplier renegotiation may help. It may not address the condition producing the larger margin problem.
3. Operational Loss Is Inflating the Number
COGS can also rise because the business is consuming more resources than it should to produce the same result.
Scrap, rework, yield loss, expediting, overtime, poor scheduling, small production runs, setup inefficiency, returns, and quality failures can all increase cost.
Those are not necessarily purchasing problems. They are operating conditions that financial reporting eventually records as cost.
The income statement may record an operational problem in financial language.
That does not make the problem financial in origin.
4. Organizational or Decision Architecture Is Producing the Cost Pattern
Sometimes the visible cost problem reflects the way authority and accountability are structured.
Purchasing may be responsible for cost but have no authority over specifications. Operations may be responsible for throughput but not allowed to change scheduling rules. Sales may promise delivery terms that operations must absorb. Product management may choose materials without owning margin consequences.
The financial number then becomes the final expression of decisions made across several functions.
A cost problem can be created by who is allowed to decide what.
In such cases, buying harder may not be enough. The business may need to examine the decision architecture producing the cost.
5. COGS May Be Real—and Still Not Be the Priority Problem
This is the distinction most likely to be missed.
A high COGS percentage can be real. Management can improve it. And another condition can still deserve priority first.
The company may also be facing severe liquidity pressure, declining demand, weak positioning, customer concentration, execution failure, leadership paralysis, or a credibility problem affecting revenue.
Improving COGS may still be worthwhile. But diagnostic discipline asks a narrower question:
Is this the condition that deserves priority now?
A real problem is not automatically the governing problem.
The Number Is Right. The Story May Be Wrong.
Financial statements are powerful because they summarize large amounts of operating activity. That strength can also create a cognitive shortcut. Management sees a number move and quickly constructs a story around it.
COGS rose, therefore suppliers are too expensive. Margin fell, therefore pricing is wrong. Payroll rose, therefore staffing is excessive. Revenue fell, therefore sales is weak.
Each explanation may be plausible. None is established by the number alone.
A correct financial number can support an incorrect causal explanation.
The next step is not disbelief. It is investigation.
What Repeated “Why” Questions Can—and Cannot—Do
Asking “why?” repeatedly can be useful.
Why is COGS high? Because material cost increased. Why did material cost increase? Because the business is buying in smaller quantities. Why are quantities smaller? Because production schedules have become fragmented. Why are schedules fragmented? Because sales commitments are being accepted without production coordination.
That line of questioning may reveal a deeper pattern. But repeated questioning does not guarantee that the final answer is correct.
The inquiry can be distorted by confirmation bias, incomplete information, omitted alternatives, assumptions disguised as facts, or a causal chain that sounds coherent but is wrong.
Five Whys can deepen the question. It cannot prove the answer.
A stronger diagnostic process keeps competing explanations alive and asks what evidence would distinguish among them.
Five Conceptual COGS Illustrations
The following are conceptual diagnostic illustrations. They are not independently verified cases and are not presented as proof that a particular governing constraint existed in any specific organization.
The Supplier Renegotiation
A manufacturer has used the same supplier for years. COGS has risen. Management believes the supplier terms are outdated.
That may be correct.
But before treating renegotiation as the full diagnosis, several questions remain.
Has market pricing changed? Has purchase volume changed? Have specifications changed? Has freight changed? Has buying behavior fragmented? Has the supplier relationship actually become uneconomic?
If the evidence points clearly to terms, renegotiation may be exactly the right response.
The obvious answer should be tested—not automatically rejected or automatically accepted.
The Restaurant Food-Cost Problem
A restaurant's food-cost percentage rises steadily. The immediate explanation is ingredient price.
But other possibilities include portion variance, waste, menu mix, discounting, theft, purchasing frequency, recipe design, or inconsistent operating discipline.
The number is useful because it tells management where performance deteriorated. It does not tell management which mechanism caused the deterioration.
The Distributor's Product Mix
A distributor's gross margin declines while supplier pricing remains relatively stable. Revenue is growing. The mix, however, is moving toward high-volume, lower-margin products.
Management calls it a COGS problem.
Another interpretation is possible:
The business may have a mix problem expressed through the COGS percentage.
The corrective action depends on what is producing the mix—customer demand, sales incentives, strategic positioning, competitive response, or deliberate market expansion.
The same financial result can come from different operating causes.
The Manufacturer's Scrap Problem
A manufacturer sees COGS increase. Material prices have not changed materially. Closer examination shows rising scrap and rework.
The financial number correctly reports the consequence.
The diagnostic question becomes:
Why is scrap rising?
Possible explanations include equipment condition, process discipline, scheduling pressure, specification complexity, training, supplier quality, or production decisions made under delivery pressure.
COGS points to the result. Diagnosis must distinguish among the mechanisms.
The Product Specification
A business has negotiated aggressively with suppliers. Purchasing performance is strong. COGS remains stubbornly high.
One possible explanation is that the product itself has been designed around expensive material, component, or service requirements. The purchasing team may be executing perfectly inside an uneconomic specification.
You can have excellent purchasing inside a cost structure that cannot produce the required margin.
In that case, the problem may not be procurement performance at all.
The Difference Between a Cost Driver and a Governing Constraint
This distinction is essential.
A cost driver helps explain why a financial number moves. A governing constraint is the condition currently limiting overall performance and deserving priority. They are not automatically the same.
Higher freight can be a cost driver without making freight the governing constraint. Higher material cost can be a cost driver without making purchasing the governing constraint. Poor yield can be a cost driver without making operations the governing constraint.
The question becomes:
Which condition is not only affecting the number, but governing the performance that matters most?
That requires broader evidence.
The COGS Line Can Be a Starting Point—not a Verdict
A useful financial review can begin with the number.
What changed? How much? When? Where? For which products, customers, locations, or suppliers?
Then the inquiry can move outward.
What operating changes accompanied the financial change? What decisions changed? What market conditions changed? What incentives changed? What resource requirements changed? What explanations are competing? What evidence would support or eliminate each one?
The number tells you where to look. It does not tell you what you will find.
That is the transition from financial observation to diagnostic reasoning.
Five Questions Before Prescribing a COGS Solution
1. What specifically changed in the number?
Did total COGS rise? Did COGS as a percentage of revenue rise? Did one product category drive the change? Did labor, material, freight, waste, or overhead move?
Do not diagnose an aggregate when the movement may exist in only one component.
2. What changed operationally at the same time?
Volume? Mix? Suppliers? Specifications? Scheduling? Quality? Staffing? Customer requirements? Production method?
The financial movement should be compared with the operating changes surrounding it.
3. What competing explanations remain plausible?
Do not stop at the first reasonable answer.
Supplier cost may be one explanation. Process loss may be another. Mix may be another. Authority structure may be another. External market conditions may be another.
A plausible explanation is not yet a diagnosis.
4. Which condition appears to deserve priority?
Several things may be wrong simultaneously.
The question is not:
“What can we improve?”
It is:
“What should we address first?”
That is the prioritization decision.
5. What result should change if the diagnosis is correct?
If supplier terms are governing the problem, what should change after renegotiation? If scrap is governing the problem, what should change after process correction? If mix is governing the problem, what should change after portfolio or incentive changes?
Define the expected result before implementation. Then confirm whether it occurred.
What the Management and Accounting Literature Adds
The broader literature provides useful context for the distinction between financial measurement and causal explanation.
Management accounting has long emphasized the need to understand cost behavior, cost drivers, contribution economics, and activity relationships rather than treat aggregate financial lines as self-explanatory. Activity-based costing, for example, developed in part to improve visibility into the activities and resource consumption underlying reported cost.
The broader management literature on performance measurement likewise cautions against equating an observed metric with the complete explanation for organizational performance. Root-cause methods, systems thinking, and causal analysis similarly emphasize the need to distinguish observed outcomes from the mechanisms producing them.
These bodies of scholarship do not independently validate the SAI Business Constraint Discipline™.
They reinforce a narrower and important principle:
Measurement and causal explanation are different tasks.
SAI adds the prioritization question:
Which condition appears to be governing performance now?
A High COGS Percentage Does Not Automatically Identify the Constraint Class
Because the symptom is financial, management may naturally assume the constraint is Financial. That may be correct. It may not be.
The limiting condition may involve any of the Seven Classes:
Market — customer demand, competitive positioning, pricing pressure, or channel economics may be producing an unfavorable mix.
Operational — scrap, rework, yield loss, labor inefficiency, throughput, or process design may be increasing cost.
Financial — capitalization, purchasing economics, liquidity, cost structure, or financial commitments may be limiting performance.
Organizational — authority, accountability, coordination, handoffs, or incentives may be producing poor cost decisions.
Strategic — product architecture, business-model choices, sourcing strategy, market selection, or allocation decisions may be driving the economics.
Leadership — executive judgment, reluctance to make difficult commercial decisions, poor prioritization, or decision bottlenecks may be sustaining the condition.
Credibility — supplier trust, market reputation, purchasing leverage, stakeholder confidence, or commercial legitimacy may affect available terms or relationships.
The financial location of the symptom does not automatically identify the class of the constraint.
Evidence must do that work.
Sometimes the COGS Problem Really Is Straightforward
Diagnostic discipline should not make simple problems unnecessarily complicated.
Sometimes the supplier raised the price, an alternative is cheaper, quality is equivalent, switching cost is acceptable, and the appropriate response is to renegotiate or change suppliers.
Sometimes waste is visibly excessive. Sometimes labor standards are outdated. Sometimes freight contracts are poor. Sometimes the product mix is clearly uneconomic.
In those cases, additional diagnostic complexity may add little value.
Depth is useful only when the evidence requires it.
The purpose of diagnosis is not to force every problem into a complicated explanation. It is to avoid acting with more certainty than the evidence supports.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Identify
Start with the financial result.
What changed? Where? When? By how much?
Then examine possible causes.
What operating conditions changed? What decisions changed? What external conditions changed? What alternative explanations remain plausible?
Do not confuse the financial location of the problem with the structural location of the cause.
Prioritize
A business may have supplier issues, waste, labor inefficiency, poor mix, weak pricing, organizational conflict, and liquidity pressure at the same time.
The diagnostic question remains:
Which condition deserves priority now?
Not every cost problem should be solved first merely because it is measurable.
Resolve
Once the priority condition is identified, match the corrective action to it.
Renegotiate supplier terms. Change sourcing. Redesign the product. Improve yield. Correct quality. Change incentives. Clarify authority. Reprice the portfolio. Restructure the process.
The intervention should follow the diagnosis.
Confirm
Did the targeted condition improve? Did COGS move as expected? Did gross margin improve? Did the improvement persist? Did another condition become limiting? Was the original causal explanation supported?
If the expected result does not occur:
Reopen the diagnosis.
And if a previously resolved problem returns:
Recurrence means reopen the diagnosis.
Confirmation is where the proposed explanation meets the evidence.
What This Changes for Business Owners
Do not ask only:
“Why is COGS high?”
Ask:
“What evidence tells me why COGS is high—and whether that condition deserves priority?”
That second question prevents a financial symptom from becoming an automatic prescription.
What This Changes for CFOs and Accountants
Financial reporting already provides one of the most important forms of evidence in the business. The opportunity is to make the boundary explicit.
A variance identifies movement. Analysis develops possible explanations. Diagnosis tests which explanation best fits the evidence and whether that condition deserves priority.
That distinction does not diminish accounting. It extends its usefulness.
What This Changes for Advisors and Consultants
Do not treat a visible cost problem as permission to begin with the solution most closely aligned with your specialty.
A procurement advisor may see supplier terms. An operations advisor may see waste. A strategist may see product architecture. A CFO may see margin structure.
Each may be seeing something real.
The existence of a real problem does not establish that it is the priority problem.
What This Changes for Business Educators
Students should learn to distinguish:
- measurement,
- variance,
- cost driver,
- causal hypothesis,
- governing constraint,
- corrective action,
- confirmation.
Those are different analytical stages. Collapsing them into one answer teaches prescription before diagnosis.
Implications / Applications
For business owners: Treat the COGS line as evidence, not as a complete diagnosis.
For accountants and CFOs: Separate financial measurement from causal certainty.
For operations leaders: Trace the operating mechanisms behind reported cost.
For advisors: Keep competing explanations alive before recommending intervention.
For executives: Prioritize the condition governing performance, not merely the number attracting attention.
For educators: Teach students to move from metric to explanation to evidence to priority.
Across all six:
The COGS line measures the result. Diagnosis must explain the condition producing it.
Limitations and Questions for Further Examination
This paper advances a practitioner and conceptual proposition about cost of goods, financial reporting, causal reasoning, and diagnostic prioritization.
It does not establish that financial statements are inadequate for business diagnosis.
It does not establish that accountants, CFOs, or financial professionals generally stop at surface-level explanations.
It does not establish that high COGS is always a symptom of a deeper structural condition.
It does not establish that supplier renegotiation, purchasing discipline, product-mix analysis, or cost reduction are usually insufficient.
It does not establish that repeated “why” questioning reliably identifies a governing constraint.
It does not establish that the financial location of a problem proves or disproves a Financial Constraint.
It does not establish that every COGS problem requires broad enterprise diagnosis before corrective action.
And it does not establish that the SAI Business Constraint Discipline™ or SAI diagnostic instruments have been independently validated as producing superior cost-management outcomes.
Questions deserving further examination include:
How often do businesses misattribute aggregate cost movements to the wrong underlying driver?
Which cost patterns are most reliably traced through conventional financial analysis alone?
When does product mix explain COGS movement better than supplier economics?
How should organizations distinguish a cost driver from a governing constraint?
What evidence best distinguishes operational loss from strategic product-economics problems?
When is additional diagnostic depth unnecessary because the direct cause is already clear?
How should financial professionals communicate diagnostic uncertainty without reducing decision usefulness?
What independent evidence would be required to test whether diagnosis-first sequencing improves cost-management outcomes?
These questions remain open.
Conclusion
The COGS number can be correct. The accountant can be correct. The supplier analysis can be correct. The purchasing review can be correct. The operating data can be correct.
And management can still be wrong about what deserves priority.
That is not a contradiction. It is the difference between observation and diagnosis.
The financial statement tells you where performance moved. It may suggest why. It may strongly support one explanation.
But the number itself does not settle the causal question.
The number is right. The diagnosis may not be.
The next step is not to distrust the number. It is to ask what the number actually proves—and what it does not.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Diagnosis first.
Improvement second.
Evidence Boundary
This White Paper combines several forms of material that should not be treated as equivalent.
Practitioner / Operating Observation
Observations concerning cost-of-goods analysis, margin pressure, financial reporting, supplier decisions, purchasing, product mix, operational loss, and management decision-making reflect practitioner experience and operating interpretation.
Conceptual Diagnostic Illustrations
The supplier, restaurant, distributor, manufacturer, scrap, and product-specification examples are conceptual diagnostic illustrations. They are not independently verified cases and are not presented as proof that a particular governing constraint existed in any specific organization.
Internal SAI Framework
The governing-constraint concept, the Seven Classes of Business Constraint™, and IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM are components of the Schneider Axiom Institute Business Constraint Discipline™.
Independent External Scholarship
External scholarship provides intellectual context concerning management accounting, cost behavior, activity-based costing, performance measurement, root-cause reasoning, and organizational analysis.
It does not independently validate the SAI Business Constraint Discipline™.
SAI Proposition / Interpretation
The proposition that a financial metric can accurately identify a performance result without establishing the governing condition producing it is an SAI interpretation informed by practitioner experience, diagnostic reasoning, and related scholarship.
Independent Validation
This paper does not claim independent validation that the SAI Business Constraint Discipline™, the Business Constraint Diagnostic™, or diagnosis-first sequencing produces superior financial, margin, or cost-management outcomes.
References
Cooper, R., & Kaplan, R. S. (1988). Measure costs right: Make the right decisions. Harvard Business Review, 66(5), 96–103.
Kaplan, R. S., & Norton, D. P. (1992). The balanced scorecard—Measures that drive performance. Harvard Business Review, 70(1), 71–79.
Ittner, C. D., & Larcker, D. F. (1998). Innovations in performance measurement: Trends and research implications. Journal of Management Accounting Research, 10, 205–238.
Deming, W. E. (1986). Out of the Crisis. MIT Press.
Related SAI Resources
The Number Is Not the Problem — The Constraint Creating the Number Is
A companion White Paper examining why financial results should be treated as evidence rather than automatically as diagnosis.
Profitable. Growing. Still Worried About Payroll.
A companion White Paper examining why profitability and liquidity can diverge even when the financial statements appear strong.
The Intervention Worked. The Client's Problem Didn't.
A companion White Paper examining why technically successful work may fail to improve the client's priority business outcome.
You Grew the Business. The Problem Grew With It.
A companion White Paper examining how scale can amplify, expose, create, or displace limiting conditions.
The SAI Business Constraint Discipline™
A structured approach to identifying what appears to be limiting organizational performance, determining what deserves priority, resolving the priority condition, and confirming whether improvement occurred.
The Seven Classes of Business Constraint™
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
Business Constraint Diagnostic™
An SAI diagnostic resource designed to support identification of a probable governing constraint class and the structural condition within that class that appears to be limiting performance.
SAI Credential Programs
Programs designed to develop structured diagnostic capability for business owners, executives, advisors, and consultants.
These resources are supplementary.
The intellectual argument in this White Paper stands independently of any purchase or enrollment.
Lawrence M. Schneider
Founder & CEO
Schneider Axiom Institute™
Lawrence M. Schneider brings more than five decades of CEO-level operating experience across manufacturing, distribution, construction, land development, franchising, and multi-entity businesses.
Schneider Axiom Institute develops and teaches the Business Constraint Discipline™—a structured approach to identifying what is limiting organizational performance, determining what deserves priority, resolving the priority condition, and confirming whether improvement occurred.
Diagnosis before prescription.
© 2026 Schneider Axiom Institute LLC. All Rights Reserved.