RFQ checklist for China-side peptide sourcing

A useful RFQ freezes product, quantity, destination, and documents before money moves — so China-side control and evidence scope can be confirmed. Without those four locks, a supplier quote, a forwarded PDF, or a public library record cannot be matched to this order. Use the five points below as a written enquiry file, not as a chat script.

This checklist is for professional B2B buyers designing China-side peptide sourcing controls. It is educational long-form guidance for freezing scope and documents — not medical, dosing, or end-use advice, and not a first-message demand list for WhatsApp.

Why freeze the RFQ before payment gates

China-side control works when supplier, laboratory and carrier operate against the same written specification. An incomplete RFQ leaves gaps: a “same product” quote that changes format or packaging; a sample COA used as if it covered a production lot; or destination assumptions that never appear in the order file.

Freezing the RFQ early does three practical things:

1. Makes quotes comparable — product, format, strength, packaging and quantity are fixed, so price and lead time refer to the same goods.
2. Sets evidence scope in advance — you decide whether you need only a public / sample-oriented Tested Sample reference for early review, or a path toward Batch-Linked confirmation when lot correspondence can be verified.
3. Separates sample expectations from production lots — pilot quantity, sample timing and production-lot documents are stated up front, so payment milestones can follow completed checks rather than hope.

For how to read a report once documents arrive, see How to read a peptide COA. For label definitions, see Tested Sample vs Batch-Linked COA. For the deeper scope argument, see What a COA proves.

The five-point RFQ checklist

Copy these five headings into your enquiry file. Fill each in writing before deposit or other material payment. Soft tone: this is a buyer preparation checklist — not a confrontational opening message.

1) Product / format / strength / packaging

State the named compound, the physical format (e.g. lyophilized vial, bulk powder, or other agreed form), the stated strength or fill, and packaging configuration (vial size, units per pack, labeling language if relevant to your process).

Why it matters: A quote that only says the product name is not yet a sourcing decision. Format and packaging changes alter cost, handling, labeling and which documents you can reasonably request.

Write down at least:

• Named product as you will cite it on POs and packing lists
• Format and stated strength / fill
• Packaging unit and pack-out
• Any labeling or packing marks you will require on goods (separate from lot marks — see documents and timeline below)

Cross-check public examples by product on Verified products and in the COA library so your written name aligns with how evidence records are indexed — those pages organize public reports; they are not a retail catalog.

2) Quantity (pilot vs ongoing)

Separate pilot / first release quantity from any ongoing / follow-on forecast. State both if both exist, and say which quantity this RFQ is asking suppliers to price and schedule now.

Why it matters: Pilot volume and ongoing volume support different control intensity. A small pilot may reasonably start with Tested Sample evidence and written specs; larger or repeat releases more often need a documented path to lot marks and Batch-Linked review when correspondence is available. Mixing “sample pricing” with “ongoing volume” in one vague line creates mismatched lead times and payment expectations.

Write down at least:

• Quantity for this RFQ (units / packs / kg as applicable)
• Whether it is pilot-only, first commercial release, or part of an ongoing plan
• Any split between sample / retain quantity and sellable or stock quantity (if your process uses that split)

Do not treat a public PDF from a prior sample as an automatic cover for a larger follow-on lot. Each order remains its own evidence file.

3) Destination country + any import constraints already known

Name the destination country (or countries) for the goods under this RFQ, and list any import, customs, carrier or paperwork constraints you already know from your side — without asking BatchVerity or a supplier to invent legal clearance.

Why it matters: Destination shapes documentation language, packing, carrier choice and what “complete documents” means for your file. Leaving destination blank forces everyone to guess; guessing is not China-side control.

Write down at least:

• Destination country / region for this shipment plan
• Constraints you already know (e.g. required commercial invoice fields, preferred Incoterms, document language, carrier limitations you have been told)
• What you are not asking anyone to certify (destination eligibility and regulatory clearance remain your counsel’s domain)

This article does not establish that any product is available or cleared for any market. Naming destination in the RFQ is operational scoping — not an approval claim.

4) Documents: sample COA (what’s public today) vs batch-linked (only if lot correspondence is available)

State which documents you need for this order, and label evidence scope correctly.

Document ask	What it usually means	When to request it
Sample / public-reference COA (Tested Sample)	An independent laboratory report for submitted material — the default reading for public library records	Early source review, written-spec design, pilot planning
Batch-Linked confirmation	Same kind of independent report plus documented lot correspondence to the sales lot under discussion	Only when verifiable lot / batch marks (or equivalent controlled identifiers) can connect the tested unit to the proposed goods — and that match will be recorded
Commercial / shipping pack	Invoice, packing list, and other trade documents your file requires	As agreed for the release; separate from laboratory scope

Evidence boundary (retain this language in the RFQ file):

