A supplier introduction email has one job: make it easy for the right supplier to decide whether it can help you.
It is not your life story. It is not a five-line “Please send your best price” message. And it is not a full production contract hidden inside a long email thread.
A good first message tells a supplier who you are, what you need, how far along the product is, and what you want back from them. It gives enough context for a useful reply without demanding a final price from a factory that has not yet seen the real requirements.
That balance matters. Thomas recommends keeping supplier requests simple to follow, limiting the information you ask for at the first stage, and structuring the request so a supplier can understand the buyer’s need quickly. [1] The clearer the first contact, the easier it is to spot suppliers that understand the product and ask sensible questions in return.
Know what the first email is for
Before writing, decide whether you are opening a conversation or asking for a formal quote.
An introduction email is useful when you have identified a supplier that might fit your product but still need to understand its capabilities, interest, order requirements, sample process, or preferred way to review your idea. It is an early screening step.
A formal RFQ is different. It asks a supplier to price a defined specification. An RFP asks a supplier to propose an approach to a broader problem. If you ask for a final unit price before you have explained the product, quantity, packaging, and quality requirements, the number you receive may be based on assumptions you do not share.
Order.co describes an RFI as an early request for information that helps buyers determine whether suppliers meet initial evaluation criteria before they move into more detailed requests. [2] Your introduction email can work like a short, practical RFI. It should help you decide whether a supplier deserves a deeper conversation, not pretend that the sourcing decision is already complete.
When you are ready to ask for a formal price, use Sourcing All’s guide to RFQs versus RFPs for product sourcing to choose the right request format.
Start with a subject line that says what you need
Suppliers receive many messages that say only “Hello,” “Cooperation,” or “Looking for a partner.” Those subject lines give the recipient no reason to open the message first.
Use a direct subject line that identifies the product category and the reason you are writing. It does not need to sound clever. It needs to make the email easy to route to the right person.
| Weak subject line | Clearer alternative |
|---|---|
| Inquiry | Initial enquiry: custom insulated bottle manufacturing |
| Cooperation request | Supplier introduction: branded travel organizer project |
| Need price | Capability enquiry: sewn pet carrier with custom packaging |
| Hello manufacturer | Product enquiry: injection-moulded storage case, sample and MOQ questions |
If you know the recipient’s name, use it. If you only have a general sales inbox, a professional greeting is enough. Avoid pretending that you have reviewed a supplier’s entire company when you have only seen a directory profile. A simple “I found your company while researching manufacturers for [product category]” is honest and clear.
Put the essential information near the top
The first paragraph should allow the supplier to answer four questions quickly: who is writing, what product is involved, what stage the project is at, and why this supplier might be relevant.
For example:
Hello [Name],
My name is [Name], and I am [role] at [company]. We are developing a [plain-language product] for sale in [target market]. We found your company while looking for suppliers with experience in [relevant process, material, or product category]. We would like to understand whether this project is within your manufacturing capability.
That is enough for an opening. You do not need to claim that your company will place a huge order if you cannot support that statement. You also do not need to hide that you are early in development. State the stage honestly: concept review, prototype, sample revision, or a defined product ready for quotation.
Thomas advises including buyer contact details and, when technical questions may arise, a technical contact who can address them. [1] Add your company website if it is available and relevant, but do not make a website a test of whether you deserve a response. The product information in the email matters more.
Describe the product in plain language first
A supplier should not have to open five attachments to understand the basic idea.
Give a short product summary in the email body. Explain the intended use, the main material or process if known, the most important feature, and the approximate order profile. A few lines are usually enough.
For a custom product, Thomas lists useful RFI inputs such as performance or environmental specifications, drawings or schematics, the intended application, production-run type, quantity, and the date by which the buyer needs a response. [1] You do not need every item in the very first message. Include the information that will help the supplier say whether the project fits, then attach the supporting material it needs to look more closely.
A simple product summary might read:
We are developing a 500 ml insulated stainless-steel bottle with a powder-coated exterior, laser logo, and individual retail box. The first order is expected to be approximately [quantity], subject to sample approval. We have reference images and a preliminary packaging layout attached. Please let us know whether you have experience with this product type and which details you would need before reviewing feasibility.
The supplier can now see the product category, material, decoration method, packaging expectation, quantity range, and the question you need answered. That is far more useful than “I want to make a high-quality bottle. Please quote.”
State what is fixed and what is still open
Early product conversations often go wrong because buyers do not say which details are non-negotiable.
Make two short lists in the email or attachment. The first list covers fixed requirements: product function, size limit, target material, brand elements, target market, or deadline. The second covers open questions: preferred construction method, material alternatives, packaging options, tooling approach, or sample route.
This gives the supplier room to contribute without inviting it to quietly replace the essential product. It also makes the first reply more useful. A capable supplier may say, “We can make the product, but the requested finish needs a different coating process,” instead of issuing a quote for something that only looks similar.
If the product is still only an idea, prepare a short concept note before you email suppliers. The guide on finding a manufacturer for a new product idea explains how to build a manufacturer search brief and shortlist candidates before your outreach becomes too broad.
Use attachments to support the email, not replace it
Attachments are valuable when they remove ambiguity. They are less useful when they are an unlabelled folder of images, screenshots, and file names such as “new final final 3.”
Name each file clearly. A supplier should be able to see what it is and why it matters before opening it. For example: Product-concept-v1.pdf, Reference-images.pdf, Bottle-dimensions-v1.pdf, or Packaging-layout-draft.pdf.
In the email body, list the attachments and explain what the supplier should review. If you are sending a drawing, say whether it is for dimensions, overall shape, or a production-ready design. If you are sending a reference product image, say which features are relevant and which are not. An image can show style, but it may not reveal material grade, wall thickness, internal construction, or performance requirements.
Do not send sensitive files to a broad, unqualified list simply because you want quick replies. Start with the information needed for initial capability screening. Share more detailed files as the supplier becomes a credible candidate and the appropriate business protections are in place.
Ask questions that move the conversation forward
A first message should invite a useful response. It should not read like an exam with 30 questions.
Choose a few questions that tell you whether the supplier is relevant. The exact questions will depend on the product, but the following set works for many custom-product enquiries:
- Do you manufacture this product type directly, or do you source it through another company?
- Which similar materials, processes, or product categories do you handle?
- Is the attached concept within your usual capability? If not, which part is outside your scope?
- What information would you need before reviewing sample feasibility or preparing a formal quotation?
- What is the usual sample path for a product like this, including any likely tooling or set-up step?
- What initial quantity range is practical for your production process?
- Who should receive technical follow-up questions from our side?
Order.co recommends giving suppliers project context, timing, essential parameters, and clear response guidance, while leaving room for relevant supplier input. [2] That is why an open question such as “What do you need from us to assess feasibility?” belongs in the first email. It lets the supplier show how it thinks about the work.
Give the supplier a clear response request
Do not make the supplier guess what a good reply looks like. End with a short, specific request.
For example:
Please reply by [date] to confirm whether this product is within your capability, identify any missing information, and share the best contact for technical review. If the project looks suitable, we can then send the full product brief and discuss the sample process.
A response date is helpful when you are contacting several suppliers, but make it realistic. Thomas includes a requested response date among the information to include in standard and custom-product information requests. [1] The date tells suppliers how to prioritize the request and helps you keep the research process moving.
Give one response channel. If you want the supplier to reply by email, say so. If a sales contact and a technical contact are both involved, tell the supplier whom to copy. Simple instructions reduce back-and-forth before the product conversation even starts.
A supplier introduction email template
Use this template as a starting point. Replace every bracketed item before sending it. Remove any line that does not apply to your product.
Subject: Initial enquiry: [product category] manufacturing capability
Hello [Name],
My name is [your name], and I am [role] at [company]. We are developing a [plain-language product] for [target market or intended use]. We found your company while researching suppliers with experience in [product category, process, or material].
The project is currently at the [concept / prototype / sample revision / quote-ready] stage. The main requirements are [two or three fixed requirements]. We are also open to your advice on [one or two genuine open questions].
Our expected first order is approximately [quantity or range], subject to sample approval. The current target timing is [timing, if relevant].
Attached are [list attachments] to explain the concept. Please confirm whether this product is within your manufacturing capability. If it is, please let us know:
- Whether you manufacture this product type directly;
- Which details you would need before reviewing feasibility or preparing a formal quote;
- Your likely sample and production steps for a project like this; and
- The best contact for technical follow-up.
Please reply by [date], if possible. Thank you for your time.
Kind regards,
[Name]
[Role and company]
[Email] | [Phone or messaging contact] | [Website, if relevant]
This template does not guarantee a reply. It does give a relevant supplier a straightforward way to decide whether and how to respond.
Change the email for the stage of your project
The message should match the maturity of the product.
If you are at the concept stage, ask about relevant experience, process fit, material options, and the information needed for feasibility. Do not ask for a final price.
If you have a prototype, explain what it proves and what it does not. For example, the prototype may confirm product size and function but not the final material, tooling method, or production cost. Ask whether the supplier can review the prototype against its production process.
If the specification is ready, keep the introduction brief and move toward a formal RFQ. State that a structured product brief is attached or available and ask the supplier to confirm it can quote the defined scope. A formal request should make it easier to compare supplier replies, not create three different versions of the product.
Avoid these first-email mistakes
The most common problem is being too vague. “Please quote your best price” gives a supplier no product version, quantity, packaging scope, or quality requirement to price.
The second problem is sending too much too soon. A long message with every possible question, five unlabelled attachments, and no clear priority may delay a reply or produce a confused response. Thomas and Order.co both stress that information requests should be structured, easy to follow, and focused on the information needed at that stage. [1] [2]
The third problem is assuming that a fast answer proves capability. A supplier may respond quickly because it has a standard item ready to sell. That can be useful, but it does not show that the product matches your custom requirements. Read the response carefully. Does it address your actual product? Does it identify unknowns? Does it suggest a sensible next step?
Finally, remember that an introduction email is only the opening of the sourcing process. A clear email can lead to better information. It cannot replace supplier verification, sample approval, a complete specification, agreed commercial terms, or a purchase order.
A good supplier introduction email is simple, specific, and honest about the stage of the product. It helps the right factory or supplier understand the opportunity and helps you see which replies deserve a closer look. That is the real goal of the first message.
References
[1] Thomas, “Tips for Writing Effective RFIs”
[2] Order.co, “RFI Meaning: Plus How It Compares to an RFP, RFQ, and RFT”