Why There's No Single "Right" Way to Source Face Cleansers

I've been managing our skincare procurement budget for six years—roughly $340,000 in cumulative spending across cleansers, serums, and masks. Every new hire on our product team eventually asks me the same thing: what's the best way to source a face cleanser?

Honestly? There isn't one. I've watched brands blow their margin over-engineering a basic gentle face cleanser, and I've watched others lose a retail account because they cut corners on stability testing.

The right path depends on your scenario. Here's how I break it down.

The Three Sourcing Scenarios (And Why They're Not Interchangeable)

Most B2B buyers I talk to fall into one of three buckets:

  • Scenario A: Market testing — you're launching your first (or second) cleanser and need to validate demand before committing.
  • Scenario B: Catalog expansion — you have an established brand and want to add a face cleanser for men, a hydrating facial cleanser, or an oil face cleanser to an existing lineup.
  • Scenario C: Niche positioning — you're building around a specific claim, like a facial cleanser for sensitive skin.

These aren't interchangeable. The formulation decisions, the MOQ math, and even the supplier profile you should be looking for are different in each case. Let me walk through them.

Scenario A: Market Testing — Prioritize Flexibility Over Unit Price

If you're testing the market, the temptation is to chase the lowest unit cost. I've done this. In 2023 I went with a supplier who quoted about 22% less per unit than my backup option, mostly because I could hit a lower MOQ.

That was a mistake.

What I didn't account for: their spec sheet flexibility was basically zero. When we wanted to tweak the surfactant level after the first sample round, they treated it like a new order. New setup fee, new timeline, new minimum. By the time we got what we wanted, we'd paid more than the "expensive" quote would have cost—and we lost six weeks.

For a market test, the metric that matters isn't cost per unit. It's cost per learning cycle. You want a supplier who can iterate with you on sample formulations without treating every change as a new project.

What to look for:

  • Low MOQ for the first run (don't commit to 5,000 units before you have data)
  • Willingness to do two or three sample iterations
  • Clear pricing on reformulation before you sign

Yes, you'll probably pay a premium per unit. That premium is the price of optionality, and in this scenario, it's usually worth it.

Scenario B: Catalog Expansion — Standardize Before You Customize

This is where most of the "which supplier is best" debates actually happen. You already have a brand, you already have customers, and now you're adding a gentle face cleanser or a hydrating facial cleanser to the line.

The conventional advice is that custom formulation is always better. I don't agree—not at this stage.

Here's why. When I expanded our line in 2024, I compared custom development against two white-label bases. The custom route quoted roughly 40% higher per unit, plus setup. The white-label bases were ready to ship.

We went with one white-label base for the first six months, and it did fine. Customer reviews were solid. Once we had data showing which SKU actually moved, we invested in custom formulation for that one and left the rest on the base.

Customizing everything at once is a great way to spend money on SKUs that might not survive their first quarter.

A practical note on the men's and hydrating categories: many suppliers put these on the same base formulation with different fragrance and packaging. That's fine for a market entry. But check the actual INCI—audit the ingredient list against what you're claiming on the front of the bottle. If the label says hydrating, the humectant load should support that. If it says for men, you'd better have a reason beyond a blue label.

Scenario C: Niche Positioning — Testing Isn't Optional

If you're building around sensitive-skin positioning, the cost calculus changes entirely.

This is where I'll push back on the standard procurement instinct. Everywhere else, I'll tell you to shop the quote. Here, shop the compliance file first.

A supplier with a strong stability testing protocol, clear microbiological limits, and documentation that stands up to retail audits will cost more. It should cost more. If someone quotes you a facial cleanser for sensitive skin at the same price as a general-use product with no additional testing, ask what they're skipping.

Two things I'd verify before signing anything:

  • Regulatory positioning. In the US, FDA draws a line between cosmetics and drugs based on intended use. Claiming a cleanser "treats" or "heals" anything pushes it into drug territory and triggers a different compliance regime. Make sure your supplier understands where the line is, because your brand eats the consequences if they don't. (Verify current FDA guidance at fda.gov; regulations change.)
  • Stability and compatibility data. Especially for sensitive-skin or oil-balance claims. Ask for the testing file, not just a summary.

I have mixed feelings about how much this costs. On one hand, it feels like you're paying for paperwork. On the other, I've watched a competitor get a product pulled from a major retailer over a claim their supplier told them was fine. The testing file is cheaper than the recall.

How to Tell Which Scenario You're In

This is the part most sourcing guides skip. They give you the scenarios and leave you to guess. Here are the three questions I actually use:

  1. Do I have sales data on this exact category yet? If no, you're in Scenario A. Don't overinvest in a product line without a baseline.
  2. Is my existing brand carrying this product, or is the product defining the brand? If the brand carries it, you're in B. If the product defines the brand—like a sensitive-skin specialist line—you're in C.
  3. Would a compliance failure kill this product line? If yes, you're in C regardless of what the other answers say. Regulatory risk overrides procurement cost logic.

You can be in different scenarios for different SKUs at the same time. We've got two SKUs in B and one in C right now. That's normal.

The mistake is choosing a supplier strategy before you know which scenario you're in. That's how you end up paying custom-development prices for a market test, or white-label prices for a product that needs regulatory cover.

Bottom line: figure out your scenario first. Then cost the sourcing around it.