What Happens to Your NCR Retail Online Domain and SSL Certificates

The discontinuation of NCR Retail Online affects more than the storefront software behind an ecommerce website. Your domain name, DNS records, SSL certificate, email services, payment connections, and customer-facing URLs all need to be reviewed as part of the move to a replacement platform.

A domain is separate from the shopping cart that operates on it. In many cases, the web address can remain under the retailer’s control after the NCR platform is shut down. The important issue is identifying the registrar, confirming account access, and changing the DNS configuration before the old hosting environment disappears.

SSL certificates require a separate check. A certificate issued for the former store may continue to show as valid until its expiration date, but it may no longer be renewed, installed, or correctly connected to a replacement website. A secure migration therefore requires new certificate management on the destination platform.

The domain does not automatically disappear

Your NCR Retail Online domain is usually registered through a domain registrar rather than owned by the ecommerce application itself. The registrar account may have been created by your business, an NCR Counterpoint partner, or another web services provider. That distinction determines who can update nameservers, renew the registration, and authorize a transfer.

A discontinued store platform does not necessarily cancel the domain. However, a domain can still become inaccessible if its registration expires, its payment method fails, or administrative contact details point to a former employee or partner. Verify the renewal date, registrant information, recovery email address, and two-factor authentication before making other changes.

If the domain was bundled with hosting, ask exactly what is being discontinued. Hosting, DNS management, email forwarding, domain registration, and certificate provisioning may have been separate services even if they appeared on one invoice. Keeping the domain active while replacing the store is often the safest path.

DNS controls the route to your replacement store

DNS records tell browsers where to find your website. The main records commonly involved in a migration are A or AAAA records for an IP address, CNAME records for a hosted storefront, MX records for email, and TXT records for verification, SPF, DKIM, and other security functions.

Before changing DNS, export or document the existing zone. A replacement platform may require a new CNAME or a specific IP address, while email records should generally remain unchanged unless the mail provider is also moving. Accidentally deleting MX or TXT records can interrupt business email or cause messages to fail authentication.

Lowering DNS time to live, or TTL, before the planned switch can reduce the period during which visitors reach different versions of the store. DNS caching still varies by resolver, so the old site and new site should be tested in parallel where possible. A staging domain or temporary platform URL can help confirm catalog, checkout, shipping, tax, and customer account functions before the public changeover.

SSL certificates need a fresh ownership check

An SSL certificate encrypts traffic and proves that a website is authorized to use a domain. It does not transfer automatically merely because the domain name remains the same. The new Magento, WooCommerce, or hosted commerce environment must obtain and install a certificate for the live hostname.

If NCR or a partner managed the original certificate, find out whether it was a dedicated certificate, a shared certificate, or an automated certificate issued through the hosting provider. The certificate may cover the root domain, the www version, subdomains, or several alternate names. A new configuration must include every hostname customers are expected to use.

The following checks show what typically changes during a platform transition:

Certificate warnings can appear even when the certificate itself is valid. Common causes include an incomplete certificate chain, a hostname mismatch, a missing www certificate, or mixed content from images and scripts still loaded over HTTP. Test the storefront on multiple browsers and use an external TLS checker after DNS has propagated.

Prepare the old URLs before switching

A domain migration is also a URL migration. Product pages, category pages, promotional landing pages, blog posts, and image paths may have different structures on WooCommerce or Magento. If the old addresses are abandoned without redirects, search rankings can fall and customers following saved links may encounter 404 errors.

Create a URL inventory from analytics, search console data, site exports, and existing navigation. Match high-value NCR Retail Online URLs to their closest equivalent on the replacement site. A permanent 301 redirect is generally appropriate when content has moved, while a useful custom 404 page can guide visitors when no direct replacement exists.

Seasonal pages deserve special attention because they may receive traffic long after a campaign ends. For example, an existing Christmas gift page should be assessed for its search value, backlinks, and customer intent before it is removed or redirected. Preserve relevant content where practical instead of sending every retired URL to the homepage.

Keep the old domain active during the transition. It may be needed for redirects, certificate validation, branded email, customer support links, and printed materials already in circulation. Closing the old hosting account too early can remove the very files and configuration details needed to complete a clean migration.

Shipping and checkout connections must be retested

Changing the domain and SSL certificate is only part of the operational work. The new store must reconnect payment gateways, tax services, shipping calculators, inventory synchronization, order notifications, analytics, advertising feeds, and customer account functions. Credentials may be stored in the old administration area and cannot be assumed to migrate with product data.

Shipping rules are particularly easy to overlook. Different platforms may interpret zones, postal codes, product weights, free-shipping thresholds, and carrier rates differently. Before launch, review the process described in reconfigure shipping rules and compare every rule with the retailer’s current delivery policy.

Run test orders using several destinations and product combinations. Check taxes, shipping charges, discount codes, inventory deductions, confirmation emails, refunds, and fulfillment notifications. Confirm that the checkout page remains on HTTPS from the cart through payment and that no browser console errors reveal insecure third-party assets.

A controlled handover protects customers

Assign clear responsibility for the domain, DNS, certificate, hosting, and application. A retailer should have direct administrative access wherever possible, with recovery details held by the business rather than an individual contractor. Keep a record of renewal dates, certificate issuer, DNS provider, platform credentials, and emergency contacts in a protected password manager.

Use a short maintenance window for the final DNS change and publish a customer-service message if ordering will be temporarily limited. Monitor uptime, certificate status, checkout completion, order creation, and email delivery immediately after launch. Analytics and server logs can reveal broken links or abandoned checkout steps that ordinary browsing does not expose.

Security should remain a priority after the switch. Remove old API keys, revoke unused administrator accounts, update plugins and extensions, and confirm that the replacement platform has current patches. For WooCommerce stores, the guidance on choosing a new store theme is useful when evaluating compatibility, performance, mobile behavior, and secure asset loading.

A practical migration checklist

• Confirm domain registrar ownership, renewal status, and recovery contacts.
• Export DNS records and preserve MX, SPF, DKIM, and verification entries.
• Issue a new SSL certificate covering every public hostname.
• Map important legacy URLs and configure 301 redirects before launch.
• Test checkout, payments, shipping, inventory, email, and mobile browsing.

Begin by identifying who controls the domain and DNS account, then schedule the certificate and storefront change with your NCR Counterpoint partner or chosen migration provider. A documented handover, verified HTTPS configuration, and monitored redirect plan will keep the retailer’s web address working while the commerce system changes underneath it.