Domain Setup

Custom domains are requested in CP and reviewed by Ops.

S3-6 added the thin Domain Workflow. S3-7A documents it as a skeleton guide for scoped acceptance. DNS and SSL remain manual/semi-manual in the current Stage 3 path.

Default subdomain

After provisioning, each store can expose a default domain. Merchants can use it as the CNAME target for custom domain setup when available.

Custom request

Open CP Store Detail, enter a hostname, and request review. Valid requests start as pending custom domains.

Ops review

Platform Ops approves or rejects pending custom domains. Rejected domains can include a platform note.

CNAME guidance

  • Use the store default domain as the CNAME target when CP shows one.
  • Submit hostnames only. Do not include protocol, path, wildcard, or port.
  • Pending means waiting for platform review.
  • Active means the platform accepted the domain record.
  • Automatic DNS and automatic SSL are not included in current Stage 3.
Open CP Store Detail after login Back to Help