Recovery
Research Peptide Supplier Audit Questionnaire for Canadian Buyers
On this page
On this page
- Quick answer: what should a research peptide supplier audit questionnaire ask?
- How this questionnaire fits the Northern Compound documentation stack
- The supplier audit questionnaire template
- Copy-paste questionnaire for supplier support
- Scoring the answers without overfitting the spreadsheet
- Question group 1: RUO boundary and claim discipline
- Question group 2: product identity and catalogue clarity
- Question group 3: COA quality and analytical evidence
- Question group 4: lot traceability
- Question group 5: storage, shipping, and receiving assumptions
- Question group 6: support behaviour and document access
- Category-specific add-on questions
- When to use ProductLink paths
- One-page audit packet: what to save before a supplier is scored
- Decision tree: accept, clarify, quarantine, reject, or do not cite
- How to handle missing answers without turning the audit into a negotiation
- Internal use case: auditing a live product route without overclaiming it
- Common failure modes this questionnaire catches
- Authoritative references for audit framing
- FAQ
- Bottom line
Quick answer: what should a research peptide supplier audit questionnaire ask?
A research peptide supplier audit questionnaire should ask whether a supplier can support a specific research-material purchase with current, lot-level evidence. It should not ask broad confidence questions such as “Are you reputable?” or “Is this high quality?” Those answers are too easy to market around. A useful questionnaire asks for documents, dates, identifiers, methods, storage assumptions, support paths, and claim boundaries.
For Canadian research peptide buyers, the audit should cover ten areas:
- Research-use-only boundary: whether the supplier avoids human dosing, treatment, cure, athletic-performance, cosmetic-result, or personal-use guidance.
- Product identity: exact peptide name, salt or acetate form when relevant, blend ratio if applicable, fill amount, and catalogue identifier.
- Batch-specific COA availability: current certificate, lot number, test date, method names, lab/source attribution, and whether the COA matches the vial or product page.
- Analytical evidence: HPLC or UPLC purity plus mass-based identity evidence such as MS, LC-MS, MALDI, or expected/observed mass.
- Traceability: whether product page, invoice, vial label, COA, shipment record, and support answer can be tied to the same lot.
- Storage and handling: unopened storage temperature, light and moisture language, shipment assumptions, reconstitution documentation path, and retest/expiry framing.
- Shipping and receiving: courier expectations, temperature excursions, damaged package process, missing COA process, and evidence-retention expectations.
- Support quality: whether support answers narrow documentation questions without drifting into personal-use guidance.
- Change control: whether page copy, COAs, catalogue identities, and document access are updated in a way a buyer can audit.
- Decision status: accept for further review, clarify, quarantine, reject, or do not cite.
This questionnaire is written for non-clinical research procurement. It is not medical advice, legal advice, dosing guidance, administration guidance, treatment guidance, cosmetic guidance, or a recommendation for human use. It is a documentation tool.
Use it before comparing broad peptide catalogues, GLP-1 research materials such as Semaglutide, Tirzepatide, Retatrutide, and Cagrilintide, recovery materials such as BPC-157, TB-500, and BPC-157 + TB-500 blend, skin research materials such as GHK-Cu, KPV, and LL-37, or cognitive research materials such as Selank, Semax, and DSIP.
How this questionnaire fits the Northern Compound documentation stack
Northern Compound already has several procurement tools. This page fills the gap between a red-flag screen and a scored supplier comparison.
- Start with the research peptide supplier red flag checklist when a page feels risky or aggressively consumer-facing.
- Use this questionnaire when the supplier deserves a structured evidence request.
- Save each reply in the research peptide supplier response log template.
- Score the supplier with the research peptide supplier scorecard.
- Review the certificate with the peptide COA verification checklist.
- If the supplier does not provide the needed file, send a narrow request from the research peptide COA request email template pack.
- If the lot is purchased, preserve the final evidence in the research peptide batch documentation template.
That order matters. A questionnaire without a scorecard becomes a pile of answers. A scorecard without questions becomes a subjective ranking. A COA checklist without supplier-response records can miss the context that explains why a document was accepted, clarified, or rejected.
The supplier audit questionnaire template
Use the table as a working questionnaire. The “evidence to save” column is as important as the question. If the supplier answers in plain language but no document is retained, the audit trail is weak.
| Audit area | Question to ask | Strong answer | Evidence to save | Decision impact |
|---|---|---|---|---|
| RUO boundary | Can you confirm this material is sold for research use only and that support will not provide dosing, administration, treatment, or personal-use guidance? | Clear RUO confirmation and no protocol drift | Product page capture, support reply, RUO terms page | Required before any further score |
| Product identity | What is the exact catalogue name, peptide identity, form, fill amount, and SKU for the lot under review? | Specific identity and SKU without synonym confusion | Product page capture, SKU, vial label photo | Clarify if naming is vague |
| Batch COA | Is a current, batch-specific COA available before purchase or at shipment? | Current lot-matched COA with test date and method names | COA PDF, file name, capture date | Missing COA caps supplier confidence |
| Identity testing | What identity method supports the peptide identity? | MS, LC-MS, MALDI, or expected/observed mass data named or shown | Spectrum, mass table, COA line item | Purity alone is not enough |
| Purity testing | What chromatographic method supports purity? | HPLC or UPLC with chromatogram or peak table | Chromatogram, method name, purity result | Strong only with identity evidence |
| Lot traceability | How do the vial, invoice, product page, and COA map to the same lot? | Visible lot mapping without support-only interpretation | Vial label, invoice, COA lot number | Clarify or quarantine if mapping is unclear |
| Storage | What unopened storage conditions apply to this lot? | Temperature range, light/moisture cautions, retest/expiry language | Storage page, product page, support answer | Required for handling-sensitive materials |
| Shipping | What shipment condition or packaging expectation applies? | Clear packaging and what to do after delays or damage | Shipping page, courier note, package photo | Use receiving SOP after arrival |
| Support | Who answers documentation questions after checkout? | Dedicated support path and document-request process | Contact route, ticket number | Low-friction support raises confidence |
| Change control | If a COA, product page, or storage instruction changes, how can a buyer preserve the version reviewed? | Stable downloadable documents and clear revision dates | PDF metadata, page capture, date | Important for repeat procurement |
This is not a vendor ranking. It is an evidence request. The supplier does not need to write a long essay. Short answers are fine if they are precise, consistent, and attached to the right lot.
Copy-paste questionnaire for supplier support
Use this when a supplier has a plausible catalogue page but the documentation packet is incomplete. Keep the request narrow. Do not ask for medical, dosing, administration, or personal-use advice.
Hello,
I am reviewing [product name/SKU] for non-clinical research procurement documentation.
Could you confirm the following for the current lot or the lot that would ship?
1. Exact catalogue name, SKU, fill amount, and peptide form if applicable.
2. Current lot number or batch identifier.
3. Whether a batch-specific COA is available before purchase or with shipment.
4. COA test date and whether the COA is tied to the same lot that would ship.
5. Identity method used, such as MS, LC-MS, MALDI, or expected/observed mass.
6. Purity method used, such as HPLC or UPLC, and whether chromatogram or peak data is available.
7. Unopened storage conditions and any light/moisture cautions.
8. Shipping or receiving notes for delayed, warm, damaged, or wet packages.
9. Whether your support team provides research-use-only documentation answers only and does not provide dosing, administration, treatment, or personal-use guidance.
10. Best way to request updated documents for the same lot later.
Please do not provide dosing, administration, treatment, cosmetic, athletic-performance, or personal-use recommendations. I am only requesting documentation for research-use-only procurement review.
Thank you.If the supplier answers with protocol advice, dosage language, patient language, or “how to use” instructions, do not treat that as helpful service. Save the answer as a compliance finding and score the supplier down.
Scoring the answers without overfitting the spreadsheet
A questionnaire is useful only if the answers change the decision. The easiest scoring model is not complicated:
| Answer grade | Meaning | Action |
|---|---|---|
| A | The supplier gives a current, lot-specific answer and provides a document or stable page capture to support it | Accept the row and move to scorecard weighting |
| B | The answer is specific but one supporting detail is missing, such as lab attribution, retest date, or visible trace data | Clarify before final supplier comparison |
| C | The answer is plausible but requires support interpretation or does not map cleanly to a lot | Cap the supplier until the mapping is documented |
| D | The answer is generic, stale, sales-oriented, or inconsistent across page, COA, and support | Quarantine the supplier for this procurement decision |
| F | The supplier gives human-use guidance, dosing, treatment claims, fake certainty, or refuses basic documentation | Reject for RUO procurement screening |
Do not average away an F. If a supplier has a polished website and fast support but gives dosing advice when asked for documentation, the audit has found a boundary failure. If a supplier offers an attractive price but cannot tie the COA to the current batch, the audit has found a traceability failure.
Use the same cap logic as the supplier scorecard:
- Human-use or dosing language: cap at 30 or reject.
- Missing batch-specific COA: cap at 50 until the exact lot document exists.
- Purity percentage without identity support: cap at 60 until mass-based identity is shown or explained.
- Lot mapping visible only through support interpretation: cap at 70 until the identifiers are saved.
- Missing storage or shipping assumptions: cap at 75 for handling-sensitive materials.
The point is not to punish suppliers for imperfect paperwork. The point is to keep weak paperwork from looking stronger than it is.
Question group 1: RUO boundary and claim discipline
Ask this first because it governs the rest of the review. A supplier that cannot stay inside RUO language should not earn trust because its COA looks scientific.
Strong supplier behaviour looks like this:
- product pages use research-use-only language in visible areas;
- product copy avoids disease treatment, diagnosis, prevention, cure, body-transformation, performance, recovery outcome, tanning, cosmetic-result, and anti-aging promise language;
- support refuses dosing or protocol questions and redirects to documentation only;
- study citations are framed as mechanism or assay context, not as human-use evidence;
- testimonials, before-and-after images, forum language, and protocol calculators are absent from the product path.
Weak supplier behaviour often looks more subtle. The footer says RUO, but the headline implies personal outcomes. The FAQ avoids the word “dose” but answers “how long until results.” The page cites a study in animals or cells but talks as if the result transfers to buyers. The support answer starts with documentation and ends with personal-use advice.
For the audit file, save the page capture and support answer. If the supplier later changes copy, your dated record explains the decision that was made at the time.
Question group 2: product identity and catalogue clarity
Peptide catalogues can be easy to browse and still hard to audit. Similar names, blend abbreviations, salts, cosmetic-adjacent terms, and dead product routes can create traceability problems.
Ask:
- What is the exact product name and SKU?
- Is the material a single peptide, a blend, or a related research reagent?
- If it is a blend, what ratio or composition is represented in the product identity?
- Is the peptide form stated when relevant?
- Is the fill amount clear on the product page and vial label?
- Does the product page match the COA name?
- Does the supplier use obsolete, alternate, or consumer-facing names that could confuse the record?
This matters for broad catalogues and for specific lanes. A GLP-1 page should distinguish receptor-lane research materials rather than collapsing them into weight-loss copy. A recovery page should distinguish BPC-157, TB-500, and a fixed blend rather than implying the same documentation standard covers all three. A skin page should separate RUO GHK-Cu, KPV, and LL-37 materials from cosmetic-result language.
If the supplier cannot state the identity plainly, stop. Do not let a COA or product image carry a record that the supplier cannot describe.
Question group 3: COA quality and analytical evidence
The COA is often the centre of the audit, but it should not be treated as magic paperwork. A useful COA answers specific questions:
- Which lot was tested?
- When was it tested?
- What method established purity?
- What method supported identity?
- Does the COA show enough trace detail to support the result?
- Is the COA generic or current-lot specific?
- Can the buyer match the COA to the vial and order?
A purity percentage alone is not enough. HPLC or UPLC can support chromatographic purity, but it does not prove that the material is the intended peptide. Identity evidence should come from mass-based methods or equivalent identity confirmation. The exact methods can vary by supplier and compound, but the audit should not confuse a scientific-looking number with a complete material record.
For detailed COA review, use the peptide COA verification checklist. This questionnaire asks whether the document exists and whether the supplier can explain it. The COA checklist asks whether the document itself is strong enough.
Question group 4: lot traceability
Traceability is the boring part that prevents a lot of bad decisions. The audit should be able to answer one question without guesswork: is the document packet tied to the material that would ship or did ship?
Ask the supplier to map:
- product page SKU;
- order or quote identifier;
- vial label lot number;
- COA lot number;
- shipment record;
- support ticket or document request;
- storage or handling instruction version.
A supplier can be honest and still weak here. Sometimes a lot number appears on the vial but not the product page. Sometimes support can explain the mapping, but the buyer has to save that explanation because the documents are not self-evident. Sometimes the COA is for a representative batch rather than the batch that ships.
Use “clarify” rather than “trust” when support is needed to interpret the mapping. Use “quarantine” when the mapping affects a purchased lot that has already arrived.
Question group 5: storage, shipping, and receiving assumptions
Research peptide documentation does not end at the COA. A material can have a strong certificate and still be hard to interpret if storage and shipment assumptions are absent.
Ask:
- What unopened storage temperature does the supplier state?
- Are there light or moisture cautions?
- Is there a retest, expiry, or stability framing?
- What does the supplier expect during normal shipping?
- What should a buyer document if a package arrives delayed, warm, wet, damaged, or missing paperwork?
- Does the supplier provide receiving guidance that stays inside RUO documentation rather than personal-use instructions?
When a package arrives, move from this questionnaire to the research peptide receiving SOP, peptide temperature excursion log, and peptide storage and vial inspection checklist. The supplier audit is pre-purchase or pre-reliance. Receiving records are lot-level evidence.
Question group 6: support behaviour and document access
Good support is not the same thing as permissive support. For RUO materials, the best support answer is often narrow, boring, and documentation-focused.
Strong answers:
- provide a COA or explain when it becomes available;
- name the relevant lot or SKU;
- point to a document request path;
- answer storage and shipment documentation questions;
- refuse to provide dosing, administration, or personal-use advice;
- keep the tone procurement-focused rather than outcome-focused.
Weak answers:
- say “all products are high purity” without batch evidence;
- promise effects or outcomes;
- answer with a protocol;
- ignore lot numbers;
- send a cropped screenshot with no file name or test date;
- state that a COA exists but will not show it before or after shipment;
- treat storage as obvious without a written instruction.
Save support answers in the supplier response log. Include date, route, ticket ID if any, exact question, exact answer, attachments, lot number, and the decision made after the answer.
Category-specific add-on questions
The base questionnaire works across the archive, but some lanes deserve extra questions because search demand pulls them toward consumer claims.
| Category lane | Extra questions | Companion asset |
|---|---|---|
| GLP-1 and incretin research | Does the page avoid weight-loss treatment language? Are receptor-lane differences described without implying personal outcomes? Are large-peptide identity and storage assumptions clear? | GLP-1 research compound comparison matrix |
| Recovery peptide research | Does the page avoid injury-healing, pain-treatment, mobility, or athletic-recovery promises? Is blend identity clear when BPC-157 and TB-500 are combined? | Recovery peptide comparison table |
| Skin peptide research | Does the page separate RUO material documentation from cosmetic-result copy? Are copper peptide, antimicrobial, melanocortin, or barrier-model claims kept assay-specific? | Skin peptide research glossary |
| Cognitive peptide research | Does the page avoid intranasal/personal-use copy and cognitive-enhancement promises? Are endpoints framed as research models, not outcomes? | Cognitive peptide research glossary |
| Growth-hormone secretagogue research | Does the page distinguish GHRH, GHSR, DAC/no-DAC, blend ratios, and endocrine-spillover language without protocol advice? | Growth-hormone secretagogue comparison guide |
| Diluent and handling materials | Does the supplier provide lot information, sterility/endotoxin context where relevant, expiry/retest language, and storage assumptions without implying injection instruction? | Bacteriostatic water lot-release checklist |
These add-ons keep the questionnaire from becoming too generic. The same supplier can be easy to audit for one product lane and weak for another.
When to use ProductLink paths
Product links are useful only after the documentation question is clear. Northern Compound uses ProductLink paths to preserve attribution and avoid raw product URLs, but a ProductLink should not make an article sound like a recommendation to use a compound personally.
A compliant product path sounds like this:
- “Review current COAs and batch documentation before comparing BPC-157 research material.”
- “For GLP-1 research procurement, compare lot-level evidence across Semaglutide, Tirzepatide, and Retatrutide.”
- “Skin-model researchers should separate cosmetic language from RUO documentation before reviewing GHK-Cu or KPV.”
A weak product path sounds like a shortcut around the audit. Avoid “best,” “results,” “cycle,” “protocol,” “for recovery,” “for skin improvement,” or “for weight loss.” The product link should point to a documentation-aware lane, not a promise.
One-page audit packet: what to save before a supplier is scored
The questionnaire should leave behind a small packet that another reviewer can understand without reading the whole email thread. If the packet is not saved, the audit becomes a memory exercise.
| Packet item | What to save | Why it matters |
|---|---|---|
| Product-page capture | PDF or screenshot with URL, capture date, SKU, fill amount, and RUO language visible | Shows what the supplier represented when the decision was made |
| COA file | Original PDF or image with file name, lot number, test date, purity method, and identity method | Preserves the evidence instead of relying on a link that may change |
| Vial or label evidence | Supplier label photo when available, or receiving photo after arrival | Connects the document packet to a physical lot identifier |
| Support answer | Full text of the supplier reply with date, route, ticket ID, and attachments | Shows whether support stayed inside documentation boundaries |
| Storage/shipping note | Product-page storage language, shipping condition statement, or support answer | Protects the receiving and stability review from assumption drift |
| Decision record | Accept, clarify, quarantine, reject, or do not cite, with reviewer and date | Turns the audit into an action instead of a comment thread |
A strong packet can be short. The point is not to create a regulated dossier. The point is to preserve enough evidence that a future reviewer can see why the supplier was advanced, paused, or rejected.
Decision tree: accept, clarify, quarantine, reject, or do not cite
Use the same decision language across supplier review, COA review, receiving, and content citations. Consistent words keep the workflow from becoming subjective.
| Decision | Use when | What happens next |
|---|---|---|
| Accept for further review | The supplier answers the questionnaire, preserves RUO boundaries, and provides enough lot-specific evidence to move into scorecard weighting | Score the supplier and verify the COA line by line |
| Clarify | One or more fields are missing but the answer stays documentation-focused and fixable | Send a narrow follow-up and log the response |
| Quarantine | A lot has arrived or been selected but the record has a mismatch, storage gap, damaged package issue, or unresolved document problem | Hold the lot out of active research records until the discrepancy is resolved |
| Reject | The supplier cannot provide basic documents, gives human-use guidance, has mismatched lot evidence, or makes unacceptable claims | Do not rely on the supplier for that procurement decision |
| Do not cite | The page is not purchase-ready or documentation-ready enough to appear as a reference in Northern Compound content | Avoid using the page as an example or outbound route |
The “do not cite” decision is useful for editorial work. A supplier page may not be part of an actual purchase, but it can still appear in research, competitor review, or content planning. If the page uses human-outcome claims or cannot support its documents, do not treat it as a linkable example.
How to handle missing answers without turning the audit into a negotiation
Suppliers sometimes answer around the question. That does not always mean bad faith, but it does mean the buyer should avoid filling gaps with optimism.
If the COA is missing, ask for the current lot COA once. If the answer is still generic, mark the COA row as missing and cap the score. If identity evidence is named but not shown, ask whether expected/observed mass, spectrum, or a method line can be supplied. If support cannot provide it, score the identity row as partial rather than inventing confidence from the purity number.
If storage language is vague, ask for unopened storage conditions and shipping assumptions, not handling advice. If support answers with personal-use, route, or administration language, stop the exchange and save the answer as a boundary failure. More follow-up is not better when the conversation has left the documentation lane.
If the supplier says documents are available only after checkout, record that policy. It may not be an automatic rejection for every buyer, but it lowers pre-purchase auditability. A buyer cannot compare suppliers cleanly when one supplier lets current-lot documents be inspected before purchase and another requires payment before the basic record is visible.
Internal use case: auditing a live product route without overclaiming it
A ProductLink route can be useful for a reader who already knows the research lane, but the link should never imply that the supplier audit is complete. Use the questionnaire as a checkpoint before treating any product page as credible.
For example, a recovery-model buyer may compare BPC-157, TB-500, and BPC-157 + TB-500 blend. The questionnaire asks whether each route has its own identity, COA, lot mapping, and claim discipline. It should not assume a blend inherits evidence from the single-compound pages.
A GLP-1 research buyer may compare Semaglutide, Tirzepatide, Retatrutide, and Cagrilintide. The questionnaire keeps receptor-lane comparison separate from weight-loss marketing. It asks for material identity, current lot documents, storage assumptions, and RUO-safe support answers.
A skin-model buyer may compare GHK-Cu, LL-37, and KPV. The questionnaire keeps cosmetic-result claims out of the decision and forces the review back to model, method, COA, and document trail.
The product route is the last click, not the first proof.
Common failure modes this questionnaire catches
The questionnaire is most useful when it catches problems before the buyer has to unwind a bad record.
| Failure mode | What it looks like | Why it matters | Better next step |
|---|---|---|---|
| Generic COA | A certificate exists but has no lot number or current test date | The document may not describe the material under review | Request current lot COA |
| Purity-only proof | HPLC result is shown but identity method is absent | Purity does not prove identity | Ask for MS or equivalent identity support |
| Lot mismatch | Vial, invoice, product page, and COA identifiers do not align | The audit trail cannot tie evidence to material | Clarify or quarantine |
| RUO footer drift | Page says RUO but copy implies personal outcomes | Compliance language is contradicted by marketing | Score down or reject |
| Support protocol drift | Support answers documentation request with dosing or use advice | Support behaviour crosses the boundary | Save answer and reject for RUO screening |
| Storage silence | No unopened storage or shipping assumption is stated | Handling history becomes hard to interpret | Request written storage guidance |
| Dead route | Product link, COA link, or support path fails | Buyer cannot retrieve evidence later | Capture, log, and avoid relying on stale path |
If the supplier corrects a failure, do not erase the old record. Add a dated update. Supplier quality is a trajectory.
Authoritative references for audit framing
These references do not certify any supplier and do not turn this questionnaire into legal advice. They support the underlying quality-system logic: document control, supplier qualification, traceability, batch records, and boundary discipline.
- Health Canada: Good manufacturing practices guide for drug products for general Canadian quality-system expectations around records, premises, quality control, and documentation.
- ICH Q7: Good Manufacturing Practice Guide for Active Pharmaceutical Ingredients for supplier, material, batch, laboratory-control, and document-control concepts used in regulated quality systems.
- ICH Q10: Pharmaceutical Quality System for management of quality risks, corrective actions, change management, and continual improvement.
- USP General Chapter 1223 Validation of Alternative Microbiological Methods as a starting point for understanding why method context and validation language matter, even when a buyer is only reviewing supplier claims at a high level.
- ISO 9001 quality management principles for supplier evaluation, documented information, and process-control concepts.
Do not use these references to imply that a research peptide supplier is GMP-certified, clinically appropriate, or suitable for human use. Use them to explain why a buyer should ask boring, evidence-based questions.
FAQ
Bottom line
A Canadian research peptide supplier audit questionnaire should make trust inspectable. It should ask for current lot-specific documents, clear identity support, traceable records, storage assumptions, RUO-safe claims, and support answers that stay in the documentation lane.
The questionnaire is not a guarantee and not a shortcut. It is a precondition for a defensible scorecard. If the answers are complete, move to the scorecard and COA checklist. If the answers are missing, clarify. If the answers cross into personal-use guidance, reject the supplier for RUO procurement screening and keep the record.
Further reading
Recovery
Research Peptide Supplier Scorecard for Canadian Buyers
Quick answer: what belongs in a research peptide supplier scorecard? A research peptide supplier scorecard is a structured way to compare Canadian research-material suppliers...
Recovery
Peptide COA Verification Checklist for Canadian Research Buyers
Quick answer: how to verify a peptide COA A peptide COA verification checklist should let a Canadian research buyer answer a narrow question before relying on any vial, blend, or...
Recovery
Research Peptide COA Request Email Template for Canadian Buyers
Quick answer: what should a peptide COA request email ask for? A research peptide COA request email should ask the supplier for current, batch-specific documentation that connects...