You asked a multi-part question and the supplier replied to only one item. That partial response can still be useful if you treat it as a partial deliverable, not a completed conversation. The immediate goal is to preserve what you have, make the outstanding items explicit, and create a clear, timestamped record that supports the next decision: wait, remind, or escalate.

Label the response and separate what is complete from what is missing

Start by reading the supplier response against each component of your original message. Mentally or on a copy of your sent message, mark items as answered, partially answered, or unanswered. Do not assume silence means agreement or acceptance; treat it as unknown.

Next, produce a one-paragraph summary that says which specific items the supplier answered and how. Use concrete phrases: "Answered: lead time 30 days; Partially answered: sample cost provided but shipping cost missing; Unanswered: MOQ and packaging specs." That summary becomes the top of your follow-up record and reduces ambiguity for anyone else who reviews the thread.

• List each original question as a numbered line.
• Annotate each line: Answered / Partial / No reply.
• Save this annotated list as the first lines of your next message or internal log.

Reframe the remaining questions as separate, short items

Turn each unanswered element into its own simple question or data point request. Short, single-topic items are easier for suppliers to handle and for you to track. Replace compound phrasing with a single request per line, for example: "MOQ per SKU?" instead of "What is MOQ and can you reduce it?"

Where context matters, add a one-line reason so the supplier understands why you need the answer. For instance: "MOQ per SKU? (Needed to calculate landed price for our Monday meeting.)" The reason can encourage a faster reply and gives recipients an immediate decision context without adding negotiation points.

• Use numbered lines for each remaining item so responses can be matched to questions.
• Keep each request under 12 words when possible.
• Add a one-line reason only when it helps the supplier prioritize.

Choose a preservation method and capture the record

Decide where the record will live before you send a follow-up. That can be the original email thread, a shared procurement spreadsheet, a ticket in your sourcing tool, or your CRM notes. The important part is that the annotated list and the supplier reply live together, with timestamps, so decisions and accountability are visible later.

When you send the follow-up, paste your short annotated list into the message body rather than attaching a separate file. That keeps the record searchable and prevents version confusion. If you use a template, keep these three lines: context, numbered unanswered items, and a clear deadline or requested timeframe for each item.

• Template start: "Following up on your reply. Items answered below; remaining items numbered."
• Numbered items: 1) MOQ per SKU? 2) Sample shipping cost? 3) Packaging spec sheet?
• Close: "Please reply to each numbered item by [date/time]. Thanks."

Write a concise follow-up that preserves what was answered

Send a single short message that does three things: acknowledge what was answered, list the unanswered items as numbered questions, and set a clear next step or deadline. Use plain subject-line prefixes when needed, such as "Follow-up" or "Clarification requested," and keep the body under ten lines so it is scan-friendly.

Include the supplier's text for the items they did answer when helpful. Quoting brief snippets reduces misinterpretation and creates a direct link between their content and your internal record. If you work across teams, CC the relevant internal stakeholders so the record is visible and action owners are clear.

• Acknowledgment example: "Thanks for confirming lead time is 30 days (your message below)."
• Number remaining items clearly and request a timeframe for each.
• Set a decision window: "Please respond by [date]; otherwise we will assume [next step]."

Decide the next step if items remain unanswered

If the supplier does not answer by your deadline, treat each unanswered item according to its business impact. Low-impact details may be postponed or handled at sample review. High-impact items such as compliance data, final prices, or MOQ should trigger escalation or trigger a contingency plan. Define those thresholds in your purchase order or internal sourcing matrix ahead of time so choices are repeatable.

Document the decision you make. For example: "No MOQ received by X date; buyer will request MOQs from two alternate suppliers" or "Packaging spec missing; proceed with provisional packaging at buyer's risk pending written confirmation." That short, dated note keeps the record auditable and informs downstream teams preparing contracts or shipments.

• Classify unanswered items: Informational, Negotiable, Blocker.
• Apply a predefined action per class: log, negotiate, escalate.
• Record the chosen action with date, owner, and next checkpoint.

When to involve specialists and how to present the record

Specialists such as quality, legal, or customs teams may be needed when the unanswered item affects compliance, contract terms, or financial exposure. Before you loop them in, summarize the thread with the numbered unanswered items, the supplier's partial replies, and your recommended next action. That focused package saves review time and reduces back-and-forth.

Provide specialists with the exact record format they prefer: a PDF of the thread, a ticket link, or a short one-page summary. Ask them what additional detail they need and add those questions back into your numbered list so any future supplier reply addresses both procurement and specialist concerns in the same thread.

• Include date-stamped thread, annotated items, and your suggested next step.
• Ask specialists for the minimum extra information required to clear the item.
• Keep replies centralized so the record remains intact.

Draft and send a numbered follow-up that lists the unanswered items and a clear reply deadline.