> ## Documentation Index
> Fetch the complete documentation index at: https://docs.suprsend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Template Variants

> Serve different content to different audiences - by tenant, language, or any condition - from a single template.

Variants let you send different content to different recipients from the same template. Instead of creating separate templates for each tenant, language, or audience segment, you create variants with conditions - SuprSend picks the right one at send time.

Every template starts with a **default** variant. Add more only when you need them.

You can embed the template editor directly in your application using the [Embeddable Templates SDK](/docs/embeddable-template-react-sdk). This lets your customers edit notification templates within your product, or your internal team manage templates and run campaigns - all without switching to the SuprSend dashboard.

***

## When to use variants

<CardGroup cols={2}>
  <Card title="Multi-tenant" icon="buildings" iconType="solid">
    Each tenant's users see their own branding - logos, colours, copy. One template serves all [tenants](/docs/tenants).
  </Card>

  <Card title="Multi-lingual" icon="language" iconType="solid">
    One variant per language. SuprSend auto-selects based on the recipient's preferred language. See [Multi-lingual Templates](/docs/multi-lingual-template).
  </Card>

  <Card title="Payload-based" icon="code-branch" iconType="solid">
    Different content based on trigger data — for example, `plan == "pro"` gets a premium message.
  </Card>

  <Card title="A/B testing" icon="flask" iconType="solid">
    Different copy to different segments. Compare in [Analytics](/docs/analytics). Needs manual maintenance - use for specific hypotheses, not as a default.
  </Card>
</CardGroup>

***

## Create a variant

Click the **+** button next to "All Variants" in the left panel. You'll see two options:

<Frame caption="Add New Channel or New Variant">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-add-menu.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=abf7f558d9de27ddb5d8c8c505990736" width="414" height="654" data-path="images/docs/templates-variants-add-menu.png" />
</Frame>

### Add a new channel

Select **New Channel** to add a channel to the template (for example, add SMS to a template that only had Email). Pick the channels and click **Add Channels**.

<Frame caption="Select channels to add">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-new-channel.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=d38dd9b440e3187ff799a09367b1315c" width="1024" height="438" data-path="images/docs/templates-variants-new-channel.png" />
</Frame>

### Add a new variant

Select **New Variant** to create a variant with conditions for an existing channel.

<Frame caption="Create Variant modal">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-create-modal.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=af967a0e14b0bc17af3c31c8168651bb" width="1024" height="812" data-path="images/docs/templates-variants-create-modal.png" />
</Frame>

Fill in:

**Channels** - which channels this variant applies to. *(Required)*

**ID** - a unique identifier. Use descriptive names: `uber-en`, `acme-es`, `pro-users`. *(Required)*

**Locale** - the language for this variant. *(Required)*

**Tenant** - scope to a specific tenant. Leave blank for non-tenant variants.

**Conditions** - rules that determine when this variant is sent. Each condition has a **Data Type** (Recipient, Actor, Tenant, or Input Payload), **Property**, **Operator**, and **Value**. Add multiple conditions with **+ OR**.

| Common operators                                         |                      |
| -------------------------------------------------------- | -------------------- |
| `==`, `!=`                                               | Equals / not equals  |
| `>`, `>=`, `<`, `<=`                                     | Comparisons          |
| `contains`, `not contains`                               | Substring match      |
| `is empty`, `is not empty`                               | Null checks          |
| `datetime is`, `datetime is before`, `datetime is after` | Date comparisons     |
| `intersects (array)`, `not intersects (array)`           | Array overlap checks |

<Tip>
  **AI prompt - design variant conditions:** *"Design SuprSend template variants for \[describe scenario]. Data available: \[payload keys, tenant props, recipient props]. For each variant suggest: ID, conditions, ordering (first match wins), and which should be the default fallback."*
</Tip>

***

## Edit a variant

Click any variant in the left panel to open it. You're always editing the **draft** - the live version is untouched until you commit.

