Why QMS Determines Whether a Business Model Thrives, Breaks, or Bleeds Money
In 25 years around food and regulations, I’ve learned that no matter how complex the operation or how sophisticated the system, one constant shapes every business — money and the need to preserve, grow, and sustain it. In the military, government funds matter the same way sales do in the civilian world. There are still checks and balances, still financial statements to reconcile, and departmental budgets are always scarce.
As I expand my consulting footprint in cost‑sensitive environments, I’m seeing a trend that concerns me: many businesses don’t fully understand their costing model. That gap becomes the reason they don’t understand why their QMS isn’t working, which ultimately renders quality, compliance, regulatory, and ethics functions useless — and that’s where I come in. It’s especially visible in companies with multiple costing structures, like retailers and manufacturers. The nuance is simple. When something works on a small scale, the natural instinct is to replicate it on a larger one. We learned that from a man who started selling books online and ended up reshaping the modern consumer experience.
But my stance has never changed: you can’t protect what you don’t understand. If you don’t know how a product moves through the supply chain, how it reaches the consumer, or what each stop requires to keep the company safe, you can’t build systems that work. I’ve always viewed the governing departments of large corporations as the entities that keep the business afloat financially and legally. If the people in those roles are siloed and don’t understand how the business operates as a whole, they can’t implement the controls that protect it. It’s like putting someone behind a stick shift who doesn’t know how to drive stick — they’re not going anywhere because they don’t understand the mechanics of what they’re operating.
In today’s insight, I give you a cross‑industry look at how QMS supports distribution, retail, sales, logistics, and M&A — and why quality systems must follow both product movement and financial risk if they’re going to be competitive, meet financial goals, and operate from a money pot rather than a money pit.
Quality Follows the Cash Flow — And So Do the Problems
Before any organization can build a meaningful Quality Management System, it must understand how its business operates — how product is sourced, how it moves, how responsibility shifts, and how money flows through the supply chain. This isn’t about becoming a finance expert; it’s about recognizing that the product type, sourcing model, and commercial pathway dictate the level of control, documentation, and oversight required. In retail, distribution, and trade commerce, a QMS must be built to match the way the business truly functions, or it will fail long before it ever has a chance to protect the brand.
Now let’s begin!
Scenario #1: The DWPE Lot That Made the Sourcing Director Cry
The first time I saw a DWPE lot break an entire sourcing model, it wasn’t a safety issue — it was a communication failure. A DWPE halts inventory, freezes revenue, and exposes every weakness in a sourcing and documentation model, and that’s exactly what happened. The lot had already failed testing, but because departments weren’t aligned, it still shipped. Six months later, the DWPE hit, and no one knew what it was or how to contain it.
I reached out to the supplier, assuming they were at fault, only to learn the real problem was internal. Our department had been treated like a check‑in‑the‑box function for years, ignored by leadership and disconnected from the rest of the business. Root cause analysis revealed that the sourcing director had told the supplier they could ship without required testing just to secure the business — a pattern the FDA had already flagged in a previous inspection. When the findings were presented, he broke down and blamed the VP, and the fallout forced the company into a full training on cross‑functional communication. The lesson was simple: when departments don’t talk, accountability disappears, and the business pays for it — in this case, roughly $12 million in inventory the company had to absorb.
Scenario #2: OTC Products — When the Absence of a QMS Becomes a Billion‑Dollar Loss
OTC products fall under some of the strictest regulations in the U.S., and entering that space requires a fully built, fully functioning QMS long before a single unit ships. This company spent two years preparing to relaunch its OTC line — two years of planning, forecasting, supplier engagement, and internal excitement — but none of it mattered because the system behind the launch didn’t exist. During COVID, leadership hired a director they believed had FDA experience, assuming her presence meant compliance was finally under control. She didn’t have the background they thought she did, and the QMS she was expected to build never materialized. She shadowed me to learn the category, but it became clear she didn’t know how to manage batch approvals, cite 21 CFR 210/211, or structure the documentation required for OTC products entering the U.S. Despite that, she was allowed to hire a team, expand titles, and grow an org chart faster than the system itself.
Two years later — right when the company was ready to launch — the truth surfaced. The OTC products they had instructed suppliers to manufacture couldn’t be imported at all. Containers were already moving, orders were already fulfilled, and yet no one had built the QMS needed to support the category. With no batch approvals, no regulatory alignment, and no compliant documentation, the company ended up with nearly a billion dollars’ worth of expired OTC inventory sitting in limbo, completely unsellable. Two years of preparation collapsed in an instant because the foundation was never there.
How to Implement Your QMS No Matter Where Your Business Stands
Quality systems don’t fail because the regulations are complicated — they fail because the business model isn’t understood. Every breakdown in the scenarios came down to the same gaps: limited knowledge, poor communication, and no understanding of how the business actually moved. At the center of that movement is money — the fines tied to regulatory violations, the inventory losses that come from poor controls, and the cost of product recalls when systems fail. A QMS only works when the people running it understand product flow, regulatory expectations, and the financial exposure tied to every decision. This is also where culture matters. Quality training, regulatory webinars, and ongoing education shouldn’t be optional or limited to one department — they should be part of how the company operates. Without that foundation, it becomes easy for someone with no real expertise to sound informed simply because they can repeat terminology they just looked up. That’s how organizations end up trusting the wrong voices, building systems on assumptions, and making decisions that collapse under pressure.
To understand what a functioning system actually looks like, we start at the point where risk — and cost — is born: direct imports.
Direct Imports: When FSMA Meets ISO and FSSC
Many companies move to direct imports for one reason — cost. Owning product at origin lets them control pricing, reduce middle‑layer expenses, and manage the financial risks tied to fines, inventory write‑offs, and product recalls. Direct import programs require a level of discipline many organizations underestimate — this was my introduction to regulatory compliance, FDA’s FSMA world. When you own the product at origin, you also own the risk at origin, which means FSMA’s Foreign Supplier Verification Program (FSVP) must be supported by the process rigor of ISO 9001 and the food safety architecture of FSSC 22000. These frameworks don’t replace or depend on one another, but they strengthen the system in different ways, and understanding both is what makes a regulator effective.
A company once tried to meet FSMA obligations with surface‑level documentation and even convinced leadership that the manufacturer could write their own FSVP, that PCQIs were optional, and that they could manage their own controls and compliance. They relied on a supplier checklist that was more than three years old and SOPs that still had template brackets in them — never recognizing that ISO 9001 governs the discipline behind process control or that FSSC 22000 structures the preventive architecture needed to keep risk contained. The result was import alerts, regulatory warnings, and shipment rejections that stopped forecasted financials and halted business revenue — the natural consequence of treating origin‑level risk as something that could be delegated away.
Domestic Imports & Landed Cost: When Controls Prevent Catastrophe
Domestic import models operate in a different rhythm, but the risk profile is just as unforgiving. In a landed‑cost structure, you may not technically own the product until it arrives, but you absolutely own the consequences of everything that happens before it gets to you — and those consequences are financial. Missed controls turn into fines, rejected shipments become inventory loss, and breakdowns in oversight escalate into recalls that drain revenue and damage the brand.
A landed‑cost model creates a split‑responsibility environment where the supplier controls the product until arrival, but the retailer or importer controls the standards. When those standards aren’t enforced through a strong, shared QMS and regulatory compliance program, the gap between expectation and reality becomes a breeding ground for disaster — operationally and financially.
This one is a good news story — we can learn from those too. One team managing product across multiple states avoided a multimillion‑dollar catastrophe because their QMS wasn’t siloed; it was built by people who understood the language of trade, logistics, and overall quality. Their controls were stringent, synchronized, and holistic, and every stop in the supply chain understood the risk and implemented preventive controls. That system prevented a shipment from being loaded into a container whose walls were infested with maggots — something the shipper caught only because they inspected the container instead of loading it blindly. Had that container been used, the failure would have triggered regulatory escalation, destroyed customer trust, and cost between $2–4 million in disposal, replacement, and brand damage. The catastrophe was avoided because the controls matched the way the business actually operated — and that alignment is what prevents failures before they happen.
Mergers & Acquisitions: The Hidden Engineering Behind Quality Systems
I’ve been part of three very different M&A transitions in my career, each one teaching me a new dimension of how quality systems behave when companies move, merge, or divide. I’ve lived through a larger company acquiring a smaller one, a smaller company splitting into two distinct entities, and a small company shifting from public to private ownership. Each transition came with its own challenges — harmonization, isolation, duplication, and rebuilding of systems — and each one carried real financial consequences: stalled revenue, duplicated costs, compliance fines, inventory loss, and the expensive rework that follows when systems don’t align. Every transition proved the same truth — when the business model changes, the QMS must be rebuilt with it, or the company pays for the gap.
Harmonization During Acquisition
When a large company acquires a smaller one, harmonization becomes a structural undertaking. The first step is mapping — every SOP, form, workflow, approval path, and informal practice must be laid out side by side. This mapping exposes discrepancies between what is documented and what is actually done, revealing gaps that must be addressed before the systems can merge. When those gaps aren’t resolved, they turn into unnecessary costs: duplicated work, reissued documentation, compliance fines, and operational delays that stall revenue.
System Splitting During Organizational Division
When a smaller company splits into two, the engineering work shifts toward isolating systems and duplicating what each entity needs to operate independently. Data segregation becomes the first major challenge, requiring careful assignment of records to maintain regulatory compliance. Shared databases must be divided without compromising historical integrity. Process isolation demands dismantling shared workflows and rebuilding them so each entity can operate independently. This is where informal dependencies and undocumented responsibilities surface and must be formally reassigned. System splitting isn’t a copy‑and‑paste exercise — it’s reconstruction that requires precision, verification, and money. Every misstep becomes a cost: rework, system downtime, regulatory penalties, and inventory loss when controls fall out of sync.
Software Implementation Challenges
New software implementations during M&A transitions often fail because readiness is overlooked. Leadership may select and launch a system without aligning workflows, training teams, or establishing monitoring mechanisms. When preparation is skipped, adoption collapses. Workarounds appear, data becomes inconsistent, and processes break. Six months later, organizations often post job openings for someone to “manage the software” — not because the system is complex, but because the rollout lacked foundational support. Instead of training the employees who already understand the business, companies frequently hire new personnel to manage these systems, creating even more fragmentation and more cost.
Avoiding this requires treating implementation as a company‑wide change, not an IT project. A vendor representative should lead organization‑wide training that shows how the system works and what’s changing. Departments should have mandatory training so employees understand new workflows before they go live. Leadership must communicate the change early — what’s coming, when it’s coming, and how teams should prepare. When employees are trained, aligned, and informed, adoption stabilizes and the need for emergency hires disappears — along with the unnecessary expenses that come with them.
The Role of Subject Matter Experts
Subject matter experts (SMEs) are often removed during transitions under the assumption that documented systems are sufficient for continuity. However, SMEs carry critical undocumented knowledge, understand historical context, and maintain operational stability. Removing SMEs destabilizes systems, leading to drift, inconsistency, and incomplete training. Organizations often find themselves reposting the same roles months later, paying twice for the same capability, and absorbing the financial fallout of errors that could have been prevented had the right people remained in place.
Promotion Misalignment
Promotions granted during transitions can reveal capability gaps. Individuals may seek advancement based on tenure rather than readiness. When promoted, they may ask whether their responsibilities will remain unchanged — a clear sign of disconnect between title and operational capability. Quality management roles require system knowledge, control oversight, and the ability to manage documentation, training, and monitoring. Titles do not create capability; capability justifies the title — and misaligned promotions cost money through mistakes, rework, compliance failures, and operational slowdown.
Closing
All of these lessons — systems, controls, readiness, capability — come from years of watching organizations succeed and fail through transition. Every failure carried a price.
In my opinion, money is always best used when it’s geared toward betterment. Companies should be investing in the systems that prevent fines, inventory loss, recalls, and the unnecessary costs that come from avoidable mistakes — and investing in their people so they have the knowledge to keep the business safe.
So that’s it, my career in a nutshell — helping people prevent the mistakes I’ve witnessed, fixed, cried through, and ultimately learned from. As always, if you ever need any assistance with your operational goals, feel free to reach out.
Thanks for reading and have a productive week.