It’s an imperfect solution. VPNs are an issue - and even if you don’t use a VPN, the API only knows the location of the ISP’s servers - which can be in a different state.
My point was that, the law should leave tax inclusion in pricing as optional. There is no way to implement automatic detection cleanly, other than prompting the user to confirm their location, which is a huge annoyance - so the ‘tax inclusion’ rule would not make things better or more convenient.
elbrar@pawb.social 8 months ago
that would very much wreak havoc with caching since you basically can’t cache pricing including sales tax as it depends on your very specific location.
of course, for things like event tickets, it’s the venue’s location that matters for tax, so it works out to be a non-issue.
snowsuit2654@lemmy.blahaj.zone 8 months ago
Maybe you could do more localized caching. Localities with different sales tax are finite and few. Cache pages based on those localities and then serve pages based on the IP of the client. It’s not ideal or as optimal, but it’s not that unreasonable in my mind. If it became the norm we’d build the infrastructure to sustain it.
ericisshort@lemmy.world 8 months ago
Companies have no problem doing it to comply with EU regulations which require tax to be included, so I see no technical reason why they couldnt figure it out for the US.
floppade@lemm.ee 8 months ago
Fair, I admittedly don’t know how one would implement it, but the sales tax data is being used by their clients for something.
Looking into it further, some states, according to Shopify’s FAQ on the topic, have different rules with regards to destination-sourced vs origin-sourced sales. 🤷♂️