Anyone can create an account without talking to us first, and the store exists at the end of sign-up: a real storefront on a subdomain, with a default theme already seeded and ready to edit. Building and publishing are both open — theme editor, catalog, checkout settings, the whole dashboard, on the real product rather than a demo of it. Once you confirm your email address, the store’s default theme goes live on its PlatformDTC address. Confirming your email also grants a new account a one-time $100,000 in AI credits. There is no monthly fee and no plan to choose: you pay a fee on each sale, taken from the payment before it reaches your payouts. Current rates are in Payment fees and rates and at platformdtc.com/pricing. A feature that is still in beta says so with a Beta tag beside its name in the dashboard menu. Everything else is generally available. Published stores are live stores taking real payments, and the orders placed on them are real orders.

​
What is covered

One account covers the whole run of a store, not one slice of it.

​
Up to 10 stores per account

An account can hold up to 10 stores. Add one from the store switcher (Add Store) or Settings → General → All stores. The 10 counts every store that has not been removed, whether it is published or not; a removed store does not count. Partner development stores do not count either. At 10, Add store is replaced by Contact us, and the API answers 409 with STORE_CAP_REACHED: “You can have up to 10 stores. Contact us to remove one you don’t use, or to get more.” Store removal is done by our team, not from the dashboard, so write to us through the contact page either way. An account that already had more than 10 stores keeps all of them and can keep working in them. It can’t add another until it is under 10.

​
Checkout runs on your own domain

Attach a custom domain and checkout runs on it — the shopper who clicked Buy on yourbrand.com pays on yourbrand.com and never leaves your brand. Before a custom domain is attached, checkout runs on the platform domain at platformdtc.com/checkout/<session>. See Checkout URLs. Express wallets available at checkout: Apple Pay, Google Pay, Link, Amazon Pay and Klarna. A wallet only renders on a hostname registered with its provider, which is why moving your checkout to a new host is gated on that registration rather than on a checklist.

​
What may change under you

We fix behaviour we think is wrong rather than preserving it for compatibility. In practice that means:
  • Screens move and defaults change. Navigation, layout and the default value of a setting are all fair game.
  • New surfaces arrive before they are complete. A feature can ship narrow and widen later.
  • Some numbers get corrected retroactively. When a metric was computed wrongly we recompute it and say so, which can move a figure you had already read.
What does not change without notice:
  • The Agent Gateway contract. Scopes, idempotency, job semantics, approvals and webhook payloads are versioned. Breaking changes to them are announced in the changelog before they land.
  • Your data and your domains. Nothing is deleted, reset or migrated as part of a product change.
Every change a merchant would notice is written up in the changelog, with a Changed section and a Kept working section — the second one exists so you can tell at a glance whether anything you depend on moved.

​
How to send feedback

The things that annoy you should reach a person. In the dashboard, open your account menu and pick Send feedback, or write to us: A bug report travels furthest when it carries the store, the time, and what you expected instead. For an API problem, include the request id from the response and the endpoint — that is usually enough to find the exact call in the audit record without asking you anything further.

​
Where to check status

status.platformdtc.com publishes the live state of the surfaces we probe — storefronts, checkout, dashboard, Core API, notifications and these docs — with p50 and p95 response times per component, plus the incident record. Background jobs and analytics are not probed yet; the page says so rather than showing a green dot they have not earned. It publishes p50 and p95 response times per component, not just up or down, because a service can be up and still be unusable. If something feels slow, you can cite the same figure we would. Status has a JSON API, RSS/Atom feeds, and email, Slack, Teams and webhook subscriptions — see Platform Status.
Not to be confused with Endpoint Status, which records which individual API endpoints are verified, gated or known-broken. That page is the one to check before building on a specific endpoint.

​
What we do not claim

PlatformDTC storefronts do not currently serve UCP or agentic-checkout discovery endpoints. Requesting them returns 404. We publish research measuring exactly that surface on other platforms, so it would be dishonest to leave the gap unstated here: if your integration depends on a storefront answering a UCP or agentic-checkout request, it will not work today. Agent access to a store goes through the Agent Gateway instead — a scoped, audited, idempotent API with a human approval gate on spend.