Domains

Point your own domain at Fontdue, and send receipts from your own email address

There are two domains Fontdue uses to reach your customers on your behalf – the one customers visit, and the one their receipts arrive from. By default both belong to Fontdue (your-site.fontdue.com and [email protected]). Replacing them with your own domains is a separate DNS setup each, and both are done from Settings in the admin: Custom domain and Email domain.

Custom domain

Your Fontdue store lives at your-site.fontdue.com until you connect a custom domain. A custom domain serves the same Fontdue-hosted pages under a domain you own – store.example.com instead of example.fontdue.com.

Connect the custom domain before your site launches – it’s part of going live, not a later upgrade. When your site reaches Fontdue across a fontdue.com address, Safari treats the cart cookie as third-party and blocks it, so customers on Safari and iOS can find that Add to cart does nothing. Serving Fontdue from a subdomain of your own domain makes the cookie first-party, which fixes this.

Choosing a domain

The domain to connect depends on how your site is built:

  • Fontdue template sites – if your site is built on the Fontdue template, the custom domain becomes your site’s main address. Enter your main domain, example.com: Fontdue serves the store on www.example.com, and the bare example.com redirects to it.11Entering www.example.com sets up the same thing.
  • Sites that embed Fontdue – if your site lives elsewhere and embeds Fontdue components, your main domain stays where it is, and a dedicated subdomain carries the Fontdue-hosted pages. store is the convention: store.example.com.

A domain can be connected to one Fontdue store at a time.

Connecting the domain

Connecting a custom domain takes a few minutes in the admin and one or two records with your DNS provider – the company you bought the domain from, or wherever its DNS is managed.

1 Add the domain

In Settings → Custom domain, enter the domain and click Add domain. Fontdue shows the DNS records to add.

2 Add the DNS records

A subdomain needs one CNAME record pointing at dns.fontdue.com. A main domain needs that CNAME for www, plus an A record for the bare domain so it can redirect to www. Each name and value has a copy button.22Some DNS providers want only the part of the name before your domain – store rather than store.example.com.

If your domain’s DNS is on Cloudflare, set the records to DNS only (the grey cloud). Remove any AAAA records for the same names – they send some visitors elsewhere.

3 Wait for it to connect

DNS changes usually take a few minutes and can take up to 48 hours. Each record shows Pending until Fontdue sees it, then Verified. Click Check now to look again – there’s no need to keep the page open, because Fontdue also checks on its own (see below). Once every record is Verified, Fontdue sets up the domain with its hosting provider and the HTTPS certificate is issued automatically, usually within a few minutes.33Fontdue waits for the records on purpose: a certificate requested before the DNS points at Fontdue can fail to issue.

To move to a different domain, click Remove domain and add the new one. Your store is back on your-site.fontdue.com in between.

After the domain is live

Once the custom domain is active, update the places that still reference your fontdue.com URL:

  • Sites that embed Fontdue – update the url in your integration code to the new domain, for example fontdue.initialize({ url: "https://store.example.com" }) in a script-tag setup or the url prop on FontdueProvider in a React setup. Also check that your Site URL is filled in with your site’s homepage – customers are redirected there after checkout, and receipt emails link back to it. It isn’t set automatically for embedded sites.
  • Fontdue template sites – nothing to update: as long as the Site URL setting is blank, checkout redirects and receipt links follow your site’s address automatically, custom domain included.44If you’ve filled in Site URL explicitly, update it to the new domain.

Switching over from fontdue.com

Fontdue checks the custom domain every 15 minutes and switches to it once it finds your store answering there. Until then – while DNS is still propagating, for example – your store keeps working on your-site.fontdue.com, and nothing Fontdue sends points anywhere else.

Once the switch is made, everything Fontdue links to uses the custom domain: signing in to the admin, checkout and receipt links, and your sitemap. On Fontdue template sites, every page on your-site.fontdue.com permanently redirects (301) to the same path on the custom domain, so search engines index one copy of your site rather than two, and each page carries a canonical tag naming its address on the custom domain.55Because every page already has a canonical tag, don’t add one in HTML head – that code is the same on every page, so a fixed canonical URL would tell search engines that every page is a copy of one. While you’re signed in to the admin, pages on your-site.fontdue.com aren’t redirected, so previewing your site keeps working.

If the custom domain stops reaching Fontdue for three hours, Fontdue switches back to your-site.fontdue.com until it answers again.

If you remove the custom domain later, your store reverts to your-site.fontdue.com. Customers who bookmarked the custom URL will no longer reach you until they’re redirected from somewhere else.

Email domain

By default, Fontdue sends receipt emails from [email protected]. The Email domain tab lets you authenticate your own domain so receipts come from your foundry’s address – [email protected], for example.

Under the hood, Fontdue uses SendGrid for transactional email. Domain authentication involves adding three DNS records so SendGrid can sign emails on your behalf.

1 Enter the email address you want to send from

For example, [email protected]. Fontdue extracts the domain and starts the authentication process with SendGrid.

2 Add the DNS records

Fontdue shows three records you need to add to your DNS provider:

  • One CNAME for email tracking.
  • Two DKIM records for email signing.

The admin has a one-click copy button for each host and value – paste them into your DNS provider as they’re shown.

3 Verify

Click Verify DNS records. Fontdue re-checks them against SendGrid. DNS changes can take up to 48 hours to propagate, so if verification fails immediately, give it a few minutes (or a few hours) and try again.

4 You're set

Receipt emails now send from the address you entered. You can change the email later as long as it stays on the same verified domain. Removing the domain reverts receipts to [email protected].

Changing or removing the email domain

Once the domain is verified, you can change the Receipt email to any address on the same verified domain without redoing the DNS flow. Changing to an address on a different domain requires re-authenticating that new domain.

To remove the domain entirely, click Remove domain. This clears the SendGrid authentication; receipts go back to sending from [email protected].

1 Entering www.example.com sets up the same thing. ↩
2 Some DNS providers want only the part of the name before your domain – store rather than store.example.com. ↩
3 Fontdue waits for the records on purpose: a certificate requested before the DNS points at Fontdue can fail to issue. ↩
4 If you’ve filled in Site URL explicitly, update it to the new domain. ↩
5 Because every page already has a canonical tag, don’t add one in HTML head – that code is the same on every page, so a fixed canonical URL would tell search engines that every page is a copy of one. ↩