Grey Market Peptides: What the Label Means for Sellers

Is selling grey market peptides illegal?

Here, grey market peptides is a descriptive term for products promoted outside an approved-drug framework, not a legal category or permission to sell. FDA's August 2026 letters said research-use labels did not override website evidence of intended human drug use in the cited cases. You should assess your own product, claims and sales context with qualified counsel. [1][4]

If you run or are considering a United States research use only store, your useful starting point is a specific catalog question. You need to establish what you propose to offer, what your pages communicate, and which unresolved facts require professional review. A broad market label cannot perform that work for you.

Use this article to assemble a review packet, compare the cited cases carefully, and separate supplier paperwork from questions about your own business. The worksheets are suggested internal review tools. They do not prescribe legal requirements, provide replacement marketing language, or establish permission to proceed.

Key Facts

• FDA's Peptide Partners letter, dated August 24, 2026, said research-use wording did not overcome website evidence of intended human drug use in that case. [1]
• FDA's NuScience letter, also dated August 24, 2026, addressed laboratory and research wording alongside website evidence. [4]
• FDA cited bacteriostatic water and a peptide calculator together in the NuScience assessment; its Royal Peptides letter also cited a peptide guide. [3][5]
• FDA described the specified Peptide Partners products as unapproved new drugs, a finding tied to those products and the evidence in that letter. [6]
• FDA cautioned that the violations identified in its Peptide Partners letter were not an all-inclusive list. You should not use the listed examples as an exhaustive review checklist. [7]

TL;DR

You cannot determine your store's status from the phrase grey market peptides or from a research-use label alone; the cited FDA letters considered surrounding evidence. [1][4] Build a product and claims inventory, map linked resources, and separate supplier identity and lot documents from intended-use questions. Take the unresolved issues to qualified counsel before making a catalog decision, using the worksheets below as preparation rather than a legal test.

The working meaning of grey market peptides

Use grey market peptides here as a working description, never as a decision about your legal status. Your practical task is to replace that broad phrase with specific questions about products, statements, documents, and intended business activity. See also Can you legally resell peptides?.

The term is the starting vocabulary for this article. It does not tell you whether a particular item has an approved application, how FDA would assess your own website, or what conclusion counsel would reach about your proposed activity. In the cited Peptide Partners case, FDA made a finding about identified products and the website evidence it described. That is a materially narrower statement than a verdict about every business someone might call grey market. [1][6]

A term-versus-conclusion box

Use the box when you discuss the project with a colleague or adviser. If you hear that a proposed catalog is acceptable because it is research only, ask which fact that sentence establishes. If the answer merely repeats the label, you have identified a circular answer. You still need the underlying product facts and the actual content that customers would encounter.

For a hypothetical internal planning example, imagine your draft business brief says only that you intend to operate a grey market peptide store. You cannot assign useful review work from that sentence. Replace it with a neutral description of the proposed catalog, the claimed research context, the location of draft pages, and the question you want counsel to assess. Do not add a conclusion about permissibility to make the description sound complete.

Keep your description separate from your desired outcome. You may want a clear catalog decision, but that wish is not evidence that a particular decision is available. A useful intake statement says what you know and what remains unresolved. It lets an adviser distinguish missing facts from a disagreement about their meaning.

You can also use a simple vocabulary check before circulating the packet. Highlight every appearance of acceptable, legitimate, compliant, and approved. For each appearance, ask whether you mean document received, information checked, professional opinion obtained, or an actual agency status. Replace ambiguous internal shorthand with the narrower meaning you can support. This is an editorial discipline for your packet, not a proposed wording strategy for selling products.

Your work product from this section is a short scope note. It should identify the business question, explain your working use of grey market, and state what the note does not decide. Keep that scope note at the front of the packet so later worksheets answer the same question.

Is selling grey market peptides illegal?

Only a case-specific assessment can answer that; this article cannot classify your proposed store as legal or illegal.

