How can we help?

A custom domain needs both the intended website connection and a valid HTTPS setup. A domain in Builder’s directory or a Yes setting alone does not confirm that customers can reach the secure shop.

Gather the details

1. Record your current working ShopTill-e address and the exact custom domain you want to use.
2. Identify where the domain is registered and who manages its DNS settings.
3. Note which addresses should work, including the main domain, www and any other intended subdomain.
4. Identify existing email and other services using the domain.
5. Give support these details and agree the connection, secure access and default-address plan.

Arrange the connection

Use the exact records and provider settings confirmed for your domain. Keep a copy of the existing configuration before an intended change. DNS providers differ, and website records must be considered alongside existing email records. Ask support to confirm the current service scope and any cost before proceeding.

Check the main address and www separately

Your main domain, such as example.com, and www.example.com are separate addresses to include in the connection plan. Do not assume that copying the same record type to both will work with every DNS provider.

1. Give support both addresses you want customers to use and identify the DNS provider.
2. Have the exact record names, types and destinations confirmed for that provider and shop. Check which address will be the default and what should happen to the alternative.
3. If the provider rejects a record for @ or the main domain, retain the exact message and ask for the appropriate setup. Do not delete existing email or other records to force the example to fit.
4. After the agreed change, check each address separately using HTTPS and compare the final destination with the plan.

For example, a working www address does not by itself show that the main domain is connected or has a valid certificate. Report which address works and which fails, along with the exact error.

Check secure access

1. Check each agreed address opens the intended shop using HTTPS without a certificate warning.
2. Check product and content pages, images, basket and checkout.
3. Check the expected destination when following old or alternative addresses.
4. Confirm that email and any other affected services continue to work.
5. Complete the agreed default-domain change only when the new address is ready.

If an image or page still looks old

Record the exact page and image address, when it changed, the expected result and what another browser shows. Ask support to check the affected delivery and caching settings. Avoid repeatedly replacing a file or changing the domain simply to force one image to refresh.

Example: a launch with an existing domain

Prepare the shop at its working address, then coordinate the custom-domain change with the person who manages the domain. Keep the old working address and the agreed checks available throughout the change.

Builder domain controls · Default domain · Storefront file changes.

Ask for help with the connection

Contact support@shoptill-e.com with the exact domain, current working shop address and the addresses you want customers to use. Include any loading error and recent changes. Keep passwords out of the message.

Check a slow webshop

1. Record the exact public page and when the delay happens. Distinguish slow page loading, a slow photograph, an old image and an error or unavailable page.
2. Compare another representative page. Note whether the problem affects one product or the wider shop.
3. Where possible, compare another device, browser or connection and record the result. Keep the original conditions with your notes.
4. Note recent theme, image or content changes. Keep the affected page/image addresses rather than repeatedly replacing files.
5. If reviewing a public page with PageSpeed Insights, keep its tested address, date and mobile/desktop choice. Use public storefront pages, not private account, order or administration links.
6. Send support the affected pages, symptom, comparisons and recent changes before changing domains or several unrelated settings.

For example, a slow product photograph and an outdated photograph need different investigations. Record which one you see and compare the actual image address.

Read speed reports in context

Google’s PageSpeed guidance distinguishes a controlled test from real-user measurements collected over the previous 28 days. Missing real-user data can mean insufficient samples; it is not proof that the page is broken. Check whether results describe the page or the wider site, and do not expect a recent edit to replace historical measurements immediately.

Google’s page-experience guidance says Core Web Vitals contribute to ranking, but good scores do not guarantee a top position. Keep useful content and the customer’s complete shopping journey in view rather than treating one score as the goal.

Check delivery and caching options for your domain

Ask support which delivery, caching or CDN arrangements apply to the intended domain and launch stage, and confirm any setup work and cost. Include recent image changes and exact addresses. Do not assume an older guide’s free service or manual activation process applies to the current account.