Launching your Fontdue site is the move from a private preview – where you upload fonts, set up licenses, and shape your storefront in isolation – to a public store anyone on the internet can buy from. This page assumes First steps is behind you – fonts uploaded, a license with pricing, Stripe connected – and, if you’re embedding Fontdue in your own site, that Add to your site has the integration working. What’s left is the sequence below; the surfaces it touches have their own pages linked inline.
The launch sequence
The work below is roughly the order to take it in, and some of the steps are skippable depending on your integration path.
If you’re using the demo template, leave the Headless setting (under Settings → Integration) turned off – Fontdue serves your site at your subdomain, and at your custom domain once it’s connected.
If you’ve built your own site, turn on Headless. Visitors to your Fontdue subdomain get a Not found page, and your own site becomes the only public surface. Fontdue still serves /graphql, /quotes/*, /shared-cart/*, /customer-dashboard, and the other paths components rely on – those stay reachable regardless of the Headless setting.
With the integration shape settled, fill in the rest of your setup at your own pace:
- Set your admin timezone – every date renders in it, invoice and receipt dates included, so get it right before orders start coming in.
- Set up test fonts, order variables, and tax.
- Brand your storefront – logo, fonts, and theme colors.
- Tune the cart and checkout copy and what checkout collects.
- Author your content – product pages, standalone pages, articles.
Run end-to-end test purchases in test mode to make sure checkout, receipts, and download archives all behave the way you expect.
If your site embeds Fontdue, make sure the domain you’re launching on is in the cross-origin allowlist – it’s easy to finish development with only localhost and a staging URL listed. Skip this step if you’re using the demo template; your Fontdue subdomain is always allowed.
Connect a custom domain so the Fontdue-hosted pages are served from a domain you own instead of your-foundry.fontdue.com – which subdomain you point at Fontdue depends on your integration path. And authenticate your email domain so receipts come from [email protected] instead of [email protected]. Both setups involve DNS work in your DNS provider’s dashboard; the custom domain is activated by the Fontdue team once your DNS is in place. Connect the custom domain before you launch – Safari blocks Fontdue’s cart cookies as third-party until your store is served from your own domain. See Domains.
If your site embeds Fontdue, make sure your Site URL (see Branding) points at your site’s homepage – that URL is what receipt emails and shared-cart redirects use, and it isn’t set automatically for embedded sites.
The steps above link into the platform guide throughout – it covers the whole admin in depth, from fonts and licensing to orders, reports, and storefront content. It’s worth reading well before launch day, whether you’re deep in configuration or still working out whether Fontdue fits your foundry.