-
There's no single 'best' nonwoven supply model
-
First, a specification reality check
-
Scenario A: You need speed more than customization
-
Scenario B: You need OEM but you're not ready for co-development
-
Scenario C: You're large enough to co-develop
-
How to figure out which scenario you're actually in
-
One last thing about supplier selection
There's no single 'best' nonwoven supply model
I've sat on both sides of this decision—first as a buyer evaluating hygiene nonwoven suppliers, now as the person who rejects entire batches when the spec is off. And the one thing that frustrates me most is how many articles pretend there's a universal answer to "OEM or private label?"
There isn't.
The right model depends on three variables: your order volume, your timeline pressure, and how much of your brand promise depends on the fabric itself. Get those wrong, and you'll either overpay for customization you can't leverage, or you'll ship a product that fails your own QC standards.
I'm going to walk through the three scenarios I see most often. Not generic advice—actual decision trees, with the specification traps and cost structures that separate a good outcome from an expensive lesson.
Quick caveat: I work in quality and brand compliance, not procurement. My perspective is filtered through the rejection letters and rework invoices I've signed off on. So if you're looking for someone to tell you "just pick the cheaper option," you're reading the wrong article.
First, a specification reality check
Before you even start comparing suppliers, you need to understand what "spunbond nonwoven" actually means on a spec sheet. It's a family of technologies—SSS, SMMS, SMS, meltblown, spunbond—and the performance gap between them isn't incremental. It's structural.
Most buyers I've worked with don't realize this until they've already signed a contract. They see "spunbond" and assume it's all the same. It's not.
Here's the practical breakdown:
- SSS (spunbond-spunbond-spunbond): Good tensile strength, breathable, lower barrier. Fine for dry wipes or light-duty hygiene applications.
- SMS (spunbond-meltblown-spunbond): Adds a meltblown barrier layer. This is where medical-grade applications start. If you're making surgical drapes or isolation gowns, you need at least this.
- SMMS: Two meltblown layers. Better barrier, slightly lower breathability. Used in higher-risk medical applications.
- Meltblown alone: The finest fibers—best filtration and barrier, lowest strength. Usually laminated or combined with spunbond.
When I specify requirements for our medical clients' orders, the first question I ask is: "What's the performance you actually need, not the performance you think you need?" Half the time, they're specifying SMMS when SMS would pass their internal testing at 20% lower cost.
The other half, they're specifying SSS for an application that really needs a meltblown barrier layer—and they don't find out until their first regulatory audit.
So before you decide OEM vs private label, lock your spec tier. Because that decision changes the supplier pool dramatically.
Scenario A: You need speed more than customization
This is for: Startups, seasonal product launches, test-market runs, or anyone placing their first order with a new supplier.
If your timeline is measured in weeks and your primary goal is getting a product to market without a six-month development cycle, private label or white-label is almost always the right call.
Here's why: private label means you're buying a supplier's existing spec. No custom formulation, no new production run setup, no minimum order quantities that require a second mortgage. You pick from their catalog, they ship it with your branding on the packaging.
The trade-off: You get what they have, not what you might ideally want. And that 's generally fine if your product doesn't compete on fabric performance.
But here's where the quality side of my brain kicks in. In our Q1 2024 quality audit, I reviewed 200+ nonwoven batches across three suppliers. The private-label batches had the highest spec variability—not because the suppliers were bad, but because private label often uses shared production runs. If the supplier switches base materials mid-run to reduce their own costs, your spec can drift without anyone telling you.
That doesn't mean all private label is risky. It means you need to lock your acceptance criteria into the contract, with a defined sampling protocol.
My recommendation if you're in this scenario:
- Ask for a pre-shipment sample from the actual production run, not a lab sample. Lab samples aren't production samples.
- Specify your key performance thresholds: hydrostatic head (for barrier), tensile strength (MD and CD), and air permeability. Add a baseline: "No deviation greater than 10% from approved sample."
- Request the supplier's quality certificate for the specific run, not a general compliance statement.
One thing most buyers don't realize: if you're buying private label from a distributor, they may not know the exact production parameters themselves. They're often one step removed from the actual mill. Ask who the actual manufacturer is. If they won't tell you, that's a red flag.
Scenario B: You need OEM but you're not ready for co-development
This is for: Established brands with specific product requirements, mid-volume runs (roughly 50,000 to 500,000 units annually), and teams that know what they need but not necessarily how to get there.
OEM means the supplier produces to your specification, under your brand. You define the fabric properties, the packaging, the labeling. They make it. You own the design and the brand equity.
This is where most of the supplier evaluation articles get it wrong. They treat OEM as the "premium" option. It's not premium—it's different. And for a lot of brands, it's the wrong fit for reasons that have nothing to do with cost.
I went back and forth between recommending OEM and private label for one of our hygiene clients for nearly three weeks. On paper, OEM looked right—they had a specific softness and drape requirement for a premium wipe product. But their volume was borderline, and the OEM tooling would've added roughly $8,000-12,000 in NRE charges, with a 10-12 week lead time.
Ultimately, we went private label with a custom converter step (they bought base roll stock and had it converted). It gave them 80% of the customization at 30% of the cost. Not the "ideal" solution, but the right one for their situation.
What to watch for in OEM:
- NRE charges are real. Non-recurring engineering costs for spunbond OEM typically range from $5,000 to $25,000 depending on complexity, plus sampling fees. Get these itemized before you commit.
- Volume commitments matter. Most OEM agreements include minimum annual volumes or take-or-pay clauses. If you're not confident in your demand forecast, this can become an anchor.
- IP ownership needs to be explicit. Who owns the fabric specification after the contract ends? If you're not careful, your custom spec can end up in the supplier's catalog, sold to your competitor. This happens more than anyone admits.
And here's the insider knowledge that took me years to learn: the OEM supplier's "standard" production spec is often not as tight as their lab sample suggests. What they send you for approval is a controlled lab run. Production runs have wider tolerances. Always specify your acceptance criteria based on production capability, not lab capability. If they can't meet it in production, find out before the first container ships.
Scenario C: You're large enough to co-develop
This is for: Brands with significant volume (typically 1M+ units annually), dedicated R&D resources, and a product strategy where the fabric is a core differentiator.
This isn't really "OEM vs private label" anymore—it's a partnership model. You're not just buying a spec, you're building one together.
I'm going to say something that might be unpopular: Most companies that think they're in this scenario aren't. They're reverting to OEM because they think co-development sounds more strategic.
The problem is that co-development requires resources: dedicated quality engineering on your side, consistent communication, and a willingness to absorb the cost of experimentation. If you're not prepared for 6-12 months of development cycles and shared IP negotiations, you'll end up with an expensive version of Scenario B.
If you are genuinely in this scenario, the supplier relationship looks different. You'll have quarterly business reviews with technical teams, not just sales. You'll co-invest in tooling. You'll have a shared quality dashboard.
And the fabric will be genuinely custom—not just a tweaked catalog spec. When companies like Freudenberg or their peers develop a new nonwoven for a specific partner, it's a multi-team engineering project. That's not a transactional relationship.
The transparency angle here matters most. I've learned to ask "what's NOT included" before I ask "what's the price." In co-development, the supplier who lists all the development milestones, testing costs, and IP terms upfront—even if the total looks higher—usually costs less in the end because you're not absorbing surprises three months in.
How to figure out which scenario you're actually in
Ask yourself three questions, honestly:
- Does your fabric spec give you a competitive advantage?
- Can you commit to a volume that justifies custom tooling or development investment?
- Do you have internal resources (time, technical staff, budget) to manage a development cycle?
If you answered "no" to any of these, you're probably in Scenario A, even if your volume suggests otherwise. That's not a failure—it's a realistic assessment.
If you answered "yes" to all three but you're not sure about the development timeline commitment, Scenario B is your safest path. You can get OEM quality without the co-development overhead.
And if you answered "yes" to all three and you have the internal bandwidth to manage a 6-12 month development cycle, Scenario C is where the real differentiation happens.
One last thing about supplier selection
No scenario excuses you from doing supplier verification. I've rejected first deliveries from suppliers I'd used for years—because they quietly changed a sub-supplier or shifted a production line without notifying us.
The best protection isn't the contract language. It's a pre-production sample, a defined acceptance protocol, and a shipment hold until you've verified the first container meets spec.
That adds a week to your timeline. It's worth it every single time.