• Public library = Tested Sample. Records in the COA library should be read as Tested Sample unless a specific record explicitly documents Batch-Linked correspondence.
• Batch-Linked is confirmed per order when a verifiable lot link exists — not assumed from product name, strength match, or a verbal “same batch” claim.
• A Tested Sample result does not automatically prove a future production lot or every unit in a shipment. Batch-Linked narrows scope; it still does not erase unit-to-unit or lot-to-lot variation.

If you only need early review of what a public or sample-oriented report shows, say so. If you need a path toward Batch-Linked for a larger release, say which lot marks you expect on labels, packing lists and retained samples. Do not ask for “batch-approved for use” language — ask for documented correspondence and independent panels that appear on the report. See Tested Sample vs Batch-Linked COA and What a COA proves.

5) Timeline / sample vs production lot expectations

Separate sample timing from production-lot timing, and say which documents and checks belong to each stage.

Why it matters: “ASAP” without stages collapses sample review into production commitment. Clear stages let payment gates follow completed evidence — spec freeze, sample documents, lot marks, then larger release — instead of moving money on an incomplete file.

Write down at least:

• When you need a written quote against the frozen product / quantity / destination / documents
• Whether a physical or documentary sample stage comes before production commitment
• Target window for production-lot readiness (stated as a planning window, not as a guarantee)
• Which evidence checks must complete before deposit, before balance, or before shipment release

China-side coordination is about closing gaps between supplier, laboratory and carrier with written specs and scoped evidence — not treating any one PDF as a blanket clearance. For supplier-side questions beyond the RFQ freeze, see the upcoming How to vet a China peptide supplier checklist.

How the five points work together (one-page example)

A complete one-product RFQ might look like this in outline form (illustrative structure only — not a quote request for any named goods):

1. Product — named compound; lyophilized vial; stated strength; pack-out X vials / carton; label marks as agreed.
2. Quantity — pilot N units now; ongoing forecast noted separately and not priced as binding.
3. Destination — country named; known invoice / packing constraints listed; no clearance asked of the counterparty.
4. Documents — Tested Sample COA for early review (cite public library scope); Batch-Linked path only if lot marks on goods and retained samples can be recorded for this order.
5. Timeline — quote by date A; sample / documentary review before production commitment; production window B–C; payment gates tied to completed checks.

Fill the blanks for your product. Share those five filled points when you request a complimentary one-product review (below) — that keeps the conversation educational and scoped, not a hard-sell chat open.

Soft next step

If you have one product requirement and want a second pair of eyes on whether the five points are freeze-ready — and what evidence scope (Tested Sample vs Batch-Linked path) fits that written file — request a complimentary preliminary review via Contact.

Share the five points above for a one-product review. This is not an approval, clearance, or determination that goods are suitable for any destination or use.

WhatsApp: United States +1 303 961 4229 · China +86 180 0545 5057 · Email: sales@batchverity.com

Qualified B2B enquiries only. Laboratory testing, factory audits and extended investigations are quoted separately.

---

FAQ

What should a peptide RFQ for China-side sourcing include?

At minimum: product / format / strength / packaging; quantity (pilot vs ongoing); destination country plus import constraints you already know; documents with clear Tested Sample vs Batch-Linked scope; and timeline expectations that separate sample from production lot. Freeze those before material payment.

Why freeze the RFQ before money moves?

So quotes, lead times and evidence requests refer to the same goods and the same document scope. An incomplete RFQ leaves China-side gaps between supplier, laboratory and carrier that a single PDF cannot close.

Is a public COA enough for my RFQ?

Public records in the COA library are useful as Tested Sample references for early review. They are not, by default, Batch-Linked proof for a future sales lot. Confirm per order whether you only need Tested Sample scope or a documented lot-link path.

When should I ask for Batch-Linked documents in the RFQ?

Only when verifiable lot correspondence can exist for the order — lot / batch marks (or equivalent controlled identifiers) on the submitted unit and on the proposed goods, with the match recorded. Product name alone is not enough. See Tested Sample vs Batch-Linked COA.

Should I send this checklist as my first WhatsApp message?

No. This article is educational long-form for building a written enquiry file. Soft commercial contact can start with a brief, polite one-product enquiry; use the five points as your internal preparation (and what you share for a complimentary review), not as a demanding first-message script.

Does filling this RFQ mean BatchVerity approves or clears my goods?

No. A complimentary review of your five points is preliminary scoping help — not approval, clearance, regulatory advice, or a determination of suitability for any use or destination.

Where can I see example product evidence pages?

Browse Verified products and the COA library. Those pages organize public Tested Sample reports by product for professional review; they are not a retail catalog. Field-level reading guidance is in How to read a peptide COA.

---

Scope note (retain on publish)

This article is an educational RFQ / enquiry checklist for professional B2B sourcing. It is not medical, legal or regulatory advice; it does not establish product availability for a destination; and it does not approve, clear or certify goods for any human use. No dosing, therapeutic, or benefit claims are intended.