Tagada Rx
Who this is for — Brands selling prescription-based treatments online (weight management, hair loss, skin care, hormones…). Tagada Rx turns a regular Tagada store into an asynchronous telemedicine pharmacy: the patient answers a medical intake, pays, a licensed clinician reviews the case, a partner pharmacy ships the treatment, and the subscription rebills on the day the pharmacy actually ships.Tagada Rx is an opt-in add-on — activated per store. On TagadaRx the sold price is 6.9% of GMV (processing included), with $0 setup. Clinician and pharmacy costs pass through at cost. See Activation.
What is Tagada Rx?
Everything you already know from Tagada — products, checkout, payments, subscriptions, CRM — plus a clinical layer:Clinical network
A pre-integrated network of US-licensed clinicians (all 50 states). Tagada submits patient intakes as cases; clinicians review asynchronously, approve or decline, and e-prescribe.
Pharmacy fulfillment
Approved prescriptions are routed to a partner pharmacy. Shipment and delivery events flow back into your Tagada order timeline automatically.
Ship-day rebilling
Recurring treatments rebill the day the pharmacy ships — not on an arbitrary calendar date. No “charged but never shipped” revenue.
Patient portal
A ready-made patient area: case timeline, secure messaging with the care team, and photo-ID upload for identity verification.
PHI never touches Tagada storage. Patient identity and intake answers transit through the API straight to the clinical network. Tagada persists only non-PHI routing data: case ids, statuses, timestamps, and event metadata.
How a sale works, end to end
- Checkout first, clinical second. The patient completes a marketing quiz (no PHI) and authorizes a card hold. The hold is not clinical approval — the storefront copy must make that clear.
- Case submission. On the thank-you page the storefront collects the network questionnaire and calls
rx.submitCase()with the patient identity and intake answers. Tagada forwards everything to the clinical network and records a case (rxcase_xxx). - Clinician review. A licensed provider in the patient’s state reviews asynchronously. Approval, decline, prescription, shipment, and delivery all arrive as webhooks which Tagada normalizes into case events.
- Capture or void — never a refund. Approve captures the hold. Decline voids it. Money never leaves the card if the clinician does not prescribe.
- Recurring refills. On every shipment, Tagada schedules the next charge at
ship day + cycle(30 days by default). An hourly job scans due cases and fires the rebill.
The case lifecycle
Every clinical case (rxcase_xxx) moves through a strict state machine:
Each transition is recorded as an append-only case event (
case.approved, shipment.shipped, message.created, …) that you can read from the API, the CRM, or the patient portal timeline.
The three integration surfaces
You never talk to the clinical network directly — Tagada owns that integration, its credentials, and its webhooks.
Choose your track
How it works (deep dive)
Architecture, PHI handling, webhooks, rebilling — the mental model in one page.
Operating modes
Merchant of Record (affiliate) vs Direct Merchant — who is the seller, who pays whom.
Activate in the CRM
Request activation, pay the setup fee, map your products.
End-to-end tutorial
From empty store to first prescription — the complete flow, step by step.
Building blocks
The decoupled architecture: every storefront is a facade over the same Rx bricks.
Storefront templates
Three funnel archetypes, one skeleton — with live demos.