From an Idea to a Finished Product: How We Helped an Amazon Seller Develop a Children’s Product

By Vivian Pi, CEO — Select Trade

A real China product development case study from concept to sampling.

A real Amazon product development case study in China: how an Amazon seller turned a children’s product idea into a finished product through factory matching and sampling.

Client Background

Our client is an Amazon seller who wanted to develop a new children’s product inspired by an important moment in his family – the birth of his second child.

The client already had a clear vision of what he wanted, but turning an idea into a manufacturable product required much more than simply finding a factory.

The product needed to be discussed, refined, designed, sampled, tested, and modified.

The Challenge: Turning an Idea Into a Real Product

The client had many ideas about the product and continued refining the concept during development.

The challenge was to translate those ideas into something a factory could actually manufacture.

This required finding a supplier that could:

• Understand the product concept
• Communicate effectively
• Work through multiple design changes
• Develop samples
• Adjust the product according to feedback
• Produce the final product consistently

This is the point where most buyers get stuck. They have a product idea, but they do not have a manufacturer, and the two things do not connect by themselves. A factory that makes an existing product will not automatically know how to turn your concept into a production-ready item, and a buyer who has never developed a product before will not automatically know what a factory needs to hear. The gap between the idea and the factory has to be closed deliberately, and that is the work described on this page.

Our Solution: Product Development + Factory Matching

A member of the Select Trade team, Tuff, has experience with product design and helped communicate the client’s ideas into practical product requirements.

Instead of immediately choosing the first available factory, we researched suitable manufacturers and compared their capabilities.

We identified 3 potential factories and evaluated them based on:

• Manufacturing capability
• Product development experience
• Price
• Communication
• Willingness to cooperate
• Ability to make modifications

After comparing the options, we recommended the third factory.

Its manufacturing capabilities were strong, the pricing was reasonable, and its sales representative was cooperative and responsive.

If you want to see how this work fits into our wider service range, the services we offer buyers in China cover both sourcing an existing product and taking part in the development of a new one.

From Sample to Final Product

Once the factory was selected, we started the sampling process.

The development process took approximately 2-3 months.

During this period, the product went through multiple rounds of communication and modification.

The client continued to refine the details, while our team communicated the requirements with the factory and followed up on the development process.

This was not a simple:

Find Factory -> Place Order -> Ship Product

process.

It was a:

Idea -> Product Requirements -> Factory Matching -> Sample -> Modification -> New Sample -> Final Product

process.

Why Comparing 3 Factories Before You Commit Matters

A single quotation tells you what one factory thinks. Three quotations tell you what the market thinks. When we identified 3 potential factories for this project, the point was not to collect three prices and pick the lowest one. The point was to see how each supplier responded to the same concept, because the way a factory reacts to an unfinished idea tells you more than the way it reacts to a finished drawing.

Comparing several factories makes four things visible that a single supplier hides:

• How much development experience a factory really has, judged by the questions it asks about your concept rather than the claims on its website.
• How it communicates, especially when the answer is inconvenient, such as a design detail that cannot be made as drawn.
• How willing it is to make modifications, which is the single most important trait on a custom product.
• How stable the price and the plan are when the scope is still moving, rather than only when the order is fixed.

In this project, the comparison is exactly what produced the decision. The third factory was not chosen because it was first, fastest, or cheapest. It was chosen because its manufacturing capabilities were strong, the pricing was reasonable, and its sales representative was cooperative and responsive. Those are the qualities that carry a development project through the difficult middle, when the product is still changing.

What This Case Shows

Many overseas buyers have a product idea but don’t know where to begin.

They may know:

What they want the product to do

but not yet know:

How it should be manufactured.

This is where an experienced China sourcing team can add value.

We can help bridge the gap between:

Your Idea

and

A Factory That Can Actually Make It.

More Than Finding Existing Products

Traditional sourcing often starts with an existing product.

Product development starts somewhere different:

The Client’s Idea.

From there, the process may involve:

• Product concept clarification
• Factory research
• Supplier capability comparison
• Product design communication
• Prototype development
• Sample production
• Sample modifications
• Final supplier selection

The exact process depends on the product.

This is the difference between asking a supplier to quote something that already exists and asking a manufacturing partner to help create something that does not yet exist. The first is a purchasing exercise. The second is a development project, and it needs a team that can hold both the client’s intent and the factory’s constraints in the same conversation.

