• Sam Wave

    (@nextwavingit)


    We utilized this plugin and Stripe’s tax service because, on paper, it’s very reasonably priced for the volume of sales we do. However, there are two major issues that it seems you are overlooking that make this plugin much more costly.

    1) The plugin treats all guest customers as if they’re coming from the state where the store is located (one where tax is collected). Therefore, every time the customer views their cart or checkout page, unnecessary (and costly!) API calls are made until they fill out an address where no tax is collected.

    Some important notes: The WooCommerce Tax setting “Calculate tax based on” is set to “Customer shipping address” while the “Default customer location” is set to “No location by default.” Obviously this plugin is not taking these settings into account.

    2) Compounding issue #1, there is no way to disable tax calculation on the cart page, which customers might view many times. I noticed you responded to a negative review on woo.com complaining about this over a year ago, promising updates. . .

    Unless a store receives practically no traffic, this plugin effectively makes the “pay-as-you-go” Stripe Tax plan useless, as the API calls quickly add up to more than the $90/mo. plan.

    I would love to receive some feedback to know if you are working on correcting these issues. My client is pretty unhappy right now because we estimated a price based off their traffic in taxable states and it seems that this plugin is intentionally designed to make unnecessary API calls to rack up chargers.

Viewing 2 replies - 1 through 2 (of 2 total)
  • rjozsastripe

    (@rjozsastripe)

    Hello Sam,

    Thank you for reaching out and providing feedback. I completely understand why you and your client are frustrated. I can assure you our intention is not to artificially inflate prices.

    1) The plugin is currently defaulting guest users to the store’s base state, bypassing the WooCommerce “No location by default” setting. This is causing unnecessary API calls before a user inputs their actual address. Our team has already addressed this, and a fix will be included in our next release v2.0.3.

    2) I am not aware of this feature being our roadmap, I will have to run it by the team. Can you please provide us some additional details?

    Best regards,
    Robert

    rjozsastripe

    (@rjozsastripe)

    Hello Sam,

    As an update – we have added to the backlog your feature request regarding being able to disable tax calculations on the cart page.

    Thank you again for your feedback.

    Best regards,
    Robert

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.