Title: version 3 doesnt work
Last modified: January 12, 2026

---

# version 3 doesnt work

 *  [funkyj4ever](https://wordpress.org/support/users/funkyj4ever/)
 * (@funkyj4ever)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/)
 * Hi,
 * I used it for years. But when i update to v3 its no longer working. I just get
   no shipping method available. Nothing in the logs

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

 *  Plugin Author [Sofyan Sitorus](https://wordpress.org/support/users/sofyansitorus/)
 * (@sofyansitorus)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18784361)
 * Hi [@funkyj4ever](https://wordpress.org/support/users/funkyj4ever/),
 * Thank you for reporting this and for the detailed explanation.
 * Based on our investigation, it appears the issue is related to the legacy framework
   that handle WooReer configuration before version 3.x did not work correctly. 
   Starting from version 3, WooReer no longer uses the **Google Distance Matrix 
   API**. Instead, it now relies on the **Google Routes API**. Because of this change,
   existing installations **must be re-configured** after updating from version 
   2.x to version 3.x. If the Routes API is not properly enabled and configured,
   WooCommerce may display _“No shipping options were found”_, even though no errors
   appear in the logs.
 * Regarding your question about API keys:
    - The Distance Matrix API is **no longer used** in version 3.
    - You should ensure that the **Google Routes API** is enabled and correctly 
      configured.
    - Other APIs (Geocoding, Maps JavaScript, Places) may still be required depending
      on your site setup, but the key requirement for distance calculation in v3
      is the Routes API.
 * As an **alternative workaround**, you may revert WooReer to **version 2.2.4**,
   which still uses the Distance Matrix API and should work with your previous configuration.
 * To help us investigate this further and prepare a proper fix or guidance, it 
   would be very helpful if you could provide the following details:
    - Installed **WordPress version**
    - **WooCommerce version**
    - **Active theme name and version** (including the URL of the theme’s homepage)
    - The **first and last row** of your **Table Rates configuration**
 * Once we have this information, we can reproduce the issue more accurately and
   provide more targeted assistance.
 * Thank you for your patience and continued support.
 * Kind regards,
   Sofyan
 *  Thread Starter [funkyj4ever](https://wordpress.org/support/users/funkyj4ever/)
 * (@funkyj4ever)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18784672)
 * I paste my api key in the settings box no errors but still not working. I enabled
   routes etc
 *  Plugin Author [Sofyan Sitorus](https://wordpress.org/support/users/sofyansitorus/)
 * (@sofyansitorus)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18784749)
 * [@funkyj4ever](https://wordpress.org/support/users/funkyj4ever/)
 * To help us investigate this further and prepare a proper fix or guidance, it 
   would be very helpful if you could provide the following details:
    - Installed **WordPress version**
    - **WooCommerce version**
    - **Active theme name and version** (including the URL of the theme’s homepage)
    - The **first and last row** of your **Table Rates configuration**
 * Once we have this information, we can reproduce the issue more accurately and
   provide more targeted assistance.
 *  Plugin Author [Sofyan Sitorus](https://wordpress.org/support/users/sofyansitorus/)
 * (@sofyansitorus)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18786552)
 * Hi [@funkyj4ever](https://wordpress.org/support/users/funkyj4ever/),
   Thank you
   for your patience while we investigated this issue.We’ve identified and addressed
   the problem in version 3.0.4, which has just been released. The fix resolves 
   the configuration handling that was causing the “No shipping options were found”
   message on some installations after upgrading from version 2.x.If you continue
   to experience any issues after updating, please share the details I mentioned
   earlier (WordPress version, WooCommerce version, theme info, and Table Rates 
   configuration), and we’ll be happy to dig deeper.Thank you for reporting this—
   your feedback helped us improve WooReer for everyone.
 *  Thread Starter [funkyj4ever](https://wordpress.org/support/users/funkyj4ever/)
 * (@funkyj4ever)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18787478)
 * I tested it. Still not working. I did get a calculation. but after choosing which
   api i want to use google maps. and fill in the key i get the same issue again.
   I do got a log now. Also i do use **WooCommerce Checkout Manager**
 * **2026-01-15T18:26:35+00:00Fout** Legacy shipping calculation error: API request
   parameter is empty: destination Aanvullende context{ “data”: { “package”: { “
   contents”: { “1e80f026cb64ca4ba830bebdfcc5b7eb”: { “addons”: [], “booking”: {“
   _year”: 2026, “_month”: 1, “_day”: 20, “_persons”: [], “_date”: “2026-1-20”, “
   date”: “20 januari 2026”, “_time”: “”, “_qty”: 1, “_start_date”: 1768867200, “
   _end_date”: 1768953599, “_all_day”: 1, “_local_timezone”: “”, “_cost”: 345, “
   _booking_id”: 38646 }, “key”: “1e80f026cb64ca4ba830bebdfcc5b7eb”, “product_id”:
   486, “variation_id”: 0, “variation”: [], “quantity”: 1, “data”: { “availability_rules”:[],“
   check_in_cart”: true, “confirmed_order_bookings”: [] }, “data_hash”: “70fbd381c354ab9d174c2a17a55bda58”,“
   line_tax_data”: { “subtotal”: [], “total”: [] }, “line_subtotal”: 345, “line_subtotal_tax”:
   0, “line_total”: 345, “line_tax”: 0 } }, “contents_cost”: 345, “applied_coupons”:[],“
   user”: { “ID”: 1 }, “destination”: { “country”: “NL”, “state”: “”, “postcode”:“”,“
   city”: “”, “address”: “”, “address_1”: “”, “address_2”: “” }, “cart_subtotal”:“
   345”, “rates”: [] } } }[](https://hallofoto.nl/wp-admin/admin.php?page=wc-status&tab=logs&view=single_file&file_id=wcsdm-9-2026-01-15#L2)**
   2026-01-15T18:26:36+00:00Info** Using legacy shipping calculation for data version
   2.1.0 Aanvullende context{ “data”: { “id”: “wcsdm:9”, “cost”: 0, “label”: “Gratis(
   4 km)”, “package”: { “contents”: { “1e80f026cb64ca4ba830bebdfcc5b7eb”: { “addons”:[],“
   booking”: { “_year”: 2026, “_month”: 1, “_day”: 20, “_persons”: [], “_date”: “
   2026-1-20”, “date”: “20 januari 2026”, “_time”: “”, “_qty”: 1, “_start_date”:
   1768867200, “_end_date”: 1768953599, “_all_day”: 1, “_local_timezone”: “”, “_cost”:
   345, “_booking_id”: 38646 }, “key”: “1e80f026cb64ca4ba830bebdfcc5b7eb”, “product_id”:
   486, “variation_id”: 0, “variation”: [], “quantity”: 1, “data_hash”: “70fbd381c354ab9d174c2a17a55bda58”,“
   line_tax_data”: { “subtotal”: [], “total”: [] }, “line_subtotal”: 345, “line_subtotal_tax”:
   0, “line_total”: 345, “line_tax”: 0, “data”: { “availability_rules”: [], “check_in_cart”:
   true, “confirmed_order_bookings”: [] } } }, “contents_cost”: 345, “applied_coupons”:[],“
   user”: { “ID”: 1 }, “destination”: { “country”: “NL”, “state”: “”, “postcode”:“
   2314 XN”, “city”: “leiden”, “address”: “Kasteellaan 1”, “address_1”: “Kasteellaan
   1”, “address_2”: “” }, “cart_subtotal”: “345”, “rates”: [] }, “meta_data”: { “
   api_response”: { “distance”: 4, “distance_text”: “4 km”, “duration”: 593, “duration_text”:“
   9 minutes” } } } },
 *  Plugin Author [Sofyan Sitorus](https://wordpress.org/support/users/sofyansitorus/)
 * (@sofyansitorus)
 * [4 months, 2 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18789502)
 * [@funkyj4ever](https://wordpress.org/support/users/funkyj4ever/), thanks for 
   the feedback and log. From the log you provided, I can see that the plugin now
   works fine in legacy mode. The issue appears only when you updated the settings
   to use the Google Routes API. As you mentioned that you use WooCommerce Checkout
   Manager, I suspect that the version 3.0 of the plugin is conflicting with it.
   If you could provide details about the settings or customizations you made with
   the WooCommerce Checkout Manager plugin, that would help me investigate further.

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fversion-3-doesnt-work%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/wcsdm/assets/icon-256x256.png?rev=3405790)
 * [WooReer](https://wordpress.org/plugins/wcsdm/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wcsdm/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wcsdm/)
 * [Active Topics](https://wordpress.org/support/plugin/wcsdm/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wcsdm/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wcsdm/reviews/)

 * 6 replies
 * 4 participants
 * Last reply from: [Sofyan Sitorus](https://wordpress.org/support/users/sofyansitorus/)
 * Last activity: [4 months, 2 weeks ago](https://wordpress.org/support/topic/version-3-doesnt-work/#post-18789502)
 * Status: not resolved