Custom Domain
Every store is reachable by default on its subdomain, and a custom domain (for example www.mybrand.com) can be connected through a request-and-approval flow.
Your Default Subdomain
When a store is created it is automatically assigned a subdomain:
yourshop.platform-domain.com
For example, a store with identifier mystore might live at mystore.storacart.com. The chosen theme runs on top of this domain — switching a theme does not change the store URL. The subdomain is permanent unless replaced through the Custom Domain feature.
Connecting a Custom Domain (4 Steps)
Tenant Admin → Custom Domain
Step 1 — Open the Custom Domain page. You will see a DNS Configuration Guide with the exact records to add, the current domain and request status, and a Request Custom Domain button.
Step 2 — Point the domain's DNS to the platform at your registrar (GoDaddy, Namecheap, Cloudflare, or similar) before submitting. Use the exact values shown on your Custom Domain page, not generic examples.
Standard records (non-Cloudflare):
| Type | Host | Value | TTL |
|---|---|---|---|
| CNAME | www | platform-domain.com | Automatic |
| CNAME | @ | platform-domain.com | Automatic |
If you use Cloudflare, root CNAME flattening may not work in proxy mode — use an A record instead:
| Type | Host | Value | TTL |
|---|---|---|---|
| A | @ | Server IP shown on your Custom Domain page | Automatic |
| CNAME | www | platform-domain.com | Automatic |
Replace platform-domain.com and the server IP with the actual values from your Custom Domain page's DNS guide.
Step 3 — Submit the request. Click Request Custom Domain, enter the domain without http:// or https:// (root mybrand.com, www.mybrand.com, or shop.mybrand.com all work), watch the automatic availability check (green means available, red means already in use), and click Send Request. Status becomes Pending.
Step 4 — Wait for approval. The platform team reviews the request and verifies DNS. The store becomes accessible at the custom domain automatically once Connected.
Server-side steps for cPanel, AApanel, and CloudPanel are covered in the panel guides below.
Propagation
DNS changes take 5 minutes to 48 hours to propagate globally (usually under 30 minutes). Track progress at dnschecker.org. A Connected status with a not-yet-loading domain usually just means propagation is still in flight — wait, then clear the browser cache and retry.
Request Statuses
Tenant Admin → Custom Domain → Domain Request Status
| Status | Meaning | What to Do |
|---|---|---|
| Not Requested | No request submitted yet | Click Request Custom Domain to start |
| Pending | Submitted, awaiting review | Wait for the platform team; confirm DNS records are added |
| In Progress | Team is connecting the domain | DNS verification in progress |
| Connected | Custom domain is live | Store now runs on the custom domain |
| Rejected | Request denied | Contact the platform provider, fix DNS, and submit a new request |
Email Notifications and New Requests
An email is sent at every status change (pending → in progress → connected or rejected) — check the inbox and spam folder. To change domains later, or after a rejection, click New Request, enter the new domain, and resubmit. If a Connected domain already exists, the newly approved domain replaces it.
Panel Setup Guides
- How to add custom domain in cPanel
- How to add custom domain in AApanel
- How to add custom domain in CloudPanel
Related: User Dashboard Custom Domain pointer, and Domain Reseller Overview for purchasing domains on the platform itself.