# For brands

Drape's pitch to brands is *"Small brands deserve bigger stages."* — a
try-on-enabled storefront and a discovery channel for curated, culture-forward
independent labels, without running a parallel checkout elsewhere.

> *"Join Drape to offer virtual try-on, power in-store discovery, and manage your
> catalog on your own subdomain. Shoppers discover, try on, and checkout on Drape —
> your storefront is where the sale happens."*

## What brands get

| Feature | What it is |
|---|---|
| **Virtual try-on** | Shoppers try the brand's garments on their own body |
| **Branded storefront** | A tenant subdomain — `yourbrand.drape.to` |
| **In-store QR** | QR codes that bridge physical retail into the app |
| **Team & roles** | RBAC — invite teammates with scoped permissions |
| **Brand analytics** | Try-on / preview / order performance dashboard |
| **Website widget** | A "Shop on Drape" button embeddable on the brand's own site (not an external cart). See [Website widget & deep links](./deep-links.md). |

## Plans & pricing

Subscription plus a per-order platform fee — *"lower on Basic and Premium."*
Public ladder (marketing + brand portal); fees apply only when an order is paid.

| Plan | Price | Platform fee | Highlights |
|---|---|---|---|
| **Freemium** | **$0** | **10%** | Default after approval · up to **25** listings · analytics · Stripe Connect · branded storefront |
| **Basic** | **$19.99/mo** | **8%** | Unlimited listings · widget customization · priority support · lower fee |
| **Premium** | **$29.99/mo** | **6%** | Everything in Basic · lowest public fee · POS / inventory sync · API, webhooks & co-branded mobile · ERP/CRM by request |

Internal plan ids stay `free` / `brand` / `brand_plus` for Stripe and the database.

:::note[Grandfathered — admin only]
Admins can assign **Grandfathered** ($0 / **5%**, Premium-like entitlements) with a
**required end date**. It never appears on marketing or self-serve Billing. When
the date passes, the store falls back to Freemium unless they subscribed to Basic
or Premium.
:::

:::note[Source of truth]
Live display prices come from admin-managed `brand_plan_catalog`
(`GET /api/marketing/brand-plans`) plus `PLAN_CONFIG` entitlements in
`backend-postgres`. Client fallbacks live in `drape-brand-v1/lib/billingPlans.ts`
and `drape-marketing/lib/brandMarketing.ts`.
:::

## How onboarding works

```mermaid
graph LR
    A["01 Apply<br/>brand.drape.to/apply"] --> B["02 Review<br/>curate culture-forward labels"]
    B --> C["03 Approved<br/>portal + {slug}.drape.to provisioned"]
    C --> D["04 Go live<br/>Stripe Connect + catalog"]
```

From the marketing FAQ: brands can keep selling on Shopify, but **checkout and
catalog happen on Drape** — traffic is driven in via deep links, QR, and the
widget ([deep links](./deep-links.md)). Premium brands can also wire
[order webhooks](./webhooks.md) into their own systems. After approval, brands start on **Freemium** (analytics + Connect included).
Selling starts once Stripe Connect is complete. Basic and Premium are monthly with
no long-term contract; platform fee applies per paid order.

## Two portals, one offering

Brands operate through two front-ends over the same backend:

- **Desktop brand portal** — `Drape-brand` at `brand.drape.to` / `{slug}.drape.to`.
  The full dashboard: catalog, orders, analytics, content, live streams,
  engagement, retail/in-store, locations, team RBAC, billing, integrations, and
  the widget. Architecture detail on the
  [Web surfaces](../architecture/web-surfaces.md) page.
- **Mobile brand portal** — inside the Expo app (`Drape-/frontend`), covered on the
  [Seller portal](./seller-portal.md) page.

They are parallel surfaces, not duplicates — pick by device. The desktop portal is
the richer of the two and carries the newer Postgres-backed capabilities (RBAC,
integrations, live, in-store payments).

## Payouts

Every plan settles through **Stripe Connect Express**: when a store is
Connect-enabled, checkout routes funds to the brand via an application fee plus a
transfer, with the marketplace fee taken per order. See
[Backend → Payments](../architecture/backend.md#payments).