Skip to main content
storekit+ required - Custom domains are available on storekit+ and higher subscription plans. This feature is currently in early access.
Connect your own domain to your storekit ordering page for a seamless branded experience. Alongside order.storekit.com/your-store, customers can reach your stores on a domain you own. Custom domains are set up per brand, not per store: the domain is added to a brand and then serves every store in that brand.

​
Why Use a Custom Domain?

​
Stronger Brand Identity

A custom domain reinforces your brand at every touchpoint. Customers see your domain in:
  • The browser address bar
  • Receipts and confirmation emails
  • Social media links
  • Marketing materials

​
Better Analytics & Tracking

With a custom domain, your ordering page analytics are kept separate from storekit’s domain. This means:
  • Cleaner data in Google Analytics and other tools
  • Easier attribution for marketing campaigns
  • More accurate conversion tracking
  • First-party cookies for reliable visitor identification

​
Improved SEO

Search engines treat your ordering page as part of your main website when using a subdomain. Benefits include:
  • Domain authority flows to your ordering pages
  • Unified search presence for your brand
  • Better local SEO signals
We recommend using a subdomain rather than your top-level domain: Why a subdomain?
  • Your main website remains unaffected
  • Easier to set up and maintain
  • No risk of breaking existing website functionality
  • Can run alongside your existing website
  • Simpler SSL certificate management
Popular subdomain choices:
  • order.yourbrand.com
  • orders.yourbrand.com
  • menu.yourbrand.com
  • shop.yourbrand.com

​
How to Connect Your Domain

There is no Custom Domain page in the dashboard’s settings navigation. Domains live inside the brand they serve, so you open the brand first.
1

Open your brand

Click your profile in the bottom-left of the sidebar, then Brands in the settings navigation, then the brand you want the domain to serve. You land on that brand’s Brand Settings page.A brand has to exist before a domain can be added to it. If the Brands page is empty, click Add brand and create the brand first.
2

Add the domain

Under Custom Domains, click Add Custom Domain, type the subdomain you want to use (e.g., order.yourbrand.com) and click Connect.
3

Update your DNS

A domain setup wizard opens with the DNS records for your domain. At supported registrars it can sign you in and add the records for you; otherwise it shows the records so you can add them yourself or forward them to your IT team or domain administrator.
4

Verify and activate

Once DNS changes propagate (usually within a few minutes to 24 hours), storekit verifies and activates your custom domain with a free SSL certificate. The domain is listed under Custom Domains with its status beside it — it reads Not configured until the DNS records are in place, then Propagating or Verifying, and finally Active. Use refresh to re-check a propagating domain, or configure to reopen the DNS wizard for a domain that is still Not configured.
Brands only appears in the settings navigation on accounts that have custom domains enabled. If you do not see it, contact our team to have the feature switched on for your account.
Need help with DNS settings? Contact your domain registrar’s support or reach out to our team.

​
Using Cloudflare for DNS?

If your domain’s DNS is managed through Cloudflare, ensure the following settings for your ordering subdomain:
  • Set the CNAME record to DNS only mode (grey cloud icon) — do not enable proxying (orange cloud)
  • Do not configure any SSL/TLS or certificate settings for this subdomain
  • Exclude this subdomain from any redirect rules, transform rules, WAF rules, or bot protection
Enabling Cloudflare’s proxy (orange cloud) on your ordering subdomain will cause connection issues. storekit handles SSL and security for your custom domain automatically.

​
How Store URLs Work On Your Domain

A custom domain belongs to a brand and serves every store in that brand. Each store keeps its own store slug, and that slug is the first part of the path:
So a brand with three locations is reachable like this:
Opening the domain on its own shows the brand’s store-selection page, where customers pick a location. A few consequences worth knowing before you print anything:
  • A domain cannot be pointed at one specific store. There is no per-store domain and no setting to deep-link a domain straight to a single store’s menu — the store slug is always in the path. To send customers to one location, link to https://yourdomain.com/{store-slug}/menu.
  • You cannot change the path. The slug in the URL is the store slug, not the store name, and it cannot be replaced with a word of your choice.
  • Renaming a store does not change its slug, so the store URL stays the same after a rename. Slug changes are not self-serve — contact support if you need one.
  • One domain per brand serves all of that brand’s stores. If you need separate domains for separate groups of stores, they have to be separate brands.

​
Troubleshooting: payments/checkout not working after switching domain

If card payments, Apple Pay, or Google Pay stop working for customers immediately after you connect a custom domain, work through the checks below before removing the domain.
Always test a real payment on your new domain — including card, Apple Pay, and Google Pay — before switching customer-facing links, QR codes, or marketing materials over to it.
  • Confirm the CNAME is DNS only (grey cloud), not proxied. If your DNS is managed through Cloudflare, a proxied (orange cloud) record is the most common cause of checkout and payment failures. Follow the Using Cloudflare for DNS? guidance above to set the record to DNS only and exclude the subdomain from redirect, transform, WAF, and bot-protection rules.
  • Allow SSL and domain verification to finish before taking live orders. After you add the DNS record, storekit needs to verify the domain and provision an SSL certificate. This usually completes within minutes but can take up to 24 hours. Checkout may behave unpredictably until verification and SSL are fully complete, so wait for the domain to show as active before pointing customers to it.
  • Apple Pay and Google Pay may need the new domain registered with the payment provider. These wallet methods can require the new domain to be registered/verified with the payment provider, and that verification may lag a domain switch by a short period. If cards work but Apple Pay or Google Pay do not, this is the likely cause — contact our team so we can confirm the domain is registered for wallet payments.
Need to keep taking orders right away? Your original order.storekit.com/your-store URL keeps working throughout. Use it for customer-facing links while the custom domain is being fixed, then switch back once you’ve confirmed payments work on the new domain.

​
Frequently Asked Questions

Once you’ve added the DNS record, verification typically completes within minutes. In some cases, DNS propagation can take up to 24 hours.
Yes — and it stays live alongside your custom domain. Both URLs serve your store, so existing links and printed QR codes keep working after you connect a domain.Your order.storekit.com/your-store URL does not automatically redirect to the custom domain. If you want the storekit URL to redirect to your domain, contact support and ask us to set it up — it is not a setting you can switch on in the dashboard.
Yes, storekit automatically provisions and renews SSL certificates for your custom domain at no extra cost.
While technically possible, we strongly recommend using a subdomain. Using your root domain requires additional configuration and may conflict with your existing website.

Related topics

Customise store design and branding in storekitstorekit documentation: online ordering guides and APIsWebMCP ToolsFind and share your storekit store URLQuick Start Guide