​

The Rx building blocks

Tagada Rx is decoupled by design. The clinical flow is a small set of backend bricks — products, quizzes, orders, intakes, patients, cases, portal, refills — and every storefront is just a facade that calls them in some order. The Tagada-hosted templates use the exact same bricks as a fully headless integration on your own infrastructure: nothing in the clinical layer is template-only.

---

​

The matrix: every brick, every surface

Three auth models, one per column:

• Storefront calls need no key — the case routes prove ownership with the (orderId, checkoutToken) pair your checkout already holds.
• Server calls use a Tagada API key (tagada.rx.* in the Node SDK).
• Portal calls ride the customer’s CMS session (email OTP login).

---

​

The same flow, on any facade

Whatever the facade, a sale always executes the bricks in this order: Two hard rules survive every facade:

1. The marketing quiz and the medical intake are two different objects. The quiz sells before payment and contains no medical questions; the network-authored intake runs after the card hold. If the clinician declines, the hold is voided — money never left the card.
2. PHI is pass-through. patient and intakeAnswers go from the browser through Tagada to the clinical network in one request. Never store them in your own database or queue them “for later”.

---

​

Funnel orchestration (Tagada-hosted facades)

On Tagada infrastructure, each step of the journey is a box in the Tagada funnel system — a funnel step with its own RuntimeStepConfig (resources, checkoutOffers, orderBumps, upsellOffers, pixels, paymentSetupConfig), A/B-testable per step. The plugin manifest declares the remappable pages (/, /checkout, /offer, /thank-you) and the funnel engine drives transitions (useFunnel().next). Headless facades keep the same logical steps but orchestrate them themselves — the bricks don’t care who drives navigation. See Storefront templates for how the hosted templates arrange the boxes, and With the Headless SDK for the self-orchestrated version.

---

​

Where to go next