Connect a custom domain to your Vareons store

Every Vareons store owns an address that works immediately on registration in the form {name}.vareonos.com, and the platform also runs an additional domain, vareons.store, alongside the primary one. This subdomain needs no setup from the merchant and is enough to start selling and share the link.

If the merchant owns a domain (for example mystore.com), connecting it is managed from /dashboard/settings?tab=domains. You add the domain and it appears as pending_dns, and the system shows the required DNS records (record type, name/host, and value) in a setup dialog you can copy from. After adding the records at your domain provider, use the Check DNS / Refresh action, which re-verifies the DNS records and the Cloudflare SSL certificate status.

The status path is explicit: from pending_dns to verification, then either active when DNS and certificate issuance succeed, or intermediate states such as invalid_dns and pending_ssl with diagnostic hints (for example apex record or ownership TXT notes) shown to the merchant. The DNS setup and Check DNS / Refresh actions stay available even for an active domain, because changing an ALIAS or apex record later can require a re-check. Note that this path does not go through platform admin approval: verification is purely technical via DNS and the certificate.

A new subdomain on the primary domain can also be added; in that case it becomes active directly and the store's domain field (User.domain) is updated. A custom domain, by contrast, is not copied into the subdomain field; it is resolved per request from the domains collection by checking that the domain is active and DNS-verified. This means a custom domain only serves traffic once status=active and dnsVerified=true.

Once connected, the domain can be set as the store's primary from the same tab, or removed (unless it is suspended; a suspended domain shows a contact-support note). In practice, a custom domain gives your store an easy-to-remember address, increases trust, and strengthens brand association in Facebook and TikTok ads and in search engines, while the dashboard and editing remain on the platform's primary domain.

One operational benefit: a single store can serve more than one address (a primary subdomain, a custom domain, and the vareons.store domain), because tenant resolution happens from the Host in the proxy layer before the page is reached, so a request lands on the same store and the same data regardless of the address the visitor typed.