Plans & entitlements
This page is about platform billing — what a store pays Orchard to run on the platform — not the store’s own commerce. For what the store’s customers pay the store, see Data model and Subscription lifecycle.
Pricing isn’t public yet. The tier structure and what each tier unlocks below is live and accurate. Concrete list pricing and a self-serve upgrade flow are not — plans are assigned by your Orchard operator today. This page will grow a pricing section once that’s ready to publish.
The tiers
Orchard has four plan tiers. “Premium” is the display name for the tier the
platform tracks internally as scale.
| Tier | What it unlocks beyond the tier below |
|---|---|
| Starter | Content pages, wishlists, product reviews |
| Growth | + subscriptions, analytics, a custom domain, email marketing, gift cards, referrals |
| Premium | + wholesale pricing, practitioner accounts, bundles, loyalty points |
| Custom | Everything, negotiated per tenant |
A tenant’s plan gates whether a feature is available at all — a Starter store can’t turn on subscriptions or a custom domain regardless of configuration.
Delivery speed also scales with plan
Separately from which features are available, four operational levers scale with plan tier and are live in production today:
| Lever | Starter | Growth | Premium | Custom |
|---|---|---|---|---|
| Real-time storefront inventory | No | No | Yes | Yes |
| Real-time admin updates | No | Yes | Yes | Yes |
| Analytics refresh | Once a day | Hourly | Every 15 min | Every 15 min |
| Transactional email delivery target | 15 min | 5 min | 1 min | 1 min |
These are why the changelog describes Premium as unlocking “faster email delivery, real-time storefront inventory, and more frequent analytics refreshes” — this table is the concrete version of that claim.
How a plan is assigned today
Plan assignment is operator-managed, not self-serve. If you’re the store owner and want to change tiers, talk to your Orchard operator rather than looking for an in-admin upgrade button — plan pages in the admin currently point you to your operator rather than a checkout flow.
What this means for you as an integrator
The public /api/v1 surface doesn’t vary by plan tier in its shape — an
endpoint for a feature gated behind Growth or above simply isn’t usable until
the tenant’s plan includes it (for example, subscription checkout on a Starter
tenant). If you’re building against a specific tenant and a feature seems
unavailable, confirm their plan tier before assuming an API bug.