cPanel • VPS Speed • WordPress Ready

Super Fast Web Hosting Plus With Dedicated Power

Get VPS-grade speed paired with the ease of cPanel. Host up to 200 websites and databases, enjoy free unlimited SSL certificates, unmetered traffic, and raw capacity up to 32 GB RAM & 16 CPUs.

Capacity

200+ Sites

Memory Peak

32 GB RAM

Core Capacity

16 CPUs

Zadic cPanel Hosting Dashboard

Free Unlimited SSL Pre-Installed

cPanel

Free Unlimited SSL

Every single website and subdomain receives an automated, robust SSL certificate at zero extra cost across your account.

Unmetered Bandwidth

Scale with confidence. Our Web Hosting Plus plans handle traffic surges with unmetered throughput built for demanding portals.

Up to 32 GB RAM & 16 CPUs

Experience dedicated-server performance without the complexity of server administration, all managed through modern cPanel tools.

MANAGEMENT & CONTROL

Why ZADiC Web Hosting?

ZADiC Web Hosting delivers dedicated computer capacity on an optimized Linux architecture backed by industry-standard cPanel control.

Easy Website Creation

Install top-tier content management engines like WordPress, Drupal, and Joomla directly from your cPanel in a single automated step.

Rapid Website Publishing

Build, deploy, and launch websites swiftly. Go live with staging tools, automated configurations, and instant DNS synchronization.

Business Management

Control email accounts, files, databases, real-time traffic statistics, domain setups, and application backups from one centralized pane.

Comprehensive Web Services

Power every aspect of your online presence with integrated tools brought to you by ZADiC Web Hosting.

 

 

Web Design Plus Hosting

Responsive design packages with fast hosting, SSL certificates, appointments, and shopping cart setups.

Explore Website Builder →

Website Hosting

Dedicated stacks including cPanel, managed WordPress, Web Hosting Plus with Free SSL, and enterprise VPS with 24/7 support.

Domain Name Registration

Search 200+ domain extensions. .COM domains are $10.99 for new registrations and transfers, with full DNS management.

Register Domains →

Professional Email

Brand your communications with custom you@yourdomain mailboxes backed by cloud security and Microsoft 365.

Configure Email →

Search Engine Optimization

Step-by-step SEO audits and structural recommendations to elevate organic keyword positions on Google.

Explore SEO Tools →

Email Marketing

Connect with subscribers, automate campaigns, track open rates, and boost retention through high deliverability.

Start Campaigns →

RELIABLE COMPUTING TIERS

Popular cPanel Hosting Plans

Reliable Linux-based web hosting paired with an intuitive cPanel dashboard. Deploy WordPress and popular applications with one-click installers, manage email accounts and databases seamlessly, and secure selected websites with unlimited free SSL on eligible plans.

cPanel Starter

Entry Level

$4.99

/month

1 website

1 database

10 GB storage

SSL not included

cPanel Economy

Standard

$9.99

/month

1 website

10 databases

25 GB storage

SSL not included

cPanel Deluxe

Most Popular

Most Popular

$14.99

/month

10 websites

25 databases

50 GB storage

Unlimited Free SSL

cPanel Ultimate

High Performance

$18.99

/month

25 websites

50 databases

75 GB storage

Unlimited Free SSL

RELIABLE COMPUTING TIERS

Popular Web Hosting Plus Plans

Select your required resource allocation. Every tier includes unmetered traffic, automated cPanel management, and unlimited free SSL.

Launch

For multiple basic sites

$30.99

/month

100 GB Storage

4 GB RAM & 2 CPUs

Unmetered Traffic

50 Websites & DBs

Unlimited Free SSL

Enhance

High-traffic CMS sites

Popular

$49.99

/month

200 GB Storage

8 GB RAM & 4 CPUs

Unmetered Traffic

100 Websites & DBs

Unlimited Free SSL

Grow

Advanced eCommerce

$69.99

/month

300 GB Storage

16 GB RAM & 8 CPUs

Unmetered Traffic

150 Websites & DBs

Unlimited Free SSL

Expand

Peak enterprise capacity

$99.99

/month

400 GB Storage

32 GB RAM & 16 CPUs

Unmetered Traffic

200 Websites & DBs

Unlimited Free SSL

EASY SETUP ENVIRONMENT

One Click Installs

Deploy applications with automatic setup, regular security updates, and scheduled backups.

Featured Media & Video Guides

Watch step-by-step setup guides to deploy high-traffic portals in seconds.

Content Management

WordPress, Drupal, Joomla, b2evolution, Serendipity, Concrete5, MODX.

Community Building

phpBB, MediaWiki, SMF, Vanilla Forums, MyBB, ElkArte.

e-Commerce & Business

Magento, OpenCart, PrestaShop, Zen Cart, osCommerce, BoxBilling.

Photos and Files

Nextcloud, Piwigo, ownCloud, Coppermine, Zenphoto, Gallery.

Surveys and Statistics

LimeSurvey, Matomo, Advanced Poll, Simple Poll, Open Web Analytics.

Miscellaneous

RoundCube, phpMyAdmin, Webmin, SiteBar, Open Real Estate.

Talk With an Expert to Get Started Today!

Need guidance picking the right RAM or CPU tier? Our systems team is available 24/7 to help you.

