833
this post was submitted on 11 Oct 2023
833 points (99.4% liked)
Technology
59598 readers
3448 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Use your ip address or GPS location or address to get your location and use a sales tax api product like: https://www.avalara.com/us/en/products/integrations/avalara-api.html
Not an endorsement, just an example that companies already consider this.
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.
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.
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.
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.
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. 🤷♂️