RUO Website Compliance Checklist: Disclaimers, Attestation, Age Gates and Copy
A page-by-page RUO website checklist covering disclaimers, copy, imagery, checkout confirmations and review operations. Not legal advice.
Read the guidePlatform · Access
Age gate and attestationstored on every order.
Access controls decide who reaches your store and what each buyer confirms at checkout. We configure them with you and store the result on every order, so your team can show what was confirmed and when. The settings implement your policies. They are not legal advice.
Three store access modes.
Choose how visitors reach the catalog. Open lets anyone browse. Age gate asks visitors to confirm the minimum age before entering. Accounts-only keeps the catalog behind sign-in. You can change the mode in the admin as your policy changes.
- Open
- Age gate
- Accounts-only
Attestation and age on every order.
The minimum age is configurable from 18 to 25. The research-use attestation text is yours to write with counsel. At checkout the buyer confirms both, and the attestation and minimum age are stored with the order. Your team sees them alongside the order in the admin.
PepXLabs demo store · sample data
What an age gate is, and is not.
An age gate records a self-declared age. It is not document or database ID verification. If your counsel requires ID verification, we scope that integration on the call rather than suggest the age gate replaces it.
Why store the attestation with the order.
A checkbox that is not saved proves little later. Because the attestation text and minimum age are stored with each order, your team can see what the buyer confirmed when a processor, a bank or your own counsel asks.
Staff work with this record in the same admin that handles orders, refunds and fulfilment. Five staff roles, 2FA and an audit log are part of the same admin.
How we set it up with you.
On the build call we go through your access policy: which mode to start with, the minimum age, the attestation text from counsel, the disclaimer text and the countries and states to block. We configure those settings during the build and walk your team through changing them in the recorded launch walkthrough.
Store access, age and attestation are configured the same way for research peptide stores and for the other restricted categories we build for. Your policy decides the values; the platform applies them across the store and records attestation and age on each order.
Blocked countries and US states.
Block the countries and US states you choose. Rules vary by place and change over time, so decide the list with your counsel. The platform applies the list; it does not decide what is lawful where.
Disclaimers and feeds.
Disclaimers appear at add-to-cart, in the cart and in the footer, with text you configure. The Google Merchant feed excludes ad-restricted product names. The copy checker reviews storefront copy, emails and AI edits in off, warn or block mode.
How the copy checker works →What FDA letters cited →Draft disclaimer text for free →PepXLabs demo store · sample data
Before you choose a build.
Is the age gate ID verification?
No. It records a self-declared age. If counsel requires document or database ID verification, we scope that integration on the call.
Can I change the minimum age?
Yes. The minimum age is configurable from 18 to 25, and it is stored with the attestation on every order.
Which states should I block?
That is a decision for you and your counsel. We block the countries and US states you choose; we do not publish a list.
Can I write my own attestation text?
Yes. The attestation text is configurable. Our free disclaimer generator drafts a starting version for counsel to review.
More of the platform.
See it with your store in mind.
We can review your catalog, documentation, payment requirements and team workflows on the call. No promises on revenue, rankings or approvals.
Schedule a call to see a demoRelated guides
How to Start a Research Peptide Store in 2026: The Technical Launch Checklist
How to start a peptide business with a research-use-only store: platform selection, payments, lot-level COAs, compliance, SEO and a 25-point launch checklist.
Read the guidePeptide Payment Processing: Building a Store Processors Will Review Favourably
What payment reviewers look for on a research peptide website, plus an audit checklist and processor-agnostic checkout design. Approval is never guaranteed.
Read the guide