The Stages of Product Development in China, Step by Step

Product development is not one task. It is a chain of stages, and each stage depends on the one before it being right. This is the sequence a project like this one moves through, from a first conversation to a finished product.

1. Concept clarification. The buyer’s idea is turned into a description a factory can react to. This means stating what the product does, who uses it, roughly how big it is, what it is made of, and what it must not do. Nothing is manufactured at this stage. The goal is to remove ambiguity from the idea so that everyone is discussing the same product.
2. Factory shortlisting. A list of manufacturers that could plausibly make the product is assembled. The list is built around capability, not convenience. Not every factory that produces a similar category can develop a new item in that category, so the shortlist is a first filter, not a final answer.
3. Capability comparison. The shortlisted factories are compared on the criteria that matter for development: manufacturing capability, product development experience, price, communication, willingness to cooperate, and ability to make modifications. This is where 3 factories in this project were weighed against each other before any commitment was made.
4. DFM-style feedback. A factory that can genuinely develop a product will come back with engineering feedback rather than only a price. It will tell you which features are easy, which are difficult, which need a different material, and which will raise the cost. This feedback is the raw material of the next revision, and it is a strong signal of whether the factory is a real development partner.
5. Tooling. Where a product needs tooling, this is the stage where the physical means of production are prepared. Tooling decisions are tied to the design, so they should not be locked in before the design is stable. Understanding who controls the tooling is part of this stage, and it is covered in the pitfalls below.
6. Prototype. A first physical version of the product is produced. A prototype exists to answer questions, not to be sold. Its job is to show what the concept looks like in the real world and to expose the problems that were invisible on paper.
7. Sample rounds. The prototype is reviewed, changes are requested, and a new sample is made. A custom product normally goes through more than one round here. In this project, the product went through multiple rounds of communication and modification before it matched the client’s intent.
8. Pre-production sample. Once the design is settled, a sample is produced using the intended production method, materials, and tooling. This is the reference version: the one that defines what the shipped product is supposed to be, and the standard against which production is checked.
9. Pilot run. A small production run is used to confirm that the process holds up when it is not a one-off sample. The pilot run is where issues in assembly, consistency, or finishing usually appear, and it is far cheaper to find them here than in a full order.
10. Mass production. With the design frozen and the process proven, the product is manufactured in the agreed quantity. Production then follows the pre-production sample as the reference, which is why that sample is worth taking seriously.

The order of these stages is not decorative. Skipping concept clarification produces a factory guessing at your product. Skipping the pre-production sample produces a shipment that nobody can measure against anything. Each stage exists to catch a specific kind of mistake before it becomes expensive.

What to Prepare Before You Approach Factories

You do not need a finished product design to start a development project. You do need to be able to answer the practical questions a factory will ask. The clearer your answers, the faster and more accurately a factory can respond, and the less of the development budget is spent discovering what you actually wanted. Prepare the following before the first serious factory conversation.

• What the product does. The core function in plain language, and how a user interacts with it. This is the one item you should never leave vague.
• Who the target user is. An adult buyer and a young child user are completely different design problems, especially for a children’s product.
• Dimensions. Approximate size and weight, even as a range. Exact numbers can come later, but a range anchors every other decision.
• Material. The material you expect, or the properties you need, such as soft, rigid, washable, or lightweight.
• Safety requirements. Any safety standard the product must meet, and any feature that could create a hazard. For children’s products this is not optional detail; it shapes the design.
• Target cost. The price you need the product to land at, so the factory can tell you early whether the concept is realistic at that level.
• Packaging. How the product should be packed, including whether it is sold on a marketplace where packaging is part of the offer.
• Target market. Where the product will be sold, since the market determines which requirements apply.
• Certification needs. Any certification or compliance documentation the destination market requires for this type of product.
• Quantity expectations. A realistic sense of the volume you are aiming for, so the factory can plan meaningful production.

A simple written summary of these points is more useful than a long conversation, because it can be passed directly to a factory and compared across suppliers. It also gives you a fixed reference to update as the project develops, instead of watching the requirements drift in an email thread.

How to Tell If a Factory Can Really Develop a Product

Plenty of factories can produce an existing product to a known specification. Far fewer can take a half-formed idea and help turn it into a manufacturable item. The two skills are related but not the same, and confusing them is one of the most common reasons a development project stalls. Here is how to tell the difference.

