US Precision Peptides — The operation
The researcher sees the vial. The operation makes it repeatable.
Every order on this site has two halves. The part the researcher reads, signs, pays for, and unboxes — and the part that records the lot, files the receipt, and proves the same vial can ship to the next researcher tomorrow.
Two halves of one transaction
Every transaction here has two halves — the part the researcher sees, and the part that makes the operation repeatable. The first half builds the order. The second half makes sure the next lot, the next researcher, the next ledger entry land where they belong. Both halves are documented below.
For the researcher
What you see, sign, and unbox.
Thirteen pieces of the order experience, in the order you meet them. Open any row.
Site Access Wall and 21+ acknowledgement Researcher
The catalog is gated by design. Before any vial, price, or COA reveal, you acknowledge the 21+ posture and the research-use-only framing. The wall covers everything except the COA library, the blog, and the legal pages — surfaces that have a public-reading reason to exist. The acknowledgement is logged against your session so you do not see the wall again until it expires.
Passwordless magic-link sign-in Researcher
One email link signs you in. No password to remember, no password to leak. The same identity follows you across devices because the link issues a session, not a credential. The login endpoint and the registration endpoint behave identically on the wire, so an attacker cannot use the response to learn whether your email is on file. Sessions revoke individually or in bulk from the account page.
Five-rail checkout Researcher
Pick the rail that fits the order. Venmo (auto-confirmed via an inbox watcher), Solana Pay (self-hosted, no merchant intermediary), BTCPay Server Bitcoin (self-hosted node), Coinbase Commerce (hosted checkout), and a card rail wired and held in standby. All five run on the same order state machine, so a rail switch never produces an orphan order, a double-charge, or an inconsistent receipt.
Tiered pricing visibility Researcher
Pricing runs on a five-tier ladder. When you sign in, the catalog shows your account price as a labeled caption under the public price, so there is no guessing what you actually pay. Tier movement is recorded against your account history. The same engine drives the SALE badge logic on a product page when an override beats the tier price.
Volume-bundle pricing Researcher
Three vials get five percent off, four get eight, five-or-more get ten. The math runs at the cart line, not after the fact, and the engine returns the best of two — your tier price or the bundle price, whichever is lower. The bundle break appears as a line on the cart so you can see exactly what the count is doing to the total before you check out.
Store credit balance Researcher
Your account page shows the current store credit balance and applies it automatically at checkout, with the option to opt out per order. Grants, debits, and refunds-to-credit post to a single ledger so the balance reconciles back to a list of dated entries — not a number that floats. The same ledger is what the operator sees on the admin side.
Lot-matched COA on every vial Researcher
Every shipped vial carries the signed Certificate of Analysis for the exact lot inside it. The order record stores the lot ID. The COA library stores the same lot ID. There is no batch substitution between what the chemical supplier released and what the order page references. When the lot number on the vial label matches the lot number on the COA URL, you have ground truth, not marketing.
COA permalink library Researcher
Every released lot has a permanent, shareable URL at /coa/<slug>. The page frames the original signed PDF and lists the per-lot metadata: compound, lot number, release date, supplier, and the order it ships against. The library index at /coa is editorial and indexable, so the same document a researcher hands a supplier is the document an outside auditor can open without an account.
Back-in-stock email signup with 72-hour hold Researcher
When a SKU runs out, enter your email and you are first in line. Subscribers get a 72-hour claim window before the lot opens publicly, plus a 72-hour cart hold once the link is used. Day-seven and day-fourteen follow-ups land if you do not check out. The signup is on the empty-state card itself, so the action you wanted to take is the action you are offered.
Anti-enumeration order tracking Researcher
The order lookup endpoint cannot be brute-forced. Whether or not an order exists with the email you enter, the response shape and timing are the same. The link that gives you order detail arrives by email and expires. An attacker scraping the endpoint sees nothing actionable; you, with the email already on file, get one click to the order page.
Privacy choices and GPC-honored opt-out Researcher
One click opts you out of analytics and any non-essential tracking. The Global Privacy Control signal is honored at the browser level, so a browser that broadcasts GPC starts opted out. Every state change writes to an append-only audit log against the anon_id or, if signed in, the account. The opt-out page itself is public and reachable without acknowledging the site wall.
Researcher account dashboard Researcher
One page, one identity. Past orders, saved shipping addresses, your tier and account price, your store credit ledger, and your magic-link sign-in history all sit on the account dashboard. No password to manage. Session list shows where you are signed in; one click revokes the rest. Order detail links back into the COA library when the lot has been released.
Cold-chain handling pathway Researcher
For temperature-sensitive material, a cold-chain pathway is wired end to end on the back end: gel-pack and insulated-mailer SKUs, a cold-chain flag on the order, a different ship-day cadence. The self-serve checkout option is held off the front end until the supply side is ready to honor it on every applicable SKU. The infrastructure ships before the promise.
For the operation
What makes the same order ship next month.
Fourteen pieces of the back-of-house. The part that does not show on the order confirmation but is the reason the next confirmation looks the same.
FEFO inventory with supplier-lot lock Operation
Inventory allocates first-expiry-first-out. One internal lot maps to one chemical-supplier lot — the lock is at the schema level, not a policy a clerk has to remember. Receiving runs through a lot_deliveries table so a single supplier lot can land across multiple shipments without collapsing into phantom stock. The lot lifecycle has five statuses: received, released, allocated, depleted, recalled. Every transition is auditable.
Refunds and RMA workflow Operation
Refunds resolve at the line level. Full or partial, against the rail the order paid on, with restock back to the originating lot in one transaction. Return Material Authorization is its own workflow — an RMA can sit open while the material comes back, then close with or without an auto-issued refund. Five line categories cover product, shipping, tax, adjustment, and rounding. Nothing falls between two tables.
Immutable order-assent ledger Operation
At order submission, the server stamps the exact policy version, the IP, the user agent, and a SHA-256 hash of every checkbox label shown. The row lands in order_assent and is append-only — there is no UPDATE path. A pre-commit hook on the repo blocks any policy text edit that ships without a policy-versions.json bump. The version a researcher acknowledged stays attached to the order forever.
Append-only audit logs Operation
Consent transitions, anon-id mappings, admin actions, refund issuances, lot status changes — all of it writes to append-only tables. No silent rewrites. If an event happened, there is a row that records it happened, and a row that records the next thing that happened to that record. Reading history backwards is a query, not a forensic exercise.
Persistent S1 alert bar Operation
Every admin page renders through a shared shell with a live alert bar at the top. Flagged orders, email-send failures, webhook outbox failures, out-of-stock SKUs, refunds aging past 48 hours, adjustments aging past 24 hours — six feeds, every page. The operator does not have to go looking for what needs attention. It is already at the top of whatever screen they opened.
Researcher CRM module Operation
Per-researcher context lives in one record. Order history, shipping addresses, payment rail preferences, store credit ledger, magic-link audit, notes, tags, communications, and a nightly rollup for lifetime value and churn signals. Transactional email engagement events ingest from the mail provider and post against the same record. The view is the operator's read of who is actually on the other side of the orders.
Cloudflare Access admin gate Operation
The admin shell sits behind Cloudflare Access. Authentication is a signed JWT from CF Access — there is no operator password layer in the application code to forget, rotate badly, or leak. Localhost bypasses for dev. Production refuses requests that do not carry a valid Access JWT, full stop. The zero-trust posture lives one layer above the app, where it belongs.
Daily Postgres backup with watchdog Operation
Every night at 03:00, pg_dump writes the full database to independent on-prem storage. At 04:00, a watchdog checks the dump landed, the size is sane, and alerts if either is wrong. Retention runs 30 days. Disaster recovery is a copy-paste runbook against a file that exists, not a hope that a managed snapshot is where it should be when the day comes.
n8n cron bridge Operation
Sub-daily scheduled jobs route through a self-hosted n8n on independent infrastructure, because the storefront's hosting tier caps cron resolution at daily. The same lane runs the Venmo inbox watcher that auto-confirms payments. A bridge, not a workaround — it has been the lane long enough that the orchestration sits in n8n on purpose, not because the platform forced it.
Auto-confirmed Venmo via inbox watcher Operation
The Venmo confirmation lane is automated. An n8n workflow watches the Venmo Gmail inbox, parses the payment confirmation email, and posts an HMAC-signed event back to the storefront. The order transitions from pending_venmo to paid without an operator opening an inbox or marking anything by hand. The signature stops anyone else from posting a payment that did not happen.
Product-view tracking dashboard Operation
Logged-in product views post to an internal dashboard. Card impressions are gated by IntersectionObserver. Time-on-card is measured by a heartbeat tick, not by a clock that runs while a tab is in the background. Same-session cart attribution joins the view event to the line it became. The signal is gated by the analytics consent setting on the researcher's account — opt-out really opts out.
Five-tier pricing engine with bulk CSV import Operation
The catalog is checked in as JSON for source-of-truth scalars. Price overrides land in a database table — catalog_price_overrides — and merge on read, so an operator can bulk-update prices via a CSV import without a redeploy. The order line stores its own items_json snapshot at the moment of submission, so price changes the next day do not rewrite the receipt from yesterday.
Site Access Wall with landing analytics Operation
The wall is not just a gate. The /account/access landing page carries its own funnel analytics — eight named events tracked through to acknowledgement, plus a sticky-cookie headline A/B for the entry copy. The admin shell has a tile that links straight to the GA4 and Clarity views for the funnel. The operator sees access-conversion as a measured surface, not a guess.
Resend plus Proton SMTP outbound mail Operation
Transactional email runs on Resend with engagement webhooks landing back on the researcher record. Supplier and operator-to-researcher correspondence runs on Proton SMTP through a separate sending identity. Both senders are DMARC, DKIM, and SPF aligned. Two lanes on purpose — when the receipt and the personal reply do not have to share an inbox, neither one has to win.
By the numbers
The shape of the surface.
What this is
A research-peptide platform, operator-first.
- A chemical supplier shipping to researchers
- Released material, analytically released, lot-tracked
- Research-use only — 21+ acknowledgement at every order
- A documented review process for every researcher agreement
- An operation built to ship the same order next month
What this is not
Not a pharmacy. Not a supplement. Not advice.
- No therapeutic, diagnostic, or treatment claim
- No dosing or human-use guidance
- No regulatory approval claim — released, not approved
- No legal certification — a documented process, not legal advice
- Not for human or veterinary consumption
This page describes platform functionality and documented review processes. It is not legal or tax advice and does not assert that the platform is breach-proof or risk-free.
Two doors. Pick yours.
Browse the catalog if you are sourcing material. Email the operation if you are evaluating it as an investor, partner, or stakeholder.