> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/integration-paths.md).

# Integration Paths

Choose an integration path based on how much of the patient experience you want to own. Whichever path you pick, every one of them runs through the same clinical workflow underneath:

1. **Checkout** — The patient purchases or requests a treatment.
2. **Intake** — The patient completes a Questionnaire for the selected [Offerings](/partner/key-concepts/offerings.md).
3. **Clinical review** — MDI creates or matches the patient and opens an Encounter.
4. **Decision and fulfillment** — A clinician decides, then approved prescriptions move to fulfillment.

What actually differs from path to path is how much of the storefront and patient-facing experience you build yourself versus how much MDI hosts for you.

You're also not locked into a single choice, and most partners' integrations evolve over time. It's common to start with something like Shopify to get to market quickly, then layer in API workflows later once you need more custom control.

{% hint style="info" %}
Configure webhooks for every integration path. They keep your systems synchronized with clinical and fulfillment events. See [Webhook Setup & Signature Verification](/partner/troubleshooting/technical-concepts/webhook-setup-and-signature-verification.md).
{% endhint %}

### Compare integration paths

| Path                                                               | Best for                                   | What you build                             | Typical effort |
| ------------------------------------------------------------------ | ------------------------------------------ | ------------------------------------------ | -------------- |
| [API](/partner/integration-paths/api.md)                           | Fully custom journeys                      | Storefront, intake, and patient experience | 2–4 weeks      |
| [White-Label Apps](/partner/integration-paths/white-label-apps.md) | Faster launch with branded MDI experiences | Voucher generation and embedded access     | 1–2 weeks      |
| [Shopify](/partner/integration-paths/shopify.md)                   | Shopify storefronts                        | Product configuration and plugin setup     | 3–4 days       |
| [WooCommerce](/partner/integration-paths/woocommerce.md)           | WooCommerce storefronts                    | Product configuration and plugin setup     | 3–4 days       |

### Compare feature support

|                           | Full API     | White-label apps            | Shopify      | WooCommerce     |
| ------------------------- | ------------ | --------------------------- | ------------ | --------------- |
| Customize checkout        | Full control | Partial control             | Limited      | Partial control |
| Customize patient UI      | Full control | Branded embedded experience | Limited      | Flexible        |
| Match existing patients   | Full control | Partial control             | Limited      | Very limited    |
| MDI help designing intake | Limited      | Full support                | Full support | Full support    |

{% hint style="info" %}
MDI won't limit you based on an integration path. You can mix and match different paths as needed, *e.g. build your own intake form experience using APIs and integrate with our white-label Patient Portal experience.*
{% endhint %}

### Selecting the best starting point

In practice, most partners land somewhere in between: they combine a pre-built experience with selected API capabilities rather than committing to one path exclusively. Treat the descriptions below as a guide to the strongest starting point for your situation, not a hard limit on what you can eventually build.

* **Full API** — Choose this path for complete control. Your team builds the checkout, intake, messaging, and system integrations.
* **White-label apps** — Choose this path for a branded experience with faster implementation. MDI provides the intake and messaging experiences, while your application creates Vouchers and directs patients to them.
* **Shopify** — Choose this path if you already have a Shopify storefront. The plugin connects products to intake forms and adds patient messaging to the order experience.
* **WooCommerce** — Choose this path if you already have a WooCommerce storefront. The plugin connects products to intake forms and supports the same core workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/partner/integration-paths.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.