It's usually not possible because you don't know how much the shipping + taxes are until the customer enters the billing information.
It's usually not possible because you don't know how much the shipping + taxes are until the customer enters the billing information.
A postal code should suffice, and I'm not providing more personal information if the site is unwilling to say what I'll be charged upfront.
A relatively common example would be shops using the Shopify platform.
Any good UX designer can come up with a solution for this in a couple of hours or less. There's just no motivation to make it happen because this obfuscation of data is particularly optimized and useful for the sellers.
You can approximate UPS/FedEX costs by fitting a trend line, they are decently modeled by a linear (base charge + K*distance) function, but when you go to buy the label you might be way off. This puts you in the lose-lose-lose of either eating the difference of wrong estimates, overcharging for shipping and losing conversions, or just making people hate you by increasing the shipping over the estimate. Making a shipping API call is noticeably slow, so most people require an interaction after the address is entered.
Tim Sweeney's hot take was that "the two hardest problems in computer science are cache invalidation and shopping carts!"
If they're doing that anyways, they should have everything they need to hazard a pretty good guess (and then they have an actual inducement for me to provide it).
It's really not that weird when you consider the US is not a unitary state.
Something like: we will allow you to sell our product but only if you don't advertise discounts more than x%.
Sure, they show you a different content depending on your IP address and lots of shady heuristics, but when it comes to estimate a shipping cost, it is absolutely impossible: you can just be anywhere, who knows where you are. I say bullshit.