Start with the subject of your question. Are you asking about a particular catalog item, a statement you plan to publish, a proposed distribution arrangement, or the whole business? If you combine those subjects in a single yes-or-no request, you make it harder to see which fact controls which part of the answer. Use a separate question for each unresolved issue, then ask counsel how the answers interact.

A conditional review map

The branches are an organizing method, not a legal decision tree. A completed row means you have framed a question. It does not mean you have satisfied a legal condition. Keep the distinction visible if someone else will use your spreadsheet during a planning meeting.

FDA's Peptide Partners letter supplies an example of why the product branch matters. FDA stated that no approved applications were in effect for the specified products and described them as unapproved new drugs. You should attribute that conclusion to FDA and those products, rather than assuming that the conclusion automatically covers an unidentified item in your own proposed catalog. [6]

The intended-use branch needs its own evidence. The same letter said the website established intended human drug use despite the research wording. A supplier document about a material is therefore answering a different question from the question raised by that website evidence. Combining them into a single green status cell would conceal the distinction you are trying to understand. [1]

For a hypothetical catalog meeting, suppose you have complete product identity information but unresolved questions about page statements. Record the identity work as complete within its own limited scope and leave the statements question open. Do not describe the entire product review as finished simply because the easiest part has an answer. Conversely, do not discard useful identity information because a different issue remains unresolved.

For related framing, see the questions behind selling peptides online.

Research-use labels and the evidence around them

You should read your research-use wording together with the rest of the customer-facing material. FDA explicitly considered website evidence despite research or laboratory labels in the cited Peptide Partners and NuScience cases. [1][4]

Treat the label as an item to inspect, rather than the answer key for every other item. Your review packet should let someone see both the statement of purpose and any surrounding statement that appears to describe a different purpose. You do not need to decide the legal significance yourself to identify that the materials require a combined review.

In the Peptide Partners letter, FDA described research-use and non-human-use language before explaining its website-based finding. In the NuScience letter, FDA similarly addressed laboratory, research, and analytical wording before stating its conclusion about the website evidence. These are case-specific examples of the relationship between a label and surrounding context. They do not provide a formula for rewriting your pages. [1][4]

A paired-reading exercise

For a hypothetical internal exercise, place a draft label beside its product page and read them as a pair. In your left-hand notes, copy what the label states about purpose. In your right-hand notes, identify the page statements that need review. Keep the source wording intact within the internal materials, and describe your uncertainty in a separate note.

Your observation column should be plain enough for another person to reproduce. For example, in a hypothetical review, “the category introduction adds a purpose statement absent from the item page” is more useful than “the category is risky.” The former identifies a comparison to inspect. The latter skips from an impression to a conclusion without showing the underlying material.

Handle incomplete pairings explicitly. If you have a label but no available page version, mark the page unavailable. If you have a draft page but the label is still proposed, mark the label proposed. Do not compare a current item with an imagined counterpart and then treat the comparison as observed business evidence.

Your handoff test is whether a reviewer can see the same pair you saw. Ask a colleague to locate the label statement and the page statement using only the references in your packet. If the colleague needs your memory to identify the material, improve the references before passing the issue onward. This tests the usability of your packet; it does not test whether the content is permissible.

You can use the explanation of research-use wording for related background.

Website statements that influenced FDA's assessment

FDA's Peptide Partners letter identified product labeling, including website content, as evidence of intended use, and it did not treat the research-use wording as controlling. [2][1] Use a claim card to isolate the passage you want assessed and the question you need answered.

Begin your page review at the level of a claim, not at the level of an entire website. A site can contain a category introduction, an item description, a comparison chart, and a support answer that say different things. Your internal worksheet should let you point to the exact statement under review and the context needed to read it accurately.

An annotated case table

Use a claim card for each passage that needs assessment. Give the card a short neutral name, the page reference, the exact passage in your internal packet, its location on the page, and the reason you are escalating it. Attach enough surrounding content for the passage to make sense. Put your interpretation in a separate field so a reviewer can disagree with it without losing the observation.

