Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Malaysia and Singapore as tax_inclusive #323

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

rochlefebvre
Copy link
Contributor

@rochlefebvre rochlefebvre commented Dec 18, 2024

What are you trying to accomplish?

Shopify considers Malaysia and Singapore to be tax-inclusive countries.

https://www.iras.gov.sg/taxes/goods-services-tax-(gst)/basics-of-gst/invoicing-price-display-and-record-keeping/displaying-and-quoting-prices

I cannot find supporting evidence that prices are indeed tax inclusive in Malaysia 🤷, but for now let's update the yaml to be consistent.

Checklist

  • I have added a CHANGELOG entry for this change (or determined that it isn't needed)

@rochlefebvre rochlefebvre force-pushed the make-SG-and-MY-tax-inclusive branch from 0613025 to a752e08 Compare December 18, 2024 20:38
@rochlefebvre rochlefebvre marked this pull request as ready for review December 18, 2024 20:39
@rochlefebvre rochlefebvre requested a review from a team December 18, 2024 20:39
@rochlefebvre rochlefebvre added the #gsd:43663 Deduplicate country metadata label Dec 18, 2024
@rochlefebvre rochlefebvre self-assigned this Dec 18, 2024
Copy link

@jtrollia jtrollia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving with basic questions for my culture personnelle 😅

  • what happens when Shopify and Worldwide disagree on a term?
  • what can go wrong when making such changes? Merchants may complain that they start showing prices with taxes included?

@rochlefebvre
Copy link
Contributor Author

Approving with basic questions for my culture personnelle 😅

  • what happens when Shopify and Worldwide disagree on a term?

Worldwide was created to share Shopify's modeling of countries, zones, languages, and addresses with the world. Most facts contained are held universally true, while some are the result of Shopify picking a value. The tax_inclusive field in particular is not especially accurate, as no country is 100% inclusive or exclusive of tax. It's an approximative fallback, really.

So we try to keep worldwide as an accurate modeling of Shopify's world view, rather than the other way around.

  • what can go wrong when making such changes? Merchants may complain that they start showing prices with taxes included?

Worldwide was created as a fork of an internal gem, which still maintains its own set of facts. Our systems currently rely on this internal gem for modeling the world. We are currently reducing this data duplication by having the internal gem call worldwide underneath.

For important yet subjective attributes like tax_inclusive, we'd rather maintain the "old" answer, which is that Malaysia and Singapore are mostly tax-inclusive. If I didn't push the present PR out, then our internal gem refactoring would lead to a change in these countries' tax setting. I want to prevent such a regression by aligning worldwide with the internal gem.

@rochlefebvre rochlefebvre merged commit ba0437a into main Dec 19, 2024
10 checks passed
@rochlefebvre rochlefebvre deleted the make-SG-and-MY-tax-inclusive branch December 19, 2024 21:43
@rochlefebvre rochlefebvre mentioned this pull request Dec 20, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#gsd:43663 Deduplicate country metadata
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants