How to Handle Domain Orders, Renewals, and Transfers as a Reseller
A reseller should handle registration, renewal, and transfer as separate workflows. Confirm availability, price, customer payment, reseller balance, contact data, DNS plan, renewal timing, transfer lock, EPP code, and customer approval before submitting paid domain actions.
Who This Guide Is For This guide is for: · Hosting providers selling domains · NiceNIC resellers · Agencies managing client domains · Developers building domain automation · WHMCS users · SaaS platforms offering custom domains · Support teams handling customer orders This guide explains practical steps and support expectations. Exact behavior may vary by TLD, account status, registry rules, payment method, registrar workflow, hosting provider, DNS provider, or supported NiceNIC feature.
Before You Start Before you begin, prepare: · NiceNIC reseller account · Business model or customer type · TLD list · Pricing plan · API or WHMCS plan · Account balance workflow · Support owner · DNS backup process · Renewal schedule · Abuse and compliance process Important: Confirm the current status inside your NiceNIC account or through the official support channel before making high-impact changes such as payments, transfer requests, nameserver changes, contact updates, or abuse remediation.
Step-by-Step Instructions Step 1: Separate registration, renewal, and transfer workflows This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Confirm unlock status, EPP/AuthInfo code, contact email access, and expiration risk before submitting transfer. · Do not retry a failed transfer until the cause is corrected. Step 2: Build a standard order intake form This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Review the account information carefully before acting. · Keep a written record of the decision, action, and final result. Step 3: Check availability and price before charging This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Use the account panel, RDAP, order history, or support ticket information as the source of truth. · Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance. Step 4: Confirm customer payment and reseller balance This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Use the account panel, RDAP, order history, or support ticket information as the source of truth. · Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance. · Confirm amount, currency, invoice, payment method, and transaction evidence before escalation. · For resellers, keep enough balance for renewals as well as new orders. Step 5: Validate contact data This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Review the account information carefully before acting. · Keep a written record of the decision, action, and final result. Step 6: Confirm nameserver and DNS plan This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Use the account panel, RDAP, order history, or support ticket information as the source of truth. · Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance. · Back up existing DNS records before changing nameservers or DNS settings. · Test website and email separately after the change. Step 7: Submit registration carefully This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Review the account information carefully before acting. · Keep a written record of the decision, action, and final result. Step 8: Build a renewal calendar This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Review the account information carefully before acting. · Keep a written record of the decision, action, and final result. Step 9: Prepare transfer checklist This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Use the account panel, RDAP, order history, or support ticket information as the source of truth. · Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance. · Confirm unlock status, EPP/AuthInfo code, contact email access, and expiration risk before submitting transfer. · Do not retry a failed transfer until the cause is corrected. Step 10: Back up DNS This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Back up existing DNS records before changing nameservers or DNS settings. · Test website and email separately after the change. Step 11: Monitor completion and keep records This step helps you handle how to handle domain orders, renewals, and transfers as a reseller with a clear, safe, and support-ready workflow. · Review the account information carefully before acting. · Keep a written record of the decision, action, and final result.
Common Mistakes Mistake 1: Launching automation without testing Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request. Mistake 2: Not checking balance before paid orders Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request. Mistake 3: Ignoring renewal workflow Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request. Mistake 4: Selling too many TLDs before understanding rules Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request. Mistake 5: Not backing up DNS before transfer Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request. Mistake 6: Showing raw technical errors to customers Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
FAQ 1. What is this article about? This article explains how to handle domain orders, renewals, and transfers as a reseller in a practical NiceNIC Help Center format. 2. What should I check first? Start with the domain name, account, order or status information, current evidence, and the exact action you want to complete. 3. Can this affect website or email? Yes, some domain, DNS, renewal, transfer, hold, or nameserver issues can affect website and email. Test both services separately. 4. Should I repeat the same request if it fails? Not for paid, transfer, renewal, restore, DNS, or compliance-sensitive actions. Confirm the original status first. 5. What evidence should I save? Save screenshots, order numbers, invoice numbers, transaction IDs, RDAP results, status codes, error messages, and support ticket numbers where relevant. 6. Can NiceNIC support help? NiceNIC support can review issues for supported accounts, domains, payments, reseller workflows, API or WHMCS actions, and domain management cases where applicable. 7. How does reseller setup fit into this process? Reseller setup should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken. 8. How does API fit into this process? Api should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken. 9. How does WHMCS fit into this process? Whmcs should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken. 10. How does domain registration fit into this process? Domain registration should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.