Activating Tagada Rx

Tagada Rx is activated per store. On TagadaRx there is no setup fee — you apply, we review, and we unlock the store (invite code or your account manager). Until the store is active, case submission is rejected. Sold price on TagadaRx: 6.9% of GMV, processing included. Clinician and pharmacy costs pass through at cost — never marked up. There is no per-prescription fee.

not_requested ──► pending_payment ──► active
   (apply)            (under review /        (Rx menu appears,
                       invite unlock)          cases can flow)

From the CRM (recommended)

Open the Rx page of your store

In the CRM, navigate to your store → Tagada Rx (/stores/{storeId}/rx). Before activation the page shows the activation card.

Pick how you run the brand

Your brand on TagadaRx is open now — 6.9% of GMV,

0 setup, processing and LegitScript included, min

200k GMV / month. Standalone (same stack, you are MoR — 4.9% + $4,980 setup) is coming soon.

Apply

Click Apply to launch on TagadaRx. The page switches to Application under review.

Unlock

We review every application. If you already have an invite code, enter it on that page. Your account manager can also unlock the store.

The Rx menu appears

Once active, a Tagada Rx section appears in the store sidebar with six tabs: Overview, Cases, Products, Storefront, Commission, and Settings. On Products you make exactly two decisions per treatment — sell it or not, and your retail price; the medical questionnaire, clinician review, and pharmacy routing are pre-configured by Tagada (the questionnaire is viewable read-only from each treatment card).

On TagadaRx, unlocking the store also provisions the Rx processing account behind the scenes — no extra onboarding on your side.

Wire the clinical configuration

After activation, the store needs its clinical-network configuration before cases can flow. This is done once, usually together with your account manager during onboarding:

Network credentials — issued by the clinical network for your brand (client id/secret, environment id, webhook secret).
Brand clinical config — flips from draft to active once credentials are verified.

From the CRM this lives under Tagada Rx → Settings. From the API:

await tagada.rx.configureBrandClinical({
  storeId: 'store_xxx',
  credentials: {
    clientId: '…',
    clientSecret: '…',
    webhookSecret: '…',
    externalEnvironmentId: '…',
  },
});

Map products to treatments

A product only triggers the Rx flow once it’s mapped to a clinical-network offering (the network’s SKU for a treatment):

CRM

Tagada Rx → Products → pick a product → set its Treatment ID (the network offering id) and the clinical requirements.

Or via API / Node SDK

await tagada.rx.setProductOffering({
  storeId: 'store_xxx',
  productId: 'product_xxx',
  externalOfferingId: '<network offering UUID>',
  requiresLabs: false,
  requiresIdVerification: true,
  isDeaControlled: false,
});

Verify from the storefront side

curl "https://api.tagada.io/api/public/v1/rx/required-for-product?productId=product_xxx"
# → { "required": true, "requiresIdVerification": true, ... }

isDeaControlled: true products are rejected at case submission in affiliate mode. Direct mode only.

Launch your storefront

Once active, Tagada Rx → Storefront offers two paths:

Use a template (fastest)

Pick a storefront template (multi-vertical, plan-first, or quiz-first), add your logo, brand name, colors, and subdomain — publishing clones the plugin instance and installs a Funnel v2 on your-brand.tgdcare.com. Each step (landing, quiz, checkout, offer, thank-you, portal) shows up in the CRM funnel builder. Your product catalog and payment flow are wired automatically.

Build your own (Headless SDK)

Build the storefront on your own stack with the Headless SDK, following the compliance directives. The build is still deployed on your Tagada subdomain — LegitScript certification is tied to Tagada-hosted domains. Deploying on your own root domain is coming soon (direct mode).

Switching templates later is safe: republishing swaps the facade on the same subdomain, same funnel, same cases and patient history.

Checking the state programmatically

const status = await tagada.rx.integrationStatus('store_xxx');
// { state: 'not_requested' | 'pending_payment' | 'active', operatingMode, ... }

The same endpoint powers the CRM activation card, so what you see in the dashboard is exactly what the API returns.

Full activation via API only

Everything above the CRM does is available on the merchant API — useful for partners provisioning many brands:

Step	Endpoint	Node SDK
Request activation	`POST /api/v1/rx/integration/activate`	`tagada.rx.requestActivation()`
Confirm setup fee (admin)	`POST /api/v1/rx/integration/confirm-setup-fee`	`tagada.rx.confirmSetupFeePaid()`
Clinical config	`POST /api/v1/rx/brand-clinical-config`	`tagada.rx.configureBrandClinical()`
Product mapping	`POST /api/v1/rx/product-offerings`	`tagada.rx.setProductOffering()`
Status	`GET /api/v1/rx/integration/status`	`tagada.rx.integrationStatus()`
Available networks	`GET /api/v1/rx/networks`	`tagada.rx.listNetworks()`

Get Started

Activate

Build

Patients

Partners

Reference

Activate in the CRM

Activating Tagada Rx

From the CRM (recommended)

Wire the clinical configuration

Map products to treatments

Launch your storefront

Use a template (fastest)

Build your own (Headless SDK)

Checking the state programmatically

Full activation via API only

​Activating Tagada Rx

​From the CRM (recommended)

​Wire the clinical configuration

​Map products to treatments

​Launch your storefront

Use a template (fastest)

Build your own (Headless SDK)

​Checking the state programmatically

​Full activation via API only

Activating Tagada Rx

From the CRM (recommended)

Wire the clinical configuration

Map products to treatments

Launch your storefront

Checking the state programmatically

Full activation via API only