Buying Guide
How to prepare a product RFQ that sellers can answer
By Cusket Editorial · Published · Updated
Build an RFQ that sellers can quote without guessing: specs, quantities, acceptable alternatives, delivery assumptions, quote fields, and decision criteria.
Why most RFQs get weak replies
A request for quotation is not just a message asking for price. In B2B buying, the RFQ is the working brief that tells the seller what to quote, what assumptions to use, and what proof the buyer needs before moving toward an order. When the brief is vague, sellers either delay the response, quote a safe high price, or answer with generic catalog information that cannot be compared against other suppliers.
A useful RFQ removes ambiguity. It tells the seller what product is needed, how it will be used, what quantity range matters, where it must be delivered, what terms are acceptable, and which details will decide the purchase. The goal is not to write a long document for its own sake. The goal is to make every seller answer the same commercial question so the buyer can compare responses without rebuilding the context each time.
Start with the buying job, not the product name
Product names can be misleading. Two sellers may use the same name for different specifications, or different names for equivalent products. Begin the RFQ with the business job the product must perform.
For example, instead of writing only "USB-C cable," write: "We need USB-C charging cables for retail resale, 1 meter length, braided outer jacket, expected to support 60W charging, with packaging suitable for shelf display." That one sentence tells the seller the category, use case, technical expectation, presentation requirement, and likely commercial channel.
For packaging, describe the product being packed, the fill weight or dimensions, whether the package must be retail-ready, and whether artwork or custom printing is required. For replacement parts, describe the machine, compatibility requirement, tolerance, material, and whether certification or test documentation is needed. For digital products, describe activation steps, delivery instructions, support expectations, and refund handling.
Define the specification hierarchy
Separate the RFQ into three levels: mandatory requirements, acceptable alternatives, and preferences. This prevents sellers from treating every detail as equally rigid.
| Requirement type | What it means | Example |
|---|---|---|
| Mandatory | The quote is not acceptable without this. | Must be compatible with model X; must ship to Germany; must include CE documentation. |
| Acceptable alternative | Seller can propose another route if it meets the business goal. | Equivalent material acceptable if durability test data is provided. |
| Preference | Useful, but not a blocker. | Matte finish preferred; black packaging preferred; delivery within 21 days preferred. |
This structure improves seller replies because it gives them room to solve the problem without ignoring the buyer's constraints. It also makes negotiation cleaner: if a seller misses a mandatory item, the buyer can reject or ask for correction; if they miss a preference, the buyer can still compare the quote.
Include quantity as a range when demand is not final
Many buyers ask for one quantity too early. That can hide the real economics. If demand is uncertain, request quote tiers instead of a single number.
A strong RFQ might ask for 100, 300, 500, and 1,000 units, or it might ask for the seller's MOQ plus the next two price breaks. This gives the buyer a clearer view of unit economics, setup cost, freight efficiency, and cash commitment.
Do not compare only the lowest visible unit price. The right comparison is usually the first usable quantity tier plus the total landed expectation. A supplier with a slightly higher unit price but a lower MOQ, clearer lead time, and better support path may be the better first purchase.
State delivery assumptions early
Delivery terms change the quote. If the seller is quoting ex-works, the buyer may still need export handling, freight, duties, import taxes, and local delivery. If the seller is quoting delivered cost, the buyer needs to know what destination, courier, service level, and included charges are assumed.
At minimum, include destination country, city or postal region if relevant, preferred delivery method, deadline, and whether the quote should include freight. If delivery terms matter, ask the seller to state the term explicitly rather than burying it in notes.
Useful delivery questions include:
- What delivery term is the quote based on?
- Is freight included or estimated separately?
- What shipment size or package dimensions are assumed?
- What lead time starts after payment, artwork approval, sample approval, or production confirmation?
- Which party handles export documents and import clearance?
Ask for quote outputs in a fixed format
Comparable replies are the entire point of RFQ work. Tell sellers exactly what fields to return.
| Field | Why it matters |
|---|---|
| Unit price by quantity tier | Shows price breaks and the first usable tier. |
| MOQ | Shows whether the supplier fits the buyer's volume. |
| Setup or tooling fee | Prevents custom costs from being hidden inside later messages. |
| Sample availability and cost | Helps buyers validate quality before a larger order. |
| Production lead time | Separates production time from shipping time. |
| Delivery method and freight assumption | Keeps landed cost comparisons honest. |
| Payment path | Shows whether checkout, invoice, bank transfer, or another route is expected. |
| Warranty, return, or defect policy | Clarifies post-purchase risk. |
| Quote validity | Protects against stale pricing or currency movement. |
If the product is custom, add fields for artwork, mold, die line, material grade, certification, tolerance, color matching, packaging, labeling, and acceptance criteria. If the product is digital, add fields for fulfillment timing, activation instructions, region restrictions, support contact, and refund handling.
Attach source material only when it reduces ambiguity
Attachments help when they clarify specifications. They hurt when they replace the actual RFQ. If you attach drawings, images, spreadsheets, packaging artwork, or a sample photo, still summarize the critical requirements in the message body.
For images, explain what the seller should copy and what they should ignore. A reference image might show shape and finish, but not material, dimensions, certification, or packaging. Sellers should not be forced to guess which detail is important.
Red flags in seller replies
Weak replies usually show up quickly. Watch for sellers who answer with only a unit price, ignore the requested quantity tiers, avoid delivery terms, refuse to state lead time assumptions, or say "same as picture" without confirming specifications.
Other red flags include:
- A price that is not tied to a specific quantity or configuration.
- A quoted MOQ that changes after the buyer asks about samples.
- A delivery estimate that does not distinguish production time from transit time.
- A seller who cannot explain packaging, labeling, warranty, or defect handling.
- A quote that excludes obvious costs without saying what is excluded.
- A reply that pushes immediate payment before confirming requirements.
A red flag does not always mean the seller is bad. It means the buyer should slow down and request clarification before treating the quote as comparable.
A practical RFQ message template
Use this as a starting point and adjust it by category.
| Section | Buyer input |
|---|---|
| Product needed | Product name, category, and intended use. |
| Mandatory requirements | Non-negotiable specs, compatibility, certifications, dimensions, or materials. |
| Quantity range | Target quantity and requested quote tiers. |
| Destination | Country, city or region, and delivery deadline if relevant. |
| Delivery expectation | Whether freight should be included and which delivery term is preferred. |
| Customization | Artwork, packaging, labeling, color, tooling, sample, or approval steps. |
| Required response | Unit price, MOQ, price breaks, lead time, freight assumption, payment path, policy notes. |
| Decision criteria | What will matter most: price, speed, certification, quality proof, support, or flexibility. |
A concise example:
"We are sourcing 500-2,000 retail-ready power adapters for resale in the United States. Please quote 500, 1,000, and 2,000 units. Mandatory requirements: US plug, relevant safety documentation, individual retail packaging, and clear warranty terms. Please include MOQ, unit price by tier, sample cost, production lead time after approval, freight assumption to California, payment path, quote validity, and any excluded costs. If you recommend an alternative specification, explain the difference and why it meets the same use case."
How to compare responses after they arrive
Do not rank replies by price first. Build a comparison table with the same fields you requested. Then mark each seller as complete, partially complete, or not comparable.
A complete reply answers the product requirements, quantity tiers, delivery assumption, lead time, and policy questions. A partially complete reply may still be useful, but it needs follow-up. A not-comparable reply should not be used as evidence for market price until the seller fills the gaps.
The strongest shortlist usually has three qualities: the product fit is clear, the commercial terms are explicit, and the seller can explain what happens after the buyer commits. That is the difference between a quote and a procurement-ready quote.
How this fits a Cusket buying flow
On Cusket, use product pages, seller context, category pages, and guide notes to prepare the RFQ before contacting a seller. Save the product identity, selected options, quantity target, delivery expectation, and open questions. If a listing already has enough information for checkout, use the RFQ only for missing details. If the product is custom, high volume, or operationally sensitive, use the RFQ as the control document for comparison.
A good RFQ should make the next step obvious: request a sample, ask one clarification, shortlist the seller, or move toward checkout. If the reply creates more uncertainty than it resolves, the RFQ did its job by showing that the seller is not ready for that purchase yet.
Related Cusket paths
Use the RFQ structure with pages that keep product context visible while you compare sellers:
- Compare B2B suppliers
- Understand MOQ before sending an RFQ
- Build a supplier scorecard
- Browse product discovery
- Open buyer support