Forum Replies Created

Viewing 15 replies - 16 through 30 (of 74 total)
  • Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @richecolocity

    Thanks for sending this over! Looking at the logs, could you try going to WooCommerce > Settings and removing the trailing space from the end of the City field, then clear the API cache under Integration, and let us know if that changes the results during checkout? (We don’t need logs on this test unless it gives back different errors).

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @richecolocity

    Could you try clearing the cache via WooCommerce > Settings > Integration > ShipStatation > Clear API Cache

    It could be a bad initial cache if the WooCommerce store settings were updated after the plugin was set up, but clearing the cache will at least give a clean slate.

    If you’ve cleared the cache and it’s still not returning rates, you could enable Logging under the same Integration page, try a test checkout, then navigate to WooCommerce > Status >Logs and download the Live Rates for ShipStation.

    If you want to take a look at the downloaded logs, scrub any data you deem to be sensitive, and post some of that to the public forum thread here, we’ll be able to take a look at what the API is returning.

    Finally, is the U.S. state you’re shipping from considered an Outlying Island or Territory?

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @richecolocity

    Have you also set up your Shipping Zones?

    This is found under WooCommerce > Shipping after which you would add Live Rates for ShipStation as a shipping method and then set up the services and packages you would need to use.

    Plugin Support IQComputing Alex

    (@iqcalex)

    Do you get that same error when testing this against the Shipping Calculator within ShipStation? Could this be injunction with a specific carrier?

    Do you have an example of an address that should return rates but does not?

    For example, we’ve tried the following and received rates from both UPS Standard and UPS Standard Intl.
    1234 Canada Lane
    North River
    Ontario
    M0X 1Z9

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @tsso0120

    We’ll look into this issue as we may need to make an option to account for this difference between WooCommerce and ShipStation in this case.

    We will add the estimated delivery days onto our feature list. ShipStation does bring that back with the API results so it is doable.

    We don’t have a timeline for this, but if you stay subscribed to the thread, we’ll keep you updated when a solution is in place.

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @centuryperf

    Apologies, this thread went under our radar, were you able to resolve this issue? We have had another user report issues with ShipStation API and Canada, but that had to do with GLS.

    Are you able to replicate this issue using the calculator within ShipSatation directly?

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @centuryperf

    Sorry about that! We have published a new update which adds a new option to clear all data on uninstall. On normal uninstall we’ve opted to keep all shipping methods and settings in case there’s a reinstall. Hopefully this prevents future issues while also trying to keep the WordPress database clean on removal.

    Hello @robersw

    Thanks for the suggestion ! We’ve implemented it in the latest version of the plugin. Should the Shipping API Key ever get lost in the shuffle in the future, an Admin Notice will appear with a link to the integration settings page. Hopefully, this notice only appears once after install, but it’s a good idea to have as a fallback notice.

    If either of you run into any other issues on this version, please create a new thread so that we may track the progress of those issues. Thanks again and have a wonderful rest of your week!

    Plugin Support IQComputing Alex

    (@iqcalex)

    @centuryperf Hello,

    Sorry about that, but thank you for the report information, it was instrumental in tracking down the issue to patch. We have published a v1.2.3 which resolves this issue. Please let us know if you run into any other issues or oddities and our team will take a look!

    Plugin Support IQComputing Alex

    (@iqcalex)

    Hello @nextphase

    Thanks for reporting this issue! We were able to replicate this on our end and have published a patch for it. We hope to have it live on WordPress.org soon. In the meantime, you can download the latest patched version at the link below:

    https://github.com/IQComputing/live-rates-for-shipstation/releases/tag/v1.2.1

    Plugin Support IQComputing Alex

    (@iqcalex)

    @marstarcanada Hello

    Good News!

    We’ve heard back from ShipStation and they suggested that a patch was pushed to their API to resolve this issue. I wasn’t able to verify this in my tests – rates appear to still be coming back as USD currency but that may be due to my root store being US based. Would you be able to test this on your end and let us know if you’re seeing CAD for GLS Canada?

    Plugin Support IQComputing Alex

    (@iqcalex)

    @marstarcanada Hello

    Thank you, I hope you and your had a good Christmas as well!

    Unfortunately, we haven’t heard back from ShipStation. It seems like they are aware of this issue and did acknowledged it in our prevoius discourse. We’ve sent them another email this morning to nudge them and will reply back to this thread with any pertinent information.

    Plugin Support IQComputing Alex

    (@iqcalex)

    @neee Hello,

    The Custom Packing Boxes system takes into account the Package Volume (based on dimensions) and Product Volume (also based on dimensions) then tries to find the best Package to Product volume match which would fit as many products in a box before moving to the next “batch” (to retest remaining volume).

    It’s important when setting up Custom Packing Boxes that both the Package and the Product has it’s dimensions set. Otherwise, the Custom Packing Boxes system won’t be able to accurately calculate volume, skip trying to pack the product, and will default to getting an estimate based on the known Product dimensions (ala shipped individually).

    If there are multiple Packages (or a mix of Packages and individual Products), the API gets estimates per package, then WooCommerce groups the costs and displays the sum to the customer. On the Edit Order screen these should be broken down into which Products ended up in which Custom Packing Boxes.

    Hopefully you’re able to get the Custom Packing Boxes working for you. Otherwise, there are some other Product Packing options available, and the plugin has a PHP Development filter hook for developers to add in custom logic.

    Plugin Support IQComputing Alex

    (@iqcalex)

    @neee Hello,

    We have published an update to address the caching issues. Could you please update the plugin and let us know if you continue to run into issues?

    Plugin Support IQComputing Alex

    (@iqcalex)

    @neee Hello,

    Apologies for the inconvenience, but I don’t think there’s a workaround for a live site. We do have this in our upcoming branch to be pushed out early next week. I’ll reply back to this thread once the update goes live so that if you are subscribed to the thread you’ll receive a notification.

    You may be able to download the upcoming branch from Github as this should be stable, but it’s also a development branch so all changes may not be reflected. We do recommend installing this on a staging website first to ensure it works as you expect it to.

    https://github.com/IQComputing/live-rates-for-shipstation/tree/upcoming

    Plugin Support IQComputing Alex

    (@iqcalex)

    @neee Hello,

    We do cache the returned results to prevent multiple requests. This is due to multiple reasons:

    Earlier you mentioned that you had “…read ShipStation takes a while to populate the shipping rates”, which is one of the reasons. ShipStation itself takes a decent amount of time to give us rates from it’s API, close to ~30-45 seconds per request in some cases and depending on how many Carriers we need to get rate estimates from. In addition to this, WooCommerce itself pings the Shipping Method multiple times during a normal page load and requests to run Shipping Calculations.

    Looking at our caching mechanism, I do see what you mean. We really should be including the destination in the caching key generation. I’ve made a note for our team to put together a patch for this issue which will be included in the next version that we plan to ship this month.

    I’ll reply back to this thread whenever this update goes live so that if you’re subscribed you’ll receive a notification. Thank you for the report!

Viewing 15 replies - 16 through 30 (of 74 total)