Resolving WooCommerce critical errors and tax settings with WooCommerce Shipping & Tax and Stripe plugins in WordPress

Summary:
A WordPress eCommerce site running WooCommerce encountered a critical error stemming from a stuck database migration tied to the WooCommerce Shipping & Tax plugin. Additionally, there were concerns over Stripe checkout configuration and multi-state sales tax settings. This case study details how Freshy resolved the technical issues and improved store operations.

Issue background

The client reported three issues affecting their WooCommerce store:

  1. A stuck WooCommerce Shipping & Tax database migration, resulting in a critical error.
  2. The site was still using Stripe’s legacy checkout.
  3. Tax was only being calculated for Virginia (VA), and not for other states.

The migration issue initially prevented the “Orders” admin page from loading, and the errors were severe enough to require immediate action.

Diagnosis

Freshy began by applying a temporary code patch directly within the woocommerce-shipping/src/Migration/MigrationController.php file to suppress the error and allow backend access. The script was hanging during the migration process, likely due to plugin version mismatches or data conflicts.

For the checkout issue, the Stripe settings were still configured to use the older “legacy” version rather than the newer streamlined checkout experience.

The tax issue arose because automated tax calculation was only working for VA. This indicated that WooCommerce’s Automated Taxes feature, powered by Jetpack and WooCommerce Services, was either misconfigured or incomplete.

Resolution steps

  1. Patched WooCommerce Shipping & Tax temporarily:
    • Applied an emergency override to bypass the error and access the site.
    • Later confirmed the plugin update resolved the migration, so the patch was safely removed.
  2. Enabled new Stripe checkout:
    • Activated the modern Stripe checkout from the plugin settings.
    • Tested the checkout page for design or functionality issues — none were found.
  3. Tax settings resolved:
    • Verified that automated tax calculation was only working for VA.
    • Ensured Jetpack was connected and WooCommerce Services were active.
    • Enabled automated taxes under WooCommerce → Settings → Tax.
    • Confirmed geolocation settings were enabled.
    • Offered to import standard CSV tax rate files for other states if automated service was insufficient.

Final outcome

With plugin versions updated and automated settings properly configured, the database migration completed successfully, Stripe’s checkout was modernized, and tax calculations became more flexible. The WooCommerce store now runs error-free, with a smoother checkout experience and improved compliance for multi-state sales.

Experiencing WooCommerce plugin conflicts or tax setup issues? Contact Freshy — we can help stabilize and scale your WordPress eCommerce setup.