How to Write an RFQ to a Japanese Supplier
Updated · Written by HAM International Trade Team
Open with who you are, why you selected the supplier, and the decision you need. Provide item identity or a controlled specification, application, quantity, destination, timing, acceptance evidence, and numbered commercial questions. Separate mandatory requirements from preferences, and invite a redirect or decline if the request is outside scope.
The RFQ must survive internal routing
A first message may reach a general mailbox, domestic sales desk, engineer, distributor contact, or administrator. In the opening lines, identify your company and country, the product family, whether the request concerns supply, identification or custom manufacture, the destination, and the requested action. Mention the official page, product or referral that led you there so the recipient can judge relevance.
Do not imitate ceremonial Japanese business language or hide the request inside a long company introduction. Plain, respectful English is workable when the structure is clear. If the recipient is not responsible, explicitly ask for forwarding to the export, product or sales contact—or for a short decline. That gives the first reader a safe action.
An RFQ that can be routed, assessed and quoted
Use labels that answer the recipient’s first questions in order.
- Subject
- RFQ — [maker and complete code or defined part] — [quantity] — delivery to [city, country]
- Makes product, scale and destination visible before opening.
- Context
- We are [company, country] and use the item in [brief application]. We found your company through [official route].
- Establishes legitimacy without a generic corporate biography.
- Requirement
- Please quote the attached requirement revision. Mandatory: [identity/specification/condition]. Preference: [clearly separated].
- Prevents preferences becoming accidental rejection criteria.
- Quantity and timing
- Quantity [x], expected repeat demand [if real], destination [place], required-use date [date and meaning].
- Allows a lead-time answer tied to an actual scenario.
- Questions
- Please confirm exact item, role, condition, lead-time basis, Incoterms rule and named place, packing, documents, payment and validity.
- Requests comparable fields instead of an undefined discount request.
- Response path
- If this is outside your scope, please advise whether another department or authorised channel should receive it.
- Makes redirection or decline easier than silence.
Give enough technical context to prevent the wrong quote
For catalogue parts, provide manufacturer, complete code including suffix, clear label and item photographs, host machine, function, installed revision, required accessories, desired condition and whether alternatives may be proposed. If identity is uncertain, say that the request is for identification and list the evidence available. Do not put an uncertain guess into a mandatory part-number field.
For custom work, attach a controlled drawing or requirement with revision, units, material, treatments, tolerances, inspection, standards, quantity, annual demand, sample or tooling needs, and approved file formats. Remove unrelated confidential data. State which characteristics are mandatory, which can be discussed, and who will answer technical questions.
Ask questions whose answers can enter a decision
Number the requested fields: offered manufacturer and code, condition, quantity and MOQ, unit and total price, currency, validity, stock or production basis, lead-time start event, Incoterms rule with named place, packing, export documents, payment timing, warranty or return process, and deviations. Ask candidates to mark Unknown rather than fill gaps with assumptions.
Request evidence appropriate to the item: current photographs, manufacturer traceability, certificates, inspection records, material reports, or a written statement of seller role. Avoid demanding every possible certificate. An unfocused list creates work without proving the property your engineers or compliance owners actually need.
Prepare, issue and clarify one controlled request
Version control matters when several people and suppliers answer in parallel.
- 01
Define the decision
State whether you need identification, availability, manufacture, technical clarification or a firm quote.
OUTPUTRFQ purpose
- 02
Build the evidence pack
Collect identity, specification, application, quantity, destination and acceptance needs.
OUTPUTControlled attachments
- 03
Write the response table
Ask for fields that technical, commercial and logistics reviewers can compare.
OUTPUTRFQ revision
- 04
Route and follow up
Use an official channel, reference the request, and ask for redirect or decline.
OUTPUTNamed status
- 05
Issue clarifications
Share material answers and revisions consistently with all still-comparable candidates.
OUTPUTComparable offers
Pre-send RFQ review
A colleague unfamiliar with the case should be able to identify the requested decision.
- Subject identifies item or process, quantity and destination
- Buyer company, country and official contact details are complete
- Supply, identification or custom-manufacture purpose is explicit
- Mandatory requirements, preferences and permitted alternatives are separated
- Files are readable, revision-controlled and stripped of unnecessary secrets
- Quantity, destination and timing have operational meaning
- Requested commercial fields can be compared across candidates
- Redirect, decline, clarification owner and response date are clear
Follow up by reducing uncertainty, not adding pressure
If there is no response, verify the address and supplier fit before resending. A short follow-up should reference the original subject and date, restate the one requested action, and offer a smaller next step: confirm the right department, advise whether the item is handled, or decline. If new information changes the requirement, issue a visible revision rather than silently altering the email chain.
HAM can help turn a requirement into a concise bilingual-ready enquiry, identify an appropriate Japan-side route, and organise replies and open questions. The buyer remains responsible for technical acceptance, supplier approval, commercial agreement, compliance, and release of any order or payment.
Frequently asked questions
- Should the first RFQ be written in Japanese?
- Not always. Clear English may work with an export-facing team. Japanese support can improve routing, but it cannot compensate for an undefined item, quantity, destination or decision.
- How long should an RFQ be?
- Use a short message plus controlled attachments. Length should follow complexity; the requested action and core facts should still be visible without searching through a company presentation.
- Should I ask for a discount in the first RFQ?
- First request a quote on a defined quantity and scope, including MOQ, validity, lead-time basis, delivery rule and exclusions. Negotiate from a comparable offer rather than an undefined price request.