What you are connecting
A custom domain in Confita v1 is a seller-owned subdomain. That means you keep your main website wherever it already lives, and point one subdomain to your Confita shop.
Good examples are shop.example.com, orders.example.com, menu.example.com, cakes.example.com, or tienda.example.com. Deeper names such as cakes.orders.example.com can also work if your DNS provider supports them.
Root domains such as example.com are intentionally not part of this version. They need different DNS behavior and are easier to break if the domain already hosts your main website.
| You type in Confita | DNS record type | DNS name | DNS target |
|---|---|---|---|
| shop.example.com | CNAME | shop | confita.pages.dev |
| orders.example.com | CNAME | orders | confita.pages.dev |
| cakes.orders.example.com | CNAME | cakes.orders | confita.pages.dev |
Manual CNAME setup
Choose manual setup if you want to copy the DNS values yourself, or if your domain is managed somewhere other than Cloudflare.
Open your DNS provider, find DNS records for the domain, and add a new CNAME record using the values Confita shows. The DNS name is the part before your domain. For orders.example.com, the name is orders. For cakes.orders.example.com, the name is cakes.orders.
The target is the Confita Pages target shown in the app. In production this is usually confita.pages.dev. After saving the record, return to Confita and refresh the status.
- Do not create an A record for this flow.
- Do not change the DNS for your root domain unless you know exactly why.
- If another record already exists for the same subdomain, remove or change that conflicting record first.
Automatic Cloudflare setup
Choose automatic Cloudflare setup if your domain uses Cloudflare DNS. Confita sends you to Cloudflare, you approve limited DNS access, and Confita creates the CNAME record for the subdomain you entered.
Confita does not ask you to paste a broad API key. The setup stores the Cloudflare zone and DNS record metadata needed to show status, not your general Cloudflare login.
If Cloudflare finds an existing conflicting DNS record, Confita will not overwrite it automatically. You will see a conflict message and can fix the record manually.
Why verification can take time
DNS changes are not always visible everywhere immediately. Some providers publish a new CNAME in minutes, while others can take longer depending on caching and old records.
Confita also has to attach your subdomain to the Confita Pages project. A CNAME alone is not enough; both the DNS record and the Pages custom-domain association need to be ready before your shop can load from the custom subdomain.
Troubleshooting
If verification is still pending, check that the record type is CNAME, the name matches the subdomain label shown in Confita, and the target has no extra spaces or path.
If you see a conflict, your DNS provider already has a record for that subdomain. Edit or remove the existing record, then add the Confita CNAME again.
If your main website is on example.com, leave it alone. Use a subdomain like shop.example.com or orders.example.com for Confita.
Sources
Details were checked against public sources on June 11, 2026. Confirm current provider instructions before making account or DNS changes.
Frequently asked questions
Can I choose something other than shop?
Yes. Shop is only an example. Use any subdomain you control, such as orders, cakes, menu, tienda, or a deeper name like cakes.orders.
Do I need to create the subdomain first?
In DNS, creating the CNAME record is what creates and routes the subdomain. You usually do not need a separate subdomain setup step.
Can Confita set up my domain automatically?
For Cloudflare DNS, Confita can guide you through an approval flow and create the CNAME automatically. For other DNS providers, use the manual CNAME values shown in the app.
Will my old Confita link still work?
Yes. Your confita.app/s/... link stays live as a fallback even after a custom subdomain becomes active.