Wholesale peptide application checklist.

Why a wholesale account exists

A wholesale account is the buyer-side counterpart to the lot-record discipline described in the quality assurance process. Catalog browsing on PeptideDistro.com is open and indexable; pricing, minimum order quantity (MOQ) tiers, lead time, certificates of analysis, and batch documentation packets are reviewed once the buyer is identified, the qualified-buyer status is attested, and the intended-use scope is on the record. The account is what ties lot-specific records — every COA, every chromatogram, every batch packet — to a buyer the desk can stand behind. It also enables recurring-program pricing, custom blend or private label scoping, and consistent destination/handling routing across multiple shipments.

This article is a checklist. It walks through the fields the wholesale desk actually reviews on the wholesale application, the supporting context that speeds first-response, and the downstream pieces — quote desk, COA routing, custom-blend intake — that depend on the account being on file. Procurement and lab-management readers should be able to assemble a complete submission in a single sitting once the items below are gathered.

Business record fields

The first block on the application is the business record itself. The desk needs a clear answer to “who is the buyer?” before it can route pricing or documentation. Fields gathered:

• Legal business name as registered in the operating jurisdiction. DBAs are recorded separately if they differ from the legal name.
• Operating address (street, city, state, postal code, country). Used for shipping/handling routing.
• Tax / business identifier appropriate to the jurisdiction (US EIN, state reseller number where applicable, VAT number for international entities).
• Website URL if the entity has a public web presence; institutional, hospital, university, or company URL.
• Organization type: academic / university research lab, independent research laboratory, pharmaceutical / biotech, contract research organization (CRO), compounding pharmacy (research procurement), distributor / reseller, private-label buyer, procurement team, or other qualified buyer category.
• Years operating and rough size (employee headcount range or research-program size). Used by the desk for context, not as a hard threshold.

Buyer contacts

Two contacts are useful on the application even if a single person is initiating the request. The first is the commercial contact — the person the desk replies to for pricing, account changes, and recurring-program scoping. The second is the technical contact — the lab manager, principal investigator, QA lead, or research-program lead the desk reaches when a documentation question is technical (sequence reference, modification clarification, COA-field interpretation). Each contact carries name, title or role, business email, and phone where available.

For larger procurement organizations, a separate finance / billing contact shortens the cycle for net-terms and PO-based programs once the account is approved. PeptideDistro.com does not display public pricing; net-terms and program-pricing options are scoped during the post-approval onboarding conversation.

Intended-use scope

The intended-use scope is the highest-leverage field on the application. The desk reviews it directly and uses it to pre-route lot-record diligence. A complete intended-use scope includes:

• Research-program area: in vitro assay development, screening libraries, analytical reference, target validation, identity standards, instrument-method development, formulation feasibility (RUO), or other research-workflow context.
• Compound or family of interest: specific peptides or research categories (recovery and repair, GH secretagogues, melanocortin research, etc.). Linking categories from the peptide directory is acceptable.
• Volume / scale context: sample-pack scale, mid-scale research-program (10–50 vials per peptide), or recurring-program scale. The desk does not require firm numbers at intake; ranges are fine.
• Documentation needs: standard COA only, full batch documentation packets, redacted samples for institutional review, or recurring records for an audit-driven program.
• Destination & handling: domestic US, international, cold-chain shipping, lab receiving constraints (loading-dock hours, signature requirements).

Importantly, the intended-use scope does not need to include patient-facing, clinical, or therapeutic context — and should not. PeptideDistro.com does not supply material into clinical, consumer, supplement, or cosmetic channels, and the application form is structured to keep that boundary clean.

Qualified-buyer attestations

Two attestations are required at intake and recorded against the account record. The first is the research-use attestation: the buyer confirms that compounds will not be used for human or animal consumption, therapeutic claims, or downstream resale as drugs, supplements, or cosmetics. The second is the wholesale-terms attestation: the buyer acknowledges the Terms of Service, Privacy Policy, and Wholesale Terms. Each attestation is timestamped and IP-hashed at intake; both flow into the account-record audit trail. The same attestations are required on quote requests, document requests, and custom blend intakes — once an account is on file, the attestation snapshot is reused with each individual transaction.

Procurement teams in regulated environments should treat these attestations the way they treat any other supplier-side affirmation: the institutional procurement policy controls whether the attestation envelope matches the buyer’s actual use case, and that fit is the buyer’s responsibility under applicable rules. A useful sanity check: would the buyer’s research review board, IRB, or institutional procurement office sign off on a purchase under the “research use only” envelope? If the answer is unclear, the application should pause until the institutional path is confirmed.

Documentation that travels with the account

Once approved, the account becomes the routing point for lot-specific records. The COA & document library is the public surface; the account record is the private backing. Documents the desk routes against an approved account include:

• Lot-specific certificates of analysis (one per shipment, retained for record continuity).
• Batch documentation packets (COA + chromatogram + MS spectrum + lot/expiration + fill counts + label artwork for private-label or custom-blend lots).
• HPLC chromatograms and MS spectra on request for identity-confirmation review.
• Stability and storage records.
• Sample documentation packets for institutional diligence (also available pre-approval).

Records are tied to the account record and the source lot, so re-routing on later request — for audit, for research-program close-out, for downstream documentation — is a single desk operation rather than a manual reconstruction.

MOQ and pricing context

PeptideDistro.com does not display public pricing or MOQ tiers. Pricing is reviewed against the account record because the relevant variables — destination country, documentation needs, recurring-program cadence, custom-blend scope, white-label packaging, lead-time tolerance — meaningfully change pricing at the program level. Procurement teams should treat the wholesale application as the gateway to a pricing conversation rather than as a direct quote tool. The quote request desk is the right surface for SKU-level pricing once the account record is established; the custom blend intake handles composition, label, and packaging scope for blend or private-label programs.

Application timeline

First response from the wholesale desk is typically within one to two business days for a complete application. Decisions depend on the completeness of the business record, the qualified-buyer attestations, and the intended-use scope provided. Incomplete applications are returned with a specific list of missing fields rather than declined; this keeps the cycle short for buyers who need to come back with one or two additional pieces of information. After approval, an onboarding email confirms the account record, the recurring-program contact path, and the documentation-routing options enabled on the account.

Submission checklist

• Legal business name, operating address, and tax/business identifier ready.
• Organization type selected; institutional or company website URL on hand.
• Commercial contact and technical contact identified (name, title, business email).
• Intended-use scope drafted: research area, compound family, volume range, documentation needs, destination.
• Research-use attestation reviewed against institutional procurement policy.
• Wholesale Terms, Terms of Service, and Privacy Policy reviewed.
• Sample documentation packet requested separately if pre-approval diligence is required.
• Custom blend or private-label scope drafted separately if the program goes beyond the catalog.

Related material

Continue reading: How to read a peptide certificate of analysis and HPLC and mass spectrometry for research peptides describe the documents and analytical record that flow into an approved account. The COA & document library documents how lot-specific records are routed, and the quality assurance page covers the supplier-qualification, identity, and lot-release process behind every released lot. To open an account, use the wholesale application or, for SKU-specific pricing, the quote request desk.

Sources & references

• U.S. Food and Drug Administration, Research-use-only product labeling guidance. fda.gov
• National Institutes of Health, Office of Research Compliance and procurement guidance. oir.nih.gov
• Council of Chief State School Officers and academic research-procurement guidance summaries (institutional purchasing policies, used for context).
• PeptideDistro.com, Wholesale Terms, Compliance Overview, and Quality Assurance documents (linked above).

Frequently asked questions