Back to Community
Home / Community / Plugin → Woocommerce tax (formerly woocommerce shipping & tax)

Why WooCommerce Automated Tax Returns $0.00 (And How to Fix It)

33 threads Sep 9, 2025 Plugin → Woocommerce tax (formerly woocommerce shipping & tax)

Content

One of the most common issues reported with the WooCommerce Tax plugin (formerly WooCommerce Shipping & Tax) is automated tax calculations returning $0.00 when a tax amount is expected. This guide will walk you through the primary reasons this happens and the steps you can take to resolve it.

Understanding the Core Problem: "has_nexus": false

Based on numerous community reports, the root cause of a $0.00 tax calculation almost always appears in the plugin's log files. When you enable logging (WooCommerce > Settings > Tax > Tax Options > Enable Logging), you'll see entries like this:

Received: {"tax":{"amount_to_collect":0,"freight_taxable":false,"has_nexus":false,"order_total_amount":120.75,"rate":0,"shipping":71.75,"tax_source":null,"taxable_amount":0}} (WCS Tax)

The key phrase here is "has_nexus": false. This means the TaxJar API, which powers the automated calculations, does not recognize that your business has a tax obligation (or "nexus") in the customer's state. Without a recognized nexus, the API returns a zero tax rate.

Why Does This Happen? Common Causes

  1. Incorrect Store Address Settings: The plugin determines your nexus states primarily based on your shop's base address. If this address is not set correctly in WooCommerce > Settings > General, the API cannot establish where you have a tax presence.
  2. Jetpack Connection Issues: Automated taxes require a stable connection to the WooCommerce Services servers via Jetpack. If this connection is broken, incomplete, or experiencing issues, the API calls will fail or return incorrect data.
  3. API Request Formatting Errors: Sometimes, the data sent to the TaxJar API is malformed. Logs might show 400-level errors (like a 406 error) indicating a "Bad Request." This is often due to missing or incorrectly formatted address data being passed from the checkout page.
  4. Cached Tax Rates or Errors: The plugin caches tax rates and even errors to improve performance. If an initial error occurred, you might see a log entry like "Retrieved the error from the cache," meaning subsequent requests are serving the cached error instead of making a new API call.
  5. Product Tax Exemption Settings: If you are using product-specific tax codes for exempt items (like certain food products), an incorrect Tax Status or Tax Class setting on the product edit screen can lead to unexpected results, even in states where you have nexus.

Step-by-Step Troubleshooting Guide

Follow these steps to diagnose and fix the problem.

Step 1: Verify Your Store's Base Address

This is the most critical step. The plugin uses this address to determine your primary nexus.

  • Navigate to WooCommerce > Settings > General.
  • Ensure the "Store address" and especially the "Country/State" fields are accurate and reflect the physical location of your business.
  • Save changes.

Step 2: Enable and Check the Tax Logs

The tax logs are your best tool for diagnosis.

  • Go to WooCommerce > Settings > Tax > Tax Options.
  • Check the box for "Enable Logging" and save changes.
  • Attempt a test checkout that should trigger tax calculation.
  • Return to WooCommerce > Status > Logs and select the latest "wc-services-taxes-" log file from the dropdown.
  • Look for the "Received" line in the log. If you see "has_nexus": false for a state where you should be charging tax, your base address is likely the issue. If you see an HTTP error code (like 400 or 406), there is a data formatting problem.

Step 3: Verify Your Jetpack Connection

A stable connection is mandatory for the API to function.

  • Ensure the Jetpack plugin is installed, activated, and properly connected to a WordPress.com account.
  • Check that your site can communicate with WordPress.com services without any firewall or security plugin interference.

Step 4: Clear Cached Data

If your logs show that errors are being retrieved from the cache, you need to clear them.

  • Install a plugin like "WP Rocket" or "W3 Total Cache" and use its functionality to clear all cached data.
  • Alternatively, your theme or host may have a caching mechanism; consult their documentation on how to clear it.
  • After clearing the cache, perform another test checkout to force a new API call.

Step 5: Check Product-Level Tax Settings

If tax calculates for some products but not others, or seems incorrect for exempt items:

  • Edit the product in question in WordPress.
  • In the Product Data > General tab, ensure the "Tax status" is set correctly (e.g., "Taxable" vs. "None").
  • If using a special tax class for exemptions, ensure it is selected in the "Tax class" dropdown.

When to Seek Further Help

If you have worked through all these steps and the issue persists, carefully review your tax logs for any specific error messages. The details in these logs are the most valuable information for troubleshooting. You may find it helpful to search for the exact error message online or discuss it in community forums where other users may have encountered the same problem.

Remember, tax laws are complex and vary by location. It is always a good idea to consult with a tax professional to ensure your store is configured to comply with the regulations that apply to your business.

Related Support Threads Support