For a hypothetical claim card, imagine a product page contains a statement about an effect in people. In the public article, you do not need to repeat the effect or offer a substitute claim. In your internal review, you should identify the passage, mark the human-effect concern, and send the context for qualified assessment. That keeps your work focused on identifying an issue rather than developing promotional wording.

Distinguish a claim you authored from a statement appearing somewhere you do not control. Record where each statement came from and how it became associated with the page. Do not assume that a quotation, embedded passage, or linked reference has a particular legal significance merely because you can describe its source. That significance is a separate question for counsel.

Adjacent products and tools as contextual evidence

You should map linked tools and companion products because FDA cited that surrounding context in the NuScience and Royal Peptides letters. The NuScience passage names bacteriostatic water alongside a peptide calculator; the Royal passage names bacteriostatic water alongside a guide and calculator. [3][5]

Those findings make a page-only inventory incomplete as a description of the cited cases. They do not establish that every tool, link, or companion item has the same significance in every setting. Your task is to show the relationship among the materials you actually present and let qualified counsel assess what the combined context means for your circumstances.

A relationship map you can hand off

This map is about context. Do not turn it into instructions for operating a calculator, preparing a product, or changing a resource to avoid scrutiny. You can document the presence and relationship of the material without explaining how someone would use it.

For a hypothetical review example, imagine that your item description contains only a short research statement while a shared navigation link leads to another resource. Your page inventory and your resource inventory would each look sparse if read separately. The relationship map lets an adviser see that the resource is reachable from the item page. It adds a missing connection without asserting a legal conclusion about that connection.

Use distinct labels for observed, proposed, and unresolved relationships. An observed relationship is one you can locate in the material under review. A proposed relationship appears in a draft that has not been presented as current. An unresolved relationship is one you have not been able to establish. Avoid using a blank cell for all of these conditions because a blank gives the next reviewer no usable information.

An unavailable destination is an exception worth preserving. Record the reference and state that you could not inspect its content in the review materials. Do not infer what it contains from its title alone. If a resource is available only in a draft attachment, attach that version and label it accordingly. Your packet should show what you actually examined, including where examination stopped.

Your responsibility test is to assign ownership to the connection as well as the destination. Ask who maintains the product page, who maintains the linked resource, and who can explain why they are associated. If different people own those surfaces, ask them to confirm the relationship in the same packet. That prevents a handoff in which each person describes only their own isolated page.

A case comparison across three FDA letters

You should compare the cited FDA letters by recipient, date, wording, and surrounding evidence, keeping every finding attached to its own case. The comparison below covers Peptide Partners, NuScience Peptides, and Royal Peptides and uses their letters dated August 24, 2026. [1][3][4][5]

The unresolved cell is useful. It shows the limit of the evidence presented in this comparison. You should not fill it by assuming that similar recipients used identical labels. Nor should you infer from the limited excerpt that Royal did or did not use particular wording. The cell concerns what this comparison supports, not everything that might appear elsewhere in the full record.

Supplier documentation and its limited role

You should examine supplier identity, lot traceability, and test assertions as a separate internal due-diligence exercise.

Start by stating what you expect each document to establish. If you request identity information, your immediate question is who supplied the material and how the document connects to that entity. If you request lot information, your immediate question is whether the identifiers connect the document to the item under review. If you examine a test assertion, your immediate question is what the document actually states and what remains unclear.

These are suggested document-review questions, not a list of statutory requirements. You should not tell a supplier that this article establishes a required document format.

A supplier-document worksheet

For a hypothetical document exception, imagine that a certificate names a product while your inventory record uses a different identifier. Your immediate finding is that you cannot yet connect the records. Do not upgrade that observation into a finding that the material is acceptable, unacceptable, authentic, or inauthentic. Ask for the information needed to reconcile the identifiers and keep the unresolved connection visible.

For a different hypothetical exception, imagine that the identifiers match but the test assertion is not clear to you. Completing the traceability check does not complete the technical assessment. Assign the unclear assertion to someone qualified to interpret it. Your responsibility is to make the question specific and provide the relevant document, rather than inventing a test standard or threshold that is absent from your evidence.

