WooCommerce REST API Keys: Limit Access Safely
You can create WooCommerce REST API keys under WooCommerce > Settings > Advanced > REST API, then select Read, Write, or Read/Write access levels. We recommend giving each integration only the access it needs, using a dedicated WordPress user where practical....
WooCommerce Webhooks Not Firing? Here’s How to Fix Them
WooCommerce webhooks may stop firing because they’re paused, disabled, set to the wrong event, or unable to reach the receiving service. The fastest fix is to follow the evidence: check the webhook status, match the event, and read the delivery log. Your store...
Recover WooCommerce Carts With Follow-Up Emails
WooCommerce abandoned cart emails give shoppers a clear way to return to items they left behind. To send them, you need a recovery tool that captures the cart, an email address, and a follow-up workflow. The details matter. A reminder can’t help if it lands in...
Customize the WooCommerce Thank You Page After Purchase
A customized WooCommerce thank you page gives customers a clear receipt, useful next steps, and a reason to feel good about their purchase. You can make changes with the WordPress Site Editor, an extension, or custom development, depending on your store’s setup....
Set WooCommerce Minimum and Maximum Order Quantities
A WooCommerce minimum order quantity lets you require customers to buy a certain number of items. A maximum sets the upper limit. To enforce either rule, you’ll generally need an extension. The right limits can make packing easier and protect stock during busy...What's New?
Domains / 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. [...]
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 / 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. [...]
WooCommerceSet 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. [...]
WooCommerceWooCommerce 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. [...]
WooCommerce / WordPressPrint WooCommerce Shipping Labels and Update OrdersYou can print WooCommerce shipping labels from an order, then update its status when fulfillment is finished. The important part is keeping postage, tracking, and order status connected without treating them as the same thing.
We recommend starting with one label-printing tool and clear rules for customer updates. That keeps your packing process easier to manage and helps prevent duplicate notifications. First, choose the tools that match how your store ships.
Key Takeaways
Use a label-printing plugin for postage, and configure shipping rates charged to customers separately.
Enter accurate product weights, package dimensions, and origin details before requesting carrier quotes.
Add tracking before sending completion emails, and change statuses only when the fulfillment record supports the update.
Compare Shipping Plugins by the Job They Do
Shipping plugins handle different jobs. Some calculate what customers pay. Others buy postage, print labels, and pass shipment information back to your store.
Here's how the main options compare.
Plugin or platformBest forTrade-offWooCommerce ShippingDiscounted labels inside the WooCommerce dashboardLive rates at the point of purchase require a separate setupShipStationImporting orders across sales channels and sending tracking to customersRequires a separate subscriptionFlexible ShippingCheckout rates based on weight, cart total, and other conditionsFree base plugin and PRO version; doesn't print labels itselfWooCommerce Table Rate ShippingRate tables using weight, price, item count, shipping class, and destinationPaid WooCommerce Marketplace extensionPacklink PRO, Sendcloud, Easyship, BoxtalMulti-carrier labels created from synced ordersCarrier availability depends on the seller's countryELEX USPS (WooCommerce USPS Shipping Method)Live USPS rates at checkoutUSPS only; the paid version adds label printing
The practical choice starts with your biggest task. For dashboard postage, we recommend considering the official WooCommerce Shipping plugin. It offers discounted labels and live label-rate comparison without requiring separate carrier accounts.
ShipStation makes more sense when orders arrive through several sales channels. Flexible Shipping and Table Rate Shipping address customer-facing pricing rules instead. Choose around the work you need done, rather than installing several tools with overlapping features.
Before relying on Sendcloud's synced-order label workflow, confirm that its carriers are available in your country.
Print WooCommerce Shipping Labels From an Order
Install and activate WooCommerce Shipping as your shipping label plugin, then complete its connection, origin, and payment setup. With that foundation ready, you can print shipping labels from the order.
Open WooCommerce > Orders and select the order you want to fulfill. Review the purchased items and delivery address.
In the Shipping Label section, click Create shipping label. Some versions display the plural wording, "Create shipping labels."
Verify the ship-from address and destination. Enter the package weight and dimensions, including the packaging rather than relying only on product weight.
Compare available carrier services. Options can include USPS, UPS, or DHL Express, depending on the origin and shipment.
Select the service, pay for the label, then print it or save the PDF.
The official WooCommerce Shipping documentation describes the order-page label workflow.
Before attaching the label, match it to the order and parcel. Keep the carrier, service, and tracking number associated with the correct purchase.
Pay particular attention when several parcels are waiting together. A correctly printed label still creates trouble if it goes on the wrong box.
Creating postage also doesn't automatically tell you which order status is appropriate. Your store's fulfillment process should control that decision.
Update Order Statuses When Fulfillment Changes
An order status tells your team what work remains. Carrier tracking tells customers where the parcel is. We recommend keeping those messages separate.
Keep Processing Until Fulfillment Is Finished
For a typical paid physical order, Processing means payment has arrived and fulfillment is next. Printing a label can happen while packing is still underway.
When fulfillment is finished, open the order, choose Completed in the Status dropdown, and click Update. Completed describes your store's fulfillment milestone, not proof that the customer received the package.
Our guide to WooCommerce order statuses explains when each status fits. Keep order notes aligned with the action taken so another team member can follow the record.
Add Tracking Before Completion Emails
Save the correct carrier and tracking number before completing the order. That gives a compatible tracking integration the information it needs to include a shipment link in the completion email.
A purchased label doesn't prove the carrier has received the parcel. Avoid wording that promises movement or a delivery date before tracking supports it.
For partial shipments, don't complete the entire order while items remain unfulfilled. If a shipping integration changes statuses automatically, make its trigger match your fulfillment rule. One deliberate update is easier to trust than several plugins changing the same order.
Set Checkout Rates and Free Shipping Rules
WooCommerce core includes Flat Rate, Free Shipping, and Local Pickup through shipping zones. It doesn't request live carrier rates by itself.
Build Zones Around Accurate Product Data
Open WooCommerce > Settings > Shipping > Shipping zones. Define destinations, add eligible methods, and place narrow local zones above broader regions. WooCommerce uses the first matching zone.
Create zones for the international destinations you serve, and verify that your chosen methods cover them.
Set the store origin address, assign shipping classes where useful, and enter any credentials required by your carrier extension.
Accurate product weights are essential for weight-based shipping and live carrier quotes. Many carriers also need dimensions, and missing data can produce an inaccurate quote or no quote at all.
Choose a Minimum Your Margins Can Support
For free shipping above an order value, add Free Shipping to the relevant zone. Select its minimum-order requirement and enter your chosen amount. Keep a flat or table rate available for smaller orders.
Use recent orders and actual delivery costs to choose that minimum. Include packaging, preparation costs, expensive destinations, and products that cost more to send.
There isn't one minimum that suits every store. Test baskets below, at, and above yours before promoting it. State the eligible destinations and any coupon requirement clearly.
For a fixed delivery charge, WooCommerce's Flat Rate settings support per-order, per-item, and shipping-class calculations.
Test the Shipping Setup Before Going Live
A saved setting is only the starting point. We recommend testing the complete purchase path, from order placement through payment, label creation, status change, and customer notification.
Run Orders Through Every Shipping Zone
Use representative products and addresses, including heavy items and costly destinations. Compare the checkout quote with the carrier's rate for the same origin, destination, package, and service.
Use this short setup checklist:
Confirm each destination matches the intended zone and has an eligible shipping method.
Test guest orders, mobile orders, and baskets with different shipping classes.
Open the customer email and follow its tracking link to the correct shipment.
Our WooCommerce order tracking setup guide covers the connection between shipment details and customer-facing updates.
Avoid Duplicate Rates and Stale Checkout Totals
Two plugins can expose overlapping shipping methods or send duplicate updates. Give each integration a clear job, and remove redundant methods.
Show delivery costs early enough for customers to make an informed decision. Plan for returns and decide how return labels will be handled before one arrives.
Keep Cart, Checkout, and My Account outside shared full-page caching. Retest shipping after plugin updates or carrier API changes, especially when quotes disappear or totals stop refreshing.
Frequently Asked Questions
Are Label Rates the Same as Checkout Rates?
No. The customer-facing rate determines what your customer pays for shipping. Label rates determine what your store pays for postage.
Those amounts can differ when you offer flat-rate or free shipping. Compare both when reviewing margins so a convenient checkout offer doesn't leave delivery costs uncovered.
Where Can Shipping Method Names Be Changed?
Open WooCommerce > Settings > Shipping > Shipping zones, select the zone, and edit the method. Change its customer-facing title, then save.
Use clear names such as "Standard Delivery" or "Local Pickup." A friendly title helps customers choose, but it doesn't change the method's pricing or eligibility.
Can an Existing UPS Account Be Used?
Yes. WooCommerce documents an own-account UPS integration within WooCommerce Shipping.
Its label window displays available rates after the origin and destination addresses are entered and verified. This is an optional account connection for label purchasing, separate from configuring live carrier rates at checkout.
Keep Fulfillment Clear as Your Store Grows
A dependable shipping workflow has a clear sequence: calculate the charge, prepare the parcel, create postage, and update the customer. Keep order statuses tied to completed work, and your records become much easier to follow.
At ZADiC, we recommend pairing that workflow with hosting that fits your store's workload. Our WordPress hosting and Web Hosting Plus give you options for the website supporting your store's purchasing experience.
Ready to put the pieces together? Start with one shipping tool, run a complete test order, and choose the ZADiC hosting plan that fits your store's next stage. [...]
WooCommerceSet Up WooCommerce Order Tracking Customers Can UseTo set up WooCommerce order tracking, add shipment details to each order, then make those details available through emails and customer accounts. A tracking extension connects the order to the carrier, so customers can follow their package without contacting you.
We recommend starting with the simplest setup that fits your shipping workflow. First, separate the order status WooCommerce manages from the delivery updates your carrier provides.
Key Takeaways
WooCommerce order status describes your store's workflow; shipment tracking follows the package.
Add tracking details before completing an order so the completion email can include the tracking link.
Give customers a tracking page, account access, or an email link, and test the complete journey before launch.
Choose How Your Store Will Handle Tracking
Start With the Shipping Tools Already Installed
WooCommerce records statuses such as Processing and Completed, but those labels don't explain where a package is travelling. For carrier tracking, you need shipment information connected to the order.
If you buy labels through WooCommerce Shipping, tracking details may already appear in your label workflow and order record. That can remove the need for another extension.
We recommend reviewing that existing workflow before installing anything. One working tracking system is easier to maintain than overlapping plugins that send duplicate updates.
Add an Extension for External Shipments
If you use third-party shipping, an extension gives you a place to attach the carrier and tracking number to each order.
Shipment Tracking is a straightforward option for linking shipments to WooCommerce orders. Other tools add CSV imports, branded tracking pages, or connections to tracking services.
Choose based on the work you need to handle. A store entering a few tracking numbers manually has different needs than a fulfillment team importing shipments in bulk.
Add Tracking Details to a WooCommerce Order
Install and activate your chosen extension first. These steps follow the Shipment Tracking documentation, rather than WooCommerce core alone.
Enter the Carrier and Tracking Number
Open WooCommerce > Orders and select the order you're shipping.
Find the Shipment Tracking panel in the order sidebar.
Choose a shipping carrier from the list.
Enter the tracking number exactly as supplied by the carrier.
Set the shipping date if needed, then click Save Tracking.
For supported carriers, the extension builds the tracking link automatically. Keep the number intact, including any letters and leading zeros.
Shipment Tracking supports multiple tracking numbers on one order. Add a separate tracking entry for each package rather than squeezing several numbers into one field.
Use Custom Provider for an Unlisted Carrier
Choose Custom Provider when your carrier isn't listed. For an unlisted custom carrier, enter its name and full tracking URL.
Use the carrier's working shipment link, including the tracking number where its URL requires one. A general homepage sends customers searching again.
Open that saved link before sending it. It should lead to the intended shipment without requiring your staff login.
Compare Tracking Extensions by the Work They Save
Carrier totals are vendor claims, not a shared measurement. Choose an extension based on your workflow first.
These options cover different fulfillment needs.
ExtensionVendor-listed featuresPractical fitShipment TrackingAutomatic carrier links, custom providers, and multiple tracking numbersAdding parcel links to orders and customer updatesYITH WooCommerce Order & Shipment Tracking489 carriers, CSV import, and a shortcode tracking pageImporting shipments and offering customer lookupTrakooMore than 80 carriers, custom carriers, and CSV bulk add/exportManaging tracking records in batchesWooCommerce Order Tracker by WP Swings400+ carriers and DHL On Page TrackingBuilding an on-site tracking experience
The useful difference is how each tool fits your daily work, not which carrier count looks biggest.
Shipment Tracking's carrier options include Australia Post, Canada Post, DHL, DPD, FedEx, Royal Mail, TNT Express, UPS, and USPS.
YITH CSV imports require the carrier code in your file to match a supported code. A differently typed carrier name can interrupt an otherwise tidy import.
Trakoo advertises premium connections that let stores use a tracking service such as TrackingMore, 17Track, EasyPost, AfterShip, or TrackTry. Its SMS options use Twilio, Nexmo, or Plivo. These connections suit a different job than simply adding a carrier link.
Keep the choice focused on your needs: manual entry, bulk imports, on-site tracking, or connected notifications. Install the extension for the feature you'll use.
Give Customers a Clear Tracking Page
Understand the Built-In WooCommerce Shortcode
WooCommerce includes , which creates an order lookup form. Customers enter their order ID and billing email address.
It reports order information, but it doesn't create carrier tracking data by itself. A tracking extension must supply the shipment details you want customers to access.
To publish the basic lookup page:
Go to Pages > Add New and name the page "Track Your Order."
Insert a Shortcode block and add .
Publish the page and add a clear "Track Your Order" link to a useful navigation area.
Test the shortcode with a valid order ID and its matching billing email.
Keep the form easy to find, especially for guests who don't have an account.
Use Extension Shortcodes for Shipment Details
YITH provides a shortcode-based tracking page where customers enter their email and order ID to view shipping status.
WP Swings lists and for its tracking experience. Its settings are under WooCommerce > Settings > Track Your Order.
Use the shortcode belonging to the extension you've installed. Adding several unrelated tracking forms creates confusion.
Logged-in customers can find shipment details in My Account. Shipment Tracking can also display tracking information in My Account order details. Test My Account > Orders > View with a customer account, not your administrator session.
Send Tracking in the Right Order Email
Save the tracking information before changing the order status to Completed.
With Shipment Tracking or YITH configured and the relevant notification for tracking emails enabled, marking the order Complete sends the Completed Order email with its tracking link. The saved shipment details are available when the message is generated.
That sequence matters. Completing the order first can send an email before you've attached the number.
A Completed order records your store's fulfillment status. It isn't proof that the carrier has delivered the package.
Keep status changes tied to the real order workflow. Changing a status simply to force an email can also trigger inventory changes or extension actions. If an extension adds a custom order status, test its email and inventory triggers before using it.
Our guide to status-based WooCommerce order emails explains the difference between editing a message and changing its trigger. A redesigned template alone doesn't create a new notification.
Keep Store Status and Carrier Updates Separate
WooCommerce's order status tells you whether a purchase is awaiting payment, processing, or completed. The carrier reports shipment events and any estimated delivery date it makes available.
We recommend keeping your wording equally clear. A shipping label doesn't prove the carrier has received the parcel. Don't promise a delivery date based only on the label's creation.
If tracking opens the wrong shipment, compare the saved provider, number, and custom link. If order details belong to another customer, stop and correct the order association before sending another update.
For troubleshooting, keep one order as your reference. Record its ID, status, shipping details, and timestamps. Changing several orders and settings at once makes the fault harder to follow.
Connect Fulfillment Systems Without Breaking Order Storage
Add Tracking Through the REST API
Manual entry works until another system already holds the information. Warehouses, shipping platforms, and fulfillment services can send tracking data back through Shipment Tracking's WooCommerce REST API support.
WooCommerce documents how to add shipment tracking programmatically. Your integration needs to associate the provider, tracking number, and optional shipped date with the correct order.
We recommend handling retries carefully. Repeated shipment messages shouldn't create duplicate tracking entries or repeated customer notifications.
Prepare Integrations for HPOS
High-Performance Order Storage, or HPOS, keeps order data in dedicated tables. Custom integrations should use WooCommerce's order APIs instead of assuming every order lives in WordPress post metadata.
Before changing order storage, back up the store and test tracking, payments, emails, and fulfillment on staging.
Complete order synchronization before switching an existing store. Compatibility mode can support the transition, but synchronized data isn't a separate backup. Keep an independent recovery point.
Give Tracking a Dependable Hosting Base
Tracking adds account requests, notifications, and sometimes background imports. Your hosting needs room for that work alongside checkout.
At ZADiC, our WordPress hosting plans start at $9.99 per month. We recommend choosing around your catalog, traffic, and order workload.
For a growing store, our shared hosting and Web Hosting Plus comparison helps you choose the next level of capacity.
Hosting won't correct a mistyped carrier number. It gives your store the resources to run the tracking system you've configured.
Frequently Asked Questions
Why Aren't Order Confirmation Emails Arriving?
Start with the affected order's status, billing email, and order notes. Then open WooCommerce > Settings > Emails and inspect the expected notification.
If the trigger happened and sending succeeded, investigate delivery records, spam filtering, and email authentication. Repeatedly changing the order status can create extra problems.
Can Tracking Be Added After an Order Is Completed?
Yes, you can add shipment details to an existing order. However, saving them doesn't mean the original Completed Order email will be sent again automatically.
Test your extension's notification behavior before relying on a second customer update.
Can One Order Have Several Tracking Numbers?
Yes. Shipment Tracking supports separate tracking entries for split shipments.
Keep each carrier and number together so customers can follow every package independently.
Make Every Shipment Easier to Follow
Useful tracking starts with accurate shipment details saved before the customer notification goes out. Give customers a working carrier link and a clear place to find it again.
We recommend finishing with one controlled order test. Follow the email, account page, and tracking link as a customer would, then put the workflow to work. [...]