Manual Tax Rate CSV Import Failure

  • Resolved grandvalleydave

    (@grandvalleydave)


    6 years, 1 month ago

    I discovered recently that the automated sales tax rate lookup information for WooCommerce (provided by TaxJar via Services) for the State of Colorado is incorrect. This was verified by WooCommerce via a support ticket (#1756083). WooCommerce has been unable to provide support (pointing fingers at TaxJar) and only offered the option of manually uploading the sales tax information via the CSV Import option in the Settings – Tax – Standard rates section of the WooCommerce plugin. Before uploading a template file containing example data is offered so you can make sure your CSV file is formatted correctly and contains all the necessary data.

    I was able to purchase a CSV file containing all the sales tax information for the State of Colorado and conformed the data I needed (based on the template file) into a new file that I exported as a CSV. Upon import, all the data for City and Zipcode get stripped out of the file and not imported (replaced with an *) rendering the Standard rate Sales Tax table useless since it uses Zipcode to look up the Sales Tax rate for each purchase (based on customer shipping address).

    I deleted the data in the table (a very tedious and wonky process), and tried the import again hoping that there was just a hiccup on the first attempt. Nope. Same issue.

    Since the CSV file contains 643 rows of data, I decided to test to see if it was just choking on the amount of data. I broke the table into 10 records and attempted the import again. Nope. Same issue.

    So I decided to test to see if the issue was that my CSV file had an issue. After cleaning the Standard rates table again, I imported the example template file provided by WooCommerce as an example of how your CSV file should be formatted and organized. Nope! This file, supposedly a known-good file, fails with the same issue.

    Anyone have any ideas?

    Dave

    • This topic was modified 6 years, 1 month ago by grandvalleydave. Reason: added clarity about issue with CO sales tax and the Support Ticket #
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter grandvalleydave

    (@grandvalleydave)

    After extensive testing, I have figured out that the conflict is between WooCommerce and Jetpack. ARRRRRGGG!

    If “Code is Poetry”, Automattic needs to do some more talking to itself.

    Dave

    Thread Starter grandvalleydave

    (@grandvalleydave)

    Marking the issue as “SOLVED”, but clearly there are some significant, fundamental challenges with WooCommerce as a modern online sales system.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Manual Tax Rate CSV Import Failure’ is closed to new replies.