Sofyan Sitorus

Hi,

Thanks for reaching out. At the moment, the thread only says “i can not get this to charge a delivery per item” and doesn’t include the setup details needed to verify whether this is a configuration issue or something else.

To help further, please send us the following:

• WooReer version
• WordPress version
• WooCommerce version
• Which API provider you are using
• Your expected result
  Example: “If 1 item = USD 10 shipping, then 3 items should = USD 30”
• Your actual result
  Example: “3 items still only charge USD 10”
• A screenshot of:
• the WooReer shipping method settings
• the table rates
• the cart/checkout result
• The exact steps to reproduce
• If possible, a short screen recording showing the setup and checkout test

If logging is available in your installed version, please also enable WooReer logging and share the log from one checkout attempt via WooCommerce → Status → Logs. That will help confirm whether the plugin is calculating the rate once per cart or per item.

Without the full setup details, we can’t reliably confirm whether this is a bug or just a rule configuration mismatch. If you share the screenshots and a complete test scenario, we can help you narrow it down much faster.

Once you send the configuration screenshots and expected vs actual behavior, I’ll help you check the correct setup.

Hi @avneeeesh,

Thanks for reaching out, and for the detailed description. I can see exactly what’s happening here!

You’ve correctly identified the root cause: when you change the address using your autocomplete plugin, WooCommerce’s checkout update mechanism isn’t being triggered, so WooReer never gets a chance to recalculate the shipping distance. This is a third-party address autocomplete plugin integration issue, not a bug in WooReer itself.

What’s Happening Under the Hood

WooReer (like all WooCommerce shipping plugins) relies on WooCommerce dispatches a request to the WooCommerce REST API endpoint whenever address fields change. Under normal circumstances, WooCommerce listens for change or blur events on its native checkout input fields and then dispatches a request to the WooCommerce REST API endpoint to recalculate rates.

When an autocomplete plugin populates the address fields programmatically (rather than the customer typing directly), it often fills the inputs using JavaScript without triggering the native browser change event that WooCommerce is listening for. As a result:

• The fields appear filled in visually ✅
• But WooCommerce never detects a change ❌
• So no REST API request is dispatched ❌
• And WooReer never recalculates the distance or shipping rate ❌

This matches precisely what you — and our developer notes — have observed: no request is being dispatched to the WooCommerce REST API endpoint when the address is updated.

• This reply was modified 2 months ago by Sofyan Sitorus.

Hi Deirdra,

Thanks for reporting this, and sorry for the frustration here.

Based on what you described, the most likely cause is that the Google API key passes in another plugin but does not meet WooReer’s specific requirement for the Google Routes API. In other words, a key can still work elsewhere for Maps/Geocoding/Places, but WooReer needs the Routes API enabled and billing active for validation to succeed.

I have tried several common validation cases below:

• Routes API is not enabled
• Billing is not enabled on the Google Cloud project
• The API key is invalid
• The API key field is empty
• The API key has an IP address restriction
• The API key has an application restriction

All of them are outputting the following error messages:

• Routes API not enabled
  Distance Calculator API » Routes API has not been used in project ... before or it is disabled ... Check the log for more details.
• Billing not enabled
  Distance Calculator API » This API method requires billing to be enabled ... Check the log for more details.
• Invalid key
  Distance Calculator API » API key not valid. Please pass a valid API key » Check the log for more details.
• Empty key
  Distance Calculator API » API Key field is required
• IP address restriction
  Distance Calculator API » The provided API key has an IP address restriction. The originating IP address of the call (xxx.xxx.xxx.xxx) violates this restriction » Check the log for more details.
• Application restriction
  Distance Calculator API » Requests to this API routes.googleapis.com method google.maps.routing.v2.Routes.ComputeRoutes are blocked » Check the log for more details.

Please try the following

1. Confirm the API provider

• Make sure the provider used in WooReer is Google Maps Routes API.

2. Verify the Google Cloud setup

• In the client’s Google Cloud project, confirm:
  • Routes API is enabled
  • Billing is enabled
  • The key is from the same project
• If Routes API or billing was just enabled, wait a few minutes and test again.

3. Check API key restrictions

• If the key has restrictions, please verify they are not blocking the request.
• In particular, check:
  • Application restrictions
  • API restrictions
• A key that works in another plugin may still be restricted in a way that prevents WooReer’s request from succeeding.

4. Enable WooReer logging and check the log output

• Please enable logging in WooReer, then try saving the key again.
• The log should usually contain the exact Google response, which will tell us whether this is:
  • missing Routes API
  • missing billing
  • invalid key
  • restriction-related

5. Test with a fresh API key if possible

• If the client can create another key in the same project with Routes API enabled and billing active, that would be a very useful comparison test.

Important note

Unfortunately, I can’t ask you to share the actual API key or site access in the public forum. So if the issue is specific to that one key/project, my ability to fully verify it here is limited.

If you can’t generate a new key yourself, the best next step would be to ask the client to verify the Google Cloud configuration above, especially:

• Routes API enabled
• Billing enabled
• Key restrictions
• Project consistency

For now, my best assessment is that this is most likely a Google Cloud/API configuration issue rather than a random save failure, though if you’re not seeing any admin notice at all, there may also be a UI/feedback bug worth investigating further.

Best Regards,
Sofyan

Is it possible to count shipping rate as per kM delivery….

Yes, you can achieve the shipping cost structure described in the table by utilizing the Min/Max Total Cost together with a Custom Shipping Class for products with specific dimensions.

Hi Anil,

That’s wonderful news. So glad to hear you got it sorted out! 🎉

While you’ve resolved it, it would be really helpful for the community if you could briefly share what specifically fixed the issue in this thread. Other users in similar regions or with the same setup might run into the exact same problem, and your experience could save them a lot of time! 😊

If you ever run into any other questions or issues with WooReer down the road, don’t hesitate to reach out, we’re always happy to help.

Thanks for your patience throughout the process, and wishing you and your store all the best!

Best regards,
Sofyan

Hi Anil,

Thank you for following up, and I’m sorry to hear the issue is still persisting after the update! 😊 Let’s work through this together and get your shipping options showing correctly.

I noticed the screenshot you shared, but to properly diagnose what’s happening on your end, the most important next step is to enable WooReer’s built-in logging so we can see exactly what’s happening during the distance calculation process.

1. Go to WooCommerce → Settings → Shipping
2. Click on your WooReer shipping zone
3. Open the WooReer method settings
4. Scroll down and Enable Log option and enable it.
5. Save your settings
6. Perform a test checkout (add a product to cart and proceed to checkout with a full shipping address)
7. Go to WooCommerce → Status → Logs (https://yourdomain.com/wp-admin/admin.php?page=wc-status&tab=logs), select the WooReer log file (prefixed by wcsdm), and copy/paste the log content here

The log file will be the fastest way for us to pinpoint the root cause. Once you share it, we can identify whether it’s an API communication issue, an address resolution problem, or a configuration mismatch.

Looking forward to getting this sorted out for you! 🙌

Best regards,
Sofyan

Thank you for the wonderful review! So glad the plugin is working great for you. 🙏

We keep it free because we believe everyone deserves quality tools. If you’d like to support future development, you can always buy me a coffee—no pressure at all!

Thanks again for taking the time to leave feedback. Cheers!

@kuzcotopia From the log you attached, I can see you put OO (double zero) for the max order amount field in the table rates configuration. Please give a try to update it as empty string or single zero.

Hope this helps.

Sofyan