"Why Your Samples Keep Getting Rejected?" 3 Communication Pitfalls 90% of Brands Fall Into
- DEVA Skincare

- Jun 22
- 7 min read
If you are experiencing this cycle—receiving the first sample and saying "it's not quite right," the second sample improving the texture but the color being "off," and the third sample fixing the color but feeling "less smooth than the previous version"—then this article is written exactly for you.
Repeated sample revisions are not an isolated incident; they are a widespread industry phenomenon. Cross-industry project management data shows that 37% of project failures are directly attributed to inaccurate requirement gathering, and 66% of organizations state that unclear requirements are one of the most common causes of project delays. This rule maps perfectly onto the cosmetic OEM/ODM sampling scenario: the vast majority of repeated revisions stem not from a lack of R&D capability, but from systemic deviations in communication itself.
Furthermore, communication breakdowns are cited in as high as 57% of all project failure cases, far exceeding technical or resource issues. This means that compared to improving R&D strength, improving communication methods is often the item with a much higher return on investment when it comes to solving the problem of sample revisions.
Today, from the real-world perspective of an OEM/ODM R&D team, we will deconstruct the three communication pitfalls that 90% of brand owners unconsciously fall into when submitting sample requests.

Pitfall 1: Using "Adjectives" Instead of "Parameters", Leaving R&D to Guess
This is the most frequent and most fatal pitfall.
A brand owner says: "I want a refreshing, non-greasy face cream. The texture should be lightweight, and it should absorb quickly."
Sounds clear, right? But to an R&D engineer, there is not a single piece of information in this sentence that can be directly translated into a formulation decision.
"Refreshing" could correspond to: a water-in-oil emulsion with a low oil phase ratio, a lightweight formula containing volatile silicones, or a water-gel cream with a high proportion of a plant-based water base. These are three completely different technical paths, each yielding a different skin feel.
"Lightweight" might be understood by R&D as a viscosity below 500 cps, while what the brand owner has in mind might be a product with a viscosity of 2000 cps but excellent spreadability. In a professional context, these are completely different concepts.
This "translation loss" is the root cause of repeated revisions in the industry. Unclear or constantly changing requirements are the main cause of project chaos and rework. This rule holds true for cosmetic sampling: to avoid "guessing the wrong direction," R&D teams will often choose the most conservative, conventional formulation path. The result is a finished product that is far from the brand owner's true imagination.
How to Solve It:
Use quantified sensory dimensions instead of subjective descriptions. For example, break down "refreshing" into: spreadability (rated 1-5), absorption speed (disappears within how many seconds), residual feel (presence or absence of an oily film), and hydration longevity (how many hours without tightness). This scale allows the R&D team to precisely capture the direction you truly want, rather than relying on guesswork.
Provide an "acceptable deviation range." Telling the R&D team, "The texture can be slightly heavier, but it absolutely cannot feel sticky," conveys much more information than simply saying "refreshing." It effectively tells the R&D team "where compromises can be made, and where they absolutely cannot."
Pitfall 2: Blurring the Lines Between "Requirements" and "Market Research"
The second frequent pitfall occurs when brand owners habitually mix "there is a trend in the market" with "I want this feature" when communicating requirements, failing to draw clear priority boundaries.
A typical scenario looks like this: At a briefing, the brand owner says, "Hyaluronic acid is very hot right now, and niacinamide is also very hot. Our product should ideally cover all these trending ingredients so the market response will be better."
This statement contains a common misconception: mistaking "industry trend observations" for "product technical specifications," without telling the R&D team:
Among these ingredients, which one is the core positioning of the product (the effect that must be achieved)?
Which one is just a "bonus feature if the budget allows"?
Do these ingredient combinations have any formulation compatibility issues (e.g., certain active ingredients having conflicting pH windows)?
When requirements are mixed with a lot of "maybe we can add this" information without a clear priority ranking, the R&D team will often make trade-offs based on their own judgment. And this judgment is very likely to be completely misaligned with the brand owner's true priorities. The result: after the first sample is made, the brand owner realizes, "This isn't the main focus I wanted," and the revision cycle begins.
Cross-disciplinary project management research shows that 38% of project failures stem from changes or lack of clarity in organizational priorities. This rule applies perfectly to the sampling scenario: when the brand owner themselves has not clarified the boundary between "must-have" and "nice-to-have," the R&D team cannot possibly guess the correct answer.
How to Solve It:
Tier your efficacy requirements. When submitting requirements, clearly label: Core Efficacy (the non-negotiable selling point of the product), Bonus Efficacy (prioritized if budget and formulation allow), and Explicitly Excluded Directions (even if generally considered good, it is not needed in this product).
Separate "market research" from "product requirements." If you want the R&D team to understand market trends as a reference, state separately, "This is background information, not a hard requirement," to prevent R&D from misjudging priorities.
Pitfall 3: Treating the "First Sample" as the "Final Acceptance Standard" and Lacking an Iterative Communication Mechanism
The third pitfall occurs after the sampling process has already begun, rather than during the requirement submission phase.
Many brand owners, upon receiving the first sample, habitually give a binary judgment of "satisfied" or "not satisfied," without specifying which dimension needs adjustment or what the direction of adjustment should be. For example, providing feedback like "it just doesn't feel right" without further breaking down whether the texture, scent, or color is wrong.
Upon receiving such feedback, R&D engineers can often only guess and make comprehensive adjustments across the board—they might change the texture, fragrance, and active ingredient concentration all at once. When the next sample is delivered, the brand owner might feel, "The changes are too drastic this time, and some parts I liked before are gone."
This cycle of "vague feedback → comprehensive adjustment → new dissatisfaction" is the core mechanism behind out-of-control sampling rounds. In the collaboration between R&D and marketing teams during new product development, the marketing team often underestimates the real time required for sample adjustments, leading to misaligned expectations regarding the project timeline. This misunderstanding accumulates, causing a massive amount of unnecessary rework.
How to Solve It:
Use a structured feedback form instead of subjective evaluation. After receiving the sample, rate and comment on dimensions such as spreadability, absorption speed, fragrance, color, and packaging experience separately. Clearly state, "This dimension is satisfactory, keep it," or "This dimension needs adjustment, and the direction of adjustment is..."
The Unified Logic Behind the Three Pitfalls: Minimizing "Translation Loss"
Looking back at these three pitfalls, they all share the same core logic:
Brand owners think about products in "feeling language," while R&D teams make products in "parameter language." Sample revisions are, at their core, the translation loss between these two languages.
Pitfall 1 is "Input Translation Loss": Adjectives cannot be accurately translated into formulation parameters.
Pitfall 2 is "Priority Translation Loss": Un-tiered requirements cannot be correctly prioritized for execution.
Pitfall 3 is "Feedback Translation Loss": Vague evaluations cannot be translated into precise adjustment actions.
The core method to reduce translation loss is never to demand that brand owners become professional formulators. Instead, it is to use more structured methods to translate "feelings" into a language R&D can understand: reference products, quantified sensory ratings, tiered requirement lists, and focused feedback.
What Does This Mean for You?
If you are communicating with an OEM about new product sampling, ask yourself these three questions before submitting your next requirement or feedback:
Am I using adjectives or parameters? Can I replace them with a reference product or a quantified rating?
In my requirements, which are "must-haves" and which are "nice-to-haves"? Have I clearly labeled them?
Is my feedback on this sample specific enough? After reading it, will the R&D team know exactly what to change next, rather than having to guess?
If the answer to all three questions is "yes," your sampling process will likely be much faster than in the past.
Are you looking for a reliable Skincare factory?
Are you seeking a trusted partner to launch or scale your skin care line? At Deva Skincare,we specialize in developing safe formulations that combine barrier science with clean, compliant manufacturing.
Our R&D team and certified production facilities deliver turnkey OEM/ODM solutions tailored to your target market’s regulatory and consumer expectations.
By collaborating with Deva Skincare, you gain access to industry-leading expertise and innovative formulations that set your brand apart in the competitive global market. Contact us today to discover how we can help you succeed.
Final Thoughts: Good Communication is the Greatest Lever for R&D Efficiency
Repeated sample revisions consume not only time but also the team's patience and mutual trust in each other's capabilities.
Truly changing this often does not require switching to a more expensive OEM or acquiring more advanced R&D equipment. It only requires making systematic adjustments to the way we communicate.
As an OEM, we are also continuously optimizing our own requirement-gathering processes, providing structured requirement forms and sensory rating templates. We hope to minimize this "translation loss" from our end as much as possible. But ultimately, this is a two-way collaboration: when the brand owner speaks clearly, the R&D team can execute precisely, and sampling can truly become efficient.
If you are preparing to develop a new product or are currently struggling with repeated sample revisions, please feel free to contact our R&D team. We will use structured requirement-gathering methods to help you translate "the feeling I want" as precisely as possible into "the product we can make." Deva Skincare



Comments