Liquidator3358
Explorer
Contact Me
Status
Offline
Last Activity
‎03-12-2024 01:21 PM
Topic Started
12
Topics Started
Topic Solutions
1
Solution
Post Count
44
Posts
Post Kudos
15
Likes

Community Badges

No content to show

User Activity

So, I am getting the dreadful "Shipping not available Your order cannot be shipped to the selected address. Review your address to ensure it's correct and try again, or select a different address." error and I have no idea why. Here is what I know:- ...
Yeah, unfortunately, this is not correct.  When it comes to your domain, if you point it to your headless application (which we all will), the checkout will be set to default my-store.shopify.com.  This means all links (for instance, the logo on the ...
@ShopifyDevSup  My man! That helps a ton.  I am talking to Vercel today, so I will pass this on. Thanks a bunch for looking into it.
@ShopifyDevSup  Hey Al, Not meaning to press you on this but I wanted to pick your brain before I move on.  I have a ticket out with Vercel as well, so I am trying to spearhead this thing from all three sides (my code included).
Hey @ShopifyDevSup  (Al), Okay, so here is where I am at. I have tried all the logging imaginable on my end, and it seems to be all for naught because nothing gets logged when it fails.  So for instance, I just tested it 10 times and it finally faile...
Unfortunately, you are limited to the request body, which is simply shipping info, and nothing more. You're going to need to somehow use that data to then go return what ever data you need via another api call.  Since all the session data is tied to ...
Sorry for the confusion @ShopifyDevSup  - I was detailing out how I am caching the rates on my end so that the rate retrieval process is done quickly. Okay, so I took your advice and changed the callback URL back to an ngrok route... I literally CAN'...
Alright... last bump.  Again, callback_url receives request from Shopify, rates are cached BEFORE the callback receives the request (you literally cannot proceed to checkout without having rates, there the rates are always ready to go), callback endp...
Interesting... that would explain the inconsistency.  My rates are cached before I even get to checkout, so speed SHOULDN'T be an issue (pulling from redis).  That time constraint would explain the absolute randomness that has been happening... If I ...
Does this include the default DHL/UPS/USPS that are in there? Also, my problem isn't getting the rates to work 90% of the time... my problem is the random 10% of the time when it doesn't take my rates and in defaults me to Shopify's rate.  I have ZER...
I completely missed that first suggestion and I see what you are saying.  Somehow, use the checkout/create webhook to fire my shipping rates, which will allow for the right data to be in play.
Wait, on your #1, how would I pull the customer's ID from the payload?  From what I know, you only get what's inside the req.body (origin/destination, customer's info and cart items - I don't recall seeing the customerId?) and you can't send any extr...
Hey Al, I actually did this a different way but now that you are here, I would like to pick your brain about something related.  This is how I am currently doing it: 1.  The rates get fetched and cached as the user adds/removes items throughout the s...
Per the usual, not a single word on this from Shopify.  There are threads littered with similar postings and often times, they fall completely on deaf ears.  With shipping and logistics being such an integral part of eCommerce, and with brokers/carri...
I mean seriously, can one Shopify employee who has a little knowledge troubleshoot this with me?  It makes zero sense... Shopify Support is zero help when it comes to the API, so surely another dev has a the slightest clue as to what is going on? The...
This widget could not be displayed.
This widget could not be displayed.