Decide tax treatment per product and jurisdiction
Reasons the correct tax treatment and processor tax-rule configuration for a product type across the markets it sells into, determining which jurisdictions to collect in, applicable rates, and when nexus thresholds are approached.
In / outProduct type + target markets → tax treatment decision per jurisdiction (collect/exempt, rate, nexus threshold proximity) ready for processor config
You might say…
“I sell to the US and UK and I genuinely don't know if I should be collecting VAT or if my course counts as a digital service — I just copy what I did before.”
What it does
Given a product type (digital good, service, membership) and the markets it sells into, reasons the correct tax treatment and processor tax-rule configuration — which jurisdictions to collect in, applicable rates/exemptions, and when nexus thresholds are being approached. Used when adding a product, entering a new market, or when tax rules change.
Trigger: Use when adding a new product, entering a new market, or when tax rules change — before updating processor tax configuration.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation