Puratek was founded by researchers who kept receiving compounds with no traceable documentation. Our answer: test every batch independently, publish the result, print the lot number on the vial.
2025
Puratek Begins
Built around independent testing, clear transparency, and consistent batch standards.
2021
Public COA library
Certificates moved out of email and onto the product page, making verification faster, simpler, more transparent, and instantly accessible for researchers.
99%
Purity Standard
16000+
Orders
100%
COA Verified
Shipping
Monday–Friday
OUR PURPOSE
A higher standard for research transparency.
Our purpose is simple: make verification, documentation, and traceability part of every batch—not something researchers have to ask for.
01
Our vision
Make verification the default, not
the upgrade
Researchers should never have to request proof of what they bought. We publish the assay first and let the documentation do the selling.
02
Our vision
A supply chain a scientist can audit end to end
From synthesis lot to shipping label, every step traceable from a single batch number — the standard we hold ourselves to as the catalog grows.
SHOP RESEARCH PEPTIDES
Core values
01
Evidence Over Claims
If we cannot show the assay behind a number, we do not print the number.
02
Radical Documentation
Certificates are public by default and tied to the exact lot in your package.
03
Scientific Rigour
HPLC and mass spectrometry on every lot, run by a lab with no stake in the result.
04
Full Traceability
One batch number connects the synthesis lot, the assay and the shipment.
05
Consistency
The same specification lot after lot, so your results stay comparable over time.
06
Straight Answers
A real person replies to documentation questions, Mon–Fri 9am–4pm PST.
OUR PURPOSE
How a batch becomes releasable
Every batch must pass Puratek’s 8x testing standard before it is approved for release. These four checkpoints summarize the key stages of that process. If a batch fails any required test or verification step, it does not ship.
01
Synthesis & Intake
Each incoming lot is logged, documented, and assigned a Puratek batch number for traceability.
02
Purity & Identity Testing
Independent laboratory testing verifies purity and confirms the compound identity against the expected specification.
03
Quality & Batch Verification
Testing results, lot details, and supporting documentation are reviewed to confirm the batch meets Puratek’s required quality standards.
04
Final Approval & COA
After all eight testing requirements are successfully completed, the batch is approved for release and its batch-specific COA is published.
What Researchers Say
Questions Before You Order Confidently
Are Puratek products for human use?
No. Every product we sell is strictly for laboratory and research use only. They are not intended for human or animal consumption, or for diagnostic, therapeutic or clinical use.
Where can I find the certificate of analysis?
The certificate of analysis is published on the relevant product page and linked to the exact batch or lot number. This allows you to review the available testing documentation before placing an order.
Who performs the purity testing?
Purity and identity testing are performed by an independent third-party laboratory with no financial stake in the result. Released batches are evaluated using methods such as HPLC and mass spectrometry.
Which countries do you ship to?
We currently ship to the United States and Puerto Rico. Select your country or region at checkout to view the available address and delivery options.
What happens if a batch fails testing?
A batch that does not meet Puratek’s required specifications is not released for sale. It is rejected rather than discounted, relabelled, or supplied without verified documentation.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature
session
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
Name
Description
Duration
affwp_ref
Stores the referring affiliate ID for commission attribution.
30 days
affwp_ref_visit_id
Stores the visit ID linked to the referring affiliate.
30 days
affwp_campaign
Stores the affiliate campaign name for tracking purposes.