What’s New?
  • How to Create a MySQL Database and User in cPanelWeb HostingHow to Create a MySQL Database and User in cPanelA MySQL database in cPanel gives your website a place to store content, settings, and user information. You can create the database and its user in a few steps, then grant the access your application needs. For your first setup, use the MySQL Database Wizard. It guides you through naming the database, creating a user, and assigning access. Before you begin, check your account-specific database prefix and character limits so your names fit the rules. Create a database and user in cPanel The MySQL Database Wizard is the simplest route for a first database. The MySQL Databases interface is also useful when you want to create a database and user separately or manage existing users. Use the MySQL Database Wizard Sign in to cPanel and open MySQL Database Wizard in the Databases area. Enter a name and continue. cPanel may add your account’s database prefix automatically. Create a database user, then set a strong password. Use Password Generator and save the generated password securely. Continue to the privileges screen and select the permissions the application needs. For a typical application installation, follow the application’s setup instructions. Finish the guided setup. It grants the user access to the database you created. Back in cPanel, check Current Databases and confirm the new entry appears. The cPanel Database Wizard documentation describes the guided process for MySQL and MariaDB. The exact screen layout can vary by cPanel version, but the key steps are the same: database, user, password, privileges. Use the MySQL Databases interface If you prefer to do each part in the main interface, open MySQL Databases in cPanel. Under Create New Database, enter a name and create it. For the Create User step, select Add New User and set a strong password. Find Add User to Database, choose the user and database from their menus, and select Add. cPanel then opens the privileges screen. This interface gives you a clear view of the database and user as separate items, which can help when you’re working with an existing setup. Write down the full identifier, username, and password in a secure place. Your application will need the same credentials, including any prefix cPanel adds. Add a user to a database and set privileges A database user must be attached to the correct database before an application can use it. Creating a user alone doesn’t grant access. Attach an existing user In MySQL Databases, go to Add User to Database. Select the existing user and the database, then choose Add. If the user isn’t listed, create one first under Add New User. When the privileges screen appears, choose the permissions the application requires. If the application’s instructions call for full access, use All Privileges. If they specify particular permissions, grant only those. The right choice depends on what the application needs to do with its data. Check access when a connection fails If an application can’t connect after setup, check the basics before changing database contents. Confirm that the full identifier and username include their cPanel prefixes, that the saved password is correct, and that the user is assigned to the intended database with the required privileges. A password change can also leave an application using an old credential. cPanel doesn’t reveal a stored database password, so if you’ve lost it, set a new password and update the application’s configuration to match. Understand database and username length limits Names that look short can run into cPanel’s limits because account prefixes count too. The exact username limit depends on whether the server runs MySQL 5.6, MySQL 5.7, or MariaDB. Under MariaDB, a longer cPanel account username leaves less room for the database username. Name or server version Limit and prefix details Database name Up to 64 characters; each underscore counts as two characters toward the limit Database name with prefixing enabled Up to 63 characters in total, including the prefix and underscore MySQL 5.6 database username Up to 16 characters total; the prefix uses eight account-name characters plus an underscore, or nine characters MySQL 5.7 database username Up to 32 characters total; the prefix uses 16 account-name characters plus an underscore, or 17 characters MariaDB database username Up to 47 characters total; the prefix uses the full cPanel account username plus an underscore For a prefixed name such as example_database, count the database prefix and separator toward the full name limit. The underscore also uses two characters of the database-name limit. cPanel’s MySQL Databases documentation and version-specific wizard notes explain these limits. If you administer the server through WHM, Force short prefix for MySQL and MariaDB databases in Tweak Settings limits the prefix to eight characters. Force short prefix also prevents creating new cPanel accounts whose usernames share the same first eight characters. That rule helps avoid prefix conflicts, but it affects account creation, so it’s a server-level setting to handle with care. For WordPress sites, the database prefix also appears in table names and configuration. If you’re managing a WordPress prefix, see our guide to changing the WordPress database prefix safely. Why you shouldn’t create databases in phpMyAdmin Use cPanel’s database tools to create databases and database users. phpMyAdmin doesn’t map databases created there into cPanel’s database-management system. That can cause problems with cPanel backups and restorations. phpMyAdmin is useful for working with tables and data after a database exists. It’s not the right place to create the database or its user. Keeping setup inside cPanel gives the account tools the information they need to manage the database properly. For additional guidance on access and safer database work, read our article on phpMyAdmin security in cPanel. Strong account credentials and a backup before major changes make database tasks easier to recover from. Check, repair, or rename a database safely cPanel includes tools for checking and repairing databases. Before a major change, create a backup you can restore. This is especially important before renaming a database. Check and repair tables Open MySQL Databases and find the database you want to inspect. Use Check Database to look for problems. If cPanel identifies corruption, choose Repair Database for that database. A Check Complete or Repair Complete message confirms that the operation finished. It doesn’t replace a backup, so keep a restorable copy before maintenance. For a WordPress-specific repair walkthrough, see our guide to repairing a WordPress database using cPanel. Rename a database with care MySQL doesn’t rename a database directly. Instead, cPanel creates a new database, moves the data, recreates grants and stored code, then deletes the old database. In cPanel, the rename process can terminate active connections, so a website or application using the database may be interrupted. Before renaming, back up the database. Afterward, update configuration files that refer to the old identifier. The user and its privileges also need to be in place on the replacement database. Check the application once the changes are complete. Key takeaways Use cPanel’s guided setup for a first MySQL database setup; it creates the database and user, then grants access. Prefixes count toward name limits, and username limits vary by MySQL or MariaDB version. Create databases and users through cPanel, not phpMyAdmin. Back up before repair or rename operations, and update application configuration after a rename. Frequently asked questions How do I create a MySQL database and user in cPanel? Open the guided setup, name the database, create a user and password, then assign privileges and finish. The setup tool automatically grants that user access to the database. How many characters can a database name have? The standard maximum is 64 characters, with each underscore counting as two. When database prefixing is enabled, the full database name has a 63-character maximum, including the prefix and underscore. How long can a database username be? The total limit is 16 characters for MySQL 5.6, 32 for MySQL 5.7, and 47 for MariaDB. The account prefix and underscore count toward each limit. Why shouldn’t I create a database in phpMyAdmin? phpMyAdmin doesn’t map databases into cPanel’s system. Creating one there can interfere with cPanel backups and restorations, so use MySQL Databases or the setup tool instead. Set up your database with confidence A working database setup comes down to three things: a valid name, a user with the right privileges, and credentials your application can use. Keep the cPanel prefix in your records, and make a backup before maintenance. If you’re choosing a hosting setup for a site that uses cPanel, compare cPanel hosting and website builder options to find a fit for the way you want to manage your website. […]
  • Self-Managed VPS Hosting: Your Server ResponsibilitiesVPS Website Hosting / Web HostingSelf-Managed VPS Hosting: Your Server ResponsibilitiesWith self-managed VPS hosting, you get full root access, but server management, including the operating system, software, security patches, and maintenance, is your responsibility. Your provider runs the physical hardware, network, and virtualization layer. That gives you full control, along with a longer to-do list than shared hosting. We recommend choosing this setup when you want that control and have someone ready to manage it. Start with the responsibility split, because it shapes the cost, workload, and support you’ll need from your VPS hosting provider. What self-managed VPS hosting puts under your control With VPS hosting, a virtual private server gives your websites an isolated environment on a shared physical machine. You receive allocated resources, install your own software, and configure services around your workload. Allocated RAM and storage don’t automatically mean dedicated physical CPU cores, even when a plan advertises dedicated resources. Providers may list CPU allocation in vCPUs, with shared or dedicated CPU options depending on the plan. Compared with shared hosting, the management choices determine how much control you have. Responsibility Shared hosting Self-managed VPS Managed VPS Hardware and network Provider Provider Provider Root access No Yes Depends on service OS maintenance Provider You Provider within scope Server configuration Limited choices You Shared by agreement Application updates Usually you You Depends on coverage Backups and restores Plan-dependent You arrange them Plan-dependent We suggest reading “managed” as a defined service, rather than a promise that everything is covered. Your website content, application settings, and user access still need an owner. Secure access and software updates become your job Your provider can deliver a working server. What you install, expose, and leave running after that is your responsibility. Lock down access before launching On Linux, we recommend SSH keys and a separate administrator account with sudo permissions. Test that access before disabling password-based or direct root login. Configure both provider-level and operating-system firewalls where available. Open only the ports your services require. Keep databases private unless remote access is necessary. Check whether your provider offers DDoS protection, since availability and coverage vary by plan. It doesn’t replace security measures you manage on your server. Windows needs the same care. Restrict Remote Desktop access through a VPN or trusted network instead of leaving it open to everyone. You also own administrator permissions, unused accounts, and credential changes when team members leave. Full control works best when access stays tidy. Maintain the whole software stack Updates go beyond WordPress plugins. Your operating system, kernel, PHP version, database, web server, control panel, and container images all need attention. We recommend supported software releases, scheduled maintenance, and prompt action on serious security fixes. Some changes require a reboot. Others need compatibility testing before they reach your live site. Keep a rollback path for configuration changes. A saved configuration and usable backup can turn a broken update into a manageable repair. Installing cPanel or Plesk makes these jobs easier to organize. It doesn’t transfer ownership of them. Backups and monitoring need more than a switch Automation helps, but someone still needs to know whether it worked. With self-managed VPS hosting, that someone is you or your administrator. Build recovery around usable backups Back up website files, databases, configuration, and anything else needed to rebuild the service. Keep copies outside the VPS, with separate access credentials where possible. Database backups need a consistent capture method. Copying active database files without coordination can leave you with an unusable restore. Snapshots are useful before changes, but we don’t recommend treating them as your only backup. Retention, storage location, and restore access matter too. A successful backup notification proves that a job finished. A successful restore proves that the backup can bring your service back. Test restores in an isolated environment so recovery practice doesn’t overwrite production. Watch the website and the server Monitor CPU, memory, disk space, service failures, and certificate expiry. Add an external website check, because a running virtual machine can still serve a broken checkout. Our guidance on website uptime monitoring covers that distinction. Give alerts a named responder. Review backup failures and availability alerts daily, schedule routine maintenance, and repeat recovery tests after major changes. Critical security patches shouldn’t wait for the next calendar slot. Compare the server price with the support behind it Self-managed plans usually cost less because administration stays with you. The server bill is only part of the budget. Allow for backups, panel licenses, monitoring, and administrator time. HostGator’s entry pricing is about $4 to $4.69 monthly, with its VPS range reaching $99.99. Its NVMe 2, 4, 8, and 16 tiers include root SSH and API access, but exclude cPanel and 24/7 priority support. DigitalOcean’s specialized Droplets illustrate the next pricing step: CPU-Optimized starts at $42 monthly, General Purpose at $63, Memory-Optimized at $84, and Storage-Optimized at $131. Those aren’t its cheapest basic servers. Liquid Web separates self-managed, core managed, and fully managed services. It lists cPanel, Plesk, and InterWorx options. Fully managed coverage includes 24/7 support, OS and panel updates, firewall setup, PHP support, monitoring, and backup restores. Its advertised 10 Gbps network and 99.9% server uptime guarantee describe infrastructure and availability commitments. They don’t mean every application problem is automatically covered. Storage deserves attention too. NVMe means Non-Volatile Memory Express. An NVMe SSD supports higher transfer speeds and lower latency than SATA SSD storage, as Kingston’s SATA and NVMe comparison explains. Faster storage helps disk-heavy workloads, but it won’t repair inefficient database queries. Our advice: compare the vCPU allocation, management scope, and extras such as DDoS protection. A low monthly price can still leave you with substantial work. Choose a setup your team can confidently run You don’t need every server skill on day one. Choose VPS hosting that matches your team’s capacity to manage failures before they affect customers. Match the plan to practical skills Can your administrator handle server management and read service logs? Can they diagnose a full disk, restore a database, or reverse a failed configuration change? Can someone respond when that person is unavailable? If those jobs are covered, self-managed hosting can fit custom software applications, demanding stores, development environments, and multiple client websites. If nobody owns those tasks, we recommend a more managed service. Our Web Hosting Plus plans offer a simpler upgrade path for growing sites that don’t need unrestricted server access. Choose tools without confusing them with management A panel reduces manual work. It doesn’t supply an administrator. Our cPanel and Plesk comparison explains the differences between those interfaces. Panel licensing is separate from the underlying VPS unless a plan bundles it. For projects that need deeper control, our Linux and Windows VPS plans offer panel-based or no-panel setups, with configurations reaching 32 CPU cores, 128 GB RAM, and 1.5 TB SSD storage. We recommend buying the capacity your workload needs, then choosing the administration tools you can support. Bigger specifications won’t reduce maintenance by themselves. Scale or migrate with a recovery plan A standard in-place VPS upgrade can retain the server, IP addresses, and data. You can scale up by adding capacity without rebuilding the website. The administration work continues afterward. Web servers, database buffers, PHP workers, and caches may need retuning to use the extra RAM or CPU. More memory won’t help a service that’s still configured for the old limit. Moving between providers, operating systems, panels, or management services is a migration. Treat it as a move to a tested destination, with a rollback plan. We recommend copying files and databases first, then testing the application before changing DNS. Include email, scheduled jobs, SSL certificates, DNS records, and background workers. Store orders and membership changes need a final synchronization so new activity doesn’t disappear during the move. HostGator advertises zero-downtime transfers that preserve content, themes, and plugins. Its free VPS migration offer has eligibility conditions, including a 12-month plan and signup within 30 days. This shows that migration assistance and ongoing management are separate services. Keep the original environment available until traffic, mail, and data are working correctly at the destination. Key takeaways before choosing a plan The provider maintains physical infrastructure, while you maintain the operating system and installed services. Control panels simplify administration, but updates, access security, monitoring, and recovery still need an owner. We recommend a self-managed VPS when you need custom control and have reliable administration available. Choose more managed hosting when simplicity matters more. Frequently asked questions Which operating system can a VPS run? Available Linux distributions and Windows options depend on the platform. Our VPS choices include both, with root access on Linux and administrator access on Windows. DigitalOcean lists Ubuntu, CentOS, and Debian options, custom images, and one-click applications including Docker, LAMP, LEMP, MongoDB, MySQL, and Node.js. Choose a supported OS version compatible with your application and control panel. What support does self-managed hosting include? Infrastructure, account, and billing support are different from software administration. With self-managed hosting, expect to own custom installations, application troubleshooting, hardening, and recovery unless those services are included separately. Our self-managed support resources include guides, knowledge-base articles, and ticket help for account setup, billing, and basic troubleshooting. Can a VPS be upgraded later? Yes. VPS hosting supports adding resources as demand grows, although upgrade procedures vary. An in-place capacity increase differs from changing operating systems or moving to a new platform. We recommend keeping a current backup before either change. Afterward, review resource limits and service configuration so the application benefits from the upgrade. Put control in capable hands Self-managed VPS hosting gives you room to customize, expand, and run software your way. Reliable administration is what keeps that freedom useful. We recommend choosing it when someone can own updates, security, backups, and recovery. If you’d rather spend that time running your business, choose a more managed setup. The right hosting plan gives you the control you need and a workload you can sustain. […]
  • How to Add an Addon Domain in cPanelDomains / Web HostingHow to Add an Addon Domain in cPanelAdding a cPanel addon domain lets you host another registered website in the account you already have. The key is to prepare the domain’s DNS first, then give the new domain name its own dedicated site folder in cPanel. Skip those checks and the domain may fail to add, point to the wrong place, or disrupt services tied to it. We’ll walk through the setup in order, including ownership validation, common errors, temporary domains, and cleanup. Before you add the domain An addon domain is an additional domain managed by your cPanel account. It can have its own website files in a separate directory, so each site stays organized. cPanel now commonly groups domain setup under Domains, even when your host still calls the feature “addon domains.” cPanel’s glossary defines addon domains and how their directories work. Some hosts don’t support this feature, and menu labels vary by cPanel version and hosting plan. Check the domain and your hosting plan The domain must be registered and available to add to your account. It also can’t already be attached to that same account as the main domain or as another addon domain. If cPanel reports that the domain already exists, check the account’s domain list before trying again. Your hosting package determines how many websites or domains you can attach. Those limits vary by company and plan. For example, NameHero lists Starter Cloud for one website, Plus Cloud for up to seven, and Turbo Cloud and Business Cloud for unlimited websites within a 500,000 inode or file limit. Turbo Cloud includes 3 GB of physical memory, while Business Cloud includes 4 GB. Point the domain to the host A domain’s nameservers tell the internet where its DNS records are managed. Set the nameservers at your domain registrar to the values supplied for your hosting account. NameHero says its nameservers are account-specific, so use the details assigned to your service rather than assuming one pair applies to every account. Nameserver changes take time to spread across DNS. During that period, the domain may work for some visitors before it works for others. Avoid repeatedly changing settings while the update is spreading. For a plain explanation of how the two settings differ, see our guide to nameservers and DNS records. Validate domain ownership when nameservers must stay Sometimes you can’t point the domain to your hosting provider’s nameservers. You may need to keep a third-party DNS service, build the website before connecting the domain, or prepare a DNS zone in advance. In these cases, domain name validation through your hosting panel may prove ownership without changing nameservers, if your host supports it. The validation token is temporary. Namecheap’s process gives the code a one-day validity window, so complete your chosen method before it expires. Choose one of the three validation methods Use the method your hosting panel offers and follow its instructions for the token and exact location: With DNS TXT validation, add the provided TXT record through the service that currently manages the domain’s DNS. With HTTP TXT validation, upload the provided text file to the specified website root. With HTML validation, place the supplied code in the head section of the website. After making the change, return to the hosting panel and run the validation step. A failed check may mean the token was entered in the wrong DNS manager, the file is in the wrong directory, or the code has expired. Add the domain in cPanel Once the domain is ready and your plan allows another site, the cPanel setup is short. The domain must point to the host or pass the control validation the host requires. Otherwise, submitting it may produce an error. Create the domain entry Sign in to cPanel and open the Domains menu. Click Create A New Domain. Enter the registered domain name. Choose whether it should share the main domain’s folder. Click Submit. The Subdomain field usually fills in automatically after you enter the domain. It supports cPanel’s internal setup, so you can generally leave it as provided. For a standalone website, select a separate folder for the site files. cPanel’s Create a New Domain instructions describe the available settings. Choose the right document root The website’s files live in its assigned folder. A separate folder keeps the addon site’s files apart from your main website. If you choose a shared folder, both domains can show the same content, which may not be what you intend. Use a clear folder name that matches the domain or project. Keep the new site’s files in that folder when you upload them or install an application. cPanel’s domain management documentation explains how to view and manage site folders. Fix common addon-domain errors An error during setup often points to a prerequisite, not a broken cPanel account. Check the domain’s status, DNS direction, and account limit before changing other settings. The domain is not pointed to the host If the nameservers still direct the domain elsewhere, cPanel may reject the submission. Confirm that the registrar has the hosting provider’s nameservers saved and allow time for DNS to update. If nameservers must remain unchanged, use the ownership validation option when it is available. Also check that you are editing DNS at the active provider. If a domain uses third-party nameservers, edits made in the hosting account’s DNS editor may not control the live records. The domain already exists or the plan is full If cPanel says the domain is already in use, check whether it is attached as the account’s primary domain or listed under Domains. A domain can’t be added again in the same account under a second role. If the account has reached its website limit, cPanel may block another domain even when the DNS is correct. Your host’s plan limits show why this varies: Starter Cloud allows one website, while its higher tiers allow more. Your host’s account configuration, not the cPanel screen alone, determines the limit. Set up the website after adding the domain Adding a domain creates its cPanel entry and directory. It doesn’t automatically create a finished website. Upload the site files to the selected document root, or use a supported application installer to set up a content management system such as WordPress. If you’re choosing hosting for multiple websites, compare ZADiC cPanel web hosting and ZADiC’s cPanel hosting plans. Choose a package that supports your site count and resource needs. Check SSL and the Sitejet Builder rules After DNS points to the hosting account, check whether an SSL certificate is active before sending visitors to the site. NameHero says its AutoSSL is automatic once the nameservers point correctly, though a certificate may not appear as soon as you add the domain. Test the site in a browser and confirm the secure https:// version loads the intended site before launch. If you plan to use Sitejet Website Builder, cPanel lists several Sitejet Builder restrictions. The domain can’t share a document root, have a redirect configured, or belong to an account that has reached its domain limit. Remove any existing redirect before publishing. Publishing may offer a restore point if files already exist. It can also delete an existing robots.txt file, so save a copy if you need it. See cPanel’s Sitejet Builder documentation. Use a temporary domain only for testing Some hosts provide a temporary cpanel.site subdomain so you can preview a website before connecting its permanent domain. It’s useful for early setup, but it isn’t a substitute for a permanent domain. Namecheap notes that its temporary domains don’t support email or DNS editing. When you’re ready to switch, open Domains, select Manage, and choose Replace with a registered domain. Then enter the domain and complete the prompts. The new domain may use a different document root. Your files don’t move automatically when you replace the temporary domain. Move or copy the site content to the new root, then check the domain and SSL before launch. Remove an addon domain without deleting its files Removing a domain from cPanel disconnects its entry from the account. It doesn’t automatically erase the document root or the content stored there, which gives you a chance to keep or reuse those files. Open Domains, click Manage beside the addon domain, and select Remove Domain. Confirm with Yes, remove this domain. The domain entry is removed, but the directory and website content remain in File Manager. Delete those files separately only if you no longer need them. Before removing a live domain, consider what else uses it. Website files, email accounts, and DNS settings are separate pieces of the setup. Removing the domain entry doesn’t replace a planned migration or preserve services that depend on the domain. Frequently asked questions How do I add a new domain to cPanel? Point the domain to your hosting account or complete ownership validation if nameservers must stay elsewhere. Then open Domains, choose Create A New Domain, enter the registered domain, select a new or shared document root, and submit. Why does cPanel show an error when I submit the domain? The domain may not point to the host, may already exist in the account, or the hosting plan may have reached its domain limit. Check those three items first. How long does nameserver propagation take? The update isn’t instant, and timing varies across networks. Give DNS time to update before repeatedly editing settings. Test again later from a different network if the domain still shows the old destination. Do I need to validate ownership if I can change nameservers? Usually, validation is for cases where nameservers can’t be changed and the hosting provider offers another ownership check. Follow the method shown in your hosting panel. Key takeaways Check the domain, plan limit, and nameservers before opening the cPanel form. Give each independent website its own document root. Use domain validation when nameservers must remain with another provider. After setup, add the site files and confirm the secure version works. Add the domain with confidence A cPanel addon domain is straightforward to set up when DNS, account limits, and the document root are ready first. Take care of those pieces, submit the domain, and then finish the website in its own folder. That keeps the process clear and your sites easier to manage. […]
  • cPanel vs Plesk on a VPS: Which Fits?VPS Website Hosting / Web HostingcPanel vs Plesk on a VPS: Which Fits?Choose cPanel for Linux hosting with separate website-owner and administrator tools. Choose Plesk when you need Windows Server support or prefer licensing built around domain limits. The cPanel vs Plesk decision starts with how you run your websites, not which dashboard looks better. Licensing and operating-system support can settle the choice before features enter the picture. Compare each VPS control panel by the everyday tasks you need to manage, then check whether its interface is user-friendly for those tasks. Key takeaways: cPanel vs Plesk Here’s the short version before you commit to a VPS. Decision point cPanel Plesk Supported operating systems Linux only Linux and Windows Server License measurement Accounts per server Domains allowed by edition Administration cPanel plus WHM Website and server administration tools Domain limits Depend on account configuration 10, 30, or unlimited Multi-server options DNS and Configuration Clusters Retired Multi Server extension Strong fit Linux hosting and separate client accounts Microsoft-platform hosting and domain-based portfolios Our starting advice is simple: let your applications choose the operating system. Then let your client structure choose the license. CPU, memory, and storage determine resource usage on a VPS. An unlimited-domain license removes the domain cap, but it doesn’t guarantee sufficient capacity. Operating systems and everyday management Linux or Windows comes first cPanel runs on supported Linux distributions, including AlmaLinux, CloudLinux, Rocky Linux, and Ubuntu. It does not run on Microsoft’s server platform. Plesk supports Linux and Windows Server, including Windows Server 2022 and 2025. That makes it the straightforward choice between these panels when your software depends on Microsoft’s server stack. Choose the application stack before the control panel. A familiar dashboard won’t solve an operating-system mismatch. Linux works well for conventional website hosting; Microsoft’s server stack matters when your application depends on it. cPanel separates website work from server work cPanel gives website owners tools for their hosting accounts. WHM, short for Web Host Manager, gives administrators and resellers broader controls. As a control panel, Plesk presents site and server tasks in one interface, while cPanel separates them between cPanel and WHM. Plesk’s Extensions Catalog includes tools such as Docker and Git; check OS and edition compatibility before relying on an extension on your VPS. That separation helps when you need distinct client logins, account limits, and server-level administration. You handle the server in WHM; clients handle their websites in cPanel. We favor this structure when clear account boundaries matter. For anyone coming from shared cPanel hosting, it also keeps everyday tasks familiar while adding VPS-level control. Pricing: count accounts before comparing costs Panel licensing costs are separate from your VPS bill. Storage, server resources, backups, and management services can add separate charges. cPanel charges by account tier In November 2026, cPanel’s published license pricing lists Admin Cloud at $35.99 monthly for up to five accounts. Pro Cloud costs $53.99 monthly for up to 30 accounts. An account isn’t the same thing as a domain. One cPanel account can contain multiple domains, subject to its hosting configuration. For agencies and resellers, that distinction matters. Separate client accounts give you cleaner administration, but increasing the account count can move you into a higher license tier. We recommend budgeting around client accounts rather than counting websites alone. Plesk charges by edition and domain allowance Plesk Web Admin supports 10 domains, Web Pro Edition supports 30, and Web Host supports unlimited domains with reseller management. Plesk’s published pricing page, dated November 12, 2026, lists monthly renewal rates of $16.99, $29.99, and $62.99 respectively. Its November 13 licensing guide lists different VPS monthly base rates: $18.99, $33.99, and $73.99. These official schedules differ, so they shouldn’t be presented as one interchangeable price list. The practical distinction remains clear: cPanel scales licensing around accounts; Plesk uses edition-based domain allowances. Neither panel license includes the underlying VPS. DNS and SSL: automation has boundaries DNS management routes visitors and email to the right place, but control depends on where authoritative DNS is hosted and who can edit its records. SSL certificates encrypt browser connections. Both deserve attention before migration day. DNSSEC takes more than a switch cPanel documents DNSSEC support through PowerDNS. An administrator enables the Manage DNSSEC feature, then account users manage signing keys through Zone Editor. Plesk offers DNS templates for repeatable zone settings. Its DNSSEC extension documentation says the extension is included free with Web Pro and Web Host. That corrects a common oversimplification: Plesk DNSSEC isn’t always a separate paid purchase. We prefer its templates when consistent DNS settings matter across a portfolio, while cPanel gives administrators explicit control over feature access. Wildcard certificates need DNS validation cPanel’s AutoSSL documentation identifies Let’s Encrypt as the default provider and confirms wildcard support. Plesk’s wildcard certificate process requires a matching TXT record containing the value displayed by its extension. When DNS is external, that record lives outside the panel. We wouldn’t choose either panel on a broad promise of “automatic SSL” alone. Standard certificates and wildcard certificates have different validation requirements. With external DNS, a certificate tool doesn’t automatically control the TXT records needed for wildcard validation. For fewer surprises, match certificate management to where your authoritative DNS actually lives. That connection matters more than the label on the SSL button. Mail and security: understand what you’re managing A dashboard makes configuration easier. It doesn’t remove responsibility for the services behind it. Different mail stacks, similar responsibilities cPanel uses Exim for mail transport and Dovecot for IMAP and POP3 access. Plesk’s Linux mail stack includes Postfix. Plesk documents DKIM, SPF, and DMARC configuration. These help receiving systems assess whether messages genuinely belong to your domain. External DNS still matters. If your authoritative records live elsewhere, the authentication records must exist there. Treat mail authentication as part of deployment, rather than waiting until customer messages start landing in spam. Firewall software needs a maintenance plan CSF, ConfigServer Security and Firewall, has long been associated with cPanel administration. Its original developers ended support on August 31, 2025. WebPros maintains its own version for security and stability updates, but that maintenance doesn’t include configuration or troubleshooting support. Where installed and supported, Fail2Ban can block repeated authentication attempts. Check that Fail2Ban’s rules and updates are maintained. The lesson is practical: distinguish installed software from an ongoing management service. On a self-managed VPS, assign an owner for panel and OS security updates. That owner also needs to manage access controls and incident response unless your hosting agreement assigns those tasks elsewhere. Decide who handles these tasks before launch. Clear responsibility makes support conversations much easier when something breaks. WordPress tools: look beyond one-click installation Getting WordPress installed is the easy part. Keeping several sites organized takes more attention. cPanel includes WordPress Toolkit (WP Toolkit). Deluxe features require the relevant WP Management and WP Toolkit Deluxe features to be enabled. Smart Updates tests updates in a temporary clone before applying changes to the live website. That gives you a useful safeguard when a plugin or theme update could affect the site. Softaculous may provide an installer, but check whether your plan includes it. It isn’t equivalent to site management or update testing. Compare the WordPress Toolkit feature entitlements rather than assuming every installation exposes identical tools. Basic installation, site management, and update testing are different capabilities. If your main goal is publishing a website rather than administering a server, our cPanel hosting plans offer a simpler starting point. A VPS makes more sense when you need server-level access, custom configuration, or room beyond your existing hosting allocation. Multiple VPS instances need a separate plan cPanel offers DNS Clusters and Configuration Clusters, but they address different needs. DNS Clusters share DNS records between servers for redundancy. They don’t turn websites, databases, and mail into one clustered application. Configuration Clusters let an administrator link a master server with additional servers for supported configuration tasks. That’s useful, but it’s narrower than complete fleet management. Plesk’s former Multi Server extension for multi-server management isn’t supported from Onyx 17.8 onward because of XML API incompatibility. Plesk says it has no plans to support it in Obsidian. We give cPanel the advantage for these documented native clustering functions. Neither panel’s described clustering features provide complete fleet or application-availability management. If your growth plan includes several VPS instances, separate three requirements: shared DNS, repeatable configuration, and application availability. A panel that handles one job won’t automatically cover the other two. Each server also needs its own capacity and maintenance plan. Choose the setup, then plan the move For Linux agencies that want separate client accounts, we recommend cPanel with WHM. For applications that require Microsoft’s server stack, Plesk is the clear choice. For domain-heavy portfolios, Plesk’s edition limits make licensing easier to map against your workload. Our VPS hosting options include Linux and Windows choices, with control-panel or no-panel configurations. Plesk Web Pro supports 30 domains; Web Host removes that domain ceiling and adds reseller management. Prefer direct administration? A no-panel server gives you root access on Linux or administrator access on that platform. It also leaves more setup and maintenance in your hands. Readers with containerized or repository-based workloads should verify that their chosen panel, OS, and edition support the Docker and Git integrations they need. When switching panels, plan for websites, databases, mailboxes, DNS, and scheduled tasks. A website copying successfully doesn’t prove that mail delivery or background jobs survived the move. We recommend keeping independent backups of the source files, databases, and mail. Verify that backups can be restored before changing DNS, and retain the previous environment while traffic and mail settle. Give the migration the same attention as the purchase. Frequently asked questions Can cPanel and Plesk run on the same VPS? Choose one hosting control panel per server. Both manage overlapping services and configuration, so installing them together creates conflicts rather than useful flexibility. For a panel change, we recommend a separate destination VPS and a planned migration. That gives you a working source environment while you prepare and test the replacement. Does a control panel replace server management? No. It simplifies server management. You still need responsibility for updates, access security, monitoring, and recovery. We recommend separating the panel decision from the management decision. A friendly interface can reduce manual work, but a self-managed VPS still needs someone who understands the server behind it. Pick the panel that matches your workload Choose cPanel if you run Linux and need separate client accounts. Choose Plesk if you need Windows Server or domain-based edition limits. If you want direct server control, choose a no-panel VPS. Match the workload to your license budget and maintenance responsibilities. Then explore our VPS hosting products to choose the setup your websites need. […]
  • WooCommerce Deposits for High-Value ProductsWooCommerce / WordPressWooCommerce Deposits for High-Value ProductsWooCommerce deposits let you collect part of a product’s price upfront and the remaining balance later. With a deposits extension, you can offer a smaller first payment, require a commitment on custom orders, or spread payments across a schedule. For high-value products, that gives customers breathing room without leaving your store waiting for the entire payment. We recommend starting with one product and a clear collection policy before expanding across your catalog. Key Takeaways Choose a fixed deposit, percentage deposit, or payment plan to match how you sell. WooCommerce Deposits schedules future payments but doesn’t automatically charge customers’ cards. Keep payment confirmation, fulfillment, stock, and refunds connected to the correct order records. Choose the Right Deposit Plugin A deposit and a payment plan solve different problems. A deposit collects an upfront amount with a balance due later. A payment plan divides the purchase into scheduled installments. We recommend choosing the collection method before choosing the plugin. A made-to-order item may suit one deposit and one final payment. A longer purchase arrangement may need several installments. These options provide different starting points. Option Useful starting point Main distinction WooCommerce Deposits Product deposits and scheduled payment plans Paid extension with documented WooCommerce workflows Deposits & Partial Payments for WooCommerce Basic partial-payment requirements Free entry point with its own settings and premium offering Similar names don’t mean identical behavior. The setup below follows WooCommerce Deposits, not every plugin that accepts partial payments. Set Up WooCommerce Deposits Storewide Install and activate the extension before configuring your payment rules. We recommend using staging for an existing shop so unfinished changes stay away from live customers. The WooCommerce Deposits setup documentation describes the storewide controls. Open WooCommerce > Settings > Products > Deposits. Set Default Enable Deposits to No, Yes Deposits are Optional, or Yes Deposits are Required. Choose Percentage, Fixed Amount, or Payment Plan under Deposit Calculation Method. When deposits are optional, set Default Payment Option to Pay Deposit or Pay in Full, then save. Choose optional deposits when customers can decide how much to pay initially. Required deposits suit products where every order needs the same upfront commitment. You can also use product-level settings for selected items instead of enabling deposits throughout the store. That keeps everyday purchases straightforward while giving expensive products a different payment path. The extension supports simple and variable products. Our guide to WooCommerce variable products covers product options and stock setup before you add another payment layer. Finally, make the terms easy to spot. Explain when the remaining balance is due, when work starts, and when the product ships. Build a Payment Plan With Clear Due Dates Set the Schedule Under Products Open Products > Payment Plans and create your plan. The first row is the deposit, paid Immediately. Each later interval runs from the previous payment, not from checkout. Six monthly installments therefore need six consecutive one-month intervals. The percentages must total 100%. Once the plan is saved, select it in the relevant deposit settings, including Default Payment Plan when configuring a storewide default. Follow the $48 Deposit Example The documented schedule takes 10% upfront, followed by six monthly payments of 15%. It runs for six months after the initial payment. The deposit amount is $48, or 10% of a $480 item. Each later installment is $72 before applicable tax or adjustments. Together, $48 plus six payments of $72 equals $480. Keep the customer’s Due today amount and Future payments clear. We recommend showing the schedule before checkout so the first payment doesn’t look like the full purchase price. Follow the Order Through Every Payment Understand the Deposit Statuses An unpaid deposit order starts as Pending Deposit Payment. After an online deposit payment, it changes to Partially Paid. Future payment orders remain Scheduled until their payment stage. When the payment plan finishes, the original order becomes Completed. Bank transfer, check, and cash on delivery need manual attention. These methods don’t automatically change the deposit order’s status. After receiving the money, set the order to Partially Paid. Match the payment to the order first. The order status helps your team follow the purchase, but it doesn’t replace transaction evidence. Separate Scheduled Payments From Automatic Charges WooCommerce Deposits doesn’t store card details or automatically charge the remaining balance. Customers still need to complete their follow-up payments. A scheduled installment creates a payment obligation. It doesn’t mean the customer’s card will be charged on its due date. For automatic recurring card billing, WooCommerce directs merchants toward WooCommerce Subscriptions with a compatible gateway. That’s a different setup, and the Deposits extension isn’t compatible with Subscriptions. We recommend deciding this early. Customer-paid installments and automatic renewals create different expectations, support needs, and collection workflows. Calculate Coupons and Tax Without Surprises Apply Discounts to the Correct Payments For payment plans, coupons are split across installments. With four payments of 25%, a $10 coupon reduces each payment by $2.50. Using the same $480 item, four equal installments would be $120 each. After that coupon, each becomes $117.50 before applicable tax. Tax then applies to the discounted taxable amount. Fixed and percentage deposits behave differently: the coupon discount is deferred to the final invoice. Tax is charged on the deposit at checkout, with the remaining tax collected alongside later payments. Future payment-plan installments retain the tax point and rate established when the order was placed. Fees aren’t split across payments. Distinguish Reminder Emails From Collection The documentation describes Email Reminders under Customer Notifications, with Reminder Timing controlling how far ahead of each payment the message goes. The Payment Plan Reminder Notification can be edited under WooCommerce > Settings > Emails. However, the WooCommerce Deposits product FAQ says built-in payment reminders aren’t available and suggests AutomateWoo or WooCommerce Zapier. These published descriptions conflict. An email setting still doesn’t create automatic collection. We recommend including reminder delivery and the customer’s payment link in your staging purchase test, rather than relying on an email preview alone. Know Which Product Combinations Are Supported WooCommerce Deposits works with simple and variable products, WooCommerce Bookings, and the Cart and Checkout blocks. Its listed incompatibilities include Pre-Orders, Subscriptions, Wishlists, Composite Products, Points and Rewards, Product Bundles, Grouped products, Extra Fees for WooCommerce, and Payment Gateway Based Fees. That matters before you build the offer. An expensive product bundle may look perfect for deposits, but an unsupported combination can block the arrangement you planned. Support for variable products also shouldn’t be confused with identical controls across competing deposit plugins. Each extension has its own configuration model. We recommend keeping your first setup focused: one supported product type, one payment arrangement, and clearly stated fulfillment terms. Add complexity after the basic journey works, including the customer’s account page and later payment orders. Test Stock, Reporting, and Checkout Before Launch A successful first payment is only part of the job. Test the deposit, a later installment, a failed payment, and a refund. Watch inventory throughout. The deposit should fit your stock-reservation policy, and later payment orders shouldn’t create an unexpected second stock reduction. Review reports alongside the original and scheduled orders. Keep collected money separate from the unpaid balance. Then reconcile those records with gateway transactions and bank payouts. For checkout, keep Cart, Checkout, and My Account outside shared full-page caching. Also test your actual payment gateway through the deposit and balance-payment journey. Our WooCommerce hosting launch checklist covers the foundation underneath those steps. We offer WordPress hosting for website management, while your deposit extension controls the payment arrangement. Choose hosting around your store’s checkout workload, background tasks, and support needs. Frequently Asked Questions Can Deposits Be Required for Selected Products? Yes. Use product-level deposit settings for selected items instead of requiring deposits storewide. This suits custom or made-to-order products while leaving ordinary products on full payment. Explain when work begins and when the balance becomes due. Can Deposits Be Used With WooCommerce Bookings? Yes. WooCommerce documents a deposit-required booking setup using WooCommerce Deposits. With Booking Persons, a fixed deposit can be multiplied by the number of people. Make that calculation visible so a group booking doesn’t produce an unexpected upfront amount. How Are Deposit Refunds Handled? Handle deposit refunds manually from the order’s Refund controls. Changing the status to Refunded doesn’t return money. A manual refund entry records the adjustment; it doesn’t transfer funds. Return the payment separately when needed and save the transaction reference. Review previous refunds, taxes, shipping, and stock before confirming. Partial refunds generally leave the existing status in place. Restock only when the goods belong back in saleable inventory. Can It Hold a Refundable Rental Security Deposit? The official extension isn’t designed for a refundable security deposit covering rental damage or property protection. Its deposit is a partial payment toward a purchase. A rental security hold needs a workflow built for that purpose. Make the First Payment Easy to Understand WooCommerce deposits work best when the upfront amount, later payments, and fulfillment terms are clear before checkout. Start with one supported product and follow the purchase through to its final payment. We recommend building around confirmed payments, accurate order records, and hosting that supports your checkout. Give customers a manageable first step while keeping your team clear on what happens next. […]
  • Set Up Cash on Delivery in WooCommerceWooCommerceSet Up Cash on Delivery in WooCommerceYou can set up WooCommerce cash on delivery through the built-in offline payment gateway, without installing another payment plugin. Activate it, write clear instructions, and connect it to the shipping methods your store supports. The important part is payment collection. A COD order can enter Processing before money changes hands, so your team needs a clear rule for confirming payment. We recommend starting with the core settings, then adding restrictions or fees only when your delivery workflow needs them. Key Takeaways Activate Cash on Delivery under WooCommerce’s offline payment settings, then configure the customer-facing wording. Treat Processing as a preparation stage for COD, not proof that payment has arrived. Use an extension for location restrictions, collection fees, or upfront deposits, and test the complete order journey. Enable WooCommerce Cash on Delivery The core gateway handles the basic setup and appears under WooCommerce’s offline payments settings. Your delivery team or collection service handles the actual payment. Switch on the payment gateway Open your WordPress dashboard and follow these steps: Go to WooCommerce > Settings > Payments > Take offline payments. Find Cash on Delivery and activate it. Click Manage to open its settings. Configure the fields, then click Save. WooCommerce’s Cash on Delivery documentation describes this setup path and the payment-confirmation workflow. Before accepting orders, decide who collects the money and how that collection reaches your order records. A payment option alone doesn’t create a collection arrangement. Configure the customer-facing fields The settings screen includes Enable COD, Title, Description, Instructions, Enable for shipping methods, and Accept for virtual orders. Leave the gateway active while you want COD available. Use Title for the payment option’s name at the payment step. “Cash on delivery” is clear and familiar. Description explains the option during checkout. State when payment is due and any collection conditions your service actually supports. Instructions provide the next steps after ordering, including on the order-received page and in applicable emails. Keep them consistent with the checkout description. Use Enable for shipping methods to limit COD to a shipping method your delivery service supports. Review Accept for virtual orders as part of your configuration, then save your changes before testing. Connect COD to Shipping and Test Checkout Payment availability and delivery availability need to agree. Otherwise, the store may offer an unsupported payment option. Match collection to the delivery area Use the shipping-method control to select delivery options where the shipping method can collect payment. Avoid routes that don’t support COD collection. Your shipping zone determines which delivery choices customers receive. Our guide to WooCommerce shipping zones helps you define those service areas before adding payment restrictions. Core COD settings and shipping-zone rules have different jobs. The zone establishes delivery availability; the gateway setting controls COD eligibility for selected shipping methods. Follow the customer’s complete journey Place a controlled order using an address your store serves. Read the payment title, description, confirmation page, and received email. If you use Checkout Blocks, repeat the test there. Then try an address or shipping selection that shouldn’t qualify. COD should follow your intended availability rules. Use a mailbox you control and keep staging notifications away from real customers. An email preview proves the design looks right, but it doesn’t prove checkout sent the correct message. Keep Cart, Checkout, and My Account outside shared full-page caching. Customer-specific totals need live session data. Add Restrictions and Fees With Smart COD Need more control? Smart COD for WooCommerce extends the existing gateway with availability rules and extra fees. It supports Classic Checkout and Cart and Checkout Blocks on WooCommerce 9.9 or newer. The same COD rules apply to both order flows. Restrict COD around fulfilment Smart COD restrictions can use shipping zone, shipping method, country, state, postal code, city, and user role. Postal-code rules support ranges. You can also target products in the cart, including variations, plus product categories and shipping classes. Each restriction can be switched to Enable or Disable. An active rule limits availability to the selected criteria. A disabled rule excludes the selected criteria. We recommend starting with one clear business rule. Limit collection to supported delivery areas, for example, rather than stacking several overlapping restrictions immediately. Test eligibility in both Classic Checkout and Checkout Blocks after each change. You’ll have a much clearer view of which rule controls the result. Choose how collection fees work It supports a fixed extra fee or a percentage of the cart amount. It also provides a separate local-pickup fee, a rounding option, and a tax option. Choose the structure around your collection costs. A fixed charge stays consistent; a percentage changes with the cart amount. Keep the fee label plain and make the extra fee visible before the customer submits the order. We recommend reviewing pickup separately so it doesn’t inherit an unsuitable delivery charge. Test the extra fee with COD selected, then switch payment methods. Confirm the fee and any tax treatment match the configuration. Handle COD Orders Without Confusing Payment and Delivery COD changes how you read the order list. Processing doesn’t automatically mean the customer has paid. Confirm collection before completion Core COD orders enter Processing while payment is still outstanding. Confirm that payment was collected before setting the order to Complete. Track collection, payment confirmation, and status changes as connected steps in the COD order lifecycle. Match the collection record to the correct order. Record who collected payment, the amount, and a useful collection reference in a private order note. Then update the status when the payment and fulfilment records support it. Our guide to shipping labels and order updates explains why postage, tracking, and completion should remain connected but separate. There is an automated exception: payment through the WooCommerce mobile app with a card reader for In-Person Payments marks the order Complete at payment. Keep customer messages accurate A COD processing email shouldn’t claim that payment has cleared. It should explain that the order is being prepared and when payment is expected. Edit existing notifications under WooCommerce > Settings > Emails. Choose the relevant message, select Manage, and update the available wording. Changing an email template doesn’t create a new status trigger. Custom notifications may need an extension or developer work. Don’t move an unpaid order forward just to send an email. Status changes can also trigger stock updates and connected tools. Understand COD Protection Before Enabling It The plugin’s optional protection features deserve a separate decision. Availability rules and shared delivery-history checks solve different problems. Keep data sharing deliberate COD Protection and data sharing are optional and off by default. If the external service is unavailable, COD remains available. That means an enabled protection service isn’t a guaranteed block during an outage. Your own fulfilment and payment-reconciliation process still matters. We recommend choosing the protection policy deliberately, rather than switching on every option during installation. Keep your team clear about which orders need review and why. Apply history thresholds correctly The successful-history threshold can be set between 50% and 100%, with 100% as the default. Pending orders don’t enter the calculation. The plugin’s example is straightforward: nine completed orders and one qualifying cancellation satisfy a 90% threshold. A cancellation affects eligibility only when it meets fulfilment checks. Without a recognized tracking integration, an untracked fallback applies after at least 24 hours. Any supplied source status must indicate fulfilment. The distinction matters. A qualifying cancellation carries different weight from an order that never reached the relevant fulfilment stage. Avoid treating every cancelled order as the same delivery outcome. Back Up Settings and Keep Customizations Maintainable Its Settings backup exports the plugin’s Free settings as a JSON file. The preview expires after ten minutes, and files exported by another store aren’t accepted. Treat this as a backup of those settings, not a portable copy of your entire store configuration. Keep a full website backup alongside it. For developer-led changes, the plugin provides three filters: wc_smart_cod_fee changes the extra fee, wc_smart_cod_available changes availability, and wc_smart_cod_fee_title changes the fee label. We recommend using the settings interface first. Add custom code only for a rule the interface doesn’t cover. After changing rules or code, repeat the order test. Include the fee label, totals, eligibility, saved order, and received email. A correct payment-option display is only one part of a working order journey. Frequently Asked Questions Does the built-in COD gateway add collection fees? The basic gateway covers enabling COD, payment-option wording, and shipping-method selection. For additional features, WooCommerce points to the Advanced Cash on Delivery with Fee extension. The plugin is another option for restrictions and fees. Choose around the rule your store needs rather than installing multiple extensions that control the same gateway. Can part of the order be paid online first? Yes. Smart COD PRO supports partial COD: collect a fixed amount or percentage online upfront, then leave the remaining balance payable on delivery. Explain both amounts clearly before the customer orders. Your fulfilment team also needs to distinguish the deposit already received from the balance still due. Why isn’t COD appearing at checkout? Start with the saved gateway setting, the customer’s shipping selection, and any extension restrictions. Compare them against the address and cart you’re testing. If the delivery option itself is missing, our guide to troubleshooting WooCommerce shipping rates covers that part of the setup. Fix delivery availability before changing unrelated payment settings. Make Every COD Order Easy to Follow A dependable WooCommerce cash on delivery setup connects payment instructions, delivery eligibility, and confirmed payment. The gateway makes ordering possible; your collection process keeps the order record accurate. Start with the built-in settings and add only the controls your store needs. Then test the complete journey, including the customer email and final payment record. Clear instructions help buyers order confidently. Accurate statuses help your team finish the job. […]
  • WooCommerce Fraud Prevention Before FulfillmentWooCommerceWooCommerce Fraud Prevention Before FulfillmentStop fraudulent orders before fulfillment by filtering bots, using payment-gateway fraud controls, and holding suspicious purchases for review. Effective WooCommerce fraud prevention protects your stock and revenue without putting every genuine customer through extra hoops. A burst of failed payments can look alarming, but blocking everyone creates another problem: lost sales. We recommend a layered defense, starting with the signals that tell you whether you’re facing card testing or a checkout fault. Key Takeaways Stop automated attempts at the edge, then add gateway checks and checkout bot protection. Keep suspicious orders away from shipping, downloads, and other automatic fulfillment until review is complete. Confirm whether money moved before cancelling, refunding, or asking a customer to pay again. Spot Card Testing Before Orders Ship Recognize the warning signs Carding attacks use your store to test stolen credit cards, often through small fraudulent orders for your cheapest product. Scammers use these purchases to find which cards still work. Watch for many low-value orders within minutes, unusually high declines, and random or mismatched names, emails, and addresses. Repeated attempts from one IP address are another clue. Processor fraud reports and chargebacks can confirm that the problem has already reached successful payments. WooCommerce’s card-testing guidance covers these automated attacks. The pattern matters more than one failed purchase. Separate fraud from checkout faults Open the affected order notes, then go to WooCommerce > Status > Logs and inspect the gateway log. Compare timestamps, decline reasons, transaction IDs, and repeated attempts. Timeouts, credential errors, or failed webhooks need a different fix than stolen-card testing. A shopper can also create duplicate orders by refreshing a stalled checkout. Our guide to troubleshooting failed WooCommerce payments helps separate payment failures from order-record problems before you block genuine buyers. 1. Start WooCommerce Fraud Prevention at the Edge A web application firewall at the edge stops unwanted traffic before it reaches your hosting resources or payment processing. We recommend starting with a Cloudflare Managed Challenge for browser visits to checkout. A sitewide High security setting can force legitimate shoppers through interactive challenges and lower your conversion rate. Keep the first rule narrow. Add rate limiting where logs show repeated abuse. Set limits around your store’s normal checkout activity rather than borrowing an arbitrary number. Don’t apply interactive challenges blindly to WooCommerce AJAX requests, Store API calls, or payment webhooks. Those requests need to work without a person solving a challenge. Edge protection reduces bot traffic. Your gateway still needs its own rules for payment risk. 2. Put Payment-Gateway Controls to Work Use card and address checks intelligently If you accept Stripe payments, use Stripe Radar alongside CVC or CVV and address verification checks. Each payment gateway may offer its own fraud controls. A failed security-code check deserves attention. An unavailable address check isn’t the same as a confirmed mismatch, though. Address verification coverage varies, so blanket rejection can catch honest customers. We recommend combining signals instead of treating one missing result as proof of fraud. Keep the reason for each block visible in your review process. Add authentication and control capture 3D Secure can ask the cardholder to authenticate a payment when additional reassurance is needed. Use your gateway’s supported risk-based settings rather than forcing every buyer through the same extra step. Where your gateway supports separate authorization and capture, manual capture can give you a review window before collecting funds. Authorization alone doesn’t approve fulfillment. Connect the payment decision to your shipping, download, or service-delivery workflow. A fraud warning that arrives after an automatic delivery has limited value. 3. Add a Low-Friction Human Check Cloudflare Turnstile checks whether a visitor appears human, usually without presenting a puzzle. Its keys are free, and your site doesn’t need to run on Cloudflare’s network. Use a WooCommerce-compatible integration that supports your actual checkout, whether that’s the Checkout block or a classic layout. The integration must validate the result server-side. A visible widget alone isn’t protection. The Turnstile configuration guide explains obtaining the site and secret keys through a free Cloudflare account. Test mobile checkout, express payment buttons, and failed-payment recovery after enabling it. Compare reCAPTCHA with Turnstile and check whether each CAPTCHA adds friction. Choose low-friction checks over puzzle-heavy CAPTCHA options when they stop the same abuse. Add this layer separately from major gateway changes. That makes any new checkout problem easier to trace. 4. Score Orders Before Releasing Fulfillment Let weighted rules guide review Anti-fraud plugins often use a 0-to-10 risk score. Rules assign weight to signals such as first-time purchases, rapid order generation, and duplicate orders. The scale isn’t universal. Stripe’s risk settings use a separate 0-to-99 score, with higher values indicating greater risk. Don’t copy thresholds between systems. We recommend starting with a conservative risk threshold that sends uncertain orders to review rather than rejecting them automatically. Keep provider defaults as your starting point, then adjust using confirmed fraud and legitimate orders that were wrongly flagged. Treat location mismatches as clues Geolocation checks compare the IP address country with billing or shipping details. Proxy and VPN detection can add another warning signal. These checks can trigger false positives for travel, gifts, workplace networks, and privacy tools. Treat a mismatch as a clue, not proof of fraud. Allowlist reviewed repeat customers where appropriate. Keep IP exceptions narrow because shared networks can contain many unrelated users. Trusted status should reduce unnecessary review without switching off payment security. An order-level warning only protects you if fulfillment waits for the decision. Confirm that your shipping and download integrations respect the hold. Compare Anti-Fraud Tools by Job and Cost Choose the missing layer and add an anti-fraud plugin only if it fills a gap, rather than installing overlapping tools. ToolMain controls or serviceCost modelDotstore Fraud Prevention for WooCommerceBlocks IPs, states, ZIP codes, disposable email domains, and phone numbersFree core; paid Pro featuresYITH WooCommerce Anti-FraudChecks geolocation, proxies, email domains, and billing-versus-shipping mismatches; configurable threshold actionsPaid pluginMaxMind minFraudExternal fraud intelligence through an integrationUsage-based, per transactionFraudLabs ProTransaction screening for stores of different sizesFree low-volume tier; paid monthly-volume tiersSignifydOrder screening with a financial guarantee on approved orders, depending on planPaid serviceNoFraudAI screening with human review and a pre-gateway integration optionPaid service Dotstore suits stores needing direct blocking rules. YITH adds configurable risk actions. FraudLabs Pro gives low-volume stores a free screening option. The MaxMind integration setup requires a MaxMind account, user ID, license key, and enabled device tracking. Timing matters as much as features. Gateway-native tools assess payments inside their payment flow. WooCommerce plugins may evaluate orders after creation, while NoFraud offers a pre-gateway option. Pre-gateway screening can reject a request before it reaches payment processing. Post-order scoring needs a reliable fulfillment hold. A compatible gateway and a clear decision point matter more than a long feature list. 5. Review Suspicious Batches Before Taking Action Pause affected fulfillment first, including warehouse exports, automatic downloads, gift-card delivery, and any external service that acts on an order. During manual review, match each WooCommerce order to its gateway transaction. Keep it on hold until you confirm payment and decide whether to release fulfillment. A Failed status doesn’t prove that no money moved. For confirmed fraudulent captured payments, early cancellation and refunds are usually cheaper than waiting for chargebacks. Where supported, void an uncaptured authorization instead of issuing a refund. Our WooCommerce refund workflow explains payment verification and order updates. Don’t refund an entire batch solely because the orders look similar. Separate confirmed abuse from customers caught in the same period. After review, record the decision and its reason. Those outcomes give you useful evidence for adjusting rules without making checkout harder for everyone. Keep Checkout Stable While Adding Protection We recommend testing new security integrations on staging with gateway test mode first. Change one layer at a time, then test successful payments, controlled failures, and order-status updates. Keep Cart, Checkout, My Account, and WooCommerce AJAX requests outside caching. Don’t challenge payment callbacks. Security rules that break those requests can create the same failed-order pattern you’re trying to stop. Our WooCommerce hosting launch checklist helps you plan resources, HTTPS, backups, and safe testing. Ready to strengthen the foundation? Explore our WordPress hosting plans. Hosting supports your store’s operation; transaction screening still belongs in your fraud-prevention setup. Frequently Asked Questions Should guest checkout be disabled? It can reduce spam orders, but adds buying friction. Under WooCommerce > Settings > Accounts & Privacy, uncheck “Allow customers to place orders without an account.” Newer versions may label this “Enable guest checkout.” WooCommerce’s Accounts and Privacy settings describe the option. We recommend targeted bot protection first because bots can also create accounts. Do honeypots and login limits stop payment fraud? They address related abuse. Honeypot fields are hidden from people but expose bots that fill them. Failed-login limits block repeated brute-force attempts after a configured number of tries. These controls help protect forms and accounts. They don’t replace gateway screening, card checks, or fulfillment review. Protect the Sale Before Releasing the Order WooCommerce fraud prevention works best when each layer has a clear job: filter traffic, assess payment risk, and hold uncertain orders. Keep fulfillment approval tied to the fraud decision. That protects goods and digital deliveries while leaving genuine customers a straightforward path to purchase. Start with the layer your logs show is missing. Add it carefully, test the buying journey, and keep your store ready for real sales. […]
We use cookies so you can have a great experience on our website. View more
Cookies settings
Accept
Decline
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Who we are

Our website address is: https://zadic.net.

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection. An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year. If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser. When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed. If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website. These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue. For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where your data is sent

Visitor comments may be checked through an automated spam detection service.
Save settings
Cookies settings