Modules · Clients
Every client in one timeline.
A single timeline per client -- orders, prescriptions, messages, notes. Search anything in two keystrokes.
Included
$0
About
Clients is the spine of PeptideClients. Every order, prescription, message, note, and audit event hangs off a single client record -- searchable in two keystrokes, tagged in your language, and gated by per-store membership so the right operator sees the right book. It is bundled with every plan because nothing else in the platform works without it. The other modules read from it, write to it, and never replace it.
Features
Unified profiles
One record per client, joined to every order, prescription, message, and note across every store you own.
Two-keystroke search
Type a partial name, phone, or order number and the right record floats to the top. No filters required.
Tags and segments
Apply your own tags -- maintenance, paused, GLP-1, white-label -- and pull the matching cohort into a campaign or an export.
Full audit log
Every edit to a client record, every export, every viewed PHI field shows up in the per-org audit trail. HIPAA-grade hash chaining.
Store-scoped membership
Multi-store orgs route operators to the right book by membership, so a Florida tech never sees the Texas book by accident.
Soft-delete with restore
Archive a client and the timeline disappears from operator views; platform admins can restore a record from the audit drawer in one click.
Use cases
Fulfillment lead
Find a refill in two keystrokes
A client texts asking about a refill. Type the last four digits of their phone; the timeline opens with the last six orders, the active prescription, and the open conversation -- before the message thread loads in your inbox.
Multi-store owner
One client across three stores
Same client books in Texas and Florida. Their orders from each store render on one timeline, but RLS keeps the Florida tech from editing a Texas order. Reports roll up across both.
Compliance officer
Prove who saw what, when
Pull an audit report for a single client over the last 90 days: every view, edit, export, and message, with operator id, IP, and session id. Exports as signed JSON.
FAQ
Does clients cost extra?
No. It is bundled with every plan -- Beginner, Pro, and Expert. The other modules read from it; you cannot use them without it.
How many clients can I store?
Each plan has a published cap (5,000 on Beginner, 10,000 on Pro, 20,000 on Expert). Need more? Ask for an Enterprise plan or a per-org override; we say yes for serious operators.
Is client data encrypted at rest?
Yes. The underlying Postgres is AES-256 encrypted on Supabase managed storage. PHI fields flow through the audit redaction layer before they hit the log.
Can I import existing clients?
Yes. The operator app has a CSV import in Settings; we also expose a service-role REST endpoint for one-time bulk loads. Most operators are imported in under ten minutes.
What happens if I archive a client?
The timeline disappears from operator views and the client row is excluded from active-quota counts. Platform admins can restore in one click for up to twelve months.
How is access scoped in a multi-store org?
Per-store memberships. An operator with membership in store A sees only store A's clients, even if the org has ten stores. Owners and org admins see all.
Add clients the day you need it.