Keep the supplier response in the question's own lane. An explanation of a lot identifier can resolve a traceability question. It cannot, merely by being detailed or confident, answer what your website communicates or establish the approval status relevant to your proposed activity. The FDA case passages support keeping those website and approval issues explicit. [1][6]

You can prepare this work with the distinction between batch-specific and generic COAs and a supplier-vetting checklist. Use those links as related reading, not as an endorsement of a supplier or a substitute for interpreting the documents you actually have.

Your final work product is a document index with a clear question beside each item. Keep the index separate from the claims inventory, then cross-reference it where the same catalog item appears. That gives counsel and technical reviewers access to the relevant material without suggesting that either review has answered the other's questions.

A seller's page and catalog review worksheet

You should connect each catalog item to its pages, promotional statements, support material, and linked resources in a single review worksheet. FDA's cited labeling and contextual evidence provide the reason to examine those surfaces together; the worksheet itself is a suggested internal method. [2][3]

Use the worksheet to expose gaps in ownership and evidence. A catalog entry can tell you what an item is called, but it does not automatically tell you which page version, advertising statement, or support answer is associated with it. A useful row connects the item to the actual material and names the person who can explain that material.

The entries in the following table are hypothetical internal examples, including the invented item names and review assignments. They are not descriptions of actual products, customers, advertising, or findings.

Make review states describe real progress

Use statuses that correspond to observable work. Materials requested means you have identified something you need. Materials assembled means you have the relevant material in the packet. Question framed means you have explained the uncertainty. Assessment pending means the question is waiting with the appropriate reviewer. None of those statuses should be shortened to approved.

For each row, write an exit condition before you ask someone to work on it. A page owner might finish when the complete version and its associated statements are identifiable. A supplier-record owner might finish when the document references are connected to the catalog item. Counsel's assessment is a different task with a different scope. Keeping those exits distinct prevents an administrative completion from becoming an accidental legal conclusion.

An empty advertising field deserves an explicit explanation. It might mean you have no advertising associated with the item, have not asked the responsible person, or have not received the material. Use the explanation that reflects your actual observation. Do not let an unexamined blank look like a completed absence check.

Apply the same discipline to support content. If you have a shared template rather than an item-specific answer, record that relationship. If you have only a proposed template, mark it as proposed. You do not need to write example customer instructions to show that the support surface belongs in the review; the reference and the unresolved question are sufficient.

For related organization, see the product-page review framework.

Questions to take to qualified counsel

You should take unresolved product, intended-use, and distribution questions to qualified counsel with the underlying materials attached. FDA's reminder that its Peptide Partners letter was not an all-inclusive list supports avoiding an assumption that the examples in this article exhaust the issues your business may need to address. [7]

Begin your request with the decision you need help making. State whether you are evaluating a proposed catalog, assessing current materials, or trying to understand a particular unresolved product question. Describe the relevant facts without asking counsel to validate a conclusion you have already embedded in the request.

Your escalation packet

Use questions that invite a scoped answer. Ask which additional product facts are needed to assess the proposed activity. Ask how the actual page materials and their context affect the assessment. Ask which distribution details or jurisdictions need further consideration. Ask what remains outside the scope of the review you have requested. Avoid turning the request into a demand for a blanket statement about all grey market peptides.

Set responsibility for follow-up before the meeting ends. Identify who will answer missing catalog questions, who will provide the relevant page version, and who will return any technical document clarification. Your internal handoff should assign the collection of facts to the people who can supply them, while leaving legal interpretation with counsel.

When you receive an assessment, compare its scope with your original question. Check which items, versions, proposed activities, and assumptions it addresses. If your business proposal later differs from those facts, take the difference back for review rather than extending the earlier answer yourself. This is a suggested way to preserve the meaning of professional advice, not a statement of a statutory review schedule.

Use the guide to working with a peptide business attorney to prepare the conversation.

What to do next

You should move from defining the term to assembling the specific evidence counsel needs, in the following order.

