A research product specification should let a reviewer identify a material, understand every stated quantity and connect the listing to the right supporting records. A product name and a milligram figure are useful starting points, but they are not a complete technical description. The most reliable approach is to review identity, amount, presentation and evidence as separate fields.
This guide explains how to read a research product specification, which questions to ask and how to create a short comparison record before placing an order.
Research product specification checklist
| Field | What to confirm |
|---|---|
| Identity | Catalogue name, product code and unambiguous chemical identity |
| Composition | Named constituents and the stated amount of each |
| Quantity basis | Whether a value describes mass, volume, concentration or a whole container |
| Presentation | The supplied format, such as a pre-filled pen or nasal spray |
| Traceability | Batch or lot reference, relevant dates and record version |
| Evidence | Supporting files that match the same identity and batch |
Start with product identity
Record the catalogue name and product code, then look for an unambiguous chemical identity. For a mixture, list every named constituent and its stated amount. A trade name can help locate a listing, but it cannot supply composition details that the record does not contain.
Keep unanswered questions visible. If identity information is missing, request it rather than mapping a familiar-looking name to a compound. This matters when comparing records from different suppliers, because similar names may sit beside different compositions or presentations.
Separate mass, volume and concentration
Milligrams describe mass, while millilitres describe volume. A mass concentration relates a mass to a volume. These quantities answer different questions, so a value stated in mg should not be read as though it were stated in mg/mL. NIST’s SI guide explains the distinction.
For every number, write down what it describes: one constituent, the complete formulation or the whole container. Also distinguish a supplier-stated listing value from an independent laboratory measurement.
Keep product codes and batch references separate
A product code identifies a catalogue item. A batch reference connects a particular lot to the records intended to describe it. Save both, along with the date and version of the specification reviewed. Our guide to batch information and traceability explains how these fields work together.
For example, Remedium Retatrutide 30 mg and Remedium Retatrutide 50 mg are separate catalogue records. Their stated amounts distinguish the listings; they do not establish suitability for a particular experiment.
Match supporting documents to the same record
A specification becomes more useful when its identity, batch reference and supporting documents agree. Before relying on a file, check that it concerns the same item and batch. Record discrepancies and request clarification. The certificate of analysis review guide provides a practical document checklist.
Build a short comparison record
Create one row for identity, composition, quantity basis, format, batch reference and supporting files. Beside each field, record its source and any outstanding question. This turns a vague concern into a specific request a retailer can answer.
When presentation matters, compare the fields in our pre-filled pen and nasal spray format guide. You can also review the full Apollex quality and transparency framework.
Frequently asked questions
What should a product specification include?
At minimum, it should identify the product, state the relevant amount and unit, describe the supplied format and provide enough traceability information to connect the item with its records.
Is a product name enough to establish composition?
No. A catalogue or trade name helps locate a record, but composition should be stated directly and supported by the applicable documentation.
Why does the unit matter?
Mass, volume and concentration describe different quantities. A comparison is meaningful only when the value, unit and basis refer to the same thing.
This guide concerns research documentation. It provides no directions for personal use and does not verify any individual product.