Shop-E-Business Custom Domain Inclusion Guide Line

Published At 2026/May/18

Standard Operating Procedure (SOP)

Tenant Custom Domain Onboarding Guide for Shop-E-Business

Architecture Overview:
This battle-tested checklist provisions edge SSL and seamless www forwarding for store owners. It consumes only 1 Custom Hostname quota per tenant on your primary SaaS tier by handling www redirects directly at the edge of the customer zone.

Phase 1: Database Registration

Step 1: Assign the Apex Domain in Your Database

Add the domain mapping into your Shop-E-Business database or tenant management dashboard.

Crucial Rule:
Only register the clean apex domain string (example: shasroibazar.com).

Do NOT include:
  • www.
  • https:// or trailing slashes (/)
Your ASP.NET Core middleware matches the incoming request against this canonical apex host.

Phase 2: Tenant DNS Configuration

Open the DNS manager for the customer's domain (e.g., shasroibazar.com in Cloudflare, Namecheap, or GoDaddy).

Step 2: Route the Root Apex Domain

Type Name Target / Content Proxy Status
CNAME @ (or shasroibazar.com) www.shopebusiness.com Proxied (Orange Cloud)

Step 3: Route the WWW Subdomain

Type Name Target / Content Proxy Status
CNAME www www.shopebusiness.com Proxied (Orange Cloud)
Why a CNAME instead of 192.0.2.1?
Using a CNAME pointing to your SaaS fallback ensures that if edge redirect rules are ever paused or delayed, traffic is still safely proxied toward the SaaS origin rather than failing immediately against a dummy blackhole IP.

Phase 3: Cloudflare for SaaS Hostname Registration

Step 4: Register Apex Custom Hostname

  1. Log into Cloudflare and select your platform domain: shopebusiness.com.
  2. Navigate to: SSL/TLS → Custom Hostnames.
  3. Click Add Custom Hostname.
  4. Custom Hostname: shasroibazar.com (apex only).
  5. Certificate Validation Method: Choose HTTP Validation.
  6. Origin Server: Default origin server.
  7. Click Add Custom Hostname.
Why HTTP Validation over TXT?
TXT validation often experiences timeout drops ("Timed Out Validation (TXT)") and requires tedious manual token copying. Because the customer's CNAME already points to your platform, Cloudflare completes HTTP-01 verification and provisions edge certificates automatically within 1–2 minutes without manual DNS interventions.

Phase 4: Setup WWW Edge Redirect (Zone-Specific)

Zone Warning:
Do NOT create this rule inside shopebusiness.com! You must switch the Cloudflare dashboard to the customer’s own domain zone (e.g., shasroibazar.com).

Step 5: Create the Forwarding Rule

  1. In the Cloudflare dashboard, select the customer’s domain zone: shasroibazar.com.
  2. Go to Rules → Page Rules (or Redirect Rules).
  3. Click Create Page Rule.
  4. URL Match:
    www.shasroibazar.com/*
  5. Select:
    • Setting: Forwarding URL
    • Status Code: 301 - Permanent Redirect
  6. Destination URL:
    https://shasroibazar.com/$1
  7. Click Save and Deploy.

Result: Using this edge rule prevents burning a second Custom Hostname slot, conserving your 100 free SaaS hostname quota so 1 client = 1 quota.

Phase 5: Enforcement & Final Testing

Step 6: Enforce "Always Use HTTPS"

  1. Still inside the customer's domain dashboard (shasroibazar.com), open SSL/TLS → Edge Certificates.
  2. Toggle Always Use HTTPS to ON.

Step 7: Verification Checklist

  1. In your SaaS dashboard (shopebusiness.com), verify that shasroibazar.com displays:
    • Certificate Status: Active
    • Hostname Status: Active
  2. Open a fresh Private/Incognito browser window and test:
    • https://shasroibazar.com → Loads the tenant store with a valid SSL padlock.
    • http://shasroibazar.com → Automatically upgrades to secure HTTPS.
    • https://www.shasroibazar.com → 301-redirects instantly to the apex domain without certificate mismatch errors.

Production Architecture Validated 🚀

Zero manual TXT tokens, automated renewal via HTTP-01, and 1-hostname-per-tenant quota efficiency.