1. Record what grey market means in your planning discussion without treating it as a legal status. Write the scope note before assigning review tasks so your product, page, and supplier questions stay attached to the same proposed activity.

2. List each current or proposed SKU and its product-page, advertising, and support statements. Identify the relevant versions and the person who can supply missing materials, rather than describing an unexamined field as complete.

3. Flag statements about human effects or disease for qualified review, using FDA's cited website-evidence categories as comparison points. Preserve the actual context in your internal packet instead of developing replacement promotional claims. [1][2]

4. Record whether linked tools or companion products add context to the material under review. Map the actual relationships and mark anything you could not inspect, taking account of the contextual examples FDA cited. [3][5]

5. Keep supplier identity and lot records in a separate evidence packet. State the limited question each document can help answer and do not treat a certificate of analysis as authorization for your proposed business activity.

6. Have qualified counsel assess unresolved product, intended-use, and distribution questions before your catalog decision. Bring the scope note and connected evidence, and ask what remains outside the assessment rather than assuming the cited case examples cover every issue. [7]

When should you book a peptide business fit call?

Book a peptide business fit call when you have a current or proposed catalog and need help organizing a clearer operator review workflow. Bring your claims inventory, linked-resource map, and unresolved review questions so you can discuss who owns the next work. The call does not certify legality or replace qualified counsel's assessment.

Frequently Asked Questions

Is selling grey market peptides illegal?

You cannot determine your own legal status from that descriptive phrase. FDA's cited Peptide Partners findings were tied to specified products and evidence, including website statements and approval status. [1][6] Take your actual product, claims, and distribution facts to qualified counsel for a case-specific assessment.

What should a seller make of grey market peptides websites?

You should examine what your own pages communicate and which surrounding resources they connect to. FDA cited product labeling, including website content, as evidence in the Peptide Partners case. [2] Use a claim-level inventory and relationship map to prepare your review, rather than treating another website as a model of acceptable conduct.

What should a seller make of a grey market peptides forum?

Treat a forum discussion as a list of questions to check, not as a finding about your business. Write each open forum question on its own line in your packet, with the page where you saw it and the date you checked it. Compare any question it raises with your actual facts and the scope of the cited FDA cases, then ask qualified counsel to assess what remains unresolved. FDA's Peptide Partners conclusion addressed the specified products. [6]

How can a seller assess a peptide supplier's legitimacy?

You can begin with internal questions about supplier identity, product identifiers, lot connections, and the scope of test assertions. Treat unresolved documents as questions for the appropriate reviewer, not as grounds for a vendor recommendation. Keep that work separate from your website and approval questions because the cited FDA assessment concerned those issues directly. [1][6]

Sources

You can trace the case statements above to the following FDA letters; repeated entries identify the distinct passages supporting the corresponding citations.

1. U.S. Food and Drug Administration, Peptide Partners LLC Warning Letter, research-use wording and website evidence, accessed 2026-09-30.

2. U.S. Food and Drug Administration, Peptide Partners LLC Warning Letter, product-labeling and website evidence, accessed 2026-09-30.

3. U.S. Food and Drug Administration, NuScience Peptides LLC Warning Letter, adjacent products and calculator, accessed 2026-09-30.

4. U.S. Food and Drug Administration, NuScience Peptides LLC Warning Letter, laboratory and research wording, accessed 2026-09-30.

5. U.S. Food and Drug Administration, Royal Peptides LLC Warning Letter, adjacent products, guide and calculator, accessed 2026-09-30.

6. U.S. Food and Drug Administration, Peptide Partners LLC Warning Letter, specified products and approval status, accessed 2026-09-30.

7. U.S. Food and Drug Administration, Peptide Partners LLC Warning Letter, scope of observed violations, accessed 2026-09-30.

Educational and legal disclaimer

You should use this article for education only, not as legal, regulatory, tax, banking, medical, product, import, platform, or payment advice. You should obtain qualified advice for your specific products, claims, business activity, and jurisdiction. This article does not provide directions for personal use, recommend products, or establish that any proposed catalog or business is permissible.