• It asks questions before it quotes. A development-capable factory wants to understand the product before it puts a number on it. A production-only factory quotes the moment it sees anything that looks like its usual output.
• It gives engineering feedback, not just a price. Expect comments on material choice, structure, assembly, and which details will be difficult or costly. This is the DFM-style feedback described in the stages above, and it is the clearest sign of real development ability.
• It can explain why, not only what. If it proposes a change, it should be able to explain the reason. A supplier that can only say yes cannot help you improve anything.
• It is comfortable with a changing scope. Early in a project, the product is still moving. A factory that treats every change as a problem will slow the project down; a factory that treats change as normal will move it forward.
• Its development experience matches your product. Experience making a similar item is more valuable than general size. Capability that looks impressive on paper may not transfer to your category.
• Communication is responsive and consistent. In this project, the recommended factory stood out partly because its sales representative was cooperative and responsive. On a development project, responsiveness is not a soft quality; it is the mechanism by which the product improves.

The practical test is simple. Give the factory a concept that is not finished and see what comes back. A production-only factory will wait for you to complete it or quote what it assumes. A factory that can actually develop a product will start helping you complete it.

How Samples and Revisions Should Be Handled

Samples are the working language of product development. Every round should produce a decision, and every decision should be written down. If revisions are handled informally, the project relies on memory, and memory is a poor record of what was agreed and why. The goal is a product that improves with each round and a paper trail that explains the final version.

For each sample round, write down the following:

• The date of the round and which sample version it refers to, so rounds can be told apart.
• Every change you want, stated as a specific request rather than a general impression.
• Which changes are must-fix and which are nice-to-have, so the factory knows what cannot slip.
• The reason behind each change, so the factory can propose a better solution rather than a literal one.
• What the factory confirmed it can and cannot do, kept in writing.
• The outcome of the round: what was accepted, what was deferred, and what was rejected.

More than one round is normal. A custom product that is right after a single sample is the exception, not the rule, and a project that expects a perfect first sample is usually a project that will be disappointed. In this case, the product went through multiple rounds of communication and modification across the development period, and the final product reflected the client’s original concept precisely because those rounds happened.

What matters is not how many rounds occur but whether each round is moving toward a fixed target. A round that repeats the same disagreement is a sign that the requirement was never written down. A round that resolves specific, listed items is progress. Keep the written record, and the number of rounds becomes a measure of progress rather than a source of frustration.

Buyer Checklist for a Product Development Project in China

Before and during a development project, a buyer should be able to answer every item on this list. Anything left blank is a question that will have to be solved later, usually at a more expensive moment.

• A one-paragraph description of the product and what it does.
• The target user and the context in which the product is used.
• Approximate dimensions, weight, and material expectations.
• The safety requirements and any standards the product must meet.
• The target market and the certification requirements that apply there.
• A target cost the product needs to reach.
• The packaging the product requires.
• A realistic quantity expectation for the first order.
• A shortlist of factories compared on capability, not price alone.
• Written product requirements that can be shared with a factory unchanged.
• A record of each sample round, including what changed and why.
• A clear decision on who controls the tooling.
• A final pre-production sample that production will be checked against.
• One point of contact on your side for approvals.

Common Pitfalls and How to Avoid Them

Development projects fail in predictable ways. These are the mistakes that come up most often, and what to do instead.

Assuming a prototype is production-ready

A prototype looks like a product, which is exactly why it is dangerous. It is usually made by hand, outside the normal production process, and it does not prove that the item can be made consistently at scale. Treat the prototype as a question answered, not a product finished, and expect a pre-production sample and a pilot run before mass production.

Skipping written specifications

Verbal agreements feel faster and then cost far more. If the requirement only exists in a conversation, the factory is free to interpret it, and you have no record to compare a sample against. Write the specification down, share it, and keep it updated as the product changes.

Expecting unlimited free revisions

Revisions should be normal and expected, but treating them as unlimited and free creates the wrong incentives and can sour a good relationship. Separate the changes that fix a genuine problem from the changes that are simply new preferences, be honest about which is which, and keep each round specific and written down.

Choosing on price alone

