How to Write a BPC-157 TB-500 Bundle Specification Request

A BPC-157 TB-500 bundle specification request is only useful if the person receiving it can answer it clearly. Too often the request is a long list of loosely worded questions, copied from an old template, that mixes up the bundle as a commercial offer with the individual items inside it. The replies that come back are just as muddled.

This guide shows how to write a tighter request, using CLOVA's STRENGTH bundle as the example. The aim is a short document that separates bundle questions from item questions, flags what is essential, and keeps every number tied to its unit.

Know what the bundle actually contains

Before writing a single question, pin down the subject. The STRENGTH bundle is two separate pens sold together: KLIK500 (TB-500 10mg/2mL) and KLIK157 (BPC-157 10mg/2mL). It is not a premixed blend, so it has two products, two labels and two sets of details. Like everything CLOVA sells, it is supplied for research use only.

That shapes the whole request. Questions about price, availability and delivery belong to the bundle. Questions about content, batch numbers and test reports belong to each pen. Write them as one undivided list and the answers end up attached to the wrong thing.

Split your questions into two sections

A simple structure works well.

Section A, the bundle as an offer

• Which items are included, by product and label name
• Quantity: how many bundles, and how many pens that means
• Current terms, delivery method and dispatch timing

Section B, each pen answered separately

• Stated peptide content and volume, with units
• Batch number printed on the label
• Whether a Certificate of Analysis is available for that batch
• Storage conditions stated for that item (CLOVA's storage guide covers the general requirements)

Ask the supplier to answer Section B once for KLIK500 and once for KLIK157. If the same answer applies to both, they can say so, but you will know it was considered for each.

Mark what is essential and what is just helpful

Not every question carries the same weight. Some details could decide whether the purchase goes ahead at all. Others simply make planning easier. Label them, for example "Required" and "Useful", and add a one-line reason beside each required item.

This does two jobs. It tells the supplier where to focus. And it stops a preference, such as a particular delivery day, quietly turning into a pass or fail rule that nobody agreed. The researcher who owns the project should set the required items; purchasing staff can then pass them on accurately without guessing what matters.

Keep numbers attached to their meaning

Ambiguous quantities cause more confusion than almost anything else. "Quantity 2" could mean two bundles or two pens. "10mg" could be a label figure for one pen or a total for the bundle. When you ask about an amount, say what it describes and which unit you expect.

Record the answers the same way. A good habit is to write each amount as "what it describes, number, unit, source", such as "KLIK157 stated content, 10, mg, product page". It takes seconds and saves a lot of untangling later.

Ask for records that fit the question

A product description and a test report do different jobs. The description tells you what the seller states; a Certificate of Analysis reports findings for a particular batch. Ask for the record that answers your actual question, not "all available documents".

For CLOVA products, reports are published on the Certificates of Analysis page and on product pages where a report is available. In a two-pen bundle, check whether there is a report for each pen's batch, and match each batch number on the labels to its own report.

A quick pre-send checklist

Before the request goes out, check that it:

1. Names the bundle and both pens exactly as listed
2. Separates bundle-level and pen-level questions
3. Marks each question Required or Useful, with a reason for each required one
4. States the unit and meaning of every amount you ask about
5. Asks for specific records, tied to batch numbers
6. Says what stage you are at, such as gathering information or preparing to order

Frequently asked questions

Do I need a separate specification for each pen in a bundle?

It is the clearest approach. The STRENGTH bundle contains two different products, so content, batch and documentation details apply to each pen individually. Asking once per pen stops an answer for one being read as covering both.

What if the supplier answers only part of the request?

Record what was answered and what was not, then send a short follow-up on the missing items only. A partial reply is still progress, as long as you do not mark the whole request complete.

Is it worth asking for a full technical file instead?

Usually not at the first stage. A broad request tends to produce a large attachment that still leaves your real question open. Ask for the specific detail blocking your decision, then follow up if another question appears.