Prompt
Vatlayer doesn't seem to handle product taxability well
Latest observation
Yeah, that can happen. VAT/taxability APIs often struggle with product-level edge cases because “is this taxable?” depends on a lot more than just the item name.
Common reasons vatlayer may look unreliable:
- Product classification is ambiguous: a “book,” “food,” or “software” item may be treated differently by country.
- Jurisdiction matters: taxability can change by country, region, or even municipality.
- Digital vs physical goods: many APIs don’t fully model this distinction.
- Exemptions and reduced rates: some items are taxable but at reduced or zero rates.
- Business context: B2B vs B2C, VAT registration, reverse charge, etc.
- Limited product metadata: if the API only gets a product name, it may guess incorrectly.
What usually works better:
-
Use a product tax rules engine
Keep your own mapping of product categories to tax codes, then use VAT APIs only for rate calculation. -
Classify products yourself
Store fields like:- product category
- physical/digital
- consumable/non-consumable
- exemption flags
- HS/commodity codes if relevant
-
Treat vatlayer as rate lookup, not authority on taxability
Let it provide country VAT rates, while your application decides whether the item is taxable. -
Build a jurisdiction-aware rules table
Especially if you sell in multiple countries, this is often necessary.
If you want, I can help you design a better product taxability approach or suggest alternative APIs/libraries depending on your stack and countries.
Brands