On a development project, the cheapest quotation is often the one from the supplier least able to help you develop the product. Price matters, but it belongs in a comparison that also weighs capability, development experience, communication, and willingness to modify. In this project, the factory that was recommended was chosen on that fuller set of reasons, not on price alone.

Tooling ownership confusion

If tooling is made for your product, who owns it and who controls it should be settled in writing before it is built. Without that clarity, a change of factory becomes far harder than it needs to be, because the means of production may not be yours to take with you. Agree the ownership question early, while it is still a simple question.

Buying an Existing Product vs Developing a Custom Product

The two paths to a product from China are not variations of the same process. They start in different places and they demand different work. This is where they diverge.

Aspect	Buying an existing product	Developing a custom product
Starting point	A product already exists and is in production. You choose from what suppliers offer.	Your own idea. Nothing exists until the concept is clarified and made manufacturable.
Factory selection	You match a supplier to a product that is already being made.	You compare factories on development experience, communication, and willingness to modify, not only capacity and price. In this project, 3 factories were compared before one was recommended.
Tooling and samples	Tooling already exists. Samples are usually units of an existing item.	Tooling and samples have to be developed. The product may go through multiple rounds of modification before it is right.
Time to first order	Generally faster, because the item already exists and only needs to be ordered.	Longer, because the product has to be built first. In this project, development took approximately 2-3 months.
Differentiation	Low to moderate. Other sellers can buy the same product from the same type of supplier.	Higher. The product is based on your own concept and can be shaped to your market.
Risk	Lower technical risk, but higher commercial risk from competing on an identical product.	More technical risk during development, but the result is a product built around your idea rather than one shared with everyone.
Who does the work	The supplier. You place an order and receive goods.	Shared. You define the concept and requirements; the sourcing team translates them into factory requirements and follows the development through.

Neither path is better in the abstract. The choice depends on whether you want to sell something that already exists or build something of your own. What this case shows is that the second path is open even to a buyer who arrives with an idea and no finished design.

Frequently Asked Questions

Can a factory develop a product from my idea?

Yes, provided you approach the right kind of factory. A factory that can actually develop a product will ask questions about your concept, give engineering feedback rather than only a price, and work through multiple design changes. A production-only factory will typically wait for you to complete the design or quote based on its usual output. The work is to find the first kind, which is what factory comparison is for.

How long does product development in China take?

It depends on the product. In this case, the development process took approximately 2-3 months, during which the product went through multiple rounds of communication and modification. The timeline is driven by how many changes the product needs and how quickly decisions are made on the buyer’s side, which is why written requirements and fast feedback matter so much.

What do I need before contacting a factory?

You need to be able to describe the product in practical terms: what it does, who it is for, roughly how big it is, what it is made of, any safety requirements, your target cost, the packaging, and the target market with any certification needs. You do not need a finished design. A short written summary of these points is enough to start a serious conversation.

Do I need a full design before starting?

No. That is one of the main points of this case. The client arrived with a clear vision and continued refining the concept during development, and the final product still reflected the original idea. A completed design is not a prerequisite for starting. What is needed is a clear enough concept that a factory can react to it and a willingness to refine the details as the project moves forward.

How many factories should I compare?

Enough to see differences in capability, communication, and willingness to modify. In this project, 3 potential factories were identified and evaluated against the same criteria, and the third was recommended because its manufacturing capabilities were strong, its pricing was reasonable, and its sales representative was cooperative and responsive. Comparing several suppliers on the same terms is what makes a recommendation meaningful rather than a guess.

What is the difference between a prototype and a sample?

A prototype is an early physical version made to test and discuss the concept, often by hand and outside normal production. A production sample, and especially the pre-production sample, is made using the intended production method, materials, and tooling, so it represents what the finished product will actually be. The prototype answers whether the idea works. The pre-production sample defines what production must match.

Related guides

• More China sourcing and product development success stories
• Our sourcing and product development services
• What a China sourcing agent actually does

Need Help Developing a Product in China?

If you have a product idea but don’t know which factory can make it, Select Trade can help you evaluate the project and identify suitable manufacturing partners in China.

You don’t need to have everything figured out before contacting us.

Whether your starting point is a finished design, a rough concept, or a product you already sell, we can help you compare factories, communicate requirements, and follow the development through to a manufacturable product. Send us your idea and we will tell you how a project like this one would be run for your product: contact Select Trade.

Have a Product Idea? Send Us Your Idea →