* **Edit content** - write directly in the channel editor. Content auto-saves.
* **Edit conditions** - click the **settings icon** on the variant to change its ID, locale, tenant, or conditions after creation.
* **Import content** - use the Import button to copy content from another variant or template instead of starting from scratch. See [Import content](/docs/templates#import-content).

***

## Commit

Click **Commit** to publish. The modal shows all changes - you can deselect specific variants you're not ready to publish.

<Frame caption="Commit modal - review changes before publishing">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-commit-modal.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=19b091118e61ecd4e9270e5bcccca088" width="1024" height="834" data-path="images/docs/templates-commit-modal.png" />
</Frame>

For **WhatsApp** and **SMS (DLT)** variants, committing puts the variant into **Approval Pending** - it goes live only after vendor approval. For multi-lingual templates, each language is approved separately. If a [fallback vendor](/docs/vendor-fallback) is configured, you'll need to confirm approval for each vendor.

***

## How selection works at send time

When a notification is triggered, SuprSend evaluates all non-default variants in the order they appear in the panel. The first one whose conditions all match is sent. If no variant matches, the **default** (always at the top) is sent as the fallback.

* All conditions on a variant must be true - partial matches are skipped.
* **Tenant** and **locale** are soft checks with fallback: tenant+locale → tenant+default locale → default tenant+locale → default.
* All other conditions (like `$recipient.plan == "pro"`) are hard checks - no fallback, the variant is just skipped.

<Frame caption="Variants panel - all variants grouped by channel">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-panel-full.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=514781b20cb604d533cc33ac1a1a820b" width="1024" height="525" data-path="images/docs/templates-variants-panel-full.png" />
</Frame>

### Ordering variants

Order determines priority. If two variants both match a recipient's data, the one **higher in the list** wins. You can drag and drop variants to change their position.

* The **default** variant always stays at the top - it's the fallback and cannot be moved. No other variant can be placed above it.
* All other variants can be freely reordered by dragging.
* Place more specific variants (for example, `uber-es`) above general ones (for example, `default-es`) to ensure they match first.

If a variant isn't being picked when you expect it to, check its position - a broader variant above it may be matching first.

### Testing variant selection

To verify the right variant is being picked for a specific condition, **test the full template group** - not a single variant. Testing a single variant sends that variant's content directly (bypassing conditions). Testing the template group runs the actual selection logic:

1. Click **Test** → select the **Template Group** tab.
2. Enter a **Recipient** whose profile matches the condition you want to test.
3. Select a **Tenant** if your variant has a tenant condition.
4. Click **Send Test** - SuprSend evaluates all variant conditions and sends the matching one.
5. Check [Logs](/docs/logging) to confirm which variant was selected.

This is the only way to verify that ordering and conditions work as expected end-to-end.

***

## Duplicate, delete, and disable

### Duplicate a variant

Click the three-dot menu (**...**) on any variant to duplicate it. The content is copied into a new variant - adjust the ID and conditions.

<Frame caption="Duplicate a variant">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-duplicate-menu.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=4be967b7e9640422d57af71e9ae9a256" width="504" height="406" data-path="images/docs/templates-variants-duplicate-menu.png" />
</Frame>

### Delete a variant

Click the three-dot menu on a variant and select **Delete**. This permanently removes the variant and its content. The **default** variant cannot be deleted.

### Disable a channel

Click the three-dot menu on a **channel name** (not a variant) to disable it. Notifications stop on that channel immediately, but the content is preserved. Re-enable anytime without losing work.

<Frame caption="Disable a channel - content is preserved">
  <img src="https://mintcdn.com/suprsend/sGhtraHJZNmyh1Op/images/docs/templates-variants-disable-channel.png?fit=max&auto=format&n=sGhtraHJZNmyh1Op&q=85&s=046a1ad910305e6d4e9d10968a1133f4" width="402" height="772" data-path="images/docs/templates-variants-disable-channel.png" />
</Frame>

This is useful when you want to temporarily pause a channel (for example, stop sending SMS during a vendor migration) without deleting the content and having to recreate it later.

***

## Common patterns

**One template, many tenants** - create a variant per tenant using a `$tenant.id` condition. Default is the fallback for tenants without a custom variant. Onboarding a new tenant = a template edit, no code change.

**Tenant + language** - combine conditions: `$tenant.id = acme` + `$recipient.language = fr`. Place these above language-only variants so they match first.

**A/B testing** — create a variant targeting a subset (for example, `$recipient.cohort = beta`). Compare metrics. To promote: widen the conditions or update the default. To end: delete the challenger.

After setting up any pattern, [test with a specific tenant and recipient](/docs/templates#test) to verify the right variant is picked.

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="What happens if no variant matches?">
    The **default** variant is sent. It cannot be deleted and always acts as the fallback.
  </Accordion>

  <Accordion title="Can I have different variants per channel?">
    Yes. Variants are per-channel - you can have 3 for Email, 1 for SMS, and just the default for Push. Each channel is evaluated independently.
  </Accordion>

  <Accordion title="How do I test which variant gets picked?">
    Click **Test** in the editor, enter a recipient, select a tenant, and send. The variant whose conditions match is used. Check [Logs](/docs/logging) to confirm.
  </Accordion>

  <Accordion title="What's the difference between soft and hard conditions?">
    **Soft** (tenant, locale): SuprSend falls back through a hierarchy if no exact match exists. **Hard** (everything else): no fallback - the variant is skipped if the condition doesn't match.
  </Accordion>

  <Accordion title="Can I reorder variants?">
    Yes. Drag them up or down in the panel. The default always stays at the top and cannot be moved.
  </Accordion>
</AccordionGroup>